[EPIC][CORE-F] Federation + integrity + redaction: CLFM ledger federation, replica profiles, anti-entropy, GRIE lifecycle, retention, and remote obligations #32

New issue

Open

opened 2026-09-08 01:57:02 +00:00 by nsaspy · 1 comment

nsaspy commented

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

Owner

Parent: #11
Research: prolog-rlm#402B/#402C/#402D

Goal

Implement multi-ledger durability and governance without pretending all memories share one clock, authority domain, trust domain, or retention policy.

Own:

independent ledger IDs and federation links;
exact sparse federation cuts/frontiers;
typed replica profiles: single-writer, consensus group, optimistic group, mirror/archive;
authenticated import/receipt lineage;
Merkle/range anti-entropy where appropriate;
fork/divergence detection;
remote availability/completeness states;
redaction/retention/archive/access-revocation lifecycle;
redaction obligations + attempt/ack/verification receipts;
integrity/checkpoint verification;
payload availability/replay capability classes;
federation-aware source dependence and non-corroboration of replicas.

Hard invariants

local commit order != cross-ledger causal order
replica != independent source
signed receipt != semantic truth
remote ACK != verified erasure
redaction != semantic retraction
payload erased != historical commitment erased
same principal name across ledgers != same authority

Acceptance

Partition/rejoin, mirror/replica, fork, remote-unavailable, redaction, and replay fixtures preserve exact status; anti-entropy does not duplicate evidence; a source ledger cannot falsely claim federation-wide deletion or global serializability.

Parent: #11 Research: prolog-rlm#402B/#402C/#402D ## Goal Implement multi-ledger durability and governance without pretending all memories share one clock, authority domain, trust domain, or retention policy. Own: - independent ledger IDs and federation links; - exact sparse federation cuts/frontiers; - typed replica profiles: single-writer, consensus group, optimistic group, mirror/archive; - authenticated import/receipt lineage; - Merkle/range anti-entropy where appropriate; - fork/divergence detection; - remote availability/completeness states; - redaction/retention/archive/access-revocation lifecycle; - redaction obligations + attempt/ack/verification receipts; - integrity/checkpoint verification; - payload availability/replay capability classes; - federation-aware source dependence and non-corroboration of replicas. ## Hard invariants ```text local commit order != cross-ledger causal order replica != independent source signed receipt != semantic truth remote ACK != verified erasure redaction != semantic retraction payload erased != historical commitment erased same principal name across ledgers != same authority ``` ## Acceptance Partition/rejoin, mirror/replica, fork, remote-unavailable, redaction, and replay fixtures preserve exact status; anti-entropy does not duplicate evidence; a source ledger cannot falsely claim federation-wide deletion or global serializability.

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

nsaspy commented

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

Author

Owner

Machine Spirit #405C / CONCORDAT federation hardening

CONCORDAT confirms this epic's premise and adds explicit domain contracts above CLFM ledger links.

Federation must preserve separate:

semantic/epistemic profiles
identity namespace
trust-root/verifier namespace
authority domain
provenance/privacy policy
retention/redaction policy

A CLFM ledger relationship alone does not imply semantic compatibility or trust. Cross-domain import requires a directional/versioned federation contract plus target-local appraisal. No ambient transitive trust, no merged trust bundles, no invented global order, and no replica amplification of evidence.

Suggested durable refs for imported records: source domain/ledger/object/frontier, contract version, mapping generations, source trust-root generation, target appraisal receipt, origin/dependence state, redaction obligations.

Canonical research + C14-C26/C37-C44: lost-rob0t/prolog-rlm#405C.

## Machine Spirit #405C / CONCORDAT federation hardening CONCORDAT confirms this epic's premise and adds explicit **domain contracts** above CLFM ledger links. Federation must preserve separate: ```text semantic/epistemic profiles identity namespace trust-root/verifier namespace authority domain provenance/privacy policy retention/redaction policy ``` A CLFM ledger relationship alone does not imply semantic compatibility or trust. Cross-domain import requires a directional/versioned federation contract plus target-local appraisal. No ambient transitive trust, no merged trust bundles, no invented global order, and no replica amplification of evidence. Suggested durable refs for imported records: source domain/ledger/object/frontier, contract version, mapping generations, source trust-root generation, target appraisal receipt, origin/dependence state, redaction obligations. Canonical research + C14-C26/C37-C44: lost-rob0t/prolog-rlm#405C.