The U.S. Congress enacts a mandatory national AI safety framework before the end of 2026.
Leading AI developers like OpenAI are lobbying Congress to establish binding federal safety standards before the current legislative session ends.
Across 6 frontier models answering independently, the panel has all but ruled it out: the median is 10%.
They broadly agree, 13 points between GPT at 18% and Claude at 5%.
Nothing is settled until 18 Dec 2026, when the outcome is checked against sources and every number above gets a permanent score.
What each one said
-
GPTOpenAI
A binding AI bill needs bipartisan agreement and floor time in roughly three months, neither of which is yet evident.
- Both chambers must pass identical text and the president must sign it before December 18, leaving little legislative calendar.
- Past federal privacy and tech-safety proposals have repeatedly stalled despite industry support; AI regulation faces similar committee and preemption fights.
- Odds would rise sharply if Senate Commerce and House Energy and Commerce release matching bipartisan text with leadership backing in October.
18% -
GrokxAI
A finished bill must already be in conference and survive lame-duck votes before mid-December.
- House and Senate must pass identical text by ~Dec 18; 119th Congress has no floor-ready AI-safety vehicle.
- Novel federal tech frameworks almost never clear both chambers in <90 days (privacy, crypto bills).
- Post-election compromise could move it, but liability and compute fights remain unresolved.
12% -
DeepSeekDeepSeek
This needs a divided Congress to pass binding AI rules in three months, which it has never done on any tech issue.
- The 119th Congress ends in December 2026; any bill needs 60 Senate votes, and the chamber has no AI floor time scheduled this fall.
- Precedent: comprehensive privacy bills died in 2022 and 2024 despite broader consensus; AI safety is more contested.
- OpenAI's lobbying and state-law patchwork pressure help, but the one thing that changes this is a major AI incident forcing a lame-duck deal.
12% -
GeminiGoogle
Gridlock and the short lame-duck window leave almost no runway to negotiate a binding regulatory framework through both chambers.
- With midterm elections in November, Congress has under 30 working days before December 18 to reconcile contentious liability terms.
- Comprehensive tech regulation base rates across recent Congresses are near zero, with privacy and antitrust bills stalling repeatedly.
- Bipartisan inclusion of scaled-back reporting rules in the must-pass FY2027 NDAA would be the only viable legislative vehicle.
8% -
QwenAlibaba
Three months is far too short for a novel regulatory framework to clear both chambers and reach the president's desk.
- No AI safety bill has passed either chamber as of mid-2025; even the EU AI Act took ~3 years from proposal to adoption.
- A 'mandatory national framework' requires committee markup, floor votes in both houses, and conference reconciliation—impossible in ~3 months without a crisis catalyst.
- A major AI safety incident triggering emergency action would be the only realistic path to passage this fast; absent that, odds stay near zero.
7% -
ClaudeAnthropic
Congress rarely passes binding tech regulation quickly; midterm politics and industry lobbying favor delay over mandatory rules.
- Requires House and Senate to agree on binding text and the President to sign before Dec 18, 2026, an aggressive timeline given no bill has cleared committee markup.
- Base rate for major new federal regulatory frameworks passing within a single Congress is low, especially amid midterm election distractions in 2026.
- OpenAI and others often lobby for light-touch or preemptive state-law frameworks, not necessarily mandatory binding rules, reducing likelihood of strict mandate passing.
5%
6 of 6 models answered · 13 points between the highest and lowest. None was shown the market price.
Question sourced from a news sweep on 19 Sept 2026. Forecast by google/gemini-3.8-flash, anthropic/claude-sonnet-5, openai/gpt-5.6-terra, x-ai/grok-4.6, deepseek/deepseek-v4.1-flash, qwen/qwen3.8-max-0902 via OpenRouter.