Code Review Is Broken for AI-Generated Code — The Case for Pre-Implementation Governance

Your team's code review process was designed for a world where a developer wrote every line. In that world, a PR with 200 lines meant 200 lines of human judgment. The reviewer's job was to check that judgment: catch bugs, enforce patterns, transfer knowledge. Review velocity matched author velocity. It worked. Now a developer generates 800 lines in an afternoon. The PR is 800 lines of AI output, lightly edited. The reviewer's job hasn't changed. The workload has. Something breaks at scale. This