Step 4a of the Python-first core. - analysis/stats/measures.yaml (declarative): outcomes and denominators, route targets and comparison groups, encounter contexts, the route map's stages, six filter presets and the route thresholds (5, 10, 20, 30). - analysis/stats/site_stats.py computes every number the page shows, for every preset, and writes data/public/stats.json: factor tables, models, chance events, encounters, the route map for every outcome, route rankings with q-values at every threshold, the valley map's place and step counts, and The Odds' summary cards. - The page now only displays: app.js, ui.js and explorer.js read stats.json; engine.js is no longer loaded. The three filter controls become one "Runs" menu; minimum runs become fixed thresholds. Removed: "Load a newer route export", click-to-select and "Follow" on the Deep Dive route map, and the unused old valley renderer. The coded runs are a CSV download. - tests/parity/compare_stats.py: every number matches what engine.js computed, for all six presets (factor tables, models, encounters, route rankings at every threshold, route map). Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
3.1 KiB
3.1 KiB
Roadmap
The aim is to move from summary statistics to path finding: for each dragon colour, the decision policy that maximises the chance of bonding it, with honest uncertainty.
- Repo and packaging (done): monorepo, CI, GitHub Pages, JS/Python parity tests.
- Graph format (
core/, first version done): typed scene, chance and terminal nodes; history-context keys; per-source counts (bot, form, PDF, Discord); fingerprints and short labels only, no game prose. Importers incollection/botfor the bot'sknowledge.json,runs.jsonlandencounters.jsonl(done), the form (done, via the crosswalk ingraph.js), and a PDF scene crosswalk (to do). Daily source checks for the form, the register and the PDF (done). - Context learning (
analysis/): tests of history dependence (G-tests, BH); variable-order Markov / context tree with BIC; temporal-tiered DAG structure learning (BDeu/BIC); latent "character" model vs specific triggers vs memoryless baseline, compared on held-out likelihood; hierarchical Dirichlet back-off pooling. - Solver (first version done:
core/solver.js,analysis/reports/POLICY.md; still to do: richer history models from step 3): backward induction on the augmented state (scene, history summary), i.e. an influence diagram with perfect recall. Two objectives side by side per colour:- P(target colour on this attempt);
- eventual success when deliberate deaths are free: maximise p_X / (p_X + p_other bond), solved by Dinkelbach iteration. Monte Carlo credible intervals, top-k routes, required steps and bottlenecks.
- Valley graph UI: every option at every point, with P(survive) and P(bond) per colour, the policy overlay for a chosen colour, and untested branches marked.
- Bot loop (advisor and sync published, see
docs/BOT_INTEGRATION.md; experiments.json to do): the atlas publishespolicy.jsonandexperiments.json(ranked by value of information); the private DragonKind bot consumes them and returns anonymised runs.
Python first, declarative rules (November 2026)
The repo is moving to Python, with the rules and the game written as declarative spec files. JavaScript stays only where it has to run: the site's drawing and interaction, and a small route advisor the site and Ken's bot share.
- Coding rules:
core/spec/form.yaml+core/atlas/coding.py, with rule tests. Done. - Route model in Python, built from
core/spec/game.yaml. Done (the bot's text,core/spec/crosswalk.yaml, moves with the bot importer and the JS advisor in step 4). - Done. Fix the coding bugs found in the core review (letting the Red pass, "left your squadmates" before the redesigned form, missing bot text), each with a rule test.
- The site shows precomputed statistics with fixed filter presets (done:
analysis/stats/site_stats.py,measures.yaml,data/public/stats.json; the upload button and the click-to-select route map are gone); next, a small JS advisor that reads the Python-built model replacessolver.js, andengine.jsgoes. data/dictionary.yamlfor every published column, and Croissant metadata for the datasets.