verification-before-completion

Verification evidence is enforced by identifying a proof command, running it, reading the full output, and validating exit codes before claiming task completion. This structured workflow ensures honest, verifiable completion claims by requiring fresh results as auditable proof.

The best way to verify code changes before a pull request or deployment is to run full verification commands, inspect the outputs, and confirm results match the intended outcome. Only claim success if fresh results explicitly confirm the completion criteria.

Evidence-driven decision making for QA works by attaching verification logs and command outputs directly to your completion claim. This provides auditable proof that fresh results confirm the intended outcome before a pull request, deployment, or task closure is approved.

If verification command output does not match your completion claim, you must report the failures and address the root cause. You should never claim success without fresh verification evidence explicitly confirming that the results match the intended outcome.

No specific testing frameworks or dependencies are required. The verification workflow applies across general software development workflows and QA processes, allowing you to identify and run whatever verification command is applicable to your specific project environment.