verification-before-completion

Evidence-based completion claims require a four-step verification process: identify the proving command, run full verification, read and interpret results, then report the claim only when fresh evidence supports it.

The best way to verify completion is to run the full verification command, review the entire output, and report the final status with fresh evidence to prevent regressions and ensure reliable software delivery.

A verification gating process works by requiring fresh verification output before approving PRs, releases, or sprint handoffs, creating an auditable protocol that reduces rework and ensures claims are backed by evidence.

Yes, the evidence-based verification protocol applies to QA, software development, and general project work, ensuring every completion claim is gated by fresh verification output regardless of the specific project context.

Requiring fresh verification output prevents unreliable software and miscommunication by enforcing an auditable protocol where completion claims are proven by recently executed commands and interpreted results.

Gating completion claims on verification evidence requires executing a proving command and interpreting full results each time, which adds procedural overhead to PRs, releases, and sprint handoffs but significantly reduces rework.