verification-before-completion

To verify completion with evidence, you must run the full verification workflow to produce fresh outputs, logs, and results that substantiate the claim. The workflow reads outputs, checks exit codes, counts errors, and reports the final determination with proof of correctness.

An evidence-first verification protocol enforces a step-by-step process requiring fresh verification results before making status claims. It identifies commands that prove completion, runs them to generate fresh logs, and reports the final determination with evidence.

You structure the verification workflow by identifying commands that prove completion and the success criteria that must be met. Run the full workflow to produce fresh outputs, verify exit codes and error counts, and report the final determination with evidence.

Yes, this verification approach applies to code, tests, builds, and documentation where fresh evidence is required to close work. It enforces governance by reading outputs, verifying exit codes, and reporting the final determination with evidence.

The best way to enforce quality assurance is to enforce an evidence-first approach that ensures outcomes are backed by fresh verification results. It identifies proving commands, runs the full verification workflow, and reports the final determination with evidence.

Claiming completion without verification risks releasing unverified work and misrepresenting progress because it lacks fresh evidence. Enforcing an evidence-first approach ensures outcomes are backed by fresh verification results, preventing unverified claims.