FIELD NOTE / X
Yesterday's test can ride today's release.
The complete written thought and the evidence behind it. The video edition will follow its public release.
The written argument is here.
This approved X edition is on the journal now. Its video player and original platform link will appear after each public release is verified.
Yesterday's test can ride today's release.
Video caption
Yesterday's test can ride today's release. Check source, image, report and environment. A report is evidence for one build. #EricFieldNotes
Full written post / accessibility read
Imagine a release packet that attaches a successful browser test for image A while promoting image B. Both have plausible green records, but the report never exercised the digest customers will receive. A trusted check issuer helps with provenance; it does not bind the test to the promoted artifact by itself.
The release gate should compare the tested image digest with the image digest in the deployment request, plus the source commit, test-run ID and environment. If a dependency or build input changed, the source commit alone can be insufficient. A report for A is not a pass for B.
Build two harmless candidate images in a disposable pipeline. Attach A's passing report to B's promotion request without altering the report itself. The gate should mark the required claim UNVERIFIED and stop promotion, even though the test count is positive and the check came from the expected app.
My rule: require an exact tested-to-promoted digest match for every release claim, with a new run when the artifact changes. Do this because a real passing test attached to the wrong bytes is still no evidence for the software customers will use.
#EricFieldNotes
Four-beat scene transcript
1. Yesterday's test can ride today's release.
Imagine a release packet that attaches a successful browser test for image A while promoting image B. Both have plausible green records, but the report never exercised the digest customers will receive. A trusted check issuer helps with provenance; it does not bind the test to the promoted artifact by itself.
Visual: The badge may belong to a different image.
2. Bind evidence to exact bytes.
The release gate should compare the tested image digest with the image digest in the deployment request, plus the source commit, test-run ID and environment. If a dependency or build input changed, the source commit alone can be insufficient. A report for A is not a pass for B.
Visual: Check source, image, report and environment.
3. Run a digest-replay canary.
Build two harmless candidate images in a disposable pipeline. Attach A's passing report to B's promotion request without altering the report itself. The gate should mark the required claim UNVERIFIED and stop promotion, even though the test count is positive and the check came from the expected app.
Visual: A valid old report must be rejected.
4. Green must name the artifact.
My rule: require an exact tested-to-promoted digest match for every release claim, with a new run when the artifact changes. Do this because a real passing test attached to the wrong bytes is still no evidence for the software customers will use.
Visual: A report is evidence for one build.
Research and claim limits
The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.