Continuity you can show.
One retraction. Every tool. A record of who pulled it.
Zephr fans memory out across Claude Code, Cursor and Codex — and pulls it back the moment a decision is wrong, with the reason recorded. Every decision, error, and preference is held as a separate kind with its sources and review state, so a retracted claim is the loudest kind of evidence on the page.
True 2026-01-09 → still true · written 2026-01-09
Session tokens are validated in the edge middleware, never in route handlers.
What Memory keeps
Wrong note in every tool at once. Then it’s gone.
Pull it back and Claude Code, Cursor, and Codex lose it together. Not a silent delete - you, just now, and why.
Where it was
What you get instead
A signed audit line, not a silent delete.
Every pull leaves an attributable line - who, when, why. The next session can read why a note is gone without trusting memory of the reason.
Illustrative example — not live data
It would rather say nothing than make Tuesday up.
Same question, two honest outcomes. A Fact with the file it rests on, or a typed gap - no confirmed note on refresh tokens - and what would fix it. Empty is not a guess.
Session tokens are validated in the edge middleware, never in route handlers.
No confirmed note on refresh tokens.
Empty is not a guess. Confirm a note, or keep asking - it will not invent one.
Illustrative example — not live data
When the source moves, the note should not pretend it did not.
This path is in development. The picture is the intended check: the file shifted, the Fact no longer matches, and we say so - we do not ship it as if it already runs.
Source file
The memory stays readable
Session tokens are validated in the edge middleware, never in route handlers.
Stale - still true - no longer matches
Illustrative example — not live data
Show a colleague. Or leave with the file.
A signed link lasts a week and needs no account. A pack is a file you can take. Break one character and import refuses - the check is the product, not a badge.
zephr packThe packet
intact - accepted
Break one character
Watch what the import sees.
Illustrative example — not live data
What Memory can keep.
The same names as the console. Planned rows stay planned - they do not animate as if they work.
Facts
ShippedObserved and checkable.
Notes
ShippedGeneral context.
Preferences
ShippedTaste, not a fact.
Errors
ShippedA failure was seen.
Decisions
ShippedA choice already made.
Policies
ShippedHow we are allowed to work.
Anti-patterns
ShippedDo not do this again.
Tasks
ShippedNot done yet.
As of a date
ShippedTrue then. Written then.
Where it came from
ShippedFile, commit, what replaced it.
Not enough to say
ShippedA typed gap, not a guess.
Edits supersede
ShippedHistory stays readable.
Pull from every tool
ShippedWrong note, gone everywhere.
Share by link
ShippedA week. No account.
Signed pack
ShippedLeave with the file.
Stale when the file moves
In developmentIn development.
Memory Packs
PlannedDesigned. Not built.
Team-shared memory
PlannedWaiting on the tenancy gate.
Illustrative example — not live data
The capability stack
Each rung depends on the one below it.
Memory is not a flat list of features. Facts are the foundation. Sources and revisions depend on facts. Staleness tracking depends on sources. Memory Packs are designed but not built — the top rungs are dashed outlines with nothing standing on them yet.
- 01FactsShipped
Observed and checkable. The foundation everything else builds on.
- 02SourcesShipped
Where a fact came from — file, commit, what replaced it.
- 03RevisionsShipped
Edits supersede. History stays readable.
- 04Review stateShipped
Every belief carries its review state. Nothing is confirmed that is not.
- 05Staleness trackingEvolving
A changed source marks its citations stale.
- 06Memory PacksPlanned
Designed. Not built.
The ladder shows what depends on what. Shipped rungs are solid. Planned rungs are dashed. The status is never inferred from the drawing — it is stated in words.
Truth, not volume.
Most memory products measure how much they store. We measure whether what they store is true. These are the metrics that matter, with their honest status.
Recall precision
AlwaysWhen a source exists, it is shown. When it does not, the system abstains.
Review state accuracy
AlwaysEvery belief carries its review state. Nothing is marked confirmed that is not.
Handoff integrity
Ed25519Every cross-tool handoff is signed. Corrupt a byte and it refuses.
Memory volume
Not measuredWe do not count how many memories you have. We measure whether they are true.
Recall latency
Not measuredSpeed is not the product. Truth is. When the evidence graph is slow, we fix that.
Why we do not measure volume: A memory product that stores a million wrong answers is worse than one that stores a hundred right ones. The number you want is not "how many" — it is "how true." That is what we measure.
Illustrative example — not live data
Start remembering, on the record.
Every decision you make has a source. Zephr keeps it — the claim, the file it rests on, the date, and the review state, all still attached.