verification-before-completion

To enforce verification before claiming code completion, you must run full verification commands, examine their output and exit codes, and present this evidence before making any assertions about work success or passing status.

To verify test suite output before committing code, run the full test suite and confirm zero failures in the output. You must present this executed evidence before stating that tests passed or the bug fix is complete.

Yes, the verification process applies to all stages of development, including linting and building. Any claims of completion or success across these stages require running full verification commands and examining their output and exit codes.

The best way to prevent false claims of a bug fix is to require mandatory verification. An agent must run the relevant verification commands, check for zero failures in the output, and provide this evidence before asserting completion.

Your code review process needs evidence from exit codes to maintain honesty and prevent costly errors. Examining fresh exit codes and command outputs ensures that claims of passing status or completion are backed by verified execution.