Document

Leg B ledger: first reading, 9 October 2026

A working document. It is one of the documents the site is built from, published as it is written for anyone checking the work, and it uses the project's own shorthand. The plain account of the same material is on the home page.

Leg B ledger: first reading, 9 October 2026

Method: docs/leg-b-ledger-method.md (committed before any row was built). Rows: data/leg_b_ledger.csv. Numbers: python3 scripts/leg_b_ledger.py. Every verdict is the agent's judgement; the rows record the evidence and the gap so I can overrule any one. Revised the same day after an independent check of the pull request, and closed by my rulings of 12 October 2026 (both at the end).

The answer

The singularity definition said the 2016 survey's milestones "mostly arrived early". The ledger does not support that as written. Every milestone that has arrived came early, but more milestones are past their forecast date and still not here than have arrived at all. (The sentence was amended on 12 October 2026, amendment A23 in docs/amendments.md; see the rulings at the end.)

verdict count
arrived (every stated condition met) 1
arguably arrived (main capability met, exactly one condition unmet or untested) 5
not arrived 22
no bar (the description sets nothing a demonstration could be checked against) 4

Of the 22 not arrived, 11 are past their forecast date, so they are already late, and 11 are not yet due.

Counting the 5 "arguably arrived" milestones as arrived, 17 forecasts can be judged so far: 6 came early and 11 are late, and all 11 late ones are milestones that are overdue and have not arrived. Counting only the one clean arrival, 1 came early and 16 are late. So the totals tip late only because overdue milestones count as late. Of the arrivals alone, all came early.

The split is by kind of task:

So the experts were too slow on what speech and language models went on to do, and too fast on robots and on narrow game-playing goals that the field stopped chasing.

What the headline rests on

Four rows were "arguably arrived" in the first draft and are now "not arrived", because each names more than one unmet or untested condition and the method allows only one: video from a new viewpoint, the Putnam maths competition, the high-school essay, and answering factual questions from the internet. Two of them (video and Putnam) are not yet due, so moving them changes no early-or-late count. The other two are overdue either way unless their dates count.

The factual-questions row matters most. Its only demonstration is from April 2025, and the agent found nothing earlier that compares a system with people who had internet access on simple factual questions. Its forecast date is 9 September 2023. If I count it as arrived and an earlier demonstration dated before about September 2023 turns up, it moves from late to early: 7 early and 10 late. If all four rows were counted with their current dates, the totals go back to the first draft's 9 early and 10 late. Either way, the milestones that arrived mostly came early, and the overdue ones are what tip the totals.

Scored by lead time

The ratio is actual time divided by forecast time; under 1 is early.

forecast lead early late, arrived overdue, not arrived not yet due not scored
under 5 years 1 0 1 0 0
5 to 10 years 5 0 9 0 2
10 years or more 0 0 1 11 2

(Generous reading. Four of the six arrivals came within a factor of two of their forecast; the two outside it, Atari and poker, both came far earlier.)

The forecasts of five to ten years ahead are the ones that can be checked now: 5 arrived, all early, and 9 are overdue. Most longer forecasts are not yet due. There are too few yes-or-no events to find a lead beyond which the forecasts stop working, so this ledger records which way the forecasts missed. It does not give a forecast horizon.

Where the agent's judgement matters most

Rulings (2026-10-12)

These were the open questions put to me on 9 October. He ruled on 12 October 2026, in his words "all as recommended": each answer below was the session's recommendation and I approved it, so the authorship is mixed. The questions are kept as they were asked.

  1. The four milestones left unscored (sorting long lists without the form of the solution, grouping unseen objects, answering questions with no definite answer, explaining game moves): give each a bar, or keep them out.

    Ruling: keep them out. They stay out of the scores and their verdict is recorded as "no bar" (it was "left for me" until this ruling). A bar set now would be chosen after seeing the answers, which is the thing the method was written to avoid.

  2. The five "arguably arrived" rows: which count as arrived?

    Ruling: none is promoted. The five rows stay "arguably arrived", and the strict total (only clean arrivals count) and the generous total (arguably arrived counts too) both keep being reported, as the method says.

  3. The one-condition rule: should the method get a fifth verdict (for example "partly arrived") for a demonstration of the main capability with more than one gap, or allow more than one gap under "arguably arrived"? Either is an amendment, and either would bring back the four rows moved on 9 October.

    Ruling: no fifth verdict. The one-condition rule stays as written, and the four rows moved on 9 October (video from a new viewpoint, the Putnam, the high-school essay, answering factual questions from the internet) stay "not arrived" with their nearest demonstration recorded.

  4. The singularity definition's sentence "Milestones from the 2016 Grace survey mostly arrived early" holds for the milestones that arrived, but not for the survey as a whole. Reword it (an amendment), or wait for the rulings above?

    Ruling: amend it now, dated. The sentence now says that the milestones that arrived came early, that most of the survey's milestones have not arrived, and that eleven are overdue. Recorded as amendment A23 in docs/amendments.md, citing this ledger.

  5. Leg B's gauge is defined on forecasts of METR's task-length measure, which this ledger cannot supply. Is this ledger the record of which way forecasts missed and nothing more, or should it feed the gauge somehow?

    Ruling: the record of which way forecasts missed, and nothing more. Leg B's gauge stays defined on the task-length measure, and this ledger does not feed it.

Revisions after the independent check (9 October 2026)

Rendered from docs/leg-b-ledger-2026-10.md at version a7bd17a.