Search-stability research brief · 15

Does giving KataGo thousands more visits really make the answer reliable

Five hundred professional positions, two strong models, and eight board symmetries show that more search usually reduces median drift but can expose a split first. Stable coordinates, stable values, and trustworthy teaching labels are different claims.

  1. Visits are a search budget, not answer confidence

    Visits count tree-search allocations; they do not state that the first candidate has converged. Position complexity, candidate margins, thread scheduling, and the network prior all change what one budget means. Five hundred twelve visits therefore cannot be translated into one reliability percentage, and the count is not a confidence interval.

    The same visit count can mean different convergence states in broad and narrow candidate landscapes.
  2. One quarter of top moves still change from 128 to 512 visits

    Across the frozen 500 professional positions, the b11 Transformer agrees on its top move at 128 and 512 visits in 74.8% of cases. Median root score drift is only 0.131 points, while the 90th percentile reaches 0.600. The typical position looks calm, but the tail can overturn teaching language; reporting only the median hides the labels with the highest risk.

    Top-coordinate agreement is 74.8% and median score drift 0.131 points, with a material tail.
  3. A second strong model also reorders the candidates

    On a 100-position cross-teacher subset, b11 and a separate b10 Transformer agree on the top move at the same 512-visit budget in 78.0% of positions. Agreement does not prove truth, but disagreement shows that a claim depends on architecture, training, or search interaction. Dramatic high-loss, low-human-probability cases deserve this cross-check first.

    At equal budget, model agreement is 78.0%; the remainder belongs in audit rather than automatic prose.
  4. Rotations and reflections reveal errors hidden by one orientation

    Ten anomaly-enriched positions were transformed through all eight D4 symmetries and mapped back to canonical coordinates. Only 60% had exact eight-way top-move agreement at 512 visits; 2,048 visits raised that to 80%. The transforms are repeated measurements of one position, not eight independent samples, and test whether learned approximate invariance supports a unique label.

    Map eight D4 inputs back to one board and ask whether rotations and reflections preserve the candidate.
  5. More search can expose a split before resolving it

    A Hane Naoki audit position chose B17 in all eight orientations at 512 visits. At 2,048, four rotations chose B17 and four reflections chose B7; only at 8,192 did all eight converge on B7. Deeper search did not monotonically strengthen the original answer. It first showed that shallow unanimity was accidental, then found a new stable candidate.

    Unanimous at 512, reflection-split at 2,048, converged at 8,192: depth can break surface certainty first.
  6. A stable coordinate can still hide an unstable value

    Some positions keep one coordinate across budgets and orientations while their root score range remains above one point. For teaching, stable “where” does not imply stable “how much,” and the latter determines whether words such as “clearly” or “must” are justified. Preserve the candidate set, top coordinate, value range, and principal variation instead of one bestMove field.

    Coordinate and value gates are separate; failure at either gate should soften the explanation.
  7. Stopping rules should follow consequence, not one fixed number

    Routine review can stop when candidate set, coordinate, and score are stable. A label that drives intensive training, public criticism, or historical interpretation should escalate budget and add model or symmetry checks. If deeper search remains split, expose uncertainty or withdraw the label. Compute is best spent at boundaries where it can change the teaching action, not spread evenly across every move.

    Low-risk confirmation stops early; high-risk teaching escalates, and persistent splits suppress the label.

Model and method sources

  1. KataGo Transformer architecture and symmetry study
  2. KataGo public networks and rating notes
  3. KataGo Analysis Engine documentation

Before publishing an AI judgment

  • Record actual visits, not only a preset name
  • Compare at least two budgets
  • Pass coordinate and value stability separately
  • Cross-check high-consequence cases by model or symmetry
  • Soften or withdraw labels that keep splitting
Read the complete experiment