verification-before-completion

To enforce verification before claiming task completion, you must require fresh evidence from explicit verification commands. This evidence-based closure process ensures claims are only made when verifiable results, such as exit codes and build artifacts, exist.

Evidence-based completion is a workflow that requires running verification commands to produce fresh results, reading those results, and verifying all checks pass. It provides an audit trail documenting outputs and artifacts before declaring a build or handoff done.

No, you do not need external dependencies to verify completion with fresh evidence. The solution requires no external dependencies and can be used with standard command-line verification practices to document outputs and exit codes.

To document an audit trail for quality assurance claims, run explicit verification commands to produce fresh results, then attach the evidence. Declare completion only if all checks pass, ensuring trustworthy status for builds, tests, and demos.

You should require fresh evidence over stale build results whenever trustworthy completion status is critical. This applies to software builds, tests, demos, and handoffs where misleading stakeholders with unverified completion claims poses a risk.