Verification Before Completion

Verifying build outputs before completion requires executing fresh commands and evaluating their results to confirm success. This prevents unverified status reports by enforcing an IDENTIFY, RUN, READ, and VERIFY stepwise workflow.

Evidence-based status verification is a strict sequential workflow that requires fresh command execution and output evaluation before success claims. It prevents silent failures by demanding actual test and build results as proof of completion.

To prevent unverified success reports, enforce a strict sequence of IDENTIFY, RUN, READ, and VERIFY steps before declaring completion. This guardrail ensures automated tests and builds provide fresh output evidence rather than unverified claims.

Enforcing verification before completion works with existing guardrails by adding a strict IDENTIFY, RUN, READ, VERIFY, and ONLYTHEN sequence. It applies to any workflow requiring fresh command execution and evidence evaluation across tests and builds.

Automated workflows report success without verification because they lack strict guardrails requiring fresh command execution and output evaluation. Enforcing a sequential verification workflow prevents these unverified completion claims and silent failures.

You need to enforce a stepwise verification workflow whenever a task requires evidence of results across tests and builds. It protects against dishonest completion claims by requiring fresh output evaluation before declaring success.