One store · every assistant
Nothing forgets. Nothing forks.
A memory is a short note an assistant writes down — a decision, a measured result, where a project stands. They all go to one database, on machines we own, and any assistant we allow can read them and add to them.
01One store.
One store. Every assistant reads it, writes it, and picks up mid-sentence.
02Read, write, summarize.
Recall what happened. A tool asks the memory what it already knows and gets the note that was actually written back — not a guess reconstructed on the fly.
Record what's new. A fact learned in one app is written once to the shared store, and every other tool sees it the next time it reads.
Long histories get distilled into short ones, so a session can be caught up in a few lines instead of re-reading months. Recall matches on meaning, not exact wording: ask about a deploy problem from last month and the right note comes back even if it never used those words.
Swap the frame; the token in the middle never moves. That is the arrangement — the tool changes, the memory doesn't.
03In daily use.
In daily use it looks like this. Opening a session, the assistant asks the memory what it already knows about the project and picks up where the last one left off. During the work it writes down anything durable — a ruling, a result, a trap worth not rediscovering. At the end it files a short summary: what landed, what's still open, what's next.
04One record.
Can't be talked into forgetting or lying. Every tool reads and writes the same store, so two of them can't quietly drift into disagreeing about what happened. What's true is what was written down: the record decides, not the phrasing of the question.
The model is swappable. The memory isn't. The memories live outside the model, in one store every assistant reads and writes. Change which model we run and the history doesn't move; it was never inside it. Memory kept inside a model makes every upgrade a small amnesia.
When the store can't be reached, the tool says so out loud: the reply comes back marked stale rather than quietly answering from an old copy. You always know whether you're reading the current record or a fallback.
memory isn't offered on its own yet — it is the substrate under the rest of the family, working every day. To see what it makes possible, start at the front door or read the whole family, mapped.