verification-before-completion

Verification before completion means running the full test, build, and lint suite on your changes and confirming all outputs pass expected success criteria. Execute the complete verification command, read the output carefully, and only claim success when evidence—such as exit codes and validation summaries—confirms the work is done.

Attach exact command results as proof: test exit codes, build logs showing successful compilation, linter reports with zero errors, and any regression test output. Fresh verification output—not cached or assumed results—demonstrates the work actually passes and is ready for review.

Run verification fresh before each commit or PR submission. Code changes between verification runs can introduce new failures. The Iron Law requires evidence from the exact state you're claiming is complete, not from an earlier check.

No. Local test passage alone is not sufficient verification for completion claims. Wait for the full CI pipeline—tests, builds, linters, and any regression suites—to complete and pass. Only the complete pipeline output constitutes valid completion evidence.

Stop work on the next task immediately. Return to debug the failure, fix the root cause, and re-run the full verification suite until all outputs meet success criteria. Only then resume forward progress and claim the prior work complete with attached evidence.

Code evolves between verification checks. Dependencies update, environment state changes, and new failures emerge. Fresh verification ensures the exact code state you're claiming as complete has been tested and proven to work right now, not in the past.