tegwick
53109ec5e5
Some checks failed
ci / check (push) Failing after 3s
Vendored DARVO.csv, Relations.csv and Scenarios.csv — the three unread files that carry mechanism. The engine has implemented the DARVO sequence and relation formation/breaking from GroundRules.md since the beginning, and had never read the game owner's statement of them. Every checkable clause agrees, and agreement is recorded rather than noted: a survey that finds nothing and leaves no trace cannot be told from one never run. The two hardest clauses to notice were already right — Focus placed "even if the Attack was cancelled", and Focus removed when the sequence ends before REVERSE. The tests are tripwires, not derivations. The match was made by a person reading prose, and that reading goes stale in silence when the prose changes; each behaviour pins the phrase it was read from, so a reworded edition goes red and asks for a human. Mutation-proven by rewording the cancelled-Attack clause. F25 raised, and it is the real yield: Scenarios.csv carries threshold_2_players/3_4/5_6, starting_stress and round_track, and the engine hardcodes all three — a match returning 5/7/9, stress: 2 at setup, five rounds. They agree on all four scenarios. These are the most contested numbers in the project; the whole 4/6/9 vs 5/7/9 episode turned on them, and the engine has been right by maintenance coincidence rather than by reading the file that owns them. Also pinned: Problems.csv and Scenarios.csv both state the deal and the engine reads only the first. They agree; nothing was checking. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
63 lines
3.3 KiB
Markdown
63 lines
3.3 KiB
Markdown
# Vendored edition data — provenance
|
|
|
|
**Not ours.** This directory holds a copy of content owned by the
|
|
`ground-game` repository, vendored under ADR-0011 Decision 2 because the
|
|
build must not depend on a sibling checkout that CI does not have.
|
|
|
|
| | |
|
|
|---|---|
|
|
| upstream repo | `ground-game` |
|
|
| upstream repo path | `editions/ground-darvo-r0/` |
|
|
| authoritative? | **yes** — ruled by ground-game, GROUND-WP-0002 T01 |
|
|
|
|
## Files, and why each is here
|
|
|
|
| file | vendored | upstream revision | why |
|
|
|---|---|---|---|
|
|
| `Problems.csv` | 2026-08-04 | `9fd27a51` | the deal (ADR-0011) |
|
|
| `Actions.csv` | 2026-08-06 | `4fa3b8ed` | the five action cards' own words (ADR-0015 D2) |
|
|
| `Solutions.csv` | 2026-08-06 | `4fa3b8ed` | Solution titles and microcopy |
|
|
| `Modes.csv` | 2026-08-06 | `4fa3b8ed` | mode text and `scoring_tiebreak` |
|
|
| `Tokens.csv` | 2026-08-07 | `4fa3b8ed` | the components: `front_text`, `quantity`, `sides` (ADR-0016) |
|
|
| `DARVO.csv` | 2026-08-08 | `8886543` | **the DARVO sequence as rules**: `mandatory_effect`, `target_memory`, `advance` (CB-WP-0037 T02) |
|
|
| `Relations.csv` | 2026-08-08 | `8886543` | **how Bonds and Rivalries form and break**: `formation`, `breaking`, `rules_text` |
|
|
| `Scenarios.csv` | 2026-08-08 | `8886543` | the four scenarios and their setups — the engine deals one |
|
|
|
|
**Why these three, now.** The engine already implements the DARVO
|
|
sequence and relation formation/breaking — from `GroundRules.md`, never
|
|
from the edition's own statement of them. That is not inert display data;
|
|
it is **rules taken from a secondary source and never checked against the
|
|
primary one**, and CB-WP-0037 T02 exists to check them.
|
|
|
|
**Deliberately absent**: `BOM`, `Print_Manifest`, `Back_Designs`,
|
|
`Symbols`, `Design_Tokens` — production artifacts for a physical print
|
|
run, meaningless to a simulator. And `Extensions.csv`, which names content
|
|
the designer placed *outside* the core; importing it would break the claim
|
|
that this engine plays the edition as printed (ADR-0015 D2).
|
|
|
|
## Digests
|
|
|
|
```
|
|
sha256 7a7a302aabecdeb419c562a029bec3e3576a306b0bd1175d1200de60d9530073 Actions.csv
|
|
sha256 0afb882dc8001f03bc48a152c9d8c36ad492ceeff2d30ef6a3a690937317f77b DARVO.csv
|
|
sha256 565431571bc06adafb67edefd4b368839b6b94134c2289877384688cc643390b Modes.csv
|
|
sha256 0a04830c93b62dcb2f4411a9fbde576368a7427fe9e63c5015e606e4d42d23a0 Problems.csv
|
|
sha256 cd84c3b131c1b7a541e9e42529fdce2b7911f0832cce8c50cfcb8462d01dc551 Relations.csv
|
|
sha256 f830de9ca44417a7510e04a39ea24a070a81969b33a31fa68361fba132ad40cd Scenarios.csv
|
|
sha256 0bda1ee97de726b5e8c4404ab15ecc53a359e6c23db74fb41ecb51d78f9884ad Solutions.csv
|
|
sha256 25273bb6e74c9ad545c5e89dfe0f76b294d0a6cbef51f80d548039d5f0943484 Tokens.csv
|
|
```
|
|
|
|
`make edition-check` compares this against `../ground-game` when that
|
|
repository is present, and reports **`upstream not checked out`** as a
|
|
distinct outcome when it is not — never a pass. An absent check is
|
|
reported absent, not treated as satisfied (the shape ADR-0009 used for
|
|
`node`).
|
|
|
|
## What may not change under this revision
|
|
|
|
Per GROUND-WP-0002 T01's contract: `point_value` and
|
|
`required_solution` are **authoritative and frozen within `r0`**. The
|
|
engine hashes game state and both values are *in* that state, so a silent
|
|
change would rot every recorded scenario expectation. A change to either
|
|
is a new revision (`-r1`), and this digest is what notices.
|