verification-before-completion

To verify code changes before claiming completion, you must run fresh verification commands, read the full output, check exit codes, and document evidence. This prevents premature success claims by enforcing an evidence-based validation gate.

The verification process is a fixed five-step gate: IDENTIFY the commands, RUN them, READ the full output, VERIFY exit codes, and ONLY THEN claim success. This ensures honest reporting through documented evidence.

You enforce evidence-based validation during PR reviews by running fresh command sets, validating their outputs, checking exit codes, and documenting the evidence before asserting that the release checks are successful.

Yes, you can apply automated verification gates without external dependencies. The process relies on running fresh commands and validating outputs directly within your software development workflow to ensure honest reporting before completion.

Task verification fails because claiming success requires running fresh verification commands and documenting evidence. Without checking full outputs and exit codes, the fixed verification gate prevents any premature or unvalidated completion claims.

The best way to document evidence for quality assurance is to run the full verification command set, review the outputs, and record the exit codes. You only claim success when this documented evidence meets the criteria.