- collection/pipeline.yaml declares every source (extract kind, transform,
privacy rules, load target, run source); `python -m collection update|build`
- extract keeps data/raw/<source>/current + previous only (git-ignored);
data/manifest.json records the current raw checksum and change date
- transforms are pure; validate checks runs against data/dictionary.yaml
before load; load writes byte-stable files only when they change
- data/public/runs_clean.csv: every run from every source with a new
`source` column (reddit spreadsheet, reddit thread, reported, bot,
reddit pdf); the sheet's own row label moves to `entry`; run_id is text
- bot importer ported to Python (same output as bot.js on the fixture);
labels and crosswalk in collection/specs/bot.yaml, written into graph.js
- Reddit through the official API (result links to add by hand); the 12
result pages move to collection/manual/reddit_results.yaml
- "Report a run": a GitHub issue form generated from
collection/specs/report_form.yaml, collected as source "reported", plus a
site tab pointing to it, the community spreadsheet and the megathread
- analysis and the route model read runs_clean.csv (sources in
measures.yaml); stats.json and policy.json unchanged apart from the
factor's new name
- daily workflow runs the pipeline; the raw store is kept between runs in
the Actions cache, encrypted with RAW_ARCHIVE_KEY
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
Step 4b of the Python-first core.
- core/solver.js is now a 250-line advisor (was 900 lines): it reads the game (core/spec/game.yaml,
published inside policy.json as model.game) and the count tables, and re-solves from any point in
a run with the same interpreter as the Python model. Same API for the site and Ken's bot
(advisor, recommendOption, solverHistory). The bot's on-screen text for each option moves to
game.yaml (bot_text); the deadly rolls carry their risk labels there too.
- tests/core/advisor.test.js: the advisor gives exactly the Python model's values and choices for
every colour and goal (to 1e-12, every decision on every published route), walks a run in the
game's order, and maps advice onto the bot's screen.
- Removed core/engine.js and everything that only compared it with Python (tests/parity/run_engine,
compare_runs, compare_results, compare_routes, compare_solver, compare_stats, analysis/stats/
analyze.py). In their place: tests/core/test_stats.py checks the statistics against known answers,
test_solver.py checks the route model on a synthetic world (tests/fixtures/synthetic_policy.py).
- analysis/network/build-graph.js reads the Python-coded runs; graph.json is byte-identical.
- docs/BOT_INTEGRATION.md: what changed for the bot (history keys, new choices, re-sync all three files).
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
- apps/atlas: the web page (valley map, route flow, Dragon Register)
- packages/core: coding rules and statistics (engine.js) and the shared route
graph (graph.js): scene graph, decision-variable graph, bot-to-form crosswalk,
Beta credible intervals
- packages/ingest: DragonKind bot importer to anonymised trajectories (no prose,
no account identifiers); data/bot holds Ken's sample
- research/python: independent reference implementation + update_sources.py
- tests: JS/Python parity checks and graph/importer unit tests
- CI, GitHub Pages deploy, daily check of the community sheets and route PDF
- Email addresses in free-text form answers are redacted; the raw spreadsheet
is not committed
- MIT code licence, CC BY 4.0 data licence
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ