Core: coding rules as declarative form.yaml + Python package (atlas.coding) (#9)
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>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
432e04c2c7
commit
3536007ade
@@ -0,0 +1,8 @@
|
||||
"""threshing-atlas core: the shared model every part of the project uses.
|
||||
|
||||
The rules and the game live in declarative files under core/spec/ (form.yaml, game.yaml, crosswalk.yaml);
|
||||
the modules here read them:
|
||||
|
||||
atlas.spec load the spec files
|
||||
atlas.coding community form rows -> coded runs
|
||||
"""
|
||||
Reference in New Issue
Block a user