The Black is not dice: developer statements, evidence report, and a plan that looks for the rule

- planner/knowledge.yaml: what the game's developer has said (paraphrased, dated, graded), what the Atlas does
  with each statement, and the open questions with the experiment that tests each.
- analysis/black/evidence.py -> analysis/reports/BLACK.md: counts from the runs. On the same recorded route the
  shadow shows on 21 of 79 first attempts and 1 of 80 later ones; no single route; Blue then Black after the shadow.
- game.yaml: the shadow is a guard (not a roll); what follows it is the Blue, then the Black; on-screen text for
  the squad's direction screen.
- planner/experiments.yaml v2: one exact path on every fresh account (fresh-replicate), then one choice changed
  at a time (fresh-ablate); shadow-again, second-attempt-same-path, veteran-repeat, veteran-variety; what the bot
  records about the account; the sequence to follow once the shadow shows.
- solver.js: assign() takes account facts, account offsets and cycled arms; recommendOption() answers the
  squad screen (stay + direction) in one pick.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014jqCC2LZ4x1WHQ1V57nTsv
This commit is contained in:
ekcSchiano
2026-11-16 15:24:03 +00:00
co-authored by Claude Fable 5.2
parent 51842e1aa9
commit d01ec46fcc
19 changed files with 1588 additions and 231 deletions
+24
View File
@@ -285,3 +285,27 @@ Branch `first-attempt-cycle` (not merged, not pushed).
the bot that is running, so the bot's side was written as a specification, not against its code.
- **Not done:** the page does not show first-attempt odds yet; Gitea still needs Kathleen's account, the
repository and the push (`docs/REPO_SETTINGS.md`); git.kenschiano.net answers (Gitea 1.27.0).
## 11. Update, 2026-11-16: the developer's statements, and looking for the Black's rule
- **Source.** The developer's answers in a community Discord channel (135 forwarded messages, exported
2026-11-16). The export is private raw data; `planner/knowledge.yaml` holds the statements paraphrased, dated and
graded (said / hint / declined), with what the Atlas does with each and the open questions.
- **What it changes.** The Black is not dice: the seed plays no part, it shows when the rider's choices meet its
conditions, and knowledge gives certainty. The bullies encounter and the tree are gates; there is no single route;
about five conditions. The Blue is dice from the seed. No event is rarer than 1 in 20. Runs are never forgotten
and never hurt.
- **What the runs add** (`analysis/black/evidence.py` -> `analysis/reports/BLACK.md`, rebuilt every cycle): on the
same recorded route, 21 of 79 first attempts show the shadow against 1 of 80 later ones (across routes: odds ratio
21.5, z = 9.8); on that route, runs with the same wing, section and squad still disagree; shadows are on 44
different recorded routes; after the shadow comes a Blue, then the Black; holding the Black's gaze bonded 27 of
39, lowering eyes 0 of 7.
- **Model.** The shadow is marked `guard: true` in `game.yaml`: the model's number is the share of runs that met
unknown conditions, not a chance. `shadowColour` is "past the Blue to the Black".
- **Plan (version 2).** Attempt 1 on every fresh account is one exact path (`fresh-replicate`, 60 accounts), then
one choice changed at a time (`fresh-ablate`, starts by itself). `shadow-again`, `second-attempt-same-path`,
`veteran-repeat` and `veteran-variety` test fresh against veteran. `assign()` takes account facts; the plan carries
what to record and the sequence to follow once the shadow shows.
- **Not known.** What differs between fresh accounts that see the shadow and those that do not on the same route;
what "twenty" counts; why holding the Black's gaze fails three times in ten.
- **To tidy.** One public `bond_note` holds a rider's handle ("Run 116 - ..."), in a row marked as a first attempt.