verification-before-completion

To verify work before claiming completion, run the verification command to produce fresh results and attach the output as evidence. Completion is claimed only when the verification output confirms success.

Evidence-first completion is a governance process requiring fresh verification output as proof before any success claims are made. It prevents dishonesty by ensuring results are reviewed and attached as evidence prior to completion.

To enforce verification before a pull request, use a process that mandates running fresh verification commands and attaching the output as evidence. Completion claims are blocked until verification output confirms success.

Claiming completion without verification causes problems because it introduces dishonesty into the process. Running verification and attaching fresh output as evidence ensures that success claims are backed by confirmed results.

Yes, you can use verification evidence for release status claims. The process applies to releases, commits, and PRs by running fresh verification, attaching the output, and confirming success before claiming completion.

A limitation of enforcing verification before completion is that it requires running fresh verification commands every time. Completion cannot be claimed until the verification output is produced, reviewed, and confirms success.