What plays
A single cadence.RecordPatchNet reads a position right after a stone has landed, as the side that placed it sees it (84 units), and says how the game ends for that side. A supplied search knows the rules, imagines moves from the centre outward, and reads the patch where it stops looking. A line it can follow to the end of the game is proven and outranks anything the patch reads.
How it learned
It watched Pascal Pons' perfect solver play out set-up positions to the end, and saw how each game ended for each stone placed. It saw the games and how they ended; the solver's scores were never recorded. The slow parameters learned from those positions; the record store was left empty, because writing millions of positions into it drowns it (measured: the slow readout alone then beats the two together). The records are for the games it plays afterwards.
What you see
Each flash on the right is one read of one imagined board: the two retinas it reads, the 256 channels of its context, the record cells that reading addresses, and the value it reads out. Reads are sampled through the search and replayed at a speed the eye can follow. The bars under the board are the value the search found for the column it chose and the most it allows each of the others; ghost stones are the line it expects.
Measured on this build
loading the receipt
What it cannot do
Early in the game, before the search can see the end, it still errs: the receipt above counts how often, graded move by move by the perfect solver. Against the perfect solver it wins some games moving first and loses the rest: before 24 stones it blunders in one position in ten to one in five, and one blunder against a perfect player loses the game. From 16 to 24 stones it does not always reach the end of the game within the reads it allows itself. Moving second against perfect play it loses, as every player does. This build does not yet learn from the games you play here.
Every game and every graded move of this build: receipt.json. The source on GitHub, with its school, its checks and the library: fork them and build a stronger player.