Apply ground-game's rulings: mastery in points, four boards, and a
Some checks failed
ci / check (push) Failing after 4s

vendor tool that covers what the gate checks

They ruled on all seven items the same day. Two were actionable here.

F28 RULED: points. Modes.csv MODE_COOP clarified upstream to say
"penalties apply to points, not card count"; mastery is now
total - blame - denied. A recorded scenario went red on it --
gr-e02-shared-ground pinned 0 (2 claimed CARDS - 1 - 1) and now expects
2 (4 POINTS - 1 - 1). The number moved because the rule was decided, not
because the engine drifted, and the scenario records both rulings; its
schema has no field for a second one, so both live in ruled_note with
`ruled` carrying the LATEST date.

F29 RULED not-intended and APPLIED upstream: SCN_02's suits re-tuned the
same day. The characterisation test is how we found out -- it pinned the
duplication, went red on the re-tune, and that red WAS the notification.
It now asserts every pair distinct, the stronger statement the
duplication had made unavailable. SCN_02 re-measures at 73 at 2p, not
67: its own board now.

F26/F30 ruled and recorded. F30's ruling incidentally confirms our
reading -- they name priority-2's suit as the first lever, which is the
difference we identified without having measured causation.

vendor-editions grew twice, both times because it covered less than the
gate it exists to satisfy:

  - It refused to touch ground-darvo-r0/ on the reasoning that the
    baseline is "a separate record". That was wrong within the hour:
    ground-game clarified Modes.csv and `make vendor` reported a clean
    sync while edition-check went red. A sync tool that covers less than
    its check reports success into a red gate.
  - Its two-block rewrite DETECTED which fence held which set and
    preserved the arrangement -- faithfully preserving a swap an earlier
    write had introduced, leaving each fence under a heading describing
    the other. edition-check reads every sha256 line flat and passed
    throughout: a document can be self-consistently wrong and green.
    Order is now asserted, with a control that goes red on a swap.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-09 00:15:14 +02:00
parent 98f600b1d3
commit 704b99975b
15 changed files with 373 additions and 154 deletions

View file

@ -25,7 +25,34 @@ a sample nobody chose (CB-REV-0002 #1).
vary only face-down Problems and other seats' hands, and neither changes
its move. The control is proven against a deliberate peeker first.
## 1 — SCN_01 and SCN_02 are the same board
## 0 — what happened after this was reported
**ground-game ruled on all seven items the same day** (GROUND-RPT-0006
§"disposition"). Two changed the engine or the edition, and the numbers
below are therefore **superseded where noted**:
| item | ruling |
|---|---|
| SCN_01 ≡ SCN_02 | **not intended** — SCN_02 re-tuned upstream, §1 below is now history |
| SCN_04 harder at 2p | acceptable variety; first lever would be priority-2's suit, **not** thresholds — which confirms our reading of the operative difference without our having measured it |
| 6p formality | known (F17 line) |
| modes change who wins | accepted as a design property, not a defect |
| 2 relation slots | **intentional cap**; a third slot stays an extension, so our proposed sensitivity run would measure an extension and not the shipped game |
| mastery: points or cards | **RULED: points.** Applied — see below |
| package file manifest | accepted process ask, tracked as GROUND-WP-0008 |
**Mastery is now `total blame denied`.** `Modes.csv` was clarified
upstream to say *"penalties apply to points, not card count"* and the
engine follows. `gr-e02-shared-ground` went red on it — it pinned 0
(2 claimed cards 1 1) and now expects 2 (4 points 1 1). The
number moved because the rule was decided, not because the engine
drifted, and the scenario records both rulings.
**SCN_02 re-measured after the re-tune:** 2p group success **73**, not 67
— it is now its own board and matches SCN_03's difficulty rather than
SCN_01's. §1 below describes the state that prompted the report.
## 1 — SCN_01 and SCN_02 were the same board (superseded)
Identical suit and value at **every** priority. Every cell matches
exactly, in both policies, at all three seat bands.