Mnemo is built around one idea: memory becomes more useful when its context stays attached.
Capability map
Think of Mnemo as a loop rather than a single editor: capture, organize, resurface, protect, and carry your archive forward.
Input
Capture
Capture writing, media, files, places, and reminders before those fragments disappear into separate tools.
Structure
Organize
Folders, tags, time, place, reminders, and links between entries keep the archive understandable later.
Output
Recall surfaces
Timeline, search, map, calendar, reminders, and media views are designed to bring memory back when it matters.
Ownership
Private archive
Mnemo keeps privacy, archive control, and portability central, with continuity available on top when you want it.
Capture
Mnemo supports multimodal capture for fragments such as:
- writing and rich text
- photos
- audio and voice notes
- videos
- document attachments
- saved links
- places and timestamps
- reminders tied to a moment or entry
The point is not to create more material. It is to preserve enough signal that a fragment still means something later.
Organize
Entries can be structured with:
- folders
- tags
- pinned/starred states
- references to related entries
- time metadata
- place metadata
- reminders
This is what turns scattered fragments into memory with context instead of loose content with no retrieval path.
Recall surfaces
Mnemo is not only a place to save things. It is designed to help you find them again through:
- timeline view
- search
- map view
- calendar view
- media-driven browsing
- reminder-based resurfacing
Each surface answers a different recall need. Sometimes you remember a place. Sometimes a date. Sometimes an image, a word, or a person linked to the moment.
Private archive and portability
Mnemo is built so the archive remains understandable and portable:
- local-first use remains a valid way to use the product
- export and import help with backup, movement, and recovery
- protected access and privacy controls help keep the archive personal
- cloud continuity can extend the archive across devices when you want that layer
Cloud continuity is part of the current product surface, but it should still be described with realistic caveats where environments behave differently.
How the loop works in practice
- Capture something worth keeping.
- Attach enough context that it stays meaningful.
- Revisit it through the surface that matches how you remember.
- Protect and carry the archive forward with privacy controls and optional continuity.