Solver: best decisions per dragon colour, and the bot advisor
- 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
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
46ee08a56b
commit
d2ffb84b5e
@@ -13,11 +13,14 @@ packages/core/ @threshing-atlas/core, no dependencies, runs in Node and
|
||||
src/engine.js coding rules and statistics for the community form
|
||||
src/graph.js the shared route graph: scene graph, decision-variable graph,
|
||||
bot-to-form crosswalk, Beta credible intervals
|
||||
src/solver.js best decisions per dragon colour (history-dependent decision tree,
|
||||
empirical-Bayes back-off, two objectives) + the bot advisor
|
||||
packages/ingest/ @threshing-atlas/ingest: DragonKind bot importer (fingerprints and choice text only)
|
||||
research/python/ independent Python implementation of the coding rules and statistics
|
||||
tests/ JS/Python parity tests (they fail loudly if the two disagree)
|
||||
scripts/build-site.js assembles the static site into dist/
|
||||
scripts/build-graph.js combines every source into data/public/graph.json
|
||||
scripts/build-policy.js solves for every colour -> data/public/policy.json; policy-report.js -> docs/POLICY.md
|
||||
data/raw/ source exports (form .xlsx; the register export stays local, git-ignored)
|
||||
data/public/ what the page loads: form_responses.json, register.json, graph.json
|
||||
data/sources.json where the community spreadsheets and the PDF are downloaded from
|
||||
@@ -44,6 +47,15 @@ the PDF the pages and lines that are new. The PDF itself is never committed, onl
|
||||
(`data/derived/pdf_fingerprint.json`). If a link stops working, the Action opens an issue. You can also
|
||||
run it by hand from the Actions tab, or locally with `npm run check-sources`.
|
||||
|
||||
## Best routes (the solver)
|
||||
|
||||
`npm run policy` rebuilds `data/public/policy.json` and the readable `docs/POLICY.md` (about 2.5 minutes:
|
||||
200 posterior draws for two data samples). For every colour it gives the best decision at every point under two
|
||||
objectives: the chance of bonding that colour on this attempt, and the chance the account eventually ends on that
|
||||
colour when you die on purpose whenever a run goes wrong. Chance events (which dragon appears, whether the shadow
|
||||
shows) may depend on earlier choices; how much is learned from the data. See the top of
|
||||
`packages/core/src/solver.js` for the model and `docs/BOT_INTEGRATION.md` for how the bot uses it.
|
||||
|
||||
## Bot data
|
||||
|
||||
The private DragonKind bot's files are converted locally, and only the anonymised result is committed:
|
||||
|
||||
Reference in New Issue
Block a user