Skip to content
Documentation/Core concepts

Record lifecycle

Read Committed, Verified, Anchored, and integrity states correctly.

On this page

Four independent axes

AxisMeaning
Pending → CommittedConfirm the record, create a seal, and append the log.
Pending / Queued / Verifying / Verified / FailedProgress and outcome of the verification request.
OffChain → AnchoredThe complete finalized receipt and events have been matched.
Ok → BrokenMonitoring has found contradictory evidence.

Wait for finality

Submitting a transaction does not make a record Anchored. A successful receipt and matching events at a finalized block are required.

After anchoring, the system verifies again with chain evidence. The earlier off-chain result and the on-chain result are distinct steps.

Infrastructure errors and invalid evidence

An unavailable RPC, storage dependency, or trust configuration is not invalid evidence. The request remains Queued with an infrastructure code for recovery.

When automatic retries are exhausted, the interface indicates that retries stopped. Once the dependency recovers, re-verification creates a new request. Actual cryptographic contradictions produce Failed.

Sources reviewed in the monorepo

Based on source code; live availability is stated separately.

  • apps/api/src/modules/shadow-ledger/domain/record-verification-state.ts
  • apps/api/src/modules/shadow-ledger/domain/record-anchor-state.ts
  • docs/adr/ADR-0036-verification-retry-exhaustion.md