verification-before-completion

To enforce proof before marking a task complete, you require a mandatory verification step that produces observable outputs like logs, test results, or snapshots. This prevents declaring work done without verifiable evidence of success.

Proof-driven completion is a workflow checkpoint mechanism that requires explicit validation before closing any task. It uses a standardized verification checklist to ensure bug fixes, feature implementations, and changes produce verifiable outputs before completion.

Preventing premature completion requires enforcing a verification checklist and explicit output validation before a task can be closed. This safeguard ensures teams must execute a verification step and display observable results for bug fixes and feature implementations.

Yes, a verification checklist works for auditing project workflows by providing a standardized framework to guide teams and auditors. It requires verifiable outputs and proof of success to accompany any completion claims across all project changes.

Before declaring work complete, you need to show proof of success such as execution logs, test results, or output snapshots. The verification step must display these observable results to validate the completion claim.