verification-before-completion

To verify code changes before claiming completion, you must run fresh verification commands like tests, builds, and lint checks, then read the complete output to ensure your success claim is supported by evidence.

Evidence-based verification is a governance discipline requiring developers to run verification commands and examine complete output before making any claims about project completion, ensuring all success statements are formally supported by fresh test or build data.

You can enforce a verification gate by applying a five-step process: identify the claim, run fresh verification commands, read the complete output, verify the evidence supports the claim, and only then claim completion.

Yes, this verification process works for lint checks, software builds, and tests across software projects by enforcing the execution of these commands and requiring you to examine their complete output before claiming success.

Claiming completion before running tests causes unverified success claims, which this verification discipline prevents by enforcing a formal gate that requires fresh command output and evidence examination prior to any completion statement.

The limitation of enforcing verification before completion is that it strictly requires running fresh verification commands and reading their entire output, meaning you cannot claim success for any project workflow without first producing supporting evidence.