DC-PROD-02

DC derived enforced

Coordinator slot-tick + forge-result stream replay-equivalence. For a fixed initial CoordinatorState, fixed canonical slot-tick sequence, fixed ledger state, fixed opcert public metadata, and fixed RED forge-result event stream (ForgeSucceeded | ForgeFailed sequence), the coordinator emits byte-identical broadcast effects and byte-identical ProducerLogEvent sequence. Wall-clock real-time timestamps and socket arrival order are non-load-bearing RED metadata. Replay is over canonical event streams — NOT real wall-clock time. The forge-result event stream is the canonical surface across the RED-key-custody boundary; the GREEN coordinator is replayable against it without ever seeing secret material.

Source: docs/planning/phase4-n-q-invariants.md §1 (I7, I8); §3 (D5); §4 (R3, R4); §8
Cluster: PHASE4-N-Q
Introduced in: PHASE4-N-Q

Enforcement trace

Code

crates/ade_runtime/src/producer/coordinator.rs

Tests 1

replay_byte_identity_across_two_runs

CI 0

no CI script — gap

Cross-references

Open obligation

The S2 inline replay test covers the mechanical claim across a synthetic canonical event corpus (two runs over [CoordinatorStarted; SlotTick(0..3); ForgeSucceeded | ForgeNotLeader | ForgeFailed] → byte-identical effects + log). An operator-pass replay anchor — two ade_node --mode produce runs against the same canonical inputs producing byte-identical ProducerLogEvent sequences when filtered to the replayable vocabulary — is captured by docs/clusters/PHASE4-N-Q/CE-N-Q-OPERATOR_PROCEDURE.md §F. UPDATE 2026-05-29: the real forge handler has landed (run_real_forge, no stub — N-R-A/N-S/N-W); this anchor is now gated only on operator-pass execution. Reopen criteria: capture two ade_node --mode produce transcripts against the same canonical inputs and assert byte equality on the filtered replay surface.