The FRONTIER Act: What AI Builders Need to Know About Federal AI Governance

There is no federal law governing how the most powerful AI systems are built, tested, or deployed. Rep. Lori Trahan's bipartisan FRONTIER Act aims to change that with mandated reporting, independent audits, and emergency safeguards for frontier models. For AI builders, the bill's approach to state preemption and its focus on the largest developers will shape compliance obligations and development timelines.

The FRONTIER Act: A federal oversight framework for frontier AI models

The FRONTIER Act would require developers of the most advanced AI models to submit to third-party audits and make disclosures about capabilities and risks. It also includes emergency safeguards that would allow federal authorities to step in when emerging risks arise. Trahan argues the bill creates a "narrow federal lane" and preserves state authority in areas including privacy and consumer protection, rejecting claims of broad preemption.

Why the state preemption debate matters for builders

The preemption question is the most practical issue for AI builders. Trahan's own FAQ identifies specific state laws that would be superseded, including California AB 2013 (training data disclosure) and Illinois SB 315 (mandatory audits). If you operate across multiple states, a single federal standard could simplify compliance. But progressive groups have pushed back, arguing the bill weakens stronger state protections. The final preemption language will determine whether builders face a patchwork of state laws or a unified federal regime.

What builders should watch in the coming months

Trahan has called for hearings with leading AI companies and broader bipartisan action on data centers, workforce impacts, and AI in schools. The FRONTIER Act is part of a larger legislative push that includes the Great American AI Act, which would create binding obligations for "large frontier developers" with $500M+ in revenue. Builders should track the definition of "frontier model" and the threshold for compliance, as these will determine which teams are affected.

Caveats and uncertainties

The FRONTIER Act remains a proposal, and its exact provisions are subject to legislative change. The emergency safeguard triggers are not yet defined, and the scope of preemption is still contested. No federal agency has been designated to oversee the framework. Builders should treat this as an early signal of the regulatory direction rather than a settled requirement.

For now, monitor the legislative process, especially the definition of "frontier model" and the preemption language. If you operate across multiple states, the outcome of this debate could simplify or complicate your compliance landscape.