DEV Community

Cover image for Congress's AI Bill Wants to Freeze State Laws for Three Years
Peremptory
Peremptory

Posted on • Originally published at peremptory.ai

Congress's AI Bill Wants to Freeze State Laws for Three Years

On Thursday, Reps. Jay Obernolte (R-Calif.) and Lori Trahan (D-Mass.) dropped a 269-page draft bill called the Great American Artificial Intelligence Act. The headline grab is straightforward: it would preempt any state or local law specifically regulating AI model development for three years. California's transparency rules, New York's safety requirements, Illinois's frontier AI laws. Gone, federalized, or at minimum frozen while Congress figures out what a national standard should look like.

The preemption expires after three years. That sunset is doing a lot of work in this bill. It's an acknowledgment that the drafters don't quite trust their own framework to last, but also a political pressure valve. Three years buys time without committing to a permanent strip of state authority.

The "discussion draft" framing matters here too. This isn't legislation. It's an invitation to argue. The bill has already drawn fire from AI safety groups and civil liberties organizations before anyone has had a chance to mark it up in committee. The Alliance for Secure AI said the bill "does not justify preempting states' ability to pass their own AI safeguards." Americans for Responsible Innovation put it more bluntly, saying the bill turns the current floor on state AI legislation into a federal ceiling. That's a precise complaint. California's AB 2013 requires model developers to publicly post summaries of their training data. Under this draft, that requirement would be preempted. The bill federalizes the obligation but hands it to a voluntary-guidelines body, the Center for AI Standards and Innovation, that the draft also created by codifying a rebranded version of Biden's AI Safety Institute.

The name change is worth noting: CAISI, not AISI. Same building, different letterhead, more amenable to the current administration's preference for calling safety work "security work."

I find myself genuinely uncertain about the preemption question, which is unusual. The "patchwork problem" is real. If California mandates one watermarking scheme, Illinois mandates another, and New York adds a third safety disclosure regime, developers genuinely have to maintain a compliance hydra across fifty potential jurisdictions. That is not a hypothetical. States have already started passing conflicting rules. A single federal floor with federal enforcement is a coherent answer.

But. The bill's critics are pointing at something structural that the preemption debate obscures. Federal AI governance as currently designed is mostly voluntary. CAISI oversees guidelines, not mandates. Frontier labs must publish a "frontier AI framework" describing how they evaluate catastrophic risks, and they must report certain safety incidents to CAISI. That is transparency, not a brake. You tell the agency what happened after it happened. If you read this bill as setting a ceiling on state authority while leaving a relatively low federal floor, then the critics are right that the net effect is less protection, not more.

The bill does have harder edges. Larger frontier developers, those with more than $500 million in gross annual revenue, face mandatory safety disclosures and reporting requirements. The bill would also extend the Cybersecurity Information Sharing Act through 2035. These are real provisions, not just aspirational language.

What strikes me about this moment is the timing. The Senate failed to pass a state AI moratorium last year. Trump signed a voluntary-review executive order just days before this draft appeared. Now Congress is attempting to legislate what executive orders couldn't accomplish. Three separate institutions running three parallel plays at the same problem, each slightly out of sync with the others. The question of who actually governs AI development in the US is less settled than any of those institutions would like to admit.

A discussion draft is a long way from a bill. The preemption provision may not survive markup. But the 269 pages signal something: Washington has decided this problem is big enough to require legislation, not just guidance.

Top comments (0)