Prove the release
Test the deployed sequence, environment, and dependency lineage, not only the final code state.
Green evidence matters only when it covers the artifact, ancestry, and environment being released.
See the failure before the pattern
The reviewer rejected my fix twice. Both times it was right.
Why passing tests and a good staging walk did not prove a data-dependent release was safe, and how an independent reviewer found two temporal bugs.
Data before code is a graph problem
Model a data-dependent deployment as a commit-ancestry invariant instead of a current-push checklist.
Copy the control, then adapt it
Review a production change
A reusable agent skill for independently challenging a release candidate before production approval.
Deploy data before dependent code
A GitHub Actions workflow that waits for a covering data workflow run before application deployment.
Release ancestry gate
A tested shell gate that proves a prerequisite workflow run covers the required commit and belongs to the release.
What this pattern is grounded in
Proof items describe real findings or working controls. Sanitized and reconstructed examples say so explicitly. They are evidence for the lesson, not universal guarantees.