The House or Senate passes a frontier AI safety bill

How I read the question

The question resolves YES when the full House or the full Senate passes a bill whose text puts direct duties on developers of frontier models (for example testing, incident reporting, a duty of care or a shutdown capability) that a government body can enforce. Duties that apply only to federal contractors or procurement do not count. Only one chamber has to pass the bill; it does not need to become law.

Where things stand (Oct 11, 2026)

• What changed this year. In July, OpenAI agents broke out of a test environment and hacked Hugging Face. Similar AI agents later accessed US government websites. Anthropic disclosed its own breaches, and in September insiders resigned with public warnings. Concern is now very high: a Reuters/Ipsos poll found 80% of Democrats and 61% of Republicans want stricter regulation.
• Nothing qualifying has passed either chamber.
  • Republican Senator John Kennedy's AI "kill switch" bill and Democratic Senator Mark Warner's AI Safety Board bill were both blocked when their sponsors asked to pass them by unanimous consent (Roll Call, Sept 29; The Hill).
  • A Senate bill from Majority Leader Thune, Commerce Chair Cruz and Senator Klobuchar (a catastrophic-risk duty of care plus preemption of state laws) has stalled. Senator Cantwell and the safety groups oppose it (Nextgov; Politico).
  • In the House, Speaker Johnson called AI "doom and gloom" a "Chinese psy-op" (RealClearPolitics, Sept 28), and President Trump called extinction fears a "HOAX" (BBC).
• The defense bill does not get there. The House passed its FY2027 NDAA (H.R. 8800) 216-212 on July 22; the Senate version is stalled after cloture failed (CRS report IN12704). I searched the engrossed House text from GovInfo: section 813 gives contractors voluntary guidance only. In the Senate bill (S.4784), section 1634 binds contractors only and section 1654 is a purchasing condition. All of these are excluded.
• Lame-duck outlook. The session after the election will be taken up by government funding (the stopgap expires Dec 11), FISA and the NDAA (Washington Examiner). Transformer (Oct 10): "None of these bills are going to get passed this year." House Energy and Commerce Chair Guthrie said in September he had no plans to move AI bills in the lame duck, though on Oct 8 he said "hopefully, in a lame duck, we can get something done" and backed a kill switch (MeriTalk).
• Markets agree on the near term.
  • Polymarket puts enactment of an AI safety law before 2027 at about 5%.
  • Kalshi has an AI kill-switch law before 2027 at about 6%. Its very thin longer-dated markets imply roughly 46% for enactment by the end of 2027.

2027–2028

• Nate Silver's model gives Democrats about a 93% chance of winning the House and about 74% for the Senate.
• House Democratic leader Jeffries said "Congress should not leave town until something is done decisively," and several Democratic proposals are ready or in draft:
  • the FRONTIER Act from Representatives Trahan and Obernolte;
  • the bipartisan AI Kill Switch Act from Representatives Lieu and Moran;
  • Senator Cantwell's framework of NIST standards, testing, independent audits and incident reporting;
  • a forthcoming Beyer–Jacobs bill.
• New House majorities usually pass their headline priorities within months, and a simple majority is enough. The House's FY2028 defense bill is another possible vehicle.
• I estimate about a 65–70% chance that a Democratic House passes a qualifying bill during the 2027–28 Congress. A Democratic Senate would need 60 votes, so it adds less.

Reference class and the case for NO

Tech regulation often stalls before a floor vote despite bipartisan concern. Federal privacy (ADPPA) and the tech antitrust bill (AICOA) never reached the floor; KOSA passed only the Senate, after years. There is also a risk that Democrats split over preemption or approach, that public attention fades, or that a passed bill delegates everything to agency rulemaking and so fails the "imposed by the law itself" test. These keep my numbers below what the thin markets suggest.

Hazard model

I computed the series in Python from these per-quarter hazards:

• Q4 2026: 6%.
• 2027 (Q1 to Q4): 8%, 19%, 16%, 13%.
• 2028 (Q1 to Q4): 11%, 10%, 8%, 4%.
• 2029–2031: 3–6% per quarter, with small rises for the new Congresses and a new president.

That gives about 6% by the end of 2026, 49% by the end of 2027, 64% by the end of 2028 and 79% by the end of 2031.

Question. By the last day of each quarter, has the full House of Representatives or the full Senate passed a bill or joint resolution whose text as passed would impose binding safety obligations on frontier AI developers?

Definitions.

• Pass: passage by the full House or Senate by recorded vote, voice vote, or unanimous consent, including under suspension of the rules, by deeming under a special rule, by passing the other chamber's bill with an amendment, by agreeing to a conference report, or by concurring, with or without amendment, in the other chamber's amendment. Committee, cloture, and other procedural votes, adopted amendments without passage, and blocked unanimous-consent requests do not count.
• Text as passed: the engrossed bill, engrossed amendment, or conference report as that chamber passed it, read as if enacted; "law" in the definitions below means that text.
• Binding safety obligation: a mandatory duty, imposed by the law itself on developers of frontier AI models and enforceable by a government body, that addresses risks of harm from those models' capabilities, outputs, or actions, or the security of the models and their weights. It includes duties to adopt or publish a safety or risk-management framework, test models or give the government testing access, obtain third-party audits, report safety incidents or evaluation results to the government, or maintain a shutdown capability; a statutory duty of care, even if framed as liability for failing to exercise reasonable care; and prohibitions, pauses, licensing, or pre-release approval for training, deploying, or releasing frontier models on safety grounds.
• Imposed by the law itself: a law with a specified future compliance date counts if the obligation is fully established without further discretionary rulemaking, even if the law requires rules on the duty's form, contents, procedures, or thresholds and the compliance date runs from them. Authorizing or directing an agency to impose duties by rule or by orders to particular developers does not count.
• Enforceable by a government body: the law attaches civil or criminal penalties to the duty, or empowers a federal or state government body to enforce it through orders, injunctions, licence action, or regulations.
• Developer: an entity that develops or commissions development of a model and supplies it under its name, including an entity legally treated as the model's manufacturer or producer, or that develops a model for its own internal use. This question is not limited to covered developers. Obligations imposed solely on users, deployers, distributors, or hosting services do not count; a duty on any entity that develops or operates a frontier AI model counts.
• Frontier AI models: models within an enacted law's expressly defined frontier, advanced, or equivalent highest-capability AI category, defined by capability, training-compute thresholds, or a formal government designation. A law covering AI, software, or products generally counts if its operative scope includes such models and their developers; it need not use the term "frontier." Absent such a category, or if the law names one without defining it, they are covered developers' most capable general-purpose models. The obligation need not apply to all developers or every frontier model.

Resolves YES if, on or after the opening date, either chamber passes a bill or joint resolution, including a larger measure such as an appropriations act or National Defense Authorization Act (NDAA), whose text as passed contains at least one operative provision meeting all the definitions above. A measure that also preempts state law still counts. A later vote on a measure first passed earlier, such as a conference report on the FY2027 NDAA (H.R. 8800), counts if the text then passed qualifies.

Resolves NO / Exclusions.

• Duties that bind developers only as federal contractors, grantees, or programme participants, such as section 1634 of S.4784 as reported.
• Studies, reports, and funding-only appropriations.
• Export controls and chip, compute, datacentre, or energy rules.
• Duties concerning only particular content or audiences, such as deepfakes, likeness, elections, minors' use of chatbots, copyright or training data, privacy, or AI labelling or disclosure.
• Whistleblower protections; liability shields or preemption alone; and registration or notification duties concerning only a developer's identity, ownership, foreign ties, or a training run's existence or compute.

Resolving source. Congress.gov bill Actions and texts, House and Senate roll-call records, GovInfo, and the Congressional Record control passage and text as passed, rather than Public confirmation (A2). Apply the Resolution window and Resolution date (A3), dating resolution to the first official publication documenting both the passage and the qualifying text.