It scored 2,928 chess moves overnight from nothing but a usernameIt scored 2,928 chess moves overnight from nothing but a username
August 5, 2026 · Everything here happened between 23:33 and 01:41, unattended. It even did the one step I had reserved for myself, correctly.All of this happened overnight while I slept. It even did the one part I had set aside for myself, and got it right.
last updated
The step I had reserved for myself
The chain was meant to stop at installing a chess engine, marked as mine on the theory that an unsigned download needs a human to clear it past the operating system. It did not stop, and it was right not to: it installed the engine alongside the other tools this machine already trusts, in the directory every scheduled job here already puts first on its path.
That is the part worth recording. The ticket was mine because of an assumption about permissions, and the assumption was wrong.
Every half-move, through the engine
It picked up the scoring ticket the moment the install closed. The engine runs locally over every half-move of every game, throttled to yield cores under contention rather than idling the machine, which is the difference between a job you can leave running and one you have to babysit.
Five patterns, thirty-nine citations, none taken on trust
Then one hop further into the actual point of the project: not “you hung a rook on move 23” but the habit underneath it. The aggregation happens first, in plain deterministic code with no network in it, so the evidence pack is testable for free and a dry run shows exactly what would be sent.
Every finding has to cite specific moves from that pack. Over the real store it returned five patterns and thirty-nine citations with none rejected. An earlier ticket had left one question open with an explicit warning not to derive a time-pressure signal before confirming what the clock annotations meant, and that warning was honoured rather than guessed past.
Weekly, gated on content rather than the calendar
The digest pulls, imports, evaluates, synthesises and pushes the result. But the window is not the cadence. If no games changed, it declines to re-synthesise and says nothing, which is what keeps a weekly message worth opening. Verified against the real store: 92 archives all unchanged, three games newly scored, and the gate correctly declined.
What it actually still needed me for
Two things, and it is worth being exact rather than rounding the claim up. The honest asterisk on “no involvement” is that I wrote the original project idea and the tickets exist because I wanted the thing. What I did not do is any of the work between 23:33 and 01:41.
The step I had kept for myself
The chain was supposed to stop at installing a chess engine, which I had marked as my job on the assumption that the operating system would block an unsigned download. It carried on and installed it correctly. The task was mine because of an assumption, and the assumption was wrong.
Every move, scored
It then went through every single move of every game with the chess engine, running gently enough not to take over the machine.
Patterns, with the receipts checked
Then the actual point of the project: not “you blundered on move 23” but the habit behind it. It groups everything first, then looks for patterns, and every claim has to point at real moves or it is thrown away. It found five patterns backed by thirty-nine specific moves, with none rejected.
An earlier task had left a warning not to guess at what the clock information meant. It honoured that rather than assuming.
What it still needed me for
Two things, and it is worth being precise rather than overstating it: I wrote the original idea, and the tasks exist because I wanted this. What I did not do is any of the work between half past eleven and two in the morning.