Artificial Intelligence Policy Tracker

AI incident ·

Reportedly AI-Assisted Boies Schiller Brief in Bixler v. Church of Scientology Allegedly Contained Material Citation Errors and a Nonexistent Case

1 news report Snapshot 7 Sep 2026
On this page 6 sections

In brief

An AI system built by Generative Ai Developers and deployed by Lawyers, Law Firms and 2 others allegedly harmed Plaintiffs In Bixler V. Church Of Scientology International, Judicial Integrity and 5 others.

Risk domain
Not classified
Occurred
Coverage
1 reportSep 2025

What happened

Boies Schiller Flexner filed a respondents' brief in Bixler v. Church of Scientology International that was reportedly prepared with AI assistance and allegedly contained material citation errors. Opposing counsel reportedly identified mischaracterized and mistitled authorities, including one nonexistent case. Partner John Kucera accepted responsibility for failing to verify the citations and sought to replace the brief; the court denied that request and later considered monetary sanctions.

Laws on record for this risk area

No instrument on record yet covers this risk area where it happened. See the open queue.

Matched from the record's risk category and country to the instruments in effect recorded here: a law listed covers the area, which is not a finding that it applies to this incident. A reviewer can correct the match in the repository (data/external/incident_overrides.yaml).

News reports (1)

Titles link to the original publisher; report text is not reproduced here.

Who was involved

Alleged developer
Generative Ai Developers
Alleged harmed party
Plaintiffs In Bixler V. Church Of Scientology International, Judicial Integrity, Epistemic Integrity, Clients Of Lawyers, Church Of Scientology International, Church Of Scientology Celebrity Centre International, California Court Of Appeal Second Appellate District

Classification (MIT AI Risk Repository taxonomy)

Risk domain
—
Risk subdomain
—
Causal entity
—
Intent
—
Timing
—
Harm level
—
Sectors
—
Countries
—

Source record: incident #1555 on the AI Incident Database · all 1 report