verification-before-completion

Fresh verification evidence prevents premature code completion claims by enforcing a five-step process—IDENTIFY, RUN, READ, VERIFY, ONLY THEN—requiring tests, lint, and build outputs before declaring success.

Enforcing code review claims requires running a gate function that validates verifiable outputs like tests and builds before allowing any PR workflow completion statement.

To verify test results before declaring completion, identify the claim, run the verification sequence, read the outputs, verify against criteria, and report the outcome with evidence.

Code completion claims fail without fresh verification evidence because the Iron Law requires identifying, running, reading, and verifying outputs to flag incomplete or unverified work and prevent premature release.

Yes, this verification process applies to lint and build workflows, requiring fresh outputs and evidence before any statement of completion is permitted.

Claiming completion without running fresh tests triggers red flags and safeguards that block unverified work, preventing premature release and ensuring honest status reporting.