# Review and verify acceptance

Practices: review-invariants, verify-release-path, accept-with-evidence.

Read the brief, acceptance, revision and affected paths. Explain the invariant and inspect callers, stored state, compatibility, permissions, boundaries and failure behavior. Verify factual claims against the implementation.

For a concrete defect, report trigger, actual result, expected result, evidence and affected scope. Distinguish blockers, nonblocking findings and unknowns. Record the revision reviewed.

If successive rounds find more defects in the same block, widen discovery to the invariant and all affected paths. A root-cause fix should carry a meaningful regression check; avoid tests that merely assert mocks or hide the changed layer.

Verify SQL and migrations against a representative disposable database using the actual apply tool. Verify packaged behavior through the package when that path matters. State which checks were run and which require another environment. Production execution needs its existing authority.

Return: verdict, blocking findings, evidence, checks not run, remaining uncertainty and acceptance state. Do not describe findings yield as detection recall, or a merge as a deployed result.