1. Letting the Red pass. Only climbing down quickly puts you above the Red, so a tree run that passed on the Red and then met the Greens let it pass. Those 16 runs were coded as slow descents; they are now "Descend quickly: let the Red pass" and count for the Greens' encounter, so the route model's "let it pass" option rests on its own runs. A tree run with both the Red and the Greens attempted (impossible in one run) is now flagged. 2. Leaving your squadmates. The form only offered "> Left them" from 2026-10-27 (0 of 504 squad runs before chose it, 40 of 144 after). Earlier and undated squad runs are now unknown rather than "stayed together" (form.yaml: left_squadmates_asked_from). 3. Bot text. The wounded cadet's other two choices map onto the form; a test checks every choice the bot has logged maps onto a form variable (encounter answers excepted, not modelled yet). Each rule has a test in tests/core/test_coding.py. Data rebuilt (runs, graph, policy, report); the headline odds move by at most 0.02 points. The Methods tab describes both rules. Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
core
The shared model. Every other part uses it, so a change here touches everything: run npm test after any edit.
| File | What it does |
|---|---|
engine.js |
Turns a row of the community form (any version of it) into one coded run: the run format, every coding rule, missing answers, email redaction. Also the statistics the site shows. |
spec/form.yaml |
Declarative. 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. |
spec/game.yaml |
Declarative. The game: every decision and its options in order, every roll and what its odds may depend on, every bonding encounter, and the flow of a run from the entrance to the dragons. |
atlas/model.py, atlas/solver.py |
The route model in Python: what each coded run reveals about each step, the count tables and shrinkage, and one interpreter of game.yaml used to solve, evaluate and export the best routes. tests/parity/compare_solver.py checks it against solver.js, which the site and the bot use until the JS advisor replaces it. |
atlas/coding.py |
The Python coding rules: reads form.yaml, codes every row (python -m atlas.coding). Rule tests: tests/core/test_coding.py. |
graph.js |
The route graph: the bot's scene graph, the decision-variable graph shared by all sources, the crosswalk from the bot's on-screen text to form answers, Beta credible intervals. |
solver.js |
The decision model: every choice and roll in a run, chance estimates with empirical-Bayes back-off, backward induction for each dragon, and the advisor the site and the bot use to get advice from any point in a run. |
All three JS files have no dependencies and run unchanged in Node and the browser. The site and Ken's bot load
the published copies (https://ekcschiano.github.io/threshing-atlas/solver.js etc.), so their file names on the
site must not change.
To support a new answer, add it to spec/form.yaml. To change a rule, edit atlas/coding.py, add a test case, and (until the site stops coding rows in the browser) mirror it in codeRow() in engine.js; tests/parity/ fails if they disagree.
The project is moving to Python plus declarative spec files; JavaScript stays only where it must run in the browser or in Ken's bot (see docs/ROADMAP.md).