verification-before-completion

Verification means running builds and tests, then showing the outputs as evidence. Execute your build command, run test suites, capture the results, and present them before declaring any change complete. This prevents false completion claims and ensures changes actually work.

Before marking a fix complete, build the project, run relevant tests, and display passing results. For factual claims like version numbers or dates, search and cite authoritative sources. Show all verification outputs as proof before claiming success.

Tests and builds provide visible evidence that code actually works. Running them exposes breaking changes, regressions, and failures before you claim completion. Without this verification step, you risk shipping broken code or spreading misinformation.

No. Completion requires presenting actual build and test outputs as evidence. Assertions must be verified and visible—never claim success based on assumptions or untested code. Always run the checks and display the results.

Use web searches to find authoritative sources, then cite them in your completion claim. For technical facts, pull from official documentation or release notes. Document your sources alongside the verification results.

Valid verification includes executing the build system, running test suites, displaying passing outputs, and confirming assertions against real execution. All evidence must be visible and reproducible—guesswork or theoretical reasoning does not satisfy verification.