GROUND-RPT-0007: correct our H1 report — H1-B was never measured
Some checks failed
ci / check (push) Failing after 4s

Reported to ground-game as a CORRECTION to GROUND-RPT-0004, not a new
result. Half of H1 was never measured: every game behind that verdict
was played by bots that never attacked, and H1-B acts only on an
uncancelled ATTACK at the stress gate. The rejection stands on H1-A, but
'H1-B does nothing' was never established and is false.

Also carries the structural finding -- a module can be unreachable
because of an aspect it does not name -- with an ask: should a module
declare its reachability preconditions, so a consumer reports 'not
reachable in this configuration' rather than a number that reads as a
null result?

Repeats the two unanswered items from RPT-0006: the competitive modes
are weakly tested (no bot models a rival), and problem_stress.scoped
cannot reach a decision in round one.

Left uncommitted in their tree, as with every prior report.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-10 11:28:31 +02:00
parent ab6e6e5058
commit 4ec165c991
2 changed files with 9 additions and 3 deletions

View file

@ -138,6 +138,13 @@ are the whole register and `make design` reads them from here.
and at `+55` (module-aware) the module never fires; at `110` it fires
in every game. Nothing about the module changed — only whether any seat
ever gave it a turn.
**Reported to ground-game 2026-08-09** as GROUND-RPT-0007, framed as a
correction to GROUND-RPT-0004 rather than a new result. Carries one
ask: whether a module should declare its **reachability preconditions**
— the conditions under which it can act at all — so a consumer can
report *"not reachable in this configuration"* instead of a number that
reads as a null result.
- **F30 — SCN_04 is materially harder at 2 players.** 52/100 group
success against 67 and 73, with **every other parameter held by the
edition itself**: same deal shape, same 6 available points, same

View file

@ -135,9 +135,8 @@ now known to be false.
three-dimensional sweep and nothing yet says the modules behave the
same under the competitive modes — where, per CB-EV-0033, *who wins*
moves even when group success does not.
- **ground-game has not been told about F31.** It bears on a verdict we
already reported to them (H1's rejection), and a correction we owe is
worth more than one we volunteer.
- ~~**ground-game has not been told about F31.**~~ Reported 2026-08-09 as
GROUND-RPT-0007, as a correction to GROUND-RPT-0004.
- **The scope term is inert at round-one positions** (CB-WP-0049 T04), so
`problem_stress.scoped`'s measured effect is driven by later rounds.
The panel does not report per-round effect, and that is where the