Ledger and Sequencing
Ledger and Sequencing
Document ledger and sequencing concepts where implementation evidence establishes them.
Status: Partial implementation reference — Code-confirmed; operational validation pending
Last reviewed: 2026-10-19
Scope
Representations, ordering, allocation, consistency, gaps and recovery where applicable. The source-confirmed baseline below covers part of this scope; remaining operational details are unknown.
Current implementation baseline
Corpus changes.sequence orders message creation, relationship assertion and relationship retraction events. Conversation created_sequence refers to its root creation event. Positions are safe-integer cursors in public query contracts, not message counts or timestamps; unused positions are valid.
Canonical synchronization uses exclusive after, inclusive fixed at, and X-Corpus-Next / X-Corpus-Has-More. Conversation collections instead use X-Next-Cursor. Relevance search uses offset continuation, even when sequence bounds filter results.
Evidence: change rows, synchronization handler and pagination contracts. Corpus/history identity must remain consistent throughout a replication run; see continuity guidance.
