verification-before-completion

Verification before completion requires running a fresh verification command, reviewing the output for success, and confirming the outcome before updating any status. This gate-logic workflow prevents unverified completion claims by enforcing explicit evidence checks.

Evidence-based completion in software QA is the practice of requiring explicit verification outputs before claiming a task is done. It replaces assumptions with verifiable results, enforcing an explicit gate-logic workflow to prevent risky assertions during task closures or PR reviews.

To add an explicit VERIFY step, structure your workflow to identify the task, run the verification command, read the results, and check the exit status. You only claim completion after documenting the outcomes and confirming the evidence supports a successful result.

You need to run fresh verification commands because relying on previous assumptions is risky. Enforcing an explicit verification gate ensures that your completion claims are backed by current, documented evidence, maintaining integrity for deployments, tests, and PR reviews.

Yes, you can use this verification gate process for PR reviews, tests, and deployments. The workflow applies to any software development or QA task that requires running verification commands and confirming outcomes before closing tickets or claiming completion.