Meta Built the System Every Engineering Team Needs: Risk-Calibrated Code Review Automation

AI-assisted coding at Meta grew lines per diff by 105.9% year over year. Agentic AI drove over 80% of that growth. The problem: timely review share declined. Code is being generated faster than humans can read it. Meta's answer is RADAR, and every team scaling AI-assisted development should study it.

RADAR is a risk-stratified automation layer for code review. Instead of treating every diff the same, it scores changes on risk dimensions and routes low-risk diffs through automated approval while escalating high-risk ones to human reviewers. This isn't just a faster rubber stamp. It's an admission that the old model of "every line gets a human set of eyes" doesn't work when your codebase is 80% machine-written.

The math is stark. If your team doubled code output but kept the same number of reviewers, review latency doubled. If agentic AI is writing 80% of that code, your humans are spending most of their review time reading machine output. That's an expensive use of senior engineer hours. And those hours aren't elastic. You can't just hire more reviewers fast enough.

What I find interesting about RADAR's approach is the risk calibration piece. Not all code changes are equal. A CSS color change carries different risk than a database migration. A utility function refactor is different from an auth flow modification. Rating risk computationally and routing accordingly is something every team can implement, even without Meta's infrastructure budget. You could start with file-path heuristics: changes to /auth, /payments, or /migrations get mandatory human review. Everything else gets a lighter touch.

The bigger implication: we need to stop pretending code review scales linearly with code output. It doesn't. The review bottleneck is the next thing that breaks as AI-generated code volume keeps climbing. Meta built the first production system to address it. If you're running a team with AI coding tools and your PR queue is growing, RADAR's approach is the template.

Start simple. Tag your high-risk directories. Route low-risk changes through automated checks. Save your senior engineers' review bandwidth for the diffs that actually need human judgment.

[Source: arXiv]