verification-before-completion

To prevent false positive claims of task completion, enforce a strict protocol requiring explicit verification command execution and output review before making any success assertions. This evidence-based validation prevents premature completion claims and maintains work integrity.

Evidence-based verification for software deployment and testing is a protocol requiring concrete output from verification commands as proof before any success claims are made. It mandates running specific validation commands and reviewing their output to confirm work is genuinely complete and correct.

To verify code fixes before merging a pull request, execute relevant validation commands and review their concrete output to confirm the work is complete. This protocol requires explicit verification command execution at all stages, from development to deployment, to prevent costly errors.

Yes, mandatory verification works for quality assurance without external dependencies by enforcing a strict protocol of evidence-based claims. It requires running specific verification commands and reviewing their concrete output before declaring any task complete, fixed, or passing.

You should not use evidence-based completion assertions when you cannot execute explicit verification commands or review their output. The protocol requires concrete validation output as proof, making it unsuitable for stages of work where running specific verification commands is not possible.