verification-before-completion

To prevent premature completion claims in code reviews, enforce a verification step that requires explicitly running designated commands, inspecting outputs and exit codes, and reporting fresh evidence before asserting success.

Build status verification evidence is the auditable proof collected from running and inspecting build pipelines or test suites. You need it before declaring a task finished to prevent dishonest assertions and downstream deployment failures.

Enforce quality-assurance checks by running the full verification command across your development workflow, reviewing the complete output, and claiming completion only if all checks pass with fresh evidence before you proceed.

Yes, you can apply automated verification to release gates across development workflows by enforcing fresh evidence collection from designated commands and evaluating exit codes before allowing any success claims to proceed.

Claiming work is complete without verification causes downstream failures because it leads to dishonest assertions that bypass quality-assurance checks, introducing unverified code changes into audits, builds, and deployments.