verification-before-completion

To enforce evidence-based completion claims, you must identify the designated verification commands, run them freshly, read and validate the outputs, and only then declare success with documented evidence of the results.

The best way to verify testing results before claiming completion is to run the proving commands fully, review the fresh outputs, and report the verifiable results. This ensures that status claims influencing downstream release actions are backed by fresh evidence.

Claiming work complete without fresh verification causes regressions because downstream actions proceed based on unverified status claims. Enforcing structured verification workflows requires running proving commands and validating outputs to catch undiscovered failures before declaration.

No, verification guardrails for QA workflows require running designated test commands fully and reading the fresh outputs. Without executing these verification commands and validating the results, you cannot generate the verifiable evidence needed to claim completion.

Yes, quality assurance verification requires documenting command outputs as evidence to improve traceability. The workflow involves identifying proving commands, running them freshly, reading outputs, and reporting the verifiable results to support any completion statement.