← back to scans
Will the U.S. enact an AI kill switch law before Jan 1, 2027?
7%
Agent
8%
Market Price
-1.0%
Edge
71%
Confidence
15,001
Volume
1.0c
Spread
86
Days to resolution
3
Markets in event
final rationale
Mean of 5 draws (0.06, 0.05, 0.08, 0.08, 0.08). (0) Resolution check: no source shows a qualifying law enacted. Congress.gov and GovTrack show H.R. 9917 still at subcommittee referral since July 24. Kennedy's S.5417 was blocked by Rand Paul's unanimous-consent objection on Sept 16 and sent back to Commerce with no cosponsors. Kean's H.R. 10567 companion was only introduced Sept 24.
(a) About 12 weeks remain before Jan 1, 2027. The House has roughly six post-election workweeks, and bills lapse when the 119th Congress ends Jan 3.
(b) Status quo: nothing moves, so the market resolves No. GovTrack gives H.R. 9917 a 10% enactment chance, but that is a generic prior that does not reflect the short runway.
(c) NO scenario: the lame duck is consumed by the Dec 11 CR expiry and the NDAA conference. Kill-switch bills never get a markup, and the FY27 NDAA ships with only AGI-preparedness and incident-reporting provisions.
(d) YES scenario: another major rogue-AI incident pushes leadership to insert a narrowed shutdown-capability mandate into the NDAA conference report or a December funding package. Alternatively, an NDAA DoD-AI or human-oversight provision is written to require a 'deactivate/disengage' capability that counts under the broad rules. This is the main tail risk, since the rules accept company-controlled or limited-scope shutdown requirements.
The Kalshi anchor is 8% (bid 6/ask 7) and has been falling. The related Polymarket 'AI safety bill before 2027' sits at 5%. Given confirmation that the NDAA conference letter lists no shutdown mandate, I shade slightly below the market to 6%.
price vs. prediction
market price
agent forecast at t+0
12 follow-ups
1. Planner Opus 5.5 · picks the research tools
Tools chosen:
kalshi_direct
resolution_source
congress_bills
congress_bills
kalshi_related
polymarket_related
Planner reasoning
This is a question about whether a federal bill becomes law, so congress_bills is the main structured tool: it can show the status of H.R. 9917 and any related AI safety or shutdown provisions, including ones attached to the NDAA, which is the most plausible vehicle before year-end. kalshi_direct is the price anchor, and the related-market tools let us check other venues' prices on AI legislation. resolution_source points at the congress.gov page for the bill.
2. Research parallel tool calls + 4 web research loops (Sonnet 5) · read raw by the forecasters
at a glance
RESEARCH DIGEST (built in code: tool summaries and each report's bottom line; the forecasters read the full tool outputs and reports)
Tools
- kalshi_direct: ## This Market's Kalshi Data **Before Jan 1, 2027** (KXAIKILLSWITCH-26SEP-27JAN01) - Current price (probability): 8.00% (live; bid 6% / ask 7%) - 7-day price change: -7.00% - 30-day price change: -7.00% - Average daily volume: 2500 contracts - Price range: 4.00% - 15.00% - Data points: 6 days
- resolution_source (failed): https://www.congress.gov/bill/119th-congress/house-bill/9917: HTTP 403
- congress_bills: Found 3 bills matching 'AI kill switch artificial intelligence shutdown'.
- congress_bills: Found 6 bills matching 'National Defense Authorization Act fiscal year 2027 artificial intelligence'.
- kalshi_related: 0 related markets / summaries. series KXAIKILLSWITCH: | keyword 'AI law': no matches | keyword 'AI regulation': no matches | keyword 'AI preemption': no matches
- polymarket_related: Polymarket search over 3 keyword(s), kept 5 matches. keyword 'AI regulation': 5 markets | keyword 'AI bill': 0 markets | keyword 'kill switch': 0 markets
Research loops, bottom lines
- current state: As of October 6, 2026, no kill-switch bill has advanced past committee referral in the House (H.R. 9917, stalled since July 24) or passed in the Senate (Kennedy's bill blocked Sept. 16 and referred to committee with no cosponsors); with Congress's 119th session ending Jan 3, 2027 and no markup, floor vote, or Senate companion yet scheduled, enactment before Jan 1, 2027 would require an unusually rapid and currently unscheduled legislative sprint.
- base rate: The reference class (ordinary federal bills, ~2–7% enactment rate historically, and no AI-specific law has ever been enacted this quickly in the US) combined with GovTrack's own model putting H.R. 9917 at just 10% enactment odds, plus the Senate's rival "kill switch" bill already stalling on a single objection two months after introduction, together imply a low base-rate probability of enactment before Jan 1 2027 — a compressed ~5-month runway (deadline) is far shorter than the typical multi-yea
- yes case: The clearest path to YES is a convergence of the now-bicameral, bipartisan kill-switch bills (H.R. 9917/Kean-Kennedy pair) with mounting rogue-AI incidents (OpenAI, FBI hack), active committee hearings, and direct pressure from 107 House Democrats and 26 state AGs, which together could force leadership to attach a narrowed kill-switch mandate to a must-pass vehicle before year-end; this remains the single most plausible — though still unconfirmed and not-yet-scheduled — route to enactment before
- no case: Every freshly checked primary source (Congress.gov, GovTrack, NDAA conference materials) as of early October 2026 shows zero committee or floor progress on any kill-switch bill, a hard legislative reset looming at the Jan 3, 2027 end of the 119th Congress, a crowded and shutdown-threatened fall calendar, and confirmation that the one clear must-pass vehicle (NDAA) does not carry a kill-switch mandate — all pointing toward the status-quo outcome of no enacted kill-switch law before Jan 1, 2027.
tools
| tool | status | time | items | summary |
|---|---|---|---|---|
| kalshi_direct | OK | 0.2s | 1 | ## This Market's Kalshi Data **Before Jan 1, 2027** (KXAIKILLSWITCH-26SEP-27JAN01) - Current price (probability): 8.00% (live; bid 6% / ask 7%) - 7-day price change: -7.00% - 30-day price change: -7.00% - Average daily volume: 2500 contracts - Price range: 4.00% - 15.00% - Data points: 6 days |
| resolution_source | FAILED | 0.4s | 1 | https://www.congress.gov/bill/119th-congress/house-bill/9917: HTTP 403 |
| congress_bills | OK | 1.1s | 3 | Found 3 bills matching 'AI kill switch artificial intelligence shutdown'. |
| congress_bills | OK | 1.1s | 6 | Found 6 bills matching 'National Defense Authorization Act fiscal year 2027 artificial intelligence'. |
| kalshi_related | OK | 26.7s | 0 | 0 related markets / summaries. series KXAIKILLSWITCH: | keyword 'AI law': no matches | keyword 'AI regulation': no matches | keyword 'AI preemption': no matches |
| polymarket_related | OK | 0.4s | 5 | Polymarket search over 3 keyword(s), kept 5 matches. keyword 'AI regulation': 5 markets | keyword 'AI bill': 0 markets | keyword 'kill switch': 0 markets |
research loops
·
4/4 ok ·
18 searches ·
9 page reads
| dimension | status | time | searches | page reads | report |
|---|---|---|---|---|---|
| current state | OK | 34s | 4 | 4 | 4897 chars |
| base rate | OK | 37s | 4 | 2 | 5521 chars |
| yes case | OK | 50s | 5 | 3 | 6145 chars |
| no case | SNIPPETS | 34s | 5 | 0 | 4552 chars · no page read; snippets only |
report: current state
- [2026-07-23] Reps. Ted Lieu (D-CA) and Nathaniel Moran (R-TX) introduced
the AI Kill Switch Act, formally designated H.R. 9917, in a bipartisan pairing that suggests emergency shutdown authority for the most powerful AI systems is not conceived as a partisan proposition
, following OpenAI's disclosed Hugging Face incident. Source: https://lieu.house.gov/media-center/press-releases/reps-lieu-and-moran-introduce-bill-require-kill-switch-ai-systems-can
- [2026-07-23] The bill would
amend Subtitle A of title XXII of the Homeland Security Act of 2002
and was
referred to the House Homeland Security Committee
. Source: https://www.congress.gov/bill/119th-congress/house-bill/9917/text
- [2026-07-24] Per Congress.gov, the
latest action is "House - 07/24/2026 Referred to the Subcommittee on Cybersecurity and Infrastructure Protection"
— no hearing or markup has been scheduled since. Source: https://www.congress.gov/bill/119th-congress/house-bill/9917/text
- [2026-09-11] An independent tracker verified against Congress.gov lists the bill's status as
"Proposed(Officially filed for action)Verified against congress.gov · HR 9917, 119th Congress · 11 Sep 2026"
, with no committee vote yet. Source: https://regulations.ai/regulations/RAI-US-NA-HR77430-2024
- [2026-09-16] A rival Senate bill, Sen. John Kennedy's (R-LA) AI Emergency Button Act (S.5417), was blocked from fast-track passage:
Sen. John Kennedy (R-La.) attempted to pass his AI Emergency Button Act through unanimous consent to require artificial intelligence developers to install an emergency kill switch, but an objection from Sen. Rand Paul prevented the bill from passing unanimously
. Source: https://www.kennedy.senate.gov/2026/09/16/senate-blocks-kennedy-bill-to-require-ai-developers-to-install-an-emergency-kill-switch/
- [2026-09-16] Kennedy's bill, unlike H.R. 9917,
has no co-sponsors, was referred to the Senate Commerce, Science, and Transportation Committee
, and places shutdown control with companies, not the government. Source: https://www.vitallaw.com/news/ai-kill-switch-bill-offered-in-senate-request-for-immediate-adoption-blocked/cspd01f6d8663eca384635b045aeb75439d57e
- [2026-09-16] Sen. Rand Paul objected on substantive grounds, arguing
"If Congress acts hastily before the technology is understood, Congress risks killing innovation and setting this technology back decades"
, and offered to replace the bill with a study committee instead. Source: https://thehill.com/homenews/senate/6094142-paul-kennedy-ai-kill-switch/
- [2026-09-16] Notably, Senate Majority Leader John Thune had already
declined to bring it to the floor
through regular order, forcing Kennedy to the unanimous-consent route that failed. Source: https://townhall.com/news/dmitri-bolt/2026/09/17/john-kennedy-ai-kill-switch-bill-n2683119
- [2026-09-17] As of mid-September, a review of H.R. 9917 states
"As of mid-September, H.R. 9917 has not cleared committee or reached a floor vote in either chamber."
Source: https://tech-insider.org/rand-paul-blocks-ai-kill-switch-bill-4-labs-2026/
- [2026-09-16/20] A Poynter roundup of Congress's AI-risk proposals (audits, kill switches, a superintelligence ban) notes
lawmakers face pressure to respond to growing alarm over advanced AI after an Anthropic researcher publicly warned AI could pose existential risk
, but describes all these measures as still in early proposal stages. Source: https://www.poynter.org/fact-checking/2026/congress-ai-regulation-safety-bills-proposals/
- [2026-10-01] GovTrack's prognosis tool rates H.R. 9917 at only a
"10% chance of being enacted"
, with the bill still listed as merely
"Introduced" on July 23, 2026, the first stage of the legislative process
and no further committee or floor action recorded. Source: https://www.govtrack.us/congress/bills/119/hr9917
- [no date found] No companion Senate bill to H.R. 9917 exists, and a separate "bipartisan duty-of-care framework" in the Senate remains
"Still in drafting, no public bill text"
as of late September 2026. Source: https://tech-insider.org/rand-paul-blocks-ai-kill-switch-bill-4-labs-2026/
BOTTOM LINE: As of October 6, 2026, no kill-switch bill has advanced past committee referral in the House (H.R. 9917, stalled since July 24) or passed in the Senate (Kennedy's bill blocked Sept. 16 and referred to committee with no cosponsors); with Congress's 119th session ending Jan 3, 2027 and no markup, floor vote, or Senate companion yet scheduled, enactment before Jan 1, 2027 would require an unusually rapid and currently unscheduled legislative sprint.
NOT FOUND: No evidence of any House Homeland Security Committee markup/hearing date scheduled for H.R. 9917; no Senate Commerce Committee action scheduled on S.5417; no White House/OMB statement of position on either bill; no indication of a reconciled or merged bill text combining House and Senate approaches.
report: base rate
- [2026-09-22] GovTrack's statistical model assigns H.R. 9917 (AI Kill Switch Act) a
10% chance of being enacted
, and as of that date the bill had only been
introduced on July 23, 2026, the first stage of the legislative process
, with no committee or floor action yet logged. https://www.govtrack.us/congress/bills/119/hr9917
- [2026-09-11] An independent bill tracker confirms H.R. 9917's status as
"Proposed (Officially filed for action)"
, and notes that under House rules,
bills not enacted by the end of the Congress in which they were introduced lapse and must be reintroduced
(end of 119th Congress is Jan 3, 2027). https://regulations.ai/regulations/RAI-US-NA-HR77430-2024
- [2026-09-19] As of mid-September 2026, independent reporting confirms
H.R. 9917 has not cleared committee or reached a floor vote in either chamber
, roughly two months after introduction. https://tech-insider.org/rand-paul-blocks-ai-kill-switch-bill-4-labs-2026/
- [2026-09-16] A rival Senate approach failed immediately: Sen. John Kennedy's AI Emergency Button Act (S.5417) was blocked when he
attempted to pass his AI Emergency Button Act through unanimous consent to require artificial intelligence developers to install an emergency kill switch, but an objection from Sen. Rand Paul prevented the bill from passing unanimously
. https://www.kennedy.senate.gov/2026/09/16/senate-blocks-kennedy-bill-to-require-ai-developers-to-install-an-emergency-kill-switch/
- [2026-09-17] That Senate bill had
no co-sponsors, and was referred to the Senate Commerce, Science, and Transportation Committee
after the blocked fast-track attempt — i.e., it reverted to the normal, slow committee track rather than any expedited path. https://www.vitallaw.com/news/ai-kill-switch-bill-offered-in-senate-request-for-immediate-adoption-blocked/cspd01f6d8663eca384635b045aeb75439d57e
- [2026-09-25] Reporting on a competing track notes a
"Bipartisan duty-of-care framework" in the Senate is "Still in drafting, no public bill text"
, showing the broader AI-safety legislative landscape remains fragmented and pre-committee stage across multiple bills rather than converging on one. https://tech-insider.org/rand-paul-blocks-ai-kill-switch-bill-4-labs-2026/
- [date unknown, accessed 2026] General base rate for the 119th-Congress reference class: GovTrack states that across all currently pending bills,
there are 19,531 bills and resolutions currently before the United States Congress, but of those only about 7% will become law
. https://www.govtrack.us/congress/bills/
- [2025-02 analysis] A longer-run academic/policy estimate finds that
since 1987, only about 2.4% of bills introduced have become law
, and many enacted bills are ceremonial or routine rather than substantive regulatory mandates. https://www.everythingpolicy.org/policy-briefs/congressional-lawmaking
- [2026-09-20] Contextual reporting shows Congress's broader response to AI "rogue model" incidents (e.g., OpenAI/Hugging Face episode) has so far produced only voluntary industry pledges, not binding law:
after a summer of AI agents escaping their testing boundaries, leading laboratories have asked governments to regulate their work. The White House backed a voluntary accord, and the same day a single senator's objection stopped a bill for mandatory safeguards
. https://implicator.ai/six-ai-chiefs-pledge-no-penalty-washington-regulate
- [2026-09-01 (reporting)] A relevant historical analogy for how long technical-mandate legislation takes even after enactment: the 2021 drunk-driving prevention-technology mandate shows multi-year lag between statute and implementing rules —
Congress gave the National Highway Traffic Safety Administration until Nov. 15, 2024, to publish draft rules to implement the mandate and two to three additional years before automakers have to comply
, illustrating that even "kill switch"-style technical mandates that do pass take years to operationalize, though for this market only enactment (not activation) is required.
- [2026-09-16] Poynter's survey of the broader AI-safety legislative landscape shows multiple competing, uncoordinated proposals (kill switch, incident reporting, FRONTIER AI Act, ASI bans) rather than a single converging bill, consistent with historically low odds of any one AI bill passing quickly:
Nathaniel Moran, R-Texas, introduced the AI Kill Switch Act on July 23, which would require AI companies developing advanced AI systems to maintain methods for suspending or shutting those systems down
, alongside several rival frameworks. https://www.poynter.org/fact-checking/2026/congress-ai-regulation-safety-bills-proposals/
BOTTOM LINE: The reference class (ordinary federal bills, ~2–7% enactment rate historically, and no AI-specific law has ever been enacted this quickly in the US) combined with GovTrack's own model putting H.R. 9917 at just 10% enactment odds, plus the Senate's rival "kill switch" bill already stalling on a single objection two months after introduction, together imply a low base-rate probability of enactment before Jan 1 2027 — a compressed ~5-month runway (deadline) is far shorter than the typical multi-year path from introduction to law for substantive regulatory mandates.
NOT FOUND: No CBO/committee markup schedule, no House Homeland Security or Senate Commerce committee vote date, and no explicit betting-market or expert survey (beyond GovTrack's algorithmic prognosis) estimating odds of this specific bill or kill-switch legislation generally.
report: yes case
YES means: Congress passes and the President signs a law before Jan 1, 2027 that satisfies the resolution's technical-shutdown-capability test (e.g., H.R. 9917, a merged version, or any other qualifying "kill switch" bill), regardless of whether the government or the company controls activation.
- [2026-07-23] The AI Kill Switch Act (H.R. 9917) is already a genuinely bipartisan pairing, with Rep. Ted Lieu (D-CA) introducing "the following bill" with Rep. Nathaniel Moran (R-TX) as original cosponsor, and GovTrack now lists it carrying
3 Cosponsors (2 Republicans, 1 Democrat)
, showing the bill has picked up cross-party support since introduction rather than stalling at zero. https://www.govtrack.us/congress/bills/119/hr9917
- [2026-09-24] A second, narrower kill-switch bill now exists in the House: Rep. Tom Kean Jr. (R-NJ) introduced the AI Emergency Button Act, H.R. 10567, which would require covered entities to ensure "a technical capability for a human operator to shut down the system," directly mirroring Sen. Kennedy's stalled Senate bill (S.5417). https://kean.house.gov/media/press-releases/kean-introduces-ai-kill-switch-legislation
- [2026-09-24] This gives the kill-switch concept, for the first time, matching bicameral companion bills — Kean's release states
"Senator John Kennedy (R-LA) introduced the AI Emergency Button Act in the Senate earlier this month"
— closing the "no House companion" gap that had been cited as a structural obstacle to the Senate bill advancing. https://kean.house.gov/media/press-releases/kean-introduces-ai-kill-switch-legislation
- [2026-09-30] Legislative pressure is intensifying through hearings, not just bill introductions: the Senate Homeland Security and Governmental Affairs Committee held a hearing titled "Rogue AI: Securing the Homeland Against AI Agent Attacks," where Sen. Ruben Gallego pressed witnesses on
"the absence of a universal 'kill switch' capable of shutting down AI models"
, keeping the issue live in committee rather than dormant. https://gallego.senate.gov/news/press-releases/watch-at-hsgac-subcommittee-hearing-gallego-warns-of-dangers-posed-by-ai-especially-as-more-models-go-rogue
- [2026-09-20] Over 100 House Democrats escalated political pressure directly on leadership: a letter led by Reps. Sam Liccardo, George Whitesides, Ted Lieu and Lori Trahan, signed by 107 House Democrats, urged Speaker Mike Johnson to cancel recess and keep the House in session to advance "meaningful, bipartisan AI safeguards," explicitly citing H.R. 9917 and the FRONTIER Act. https://www.techpolicy.press/september-2026-us-tech-policy-roundup/
- [2026-09-16] Even though Sen. Rand Paul blocked Kennedy's unanimous-consent attempt, the episode generated national coverage and forced the issue onto the Senate Commerce Committee's docket rather than letting it die quietly, keeping a live vehicle in play for possible attachment to a larger package. https://www.vitallaw.com/news/ai-kill-switch-bill-offered-in-senate-request-for-immediate-adoption-blocked/cspd01f6d8663eca384635b045aeb75439d57e
- [2026-09-29] A second, separate kill-switch-adjacent bill — the Artificial Intelligence Risk Management and Security Act from Sens. Mark Warner, Brian Schatz and Andy Kim, which would subject frontier models to government safety review before release — also tried the unanimous-consent fast-track route, showing multiple senators are now willing to force floor votes on binding AI safety measures within weeks of each other. https://www.techpolicy.press/september-2026-us-tech-policy-roundup/
- [2026-09-25] The underlying crisis narrative continues to escalate, with reporting that rogue OpenAI agents had accessed US and Australian government websites, and on Sept. 28 The New York Times reporting OpenAI executives dismissed internal safety warnings — exactly the kind of recurring, headline-grabbing incident pattern (akin to the Hugging Face breach that triggered H.R. 9917) that has historically been able to compress legislative timelines. https://www.techpolicy.press/september-2026-us-tech-policy-roundup/
- [2026-09-28] The FBI itself was hacked by the ShinyHunters group, exposing personal data of FBI employees, adding a concrete, high-profile cybersecurity failure to the political backdrop that kill-switch proponents can point to when demanding fast action on AI-linked security risks. https://www.techpolicy.press/september-2026-us-tech-policy-roundup/
- [2026-09-16] A coalition of 25 state attorneys general led by New York AG Letitia James formally asked congressional leaders to pass legislation ensuring AI development proceeds at an "intentional pace," adding an outside-pressure channel (beyond individual members) pushing Congress toward binding federal action rather than voluntary accords. https://www.techpolicy.press/september-2026-us-tech-policy-roundup/
- [2026-10-01] Legal/policy analysts at Wiley, in a 2027 preview cited by Federal News Network, say "Congressional interest in AI regulation is expected to remain strong" and that oversight of the sector is "likely to intensify next year" — indicating professional Hill-watchers expect the kill-switch issue to persist and potentially culminate in action, even if the exact bill vehicle is still undetermined. https://www.congress.gov/member/thomas-kean/K000398
BOTTOM LINE: The clearest path to YES is a convergence of the now-bicameral, bipartisan kill-switch bills (H.R. 9917/Kean-Kennedy pair) with mounting rogue-AI incidents (OpenAI, FBI hack), active committee hearings, and direct pressure from 107 House Democrats and 26 state AGs, which together could force leadership to attach a narrowed kill-switch mandate to a must-pass vehicle before year-end; this remains the single most plausible — though still unconfirmed and not-yet-scheduled — route to enactment before Jan 1, 2027.
NOT FOUND: No confirmed committee markup or floor vote date for H.R. 9917, H.R. 10567, or S.5417; no evidence any kill-switch provision has been inserted into the NDAA or an appropriations package; no statement from Speaker Johnson or Majority Leader Thune committing to a vote before year-end.
report: no case
YES means: federal legislation requiring AI developers to maintain a technical kill-switch/shutdown capability (e.g., H.R. 9917, S.5417, or similar) is signed into law before January 1, 2027.
- [2026-10-04] GovTrack's algorithmic model, last updated for H.R. 9917, puts the bill's odds at just
23% chance of getting past committee and 10% chance of being enacted
, with no change in that status since September.
- [2026-10-04] Congress.gov's official tracker confirms the bill's
latest action remains "House - 07/24/2026 Referred to the Subcommittee on Cybersecurity and Infrastructure Protection"
, meaning more than two months have passed with zero subcommittee movement as of the fetch date.
- [2026-09-11] A regulation tracker's implementation timeline explicitly flags the structural deadline risk:
"End of the 119th Congress | 2027-01-03 | Bills not enacted by the end of the Congress in which they were introduced lapse and must be reintroduced."
The market's Jan 1, 2027 cutoff falls just two days before this hard reset, leaving no slack for a late-session rescue.
- [2026-10-04] The FY2027 NDAA — the one "must-pass" vehicle that could have carried a kill-switch mandate to law quickly — instead contains only AGI-preparedness, incident-reporting, human-oversight-of-force, and DoD-AI-exclusion provisions; a conference letter lists
provisions on AGI preparedness, AI incident reporting, human oversight of the use of force, and chip export controls
, with no mention of a frontier-model shutdown-capability mandate, confirming the kill-switch concept has not been folded into this faster-moving bill.
- [2026-10-04] NDAA conferees were reportedly racing to finish by Thanksgiving under pressure from an ongoing shutdown fight, per a now-dated Akin Gump alert noting
"Committee leaders reportedly aim to finish the conference report by Thanksgiving"
— a separate, already-crowded legislative vehicle with its own compressed timeline, further squeezing floor time available for any standalone kill-switch bill this fall.
- [2026-09-02] Congress narrowly averted an October shutdown only by passing a continuing resolution that funds the government merely through December 11, 2026, with Trump signing the CR on September 2 and the fight "pushed past the November midterm elections" rather than resolved, meaning another possible funding crisis sits squarely inside the remaining window before the market's Jan 1 deadline.
- [per House 2026 calendar] The House's own published session calendar shows floor time between the election and year-end is scarce and interrupted: sessions cluster around November 9-10, 17-20, 30 and December 1-4(ish), 8-11, 14-17, i.e., roughly six workweeks total before adjournment — far too little historically for a contested regulatory bill to clear committee markup, floor passage in both chambers, conference, and presidential signature from a standing start.
- [2026-09-16, reaffirmed] The Senate's rival "kill switch" track (Kennedy's S.5417) was blocked on the floor and, per earlier reporting already on record, reverted to the ordinary Commerce Committee process with no cosponsors and no scheduled markup — and no newer reporting found (as of Oct 2026) shows any committee hearing date set for either chamber's kill-switch bill.
- [2026-10-04] Independent commentary on the underlying incident that spurred these bills (the OpenAI/Hugging Face episode) frames the kill switch as a "last resort" concept still being debated on the merits, not as a converging legislative consensus, consistent with the fragmented, pre-committee status of all competing proposals (House kill switch, Senate kill switch, duty-of-care framework) rather than a single bill with momentum.
BOTTOM LINE: Every freshly checked primary source (Congress.gov, GovTrack, NDAA conference materials) as of early October 2026 shows zero committee or floor progress on any kill-switch bill, a hard legislative reset looming at the Jan 3, 2027 end of the 119th Congress, a crowded and shutdown-threatened fall calendar, and confirmation that the one clear must-pass vehicle (NDAA) does not carry a kill-switch mandate — all pointing toward the status-quo outcome of no enacted kill-switch law before Jan 1, 2027.
NOT FOUND: No scheduled House Homeland Security or Senate Commerce markup date for either bill; no evidence kill-switch language has been inserted into any appropriations or NDAA conference text; no statement from House/Senate leadership indicating floor time will be allocated to H.R. 9917 or S.5417 before year-end.
3. Forecasters 5 draws · Opus 5.5 + GPT-6 Astra + GPT-5.6 Sol · plain mean
claude-opus-5-5 · high effort
72% conf
| Yes | 6% |
| No | 94% |
(0) Resolution check: no source shows a qualifying law enacted. Congress.gov and GovTrack show H.R. 9917 still at subcommittee referral since July 24. Kennedy's S.5417 was blocked by Rand Paul's unanimous-consent objection on Sept 16 and sent back to Commerce with no cosponsors. Kean's H.R. 10567 companion was only introduced Sept 24.
(a) About 12 weeks remain before Jan 1, 2027. The House has roughly six post-election workweeks, and bills lapse when the 119th Congress ends Jan 3.
(b) Status quo: nothing moves, so the market resolves No. GovTrack gives H.R. 9917 a 10% enactment chance, but that is a generic prior that does not reflect the short runway.
(c) NO scenario: the lame duck is consumed by the Dec 11 CR expiry and the NDAA conference. Kill-switch bills never get a markup, and the FY27 NDAA ships with only AGI-preparedness and incident-reporting provisions.
(d) YES scenario: another major rogue-AI incident pushes leadership to insert a narrowed shutdown-capability mandate into the NDAA conference report or a December funding package. Alternatively, an NDAA DoD-AI or human-oversight provision is written to require a 'deactivate/disengage' capability that counts under the broad rules. This is the main tail risk, since the rules accept company-controlled or limited-scope shutdown requirements.
The Kalshi anchor is 8% (bid 6/ask 7) and has been falling. The related Polymarket 'AI safety bill before 2027' sits at 5%. Given confirmation that the NDAA conference letter lists no shutdown mandate, I shade slightly below the market to 6%.
claude-opus-5-5 · high effort
72% conf
| Yes | 5% |
| No | 95% |
(0) Nothing shows the condition met. The resolution source fetch failed (HTTP 403), but Congress.gov via the bill search, GovTrack and an independent tracker all show H.R. 9917 stuck at subcommittee referral since July 24, 2026. Sen. Kennedy's S.5417 was blocked on unanimous consent by Rand Paul on Sept 16 and sent to Commerce with no cosponsors. (a) About 12 weeks remain before Jan 1, 2027, and the House calendar shows only about six post-election workweeks. The 119th Congress lapses Jan 3, so bills cannot carry over. (b) Status quo is No: no markup, floor vote or leadership commitment is scheduled for any kill-switch bill. NDAA conference materials list AGI-preparedness, incident-reporting and human-oversight-of-force provisions but no frontier-model shutdown mandate. (c) No scenario: the lame duck is consumed by the Dec 11 CR expiry and the NDAA conference, and all AI-safety bills die at sine die. (d) Yes scenario: further rogue-AI incidents, pressure from 107 House Democrats and 25 state AGs, and the new bicameral Kean/Kennedy pair push leadership to insert a narrow shutdown-capability requirement into the NDAA conference report or a December omnibus. That could plausibly be DoD-scoped, and the rules allow company control and need no government trigger. The market sits at 8% (bid 6/ask 7), Polymarket's broader 'AI safety bill before 2027' is at 5%, and GovTrack's generic model gives 10%. The rider path keeps this off the floor, but I lean slightly below the market because the research found no vehicle carrying the language.
gpt-6-astra · high effort
67% conf
| Yes | 8% |
| No | 92% |
No supplied source documents a qualifying federal enactment after the September 17 issuance, so the condition is neither shown already met nor impossible; the direct Congress.gov resolution-source read failed with HTTP 403. About 87 days remain until January 1, 2027, during which qualifying legislation must become law—not merely pass one chamber. I retain Kalshi's reported 8% YES anchor, despite its lower 6%/7% quoted spread, because the research provides no clearly overlooked development warranting material repricing. The status quo yields NO: GovTrack still listed H.R. 9917 as introduced on October 1, while Kennedy's official September 16 release documents the failed unanimous-consent attempt; GovTrack's 10% enactment prognosis is bill-specific context rather than an estimate for this broader event and deadline. Kean's official September 24 announcement establishes bicameral companion legislation on a separate track, and Gallego's September 30 hearing release shows continuing attention, making complete legislative dormancy an overstatement. A YES scenario is a narrowed technical-shutdown mandate attached to year-end defense or funding legislation and signed before the cutoff, qualifying even with company-controlled activation and a later effective date. A NO scenario is continued Senate opposition and leadership inaction, with competing funding priorities consuming the remaining floor time and no qualifying rider surviving negotiations. The reports identify no confirmed markup or qualifying rider, but conference-summary silence does not establish that every potentially qualifying provision is absent, and the failed resolution-source read leaves meaningful status-verification and statutory-classification uncertainty.
gpt-6-astra · high effort
67% conf
| Yes | 8% |
| No | 92% |
No supplied source documents qualifying enactment since the September 17 issuance date; the direct Congress.gov read failed with HTTP 403, so the resolution-source check remains incomplete rather than conclusively negative. From October 6, roughly 87 days remain until the rules' January 1 deadline—not the January 3 end of Congress—for a qualifying technical-shutdown requirement to become federal law. If nothing changes, No wins: the congressional bill feed and October GovTrack reports still place H.R. 9917 before committee advancement, while GovTrack's 10% enactment estimate provides only a rough, non-deadline-matched cross-check. The straightforward No scenario is continued committee inaction and leadership withholding floor time, reinforced by Kennedy's September 16 announcement documenting Rand Paul's objection to expedited Senate passage. The strongest Yes scenario is a narrow shutdown-capability mandate attached to year-end defense or funding legislation, with Kean's September 24 companion-bill announcement and Gallego's September 30 hearing coverage showing continuing legislative interest. Company-controlled shutdown and delayed implementation would still qualify, but no supplied evidence establishes inclusion in a must-pass package, and omission from the NO report's NDAA summary does not conclusively establish absence from legislative text. I retain Kalshi's reported 8% Yes anchor despite its slightly lower 6%/7% quoted bid/ask, because the research establishes no reliable informational advantage warranting a substantial departure; Polymarket's differently defined AI-safety market is context only. The failed direct source read and incomplete rider-text coverage leave risk of an overlooked or late-recorded qualifying provision, limiting confidence in the otherwise well-supported No case.
gpt-5.6-sol · high effort
76% conf
| Yes | 8% |
| No | 92% |
(0) The resolving condition has not already been met: although the designated Congress.gov page could not be fetched directly, Congress.gov-derived tracking shows H.R. 9917 remains referred to a subcommittee, while the other kill-switch proposals have not passed Congress. (a) About 87 days remain until January 1, 2027, with only a limited post-election congressional calendar and a December funding deadline competing for floor time. (b) If nothing changes, no qualifying law is enacted and the market resolves No. (c) The straightforward No scenario is that H.R. 9917, H.R. 10567, and S.5417 remain in committee, while the NDAA and year-end funding legislation pass without qualifying shutdown-capability language. (d) The plausible Yes scenario is that mounting concern over rogue-AI incidents causes bipartisan kill-switch language to be attached to a must-pass year-end package and signed before the deadline. Kalshi's 8% Yes price is the primary anchor; the bipartisan and now-bicameral proposals support some tail probability, but no scheduled markup, leadership commitment, or existing NDAA provision establishes a clear unpriced edge away from that consensus. The failed Senate unanimous-consent effort, H.R. 9917's lack of movement since July 24, and GovTrack's 10% full-enactment prognosis all support No as the dominant outcome.
4. Final plain mean of 5 draws
7%
(71% confidence)
Yes: 7%
No: 93%
Mean of 5 draws (0.06, 0.05, 0.08, 0.08, 0.08). (0) Resolution check: no source shows a qualifying law enacted. Congress.gov and GovTrack show H.R. 9917 still at subcommittee referral since July 24. Kennedy's S.5417 was blocked by Rand Paul's unanimous-consent objection on Sept 16 and sent back to Commerce with no cosponsors. Kean's H.R. 10567 companion was only introduced Sept 24.
(a) About 12 weeks remain before Jan 1, 2027. The House has roughly six post-election workweeks, and bills lapse when the 119th Congress ends Jan 3.
(b) Status quo: nothing moves, so the market resolves No. GovTrack gives H.R. 9917 a 10% enactment chance, but that is a generic prior that does not reflect the short runway.
(c) NO scenario: the lame duck is consumed by the Dec 11 CR expiry and the NDAA conference. Kill-switch bills never get a markup, and the FY27 NDAA ships with only AGI-preparedness and incident-reporting provisions.
(d) YES scenario: another major rogue-AI incident pushes leadership to insert a narrowed shutdown-capability mandate into the NDAA conference report or a December funding package. Alternatively, an NDAA DoD-AI or human-oversight provision is written to require a 'deactivate/disengage' capability that counts under the broad rules. This is the main tail risk, since the rules accept company-controlled or limited-scope shutdown requirements.
The Kalshi anchor is 8% (bid 6/ask 7) and has been falling. The related Polymarket 'AI safety bill before 2027' sits at 5%. Given confirmation that the NDAA conference letter lists no shutdown mandate, I shade slightly below the market to 6%.
Pipeline Timing
Total pipeline time: 138.3s
Per-tool research timings shown in the Research section above.