Files
kschianoandClaude Opus 5.5 0f4430f6f5
CI / test (pull_request) Successful in 2m0s
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:57 -05: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).