verification-before-completion

Build verification evidence is fresh output from running tests, linting, or builds that proves a task succeeded. You need it to prevent dishonest completion claims, avoid downstream rework, and provide auditable proof of success for quality assurance.

To verify test results before closing a pull request, identify your verification command, execute it fully, read the outputs, confirm success, and only then declare completion with the attached evidence.

Yes, this verification workflow handles build failures and linting errors explicitly through a five-step governance process that includes explicit failure handling and requires reading outputs before making any success claim.

The best way to automate quality assurance claims for CI pipelines is applying a gate-driven workflow that requires running verification commands, reading outputs, and attaching auditable evidence before any completion claim is accepted.

Yes, you can use this verification process for any non-software delivery tasks requiring auditable proof, as it enforces a deliberate, repeatable five-step process applicable to any workflow needing verified success assertions.

A limitation of a gate-driven verification workflow is that it strictly prohibits claiming completion without fresh verification evidence, meaning you cannot bypass the five-step process even for minor tasks or rapid iterations.