Washington and California Are Building Different AI Rules

1 Two documents, one collision

The White House's March 2026 national AI legislative framework and Governor Newsom's September 18 executive order describe the same technology from opposite premises. The White House release warns a patchwork of state laws would undermine innovation; the California governor's office calls the federal response a failure and the state's framework the model for a national baseline. Both are positions, not settled law — the federal document is proposals Congress would need to pass, while the California order is executive action built on laws already enacted.

2 What Washington has actually proposed

According to the White House release, the framework addresses six objectives — children's protection, community safeguards, intellectual property, free speech, innovation, and workforce development. On energy, it states ratepayers should not foot the bill for data centers and calls on Congress to streamline permitting so data centers can generate power on site. Nearly all of it is aspirational: the release asks Congress to turn the framework into legislation and seeks preemption of state approaches like California's.

3 What California has actually enacted

California's record is a stack of signed instruments. Per the governor's office, SB 53 of 2025 requires frontier AI developers to publish safety frameworks and report critical safety incidents. In 2026 the state enacted SB 813, certifying independent verification organizations, and AB 1405, creating a registry of AI auditors with independence standards. The September 18 order directs accelerated implementation of both and convenes experts to deliver recommendations within two months — explicitly proposals under consideration.

4 The kill switch, precisely stated

The kill switch does not exist as a requirement. The order directs the advancement of its creation — it would require companies to develop an emergency shutoff for frontier models, with efficacy verified by an independent verification organization — and its entry into state law depends on future legislative action. The order also proposes updating critical-incident definitions to include loss-of-control incidents, citing the recent Hugging Face attack as context.

5 Recommendations versus requirements

The two-track difference is structural. Washington's framework asks Congress to act and describes a uniform policy that would displace state regimes; nothing in it is enacted. California combines statutes that bind developers now with a proposal pipeline — and its own order asks Congress and the President to adopt the state framework as a floor. Congressional action could override parts of California's approach; absent that, the state rules stand while the federal items remain proposals.

6 What to watch

Two events would change the sorting: congressional action on the federal framework, and California's expert recommendations due within two months of September 18, which would move the kill switch toward legislative language — or not.

7 Bottom line

Washington's framework is a proposal seeking national uniformity; California combines enacted laws with an executive order whose most-cited feature, the kill switch, is a recommendation. Only one side has signed instruments currently binding anyone.