Files
ekcSchianoandClaude Opus 5.5 46c1f00150
CI / test (pull_request) Successful in 41s
Impossible runs: one definition, left out of the route model and the site statistics (#21, #22)
- core/spec/form.yaml impossible_flags: the flags that mean a run cannot have happened as recorded (a dragon an
  encounter does not have, a Green or the Black in the valley, two bonds, two burns, a cadet path that does not
  follow, an early death that still reached the hour...). atlas.runs.impossible() reads it.
- The route model and the site statistics (and the riders' paths) leave those runs out, from every source; every
  other run is used, however partial. The runs stay in runs_clean.csv, flagged. 80 runs: 75 form, 5 Reddit.
  Route-model odds move by at most 0.2 points.
- collection/etl/runs.py: the community form gets the same game-rule checks as "Report a run" and the Reddit
  comments (10 form rows newly flagged); new rule: the Black in the valley.
- The first-sighting pool stays a flag only: it is what riders have seen, not a rule.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
2026-11-19 16:03:45 +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").