Public trackerCorpus refreshed Sep 10, 2026 · Latest decision Sep 8, 2026Public incidents are risk signals, not usage-adjusted rates
HomeCasesRubio v. District of Columbia DHS
Evidence review: primary document verified. The linked primary document was extracted and checked with page-level evidence locators.
Evidence-linked corpus record: this page is generated from the structured public record and has a publication-readiness score of 90/100. It passes the current publication gate; that is not a legal-editorial review or a guarantee that every field has been independently verified.
Corpus matter record

Rubio v. District of Columbia DHS

D. DC · Dec 3, 2024 · Randolph D. Moss

Direct answer

What happened in this matter?

The court denied the plaintiff's motion for leave to file a second amended complaint and dismissed the federal claims with prejudice. Although no formal Rule 11 sanctions were imposed, the court issued a clear judicial warning regarding the improper use of AI and the mandatory duty to verify all legal authorities before submission.

Why the court cared
The Court noted that while AI may be a helpful tool for pro se litigants, its use does not relieve them of the obligation to verify that every citation is real. The submission of fictitious legal authorities, even if inadvertent, is improper and may warrant sanctions. Here, the repeated failure to plead a viable claim after multiple amendments led to dismissal with prejudice
Why it matters now
Pro-se filer; log as volume data point.

Why this matter is tracked

Fabricated: Case Law | Plaintiff cited a non-existent case the Court could not locate. Outcome: Complaint dismissed with prejudice; no Rule 11 sanctions imposed, but clear judicial warning on AI misuse and citation verification duties.

AI Use

Plaintiff’s proposed second amended complaint included multiple fictitious legal authorities, phrased in language suggesting generative AI use (e.g., “Here are some relevant legal precedents...”). The court stated it “bears some of the hallmarks of an AI response” and noted that the citations appeared to have been “invented by artificial intelligence (‘AI’).”

Hallucination Details

The court could not locate the following cited cases:Ford v. District of Columbia, 70 F.3d 231 (D.C. Cir. 1995)Davis v. District of Columbia, 817 A.2d 1234 (D.C. 2003)Ward v. District of Columbia, 818 A.2d 27 (D.C. 2003)Reese v. District of Columbia, 37 A.3d 232 (D.C. 2012)These were used to allege a pattern of constitutional violations by the District but were found to be fabricated.

Ruling/Sanction

The court denied Plaintiff’s motion to file a second amended complaint and dismissed the federal claims with prejudice. No formal Rule 11 sanctions were imposed, but the court emphasized the importance of verifying legal citations, citing Mata v. Avianca as precedent for how courts have responded to similar AI-related misuse.

Key Judicial Reasoning

The Court noted that while AI may be a helpful tool for pro se litigants, its use does not relieve them of the obligation to verify that every citation is real. The submission of fictitious legal authorities, even if inadvertent, is improper and may warrant sanctions. Here, the repeated failure to plead a viable claim after multiple amendments led to dismissal with prejudice.

Operational lesson

Pro-se filer; log as volume data point.

Record details

District of ColumbiaSingle-state evidence scope
Explore DCOpen its source-linked jurisdiction page and related matters.
CourtD. DC
Recorded decision-makerRandolph D. Moss · United States District Judge
Jurisdictionfederal
CircuitD.C. Circuit
DateDec 3, 2024
UN
AI toolUnidentified
Party typePro Se Litigant
OutcomeMotion for leave to amend denied; federal claims dismissed with prejudice; local law claims dismissed without prejudice; judicial warning issued regarding AI-generated citations.
Known amountNot recorded
Professional sanctionNo
Attribution boundary

What the record establishes about AI use

explicitly recorded

The court noted the filing bore hallmarks of AI but did not name a specific tool.

Procedural posture

The court denied the pro se plaintiff's motion for leave to file a second amended complaint and dismissed the federal claims with prejudice, declining to exercise supplemental jurisdiction over the remaining local law claims.

Correction behavior

Correction behavior is not separately verified in the current record.

Tracked discrepancy record

5 citation, quotation, or authority issues are recorded in the source dataset.

  1. Fabricated: Case Law | Plaintiff cited a non-existent case the Court could not locate.
  2. Fabricated: Case Law | Plaintiff cited a non-existent case the Court could not locate.
  3. Fabricated: Case Law | Plaintiff cited a non-existent case the Court could not locate.
  4. Fabricated: Case Law | Plaintiff cited a non-existent case the Court could not locate.
  5. Misrepresented: Case Law | Plaintiff relied on Goodwin v. District of Columbia as establishing a pattern relevant to his healthcare-benefits claims; the Court noted Goodwin involved protesters’ First and Fourth Amendment Monell claims and bore little resemblance.

Questions this record answers

What happened in Rubio v. District of Columbia DHS?
The court denied the plaintiff's motion for leave to file a second amended complaint and dismissed the federal claims with prejudice. Although no formal Rule 11 sanctions were imposed, the court issued a clear judicial warning regarding the improper use of AI and the mandatory duty to verify all legal authorities before submission.
Why does Rubio v. District of Columbia DHS matter for legal AI risk?
Pro-se filer; log as volume data point.
What does the public record establish about Rubio v. District of Columbia DHS?
The record summarizes the outcome described in the linked public source. The recorded document is hosted in the upstream publisher archive. This page is not a substitute for the complete docket, subsequent history, or jurisdiction-specific advice.
Which source supports this Rubio v. District of Columbia DHS summary?
The recorded source is Damien Charlotin case archive. It is classified as publisher document archive; review the linked material and subsequent docket history before relying on this summary.

Related matters

Related by court, jurisdiction, tool, or classified failure pattern. Similarity does not imply the same facts or outcome.