Receipts, logs, and Merkle-oriented artifacts answer “what do we know after the fact?” They are essential for diligence and reconstruction. They do not, by themselves, answer whether this bind should have been refused before the row changed. If the only enforcement story is “we will catch it in the dashboard,” you are still exposed at T₁.
Live verification vs tick-box compliance
Governed execution means a deterministic gate outcome on governed paths: allow, refuse, or shunt from current inputs—not a narrative that an earlier review “covered” today’s commit. That is why observability must not collapse into a second interpreter that forgives the bind; the forensic side-channel carries signals and evidence without substituting for T₁.
Lane honesty: receipt breadth and Merkle semantics remain scoped to shipped product and internal roadmaps—no Merkle-complete-everywhere marketing until symmetry work unlocks it.