Walked every tab on desktop and phone, clicked every link and button:
- Colours: new map inks and page colours, checked with simulated
protanopia/deuteranopia/tritanopia (worst pair ~12 CIEDE2000, was 1.4 for
Red/Green on the map and 9.7 for Orange/Brown on the page). Map label text
is always dark ink; dragon colour goes on borders. docs/COLOURS.md and
research/python/check_colours.py.
- Valley map: dragons get a paper halo and a visibility floor (faded ones never
drop below 0.3; bonding dragons start at 0.5); "no shadow" roll labelled
correctly.
- Wording: methods updated (strata, the newer form's questions, missing
answers, a new section on the solver, The Odds cards and genuine attempts);
findings use readable factor names and no longer claim a date adjustment;
'Load a newer route export above'; code links include solver.js and
explorer.js; The Odds shows 93% instead of '1 in 1'.
- Deep Dive route map treats all six dragons alike ('Bond a dragon' row,
default 'Bond any dragon'; rare sightings separate).
- Phone: Deep Dive no longer overflows (sections and selects can shrink).
- scripts/qa/crawl.js and mapcheck.js for future release checks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
- packages/core/src/solver.js: decision tree with perfect recall over the
community form's choices; chance events (first dragon, deaths, shadow,
meadow dragon, encounter outcome) depend on earlier choices through
hierarchical Dirichlet back-off with empirical-Bayes concentration per
event; backward induction for P(colour this attempt) and Dinkelbach for
P(colour) / (P(colour) + P(other colour)); 200 posterior draws for
credible intervals and "still best" rates; cross-fitted held-out check.
- Only genuine attempts inform encounter outcomes (goal / Malek intent).
- data/public/policy.json (all runs and a low-bias sample) and the readable
docs/POLICY.md; published on Pages with solver.js for the bot.
- Bot advisor: re-solves from any history, maps advice onto screen text,
reports margins so ties can be randomised. docs/BOT_INTEGRATION.md.
- Tests on a synthetic world with known answers; daily source update now
rebuilds the policy.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
- 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