verification-before-completion

Preventing premature completion claims requires enforcing a verification gate workflow that demands fresh evidence, like test outputs, before any task is marked complete. This ensures stakeholders only see verified results.

A verification gate workflow in QA is a four-step process—identify, run, read, verify—that prevents dishonest completion claims by requiring successful evidence validation before allowing any work to be declared complete.

You can enforce evidence-based task completion before a code review by running the verification steps and capturing fresh outputs to justify the claim. The task remains incomplete until this evidence is successfully validated.

Yes, you can use this verification gate across deployment workflows. It prevents misrepresentation of a task's state by applying clear evidence-based criteria and failure signaling before any release or PR status update is declared.

You need fresh verification evidence before declaring work complete to prevent misrepresentation of a task's state. Without visible, newly captured outputs, completion claims remain dishonest and risk premature release or inaccurate PR updates.