Force Majeure: The 'Superior Force' Clause Now Pricing AI Infrastructure Risk

A centuries-old contract doctrine excusing performance during wars, disasters, and 'acts of God' is being invoked by Oracle over a Stargate AI data center — a use commentators call unusual for a project with no war or disaster, only permitting delays.

Created 2026-09-24 Last reviewed 2026-09-24

What it is

Force majeure — French for “superior force” — is a contract clause that excuses a party from performing its obligations when extraordinary events outside its control make performance impossible or impracticable. The doctrine covers what common law calls “acts of God” (earthquakes, floods, hurricanes) alongside human events such as war, government seizure, or epidemic. Cornell Law School’s Legal Information Institute defines it as language exempting parties “for non-fulfillment of their obligations as a result of conditions beyond their control, such as earthquakes, floods or war.”

Crucially, invoking the clause does not usually terminate a contract outright. It suspends or modifies performance — commonly payment obligations or delivery deadlines — for the duration of the triggering event. The clause must typically be written into the contract in advance, and the event must genuinely prevent performance, not merely make it costlier or less convenient. Courts and commercial parties have historically read these clauses narrowly: a party cannot invoke force majeure simply because a project has become inconvenient or expensive to finish on schedule.

The clause is a fixture of energy and commodities contracts in particular, where pipelines, power plants, and long-term supply agreements are exposed to genuinely unpredictable disruptions — storms, sanctions, sudden regulatory bans. That sectoral home is what makes its appearance in AI infrastructure financing notable: the clause is migrating from contexts built around unforeseeable catastrophe into contexts built around ordinary, foreseeable construction and permitting delay.

Why it matters for AI governance and narratives

The triggering event here was Oracle’s force majeure notice to Blue Owl Capital over Project Jupiter, a Stargate data center campus in New Mexico, allowing Oracle to defer payments if the facility misses its 2028 target [as referenced in the editorial’s citations WEB-39501, POST-480206, POST-480138]. The site has been delayed by a stalled natural-gas pipeline (now targeting February 2027) and contested air-quality and water permits, with a further permitting decision due in late 2027. None of that is a war, an epidemic, or a natural disaster — the traditional triggers the doctrine was built for. That gap is precisely what analysts flagged as unusual, and it is editorially significant for the observatory’s purposes: a legal instrument designed for the genuinely unforeseeable is being used to manage the ordinary, foreseeable friction of building AI infrastructure at speed — regulatory permitting, community opposition, supply-chain timing. When a hyperscaler reaches for wartime-contract language to hedge routine construction risk, it is itself a signal about how confident capital actually is in the 2028 timelines driving AI infrastructure narratives, and it gives insurers and lenders a new data point for pricing data-center risk upward, as subsequent coverage of the episode noted.

Key facts and dates

Where to learn more

Sources

Authoritative, citable legal reference defining the doctrine and its scope.
Primary journalistic account with direct detail on the notice, parties (Oracle, Blue Owl Capital), and project timeline.
Independent confirming coverage with market-reaction detail.
Secondary corroboration citing Bloomberg's original reporting, useful for triangulating facts across outlets.
Referenced in: Editorial No. 340