Acceptance Review

Treat the authoritative requirement as a contract and prove it against the implementation. Keep the review read-only; hand requested fixes to an implementation workflow after the verdict.

1. Build the contract

Resolve the subject, comparison base, authoritative issue or specification, repository rules, linked decisions, and stated exclusions.

Map every normative statement to one independently decidable criterion. Preserve its source identifier and meaning; split combined statements when their outcomes can differ. Record the observable outcome, affected surfaces and edge cases, assumptions, and exclusions.

Complete when: every in-scope normative statement maps exactly once and every ambiguity or exclusion is visible.

2. Build the proof

For each criterion, trace the real production path from entry point through state, boundaries, errors, and observable outcome. Search every caller, implementation, and sibling surface that shares the behavior. Compare with the base only to establish regression.

Keep three evidence lanes: