Journal 3 Specification Reading Order
Journal 3 is split by semantic responsibility. For a first implementation pass, read:
incremental-graph-journal.md— conceptual model and global invariants.incremental-graph-journal-types.md— record identities, scopes, causality, authority.incremental-graph-journal-well-formedness.md— context/reference/certificate validity.incremental-graph-journal-replay.md— deterministic projection and effective proof.incremental-graph-journal-emission.md— ordinary graph transition emission.incremental-graph-journal-locking.md— finalization/atomic publication.incremental-graph-journal-api.md— snapshots, absent restoration sources, bootstrap/migration boundaries.incremental-graph-journal-sync.md— suffix replication, normalization, convergence.incremental-graph-journal-reset.md— controlled rebaseline.incremental-graph-journal-migrations.md— legacy bootstrap and Journal-aware migration.incremental-graph-journal-properties.md— algebra/lifecycle distinctions.incremental-graph-journal-theorems.md— proof obligations.incremental-graph-journal-examples.md— worked counterexamples.incremental-graph-journal-errors.md— failure categories.incremental-graph-journal-storage.md— local persistence/codec requirements.incremental-graph-journal-user-contract.md— observable expectations.incremental-graph-journal-testing.md— verification strategy.incremental-graph-journal-checklist.md— implementation acceptance checklist.
Surrounding lifecycle specs:
database-lifecycle.md— restore/open/bootstrap/migrate/sync/reset/rebuild lifecycle.
One-sentence model
Retained immutable Journal history is authority; the current IncrementalGraph database is project(Journal).
Normative ownership
Each semantic rule has one normative owner. Other Journal documents may summarize consequences, expose API/error behavior, state proof obligations, or define tests, but they do not redefine the owned rule. If wording drifts, the owner below wins.
- core Journal-authority/projection model and global conceptual invariants:
incremental-graph-journal.md; - record shapes, identity primitives, causal/authority data:
incremental-graph-journal-types.md; - well-formedness, context/reference legality, and record/basis validity:
incremental-graph-journal-well-formedness.md; - replay, certificate eligibility and selection, effective proof, freshness/validity projection:
incremental-graph-journal-replay.md; - ordinary-operation Journal emission:
incremental-graph-journal-emission.md; - publication finalization, atomic graph+Journal cutover, and locking ownership:
incremental-graph-journal-locking.md; - semantic API/snapshot/source boundaries:
incremental-graph-journal-api.md; - pairwise synchronization import, normalization, convergence, and the host-count settling construction:
incremental-graph-journal-sync.md; - lifecycle fault model, established-writer rollback boundary, and absent-installation restoration:
database-lifecycle.md; - shipped/pre-Journal migration API semantics:
migration.md; - pre-Journal bootstrap, including canonical-source decision and publication arbitration:
incremental-graph-journal-migrations.mdPart I (§§1–8), with §4 owning the arbitration procedure; - Journal-aware migration procedure:
incremental-graph-journal-migrations.mdPart II (§§9–22); - Journal format codec:
incremental-graph-journal-migrations.md§9a; - reset procedure:
incremental-graph-journal-reset.md; - local Journal persistence/codec requirements:
incremental-graph-journal-storage.md; - error categories and names:
incremental-graph-journal-errors.md, with trigger semantics owned by the relevant rule file above; - user-visible operation consequences:
incremental-graph-journal-user-contract.md, without redefining underlying algorithms; - regression/property inventory:
incremental-graph-journal-testing.md.
incremental-graph-journal-theorems.md states proof obligations derived from these definitions; incremental-graph-journal-properties.md explains algebraic consequences; incremental-graph-journal-examples.md supplies explanatory traces; and incremental-graph-journal-checklist.md is an implementation checklist. None of those files is a competing definition of an owned semantic rule.
Scope boundary
Journal 3 stops at semantic stable-snapshot/lifecycle boundaries. It does not prescribe Git branch/file mechanics, a hosted backend, SQL/HTTP/RPC schemas, authentication, or deployment topology.
A transport can remain unchanged if its adapter can provide the required stable ordinary snapshots, continuation-safe absent-installation restoration, and canonical-bootstrap source semantics. How absent-restoration safety is established is backend-specific; Journal 3 requires only the resulting guarantee and does not prescribe a single recovery authority, source count, storage topology, or publication protocol.
Also outside core correctness:
- destructive compaction (none required);
- persisted checkpoint format;
- high-level history UI/grouping;
- the future end-to-end change-sensitive synchronization running-time guarantee owned by #1607.