Every push to main builds the page into an nginx image and pushes it to
harbor.kenschiano.net/home/threshing-atlas; Argo CD Image Updater rolls the
deployment (kubefiles web/threshing-atlas) at https://threshingatlas.kenschiano.net.
forge.yaml now names that address.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tests/core/bot_contract.test.js copies the bot's AtlasPolicy.advise (DragonKind
src/atlasPolicy.js at ebe134a2) and plays the bot's own recorded screens through it
for every colour, sample and goal; checks the Black is routed through both gates and
up the tree; checks every assignment of the experiment plan is playable; checks the
known answers' shape. Added to npm run test:unit.
push-policy now also sends data/public/experiments.json and tree.json, which
docs/BOT_INTEGRATION.md says the bot reads (Solver.assign, screenPick) but which were
never delivered.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
The hierarchical back-off, the empirical-Bayes concentration and its one-outcome
guard, the shadow's gate (counting and solving), which bonds an encounter allows,
the first-attempt given with its token prior, and the reproducible random numbers.
Expected values are worked out by hand in the comments.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
- site/atlas/dice.js: a pair of dice marks a step the game decides at random (not the rider's choice). Clicking
(or Enter on) the dice opens a small popover with every outcome of that roll and its odds; Escape, scrolling or
a click elsewhere closes it. Dice.html for text, Dice.svg for the maps, Dice.legend for the keys.
- Route map: dice after each "game roll" heading (first sighting, encounter), with the share of riders at each
outcome in the runs shown. Legend: dice and gold headings = steps the game rolls.
- Valley map: dice on the "roll" / "shadow" labels of a route (the model's odds given the route so far), on the
"First dragon" step of the route list, in the first-sighting card, on the guide's own roll notes (no odds:
the guide gives none) and on the bot's answers that led to different screens. Legend under the route key.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
- analysis/black/evidence.py: Reddit comments and "Report a run" are their own groups. The attempt table gets a
column for each once it has a gated tree run (Reddit: 4 runs, 3 with a shadow; reported: none yet). A note says
Reddit describes 17 shadows but only 3 say both gates and 3 the attempt, and that, like form posts, they show
what shadow runs look like, not how often the shadow comes. black.json: by_attempt["Reddit comments"],
reddit_shadows.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
- collection/etl/runs.py fingerprints(): a form or register run's id is now <prefix>-<hash of the row's non-empty
answers, timestamp included> instead of its row number, so deleting or re-sorting rows in the sheet moves no
other run's id, and a column added later changes none. The 32 rows that are exact copies of another row get
-2, -3 (identical, so which is which does not matter). A row edited in the sheet gets a new id. Every id in
runs_clean.csv and overlap.json changes once; nothing else does (no statistic or model reads the ids).
- tests/core/test_site_stats.py (9 tests): measures.yaml conditions, source groups and presets, bond
denominators without deliberate deaths (cards, encounters, route map), the riders' paths, and a JSON-safe
stats.json, on a fixed sample of the published runs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
- The odds card for the Black: "Low evidence", "about 1 in N" first attempts, the 95% range written as
"between 1 in X and 1 in Y", later attempts effectively never, why it is uncertain (every logged shadow is a
rider who chose to post), and the steps (shadow -> reached the Black -> bonded). Dashed border.
- Valley map: the Black's routes are solved for a first attempt (they showed ~0% per attempt), labelled "on a first
attempt", and "Why this route?" gives the same range and caveat.
- "The Black is not dice" panel: why the odds are uncertain, and what replaces the assumption (fresh-account bot
runs to the tree).
- analysis/black/evidence.py wrote "odds_ratio": Infinity (no later-attempt shadow at all), which is not JSON:
the page's two Black panels showed "could not be loaded". Now null, and the report says "unbounded".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
- collection/etl/review_reddit.py (`python -m collection review-reddit`) and .gitea/workflows/reddit-review.yml:
on every scraper pull request, one comment (refreshed on each push) listing the runs added, changed and gone, the
runs that break a game rule (left out of the model and stats until corrected), other flags, runs that may also
be in the form, and result pages already counted; plus how to reject / fix / add. forge.upsert_comment keeps it
to one comment. collection/README.md: "Reviewing Reddit runs".
- analysis/overlap/overlap.py -> data/public/overlap.json: a Reddit run with at least 4 route answers "matches" a
form row giving the same answers within a day; chance is the same test a few weeks off. 9 of 36 comparable runs
match, ~7.3 by chance: about 2 of 82 look reported twice, too few to matter. Nothing is removed. Shown on the
page's Data & methods tab; in the dataset metadata; checked in test:py; part of `rebuild`.
- Neither the form nor the register records a result-page id, so the only proven copy (comment <-> result page)
stays the one #18 applies.
- data/public/stats.json: the statistics of #42 (impossible runs left out), which did not make it into that merge.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
Every push to main builds the static site (npm run build -> dist/) and force-pushes it as the only commit of
the `pages` branch. Ken's web server serves that branch (a git-sync sidecar or a pull on a timer): nothing
on his server needs a secret, since the repository is public, and the site updates within minutes of every
merge, data PRs included.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
- core/spec/form.yaml impossible_flags: the flags that mean a run cannot have happened as recorded (a dragon an
encounter does not have, a Green or the Black in the valley, two bonds, two burns, a cadet path that does not
follow, an early death that still reached the hour...). atlas.runs.impossible() reads it.
- The route model and the site statistics (and the riders' paths) leave those runs out, from every source; every
other run is used, however partial. The runs stay in runs_clean.csv, flagged. 80 runs: 75 form, 5 Reddit.
Route-model odds move by at most 0.2 points.
- collection/etl/runs.py: the community form gets the same game-rule checks as "Report a run" and the Reddit
comments (10 form rows newly flagged); new rule: the Black in the valley.
- The first-sighting pool stays a flag only: it is what riders have seen, not a rule.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
- bot-cycle.yml: no schedule. It needs a runner on the bot's machine that no one has added, so every 4 hours
a run queued forever. The bot's data already arrives through the daily source check (it reads
DragonKind/DragonKind) and the model goes back through push-policy. Still runnable by hand.
- update-sources.yml: a concurrency group, so two dispatches never build and push at once.
- .gitignore: drop `/site` (a Python template's mkdocs line). site/ is the Atlas page; new files there were
silently ignored.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
- analysis/stats/measures.yaml: the bot is a statistics source. A deliberate death (`_deliberate`, the route
model's rule: burned at an encounter the rider was not attempting) is left out of every bond rate, encounter
rate and route ranking, for every source, as the model and the summary cards already did. Biggest moves (all
runs): two Greens 8.9% -> 29.1%, meadow Orange 9.2% -> 25.2%, meadow Brown 14.3% -> 28.3%, valley Red 79.2% ->
93.3%; mostly from form riders who burned on purpose, not from the bot.
- analysis/stats/site_stats.py: runs that are not from the spreadsheet are grouped as their own source
("Reddit comments", "DragonKind bot", "Reported on the Atlas"), not as bulk logs; two new presets (Reddit
comments only, DragonKind bot only); the route map's bond denominators skip deliberate deaths.
- site/atlas/app.js: the bulk-import share counts only spreadsheet imports.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
- planner/policy.yaml: `reddit comment` is a model source. Only runs that break a game rule (the rule_flags
checks) are left out; partial runs are kept. Its own reporting-bias group, and out of the low-bias sample
(riders posting a run pick the notable ones). 77 of the 82 runs are used.
- analysis/stats/measures.yaml: the site statistics use every source answered in the form's terms (form,
"Report a run", Reddit comments).
- analysis/black/evidence.py: a shadow run is "off the gates" only when an answer contradicts a gate (3); runs
that do not say are counted separately (14).
- croissant isBasedOn lists both megathreads (pipeline.yaml `cite`).
- Rebuilt: policy.json, stats.json, BLACK.md, black.json, croissant.json.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
6 of the 82 runs now carry rule flags (Brown/Red at the shadow, Green after
jumping on the Red, Red in the meadow, Orange first for Alone/Center, fight
answers on an ignored scream). Only their data_flags change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
Reported and Reddit-comment runs now get the checks the community form
gets in core/atlas/coding.py, as data_flags (the run is kept):
- first dragon outside the documented pool for the company/direction
- a bond or burn by a dragon the encounter does not have (new
encounter_colours table in core/spec/form.yaml; Orange/Brown after the
two Greens allowed, as a Green's rescue)
- a Green on a valley run
- a cadet outcome off its scream path, fight answers or a post-fight path
on a run that did not help, a second fight move without assessing
- died before the hour, yet reached the tree/valley or an encounter
planner/policy.yaml drop_flagged: flagged runs of sources read from free
text (reddit comment) stay out of the route model; provenance notes do not
count as flags. No effect today: the source is not in `sources` yet.
On the first 82 scraped runs: 6 flagged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
analysis/known/build_known.py writes data/public/known_answers.json from pdf_encounters.json and tree.json;
solver.js knownAnswer(known, offered, { target, sceneColour }) matches a screen's choices against it (the guide's
paraphrases by their words, the bot's texts exactly) and returns a pick when one choice is clearly on the guide's
recommended path to the target, plus the evidence for every choice to hand to Clef. Rebuilt daily, checked in CI,
and sent to the bot with the route model.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ