Rob Toews called it:

“Sam Altman will step aside as CEO of OpenAI.”

We find out by Dec 31, 2026. 126 days to go

Open

Rob Toews: “Sam Altman will step aside as CEO of OpenAI.”

🔒 The test · locked Aug 28, 2026

MET if Sam Altman ceases to be CEO of OpenAI, or OpenAI/Altman publicly announce his departure or transition out of the CEO role. Adding co-CEO or divisional 'CEO of Applications' titles beneath him, or Altman remaining CEO while delegating duties, does not count at any point, before 2026-12-31 23:59 (UTC).

Settles by documented review of public evidence against these locked criteria; the reviewer is named and the reasoning published.

Test details
Settled byevidence
Window2026-01-01 → 2026-12-31
TimezoneUTC
Data vintagelatest_revision
Min source tier1
Contract hash0x9b96b3bd…ec07c4
Full resolution criteria

Resolves TRUE if, at any point between January 1, 2026 and December 31, 2026, Sam Altman ceases to hold the title of Chief Executive Officer of OpenAI, or OpenAI publicly announces in that window that he will do so. Retaining the CEO title throughout 2026 with no announced transition resolves FALSE.

Submitter-attested — no machine-readable source

Rob ToewsForbesSaid Dec 22, 2025Added to Thonest Aug 28, 2026Anchored Aug 28, 2026

Added by Thonest from a public source. The person quoted did not submit, approve, or endorse this record; the wording is verified against the source itself.

Read the original on forbes.com ↗

Reactions are about the record being worth keeping — never about whether the person was right. They are never counted for or against anyone, and never used to rank anything.

Discussion

Loading…

Heading of Prediction No. 7 in Rob Toews' Forbes column '10 AI Predictions For 2026', which forecasts a choreographed CEO transition during 2026.

History — append-only

2026-08-28
Recorded · Recorded and locked from the original source

Proof

Evidence hash0x835b62b8…80a7ed
Source snapshot—
Record fingerprint0x835b62b8f159591382738de215453f563b55f2afaca9c9c127e705dfb380a7ed
Proof path
4 hashes from this record to the anchored root
  1. 0x62c6a3b5412bf0bd0f0c8838fea3380d8a166bf3c7a517f65520f87aeeaa55a8
  2. 0xa0f2829e1aa696c1692e399db921ea251a24529d28da7965397f05508345892b
  3. 0x22faf42c69d797f1419a052fc2e05c6df26eb8e5f2178027ec3eee37a1639040
  4. 0xdb92b26db67a0ec1b41aa786452235f20366840e9fccd1392348538ab0a332a6
Merkle root0x6d72bec9980deceafe4603c764311d29e367c03ff2b0713d64b440285e267679
batch #103 manifest · 10 entries
Registry0x3d74d9e2f0f4c741fc49b34cc119b6db0cef47c0 · entry #110
the contract refuses any batch that doesn’t follow the previous one, and has no function to edit or delete one — including for us
Anchored onchainbase-mainnet · Aug 28, 2026
0xf6d50a6e…8a4bee on block explorer
Original sourcehttps://www.forbes.com/sites/robtoews/2025/12/22/10-ai-predictions-for-2026/
Third-party archiveInternet Archive copy · Aug 6, 2026
Quote checkThe source could not be read automatically (video, audio, or a site that blocks retrieval), so the wording rests on the submitter and the original link.

✓ The anchored proof cannot be rewritten, and the published record is append-only by default. Everything that happened afterward is in the history above — corrections are appended, never silently edited in.

Verify this record yourself

The check runs in your browser and reads the anchored root straight from a public Base node — not from Thonest. How this works.

Disputes

No disputes have been filed. If something here is wrong — a misquote, a wrong date, a misattributed source — say so and it gets answered on the record. How disputes work.

Related

OpenAISam AltmanFidji Simo