verification-before-completion

To enforce verification before claiming code completion, execute fresh tests, linting, and builds, then validate their exit codes and outputs to produce documented evidence before reporting success.

Evidence-first completion is a workflow discipline requiring fresh verification results from tests and builds to validate success before any completion claims are made, preventing premature releases and unreliable software.

To prevent premature pull requests, enforce documentation of fresh verification results as evidence by running tests and linting, inspecting outputs, and validating success before committing or creating PRs.

Verification before completion applies across software development, QA, and code-review workflows, ensuring trustworthy completion claims and reproducible audits by requiring fresh verification results before reporting success.

The best way to validate build and linting output is to run designated verification commands in your environment, generate fresh results, review the outputs and exit codes, then document them as evidence before committing.

Claiming completion without verification leads to unreliable software and distrust because it skips validating fresh test and build outputs, allowing unproven code changes to be committed or released prematurely.