verification-before-completion

To prevent false positive claims of work completion, enforce a strict protocol requiring the execution and examination of verification commands and their outputs before asserting task success. This evidence-based reporting approach ensures no incomplete code is shipped.

Evidence-based reporting in software engineering is a process requiring developers to run verification commands and examine outputs before claiming a task is complete, correct, or passing. This prevents premature assertions and maintains honesty in status updates.

To verify code quality before committing changes, execute the test suite and linter, examine their command outputs, and only then declare the changes ready. This mandatory verification ensures concrete evidence of correctness over assumptions.

Yes, mandatory verification applies to all stages of development, testing, and task finalization. It enforces a strict protocol that requires running and checking relevant command outputs before making any claims of success, correctness, or completion.

Shipping broken code happens without verification because developers make premature claims of completion based on assumptions rather than concrete evidence. Enforcing a strict process of examining command outputs before declaring work finished prevents these costly errors.

The best way to enforce a verification protocol before task finalization is to require the execution and examination of relevant command outputs before any claims of success are made. This rigorous validation process prevents premature assertions across all development stages.