“Now, all of this is contingent on Google, Microsoft, Amazon and Oracle building enough capacity to capture that revenue, but if we assume that happens, OpenAI needs more than $147 billion just to handle its expected compute commitments through the end of 2027.”
Our reading:
If hyperscalers build enough capacity, OpenAI needs over $147 billion for compute commitments through end of 2027.
Assessment: Unresolved Not yet due
What happened
Did the forecast come true?
Outcome: Unresolved
We checked, and the evidence so far doesn’t settle it.
Judged on a plain reading. They named no measure, so we used the reading a typical informed reader would take. It is spelled out under “How we judged it”.
Evidence up to . Checked .
Why
On February 27, 2026, OpenAI announced a $100 billion expansion over eight years to its existing $38 billion AWS agreement [e1]. The announcement does not isolate payments required for July 2026 through December 2027 [e1]. It also does not establish sufficient delivered capacity across Google, Microsoft, Amazon and Oracle [e1]. This evidence cannot settle the $147 billion threshold or satisfy the early-resolution rule [e1].
Caveats
- The packet does not establish whether the capacity condition has been met.
- No complete payment schedule isolates qualifying obligations for July 2026 through December 2027.
- The underlying analyst estimates and their fiscal-to-calendar reconciliation are unavailable.
Evidence (1 item)
Context only: OpenAI,
by $100 billion over 8 years.
Why it matters: The disclosure establishes a large AWS agreement, but its eight-year scope differs from the forecast's payment window. It cannot establish either the USD 147 billion total or the capacity condition.
- Publisher
- OpenAI
- Kind of source
- Company disclosure: the company describing itself, not an independent finding
- Measures
- OpenAI, Additional AWS agreement commitments over eight years, USD billions, company reported, ? to ?
- About events on
- Published
How we judged it
- Kind of claim
- Conditional forecast
- Deadline
- “through the end of 2027”
- As of 2026-11-01
- Not yet due
Conditions
- if hyperscalers build enough capacity (their words)
Where we had to interpret
- The threshold concerns cumulative payments required for compute from the four named providers, not OpenAI's total operating spending.
- The surrounding year-and-a-half calculation is read as July 2026 through December 2027. The forecast horizon itself begins on the post date.
- Payments for separately excluded providers and activities are not added to the threshold.
- The capacity condition requires delivery sufficient to trigger the assumed payment obligations; announced construction plans do not establish it.
Right if: The capacity condition is established and qualifying contractual payments required for the assessment period exceed USD 147 billion.
Wrong if: The capacity condition is established and a complete, consistently dated accounting of qualifying payment obligations totals USD 147 billion or less.
We wrote this test before the deadline, while the outcome was unknown.
What would settle it
Evidence establishing sufficient delivered capacity, together with binding payment schedules or reconciled payments for the four named providers. The records must establish whether required payments for July 2026 through December 2027 exceed $147 billion, without double counting or including amounts outside that period.
We found 66 claims in this post. See them all.
Full record
Source and dates
Where's Your Ed At, What Happens If OpenAI Dies?, paragraph 59.
- Said
- We read the source
- live page, full text, public
- Evidence up to
- Checked
We read this wording on 2026-10-28. The post may have been edited after 2026-08-18.
Where it was said (1)
Said once in the posts we read.
: Where's Your Ed At, What Happens If OpenAI Dies?
Now, all of this is contingent on Google, Microsoft, Amazon and Oracle building enough capacity to capture that revenue, but if we assume that happens, OpenAI needs more than $147 billion just to handle its expected compute commitments through the end of 2027.
- Where
- paragraph 59
- Published
- 2026-08-18
- We read it
- , live page
- Access
- full text, public
History
Versions
- Current: Unresolved. Evidence up to 2026-10-28.
What happened to this record
PublishedBy us
Published after both AI reviews and the final check passed.
Held backBy us
Both reviewers disagreed with the draft’s verdict.