DC-PROTO-09
DC derived enforcedReceive-side transcript determinism: given canonical inputs (initial_ledger, initial_chain_dep, initial_chaindb, event_sequence), the bridge reducer's output state (ledger', chain_dep', chaindb') is byte-identical across replays. The reducer is a pure, total transition.
- Source
docs/planning/receive-side-bridge-invariants.md §3, §4
- Cluster
- PHASE4-N-H
- Authority surface
- receive-side session transcript
Enforcement trace
Code
Tests 2
- receive_apply_replay_byte_identical_over_corpus
- receive_session_transcript_replay_byte_identical
Cross-references
Strengthened in
Evidence
End-to-end integration test receive_session_transcript_replay_byte_identical drives a synthetic ForkChoiceSignal + BatchDeliveryEvent stream through the GREEN adapter + BLUE reducer + InMemoryChainDb twice and asserts identical (ledger fingerprint, ChainDb tip slot, ChainDb tip hash).
Reducer-level determinism is covered by receive_apply_replay_byte_identical_over_corpus.
PHASE4-N-I strengthening: the receive transcript now includes the rollback transition. The RollBackward branch is deterministic over (target_point, snapshot_reader, block_source); test rollback_then_continue_admit_equals_straight_line_admit proves snapshot+rollback yields the same fingerprint as straight-line admit.