Record lifecycle
Read Committed, Verified, Anchored, and integrity states correctly.
Four independent axes
| Axis | Meaning |
|---|---|
| Pending → Committed | Confirm the record, create a seal, and append the log. |
| Pending / Queued / Verifying / Verified / Failed | Progress and outcome of the verification request. |
| OffChain → Anchored | The complete finalized receipt and events have been matched. |
| Ok → Broken | Monitoring 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.tsapps/api/src/modules/shadow-ledger/domain/record-anchor-state.tsdocs/adr/ADR-0036-verification-retry-exhaustion.md
