Implement selected logical recovery semantics
- Selected: logical committed-trajectory rollback/replay. Restore the committed model, optimizer, source cursor, RNG and ledgers together; replay can repeat discarded computation without adding retained training examples.
- Not selected: strict conservative physical-attempt reservations. Counting uncertain/discarded attempts against the cap can leave holes in retained coverage. Do not claim it simultaneously guarantees exact two-pass retained coverage under arbitrary crashes.
- Committed-checkpoint exact resume passed in the actual full model. Production NCCL/atomic model + ledger restore also passed a two-update smoke. Both are narrower than arbitrary-crash reconciliation; selected logical recovery is not silently certified for every failure point.
- Mixture denominators count retained consumed examples, not discarded reservations or masked dummy slots. The per-update board quota rounds/guards at update boundaries; report actual shares and eligibility shortfalls rather than assuming exactly 5%.
Evaluation that answers the real question
Before launch: test generation/scoring plumbing, completion handling, branch isolation and evaluation reproducibility. Fresh untrained board rows are not expected to meet an accuracy threshold. High occupancy accuracy is a later training outcome, not a prerequisite requiring unauthorized training.
- Teacher-forced loss plus raw free-generated whole-board exact match, per-square and occupied-square accuracy, piece/color errors and completion validity.
- Long-history and special-move slices: castling, en passant, promotion and captures. Initial/short-prefix duplication and transposition effects must be reported separately.
- No earlier gold squares in free generation. A history-only square-query or answer-visibility ablation can help distinguish readout from answer completion.
- Frozen legacy move, WDL and FUTURE8 regressions, plus identical fixed-budget playing evaluations where the harness supports them. Occupancy exactness alone is not playing strength.
Corrected 30-minute-budget benchmark · complete
The corrected trial completed in 27m 14.84s with code 0. Early/middle/late rates were 11,941 / 12,137 / 12,070 task examples/s; full elapsed rate was 11,867/s. It consumed 15,116,473 ordinary examples, about 1.618 passes over the 9,343,433-anchor training pilot, not two complete pilot epochs. Exact two-epoch behavior was exercised in separate coverage/cap tests. The calculator extrapolates two source epochs conditionally.
Measured settings: two RTX 4090 24 GB GPUs; torch 2.9.0+cu128 / Transformers 5.21.0; target 8,192 ordinary anchors/update rounded to whole games; 8 physical rows/rank/forward with variable accumulation and global normalization. Every steady update clipped at norm 1; batch/row settings were neither optimized nor VRAM-forced in that earlier pilot. The later matched optimization comparison is reported separately above.
Historical holdout audit passed against 8,282 frozen games with zero checked key/history/first-30-ply overlaps. Family exclusions additionally rely on sealed-source receipts. The later frozen canonical union is certified at 26,703,686 games / 2,263,679,463 ordinary anchors. See phase shares, timing, telemetry and terminal evidence above.
The first trial remains INVALID-FOR-ETA and contributes no rate to this result. Pristine initialization is unchanged. No full run, deployment or asynchronous game monitor was launched by that pilot.
Representative throughput: measure rows/s, consumed examples/s, active labels/s, padded and unpadded tokens/s, memory, corpus replay/build cost, validation, checkpoints, startup and safe shutdown on the actual final source/length/objective mixture. Runtime is the sum of exact task counts divided by relevant measured rates, plus measured overhead; report central and conservative cases.
Latest conditional scale: two epochs require exactly 4,527,358,926 ordinary examples at the certified A. The selected-profile forecast is 132 hours central / 167 hours slow + 10%, about 5.50 / 6.96 days. The anchor calculator scales that forecast, approximately 5.83 / 7.38 hours per 100 million anchors. It is not a statistical interval, guaranteed ceiling or direct 16% discount on the earlier benchmark projection. Actual checkpoints/evaluations, continuous cache production and final integration can change runtime.
Readiness boundary: portable tests, actual initialization/restore receipts, repaired history tests, valid terminal pilot benchmark and matched optimization tests are completed evidence. The full corpus is certified. Native production NCCL and atomic model + ledger restore passed a two-update functional smoke. The local guard is active and an evaluation scheduler is registered. Sustained rolling delivery, full-scale checkpoint/retention costs, completed production evaluation still need operational receipts. Logical recovery is selected; arbitrary-crash coverage and durable recovery remain distinct scopes. Clipping alone is accepted as non-blocking. The authorized full run is now active and unpromoted; the independently audited early snapshot is dated above. The optional asynchronous board-readout game check remains disabled and separate from requested health/evaluation monitoring.