- planner/knowledge.yaml: what the game's developer has said (paraphrased, dated, graded), what the Atlas does with each statement, and the open questions with the experiment that tests each. - analysis/black/evidence.py -> analysis/reports/BLACK.md: counts from the runs. On the same recorded route the shadow shows on 21 of 79 first attempts and 1 of 80 later ones; no single route; Blue then Black after the shadow. - game.yaml: the shadow is a guard (not a roll); what follows it is the Blue, then the Black; on-screen text for the squad's direction screen. - planner/experiments.yaml v2: one exact path on every fresh account (fresh-replicate), then one choice changed at a time (fresh-ablate); shadow-again, second-attempt-same-path, veteran-repeat, veteran-variety; what the bot records about the account; the sequence to follow once the shadow shows. - solver.js: assign() takes account facts, account offsets and cycled arms; recommendOption() answers the squad screen (stay + direction) in one pick. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014jqCC2LZ4x1WHQ1V57nTsv
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).