Files
kschianoandClaude Opus 5.5 e457f89b40 Game-rule checks for runs answered through "Report a run"
Reported and Reddit-comment runs now get the checks the community form
gets in core/atlas/coding.py, as data_flags (the run is kept):
- first dragon outside the documented pool for the company/direction
- a bond or burn by a dragon the encounter does not have (new
  encounter_colours table in core/spec/form.yaml; Orange/Brown after the
  two Greens allowed, as a Green's rescue)
- a Green on a valley run
- a cadet outcome off its scream path, fight answers or a post-fight path
  on a run that did not help, a second fight move without assessing
- died before the hour, yet reached the tree/valley or an encounter

planner/policy.yaml drop_flagged: flagged runs of sources read from free
text (reddit comment) stay out of the route model; provenance notes do not
count as flags. No effect today: the source is not in `sources` yet.

On the first 82 scraped runs: 6 flagged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 08:46:13 -05: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").