- planner/policy.yaml: `reddit comment` is a model source. Only runs that break a game rule (the rule_flags checks) are left out; partial runs are kept. Its own reporting-bias group, and out of the low-bias sample (riders posting a run pick the notable ones). 77 of the 82 runs are used. - analysis/stats/measures.yaml: the site statistics use every source answered in the form's terms (form, "Report a run", Reddit comments). - analysis/black/evidence.py: a shadow run is "off the gates" only when an answer contradicts a gate (3); runs that do not say are counted separately (14). - croissant isBasedOn lists both megathreads (pipeline.yaml `cite`). - Rebuilt: policy.json, stats.json, BLACK.md, black.json, croissant.json. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
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").