From 4ec165c991617d379464e569c58e6e197813df86 Mon Sep 17 00:00:00 2001 From: tegwick Date: Mon, 10 Aug 2026 11:28:31 +0200 Subject: [PATCH] =?UTF-8?q?GROUND-RPT-0007:=20correct=20our=20H1=20report?= =?UTF-8?q?=20=E2=80=94=20H1-B=20was=20never=20measured?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- specs/FindingRegister.md | 7 +++++++ .../CB-WP-0050-every-configuration-faceted-by-aspect.md | 5 ++--- 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/specs/FindingRegister.md b/specs/FindingRegister.md index 8b19008..7af42a7 100644 --- a/specs/FindingRegister.md +++ b/specs/FindingRegister.md @@ -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 diff --git a/workplans/CB-WP-0050-every-configuration-faceted-by-aspect.md b/workplans/CB-WP-0050-every-configuration-faceted-by-aspect.md index b8867fe..9228b14 100644 --- a/workplans/CB-WP-0050-every-configuration-faceted-by-aspect.md +++ b/workplans/CB-WP-0050-every-configuration-faceted-by-aspect.md @@ -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