- 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
172 lines
9.6 KiB
YAML
172 lines
9.6 KiB
YAML
# What the game's developer has said about how Dragonkind works, and what the Atlas does with each statement.
|
|
#
|
|
# Source: the developer's answers in a community Discord channel, forwarded there between 2026-10-19 and
|
|
# 2026-11-13 and exported on 2026-11-16. The export is private raw data (never committed: data/raw/). The
|
|
# statements below are paraphrased, with the date of the original message; no member is named.
|
|
#
|
|
# strength: said the developer stated it plainly
|
|
# hint said indirectly, or with a caveat ("I think", "maybe", a number offered half-seriously)
|
|
# declined the developer refused to answer (the community's "taps the sign"); recorded so that nobody
|
|
# reads a refusal as a yes or a no
|
|
# use: what in the Atlas depends on it. `open` lists what is still unknown and the experiment that tests it
|
|
# (planner/experiments.yaml). analysis/reports/BLACK.md is what the runs themselves show.
|
|
version: 1
|
|
|
|
engine:
|
|
- id: deterministic-engine
|
|
date: 2026-10-29
|
|
strength: said
|
|
statement: >
|
|
The game is a seeded, guarded, acyclic, deterministic transition system. The scene a reader stands in is a
|
|
function of the story and the path so far; the choices offered are a function of the story, the path, the
|
|
run's seed, and facts the site knows about the account. A run is deterministic once its seed is fixed.
|
|
use: The route model's rolls are fixed constants per scene, not quantities that drift; the game is a tree.
|
|
- id: seed
|
|
date: 2026-10-21
|
|
strength: said
|
|
statement: >
|
|
Each run gets a new id from the database; a keyed hash of it is the run's seed, the source of all the run's
|
|
randomness. The dice are in effect thrown before the first choice. The seed cannot be seen or influenced
|
|
from the browser, and neither time of day nor timing matters.
|
|
use: No experiment varies time of day or timing. Nothing a rider does before a run changes its dice.
|
|
- id: draws
|
|
date: 2026-11-04
|
|
strength: said
|
|
statement: A scene that uses the seed carries a chance out of 10,000 of an event.
|
|
use: Each roll is one fixed number per scene. Pooling a roll across routes that reach the same scene is right.
|
|
- id: one-in-twenty
|
|
date: 2026-10-19
|
|
strength: said
|
|
statement: No single event has worse than 1-in-20 odds; rare outcomes come from several events stacking.
|
|
use: >
|
|
A roll estimated below 5% is suspect: either several events are being counted as one, or it is not a roll.
|
|
The shadow (0.07% on later attempts) is the case in point: it is not a roll (see black/not-random).
|
|
- id: facts
|
|
date: 2026-10-21
|
|
strength: said
|
|
statement: >
|
|
The "facts" are what a web server knows about the request and the account. Neither part of the email address
|
|
is one. The site keeps little about readers, collects no analytics and does not fingerprint.
|
|
use: The bot records what it can see of the account on every run (planner/experiments.yaml, `record`).
|
|
- id: runs-remembered
|
|
date: 2026-10-29
|
|
strength: said
|
|
statement: A run is a small database entry and there is no reason ever to forget one.
|
|
use: An account's earlier runs can be among the facts. The bot keeps every account's full history.
|
|
- id: choice-order
|
|
date: 2026-10-25
|
|
strength: said
|
|
statement: The order of the choices on a screen is shuffled by the seed and belongs to the interface, not the engine.
|
|
use: Screen position is never analysed; options are matched by their text.
|
|
- id: size
|
|
date: 2026-10-25
|
|
strength: said
|
|
statement: There are about 24 million distinct paths; random play is bad at bonding.
|
|
use: Mapping cannot enumerate paths. It records each screen's options and where each leads.
|
|
- id: no-squad-bias
|
|
date: 2026-10-29
|
|
strength: said
|
|
statement: There is no squad bias toward the ability to bond anything.
|
|
use: Wing, section and squad are recorded but not expected to matter (BLACK.md section 3 agrees).
|
|
|
|
blue:
|
|
- id: blue-is-dice
|
|
date: 2026-11-04
|
|
strength: said
|
|
statement: >
|
|
Whether a Blue appears is a dice roll from the seed, like a loot drop. Someone who says they could
|
|
brute-force a Blue is right. Seeing one, the stacked odds of the bonding steps still kill most riders.
|
|
use: The meadow Blue stays a roll. Repeated attempts are the method; the gain is in the bonding answers.
|
|
|
|
black:
|
|
- id: not-random
|
|
date: 2026-11-04
|
|
strength: said
|
|
statement: >
|
|
The seed plays no part in whether the Black shows itself (repeated 2026-10-21, 2026-11-04, 2026-11-13). Its
|
|
conditions rest entirely on the rider's own choices. A rider who meets all of them gets the Black, and one
|
|
who knows the system can bond a Black with certainty, no luck involved.
|
|
use: >
|
|
The shadow is a guard, not a roll (core/spec/game.yaml `guard`). The model's "chance of the shadow" is the
|
|
share of runs like this one that met conditions we do not know yet, not the game's dice. Experiments on it
|
|
look for the rule (hold everything fixed, change one thing), not for a rate.
|
|
- id: gates
|
|
date: 2026-10-28
|
|
strength: said
|
|
statement: >
|
|
A rider must navigate the bullies encounter, and the tree is also a gate. There is no single route, and
|
|
there never will be a map that takes a rider down one specific route. The path does not change with time.
|
|
use: game.yaml `requires` on the shadow. BLACK.md section 4 (shadows on 44 different recorded routes) agrees.
|
|
- id: few-factors
|
|
date: 2026-10-28
|
|
strength: hint
|
|
statement: There are not forty factors; five "sounds like" a tolerable number.
|
|
use: The search is for a handful of conditions. Not relied on as an exact count.
|
|
- id: twenty
|
|
date: 2026-11-03
|
|
strength: hint
|
|
statement: Twenty is a discrete count the community would have a handle on once it understood how the Black is seen.
|
|
use: Unexplained. No analysis assumes what is counted.
|
|
- id: runs-never-hurt
|
|
date: 2026-11-07
|
|
strength: said
|
|
statement: >
|
|
Repeating the same path does not hurt an account's chances, so any given run either does nothing for them or
|
|
improves them. With a solution in hand there is no bad reputation to undo; the only risk is bonding
|
|
something unintended. Dooming an account at creation would be an accessibility problem.
|
|
use: >
|
|
Research attempts cannot spoil an account for the Black. Hard to square with section 2 of BLACK.md (the same
|
|
route works on a first attempt and almost never later), which is why the fresh-against-veteran experiments
|
|
come first.
|
|
- id: fresh-and-veteran
|
|
date: 2026-11-11
|
|
strength: hint
|
|
statement: >
|
|
Asked whether a rider with perfect knowledge would find the Black more easily on a first attempt or a later
|
|
one, the developer came close to answering and said the question was near a solution. Later: the community
|
|
is exploring what the developer would explore; the hard part is that an older account gives no feedback
|
|
until "it" happens; the task is to test the apparent success of a fresh account against the environment of
|
|
a veteran one.
|
|
use: Experiments fresh-replicate, shadow-again, second-attempt-same-path, veteran-repeat, veteran-variety.
|
|
- id: who-you-walk-with
|
|
date: 2026-11-07
|
|
strength: hint
|
|
statement: >
|
|
The valley might look different depending on who a rider walks in with, who they leave behind and who they
|
|
choose to fight; the dragons assess riders as riders assess dragons.
|
|
use: Company, leaving the squad, and the fight are the first decisions the ablation changes.
|
|
- id: death-does-not-matter
|
|
date: 2026-11-10
|
|
strength: said
|
|
statement: How a rider dies, the death message, and the scene a rider dies at are not factors in later runs.
|
|
use: Deliberate burns on research accounts are not a confound.
|
|
- id: order-does-not-matter
|
|
date: 2026-11-04
|
|
strength: hint
|
|
statement: As the developer understood the question, order does not matter.
|
|
use: None yet (the question it answered is not in the export).
|
|
|
|
declined: # refused, so neither confirmed nor denied
|
|
- Whether the conditions are only the answers to the questions (2026-10-25).
|
|
- Whether the shadow at the tree is the only way to meet a Black (2026-10-26).
|
|
- Whether choices repeated across runs raise or lower the chance (2026-10-21); later answered in part (runs-never-hurt).
|
|
- Whether older accounts can recover (2026-10-21).
|
|
- Whether there are hidden scores for personality, reputation or the like (2026-11-07, 2026-11-09, 2026-11-10).
|
|
- Whether the link riders see between cadet assignment and the Black is coincidence (2026-11-04).
|
|
|
|
open:
|
|
- question: On a fresh account, does one exact path always show the shadow, or only sometimes?
|
|
why: Always would mean the rule is in this run's choices. Sometimes would mean accounts differ in a fact we do not record.
|
|
experiment: fresh-replicate
|
|
- question: Which choices on that path are needed?
|
|
experiment: fresh-ablate
|
|
- question: Does an account that saw the shadow see it again on the same path?
|
|
experiment: shadow-again
|
|
- question: Does an account that missed on its first attempt miss again on the same path?
|
|
experiment: second-attempt-same-path
|
|
- question: Does an older account open up by repeating one path, or by varying its choices?
|
|
experiment: veteran-repeat, veteran-variety
|
|
- question: Holding the Black's gaze bonds about seven times in ten. What decides the rest?
|
|
why: The developer says knowledge gives certainty, so it should not be dice.
|
|
experiment: every screen after the shadow is logged; the bot follows the reported sequence (experiments.yaml `scripts`).
|