verification

Code verification against requirements works by reading existing plan and execution documentation to check alignment with acceptance criteria. It enforces an evidence-first policy, ensuring claims of completion are backed by verifiable execution logs.

You generate an acceptance report by running a verification workflow after execution logs and plan documents are ready. The workflow produces an acceptance report that records validation results, supporting evidence, and any identified issues.

Evidence-backed validation is needed for end-to-end software tasks where plans and execution logs exist. It is required when you must ensure code truly satisfies stated requirements through verifiable evidence before declaring the task complete.

Requirement validation does not work without execution logs and plan documents. The verification process applies specifically to end-to-end software tasks where these documents exist, as it requires them to trace execution against acceptance criteria.

The best way to prevent premature claims of code task completion is to enforce an evidence-first validation policy. This requires reviewing plan documents, tracing execution logs, and generating an acceptance report before declaring the task finished.