verification-before-completion

You enforce verification by running a fresh proving command, reviewing its full output, and only claiming completion with attached evidence. This prevents unverified success claims and ensures accountability in development workflows.

A verification gate is a deterministic process requiring fresh test, linter, or build execution before status updates. It identifies the proving command, runs it, and verifies results to prevent dishonest or risky unverified success claims before merging or releasing.

You need fresh verification and evidence before any status update, commit, merge, or release. It is specifically required when claiming work is complete, ensuring that tests, builds, and checks are proven successful prior to deployment or post-mortem audits.

The best way is a 5-step gate: identify the proving command, run it fresh, read the full output, verify the results, and state your claim with evidence. This deterministic approach guarantees checks are passed before releasing.

Yes, this verification gate is useful in audits or post-mortems to ensure verifiable status reporting and accountability. It enforces a policy of fresh verification and evidence before any formal status update is declared or recorded.

Claiming completion without running fresh tests is dishonest and risky because it relies on unverified assumptions. Enforcing a formal verification gate ensures tests, linters, and builds are actually executed and proven before merging or releasing.