verification-before-completion

To enforce verification before completion, you require explicit evidence from fresh test outputs and checks to meet quality gates. This process blocks task progression until validation passes, ensuring claims of done are backed by audit results.

Evidence-based task completion is a governance approach requiring fresh test outputs and validation checks before work is marked done. It prevents unverified claims by accumulating explicit evidence to pass defined quality gates.

You block workflow progression by integrating verification steps that require fresh test outputs and evidence accumulation. The workflow halts until manual checks or CI validation passes the defined quality gates before completion.

Yes, this verification approach integrates with CI pipelines and manual checks to block progression until validation passes. It requires running verification commands and capturing results as evidence to satisfy quality gates.

You need fresh test outputs before claiming work is done to ensure honesty and quality. Relying on stale results threatens integrity, whereas explicit verification steps accumulate evidence that confirms actual success against quality gates.

You capture verification results for an audit trail by running full verification commands, evaluating the outputs, and accumulating the evidence. This explicit evidence confirms success and meets quality gates before marking completion.