Incremental Graph Synchronization
This document is retired as a specification. Journal synchronization has one canonical normative owner:
incremental-graph-journal-sync.md— suffix replication, normalization, convergence, and the host-count settling construction.
That ownership is declared by the Journal 3 reading order
(incremental-graph-journal-README.md, §Normative ownership: "Each semantic
rule has one normative owner").
This file previously restated the same synchronization contract in parallel.
Two competing full specifications violated the one-owner rule above and the
documentation-cutover requirement in
incremental-graph-journal-checklist.md §16a ("There must be one obvious
canonical shipped specification for synchronization"). The file is retained
only as a pointer so existing references resolve; it is not a competing
definition of any synchronization rule. This discharges §16a's instruction to
replace or rewrite incremental-graph-synchronization.md so the canonical
synchronization specification describes shipped Journal 3 behavior: the owner
above now carries that contract, and this file is only a redirect to it.
The obligations that appeared only in the retired text — "Synchronization MUST
NOT invoke computors" and the scope/non-goals statements — are restated in
incremental-graph-journal-sync.md §Scope and non-goals. The bounded-memory
iteration contract remains owned by $id-4924739474925738.
The retired text also specified a legacy pairwise materialization merge. Journal
3 synchronization replaces that mechanism with immutable foreign-suffix import
plus deterministic replay, so those merge-domain requirements are superseded
rather than silently dropped. The canonical owner
incremental-graph-journal-sync.md states the live rules.
Superseded by Journal 3 replay and identity semantics:
REQ-SYNC-01(value origin from copy, not deep equality): the old copy-origin comparison is replaced by immutable Journal record identity (ValueId) and writer-overlap validation. Equality of two payloads, timestamps, or materialized identifiers never establishes provenance. Owned byincremental-graph-journal-well-formedness.md§Record identity andincremental-graph-journal-replay.md§Semantic value/absence head.REQ-SYNC-07,REQ-SYNC-08,REQ-SYNC-08a,REQ-SYNC-08b,REQ-SYNC-08c(timestamp-based candidate selection and merge-time freshness): Journal 3 selects values by replay andValueId, not by the(modifiedAt, NodeIdentifier, sourceFingerprint)tuple, and authors no merge timestamp. The same-coordinate stale-freshness rule is vacuous because identifiers embed the host fingerprint and the immutable-overlap law forbids writer forks.REQ-SYNC-08d(selected record timestamp copy): Journal 3 carries the exactcreatedAt/modifiedAtinstant of the selectedValueEventthrough deterministic replay; it never substitutes merge-execution time nor combines timestamps across sources. Owned byincremental-graph-journal-replay.md§timestamps.REQ-SYNC-09,REQ-SYNC-10(distinct-input classifier; structural deletion closure): owned byincremental-graph-journal-sync.md§Phase 1: dependency-closure removal.REQ-SYNC-11,REQ-SYNC-12,REQ-SYNC-13(final identifier selection; meaning ofpotentially-outdated; equality does not create origin): Journal 3 identity and freshness are owned byincremental-graph-journal-replay.md.REQ-SYNC-14,REQ-SYNC-15,REQ-SYNC-16,REQ-SYNC-17(validity-proof transport): Journal 3 rebuilds proofs by replay; there is no source-side proof transport. Owned byincremental-graph-journal-replay.md.DEF-SYNC-02(source-version identity): replaced byValueIdidentity and the immutable-overlap law; equal timestamps, identifiers, or stored values are no longer identity evidence.REQ-SYNC-23,REQ-SYNC-27(pairwise commutativity; no multi-host order-independence guarantee): superseded by the convergence and host-count bounded settling construction. Journal 3 states eventual convergence of every fair execution plus an achievable2(H-1)state-advancing settling schedule rather than pairwise merge commutativity over merge-domain artifacts (selected identifiers, lowered inputs, reverse dependencies) which no longer exist. Owned byincremental-graph-journal-sync.md§Convergence and termination.
Still applicable, with their equivalent owner:
REQ-SYNC-02(normal synchronization pipeline): obtaining a stable compatible source snapshot, sequential per-source processing, failure isolation, and publication from inactive staging remain required. The old transport-specific checkpoint/fetch and per-host materialized graph merge steps are not the core Journal algorithm: pairwiseSyncimports committed immutable foreign Journal suffixes, validates them, replays the result and atomically publishes the new pair. Owned byincremental-graph-journal-sync.md§Scope and non-goals, §Snapshot compatibility cut, §Atomic publication and §Multi-source execution; transport-specific Git mechanics are outside that normative core.REQ-SYNC-03(reset mode separation): controlled reset remains a distinct operation, not a normal synchronization merge. Its old wholesale graph-state replacement semantics are retired: Journal reset rebaselines the projection while retaining the receiver's observed immutable Journal history and preserving its local writer identity. Owned byincremental-graph-journal-reset.md§Preconditions, §§Pass 1–3 anddatabase-lifecycle.md§10.REQ-SYNC-04,REQ-SYNC-05(source and final consistency): a source whose retained records are inconsistent with its projection is rejected rather than silently dropped. Owned byincremental-graph-journal-well-formedness.mdandincremental-graph-journal-sync.md§Final replay and validation.REQ-SYNC-06(malformed-metadata rejection): malformed immutable context and duplicate/conflicting records are rejected rather than silently dropped. Owned byincremental-graph-journal-well-formedness.mdandincremental-graph-journal-sync.md§Imported causal closure and §Final replay and validation.REQ-SYNC-11a(up-to-date eligibility): theselfProofReady(K) => fresh(K)gate inincremental-graph-journal-sync.md§Final replay and validation.REQ-SYNC-18,REQ-SYNC-19(pre-switch validation; fail-closed on failure):incremental-graph-journal-sync.md§Final replay and validation and §Atomic publication.REQ-SYNC-20,REQ-SYNC-22(write-target isolation; partial-failure safety):incremental-graph-journal-sync.md§Atomic publication, which streams into inactive staging and leaves the previous active pair selected on failure.REQ-SYNC-21(switch condition): a successful synchronization publishes the final pair atomically and is a semantic no-op when nothing changed.incremental-graph-journal-sync.md§Atomic publication and §Pairwise result law.REQ-SYNC-24,REQ-SYNC-26(sequential per-host merge; host failure isolation): the outer procedure may process multiple sources sequentially and successful earlier sources commit even if a later source fails. Owned byincremental-graph-journal-sync.md§Multi-source execution anddatabase-lifecycle.md§9Failure handling.REQ-SYNC-25(per-host validation after success): each pairwiseSyncperforms final replay and validation with atomic publication before the next source proceeds. Owned byincremental-graph-journal-sync.md§Final replay and validation, §Atomic publication, and §Multi-source execution.
See incremental-graph-journal-README.md for the Journal 3 reading order.