# 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`. | | `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 --deliver ` 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").