verification-before-completion

Verifying completion with evidence requires running a designated verification command and validating fresh test results, build outputs, and logs before declaring success. This enforces honest reporting by backing claims with documented, verifiable evidence.

Verification evidence in CI pipelines and code reviews consists of documented test results, build outputs, and logs. It provides auditability and traceability to ensure completion claims are backed by fresh, verifiable outcomes rather than assumptions.

Documenting test results for project handoffs involves running a full verification workflow and capturing exit codes, logs, and artifacts into a verifiable report. This produces traceable evidence supporting honest completion reporting.

Yes, this verification process works without external dependencies. It operates as a standalone workflow to evaluate designated verification commands and produce verifiable reports, requiring no additional components or frameworks.

Claiming completion without verification creates problems because it amounts to dishonesty rather than efficiency. Without fresh verification evidence from test results and build outputs, completion claims lack traceability and cannot be trusted.