When Every Internal Check Passes and the Handoff Is Still Wrong
A handoff can be perfectly valid and still describe the wrong branch. The failure that made this concrete for me was deliberately boring. In a deterministic fixture, a producing agent reads the wrong Git branch. It records an authentication provider and a row count that are both wrong for the working tree being handed off. The JSON is valid. Its provenance graph is connected. Its commitments…
When a handoff is successful, it may still end up describing the wrong branch of data. In a deterministic test scenario, an agent reads the incorrect Git branch, resulting in authentication provider and row count values that are inaccurate for the working tree. Despite the JSON being valid, the provenance graph remains connected, and the commitments recompute correctly.
Seven checks accept the artifact, but only one rejects it when it looks at the repository instead of the handoff. The failure demonstrates that even with every internal check passing, the final handoff can still be incorrect.
The issue is not caused by a production incident or by any language model. It involves deterministic fixtures designed to isolate specific boundaries. The problem lies in the verification process, which accepts the artifact despite the wrong branch information. The failure highlights the distinction between a valid format, correct provenance, recomputed commitments, independent encoders, and an external receipt.
Each of these checks independently verifies different aspects of the artifact but does not guarantee the correctness of the final interpretation. This failure underscores the importance of understanding and clearly defining the boundaries of each verification step.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
