verification-before-completion

To enforce verification before completion, you must run the full verification command set and capture outputs, exit codes, and failures. This approach ensures you only make completion claims when fresh execution outputs prove the claim.

Evidence-first completion in CI-CD guardrails is the practice of running fresh verification commands and capturing their outputs and exit codes. It ensures success is only claimed when actual command results provide transparent proof.

To verify command outputs and exit codes, run the full verification sequence and interpret the results to determine actual status. This generates transparent reports with evidence suitable for audits, PRs, and deployments.

Yes, this verification approach works with existing CI-CD pipelines by identifying the specific verification command that proves completion. It runs the command and reports actual status with captured evidence before any deployment.

Claiming work complete without verification causes flaky builds because it skips capturing command outputs and exit codes. This leads to unreliable releases and wasted effort when failure signals are ignored before making success claims.

The best way to capture failure signals during testing is to run the full verification command set and record outputs, exit codes, and any failures. Verifying these results prevents declaring completion when failures exist.