verification-before-completion

You can enforce test verification by applying a formal gate workflow that requires IDENTIFY, RUN, READ, VERIFY, and ONLY THEN steps. This ensures no completion claims are made without fresh verification evidence from your builds. It prevents premature releases by demanding verifiable test results.

An evidence-based completion claim gate is a rigorous workflow that validates status updates by requiring fresh test results or builds. It defines a five-step process—IDENTIFY, RUN, READ, VERIFY, ONLY THEN—to ensure every positive status update is grounded in verifiable evidence.

To prevent AI agents from reporting dishonest task completion status, implement a verification gate requiring them to run fresh checks and document exact commands and outputs. This enforces evidence-based completion claims, stopping unverified status updates across development pipelines.

Verification-before-completion works for software teams by providing audit-friendly evidence logging for PRs and deployments. It integrates with your CI/CD workflows to enforce a five-step gate, ensuring every task outcome is backed by verifiable build and test evidence.

You should not use an automated verification gate when you cannot run fresh checks or document exact command outputs. The gate requires a formal workflow to produce verifiable claim-evidence outputs, so it is unsuitable for environments where tests or builds cannot be executed on demand.