RO-LIVE-02

RO release partial

A cardano-node peer's RollForward + BlockDelivered stream, consumed by the receive bridge, produces a ChainDb tip equal to the peer's announced tip at every step over a captured follow window. Live evidence captured against a private cardano-node peer; underlying invariants are CN-CONS-08, DC-CONS-19, DC-CONS-20, DC-PROTO-09, and the existing block_validity (B1) authority.

Source: docs/planning/receive-side-bridge-invariants.md §8
Cluster: PHASE4-N-H

Enforcement trace

Code

Tests 5

receive_pipeline_corpus_drive_admits_every_block
receive_pipeline_corpus_drive_chaindb_tip_matches_expected
receive_pipeline_corpus_drive_admitted_bytes_equal_corpus_bytes
receive_pipeline_corpus_drive_ledger_fingerprint_changes_on_admit
live_block_follow_session_hermetic_default_prints_readiness

CI 1

ci_check_receive_paths_corpus_present.sh

Cross-references

Evidence

Mechanical pre-condition closed by receive_pipeline_corpus_drive: every Conway-576 corpus block admits through the full receive pipeline; ChainDb tip matches expected (slot, hash); stored bytes equal corpus bytes byte-identically; LedgerState fingerprint changes on admission.
Binary live_block_follow_session builds + starts in hermetic mode; --connect mode requires a private cardano-node peer (open_obligation).
Procedure to flip status to enforced (operator captures log + commits) documented at docs/clusters/completed/PHASE4-N-H/CE-N-H-6_PROCEDURE.md — mirrors PHASE4-N-C/CE-N-C-8 and PHASE4-N-G/CE-N-G-8 patterns.