4.6 KiB
Committed regional cellular census history v1
Authority: ADR-0151.
API: evo::persistence::load_cellular_census_history, Linux optional persistence
adapter. Census semantics remain regional projection v1.
This is not a new byte codec, SQL table, network protocol or world reconciliation.
Durable source and request
The immutable biological commit is the canonical history event. Its manifest and strong payload/trace bindings are retained in the existing append-only journal, in the same transaction that publishes the head. Atomic paired migration retains both endpoint cuts together. Orphan objects, prepared requests and staged ghosts do not create biological commit events. Exact publication retries retain the same commit identity rather than adding census events. No separate census write occurs.
A request supplies:
- exact regional key in the connected database and the evidence reader's lease;
- the exact upper regional
RegionHead: frame, sequence, commit ID, SHA-256 of its complete manifest, and completed tick; - inclusive first sequence and page limit 1–8;
- retained build allowlist and the existing per-I/O timeout.
The connection must be connected and transaction-idle at entry. Explicit writer and read-only transactions are refused. Otherwise a publisher could observe its own uncommitted cut and mislabel it durable. Transaction status inspection starts no transaction and takes no lock. Lower-level explicit historical recovery keeps the existing diagnostic caller-transaction semantics and does not itself certify external commit visibility.
First sequence above the watermark, invalid limits, mismatched lease/frame, zero regional identity and non-positive timeouts fail before reading. The exact upper cut is checked against the journal, with its manifest digest and identity, before and after the page. New head publication cannot move that fixed upper cut. A false or missing cut fails; it never silently selects the latest or nearest older head.
Replay and result
For each consecutive sequence, load its immutable manifest, select raw/profile-4 or exact population/profile-5 recovery, and run the same complete verification as current-head recovery: supported versions/build, manifest digest/identity, strong object bindings, canonical restore, retained trace/outcomes and complete biological replay. No-tick upgrades and profile conversions use their recorded operations; paired migration replays both candidates and checks the shared receipt and local counterpart capsules. Recheck the recovered record against the initially loaded cut before pairing it with a census. As with head recovery, replay covers the selected commit's complete tail/no-tick operation from retained predecessor checkpoints, not all ticks since genesis.
An entry contains the exact committed record and its detached census. No-tick
commits remain distinct even at equal completed ticks; sequence is the cursor.
next_sequence exists only if another sequence remains below the same fixed upper
cut. Reading/repeating a page changes no head, state, authority or event identity.
Historical recovery never selects an old checkpoint for a running host.
Any unavailable, corrupt, unsupported, unreplayable or foreign entry fails the entire page. Earlier valid entries in that attempt do not escape as a partial page. Missing payload, trace, counterpart capsule or build support is not a zero population, local absence or terminal extinction. Current lease requirements of the evidence loaders still apply, independently of the manifests' original writers. Read output is not a new grant of authority.
The existing unique regional sequence index bounds each metadata lookup. At most eight census projections are retained; biological restore/replay work runs one cut at a time. There is no page-wide latency/capacity promise or automatic retry. Queries use committed publication boundaries, not fabricated intermediate-tick population samples; organism/genome events remain retained in the full archive.
Coverage limits
This is a backend regional read primitive within the connected database's current frame/history context. Its regional watermark is not a world watermark, external branch identifier, complete region-set proof or client permission boundary. Cross-database/clone/rewind evidence must not be merged solely because numeric world/region/tick or an earlier shared prefix matches. Branch/world reconciliation, public queries, derived performance indexes/caches, client presentation and actual multi-day ecology remain subsequent gates. No terminal-extinction result exists.