CB-EV-0020: a gate moved the rule, and the report was wrong
The AM-1 coverage gate failed the build on GR-P05 being uncovered, which is what showed the rule was in the offer layer rather than in validate. A rule enforced only by the offer is enforced only for clients that ask what is legal. The gate did not catch a bug, it caught a design error. And the reported case was not the one reported. CB-WP-0018, CB-EV-0016 and the message to ground-game all described SOLVE offered on a face-down Problem; validate already rejected face-down, so it never was. Problem 1 is the Surface Problem, face-up from the deal, so the three inert SOLVEs were the HAND case. The ruling covers both so nothing is invalidated, but a ruling was requested on a wrong description -- the second time in three passes that a premise reached ground-game unchecked, after the '12 points available' that voided GR-E01. Two of two. The pattern is not careless analysis; it is that a claim gets SENT the moment it is interesting and checked afterwards. Unexecuted verification, one step further out: not a belief acted on, but a belief published. CB-WP-0022's reproduction rule would have caught both. An earlier mutation run reported three survivors and was wrong -- the replacement strings did not match, so nothing was mutated. It proved nothing and looked like a result. Also renames CB-WP-0022-T06B to T07; the hub flagged it as an unregistered species. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
7a43de3f2a
commit
abd62c5567
5 changed files with 148 additions and 1 deletions
|
|
@ -3,6 +3,7 @@ id: CB-WP-0022
|
|||
kind: product
|
||||
title: "The design instrument: findings about the game, with their reproductions"
|
||||
status: active
|
||||
state_hub_workstream_id: "fda16340-0049-4acf-884b-a5cfdbde47c0"
|
||||
---
|
||||
|
||||
# Purpose
|
||||
|
|
@ -90,6 +91,7 @@ tier L exists to surface.
|
|||
id: CB-WP-0022-T01
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "6b8663b8-4143-4361-ad9e-7df0c4f4a19d"
|
||||
```
|
||||
|
||||
`research/CB-RES-0007-*.md`.
|
||||
|
|
@ -147,6 +149,7 @@ than duplicate.
|
|||
id: CB-WP-0022-T02
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "d2597895-fe2e-4f1e-a3db-a5fb8833434c"
|
||||
```
|
||||
|
||||
Tier L requires it. Give the reviewer the survey **and** the §judgment
|
||||
|
|
@ -171,6 +174,7 @@ Record the trail in `history/`, unpolished.
|
|||
id: CB-WP-0022-T03
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "a2e85810-e949-4ea0-81fc-36b912af326c"
|
||||
```
|
||||
|
||||
`decisions/ADR-0012-*.md`. At minimum:
|
||||
|
|
@ -195,6 +199,7 @@ priority: high
|
|||
id: CB-WP-0022-T04
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "60ddfeab-81b1-45e4-9ec9-91cc8ea7fb72"
|
||||
```
|
||||
|
||||
`specs/GameDesign.md`, with metrics, because a spec without them is prose.
|
||||
|
|
@ -219,6 +224,7 @@ and it must cost almost nothing or it will not be done.
|
|||
id: CB-WP-0022-T05
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "469413ba-ed47-4840-a60e-ee7f95dc06ff"
|
||||
```
|
||||
|
||||
The register, the tool, and then **the six findings above entered into
|
||||
|
|
@ -235,6 +241,7 @@ without a reproduction, and those never reported to their owner.
|
|||
id: CB-WP-0022-T06
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "c6a659bd-c495-4754-9332-baadad51012a"
|
||||
```
|
||||
|
||||
Generate the report and send it. **The message that sat unread for four
|
||||
|
|
@ -256,9 +263,10 @@ Include the two sharpened findings this pass has already produced:
|
|||
## Task: evidence
|
||||
|
||||
```task
|
||||
id: CB-WP-0022-T06B
|
||||
id: CB-WP-0022-T07
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "4fb77911-486d-4d9e-a53d-c4e486c74ce2"
|
||||
```
|
||||
|
||||
`evidence/CB-EV-0020-*.md`.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue