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>
analysis
Making sense of the data.
| Folder | What it does |
|---|---|
stats/ |
General statistics in Python (analyze.py, stats_core.py): rates with Wilson intervals, odds ratios with Fisher's test and Benjamini–Hochberg, ridge logistic models that adjust for data source and chase goal. core/engine.js computes the same numbers for the site, and tests/parity/ checks they match. |
network/ |
build-graph.js combines every source into data/public/graph.json (the decision-variable graph and the bot's scene graph). CI fails if the committed graph is out of date. |
reports/ |
Generated reports. POLICY.md is written by planner/policy-report.js; do not edit it by hand. |