Step 1 of moving the repo to Python with declarative rules. - core/spec/form.yaml: every question (how it is found in an export), every answer and what it is coded as, missing answers, email redaction, burn order, first-dragon pools. - core/atlas/coding.py reads it and replaces core/python/clean.py (python -m atlas.coding). - tests/core/test_coding.py: 16 rule tests, one hand-written row per rule, checking the rules are right rather than only that JS and Python agree. - analysis/stats/analyze.py takes the colours and missing answers from the spec instead of its own copy; the daily update job codes rows through the package. - pyproject.toml for the package; pyyaml and pytest added to requirements. The coded runs are byte-identical to before (5,988 runs); all parity checks still match. Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
1.7 KiB
1.7 KiB
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. |
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).