CRDT Syncconcept
CRDT (Conflict-Free Replicated Data Type) sync replicates compiled memory across a user's own devices with a state-based merge that is commutative, associative, and idempotent — so two devices converge with no server.
Sovereign memory must replicate without a cloud. CRDTs guarantee convergence under arbitrary exchange order, and Remove-Wins semantics mean a delete tombstones content everywhere.
Where it appears
- sovereign-knowledge-compiler sync/ package
- Explained by SKCE as a concept with a distributed-systems foundation
Descend
Prerequisites
Dependencies
- —
Foundations
Historical evolution
Based on Shapiro et al., 'Conflict-Free Replicated Data Types' (INRIA, 2011). SKCE implements a Remove-Wins Set + Lamport-ordered LWW with a human-overridable conflict ledger.
Implementation details
sync/crdt.py: FactSet (Remove-Wins), LamportClock (causal LWW), VersionVector. Deletion tombstones a SHA-256 content hash so it disappears from every replica after merge.
Sources
- [src/sovereign_knowledge_compiler/sync/crdt.py] src/sovereign_knowledge_compiler/sync/crdt.py
- [2026-07-15-sovereign-memory-bank-deepening-local-first-cognitive-memory] 2026-07-15-sovereign-memory-bank-deepening-local-first-cognitive-memory
- [src/sovereign_knowledge_compiler/sync/crdt.py] src/sovereign_knowledge_compiler/sync/crdt.py
- [2026-07-15-sovereign-memory-bank-deepening-local-first-cognitive-memory] 2026-07-15-sovereign-memory-bank-deepening-local-first-cognitive-memory