Scope comes first.
The authenticated backend determines the tenant. A browser or agent request does not get to select another customer’s evidence by supplying a different identifier.
ARCHITECTURE
A chain of context.
A history you can follow.
Follow evidence from its authenticated entry point to retained state, retrieval and review.
SYSTEM BOUNDARY
Authenticated contextIdentity & workspace scope
Evidence captureSource, context & configuration
Append-only coreWAL · BLAKE3 · receipt lineage
RetrievalEvidence & relationships
ReviewReplay & structured exports
Preserve the event.
The append-only log retains memory events. Cryptographic references connect recorded frames and their predecessors so historical changes can be checked.
Recover what existed.
Retrieval returns traceable evidence. Replay reconstructs retained memory state. Background maintenance supports these operations without becoming a new source of invented evidence.
THE RECORD CONTRACT
Four references. One reviewable event.
01
Source
The material captured as evidence. Its origin matters independently of its integrity.
02
Context
The retrieved material and configuration available at the recorded moment.
03
Policy
The policy reference associated with the outcome being reviewed.
04
Receipt
The references used to inspect the recorded event and its lineage.
Deterministic does not mean infallible.
Hash-linked storage, tenant boundaries and deterministic replay address specific problems. They do not eliminate hardware failures, invalid input, scheduling bugs or the need for backups and recovery procedures.
Operational guarantees must be demonstrated for the deployed system. An architecture diagram is not that demonstration.
Inspect the trust boundariesYOUR NEXT DECISION
Follow the chain.
See where it holds.
The diagram is a map, not the territory. Trace a sample record and follow its references.