verification-before-completion

To verify code changes before a pull request, execute project-defined verification commands for the current HEAD, review the outputs and exit codes, and only claim completion if the results validate success.

Evidence-backed completion means preventing unverified claims by requiring structured verification. You must specify a verification scope, execute checks, read outputs, validate results, and transparently report evidence before asserting success.

You can record verification results by executing project-defined verification commands or citing a verification ledger entry, then reviewing the command outputs to validate actual status with supporting evidence before merging.

Yes, structured verification prevents dishonest completion claims by enforcing evidence gathering. It applies to CI pipelines where merges or deployments hinge on validated tests and verification outputs.

The best way to ensure compliance before committing is to determine the verification scope, run project-defined checks, interpret the command outputs, and report actual status with supporting evidence only after successful verification.

You should never claim work is complete without verification, as claiming completion without validated tests and evidence is dishonesty, not efficiency. Always execute checks and review outputs first.