verification-before-completion

To enforce evidence-based verification before claiming task completion, run a verification command, review the full output, validate exit codes, and report success only after confirming fresh evidence across code, tests, and configurations.

A verify-then-claim workflow in CI/CD pipelines enforces a disciplined approach to run verification commands, validate exit codes, and ensure fresh verification evidence is present before status updates, PRs, or deployments.

To validate test success claims with fresh verification outputs, execute the required test commands, read the outputs, validate the exit codes, and declare success only after the evidence checks pass.

Yes, you can use this verification approach for code reviews and project handoffs where trust and reproducibility matter, ensuring fresh verification evidence is validated before declaring success and reducing risk across builds.

Claiming build success without verified evidence leads to risk and dishonesty because it lacks validation from fresh verification outputs, exit codes, and confirmed results across code, tests, and configurations.