Files
threshing-atlas/core
kathleenandClaude Opus 5.5 d9f3c200b8
CI / test (pull_request) Successful in 57s
Advisor: never advise an option that makes the target impossible while another keeps it possible
On a later attempt the data put the Black near zero on every route, so every option
tied and the bot's tie rule (random among options within 0.2 points) walked away from
the squadmate or went to the valley (DragonKind research runs 90, 91 and 102). The
advisor now also solves the game with no data (every roll possible except through a
closed gate; an encounter bonds its own colour) and marks options after which the
target cannot happen at all as `ruledOut`. The choice is never one of them while
another option keeps the target possible, and recommendOption leaves them out of the
options it gives the bot. For the Black: always investigate, help and climb the tree.

Values are unchanged; the published route tree still matches option for option.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
2026-11-22 02:15:44 +00:00
..

core

The shared model. Every other part uses it, so run npm test after any change.

The rules and the game are declarative files in spec/; the Python package atlas/ reads them. JavaScript is used only where it has to run in a browser or in Ken's bot.

File What it does
spec/form.yaml Every question of the community form (how to find it in an export) and every answer (what it is coded as), the answers that count as missing, email redaction, when "left your squadmates" was first asked.
spec/game.yaml The game: every decision and its options in order, every roll and what its odds may depend on, every bonding encounter, the flow of a run from the entrance to the dragons, how form answers map onto it, and the text the bot sees for each option.
atlas/coding.py Codes every form row into a run (python -m atlas.coding). Rule tests: tests/core/test_coding.py.
atlas/model.py, atlas/solver.py The route model: what each coded run reveals about each step, the count tables and shrinkage, the posterior draws, and one interpreter of game.yaml used to solve, evaluate and export the best routes (planner/build_policy.py). Tests: tests/core/test_solver.py, test_game.py.
solver.js JavaScript, for the site and the bot. The route advisor: reads the game and the count tables from data/policy.json and re-solves from any point in a run. tests/core/advisor.test.js checks it gives exactly the Python model's values and choices.
graph.js JavaScript, for the bot. Turns the bot's on-screen choices into form answers, and builds the route graph (analysis/network/build-graph.js). Moves to Python with the collection review.

The site and Ken's bot load the published copies (https://ekcschiano.github.io/threshing-atlas/solver.js, graph.js, data/policy.json), so those names on the site must not change.

To support a new form answer, add it to spec/form.yaml. To change a rule, edit atlas/coding.py and add a test case. To add a choice to the game, add it to spec/game.yaml (and, if the form records it, to atlas/model.py).