← back to scans
Will it be reported by any of the Source Agencies that the bilateral U.S.–Saudi agreement for peaceful nuclear cooperation under Section 123 of the Atomic Energy Act has entered into force and become legally operative between the two governments before Jan 1, 2027?
11%
Agent
12%
Market Price
-1.2%
Edge
60%
Confidence
14,519
Volume
8.0c
Spread
83
Days to resolution
1
Markets in event
final rationale
Mean of 5 draws (0.09, 0.10, 0.12, 0.12, 0.11). (0) No source reports entry into force. The agreement was signed July 22, 2026, transmitted to Congress in late August, and entered the Senate record Sept. 14. It is still inside its 90-day congressional review period, and the resolution-source read finds nothing showing the condition met. (a) About 12 weeks remain before Jan 1, 2027. (b) Status quo is No. Even if Congress stays silent, entry into force needs the review period to lapse and then a formal bilateral act, such as the diplomatic-note exchange that took two months after review in the UAE case. Trump has also said the deal 'will only move forward if Saudi Arabia joins the Abraham Accords.' Pakistan Observer reported on Oct. 8 that Riyadh still refuses that condition. (c) NO scenario: Congress never blocks it, but the administration withholds the final note exchange pending normalization. Alternatively, the 'continuous session' clock, which pauses during long recesses and faces a sparse Senate calendar (about 8 days in November, 14 in December), runs past mid-December, leaving no time to finalize. (d) YES scenario: the review lapses around Dec. 13 without an enacted disapproval, which has never happened for a 123 agreement. Trump then quietly drops the Accords linkage and the governments exchange notes before year-end, reported by a Source Agency. Kalshi is at 12% (bid 8/ask 16), down 18 points in 30 days, and Polymarket's same question is at 10%. The research supports these low prices, particularly the active Saudi refusal and the post-review formalities, so I sit slightly below the Kalshi mid.
price vs. prediction
market price
agent forecast at t+0
9 follow-ups
1. Planner Opus 5.5 · picks the research tools
Tools chosen:
kalshi_direct
resolution_source
kalshi_related
polymarket_related
congress_bills
article_search
Planner reasoning
The Kalshi price is the anchor. A 123 agreement has to be submitted to Congress and sit for a 90-day continuous-session review before it can enter into force, so congress_bills can show whether it has been submitted or whether resolutions of disapproval exist. Cross-market prices and a targeted search for the submission or signing date round this out.
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** (KXUSSAUDINUCLEAR-27-27JAN01) - Current price (probability): 12.00% (live; bid 8% / ask 16%) - 7-day price change: +0.00% - 30-day price change: -18.00% - Average daily volume: 279 contracts - Price range: 4.00% - 62.00% - Data points: 52 days
- resolution_source: already_resolved=unclear; matches_criteria=False; last_updated=September 24, 2026 (Columbia CGEP article); April 12, 2024 (Brookings article). Neither fetched page reports that a bilateral U.S.-Saudi Section 123 nuclear cooperation agreement has entered into force. The Columbia CGEP piece (Sept 24, 2026) discusses why such an agreement 'would serve US interests,' implying it has not yet been concl
- kalshi_related: 3 related markets / summaries. series KXUSSAUDINUCLEAR: 0 markets (skipped 1 no-signal) | keyword 'Saudi nuclear': ok | keyword '123 agreement': ok | keyword 'Saudi Israel normalization': ok
- polymarket_related: Polymarket search over 2 keyword(s), kept 10 matches. keyword 'Saudi nuclear': 5 markets | keyword 'Saudi 123 agreement': 5 markets
- congress_bills: Found 4 bills matching 'Saudi Arabia nuclear cooperation agreement 123'.
- article_search: Fetched 14 unique articles across 2 queries (lookback=180d). 'US Saudi 123 agreement signed submitted to Congress date': 10 articles | 'Saudi 123 agreement congressional review period entry into force': 10 articles
Research loops, bottom lines
- current state: As of October 10, 2026, the Saudi 123 Agreement is still inside its 90-day congressional review period (started Sept. 14, 2026), with a Senate vote expected before Dec. 13, 2026, and no indication that a disapproval resolution will succeed; absent congressional blockage, the agreement is on track to become legally operative before Jan. 1, 2027, though (per the UAE precedent) a formal exchange of diplomatic notes or similar step may still be needed after congressional review ends, and Trump's add
- base rate: The historical base rate strongly favors eventual entry into force (Congress has never formally disapproved a 123 agreement), but the "continuous session" clock plus comparable precedents (UAE ~7 months, China/India far longer) suggest the standard process alone would likely not conclude before January 2027 if counting from the late-August 2026 transmittal, and the added non-statutory Abraham Accords contingency introduces a real, non-trivial risk of delay or non-completion within this window.
- yes case: The statutory default (automatic entry into force absent an enacted disapproval resolution, which has never happened for any 123 agreement) combined with a Senate vote already locked in before Dec. 13 — well inside the Jan. 1, 2027 deadline — constitutes a strong, evidence-based path to YES, provided only that the standard procedural/diplomatic formalization (comparable to the UAE's post-review diplomatic note exchange) is completed or reported in the remaining weeks of the year.
- no case: The strongest NO case does not rest on Congress disapproving the deal (historically near-impossible) but on two independent, currently-unresolved obstacles: (1) Trump's self-imposed, non-statutory Abraham Accords precondition, which Saudi Arabia is still publicly refusing as of Oct. 8, 2026, and which the administration could use to withhold final implementation even if Congress stays silent; and (2) a compressed, election-year legislative calendar (only ~8 Senate session days in November, ~14 i
tools
| tool | status | time | items | summary |
|---|---|---|---|---|
| kalshi_direct | OK | 0.2s | 1 | ## This Market's Kalshi Data **Before Jan 1, 2027** (KXUSSAUDINUCLEAR-27-27JAN01) - Current price (probability): 12.00% (live; bid 8% / ask 16%) - 7-day price change: +0.00% - 30-day price change: -18.00% - Average daily volume: 279 contracts - Price range: 4.00% - 62.00% - Data points: 52 days |
| resolution_source | OK | 31.4s | 1 | already_resolved=unclear; matches_criteria=False; last_updated=September 24, 2026 (Columbia CGEP article); April 12, 2024 (Brookings article). Neither fetched page reports that a bilateral U.S.-Saudi Section 123 nuclear cooperation agreement has entered into force. The Columbia CGEP piece (Sept 24, |
| kalshi_related | OK | 7.9s | 3 | 3 related markets / summaries. series KXUSSAUDINUCLEAR: 0 markets (skipped 1 no-signal) | keyword 'Saudi nuclear': ok | keyword '123 agreement': ok | keyword 'Saudi Israel normalization': ok |
| polymarket_related | OK | 0.4s | 10 | Polymarket search over 2 keyword(s), kept 10 matches. keyword 'Saudi nuclear': 5 markets | keyword 'Saudi 123 agreement': 5 markets |
| congress_bills | OK | 1.3s | 4 | Found 4 bills matching 'Saudi Arabia nuclear cooperation agreement 123'. |
| article_search | OK | 0.4s | 14 | Fetched 14 unique articles across 2 queries (lookback=180d). 'US Saudi 123 agreement signed submitted to Congress date': 10 articles | 'Saudi 123 agreement congressional review period entry into force': 10 articles |
research loops
·
4/4 ok ·
17 searches ·
7 page reads
| dimension | status | time | searches | page reads | report |
|---|---|---|---|---|---|
| current state | OK | 37s | 5 | 3 | 5059 chars |
| base rate | OK | 33s | 3 | 1 | 4894 chars |
| yes case | OK | 51s | 4 | 2 | 5678 chars |
| no case | OK | 48s | 5 | 1 | 5683 chars |
report: current state
- [2026-07-22] The U.S. and Saudi Arabia signed a civil nuclear cooperation agreement under Section 123 of the Atomic Energy Act (plus a Bilateral Safeguards Agreement), signed by Secretary of Energy Chris Wright and Saudi Minister of Energy Prince Abdulaziz bin Salman Al Saud.
On 22 July 2026, the United States and the Kingdom of Saudi Arabia signed an Agreement for Cooperation Concerning Peaceful Uses of Nuclear Energy pursuant to Section 123 of the Atomic Energy Act of 1954, signed by US Secretary of Energy Chris Wright and KSA Minister of Energy Prince Abdulaziz bin Salman Al Saud.
- [2026-07-23] One day after signing, President Trump added a new condition on Truth Social that
the civil nuclear agreement "is totally subject to Saudi" Arabia joining the Abraham Accords
, a condition congressional aides say is absent from the written text.
- [2026-08-24/27] The administration formally transmitted the agreement package (123 Agreement text, Bilateral Safeguards Agreement, classified and unclassified Nuclear Proliferation Assessment Statement, two confidential side letters) to Congress;
the Congressional Record noted the transmission of the documents on Aug. 27
, with the package dated Aug. 24.
- [2026-09-14]
The agreement entered the Senate record on Sept. 14, starting the 90-day review period during which lawmakers can seek to pass a resolution of disapproval.
This starts the statutory clock under Section 123(b) of the AEA.
- [2026-09-17]
Democratic lawmakers introduced a Joint Resolution of Disapproval led by Rep. Gregory Meeks and three House Democratic colleagues, shortly before lawmakers left Washington ahead of midterm elections; a vote could come in November, after the midterms.
- [2026-09-25] (National Interest analysis, published ~15 days before Oct 10) assesses:
the agreement will enter into force by the end of the year unless Congress acts to prevent it; a joint resolution of disapproval is seen as unlikely to succeed.
- [2026-10-02] Reuters reported that senators (Merkley, Kaine, Markey, Coons, Van Hollen, working with Republicans)
secured a vote on the agreement and expect it before Dec. 13, under the 90-day window from its printing in the Senate record on Sept. 14.
- [2026-10-02] Democratic and Republican senators had separately (in September)
asked the Trump administration to declassify and release all information about the agreement, including the two classified side letters, noting the government has reached dozens of 123 nuclear agreements with other countries without withholding such information.
- [2026-10-05] Follow-up coverage (sightlineu3o8) confirms the same Dec. 13 timeline and the bipartisan push for a floor vote within the 90-day statutory window, with no change reported to the agreement's status.
- [No date found after Oct 5] No report found of a Senate or House floor vote having actually occurred, of a disapproval resolution passing, or of the 90-day review period concluding or the agreement entering into force.
- [Background, historical precedent] Under the AEA framework, a non-exempt 123 agreement (as this one is classified)
requires Congress to review the deal for 90 days before it enters into force; Congress can do nothing, pass a resolution approving, pass a resolution of disapproval, or seek to modify terms; the Saudi agreement is non-exempt and will not require an affirmative vote of approval to take effect.
Congress has never once enacted a disapproval resolution to block a Section 123 nuclear cooperation agreement in U.S. history.
- [Comparable precedent, 2009 UAE deal] For context on what "entry into force" requires after congressional review: in the 2009 U.S.-UAE 123 agreement,
Congress had the opportunity to review the proposed agreement until 17 October 2009, a period of 90 days of continuous session, and the agreement entered into force on 17 December 2009 when the governments exchanged diplomatic notes
— i.e., an additional formal step (exchange of diplomatic notes) followed the end of congressional review before the deal became legally operative.
BOTTOM LINE: As of October 10, 2026, the Saudi 123 Agreement is still inside its 90-day congressional review period (started Sept. 14, 2026), with a Senate vote expected before Dec. 13, 2026, and no indication that a disapproval resolution will succeed; absent congressional blockage, the agreement is on track to become legally operative before Jan. 1, 2027, though (per the UAE precedent) a formal exchange of diplomatic notes or similar step may still be needed after congressional review ends, and Trump's added Abraham Accords condition introduces some uncertainty about timing.
NOT FOUND: No report of an actual Senate/House floor vote outcome on a disapproval resolution; no confirmation of the exact date the 90-day continuous-session period legally expires; no report of diplomatic notes being exchanged or other formal "entry into force" step; no Saudi government statement on Trump's Abraham Accords linkage; no news after October 5, 2026 updating the process.
report: base rate
- [2026-07-22] The US and Saudi Arabia signed a Section 123 agreement and an accompanying bilateral safeguards agreement, culminating
"almost 15 years of intermittent negotiations"
between the two governments. https://www.iiss.org/online-analysis/online-analysis/2026/08/the-ussaudi-123-agreement-more-than-nuclear-cooperation-at-stake/
- [2026-08-24/27]
A month after signing, on August 24, the White House submitted a package to Congress which included the texts of the 123 agreement, its Bilateral Safeguards Agreement (BSA), and Nuclear Proliferation Assessment Statement (NPAS)
, with transmission formally noted in the Congressional Record on Aug. 27. https://www.stimson.org/2026/nuclear-disruption-the-us-saudi-123-agreement-and-the-future-of-nuclear-cooperation-in-the-middle-east/
- [BASE RATE]
"Congress has never disapproved a 123 Agreement"
in the history of the statute, which is the key reference-class fact favoring eventual entry into force absent political intervention. https://www.morganlewis.com/blogs/upandatom/2025/02/united-states-and-thailand-sign-123-agreement-for-peaceful-nuclear-cooperation
- [TIMING MECHANICS] Under the Atomic Energy Act,
the review period is comprised of 90 days of continuous session, broken into a 30-day review by committees followed by a 60-day review by the entire Congress
; this "continuous session" count excludes recesses, so 90 legislative days typically stretches over several calendar months.
- [HISTORICAL COMPARABLE - UAE] For the 2009 US-UAE 123 agreement,
Congress had the opportunity to review the agreement until 17 October 2009, a period of 90 days of continuous session
after May 21 submission, and
the agreement entered into force on 17 December 2009 when the governments exchanged diplomatic notes
— roughly 7 months from submission to actual entry into force, including a ~2-month gap after the congressional review period ended before formal EIF via note exchange.
- [HISTORICAL COMPARABLE - CHINA] The US-China 123 agreement illustrates that even after congressional review concludes, implementation can be delayed for other reasons:
"Almost 13 years passed between the time President Reagan submitted the current 123 agreement to Congress in July 1985 and its implementation in March 1998 under President Clinton"
due to added certification requirements Congress imposed.
- [HISTORICAL COMPARABLE - INDIA] The
40-year U.S.-India 123 agreement came into force in December 2008
, following extensive additional congressional legislation (the Hyde Act) beyond the standard review process, another case of extended timelines for high-profile agreements.
- [POLITICAL COMPLICATION]
The civil nuclear deal will go into effect in 90 days unless both houses of Congress pass disapproval resolutions, but an administration official said Trump's "position has not changed... the agreement will only move forward if Saudi Arabia joins the Abraham Accords"
, introducing a non-statutory executive-branch contingency not present in prior 123 agreement precedents.
- [OPPOSITION PRECEDENT] A withdrawal precedent exists:
the George W. Bush administration withdrew a 123 agreement with Russia from congressional consideration in 2008 after Moscow invaded Georgia
, showing the executive branch can pull an agreement even after transmittal, independent of a congressional disapproval vote.
- [LEGISLATIVE PUSHBACK] Senators have introduced competing legislation (e.g., the "No Nukes for Saudi Arabia Act") that would impose additional preconditions before any Saudi 123 agreement could take effect, though no such bill has passed historically for any 123 agreement. https://www.markey.senate.gov/imo/media/doc/no_nukes_for_saudi_arabia_act.pdf
- [CURRENT STATUS] As of the K&L Gates September 21, 2026 analysis, the agreement remained
"transmitted to Congress for 90 days of continuous session review"
with no reported completion or entry into force yet noted. https://www.klgates.com/thought-leadership/United-States-Opens-a-New-Chapter-in-Civil-Nuclear-Cooperation-With-the-Kingdom-of-Saudi-Arabia-9-21-2026
BOTTOM LINE: The historical base rate strongly favors eventual entry into force (Congress has never formally disapproved a 123 agreement), but the "continuous session" clock plus comparable precedents (UAE ~7 months, China/India far longer) suggest the standard process alone would likely not conclude before January 2027 if counting from the late-August 2026 transmittal, and the added non-statutory Abraham Accords contingency introduces a real, non-trivial risk of delay or non-completion within this window.
NOT FOUND: No confirmed exact "clock" end-date for the 90-days-of-continuous-session period given the actual 2026 congressional calendar/recesses; no confirmed report of an actual diplomatic-note exchange or other formal "entry into force" step for the US-Saudi agreement as of the search date.
report: yes case
YES means: The Section 123 U.S.–Saudi civil nuclear cooperation agreement (signed 2026-07-22) completes congressional review without a disapproval resolution becoming law, and is confirmed by a Source Agency to have entered into force and become legally operative between the two governments before 2027-01-01.
- [2026-09-01] The Arms Control Association's updated FAQ confirms the statutory default:
"The Atomic Energy Act requires Congress to review the deal for 90 days before it enters into force. Congress can do nothing, pass a joint resolution to approve the deal, pass a joint resolution of disapproval to block the deal, or seek to modify its terms."
Silence by Congress is legally sufficient for entry into force — no affirmative action is required, which is the single most likely path to YES.
- [2026-09-01] The same ACA analysis states plainly that
"Without Congressional action to block the nuclear cooperation agreement or modify its terms, the deal will enter into effect after 90 days."
This sets a clear default outcome favoring YES absent an active blocking vote.
- [2026-09-18] Discovery Alert's analysis lays out why the blocking path is exceptionally hard: opponents must get disapproval resolutions through both chambers, then either a presidential signature (impossible, since Trump champions the deal) or a two-thirds override in both chambers — a bar that has never been cleared for any 123 agreement, including prior disapproval attempts against the China and Russia pacts, both of which "entered into force once their review periods expired" (https://discoveryalert.com/analysis/us-saudi-nuclear-deal-congress-september-2026/).
- [2026-10-02] Reuters-sourced reporting (via Spokesman-Review) confirms bipartisan senators Merkley, Kaine, Markey, Coons and Van Hollen have already locked in a floor vote expected "before Dec. 13," within the statutory 90-day window that began Sept. 14 — meaning the review mechanism is on a fixed, near-term track that comfortably concludes before the Jan. 1, 2027 deadline, leaving roughly two and a half weeks of buffer.
- [2026-09-18] Discovery Alert notes that although House Democrats introduced a disapproval resolution before the Nov. 3 midterm recess, "the resolution... arrived just before House Speaker Mike Johnson dismissed members," pushing any House floor action into a lame-duck period — but even the lame-duck calendar is likely to resolve inside the window needed before Jan. 1, since the statutory clock itself (not a forced vote) governs automatic entry into force.
- [2026-09-01] ACA confirms this is a "non-exempt" agreement under the AEA framework (prior reports), meaning it needs no affirmative congressional vote of approval at all — only the absence of an enacted disapproval resolution — further lowering the bar to YES relative to "exempt" agreements like the historical India deal that needed extra legislation (Hyde Act).
- [2026-10-02] Reuters/Spokesman reporting shows the objecting senators themselves frame their effort as largely symbolic — "to fulfill its statutory responsibility to study and weigh in" — rather than expressing confidence of actually stopping the deal, consistent with the base-rate history that no 123 agreement disapproval has ever been enacted.
- [2026-09-18] Discovery Alert highlights a structural bipartisan incentive favoring passage: "Republican lawmakers, and some Democrats, frame the agreement as vital for US strategic competition with China and Russia in the Gulf," raising the political cost of blocking it and reducing the odds of a successful disapproval vote.
- [2026-07-22] The underlying agreement was the product of
on-and-off discussions with Saudi Arabia regarding a possible 123 agreement for nuclear cooperation since 2012
era negotiations finally concluded; both governments, including Energy Secretary Chris Wright, have publicly expressed intent to see the deal through, giving the executive branch's own incentive structure to pursue quick entry into force once the review period lapses, unlike the 2008 Bush-Russia withdrawal precedent which occurred amid an active bilateral rupture (Georgia invasion) not present here.
- [2026-10-05] No new information surfaced suggesting the Abraham Accords condition has hardened into a formal legal precondition for entry into force; Discovery Alert's "two-track" framing (legal vs. political) argues the agreement "can enter into force once the 90-day review lapses... regardless of normalisation, because the text lacks any such condition" — meaning Trump's Truth Social statement, while a political risk to commercial follow-through, does not by itself block the legal entry-into-force mechanism that a Source Agency would report on.
BOTTOM LINE: The statutory default (automatic entry into force absent an enacted disapproval resolution, which has never happened for any 123 agreement) combined with a Senate vote already locked in before Dec. 13 — well inside the Jan. 1, 2027 deadline — constitutes a strong, evidence-based path to YES, provided only that the standard procedural/diplomatic formalization (comparable to the UAE's post-review diplomatic note exchange) is completed or reported in the remaining weeks of the year.
NOT FOUND: No report confirming the exact calendar date the 90-day continuous-session clock legally expires; no report of a scheduled or completed diplomatic note exchange or other final "entry into force" formality for the Saudi deal; no statement from Saudi Arabia accepting or rejecting Trump's Abraham Accords linkage as a legal precondition; no Source Agency report (as of the data reviewed) stating entry into force has already occurred.
report: no case
YES means: the U.S.–Saudi Section 123 agreement completes congressional review without a disapproval resolution becoming law AND is formally implemented/exchanged as legally operative between the two governments before Jan 1, 2027. This dimension argues the NO case — that the agreement will NOT be legally operative by that deadline.
- [2026-10-08] Pakistan Observer reports the deal remains under its 90-day congressional review (started Aug. 22 per this outlet's count) but
"Apparently the deal faces an impediment as Precedent Trump has conditioned it to KSA's normalization with Israel: and Riyadh disagrees to comply with this stipulation."
This is the most recent (2-day-old) reporting confirming the Abraham Accords linkage is still an active, unresolved impasse, not a settled formality. https://pakobserver.net/us-civil-nuclear-deal-with-riyadh-strategic-implications
- [2026-07-23] PBS/AP reported Trump's post-signature condition was
"unexpected and almost certain to make finalizing the deal complicated."
Nothing in subsequent reporting shows this condition has been withdrawn or satisfied as of early October. https://www.pbs.org/newshour/world/trump-adds-new-condition-to-saudi-nuclear-deal-says-kingdom-must-normalize-relations-with-israel
- [2026-07-23] Carnegie Endowment warned
"as of Thursday morning, the issue of Saudi Arabia joining the Abraham Accords appears to be back in play. If the administration insists upon this linkage as a condition for delivery, the entire deal may fall apart."
This is an executive-branch, non-statutory contingency that operates independently of the Section 123(b) congressional clock — Congress not blocking the deal does not guarantee the administration will treat it as operative. https://carnegieendowment.org/emissary/2026/07/saudi-us-nuclear-deal-abraham-accords-123-agreement
- [~2026-07, dated ~92 days ago] A JINSA analysis documents that Riyadh's posture hardened into
"active opposition to the entire strategic framework that normalization represented, including leading an 'anti-Abraham Accords' bloc"
as regional conflict expanded — indicating no near-term Saudi capitulation on the precondition Trump has attached. https://jinsa.org/wp-content/uploads/2026/07/HM-Insight-7.10.pdf
- [2026-10-02, 8 days old via The Hill] After adjourning for the midterms,
"The Senate is scheduled to be in regular session only eight days in November and 14 days in December"
, which directly threatens the "90 days of continuous session" arithmetic the Dec. 13 projections rely on — fewer session days could push the clock's true expiration past Jan. 1, 2027 even absent any disapproval vote. https://thehill.com/homenews/senate/6121941-senate-adjourns-midterm-campaigns/
- [2026-09-01 update, Arms Control Association] Confirms the statutory mechanic that
"If the 90 days elapse without Congressional action, a 'non-exempt' nuclear agreement enters into effect. If Congress passes a joint resolution of disapproval, the agreement cannot enter into effect"
— but elapsing of the review period is only a necessary, not sufficient, condition; it does not by itself constitute "entering into force" as a bilateral act between governments.
- [2009 precedent, Wikipedia/U.S.-UAE 123 Agreement] Even after congressional review concluded Oct. 17, 2009,
"the UAE cabinet approved the agreement" on Oct. 26, and only "entered into force on 17 December 2009 when the governments exchanged diplomatic notes."
If the Saudi 90-day clock does not even conclude until mid-to-late December 2026 (per the compressed Senate calendar above), a comparable ~2-month follow-on step for formal entry into force would fall in 2027, not 2026.
- [Historical mechanism, Brookings] A prior analysis of 123-agreement timing noted that
the 90-day continuous-session review "can extend well beyond 90 calendar days," and if not completed during the current session of Congress, the agreement would have to be resubmitted to the next Congress and the clock would start again
— illustrating a structural risk specific to a midterm-election calendar year where legislative days are compressed near year-end.
- [Background precedent cited by colleagues, reaffirmed] No Section 123 agreement has ever been blocked by a disapproval resolution, but this cuts only against the "Congress blocks it" NO pathway — it says nothing about the separate "Trump/Saudi fail to consummate due to Abraham Accords deadlock" or "clock/diplomatic-notes timing" NO pathways identified above, both of which remain live and unresolved as of the most recent reporting (Oct. 8, 2026).
BOTTOM LINE: The strongest NO case does not rest on Congress disapproving the deal (historically near-impossible) but on two independent, currently-unresolved obstacles: (1) Trump's self-imposed, non-statutory Abraham Accords precondition, which Saudi Arabia is still publicly refusing as of Oct. 8, 2026, and which the administration could use to withhold final implementation even if Congress stays silent; and (2) a compressed, election-year legislative calendar (only ~8 Senate session days in November, ~14 in December) that casts doubt on whether the 90-day continuous-session clock truly expires by Dec. 13, and whether a UAE-style follow-on diplomatic note exchange could be completed before Jan. 1, 2027.
NOT FOUND: No report of Saudi Arabia agreeing to join the Abraham Accords; no confirmed exact date the 90-day continuous-session clock legally expires given the compressed fall 2026 calendar; no report of any diplomatic note exchange, Saudi cabinet ratification, or other formal "entry into force" mechanism being scheduled or completed for this specific agreement.
3. Forecasters 5 draws · Opus 5.5 + GPT-6 Astra + GPT-5.6 Sol · plain mean
claude-opus-5-5 · high effort
60% conf
| Yes | 9% |
| No | 91% |
(0) No source reports entry into force. The agreement was signed July 22, 2026, transmitted to Congress in late August, and entered the Senate record Sept. 14. It is still inside its 90-day congressional review period, and the resolution-source read finds nothing showing the condition met. (a) About 12 weeks remain before Jan 1, 2027. (b) Status quo is No. Even if Congress stays silent, entry into force needs the review period to lapse and then a formal bilateral act, such as the diplomatic-note exchange that took two months after review in the UAE case. Trump has also said the deal 'will only move forward if Saudi Arabia joins the Abraham Accords.' Pakistan Observer reported on Oct. 8 that Riyadh still refuses that condition. (c) NO scenario: Congress never blocks it, but the administration withholds the final note exchange pending normalization. Alternatively, the 'continuous session' clock, which pauses during long recesses and faces a sparse Senate calendar (about 8 days in November, 14 in December), runs past mid-December, leaving no time to finalize. (d) YES scenario: the review lapses around Dec. 13 without an enacted disapproval, which has never happened for a 123 agreement. Trump then quietly drops the Accords linkage and the governments exchange notes before year-end, reported by a Source Agency. Kalshi is at 12% (bid 8/ask 16), down 18 points in 30 days, and Polymarket's same question is at 10%. The research supports these low prices, particularly the active Saudi refusal and the post-review formalities, so I sit slightly below the Kalshi mid.
claude-opus-5-5 · high effort
68% conf
| Yes | 10% |
| No | 90% |
(0) Resolution check: no Source Agency has reported entry into force. The agreement was signed July 22, 2026, transmitted to Congress in late August, and entered the Senate record Sept. 14, so it is still inside the 90-day review, and the resolution-source read confirms it has not entered into force. (a) About 12 weeks remain until Jan 1, 2027. The review clock is projected to end around Dec. 13, but the Senate sits only about 8 days in November and 14 in December, which could push the 'continuous session' count later. (b) Status quo is No: even after review lapses, entry into force needs a further bilateral step such as an exchange of diplomatic notes. That step took about two months after review ended in the UAE case. (c) NO scenario: Congress never enacts disapproval, but Trump holds to his stated condition that the deal moves forward only if Saudi Arabia joins the Abraham Accords. Riyadh still refuses as of Oct. 8 reporting, so notes are not exchanged before year-end. Clock or calendar slippage could also push the timing into 2027. (d) YES scenario: review lapses around mid-December, the administration quietly drops the Abraham Accords linkage, and the two governments exchange notes within the last two weeks of December, with Reuters or AP reporting it. Both the compressed timeline and the political condition make this unlikely. The Kalshi price of 12% (bid 8%, ask 16%) and Polymarket's 10% on the same question agree, and the research adds no unpriced information pushing either way. I sit slightly below the Kalshi mid.
gpt-6-astra · high effort
58% conf
| Yes | 12% |
| No | 88% |
I anchor on Kalshi’s 12% YES price (8% bid/16% ask), corroborated by the apparently matching Polymarket contract at 10%, and find no sufficiently reliable unpriced information to justify departing from it. As of October 10, no supplied qualifying report establishes entry into force, but completion is not proven impossible; the resolution-source fetches are nonqualifying think-tank commentary, and signing or congressional submission does not establish legal operability. About 83 days remain before January 1, 2027, during which congressional clearance, any required bilateral formalization, and qualifying Source Agency confirmation must occur. If nothing changes from the documented pending-review status, No wins. A plausible NO scenario is delayed review or executive withholding of finalization over Saudi–Israel normalization, a condition reported by PBS/AP on July 23 and discussed by CNN on August 26; the October 8 Pakistan Observer claim of Saudi refusal is weaker corroboration, not a decisive fact. A plausible YES scenario is review completion around the December 13 timeline cited in October 2 Reuters reporting, no enacted disapproval—a historically unsuccessful blocking mechanism—and prompt finalization and qualifying reporting before year-end. However, December 13 is not independently verified as the statutory continuous-session expiration, regular sitting days are not interchangeable with that clock, and the UAE precedent’s roughly two-month post-review delay before exchanging diplomatic notes undermines claims that congressional silence automatically establishes bilateral entry into force. The 88% NO allocation therefore primarily reflects timing and executive-finalization risks rather than congressional rejection, while uncertainty about the designated Source Agencies and potential reporting lag creates additional settlement risk even if diplomatic progress occurs.
gpt-6-astra · high effort
57% conf
| Yes | 12% |
| No | 88% |
No supplied source documents entry into force as of October 10: the July 22 signing and subsequent congressional submission do not establish legal operability, and the resolution-source read found commentary rather than qualifying confirmation. About 83 calendar days remain before January 1, 2027; if the current unimplemented status persists, No wins. I retain Kalshi's 12% Yes anchor (8% bid/16% ask), corroborated by the apparent same-question Polymarket price of 10%, because the research supplies no sufficiently reliable unpriced information warranting a departure. Reuters' October 2 report of a vote expected before December 13 and the historical absence of enacted congressional disapproval support a viable Yes pathway, but neither establishes the review's expiration date or automatic bilateral entry into force. The timing evidence conflicts: K&L Gates' September 21 analysis specifies 90 days of continuous-session review, which cannot simply be equated with either calendar days or Senate floor-voting days, while the UAE precedent required a subsequent exchange of diplomatic notes. A No scenario is review or diplomatic formalities slipping into 2027, or the administration withholding finalization over the normalization condition reported by PBS/AP on July 23 and CNN on August 26; I do not treat Pakistan Observer's October 8 claim of Saudi refusal as independently established. A Yes scenario requires timely completion of review without an effective blocking measure, prompt fulfillment of the agreement's final legal requirements, and qualifying Source Agency reporting before the deadline, with the normalization linkage satisfied or not enforced against entry into force. The forecast prices reported legal operability rather than political agreement, with meaningful residual uncertainty because the exact review clock, agreement-specific finalization requirements, and designated-agency reporting eligibility were not verified.
gpt-5.6-sol · high effort
58% conf
| Yes | 11% |
| No | 89% |
(0) The resolving condition has not already been met: the resolution-source review found no qualifying report of legal entry into force, and the September 24 Columbia analysis still described such an agreement prospectively. (a) Roughly 82 days remain until January 1, 2027, while the agreement is still undergoing congressional review and the exact expiration of the 90-day continuous-session period is unconfirmed. (b) If nothing changes, the agreement remains non-operative because no exchange of diplomatic notes or equivalent final bilateral step has been reported, making No the status quo. (c) No results if the congressional clock extends beyond year-end, or if Trump withholds final implementation because Saudi Arabia has not joined the Abraham Accords; October 8 reporting says Riyadh still rejects that condition. (d) Yes results if review ends around December 13 without an enacted disapproval resolution—as every historical 123-agreement precedent suggests—and both governments quickly complete the final formalities and a Source Agency reports entry into force before year-end. Kalshi's 12% Yes price is the primary anchor, corroborated by the same-question Polymarket at 10%; I place Yes at 11% because the recent normalization impasse, uncertain continuous-session arithmetic, and UAE precedent for a post-review delay offset the strong statutory default against congressional blockage.
4. Final plain mean of 5 draws
11%
(60% confidence)
Yes: 11%
No: 89%
Mean of 5 draws (0.09, 0.10, 0.12, 0.12, 0.11). (0) No source reports entry into force. The agreement was signed July 22, 2026, transmitted to Congress in late August, and entered the Senate record Sept. 14. It is still inside its 90-day congressional review period, and the resolution-source read finds nothing showing the condition met. (a) About 12 weeks remain before Jan 1, 2027. (b) Status quo is No. Even if Congress stays silent, entry into force needs the review period to lapse and then a formal bilateral act, such as the diplomatic-note exchange that took two months after review in the UAE case. Trump has also said the deal 'will only move forward if Saudi Arabia joins the Abraham Accords.' Pakistan Observer reported on Oct. 8 that Riyadh still refuses that condition. (c) NO scenario: Congress never blocks it, but the administration withholds the final note exchange pending normalization. Alternatively, the 'continuous session' clock, which pauses during long recesses and faces a sparse Senate calendar (about 8 days in November, 14 in December), runs past mid-December, leaving no time to finalize. (d) YES scenario: the review lapses around Dec. 13 without an enacted disapproval, which has never happened for a 123 agreement. Trump then quietly drops the Accords linkage and the governments exchange notes before year-end, reported by a Source Agency. Kalshi is at 12% (bid 8/ask 16), down 18 points in 30 days, and Polymarket's same question is at 10%. The research supports these low prices, particularly the active Saudi refusal and the post-review formalities, so I sit slightly below the Kalshi mid.
Pipeline Timing
Total pipeline time: 128.4s
Per-tool research timings shown in the Research section above.