verification-before-completion

Evidence-based verification before pull request closure requires running an explicit verification command and analyzing its output to ensure proof supports any success claim. This prevents premature completion claims by enforcing a formal completion gate.

Preventing premature completion claims involves applying a repeatable five-step procedure: IDENTIFY, RUN, READ, VERIFY, and CLAIM. This enforces an evidence-backed quality gate ensuring verification steps are run before reporting development success.

A formal completion gate works by requiring an explicit verification step to be executed and its output analyzed before success is asserted. It acts as a strict guardrail to ensure evidence is captured for all code review claims.

Yes, strict guardrails are needed to verify claims with evidence because they enforce the formal completion gate. This ensures development tasks cannot assert success without first running verification commands and capturing the resulting output.

You need a quality gate capturing verification evidence during development sprints, code reviews, PR closures, and release workflows. It is required whenever strict guardrails demand proof before reporting task success.