Leadership Under Uncertainty

AI data centres · All records

The numbers are stated judgments. The record began on 12 October 2026 with starting confidences that a model set in a single reading, from its general knowledge and up to ten developments for each assessment retrieved in the three weeks before (some first reported earlier), and a published rule has made every change since. They are not measured probabilities. The question and the rule are fixed before the record begins, and each change shows its evidence and its reasons. The rule and what is not claimed are on the method page.

A corrected record of the same question began on 15 October 2026: AI data centres (version 2). A review found that this record started from one reading, never challenged, that counted one story several times, and that one of its causal factors could be read both ways. This record continues unchanged under the rules it began with.

Checking the daily state of 13 October 2026 (day 1)

Fingerprint . In the fingerprint of 13 October 2026, published on GitHub. See the record on its page.

Six steps

What your browser checks

The record is fingerprinted in the daily fingerprint of 13 October 2026, which gathers every record of that kind not yet in an earlier one. A record may therefore sit in a later day’s fingerprint than its own date, and this page gives the later date.

  1. 1
    Canonical bytesChecking
    The record is written out byte by byte under the recipe it names.
  2. 2
    FingerprintChecking
    SHA-256, computed by your browser, compared with the record’s fingerprint.
  3. 3
    Path to the day's rootChecking
    The fingerprint is folded through its neighbours to the root of the day’s tree.
  4. 4
    The published rootChecking
    Fetching the published file from raw.githubusercontent.com…
  5. 5
    Shape of the treeChecking
    A path in a tree of depth d needs d minus 1 steps.
  6. 6
    An outside clockChecking
    Asking GitHub when the commit was pushed…
Show the record’s canonical bytes
(computed in your browser when the check runs)
On your own machine

Run the check offline

Download the record and its proof, and the script that checks them. The script has no dependencies and needs Node 18 or later. Put both files in one folder and run, in that folder:

node verify-inclusion.mjs record-and-proof-64d42df20955.json

The script repeats the first five steps above on your machine. It recomputes the fingerprint from the record, folds the path through the day’s tree, fetches the published file from GitHub at the anchor commit and compares the roots, and then asks GitHub whether that commit is on the main branch of the anchors repository. It trusts only the repository named inside the script, never one named in the file, and it does not read the push time, which step 6 above shows. It exits with 0 when the record is included, 1 when it is not or the file names other coordinates, and 2 when GitHub cannot be reached or the file cannot be read.

Download verify-inclusion.mjs

The record is saved as record-and-proof-64d42df20955.json.

The chain

The record before it

This record names the daily state of 12 October 2026 (day 0) by its fingerprint. The link alone does not stop both being replaced together. What does is publication: once a fingerprint is in a file pushed to GitHub, a replacement no longer matches it. Check that one.