AI code review and AI code verification are often confused but serve fundamentally different purposes. Code review reads a PR diff and posts non-deterministic comments about potential issues, inferring intent from the code itself. Code verification checks the implementation against a human-approved spec with acceptance criteria, producing deterministic pass/fail results with an audit trail. The key differentiators are: review is intent-blind while verification knows the approved intent upfront; review output varies between runs while verification is repeatable; and review produces comments while verification produces evidence-backed verdicts. Both are needed — review handles breadth and signal across many PRs, while verification confirms that what was agreed to build is what actually got built. Aviator Verify is presented as a tool implementing this verification approach.