verification-before-completion

Verify code changes against acceptance criteria by spawning a fresh-context verifier to audit the task diff. This isolated inspection validates test coverage, scope boundaries, and language alignment without exposure to the worker's internal reasoning.

A fresh-eyes QA gate audits a worker's completed diff using a verifier with no prior context, ensuring acceptance criteria are met before committing. It prevents premature commits by validating scope and test results independently of the original worker's reasoning.

Prevent scope drift by running a fresh-context verifier that compares the task diff against acceptance criteria. This diff audit validates scope boundaries, checks test coverage, and enforces ADR decisions before the code is committed.

Yes, you can validate ADR-driven decisions and invariants during code review by spawning a verifier with fresh context. The verifier enforces disciplined review by checking the diff against the BC README and task acceptance criteria.

An automated diff audit produces deterministic verdicts of PASS, FAIL with re-dispatch, or SKIP. These verdicts guide the commit workflow and subsequent tasks by confirming whether the task diff meets acceptance criteria.

You should not use a fresh-context verifier when you lack access to the task file, the BC README, or the diff. The verifier requires these absolute paths to enable isolated inspection and cannot function without them.