verification-before-completion

A verification gate prevents unverified completion claims by requiring fresh evidence before any status change. You specify the command to run, execute it fully, analyze the output, and only then permit success claims for pull requests.

A verification-first policy requires running fresh checks and providing verifiable evidence before marking work as complete. It safeguards honesty by ensuring claims are backed by recently executed commands and analyzed outputs across workflows.

You prevent unverified completion claims by implementing a deterministic gate workflow that identifies verification commands, executes them fully, and analyzes their output before allowing any final status announcement or task handoff.

Yes, the verification gate workflow supports audits and PR gates by providing verifiable evidence before assertions. It ensures all checks pass and outputs are analyzed before success is claimed.

The verification gate requires specifying and executing a command fully before permitting success claims, meaning it cannot bypass failed checks or skipped executions. It strictly demands fresh verification evidence for every status change.