verification-before-completion

Premature commits and handoffs happen when work is claimed complete without fresh verification. Enforcing a gate function requires running verification commands, reviewing output, and validating results, which provides guardrails against claiming success without evidence.

A gate function prevents premature commits by enforcing steps to identify, run, read, and verify command outputs before claiming success. These guardrails ensure evidence-based declarations by reporting actual state before any VCS handoffs.

Yes, enforcing evidence-based completion applies to any claim of finished work and requires no specific testing frameworks. It operates by enforcing fresh verification through running full verification commands and validating results regardless of the environment.

Claiming work is complete without verification causes quality assurance issues because it is dishonest and bypasses evidence-based validation. Without running full verification commands and reviewing output, actual state goes unreported, leading to false completion claims.