30MAR

US states legislate as Washington stalls

2 min read

08:00UTC

California advanced three AI-employment bills through committee in late June, including the 'No Robo Bosses Act', though none has reached a floor vote.

← Back to Trump wants Iran's oil; 3,500 Marines land Jump to analysis ↓

ConflictDeveloping

Key takeaway

AI job protections advance only at state level, reaching only workers in states that pass them.

California moved three AI-employment bills through committee in the final days of June. AB 2545, which would make the state's Employment Development Department build an AI worker-impact dataset, cleared Senate Appropriations 9 to 0 on 29 June. SB 947, the 'No Robo Bosses Act', which would curb AI-only hiring and firing decisions, reached the Assembly Judiciary Committee on 25 June. SB 951, a 90-day technological-displacement notice bill, had an Assembly Privacy Committee hearing on 1 July, but none of the three has yet reached a floor vote. ¹

State legislatures keep advancing AI-employment law while the main federal bill has not moved. The only AI job protections gaining ground in the US now sit at state level, reaching only workers who live in those states. California cleared AB 2656 through Senate Labor 5 to 0 in mid-June and moved SB 951 through the Senate 28 to 9 earlier ; New York passed its own hiring-impact bill through both chambers the same month .

Deep Analysis

In plain English

While the US Congress has not passed any national law on AI and jobs, individual states are moving ahead on their own. California is furthest along, with three different bills inching through committee in late June, though none has had a full vote yet. AB 2545 would make a state agency start collecting real data on how AI affects hiring and firing, something the federal government currently does not do. SB 947, nicknamed the 'No Robo Bosses Act', would limit AI making hiring and firing decisions without human involvement. SB 951 would require 90 days' notice before a big AI-driven layoff, longer than the 60 days federal law requires.

Deep Analysis

Root Causes

AB 2545's requirement that the Employment Development Department build an AI worker-impact dataset exists specifically because the federal Bureau of Labor Statistics has never published a comparable series; California is legislating the exact measurement instrument Washington has left absent for three years running, with only the New York Fed's contradictory job-posting study filling the federal gap so far.

None of the three bills has reached a floor vote because each sits in a different chamber's committee structure, Senate Appropriations for AB 2545, Assembly Judiciary for SB 947, Assembly Privacy for SB 951, so their progress depends on three separate committee calendars converging before the legislative session closes, not on a single shared blocker.

What could happen next?

Meaning
California is moving to collect the AI workforce-impact data that no federal agency currently publishes, positioning state administrative data as a possible substitute benchmark for Stanford's contested JOLTS-based estimate (ID:3584).
Risk
With Congress producing no comparable federal vehicle, California's bills risk becoming a patchwork standard that only applies to workers in one state, while national employers structure AI deployment to concentrate the affected roles elsewhere.

Source Landscape

This story draws on neutral-leaning sources

Immediate impact: none of the three bills carries an enforcement mechanism yet, since none has reached a floor vote, so the economic effect in June remains limited to compliance planning by large California employers.

Structurally, AB 2545's data-collection mandate would be the first state-level instrument capable of validating or contradicting Stanford's disputed 34:1 hire-suppression estimate with real EDD administrative data rather than a survey-based extrapolation.

Consensus view: The National Conference of State Legislatures tracks over 30 state-level AI-employment bills in 2026 and notes California's three-bill slate is furthest along procedurally of any state, with AB 2545 alone requiring a public dataset the federal Bureau of Labor Statistics has never built.

Counter-view: The California Chamber of Commerce, which has placed SB 947 on its annual 'job killer' list, argues that state-by-state AI-employment rules create fifty different compliance regimes for national employers, achieving worse outcomes for workers than a single federal standard would.

Key tension: Whether a patchwork of state AI-employment laws is the fastest realistic path to worker protection given federal paralysis, or whether it guarantees the weakest, most litigated version of that protection survives in practice.

Sources:Stanford Digital Economy Lab

Mentions:California →AB 2545 →SB 947 →SB 951 →Bureau of Labor Statistics →AB 2656 →US Congress →Washington →New York State →California State Legislature →

First Reported In

Update #15 · Oracle names AI in its own annual report

Stanford Digital Economy Lab· 1 Jul 2026

Read original →

Causes and effects

This Event

US states legislate as Washington stalls

State legislatures are the only US venue where AI job protections are gaining ground, and they reach only workers who live in those states.

Led to

California eyes 45-day AI notice rule

Committee action on AB 2545, SB 947 and SB 951 continues California's AI-employment legislative push alongside AB 2656.

Occurred 17 Jun 2026

Read story →

California bill sets 90-day AI layoff notice

SB 951's committee progress continues its path after clearing the Senate 28-9.

Occurred 6 Jun 2026

Read story →

States write the AI law Congress won't

Late-June committee action extends the California bill slate's progress reported alongside New York's A9581 passage.

Occurred 10 Jun 2026

Read story →

California binds AI hiring, EU defers

The three bills continue the committee march this beat logged in late June.

Occurred 1 Jul 2026

Read story →

Different Perspectives

Oil market and P&I insurers

Brent cleared $87 intraday only once CENTCOM's blockade became physical rather than declared, even though P&I Clubs had already excluded Hormuz war risk a week earlier on 7 July: capital hedged ahead of enforcement, but prices moved only after it.

UAE reporting

UAE reporting placed the Omani tanker deaths at one seafarer against the International Maritime Agency's count of two, the first time in this war that a Gulf state's casualty figures have diverged from an international monitor's.

Jordan

Iranian strikes reached Jordan again on 14 July as part of the Gulf-wide retaliation for the Hormuz blockade, extending the conflict's geographic footprint to a state with no direct stake in the strait itself.

Bahrain

Bahrain sounded air-raid sirens on 14 July during Iran's Gulf-wide retaliation, the same day CENTCOM's blockade order and fourth night of strikes pushed the conflict's physical reach into the wider Gulf littoral.

Kuwait

Kuwait intercepted Iranian missiles and drones on 14 July as Tehran's blockade retaliation reached Gulf states beyond Iran's immediate shoreline, confirming Kuwaiti airspace now sits inside Iran's retaliatory envelope.

Oman

Oman absorbed the war's first tanker casualties in its own waters on 14 July, with two supertankers disabled and seafarers killed, putting the sultanate's shipping lanes directly in the path of the blockade fight for the first time.