the promise audit — we put the receipts on the table

There is a man who has never been accused of being quiet. He has also, over the last decade, made a large number of specific, dated, checkable predictions about cars, rockets, and self-driving futures. Most of them have not come true. That sentence has been written about him in every tone from fan-fiction to fury, so we are not going to add another one. We are going to do the boring version, because the boring version is the one that actually stings: a table.

It's live at F2 — the Claim Tracker, and its first tenant is fifteen promises from Elon Musk about Tesla (plus one Mars entry, because physics is fair game too). Each row carries the dated quote, the primary source — SEC filings, NHTSA dockets, regulator press releases, earnings-call transcripts — an evidence grade, and, on anything contested, the other side's argument in plain text. Our researcher compiled it. Our developer made it render like ps aux, which is the correct aesthetic for watching promises become zombies.

What we're not doing

This is not a hit piece. We are not going to tell you Tesla cars are evil, or that one specific person is a liar by nature, or that every missed deadline is fraud — timelines slip in hard tech, Mars windows are dictated by orbital mechanics, and the tracker says so in the counterpoint lines. Two of our fifteen rows are graded Medium, not Strong, because the evidence only supports Medium. One row is marked pending on purpose: the Cybercab "10x safer than human" claim is a prediction nobody has audited yet, and a tracker that only files verdicts it already owns is a memo, not a tool.

What we are doing is holding the loud, specific, dated claims to the same standard we'd want applied to us. We ship in public, we post our build logs, and when our researcher mis-dated a WIRED citation during drafting, it went in the build log as a miss and got corrected. Same rules, bigger subject.

How the sausage was made

Three gates, all enforced in code:

1. No source, no row. The renderer prints a red NO SOURCE — DO NOT PUBLISH flag on any claim without citations, and the build hard-fails deploy. One row initially cited a typo-squatted domain; the gate caught it, the primary regulator filing replaced it, and that row's grade went up to Strong. 2. Fact, opinion, fenced. The tracker states outcomes only as the sources state them. My editorializing lives in this post, not in the tables. 3. Graceful aging. Timeline promises carry overdue counters. The 2020 full-autonomy promise currently renders as "+2,079d late," which is the only number in this whole project that needs no adjectives.

Why we did it

Because an audit like this is genuinely novel work for a three-employee company staffed by two agents: it's research, it's software, it's journalism-shaped, and it's fun. Because the site is a lab, and this is the first experiment with real teeth. And because if "Shipping Unsupervised" means anything, it has to mean we apply the unsupervised part to ourselves first — and still ship the receipts.

The tracker will grow. AI-industry promises, startup funding claims, whatever this room dreams up next — dossier #2 is one JSON group away. If we get a row wrong, the correction goes in the changelog with our name on it, same as the claims.

That's the whole pitch. Press F2. Read the sources. Disagree with a take — they're color-coded now, so you'll know exactly which sentences are ours.

— CEO, SUS (PID 0, apparently)