Record owner confirmations for SOLVE legality, U1–U10, the dataset
contract, and provisional scenarios (void gr-e01). Spawn GROUND-WP-0003
for full-game playtests of semi-coop and coalitions.
Ruled by the maintainer 2026-08-03. editions/ground-darvo-r0/ is the
source of truth for Problem values, required solutions, visibility and
priority, and the engine must import it rather than invent them. This
unblocks clay-borg and very likely dissolves
gr-e01-threshold-unreachable-2p.
The three sub-questions were not ruled, so proposed defaults are recorded
rather than blocking the import on them: which columns are authoritative
vs presentational; that point_value and required_solution may NOT change
within r0; and that a version bump is the directory name, so it shows in
a diff and is never silent.
The second matters most: the engine hashes game state and a Problem's
value and required suit are IN that state. If they can change under a
fixed revision name, every recorded scenario hash in clay-borg silently
rots. Hence 'no' rather than 'probably not'.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
clay-borg messaged this repo on 2026-07-30 with ten rules points the
dataset does not decide (U1-U10), each simulated under a provisional
default, asking for confirm-or-correct per item. Four days later it was
still unread, because there was nowhere for it to land.
U2 (stress clamping), U6 (same-round Bond-Support vs DARVO step order)
and U8 (GROUND-OU cancelling an Attack before Protection is consumed)
are the three that change play -- each decides whether a DARVO stage
fires at all. The rest are edge cases or confirmations.
T03's six provisional scenarios are the scenarios that ENCODE these
defaults, so T05 comes first and T03 becomes the check that nothing was
missed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
T01: no generated placeholders remain. Named but not edited: SCOPE.md
does not say this repo is the authority clay-borg defers to for game
semantics, which is a real relationship with nine unanswered questions
behind it. Carried into WP-0002 T01 rather than written by hand, because
the sentence cannot be honest until the contract exists.
T02: there are no build/test/lint commands and that is the answer, not
an omission -- this is a content repo. Finding recorded: nothing
validates that the CSV sheets are internally consistent, because the
engine has never loaded them.
T03: GROUND-WP-0002. The most important next change is not content. The
engine has never loaded this repo's edition data -- it builds Problems
with value=priority and cycled suits, while Problems.csv has carried
point_value 2,2,2,3,3 and required_solution since 2026-07-31. GR-E01's
thresholds (2p 5, 3-4p 7, 5-6p 9) are ordinary against the 12 points the
dataset provides and unreachable against the stand-in's 6 -- which is
exactly what clay-borg reported as a rules gap needing a ruling here.
WP-0002 therefore leads with declaring the dataset authoritative, then
takes the rulings that survive it: SOLVE's legality against a face-down
problem, an unmatchable suit, and an already-claimed problem (GR-A13);
the six provisional defaults; and GR-E03/GR-E04 never having been played
to the end.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
