Expand description
Domain-free atomic journal behavior over content-addressed objects.
A journal publishes immutable objects before making entries visible and
advances its head through one fenced compare-and-swap transition. Backends
implement JournalBackend::admit; callers use Journal so the gapless,
closure, redelivery, and replay laws are enforced once.
Structs§
- Admission
- One atomic admission request. Implementations publish immutable objects and compare the head/fence in the same linearized operation.
- Backend
Capabilities - Evidence supplied by the concrete Table/Dir binding at construction.
- DirProjection
- Read-only Dir-shaped snapshot grouped by journal/object namespaces.
- Entry
Location - Exact physical locator for a committed v2 entry leaf.
- Entry
Namespace - Backend-allocated routing token for one v2 entry namespace.
- Host
DirJournal Backend - Crash-durable journal composition over the canonical host-backed Table/Dir port.
- Journal
- The single state-machine implementation shared by every backend.
- Journal
Entry - One immutable journal fact whose identity is the canonical semantic Datum.
- Journal
Head - The sole authoritative append position.
- Journal
Object - Immutable semantic value and its convenient payload-byte projection.
- Lease
- A writer generation. Only the backend can mint a live fence.
- Memory
Backend - Deterministic law-reference backend. It is deliberately not durable.
- Native
State Envelope - The one physical state selected by the native state CAS.
- Persistent
Object Store - Persistent semantic object facet backed by an existing journal backend.
- Replay
- Stored
Datum Ref - A verified crossing from semantic Datum identity to physical byte identity.
- Stored
State - A consistent backend snapshot used for verification and replay.
- Table
Projection - Read-only flat Table-shaped snapshot. It exposes no mutation method and is never consulted by journal authority.
- Verification
- Verified
Native Prefix Ref - Durable proof reference for the immutable v1 committed prefix.
Enums§
- Failpoint
- Stable crash-injection boundaries in upgrade and append publication.
- Journal
Error - Native
Format Id - Native physical state version. It never enters a semantic entry identity.
- Projection
Row - Detached row in a read-only projection.
- Store
Error - Failure of the owned-return persistent semantic object facet.
Traits§
- Journal
Backend - Object-safe storage seam. A Table backend implements
admitwith canonicaltable/cas; it must refuse writes unless CAS and durability are provable. - Persistent
Semantic Objects - Owned-return persistent Datum operations over the journal object backend.