verification-before-completion

A verification gate enforces a mandatory five-step process (IDENTIFY, RUN, READ, VERIFY, ONLY THEN) to validate tests, builds, and requirements before reporting completion, ensuring all success claims are backed by fresh evidence.

To verify build completion, run the full verification sequence to capture fresh command output, check explicit success criteria like exit codes and failure counts, and only then report success based on that documented evidence.

Prevent premature releases by applying a verification gate that mandates fresh evidence and explicit exit-status checks across tests, builds, and linting before any task completion is publicly declared.

Yes, the verification process applies to demos and requirement checks across CI pipelines, enforcing documented failure handling and exit-status checks to ensure all criteria pass with verifiable output.

Automated completion claims are limited without fresh verification evidence; they require explicit exit-status checks and documented failure handling to protect against falsely reporting success before all build and test criteria actually pass.

The best way to enforce quality assurance is to apply a strict verification gate that requires running commands, reading fresh output, and verifying explicit success criteria before any completion claim is accepted.