verification-before-completion

You can enforce verification before completion by running the required verification commands, parsing their outputs, and reporting fresh evidence to back every success claim regarding tests, builds, or deployments.

The Gate Function process for quality assurance requires you to identify the verification command, run it, read the outputs, verify the results, and report the evidence before making any success claim.

To collect fresh evidence for CI testing claims, state the claim to verify, run the required verification commands, review the outputs, and report the evidence before claiming completion.

Yes, you can use this structured verification process across development workflows where claims about tests, builds, or deployments must be backed by verifiable outputs to prevent premature releases.

Parsing command outputs for release verification is required to ensure every success claim is backed by verifiable evidence, which prevents dishonest or premature release claims across development workflows.