verification-before-completion

You can enforce verification before completion by implementing a gate workflow that identifies the proof command, executes it, reads the output, and verifies the results before making any success claim. This prevents unverified completion claims during PR reviews or builds.

A verification gate requires identifying a proof command, running it, and evaluating the fresh output before allowing any task to be marked as complete. It works by executing the verification, reading the results, and confirming success to prevent unverified completion claims in software audits.

Capture evidence for build and code review claims by running verification commands and logging the results to support your success claims. This evidence-first approach ensures proof of success is recorded and attached as artifacts before making any completion proclamations.

Yes, you can use a verification gate workflow for builds, release checks, PR reviews, and audits. The workflow applies to any software task where success claims must be backed by verifiable outputs before a commit or merge is allowed.

The best way to prevent unverified completion claims before a merge is to implement an evidence-first gate that executes the proof command, reads the results, and verifies them before allowing a completion proclamation. This ensures merge claims are always backed by fresh verification evidence.

A verification gate requires fresh evidence before a commit to prevent unverified completion claims and ensure success claims are backed by verifiable outputs. Executing the proof command and reading the results immediately before the commit guarantees the evidence is current and accurate for the task.