CNC Fork Experiment (T=2): Second Hardware Run Forensics and a Certifiable Replication Protocol (Test 3)
Dale James Raymond
Abstract
This report records and interprets the second real-device execution of the CNC fork experiment in the certifiable T = 2 “binary-clock” design (runner v3), including a software-forensics correction: an obsolete analysis JSON incorrectly reported ν = 1.0 even though all 2-bit clock patterns are legal by construction in T = 2. It also specifies a final replication run (“Test 3”) intended to be maximally robust against the dominant remaining failure mode (near-threshold readout invasiveness on ibm_fez). A conclusive outcome of Test 3 is meaningful regardless of direction, because (as preregistered) the runner only emits a conclusive label after certifying overlap and bounding nuisance effects (mismatch and readout invasiveness). Run metadata (from locked runner output): backend: ibm_fez output created (UTC): 2026-01-10T19:03:16.074947+00:00 IBM Runtime job id: d5ha332gim5s73ahnueg physical layout (C1,C2,S): [1, 2, 3] protocol blocks: ε ∈ {0.40, 0.20} (primary block ε = 0.40) Qiskit versions (recorded by harness): qiskit 2.2.3, qiskit-ibm-runtime 0.43.1 Key certified outputs (primary block, ε = 0.40): D̄ = 0.381793 ν = 0.016503 (≤ ν_max = 0.020) ε_inv = 0.047647 (≤ ε_inv,max = 0.050) δ′ = 0.313209 decision (locked runner): reject hard CNC The Test 3 OSF preregistration is complete and time‑stamped, but remains embargoed until execution; the public link will be added here immediately after the embargo is lifted. Raw run artefacts and outputs to be archived as a separate Zenodo Dataset record by the hardware executor (Morgan Cameron). This report is a forensic note and replication/protocol document.