Eight ideas explain the architecture: memory is not authority, time has more than one axis, receipts are evidence rather than correctness, and acceleration must remain recoverable.
Memory preserves searchable state. Authority decides whether a claim may be trusted or an action may be taken. Combining those jobs turns retrieved text into accidental policy.
A system can know when a statement became true in the world and when it learned that statement. Bitemporal state keeps corrections, supersession, and historical queries honest.
A receipt records an execution path, selected backend, state view, degradations, retained inputs, and outcome. It makes an operation inspectable; it does not make the result true.
A bounded system distinguishes completion, interruption, rejection, degradation, and failure. Converting an error into a successful-looking state is false success.
FTS tables, vector indexes, quantized candidates, caches, and graph projections may improve retrieval. Each remains derived, reconcilable, and rebuildable from a canonical owner.
A codec has a wire format, profile digest, quality budget, resource limit, score semantics, and unsupported paths. It is not a marketing adjective.
A receipt can identify a past execution without containing enough material to reproduce it. Complete replay is opt-in because prompts, context, and retrieved content carry privacy and storage costs.
Recovery and trust become tractable when durable state, derived acceleration, execution evidence, context fallback, and claim authority do not compete.
| Artifact | Canonical owner | Recoverability | Claim boundary |
|---|---|---|---|
| Searchable memory | SQLite memory.db | WAL, integrity, FTS/vector reconciliation | Local store ≠ encrypted store |
| Vector acceleration | Derived index or candidate artifact | Rebuild or exact f32 fallback | Index ≠ source of truth |
| Search execution | Durable retrieval receipt | Replay only with retained inputs | Receipt ≠ factual truth |
| Compacted context | Context Governor receipt store | Exact expansion of fallback records | Recoverability ≠ task success |
| Claim trust | Verified claim-ledger history | Hash chain, snapshot, retained-tail verification | Trust ≠ action authority |
The Atlas maps these concepts to concrete packages. Activity shows what changed. Install turns one product path into a working local system.