verification-before-completion

To enforce verification evidence before completion, you must execute verification commands like tests and builds, analyze the actual outputs, and only update the PR status after documenting fresh successes or failures.

A verification gate in a CI pipeline is a disciplined process that requires running fresh builds and tests to produce evidence, ensuring no completion claims are made without verified, documented results.

You can stop unverified completion claims by standardizing the workflow to require executing verification commands, analyzing outputs, and documenting failures or successes before any status update is allowed.

Yes, this verification process applies directly to development workflows across CI pipelines, code reviews, and release gate decisions, requiring actual verification outputs before updating assertions or handoffs.

To document build and test failures during release gate decisions, you execute the verification commands, analyze the outputs, and record the specific failures before updating the completion status.