verification-before-completion

To enforce verification before claiming task completion, you must execute specific test commands and present their output as fresh evidence. This strict evidence-before-assertions policy prevents premature success claims by requiring actual command execution and output analysis to confirm correctness.

An evidence before assertions policy is a process enforcement mechanism that mandates running verification commands and analyzing their output before declaring any development task complete. It ensures honesty in work status by preventing false positives like assuming tests pass without running them.

To prevent false positives from assuming tests pass without running them, enforce a mandatory verification process requiring the execution of defined test suites. You must confirm zero failures and present the actual command output as evidence before declaring any fixes or work statuses complete.

Yes, process enforcement for verification applies to all stages of development and task management where success or correctness is declared. It requires running specific verification commands and analyzing their output to confirm claims, ensuring accuracy across the entire workflow.

The best way to verify code quality before creating a pull request is to run the defined test suite and confirm zero failures. You must present the executed verification command output as evidence before declaring the work complete to satisfy strict process enforcement.

Claiming a build succeeded based on partial checks fails verification because it lacks fresh, executed evidence from specific verification commands. The strict evidence-before-assertions policy requires complete output analysis to prevent such false positives and ensure accurate completion claims.