verification-before-completion

To verify task completion, you gather concrete evidence by running tests, builds, and linting, then presenting the actual outputs. This approach enforces documentation of verification steps to prevent premature reporting.

Evidence-based validation is the process of producing objective outputs like test results and build logs to back up completion claims. It prevents declaring work done without running actual verification steps such as make test and make compile.

You run verification steps by executing commands like make test, make compile, and linting tools, then displaying the real outputs. This enforces objective validation across development, QA, and deployment stages before claiming work is done.

Yes, this verification approach integrates with CI-CD pipelines by executing tests, builds, and linting to generate evidence. It enforces running these steps and presenting outputs before marking tasks as complete across your deployment stages.

The best way to validate a build before marking a feature done is to execute make compile and make test, then present the actual outputs as evidence. This ensures stakeholders see verifiable build logs and test results.

You should display actual test outputs because objective evidence prevents premature reporting and ensures completion claims are backed by real results. Enforcing this documentation step provides verifiable proof across development and QA stages.