verification-before-completion

Verify completion claims before a QA handoff by running fresh checks and capturing the results as evidence. This gate requires explicit reporting of the actual outcome using a 'proof surface' narrative before declaring any work complete.

A proof surface in software quality assurance is the fresh, verifiable evidence captured by running checks before a handoff. It enforces a gate requiring explicit reporting of the actual outcome before declaring work complete, fixed, or passing.

Enforce a completion gate for code reviews and project updates by running verification scripts that capture check results. The gate requires explicit reporting of the actual outcome and the bar 'full legitimate green' before declaring completion.

Yes, you can use verification scripts to require proof before declaring a bug fixed. The scripts run checks to obtain fresh proof surface evidence, ensuring every claim of passing or fixed work is backed by verifiable results.

You need to run completion verification checks for release readiness whenever a task is declared complete, fixed, or passing. The gate ensures every handoff claim is backed by fresh proof surface evidence rather than assumptions.

The best way to validate a project update is passing is to run verification steps that obtain fresh proof surface evidence. This approach enforces a gate requiring explicit reporting of the actual outcome and the bar 'full legitimate green' before completion.