verification-before-completion

To stop false completion claims, you must enforce a verification gate that requires fresh test evidence before reporting success. This prevents premature done claims by checking exit codes and outputs to ensure the proving command actually passed.

Evidence-first completion reporting is a workflow rule requiring fresh verification output, such as passing test or lint results, before claiming a task is finished. It forces you to run the full proving command and confirm the output proves the stated result.

You can verify bug fixes by applying a gate function workflow that runs the complete verifying command, checks the exit code, and reads the output. This prevents premature success claims by allowing completion reporting only when evidence explicitly confirms the result.

Agent workflows report completion incorrectly when they rely on rationalizations like should pass or trusting previous runs instead of fresh evidence. To fix this, enforce an exit code checking rule that stops honest reporting until the full verifying command is run and confirmed.

Yes, this verification gate workflow applies directly to regression testing, linting, and builds within software engineering. It ensures you do not claim tests or lints succeeded until you run the full verification command and report what the output proves.

Common failure modes include trusting agent reports without fresh checks, relying on partial checks, or counting earlier runs as proof. Avoid these red flags by enforcing a gate workflow that runs the complete verifying command and checks the exit code before reporting.