Project Jupiter’s Force-Majeure Notice Turns ORCL Options Into a Contract-Clock Study

The headline date and the project clock are different events#

Bloomberg reported on September 24 that Oracle had sent a force-majeure notice to the Blue Owl Capital unit developing Project Jupiter in New Mexico. The reported purpose was narrower than abandoning the campus: Oracle was seeking protection from payments if the project were derailed and failed to come online on the planned 2028 schedule. Reuters reported the same account and said Oracle maintained that Project Jupiter remained on schedule and that it was fully committed to the site. That distinction changes the options question. The event is not simply the September 24 headline. The economically relevant uncertainty is conditional and long dated: whether a project milestone tied to 2028 is missed, what that does to Oracle's obligations, and whether the market can isolate that risk from the much larger set of factors already embedded in ORCL volatility. The first useful test is therefore not whether call or put activity looked dramatic on the day of the report. It is whether the listed expiration calendar actually spans the contractual risk window.

Project Jupiter already had a complicated operating timeline before the force-majeure report. Oracle says the campus is designed around more than two gigawatts of Bloom Energy fuel-cell power after it replaced an earlier natural-gas-turbine plan. Oracle's current data-center page also says customer delivery in Doña Ana County begins in the first half of 2027.

Bloomberg's report, by contrast, describes the notice as protection against a failure to come online on a planned 2028 schedule. Those statements do not necessarily conflict. A campus of this scale can have phased delivery, commissioning, and contractual milestones that occur at different times. But without the notice itself, the exact milestone that would activate Oracle's claimed protection is not public.

The regulatory clock also needs care. Project Jupiter has faced litigation and permitting disputes, yet the New Mexico Supreme Court on September 17 denied petitions in two Project Jupiter cases and lifted stays entered in August. Describing the project simply as blocked would therefore be stale. The more defensible research frame is that the project has faced changing permitting and infrastructure constraints while construction and legal processes continue.

For options research, this means September 24 is an information event inside a longer sequence. An expiration that ends before the relevant project milestone cannot fully represent the same uncertainty as an expiration that survives beyond it.

January 2028 contains the most ORCL open interest but not the full 2028 window#

ChartExchange's ORCL option-chain summary at 10:00:01 a.m. EDT on September 24 showed four listed expirations at or beyond January 2028. Summing displayed call and put open interest across moneyness buckets gives 262,784 contracts for January 21, 2028, 58,898 for September 15, 2028, 44,163 for December 15, 2028, and 1,759 for January 19, 2029.

The asymmetry is the useful observation. January 2028 has by far the largest displayed open-interest base among those maturities, yet it expires near the beginning of the calendar year that Bloomberg's report makes relevant. September and December 2028 span progressively more of that year. January 2029 is the first listed expiration in this set that survives beyond the entire 2028 calendar year.

That does not make January 2029 the most informative contract today. Its displayed open interest is tiny relative to January 2028, and open interest alone says nothing about executable depth, bid-ask quality, or the amount of project-specific variance embedded in price. It does show why a generic reference to "long-dated ORCL options" is too imprecise for this catalyst. Different maturities are observing materially different portions of the project clock.

This is a horizon-coverage problem before it becomes a volatility-pricing problem.

Open interest cannot tell us whether traders are pricing a Project Jupiter delay#

The Options Industry Council defines open interest as the number of contracts that remain open after accounting for opening, closing, exercise, and assignment activity. It is different from same-session volume. That distinction prevents a common analytical error here.

The large January 2028 open-interest total does not establish that market participants are focused on Project Jupiter. The positions could have been created for earnings, cloud demand, artificial-intelligence spending, rates, index exposure, hedging, multi-leg structures, or other company-specific risks. The smaller late-2028 totals likewise do not establish that the market is ignoring the data-center issue.

There is an especially strong alternative explanation for the maturity pattern: expiration age. January 2028 contracts have had more time to accumulate positions than later maturities. Newly listed or younger expirations can naturally have less open interest even when they overlap an economically important event.

A valid event study therefore needs a baseline. The relevant comparison is not January 2028 versus January 2029 in isolation. It is how late-2028 and January 2029 open interest, implied volatility, skew, and quoted liquidity evolve relative to their own pre-notice levels and relative to adjacent maturities as new Project Jupiter milestones arrive.

The transmission map extends beyond Oracle, but the exposures are not interchangeable#

The force-majeure notice directly concerns Oracle's relationship with the Project Jupiter developer, so ORCL is the cleanest listed market for the reported payment contingency. Other public companies sit on different parts of the transmission path.

Blue Owl is tied to the project's development and financing through STACK Infrastructure. Bloom Energy is tied to execution of the revised power design because Oracle publicly identified Bloom fuel cells as the planned power technology. Those relationships create different research questions rather than three versions of the same exposure.

If future information concerns Oracle's payment obligations or tenant commitment, ORCL is the direct company-level market. If the issue shifts toward project financing, capital commitments, or developer economics, Blue Owl becomes more relevant. If the uncertainty centers on delivery of the fuel-cell power architecture, Bloom Energy becomes a different operational exposure.

Cross-market comparison is useful only when the catalyst reaches each company through a documented mechanism. A shared "AI data center" label is not enough.

The next test is whether late maturities reprice around project milestones#

The current evidence supports a structural conclusion, not a directional one. The reported contingency reaches into 2028, while the most populated ORCL long-dated expiration in the current chain ends in January 2028. Later expirations cover more of the reported risk window but currently carry much less displayed open interest.

To determine whether Project Jupiter begins to create a separable options premium, a future study would need matched observations around identifiable milestones. The useful measurements would include end-of-day midpoint-based implied volatility, normalized-delta skew, quoted spreads, open interest after the clearing update, and the same metrics in adjacent expirations. A pre-event baseline is necessary because ordinary changes in ORCL volatility could otherwise be misattributed to the project.

The strongest falsifying evidence would be persistence of the same maturity pattern through major Project Jupiter updates with no relative change in the expirations that actually contain the 2028 window. That would weaken the idea that listed ORCL options are isolating this project risk, even if the project remains economically important to Oracle.

The force-majeure report therefore creates a research opportunity that is narrower than the headline. The question is not what the notice predicts for Oracle. It is whether a long-duration contractual contingency can become visible in an option market whose deepest long-dated positioning currently sits before much of the relevant 2028 clock has elapsed.