DC-PUMP-10
DC derived enforcedDeterministic, bounded reconnect backoff. Re-dial pacing follows a fixed const escalating schedule (RECONNECT_BACKOFF_SECS) that is monotone non-decreasing and saturates at a cap; it is deterministic -- no randomness, no wall-clock-derived jitter -- and the wall-clock delay is a RED transport concern that never reaches the BLUE core.
- Source
docs/clusters/LIVE-WIRE-LIVENESS/SLICE-S1-keepalive-under-backpressure.md + docs/clusters/LIVE-WIRE-LIVENESS/SLICE-S2-live-feed-reconnect.md (INV-WL-10)
Enforcement trace
Tests 1
- reconnect_backoff_is_deterministic_monotone_and_capped
Cross-references
Evidence notes
Determinism here is a discipline property (Part V tripwires) rather than a replay-authority one: the pacing never enters canonical input. SUPPORTING live evidence only (never the reason for enforcement): a sustained preview run 2026-08-01 (~/.cardano-live1/ade-1376-s1s2.log) held the live tip for 8h+ with 1400 consecutive keep-alive round trips, max observed inter-line stall 20.0s (the cadence itself) against the peers ~97s limit, and recovered a deliberate docker restart of cardano-node-preview in 1m48s. Enforcement rests on the named tests + ci/ci_check_wire_liveness.sh, not on this run.