Files
threshing-atlas/planner
ekcSchianoandClaude Fable 5.2 f8e4f575f4
CI / test (pull_request) Canceled after 0s
Screen tree, register rows in the master list, and bot runs coded from the picks that were played
- analysis/tree/build_tree.py -> data/public/tree.json, analysis/reports/TREE.md: every screen the bot has seen,
  every option, where each led (fixed or dice, with ranges), best known picks per colour chosen cautiously, where
  any picks end, and the untested options. solver.js screenPick(): least-tried and Thompson picks from the tree.
- The bot logs a pick it then overrode as a step: 37 runs were coded with choices they never made. Importer and
  graph.js now use the played steps only.
- runs_clean.csv: the Unofficial Dragon Register's 288 bonded dragons are in the master list as outcome-only
  rows, flagged (no analysis uses them).
- Cycle, refresh and the bot kit rebuild and carry the tree; tests check every generated report is current.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014jqCC2LZ4x1WHQ1V57nTsv
2026-11-16 15:50:12 +00:00
..

planner

The route planner: the best route to every dragon, and what goes back to Ken's bot.

File What it does
build_policy.py Solves the route model (core/atlas/solver.py, built from the game in core/spec/game.yaml) for every colour and both goals ("this attempt" and "eventually"), with 200 posterior draws and a cross-fit check. Writes data/public/policy.json, which has a content id so each bot run can record which policy it followed. About 2 minutes.
policy_report.py Writes the readable version, analysis/reports/POLICY.md.

| knowledge.yaml | What the game's developer has said about the mechanics (paraphrased, dated, graded said / hint / declined), what the Atlas does with each statement, and the open questions with the experiment that tests each. | | experiments.yaml | The experiment plan, written by hand: what each attempt of each bot account is for (the Black attempt on attempt 1, then the meadow Blue experiment, mapping and the sentinel route), with planned counts and stopping rules. | | build_experiments.py | Checks the plan against the game, counts what the bot has logged for every arm, sets each experiment's status (running, complete, paused), and writes data/public/experiments.json for the bot. |

Run both with npm run policy. The site's valley map and The Odds read policy.json; the bot downloads it with solver.js and graph.js (see docs/BOT_INTEGRATION.md).

The loop with the bot. python -m collection cycle --bot <the bot's folder> --deliver <its vendor folder> imports the bot's new runs, refits the route model, rebuilds the experiment plan and hands both back, in one command that is safe to run on a timer (docs/BOT_INTEGRATION.md, "The automated cycle").