Memory · A Field Guide
Ask Your Past
Memory is a personal archive for the things you think, see, learn, decide, and experience. You hand it a thought, a screenshot, a voice note, a link. Months later you ask it a question in plain words — and it answers from what you gave it, and shows its work.
Product overview~6 min readPrivate by default
Storage was never the hard part
You already save things. A screenshot of a restaurant a friend swore by. A half-formed idea typed into a notes app at a traffic light. A link you meant to read. A decision you talked yourself into on a walk. The saving happens. It is the finding that fails — three apps, four folders, a search box that only matches words you no longer remember using.
A memory system is not valuable because it holds ten thousand things. It is valuable because it can return the one thing you need, from a question you'd ask a person: “what was that place Sarah recommended?” — not a filename, not a tag you'd have had to invent in advance.
Memory is built around that gap. Capture is made effortless so you actually do it. Organisation happens on its own. And retrieval — the part that usually breaks — is the part the product is really about.
You shouldn't have to remember where you put a memory. You should just be able to ask for it back.
The loop
Four beats. You only do the first one on purpose.
- 01
Capture
Give Memory something — a note, a thought, a photo, a screenshot, a link, a voice memo, a document. No form to fill in, no folder to choose.
- 02
Understand
Memory reads what you gave it and pulls out a title, a short summary, the type, the people, places and projects mentioned, the dates, and the topics. You don't classify anything.
- 03
Remember
It becomes part of the archive — on your timeline, attached to the people and places it touches, linked to related memories. Every new memory adds context to the ones already there.
- 04
Recall
Later, you ask. Memory writes a short answer from your own memories and lists the ones it used, so you can open the originals.
The loop compounds. The longer you use it, the more of your life it can answer for — and the better the connections between memories get.
Ask your past
Recall works in plain language. You ask the way you'd ask a friend who was there. Every answer is written from stored memories and grounded in the ones it used — and if the answer isn't in your memory, Memory says so rather than inventing one.
Connections form on their own
You never build a link by hand. When a memory mentions a person, place or project you've mentioned before, Memory connects them. Open a person and you see every memory they appear in, the places you've been together, the projects you share.
One thread, followed
- Alex — 4 memories
- Project: Memory
- Berlin — the trip in August
- Conversation — “in if we reach a working prototype”
- Decision — no fundraising yet, revisit in September
None of that structure was entered. It's what five separate captures look like once Memory has read them.
What Memory pulls out
For every memory, whether you typed a sentence or dropped in a screenshot, the same set of readings gets extracted — so the archive stays uniform no matter how the thing arrived.
Extracted on capture
- Title
- A short, human name for the memory — not the first 40 characters.
- Summary
- One or two sentences you can scan later without re-reading the whole thing.
- Type
- Thought, note, idea, decision, link, and so on — inferred from the content.
- People
- Who is mentioned. Each becomes a way to navigate, not a profile to maintain.
- Places
- Cities, venues, rooms. A place page collects everything that happened there.
- Projects
- Threads of work, grouped without you creating a folder for each one.
- Dates
- When it happened, separate from when you saved it.
- Topics
- The recurring themes — what you keep coming back to over months.
- Relationships
- Which other memories this one connects to, and how.
Your memories belong to you
A personal archive only works if it's genuinely private, so Memory is built for that from the data model up: every memory is scoped to one account, with row-level isolation, private storage, and no public links — nothing is indexed or shared by default.
AI processing is kept narrow and legible. Answering a question sends the model your question and the few memories that matched it — never the whole archive. Capturing a memory sends only that one memory. There is a one-action export (JSON or Markdown) and a real delete. Memory doesn't make claims its infrastructure can't back up — no “military-grade” theatre, just isolation and controls you can actually use.
What it is not
- Not a notes app — you're not meant to file, foldered and tidy, and come back to organise.
- Not a chatbot — it only answers about your life, from your memories, and admits when it can't.
- Not a productivity dashboard — no streaks, no scores, no nudges to open the app.
- Not a social network — there is no feed and no one else in it.
- Not a system of record you have to feed — if capture is effort, it has already failed.
What it is: a place where your own history is searchable by meaning, and answerable by question.
Who it's for
Anyone who has thought “I know I saved that somewhere.” People with ideas scattered across three apps who want them in one place that connects them. Anyone building something over months who wants to ask their past self what they were thinking in March. And anyone who has felt the small grief of a good thought lost because there was nowhere obvious to put it.
Your brain is for having ideas, not storing them. Memory takes the storing, and hands back the recall.
Capture one thought. Let it be understood. In a year, ask your past a question — and get an answer.
Memory is a personal archiving product. In this build, understanding and recall run on an on-device mock model and all data stays in your browser; connecting an external AI provider is an explicit, per-request choice. Extracted people, places, dates and topics are best-effort and editable.