- planner/policy.yaml: which sources the route model learns from (spreadsheet,
reported, bot) and the low-bias sample
- bot runs: deaths coded by stage, Malek intent for runs with a target
- model: survival of the first dragon is not counted when nothing after it is
known; the meadow dragon falls back to what the bot saw
- solver.js: advisor(..., {sampling: "thompson", seed, draws}) follows one
posterior draw per attempt and reports each pick's propensity
Not shipped yet: mixing sources lowers the fitted shrinkage for the shadow roll
(alpha 500 -> 50 in the low-bias sample), see the conversation of 2026-11-09.
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. |
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. The planner's routes go out to the bot; the bot's runs come back through
collection/bot/. Experiments the bot should run to fill gaps the community form cannot (for example the
answers at each bonding encounter) belong here; experiments.json is on the roadmap.