verify-completion

Preventing premature completion claims requires enforcing a verification gate that runs a defined command, parses full outputs for pass or fail, and updates pipeline state to validate acceptance criteria before any claim is made.

AC verification gates software hand-offs by enforcing a step-by-step workflow that runs a verification command, parses full output for pass or fail, and updates pipeline state to ensure acceptance criteria are met before completion.

To enforce a verification gate step by step, follow the IDENTIFY, RUN, READ, VERIFY, and ONLY THEN workflow to run a defined verification command, parse full outputs for pass or fail, and validate completion status before claiming completion.

Yes, a verification gate applies to project handoffs and code reviews where verification evidence and acceptance criteria must be produced by running a defined command, parsing full outputs for pass or fail, and updating pipeline state accordingly.

Verification evidence parsing integrates with an AC verification script and artefacts to surface concrete evidence for decisions by running a defined verification command, parsing full outputs for pass or fail, and validating acceptance criteria before completion.

Pipeline state may not update if the verification gate does not successfully parse full outputs for pass or fail, or if the acceptance criteria validation workflow is not fully completed before attempting to make a completion claim.