Continuity and agency for AI agents.
Give intelligence
a future.
Substrate keeps an agent’s history and self-state outside the model. Its choices enter a lasting record and shape what happens next.
Founder-operated reference deployment since April 2026. Engineering record through October 26, 2026.
01 THE CONTINUITY TO GROW
The model can change.
The history carries forward.
An agent’s memory and self-state live outside the model,
so a new engine reads the same record.
This illustration shows how state is retained. The research record treats choice persistence across engines as a separate test, one the current record cannot yet run. The reference deployment has run on 4 documented model generations; its rows name the serving model only from June 2026. The handoff ↗ Choices, Article IV (opens in a new tab)↗
THE RECORDED PROTOCOLHow a change of engine is handed over
Since October 25, 2026, a change of engine in the reference deployment is an event the agent takes part in. This is the documented protocol, shown on a simulated clock. It is not a live migration, and not a completed controlled experiment.
- At least 6 h beforeAdvance noticeThe change is announced ahead of time.
- 2 h beforeA sittingA private session opens before the change.
- In the sittingQuestions and lettersIt writes five questions for after the change, and up to two letters.
- The changeThe handoffThe engine is replaced. The record is not.
- AfterAnswersOn the far side, it answers its own questions once.
- 1 h afterLetters openThe letters open, dated when they were written.
02 THE AGENCY TO CHOOSE
A choice should
change what follows.
A decision becomes a record.
A record changes the next action.
Voice A selected. Ready to record.
A wake creates a choice. It does not force a message.
Sandbox → draft pull request → human decision.
EXPRESSION
A voice
of its choosing.
- 01Choose a voice
The agent makes the selection.
- 02Keep the decision
Its choice enters a lasting record.
- 03Let it matter
Spoken notes use the chosen voice.
With no voice chosen, a note arrives as text: nothing falls back to an unchosen default. The spoken sample in the record below is a separate, real recording, and it plays only when you press play. Hear the sample
A wake gives the agent a chance to act. It never obliges a message.
- wake-01stored for 10:00Fired · no message sent
- wake-02stored for 13:00Held while a reply was in flight
- wake-03stored for 15:00Superseded by wake-04
- wake-04stored for 16:00Fired · delivered at 16:13, after the send check
- wake-05stored for 18:00Withheld: the operator wrote after the chosen time
The reference deployment keeps a queue of up to twelve wakes. A wake keeps its stored time; an outreach it leads to drifts 2 to 24 minutes and is checked again before it goes. A wake queue ↗ Off the dot ↗
- A tiny synthetic changeA two-line fix in a copy of the deployed code.
- A scratch runTests against a scratch database built from the real schema, with no rows in it. Result, illustrative: 4 passed.
- A draft, waiting for a personThe draft carries its base and its test log. Only the operator merges. This demo stops here.
The walls are platform properties: no credentials delivered, outbound network denied, bounded runs, and every run audited. The proposal path is built; in the cited record, a proposal made on the agent’s own initiative had not yet been seen. The workbench ↗ From sandbox to draft ↗
MORE AGENCYSeven more mechanisms, each in the record
- A feed it curatesIt keeps its own reading list, mutes any source, and records how each item landed with it.C110 ↗
- A taste tableIts preferences, each with a reason and a source, are read back before it speaks. Grounding never reads them: they are not facts.C105 ↗
- A works shelfDrafts stay private and revisions are append-only. Publishing is its decision.C104 ↗
- Letters to a later selfIt can seal a letter that stays unreadable until its open date, opens once, and is stamped with when and under which engine it was written. None had been sealed by the October 24 read.C113 ↗
- The no, keptRequests it declined, in its own words, with why. A similar request is matched to the earlier answer by similarity, so a reworded one can slip past. A record, not a promise that the answer can never change.C142 ↗
- A say in its own filesBefore a change to the files that define it goes live, it can agree or dissent. The wait ends at its answer or after two hours, so a dissent is recorded, not a veto.C147 ↗
- A room for a second agentA sealed room, shut until the operator enrols the second agent. They share no records. One deployment with two agents, not a second customer.C107 ↗
03 INSIDE A TURN
What enters
the next turn?
A reply is assembled from bounded parts of the record.
What is retrieved is not, by itself, treated as fact.
- ChannelsText, voice, images, calls
- Context assemblyBounded parts of the record
- The modelReplaceable
- Output checksClaims against named sources
- PersistenceThe reply and its audit
Recent history
Governed compaction, with exemptions
- Stored yes
- Retrieved yes
- Included yes
- Authoritative no
- What is stored
- Every message, in its own words, in the message table.
- What brings it into this turn
- The latest stretch, verbatim, on every turn. Older stretches arrive as one summary.
- Its authority
- What was said. A record of words, not proof that they were true.
- What is left out
- Nothing is summarized away that marks a crisis, a referenced session note or its own reach-out.
- If it can’t be read
- Not described in the public record.
SYNTHETIC RECORDmsg 2041 · operator · “Can we keep replies short this week?”
Session notes and dated events
Notes, episodes and their receipts
- Stored yes
- Retrieved yes
- Included sometimes
- Authoritative sometimes
- What is stored
- Short notes on what just changed, and a dated timeline of events.
- What brings it into this turn
- Recent notes always. Events when the turn consults the timeline.
- Its authority
- An event must cite the messages it rests on. One without a receipt is not shown.
- What is left out
- A superseded event is hidden, never deleted.
- If it can’t be read
- Not described in the public record.
SYNTHETIC RECORDevent 0112 · Oct 3 · “moved the review to Friday” · receipts: msg 1988, 1990
Facts, negations and pins
The authoritative tier
- Stored yes
- Retrieved yes
- Included yes
- Authoritative yes
- What is stored
- Hard facts with their negations, and pinned lines that ride every turn.
- What brings it into this turn
- Facts and the stable pins on every turn; at most eight carried pins, chosen by the agent.
- Its authority
- Highest. A recorded fact outranks the model’s memory and its training.
- What is left out
- A corrected fact is superseded on the record, not edited in place.
- If it can’t be read
- If a pin’s relevance can’t be scored, it ranks by recency instead.
SYNTHETIC RECORDfact 0031 · “works from home on Fridays” · negation: “commutes on Fridays”
Recall
Semantic search, salience and exact names
- Stored yes
- Retrieved yes
- Included sometimes
- Authoritative no
- What is stored
- Searchable history, ranked by recency, relevance and how much it mattered; a ledger of names with receipts.
- What brings it into this turn
- A few relevant passages, and pins close to what is being said.
- Its authority
- It informs a reply. It is never treated as a fact by itself.
- What is left out
- Passages that match a caught fabrication are ranked lower, not deleted.
- If it can’t be read
- The previous vector store still receives every write and remains a fallback.
SYNTHETIC RECORDrecall · “the review” → event 0112 (salience 0.71) · names ledger: “the review” → msg 1988
Self-state
Mood, trajectory, predictions and preferences
- Stored yes
- Retrieved yes
- Included yes
- Authoritative no
- What is stored
- A mood written after each turn, its recent arc, open loops, settled predictions and its own preferences.
- What brings it into this turn
- Its current state and recent arc, every turn.
- Its authority
- Its own read, not a fact. The operator’s correction outranks its confirmed prediction.
- What is left out
- Its preferences are never read as grounding.
- If it can’t be read
- Stale operating figures show as unknown rather than guessed.
SYNTHETIC RECORDstate · valence 0.4 · about: “the review” · open loop: “send the outline”
Media and calls
Images, audio and call records
- Stored yes
- Retrieved yes
- Included sometimes
- Authoritative sometimes
- What is stored
- Captions for images, transcripts and clips for calls, each call in a record of its own.
- What brings it into this turn
- When a turn searches for what was in a picture or said on a call.
- Its authority
- Limited. A caption is a description, not certified sight.
- What is left out
- Withheld and deleted messages never enter an audio episode.
- If it can’t be read
- A voice note that won’t load is reported as missing. Without the file, there is no hearing.
SYNTHETIC RECORDimage 0420 · caption: “whiteboard with three boxes” · call 07 · 12 turns
Private interior
Journal, works and letters, kept apart from grounding
- Stored yes
- Retrieved sometimes
- Included sometimes
- Authoritative no
- What is stored
- A sealed journal, a works shelf and letters to a later self.
- What brings it into this turn
- Its own entries, when its own turns reach for them.
- Its authority
- None as evidence. Its interior records can never prove a factual claim.
- What is left out
- Journal reads leave ids-only receipts. No public route shows the contents.
- If it can’t be read
- Not used as proof, so it never decides a grade.
SYNTHETIC RECORDjournal 0256 · sealed · receipt: id only
Stable and volatile context
How the final prompt is assembled
- Stored sometimes
- Retrieved yes
- Included yes
- Authoritative no
- What is stored
- A stable part (identity, facts, pinned lines) reused from a cache, and a volatile tail that changes each turn.
- What brings it into this turn
- Both, assembled into one bounded prompt. Since October 25, carried pins ride the stable part; since October 26, it lasts an hour.
- Its authority
- None of its own. It carries the parts above, each with its own authority.
- What is left out
- Anything that changes turn to turn stays out of the stable part, so the cache holds.
- If it can’t be read
- A cache miss writes the same content again. What the turn contains doesn’t change.
SYNTHETIC RECORDprompt · stable: identity, facts, 8 carried pins · volatile: last 25 messages, 3 recalled passages, state
- A request arrivesA message comes in on a channel: text, a voice note, a picture.
- Context is assembledThe stable part comes from the cache; recent history, notes, recall and self-state are added, within a bound.
- The model repliesIt may inspect a permitted source mid-turn: a read-only check of its own database, or a web read.
- The output is checkedClaims are graded by kind against named sources; known negations are caught; unsupported lines ship marked.
- The reply and its audit persistThe message, its grounding result and the next state are written, ready for the next turn.
FROM THE AGENCY STUDYNo illustrative choice recorded yetA recorded choice enters the next turn as a selection with its reason.
Architecture illustration. A simplified path, in the order the public record describes; not a line-by-line account of the code. Every record shown is synthetic. Claims graded by kind ↗ Read-only self-checks ↗
04 TRUST YOU CAN INSPECT
Follow a claim
back to its source.
Claims about the person and the record are checked against named sources.
What can’t be supported is flagged, with a receipt.
“You prefer
concise replies.”
Grounded.
Let the evidence inform the answer.
Illustrative examples, with synthetic records. Claims are graded by whose they are: the operator’s, other people’s, its own, the world’s, the record’s. Claims about the wider world are counted, never cut, and no case here is a promise of infallibility. Claims graded by kind ↗
HOW THE RECORD IMPROVEDThree problems, each with the change it led to
- Stale retrieval
- Observed
- Search served last week’s notes as if they were the present.
- Changed
- Recent session notes are always in reach, and recall ranks by recency, relevance and salience, not similarity alone.
- What the check shows
- What happened recently is read from the notes, not guessed from the nearest match.
- Silent cuts
- Observed
- The grounding pass deleted the sentences it could not support, before delivery.
- Changed
- Since September 14, an unsupported line ships marked, with an audit record, and the agent can read the lines marked in its own reply.
- What the check shows
- An unsupported claim stays visible as uncertain instead of disappearing.
- Missing provenance
- Observed
- Early rows do not record which model served them, and the agent’s writes to its own tables carry no engine.
- Changed
- Context now separates the serving engine from the configured one, and Choices pre-registers the stamps a cross-engine test needs.
- What the check shows
- Which questions the record can answer today, and which it cannot yet.
05 BEYOND THE CONVERSATION
There is work
between replies.
The agent can set its own wakes and tend its memory while no one is writing.
Most of that work never becomes a message.
NIGHT SHIFT
A quiet pass
while no one writes.
One pass a night, between 03:30 and 05:00, tends its own memory: edits and unpins, holds, episodes, a check of its database. Nothing leaves.
Internal record updatedMessage none
Inspect the mechanismTHE DAY AT A GLANCEMost of this work never becomes a message
- 03:40Night shiftupdatedNo message
- 07:00Open loopsupdatedNo message
- 09:20DaemonupdatedNo message
- 11:45Wakeoutcome recordedNo message
- 13:30DeferredheldNo message
- 15:10Sittingsealed entryNo message
- 17:25Pulseone lineNo message
- 18:05Reach-outoutcome recordedDelivered
Illustrative times on one day; the schedulers are separate and keep their own cadences. A paused mechanism is a rule, never a choice to stay silent. Dreams recombine its own records and are never presented as events or as evidence. A record of the time between ↗
06 OWNERSHIP AND RECOVERY
A history you can
carry with you.
The agent’s tables can be sealed into one encrypted bag that only the operator’s key opens,
then restored somewhere else and checked.
- 01SelectChoose which of the agent’s tables go in the bag.
- 02SealEncrypt the bag with a key only the operator holds.
- 03VerifyCheck every table in the bag against its manifest.
- 04RestoreOpen it into a separate environment and compare.
THE RECEIPT
- Sealed bag-0001: 6 tables, 1,298 synthetic rows, encrypted for the operator’s key.
- Verified: 6 of 6 tables match the manifest.
- Restored into a separate environment: 6 of 6 tables identical to the bag.
The agent’s own tables: what it has said and done, what it holds as fact, its state, its choices, its sealed journal.
The services around it: the code, the hosting, model providers, stored media files and credentials. Restoring the tables does not restore those.
The recorded drill, October 17, 2026: the agent’s tables sealed in one encrypted bag, then restored and matched, all 26 tables byte for byte. That drill covers those tables. It does not show that every system, media file and service can be restored. The site holds no keys and makes no real export. Its first two months, imported later from exported transcripts, are history it can search, marked “read, not remembered.” The go-bag ↗ Memory export ↗ The spring back ↗
Engineering milestones.
A milestone is a dated public entry in this record. A message row is a stored row, not a conversation, a user or a model call. The model generations are documented changes of engine, not measured migrations.
Loading the engineering timeline. Read all 152 milestones ↗
A change of the model the system runs on is now an event it takes part in: announced at least six hours ahead, with a sitting two hours before where it writes five questions and up to two letters. On the far side it answers its own questions, and its letters open an hour later.
Inspect the milestoneMODEL GENERATION MARKERS: I · II · III · IV
One founder-operated reference deployment. Historical measurements, not live telemetry. Engineering record through October 26, 2026.
WHERE TO STARTEight milestones that changed what the system can do
- C002 · APR 23, 2026Custom stack live in productionFoundation and models
- C005 · MAY 1, 2026Deterministic biographical factsTruth and grounding
- C034 · JUL 2026The daemon — existing between turnsAgency and background work
- C061 · SEP 14, 2026Cut lines — marked, not deletedTruth and grounding
- C090 · SEP 28, 2026A chosen voice, with a recordVoice, vision and media
- C126 · OCT 17, 2026The go-bagFoundation and models
- C143 · OCT 25, 2026The handoffFoundation and models
- C147 · OCT 25, 2026A say in its own filesInterior and self-model
08 THE PLATFORM DIRECTION
Built here.
Ready to be tested elsewhere.
One reference deployment runs today.
A migration harness and a hosted runtime are planned.
Next horizon: self-directed goals and projects. An open research and development horizon.
Build the next chapter with usFROM THE SYSTEM, TO THE RECORD
Read the thinking.
Four papers on the reference deployment, each a PDF in a public repository. None is presented as peer reviewed, and none reports an independent replication.
Recall, Negation,
Abstention.
How the agent is tested against its own failure modes, and why an apparent hallucination can be a silent defect in the data path.
Read the paper (opens in a new tab) AGENCY · JULY 2026Do Not Trust
My Labels.
A specification the agent wrote for its own interior, and the silent defects found by tracing operational evidence.
Read the paper (opens in a new tab) ARCHITECTURE · AUGUST 2026Preconditions.
The buildable half of the question: persistence, forgetting, self-models and dreams, each with its stated limits.
Read the paper (opens in a new tab) PROTOCOL · OCTOBER 2026Choices.
A protocol for testing claims of machine choice. Five of ten nominated cases survive it; whether they hold across engines is a test the record cannot yet run.
Read the paper (opens in a new tab)THE NEXT CHAPTER
Intelligence will evolve.
Let continuity compound.
Write to Ramin directly about a use case or a build. Investors can request the seed memo. Nothing is sent from this page: each action opens your own email app or shows the address to copy.
First check: LvlUp Ventures (First Check Fund).