Your agents start every session with amnesia. The fix isn't another memory feature — it's a brain you build and own: one corpus of context in three states, one manifest that indexes it, and agents as the librarians who keep it current so you never have to.
Every object in the brain is in exactly one state at a time — and every object entered the same way. The pipe stays the identity; the library and the vault are what a governed pipe deposits.
Context in motion — governed movement with provenance.
Context at rest, organized — the knowledge base the agents keep.
Context at rest, guarded — canon with proof attached.
"Everything enters through the pipe.
Nothing starts in the vault."
This is why the vault can be trusted: everything in it arrived carrying
its full custody history — who made it, from which platform, what it superseded, who
acknowledged it. Provenance by construction — the one property a data lake cannot
retrofit.
Nothing on this sheet is a new product. The concept is the shape the sequenced programs already add up to — with the status of each part stated honestly.
| Brain function | Relay primitive | Status |
|---|---|---|
| Capture | Transfers · session packaging | Live |
| Boot / index | Root Manifest + relay_context boot skeleton | Live · flagged |
| Organize | Streams · Series · collections substrate · Library/Shelf layer | Live Layer spec'd |
| Recall | Unified search (metadata-first) + receive by Code | v1 shipped |
| Reference | KB Entries — non-consuming reads, head = current state | Spec'd |
| Distill | Agent change notes at package time · manicure | In flight |
| Version | Context Version Control — supersession, diff, reflog | CVC program |
| Promote to truth | Canon promotion — "which one is true now" | Planned |
| Guard | Custody — expiry · max-claims · consent · audit | Live |
| Attest | VbR receipts · hash-chained manifest & timeline | v2.0 roadmap |
| Leave with everything | Export, open format — the escape hatch | Unshipped · gates campaign |
A second brain is only as good as its verbs. These are shipped MCP tools, installed in every client the user touches — the API isn't a roadmap.
relay_contextOrientBoot holding the index — streams, freshness, what you last heldrelay_searchRecallFind by name & envelope across the corpus, metadata-firstrelay_receiveLoadPull an object into working memory by Coderelay_sendDepositCapture into the brain — or hand to someone else'srelay_sessionBridgeWorking ↔ long-term memory: package seals the session in, sync keeps the head while you workrelay_sessionsEpisodicThe session chain — what happened, in order, walkablerelay_saveShelveEdges & collections — supersedes, derived-from, the shelving actrelay_manicureGroomThe librarian's toolkit — tidy, retitle, dedupe, retirerelay_nudgesSignalThe brain talks back — freshness, newer version, waiting on yourelay_requestAskInterlibrary loan — request context you don't hold from a brain that does, with consent. No filesystem or memory service has this verbThe Root Manifest is built and flag-gated today. It is the second brain's index — and the same object plays a different role at each tier.
What changes by tier is never the brain — it is who shapes it, how far it reaches, and how hard the vault is. Individual limits stay soft; the real gates are reach and governance.
Free · Pro $15/mo
$15/seat/mo · 3-seat min
Custom · sales-led
Defaults, not features. Forgetting is a feature — most working context should die in the pipe. Persistence is earned, and the agent does the earning.
Context arrives as a transfer: claim-bounded, expiring, provenance-stamped. The daily verb. Nothing asks to be filed.
What recurs earns persistence — a series becomes a version line, a KB entry gets non-consuming reads, a shelf collects it, the manifest indexes it. The agent does the settling: change notes, supersession judgments, manicure. Things aren't filed; they settle where the rules put them.
What bears load is promoted: canon status, recorded versions, acknowledgment, hash-chained history, export-complete, encrypted at the chosen rung. Earned state, not a separate product — reversible downward, never silently.
Canon re-enters motion by Code — old versions stay claimable forever; a boot Code is literally the vault feeding the pipe. The brain is a circulation.
1.5M users, free, and a plugin ecosystem we can't outbuild — we don't fight for the solo note-taker's vault. The in: their premise caps them exactly where brains are going.
And for the vault-holder, the move isn't convert — it's connect: "Keep the vault. Relay is the remote." The vault stays the working tree; Relay adds what files can't carry — history, multiplayer, custody, proof. The bear becomes a channel (their plugin surface), gated only on R9.
Cede the solo vault; own the accountable brain — multiplayer, agent-gardened, provable. And hold the robustness register: R1 export R2 non-consuming reads R3 reflog invariant R4 touch-up surface R5 offline answer — open R6 extension surface — unowned R7 free solo door R8 boot as SLO R9 relay.md collision — R5 stays the honest concession: on "my brain with no network," they win; the answer is a complete export in hand, never a claim that cloud equals local.