sp-verification-before-completion

A verification gate requires running the full verification command, inspecting its output, counting failures, and verifying against criteria before declaring completion. This ensures work claims are backed by auditable command results and outputs.

An auditable verification gate enforces a step-by-step process to capture outputs, exit codes, and logs before announcing any completion status. This supports post-hoc validation by ensuring fresh evidence backs every sign-off.

The best way to prevent sloppy closures is to gate work claims by requiring fresh verification evidence before any completion status is announced. This ensures outputs are reviewed and failures are counted before a task is marked done.

Yes, you can use verification gates for any workflow where status or sign-off must be backed by verifiable command results. The process applies universally to ensure completion claims are validated against actual output.

To declare completion with verifiable evidence, you must identify the verification command, run the full command, read its output, verify the results against your criteria, and only then make the completion claim with the captured evidence.