DC-MEM-05

DC derived declared

The UTxO/ledger state fingerprint and post-state are independent of the UTxO storage backend: an in-memory UTxO and an on-disk UTxO produce byte-identical replay (same WAL + checkpoint => same tail fingerprint). A memory-representation/storage change is NEVER a consensus or replay change.

Source: Project constitution §3 (replay is the integration contract); MEM-OPT cluster plan (docs/planning/mem-opt-cluster-plan.md); DC-WAL-03

Enforcement trace

Code

no enforcing code — gap

Tests 0

no tests named — gap

CI 0

no CI script — gap

Cross-references

Evidence notes

Declared at MEM-OPT scoping (2026-06-15). The load-bearing on-disk-UTxO invariant: the redb-backed UTxO (cluster MEM-OPT-UTXO-DISK) is a pure storage substitution behind the unchanged BLUE ledger interface. Enforced by extending the DC-WAL-03 / replay_from_anchor corpus to run byte-identically under both backends.