verification-before-completion

Requiring fresh verification evidence before claiming completion prevents unseen defects and dishonesty. This discipline enforces an explicit workflow to run tests, read output, and confirm success, providing traceable proof for stakeholders and reducing regression risks.

The structured workflow for validating development results is a five-step gate process: IDENTIFY the target, RUN the verification, READ the output, VERIFY the evidence, and CLAIM completion. This ensures any success claim is fully supported by fresh results.

To require fresh evidence for completion claims during QA testing, enforce an iron law discipline where output is explicitly read and verified before any success is claimed. This process captures traceable proof and reports failures immediately if evidence is insufficient.

Yes, this verification-before-completion discipline applies broadly to software engineering, development, testing, and QA workflows. It enforces explicit evidence capture and failure reporting regardless of the specific task, ensuring all completion claims are fully auditable.

The best way to prevent declaring work complete without validation is to enforce a structured gate that requires running verification commands and reading the actual output. Claims are only allowed when fresh evidence explicitly confirms success, eliminating unsupported assertions.

Claiming completion without verification leads to unseen defects because success is asserted without fresh evidence or output validation. Enforcing an explicit verification workflow captures traceable proof and reports failures, ensuring stakeholders receive honest and accurate status updates.