[EPIC][CORE-B] Durable ledger + SAFIRE storage engine: append-only history, bitemporal views, frontiers, checkpoints, invalidation, and replay #36

New issue

Open

opened 2026-09-08 01:57:02 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-08 01:57:02 +00:00

Owner

Parent: #11
Refines: #6
Research: prolog-rlm#402 (BSLPF → GRIE → CLFM → SAFIRE)

Goal

Implement the durable storage/runtime substrate for semantic history at small-to-large scale.

Own:

append-only commits and idempotency;
immutable semantic/object storage;
valid-time + known-time coordinates;
current/history materialized views;
segmented storage backend(s);
monotonic per-ledger sequence/frontier;
checkpoints/manifests;
projection dependency generations;
incremental invalidation/rebuild;
crash recovery and deterministic replay classes;
integrity/fork detection hooks;
storage cursors/range indexes;
benchmarkable backend profiles.

Derived projections/caches remain disposable and cannot overwrite canonical history.

Hard invariants

commit durable before projection acknowledgement
current view != canonical ledger
same idempotency key + same digest -> same logical commit
same idempotency key + different digest -> conflict
wall clock != ledger order
corrupt projection -> rebuild
corrupt canonical ledger -> integrity failure, not cache promotion

Acceptance

Crash/failure injection proves all-or-none commits, restart replay, stale checkpoint rejection, cold==warm==rebuilt normalized results for the same frontier/generations, and no whole-history rewrite for ordinary append.

Parent: #11 Refines: #6 Research: prolog-rlm#402 (BSLPF → GRIE → CLFM → SAFIRE) ## Goal Implement the durable storage/runtime substrate for semantic history at small-to-large scale. Own: - append-only commits and idempotency; - immutable semantic/object storage; - valid-time + known-time coordinates; - current/history materialized views; - segmented storage backend(s); - monotonic per-ledger sequence/frontier; - checkpoints/manifests; - projection dependency generations; - incremental invalidation/rebuild; - crash recovery and deterministic replay classes; - integrity/fork detection hooks; - storage cursors/range indexes; - benchmarkable backend profiles. Derived projections/caches remain disposable and cannot overwrite canonical history. ## Hard invariants ```text commit durable before projection acknowledgement current view != canonical ledger same idempotency key + same digest -> same logical commit same idempotency key + different digest -> conflict wall clock != ledger order corrupt projection -> rebuild corrupt canonical ledger -> integrity failure, not cache promotion ``` ## Acceptance Crash/failure injection proves all-or-none commits, restart replay, stale checkpoint rejection, cold==warm==rebuilt normalized results for the same frontier/generations, and no whole-history rewrite for ordinary append.

nsaspy referenced this issue

2026-09-08 01:57:39 +00:00

[EPIC][CORE] Library-first Symbolic Memory v1: durable semantic world model, learning history, federation, and zero-model recall #38