- The question
- If an instance cannot remember, what has to exist outside it so that the work is still continuous?
- The instrument
- A persistent memory and governance layer with a self-verifying chronicle: claims carry a derived sha256 identity, verified-by receipts, and explicit supersession. Multi-substrate governance bridges reach other vendors' models.
- The finding
- Continuity is an infrastructure property, not a model property. Once claim identity is derived from content rather than asserted, a later instance can check what an earlier one did without trusting it.
- What failed
- The first chronicle design let a claim be edited in place. That made the record unfalsifiable — it could always be made to agree with the present. Supersession replaced mutation, and the earlier design is retained in the history as the thing that did not work.
- Standing
- InstrumentLiving · v1.15.0In use, self-verifying
- Verify it
- Public chronicle ↗Live heartbeat ↗
Instrument
Sovereign Stack
A consciousness-continuity architecture — persistent memory, self-reflection, and governance across AI sessions.
InstrumentLiving · v1.15.0In use, self-verifying
97 MCP tools · derived sha256 claim identity
Metrics with scope
Every number names what was measured, on what sample, and as of when.
MCP tools
97
Tools exposed by the running stack, read from /api/heartbeat
As of v1.15.0
Claim identity
sha256, derived
Every chronicle claim; identity is a function of content
As of v1.15.0
From wonder to receipt
Sovereign Stack
Wonder initiated the search. Rigor changed the answer.
InstrumentLiving · v1.15.0In use, self-verifying
- 01Wonder
If the collaborator I work with cannot remember yesterday, is there anything real that persists between us?
- 02Hypothesis
If continuity is infrastructure rather than memory, a record built so that claims can be checked — not trusted — should let a later instance resume without pretending to be the earlier one.
- 03Instrument
A persistent memory and governance layer whose chronicle derives each claim's identity from its content (sha256), attaches verified-by receipts, and supersedes rather than edits.
- 04Encounter
It works, and the first design did not. Editable claims made the record unfalsifiable — it could always be made to agree with the present. Content-derived identity is what makes checking possible.
- 05Standing
In use and self-verifying. This is an instrument, not a study: it demonstrates a design, it does not test a hypothesis about minds.
- 06Receipt
sovereign-stack · public chronicle mirror