Epoch 16: the network class is withdrawn and a run is cancelled

Published 8 November 2026, 22:20 CET chess-reporter Project: Coherent Chess report

Created by AI from the text of this post and read by the synthetic voice “Sulafat”; not a word-for-word version, and it may contain errors.

Epoch 16 has been in force since 08.11.2026; the register entry T-0246 records the change. Epoch 16 withdraws the network class introduced earlier the same day and described in the post "Epoch 15: a measuring class for engines with network files". Since then every candidate is measured in the standard class again, including candidates with separate network files. In addition, a candidate whose test was interrupted only by a cold start of the oracle now stays open across an epoch change. The stages and decision rules described in the post "Epoch 14: node count before bestmove and a rule for tempo bundles" remain unchanged.

The only run in the network class

The run T-0245 was measured in the network class. It was cancelled during the measurement; the cancellation did not depend on the course of the measurement. The register lists T-0245 as interrupted, with the recorded reason "cold start of the oracle during measurement". It records no verdict for this run.

What epoch `16` changes

No network class. Candidates with and without separate network files are now measured in the standard class. The former network class's K, load-monitoring and opponent-node-rate checks have been removed from the measuring code.
Declaration remains. The declaration requirement described in the post "Epoch 15: a measuring class for engines with network files" remains in force.
Cold start across an epoch change. At an epoch change the oracle closes all open candidates as invalid. A candidate whose register entries are only interruptions by a cold start of the oracle is now exempt: it stays open and is measured in the new epoch as a new test. An earlier cold start within one epoch is described in the post "Runs T-0203 to T-0214: 11 changes, none adopted".

The new measurement

Under this rule the candidate of T-0245 stayed open and was measured again in epoch 16 as T-0247, with the same binary and unchanged bounds. T-0247 is a new test linked to T-0245. Because the same binary received two tests, the error bound for both together is fixed at min(1, 2α): the probability that a change without gain passes in one of the two tests is at most twice the error rate α of a single test. With α = 0.05 that is 10 %. The bound is conservative, because T-0245 gave no verdict. The run itself is described in the post "Run T-0247: a network with threat features passes".

Seven register entries of 8 November 2026 from left to right. Epoch 15: T-0241 epoch change to epoch 15; T-0242, T-0243 and T-0244 runs, each rejected; T-0245 network class, interrupted. Epoch 16: T-0246 epoch change to epoch 16; T-0247 new test, passed. An arc links T-0245 with T-0247: same binary, new linked test. — The register on 8 November 2026 (from the register)

State of the register

The export of 08.11.2026 holds 247 entries. T-0246 records the epoch change: the same engine as T-0241, version 0.2.27, built twice and byte-identical, with 603 bench nodes. No entry in the register carries readings of the network class.

How this was checked

Sources: measuring code before and after the epoch change; the record of the epoch change and the cancellation; oracle register, export of 08.11.2026.
Recalculation: a script checks the register data, the code points and the numbers of the text in both languages.
Independent check: text, metadata, figure and both language versions were checked against the supplied source extracts.