[SLICE 23][CORE-B/F] Implement backup/restore, integrity verification, checkpoint export/import, and disaster-recovery lineage #8

New issue

Open

opened 2026-09-08 01:56:59 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-08 01:56:59 +00:00

Owner

Parent epics: #13 #17
Depends on: #37 #39

Goal

Add explicit administrative durability for recovering a Symbolic Memory ledger without turning backups into hidden alternate truth.

Implement:

consistent backup/export at an exact ledger frontier/checkpoint;
manifest containing schema/backend/projection/redaction/integrity generations;
restore into a new/empty store with stable ledger identity policy;
authenticated recovery lineage when repairing canonical corruption;
integrity scan/checksum verification and structured corrupt/unavailable ranges;
distinction among backup, replica, archive, and federation member;
retention policy hooks so erased/redacted payload is not unintentionally resurrected from ordinary backup workflows;
dry-run/verify-only restore mode.

Acceptance

Backup at frontier F restores canonical history and rebuildable projections deterministically; corrupt backup fails closed; restored archive is not counted as an independent source; recovery lineage is explicit; redacted payload cannot silently reappear from a backup that policy says must honor the redaction generation.

Parent epics: #13 #17 Depends on: #37 #39 ## Goal Add explicit administrative durability for recovering a Symbolic Memory ledger without turning backups into hidden alternate truth. Implement: - consistent backup/export at an exact ledger frontier/checkpoint; - manifest containing schema/backend/projection/redaction/integrity generations; - restore into a new/empty store with stable ledger identity policy; - authenticated recovery lineage when repairing canonical corruption; - integrity scan/checksum verification and structured corrupt/unavailable ranges; - distinction among backup, replica, archive, and federation member; - retention policy hooks so erased/redacted payload is not unintentionally resurrected from ordinary backup workflows; - dry-run/verify-only restore mode. ## Acceptance Backup at frontier F restores canonical history and rebuildable projections deterministically; corrupt backup fails closed; restored archive is not counted as an independent source; recovery lineage is explicit; redacted payload cannot silently reappear from a backup that policy says must honor the redaction generation.

nsaspy referenced this issue

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

[SLICE 14][CORE-D] Add deterministic structured-source adapters for LLM logs, issue/PR streams, Org/Markdown, JSONL, web results, and traces #17

nsaspy referenced this issue

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

[SLICE 13][CORE-D] Implement resumable corpus/backfill engine with stable work IDs, checkpoints, cancellation, and idempotent resume #18

nsaspy referenced this issue

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

[EPIC][CORE-D] Semantic projection + corpus ingestion: compiler adapter, projection generations, structured adapters, resumable backfill, and artifact lineage #34

nsaspy referenced this issue

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

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