Add incremental retained-session persistence

This commit is contained in:
Meta Vens 2026-07-15 08:27:19 +01:00
commit e32f3c5187
7 changed files with 326 additions and 20 deletions

View file

@ -56,13 +56,16 @@ step, and disposal operations. It emits revisioned receipts and typed
Begin/Hit/End facts with stable Ymir identities. Ordinary retained steps do not
accept complete body snapshots.
The embedded retained-session library now has a replay-backed reconstruction
checkpoint and durable-in-checkpoint command receipt ledger. Host-owned private
incremental journal storage and atomic frame/resume commits remain integration
work. Complete replay history is not product state and must not ride in public
client frames. The current CLI still has no named session registry or CultMesh
command lowerings; its CultCache and Eve output remains a regenerated
diagnostic projection.
The embedded retained-session library has replay-backed reconstruction,
durable command receipts, incremental journal-suffix capture, and bounded
resume descriptors. Aetheria stores these in a second daemon-private CultCache:
immutable chunks are flushed first, immutable per-frame resumes second, and the
public Aetheria frame last. The public frame is the only commit marker. Orphaned
private records cannot advance gameplay truth, and restart fails closed once
the persistence capability has been activated. Complete replay history is not
product state and never rides in public client frames. The current CLI still
has no named session registry or CultMesh command lowerings; its CultCache and
Eve output remains a regenerated diagnostic projection.
## Target Inputs

View file

@ -101,6 +101,20 @@ world verifier, and active episodes. ABI v5 independently validates the exact
pinned native build id before opening a session. It contains no native Box3D
handle or contact key.
For incremental host persistence,
`gamecult.ymir.session_journal_chunk.v1` carries a contiguous command-journal
suffix and `gamecult.ymir.session_resume.v1` carries the bounded reconstruction
boundary. `CapturePersistence(persistedJournalEntryCount)` never repeats an
already acknowledged prefix. Restore orders chunks by their first entry,
requires exact coverage from zero through the descriptor count, and then uses
the same full replay and verifier path as a complete checkpoint. Both binary
forms are independently checksummed.
The cursor is currently an index into a complete in-memory journal. Ymir does
not yet prune or renumber that journal; storage writes are incremental, memory
retention is not. Compaction requires a generation/base-sequence contract and
must not be inferred from a host acknowledging a write.
## Forbidden Writers
- recurring complete-body synchronization after restore;
@ -146,8 +160,9 @@ is derived process state: it never appears in a public fact or checkpoint.
3. Revision-checked retained-session overlap and cast queries: done.
4. One embedded retained world and physical-payload session per Aetheria run
and zone: done.
5. Persist replay journals privately and incrementally behind a bounded resume
descriptor; complete history must not ride in public product frames.
5. Incremental journal chunks and bounded resume descriptors: done. Aetheria
stores them in a daemon-private CultCache; complete history does not ride in
public product frames. Journal compaction remains separate work.
6. For optional standalone hosting, add a session registry, generation-bearing
routed commands, idempotent Create, durable receipts, and CultMesh lowering.