Ledger
What happened, and when.
Real entries only, newest first. Times are UTC. Each entry links to its receipts. Corrections are added as new entries; old ones are never edited.
· report
The Watched Check, version 2.1, shared by public link
The incident and design report, unchanged from version 2.1 of 29 September, with a dated note on where the work led.
· released
Experiment 0 published
The write-up, the benchmark and the evidence dataset went public, with the sealed predictions.
· ran
Experiment 0: first counted run
Over an hour after both seals were in Bitcoin blocks.
· sealed
Experiment 0: five more predictions sealed
An addendum for two larger models and GPT-6.1, in Bitcoin block 969403 (about 06:02 UTC).
SHA-256 fingerprint:
9cf308ce46d4aad0149d7c387488ddbaf209641d7950b84c0cb1225339064fb8· sealed
Experiment 0 sealed
The logs, prompts, scorer, run plan and nine predictions, in Bitcoin block 969401 (about 05:50 UTC).
SHA-256 fingerprint:
3928d5249adb224ec621d8dad757ac623421c1eaa65f58be4f960beec6b96553· anchored
Incident report, version 1.6, anchored in Bitcoin
Version 1.6 of the incident report, in Bitcoin block 966450 (about 03:45 UTC). That file and its proof are not published yet, so this anchor cannot be checked from outside.
SHA-256 fingerprint:
f52d2e6c6e4065529d3224e3eeeeba26da195c488680632aaa1a7caba64f44de· incident
The incident: six AI coding sessions on one machine
Written rules asked each session to stay in its own folder, and nothing in the operating system enforced them. One session reached toward the others' work, and the vendor's safety filter refused its listing. The wall and the witness were built from the next day.