Every note-taking app remembers. That's the easy part. Storage is cheap and search is basically solved.
Here's the hard part, the one we're actually building Margin for:
A note you wrote about your fiancée doesn't know she became your wife.
It sits there, frozen in the tense of the day you wrote it. So does the plan you made with a friend who has since drifted away, the project "currently in flight" that shipped last spring, the person you wrote about every week who died in the fall. A conventional knowledge tool is a photo album that thinks it's a memory. Real memory revises. It knows what changed. It grieves, promotes, archives, and updates the story without being asked, because the story was never a pile of facts. It was a narrative moving through time.
The frozen-knowledge trap
We felt this in our own product the moment its intelligence got good enough to expose it. The Mind could read everything, connect everything, summarize anyone, and every summary was a snapshot. Perfectly grounded in evidence, perfectly blind to the arc. A person described by their oldest mention. A "current" project three months stale. Knowledge that was true when written and quietly wrong now.
The fix is a different contract with knowledge itself.
Facts have tense. When new evidence contradicts old, a status changed, a relationship evolved, a chapter closed, the old fact is superseded. Kept as history, retired as truth, not deleted and not left standing to argue with the new one. The narrative becomes "was engaged, now married," where two contradictory certainties used to stand shoulder to shoulder.
Narratives re-tell themselves. Every synthesized understanding, who a person is to you, what a project means, carries a fingerprint of the evidence it was built from. When the evidence moves, the story knows it's stale and re-tells itself from the full current picture. When nothing moved, the story holds still. A memory that rewrites itself at random is as untrustworthy as one that never updates at all.
Teaching is permanent; instructions are transient. Tell the system to do something differently and it obeys once, then the instruction retires. Tell it who someone is and that's knowledge, flowing into that person's permanent record and shaping everything after. The system sorts your words into the right lifespan on its own.
It knows even when you forget. This is the quiet endgame. A second mind that only recites what you'd have remembered anyway is worth nothing. The value is the thread you dropped: the commitment from March, the friend you haven't written about in ninety days, the project whose momentum silently stalled. Awareness of change, including the change of absence, is the whole feature.
Which is where it gets genuinely hard, and where I don't have a finished answer. How much should a system say about an absence? There's a version of "you haven't mentioned this person in ninety days" that's useful and a version that's ghoulish, and the line between them isn't in the code. It's in grief, and taste, and how a given person on a given morning wants to be reminded of what's gone. We're building the mechanism that can notice. We're still arguing about the manners.
The flywheel
None of this works as a feature you bolt on. It works as a loop:
you live → the system reads → it proposes what it understood → you correct it in seconds (a name, a merge, a "no, that's wrong because…") → the correction becomes permanent knowledge → which sharpens the next reading → which needs fewer corrections → which makes each of your seconds teach more.
Every turn of that wheel moves the system from storing your life toward following it. We validate it the way we build it: make a change, watch the narrative notice. If the story doesn't move when the life does, that's a bug now, filed at the same severity as a crash.
A photo album is honest about what it is. You open it and everyone inside is exactly as old as the day the shutter closed, which is what a photo album is for; nobody wants their photographs to quietly update themselves. What we're building wants the opposite thing from its own memory. That's the gap between an archive and a mind, and most of the work still left is in it.