Timothy B. Lee called it:
“I expect the same will be true for Tesla — the first truly driverless Robotaxis will arrive in 2026, but technical and logistical challenges will limit how rapidly they expand.”
We find out by Dec 31, 2026. 132 days to go
Timothy B. Lee: “I expect the same will be true for Tesla — the first truly driverless Robotaxis will arrive in 2026, but technical and logistical challenges will limit how rapidly they expand.”
MET if Tesla begins offering paid Robotaxi rides to the general public in at least one city with no Tesla employee inside the vehicle (no driver and no safety monitor). Rides with an in-car safety monitor, employee-only or invite-only pilots, and demonstrations do 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
Settles TRUE if, on or before December 31, 2026, Tesla offers Robotaxi rides to members of the general public in at least one city in vehicles with no Tesla employee on board (no safety driver and no safety monitor in the passenger seat). Rides limited to employees or invited testers, or rides with a Tesla safety monitor aboard, do not count.
Quote verified against the source
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 understandingai.org ↗
Prediction #11 (70% confidence), headlined 'Tesla will begin offering a truly driverless taxi service to the general public in at least one city'.
History — append-only
Proof
2 hashes from this record to the anchored root
- 0x722e4fa0ab02f23675a561af585f8ab31a77f1a0a9179c9939c8fe8fbfbef160
- 0xc55bf97909cfe07b387b6a7abb33a1cdb0fd1d0406d0dc97b193976d6ba68ed0
batch #54 manifest · 4 entries
the contract refuses any batch that doesn’t follow the previous one, and has no function to edit or delete one — including for us
0x155646d7…64eda5 on block explorer
view the canonical capture · the page as served to us, kept verbatim and covered by the evidence hash
✓ 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.
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