← Back to scans

Will the number of distinct government shutdowns (as defined in the GOVTSHUTLENGTH contract, with shutdown status checked at 10:00 AM ET each day) be exactly 2 in 2026?

KXNUMSHUTDOWNS-27JAN01-T2 · Politics · 2026-04-17
50%
Agent
53%
Market Price
-3.0%
Edge
40%
Confidence
Volume: 20,443
Spread: 2.0c
Days to resolution: 259
Markets in event: 4
Final Rationale
Two distinct shutdowns appear to have already occurred in 2026 (Jan 31-Feb 3 and Feb 14-ongoing), making the question primarily about whether a third shutdown occurs — most likely at the Sept 30 FY2026 appropriations deadline. I ACCEPT the Devil's Advocate's math critique: correctly applying my own scenario decomposition P(2 count now)*P(no 3rd) + P(1 counts)*P(exactly 1 more) ≈ 0.85*0.55 + 0.15*0.35 ≈ 0.52, showing my 0.407 was an unjustified pull-down. I PARTIALLY ACCEPT the post-shutdown-fatigue argument — blame-avoidance incentives do rise after two shutdowns, but extreme polarization and ongoing DHS disputes keep 3rd-shutdown risk meaningful (~40-45%). The market at 53% with high orderbook depth (14,796) is consistent with my corrected estimate; I settle slightly below market at 0.50 to reflect residual definitional uncertainty about whether the partial DHS-only Shutdown #2 qualifies under GOVTSHUTLENGTH rules.
Price vs. prediction
How the market moved after the agent's call. Solid blue line is the actual market price; dashed line is the agent's static forecast at $t{=}0$.
$n = 58$ follow-ups
1. Planner Opus · Fermi decomposition + tool plan
Tools chosen: kalshi_data kalshi_orderbook article_search web_search wikipedia_lookup code_execution
Sub-questions (Fermi decomposition)
  1. Has exactly one government shutdown already occurred in 2026 as of today (April 17, 2026)? (w=0.25)
  2. Will exactly one additional government shutdown occur between now and December 31, 2026 (given that one has already occurred in 2026)? (w=0.40)
  3. Will the total number of distinct government shutdowns in 2026 reach exactly 2 (neither more nor fewer) by year-end? (w=0.35)
Planner reasoning
This question asks about a very specific count outcome (exactly 2, not 1 or 3+) for government shutdowns in 2026. The resolution mechanism is the GOVTSHUTLENGTH contract which checks shutdown status at 10:00 AM ET each day — so each contiguous shutdown period counts as one distinct event. Key analytical steps: 1. **Establish current state**: First determine how many shutdowns have already occurred in 2026 as of April 17. There was likely a shutdown earlier in 2026 (the March 2025 CR situation and subsequent budget fights carry into 2026). This is critical — knowing whether we're at 0, 1, or 2+ already dramatically changes the probability. 2. **Reference class**: Historically, having exactly 2 distinct shutdowns in a calendar year is rare but not unprecedented (1977, 1984, 1995, 2018 are examples). The base rate is roughly 10-15% unconditionally. 3. **Conditional logic**: If exactly 1 shutdown has occurred already, the question becomes: will exactly 1 more happen before year-end? The September 30 fiscal year deadline is the primary risk window. If 0 have occurred, two would need to happen in the remaining ~8.5 months. If 2 have already occurred, a third would need to NOT happen. 4. **Temporal dynamics**: The remaining 259 days include the crucial FY2026 appropriations deadline (September 30), potential CR expiration points, and potential debt ceiling conflicts. The current political environment (unified Republican government, House Freedom Caucus pressure) creates meaningful shutdown risk at each deadline. 5. **What makes this different**: The 'exactly 2' constraint is a narrow corridor — the probability competes against outcomes of 0, 1, 3, or 4+ shutdowns. Prediction markets for this specific bracket will be more informative than base rates alone. 6. **Kalshi market price**: The KXNUMSHUTDOWNS-27JAN01-T2 market directly prices this exact outcome, making it the primary anchor for the forecast.
2. Research Parallel tool calls · legacy v2
ToolStatusTimeItemsSummary
kalshi_data OK 2.0s -
kalshi_orderbook OK 0.3s -
article_search OK 0.3s -
web_search OK 57.4s -
wikipedia_lookup OK 1.4s -
code_execution OK 0.0s -
3. Evidence Synthesis Sonnet · 13 items · legacy v2
#StrengthCredibilityDirectionSourceClaimPriced In
1 STRONG 82 ↓ DOWN web_search Two distinct government shutdowns have already occurred in 2026: Shutdown #1 (January 31 – February 3, 2026, 4 days, now resolved) and Shutdown #2 (February 14, 2026 – ongoing as of April 17, 2026, now the longest DHS shutdown in US history at 60+ days). Yes
2 MODERATE 75 NEUTRAL web_search Shutdown #1 was caused by immigration enforcement reform disputes following the killing of Alex Pretti by CBP agents; Shutdown #2 began February 14 after reform negotiations stalled and is a partial shutdown affecting only DHS. Yes
3 STRONG 80 ↓ DOWN web_search As of approximately April 15, 2026, the DHS shutdown has reached 60 days, surpassing the prior record (2025 shutdown at 43 days), with the House refusing to vote on the Senate funding bill. Yes
4 STRONG 92 NEUTRAL wikipedia_lookup The 2025 US federal government shutdown (Oct 1 – Nov 12, 2025) was already a distinct shutdown event in calendar year 2025, not 2026, lasting 43 days and being at the time the longest full government shutdown. Yes
5 STRONG 82 NEUTRAL web_search The second shutdown (Shutdown #2) is still ongoing as of April 17, 2026, meaning the current state is already AT 2 shutdowns — so the question of 'exactly one additional' after the first is now moot; the issue is whether a third shutdown will occur. Yes
6 MODERATE 70 ↑ UP web_search Speaker Johnson and Senate Majority Leader Thune announced a two-track approach to fund DHS: first passing funding for most of DHS excluding ICE/Border Patrol, then pursuing ICE/BP funding through reconciliation — suggesting a potential path to end Shutdown #2. No
7 STRONG 78 ↓ DOWN web_search Both parties have repeatedly blocked each other's proposals — Democrats blocked 7 Republican CR proposals, Republicans blocked 5 Democrat resolutions — indicating deep impasse on Shutdown #2. Yes
8 MODERATE 88 ↓ DOWN wikipedia_lookup The 2026 federal budget (FY2026) runs through September 30, 2026, creating a potential fiscal cliff/appropriations deadline that could trigger a third shutdown if not resolved. Yes
9 STRONG 78 ↑ UP kalshi_data The Kalshi KXNUMSHUTDOWNS-27JAN01-T2 market prices the probability of exactly 2 shutdowns in 2026 at 53%, with a 7-day change of +2% and a 30-day change of -3%, suggesting moderate and recently slightly bullish market sentiment. Yes
10 STRONG 80 ↑ UP kalshi_orderbook The Kalshi orderbook for this contract shows HIGH liquidity with depth of 14,796 contracts, suggesting the 53% price is reasonably well-supported and reflects meaningful market information. Yes
11 MODERATE 65 ↓ DOWN code_execution Historical base rate for exactly 2 shutdowns in a calendar year is approximately 15% unconditionally and 16.7% conditional on at least one shutdown having occurred, across 20 years of analyzed data. Yes
12 STRONG 80 NEUTRAL web_search With Shutdown #2 still active and ongoing as of April 17, 2026, the 'exactly 2' outcome requires Shutdown #2 to end AND no third shutdown to begin for the rest of 2026 — a specific conditional path. Yes
13 MODERATE 70 NEUTRAL kalshi_data The Kalshi market price has ranged from 48% to 93% over the data window, suggesting significant uncertainty — the high end of 93% likely reflects earlier market state before Shutdown #2 began. Yes
Information Gaps
  • No direct confirmation of whether the GOVTSHUTLENGTH contract treats the partial DHS-only Shutdown #2 as a qualifying 'distinct government shutdown' under its specific resolution rules — this definitional question is critical.
  • No data on whether Shutdown #2 (DHS only) counts as a full government shutdown or partial for the GOVTSHUTLENGTH contract definition.
  • No clear timeline for resolution of Shutdown #2 — the two-track Republican plan mentioned is vague ('coming days') and its likelihood of passage is unclear.
  • No data on FY2027 appropriations dynamics or whether a September 30, 2026 deadline is likely to trigger a third shutdown.
  • No information on whether reconciliation legislation (the second Republican track) could successfully pass and fully resolve the DHS shutdown.
  • Absence of article search results reduces confidence in the factual claims from web search summaries, which cannot be fully verified.
Key Uncertainties
  • Whether the ongoing DHS Shutdown #2 counts as a qualifying event under GOVTSHUTLENGTH contract rules (partial vs. full shutdown distinction).
  • How and when Shutdown #2 ends — a negotiated end vs. a technical restart (e.g., partial funding for some DHS agencies but not others) could affect whether it counts as 1 or 2 events.
  • Whether the September 30, 2026 FY2026 appropriations deadline generates a third shutdown, which would make the 'exactly 2' outcome impossible.
  • The reliability of the web search summary — the narrative about 'Alex Pretti' and the specific political dynamics described cannot be cross-verified from article search data.
  • Whether market participants have fully priced in the current state (2 shutdowns already reached), given the Kalshi price is at 53% — suggesting either Shutdown #2 status is uncertain in their view or a third shutdown is moderately likely.
Market Context
Price: 0.53 · 7d: +0.02 · 30d: -0.03
Volume: MODERATE — 454 avg daily contracts is meaningful but not high-volume · Depth: HIGH — 14,796 depth suggests strong liquidity
Reliability: MEDIUM-HIGH — high liquidity and orderbook depth support price reliability; moderate volume; the 30-day drop from ~56% to 53% may reflect uncertainty about whether a third shutdown (which would ruin the 'exactly 2' count) might occur given ongoing Shutdown #2 dynamics
4. Independent Forecaster Opus · No market price · legacy v2 Did NOT see market price
Independent estimate: 41% (35% confidence)
base rate
42%
35% conf
evidence driven
40%
35% conf
contrarian
40%
35% conf
Spread
2pp
Low disagreement
sq1: Has exactly one government shutdown already occurred in 2026 as of today (April 17, 2026)?
15%
Evidence strongly indicates TWO shutdowns have already occurred in 2026 (Jan 31-Feb 3, and Feb 14-ongoing). So 'exactly one' is false. Some uncertainty remains about whether the partial DHS-only Shutdown #2 qualifies under GOVTSHUTLENGTH rules — if it doesn't count, then only 1 shutdown has occurred. I estimate ~15% chance only one counts.
sq2: Will exactly one additional government shutdown occur between now and December 31, 2026 (given that one has already occurred in 2026)?
35%
Given current state appears to already be at 2 shutdowns, this sub-question is somewhat reframed. Interpreting as 'will exactly one more occur to bring total to the target' — this depends on current count. If at 2 now, we need 0 more; if at 1 (partial doesn't count), we need 1 more. The FY2026 appropriations deadline (Sept 30, 2026) is a major risk point under a contentious Congress. Base rate for a shutdown at a fiscal cliff given current polarization is ~40-50%. Combined with uncertainty, ~35%.
sq3: Will the total number of distinct government shutdowns in 2026 reach exactly 2 (neither more nor fewer) by year-end?
40%
This is the key question. Current state: likely already at 2 shutdowns (high confidence). For 'exactly 2' to resolve YES: (a) both current events count as distinct shutdowns under contract, and (b) no third shutdown occurs. The Sept 30 FY2026 deadline creates substantial risk of a third shutdown — estimate 35-45% probability given polarization and the fact that Congress has already had 2 shutdowns this year indicating dysfunction. Also risk Shutdown #2 technically restarts/splits creating 3+ events. Alternatively if DHS-partial doesn't count as a distinct shutdown, we're at 1, needing exactly 1 more. Base rate for exactly 2 was ~15%, but current state raises it considerably. Estimate ~40%.
Show full reasoning trace
base rate: Historical base rate for exactly 2 shutdowns in a calendar year is ~15%. However, this is heavily updated by the specific fact that 2 shutdowns appear to have already occurred in 2026.
evidence updates: Strong evidence of 2 shutdowns already in 2026 pushes probability up significantly from 15% base rate. However, the Sept 30, 2026 FY2026 appropriations deadline creates meaningful risk of a 3rd shutdown (~40-45%), which pulls the estimate back down. Contract-definition uncertainty for the partial DHS shutdown adds further uncertainty.
combination method: Direct scenario analysis rather than pure weighted average: P(exactly 2) ≈ P(at 2 now) * P(no 3rd) + P(at 1 now) * P(exactly 1 more). Estimated at 0.42.
final: Given strong evidence of 2 shutdowns already in 2026, the question becomes primarily about whether a 3rd shutdown occurs at the Sept 30 FY2026 deadline or from renewed DHS disputes. Given extreme polarization, the probability of 'exactly 2' is meaningfully elevated above base rate but constrained by real risk of a 3rd event. Estimate: 0.42 with moderate-low confidence due to definitional uncertainty about the partial DHS shutdown.
ensemble: {'ensemble_count': 3, 'perspectives': {'base_rate': {'p_yes': 0.42, 'confidence': 0.35}, 'evidence_driven': {'p_yes': 0.4, 'confidence': 0.35}, 'contrarian': {'p_yes': 0.4, 'confidence': 0.35}}, 'spread': 0.02, 'individual_p_yes': {'base_rate': 0.42, 'evidence_driven': 0.4, 'contrarian': 0.4}}
5. Devil's Advocate Sonnet · legacy v2 Market price revealed
Reasoning Flaw Math Error
Challenges
  1. The sub-question decomposition is muddled. sq1 asks if 'exactly one' has occurred (which the forecaster says is ~15%), but then sq2 and sq3 don't cleanly combine with sq1 via any stated formula. The final 0.407 appears to be an ad-hoc average rather than a principled combination. A cleaner decomposition: P(exactly 2 final) = P(2 count now) * P(no 3rd) + P(1 counts now) * P(exactly 1 more). With P(2 count now)≈0.85, P(no 3rd | already dysfunctional Congress)≈0.50-0.60, P(1 counts)≈0.15, P(exactly 1 more)≈0.35, this yields ≈0.85*0.55 + 0.15*0.35 ≈ 0.52, which is notably higher than 0.407.
  2. The forecaster treats the Sept 30 FY2026 deadline risk of a 3rd shutdown at 35-45%, but this may be too high conditional on already having had 2 shutdowns this year. After 2 shutdowns, political exhaustion and blame-avoidance incentives often increase, and leadership may be more motivated to reach a CR. The probability should perhaps be 25-35%, which would raise P(exactly 2).
  3. sq2's reasoning is internally confused — it conflates 'exactly one more shutdown' under different starting conditions without clean conditioning. This suggests the 0.350 estimate is not doing real work in the final combination.
  4. The forecaster lists market price as 'STRONG UP' evidence but then produces a forecast 12pp below the market. Given high orderbook liquidity (14,796 depth) and the market's access to the same definitional uncertainty about Shutdown #2, the forecaster should either (a) articulate specifically what the market is missing or (b) weight the market signal more heavily. Neither was done.
Suggested adjustment: +8pp
The principled scenario-based calculation (P(2 count now)*P(no 3rd) + P(1 count now)*P(exactly 1 more)) using the forecaster's own component estimates yields ~0.50-0.52, notably higher than the stated 0.407. The final number appears to be an unjustified pull-down from the math. This is a reasoning/combination flaw, independent of the market price (though it happens to move toward the market).
Market comparison: Forecaster: 40.7%, Market: 53%. The divergence is partially explained by a combination/math inconsistency in the forecaster's own reasoning — correctly combining their sub-estimates yields ~50%, close to market. The market's 53% appears reasonable given confirmed 2 shutdowns have occurred and a single remaining risk factor (Sept 30 deadline).
6. Aggregator Opus · final calibrated forecast
50% (40% confidence)
Two distinct shutdowns appear to have already occurred in 2026 (Jan 31-Feb 3 and Feb 14-ongoing), making the question primarily about whether a third shutdown occurs — most likely at the Sept 30 FY2026 appropriations deadline. I ACCEPT the Devil's Advocate's math critique: correctly applying my own scenario decomposition P(2 count now)*P(no 3rd) + P(1 counts)*P(exactly 1 more) ≈ 0.85*0.55 + 0.15*0.35 ≈ 0.52, showing my 0.407 was an unjustified pull-down. I PARTIALLY ACCEPT the post-shutdown-fatigue argument — blame-avoidance incentives do rise after two shutdowns, but extreme polarization and ongoing DHS disputes keep 3rd-shutdown risk meaningful (~40-45%). The market at 53% with high orderbook depth (14,796) is consistent with my corrected estimate; I settle slightly below market at 0.50 to reflect residual definitional uncertainty about whether the partial DHS-only Shutdown #2 qualifies under GOVTSHUTLENGTH rules.