verification-before-completion

To prevent premature completion claims, enforce a verification gate that requires running full tests or builds and validating their outputs before declaring success. This ensures you attach verifiable evidence, such as exit codes and failure counts, to any status assertion.

Evidence-driven verification is a governance process requiring fresh test or build outputs before asserting work is complete. It identifies the proving command, runs it fully, reads outputs, checks exit codes, counts failures, and only then makes a claim.

You enforce verification gates by identifying the specific proving command for your task, executing it to generate fresh results, and reviewing the full output and exit status. Only declare success after attaching this verifiable evidence to your completion claim.

Yes, evidence-driven verification applies to any task requiring fresh verification evidence, such as tests, builds, or checks. It codifies a reproducible workflow to identify, execute, read, and verify results before reporting success.

The best way to ensure compliance is adopting an audit-friendly workflow that requires gathering fresh verification evidence. By running reproducible checks and validating outputs before reporting success, you guarantee claims are backed by verifiable data.

You need to run the full verification command to generate fresh, reproducible evidence. Without validating the complete output and exit status, completion claims lack audit-friendly proof and risk reporting premature success.