verification-before-completion

To prevent premature success claims, mandate a strict verification protocol requiring fresh evidence before any assertions are made. This Gate Function forces engineers to run test suites and verify zero failures before declaring work completion, maintaining honesty and process enforcement.

A Gate Function for quality assurance is a structured protocol blocking success assertions until verifiable evidence is produced. It requires running relevant commands, reading the output to confirm zero failures, and then stating the result with the command used before declaring completion.

Your testing workflow allows premature declarations because it lacks a mandatory verification step. Without enforcing an Iron Law requiring evidence to precede assertions, engineers claim bugs are fixed without running the test suite to generate fresh, verifiable output confirming zero failures.

To verify bug fixes before committing code, run the relevant test suite and read the output to ensure zero failures. Then state the result, such as "All tests pass with 0 failures," along with the command used, adhering to strict process enforcement and honesty protocols.

Yes, this verification process applies to all stages of software development and task completion. It enforces a universal protocol requiring evidence before any declaration of success, ensuring honesty and preventing unverified assertions across the entire development lifecycle.

Relying on assertions without running test suites leads to dishonesty and inefficiency from unverified claims. Without executing commands to generate fresh output, you cannot guarantee zero failures, risking premature success declarations and compromised quality assurance.