verification-before-completion

To enforce verification before claiming a pull request is complete, execute the full proving command, parse the fresh output, and only assert success if the evidence validates your claims. This protocol prevents premature completion claims by requiring fresh test results as proof.

The best way to prevent premature completion claims is to implement a step-by-step governance protocol that requires executing verification commands and reading the full output before any success assertion. This ensures deliverables are backed by fresh evidence.

Evidence-based quality assurance for code changes works by requiring fresh verification outputs to determine status. You must execute the full verification command, parse the results, and only assert success if the fresh evidence confirms the completion claims.

No specific testing frameworks are required to verify completion with evidence. The process applies to any code changes, test results, or deliverables where you can execute a verification command and parse the output to validate status before asserting success.

You should run verification commands to support ticket closure claims immediately before asserting success. Executing the full verification protocol and attaching the fresh evidence ensures your completion claims are accurate and prevents delivering incorrect results.