tegwick 561facce43 CB-WP-0022 T05/T06/T07: the register, and what its first run found ... T05. tools/design.py, make design, and the register in GroundRules.md -- 14 rows, no new file, because ADR-0012 D2 made §Underdetermined the register rather than building one beside it. Backfill was the test and it caught two things the ADR did not have. First, a `role` column. The first report alarmed on U2 and was wrong to: U2's scenario is green BECAUSE the provisional default it documents is implemented, which says nothing about whether ground-game agrees. GR-E01's was a counterexample that went green. Same colour, opposite meaning -- a register that cannot tell them apart either alarms constantly or never. Only a green counterexample alarms. Folded back into GameDesign §1.3. Second, it contradicted the survey. CB-RES-0007 said "six of the ten already have provisional scenarios." Measured -- grep -lE "\bU<n>\b" over scenarios/ground -- exactly ONE U-item names itself. Five provisional scenarios exist and four probably encode U-item defaults, but the mapping is not written down, so it is not checkable. Same defect class as the wrong premises, found inside the survey that proposed the fix. Now a reported debt: open, lacking a reproduction: 9, target 0. design.py carries the control design-baseline.py never had, asserted directly: a row citing a nonexistent file must not count as reproduced, using the exact path 2da19a4 deleted -- which the old tool called green. design-baseline.py is marked superseded rather than deleted; it is the evidence for how a wrong number got into a survey. T06. The report is a FILE in ground-game under GROUND-WP-0002, committed there, with a hub message that only points at it. It asks for no ruling: it carries GR-E01's withdrawal, our reproduction debt, and two notes that are explicitly not findings. And it had to acknowledge something nobody anticipated. GROUND-WP-0002 is finished -- all ten U-items were RULED 2026-08-03, every one confirmed as the default we simulate, plus five of six provisional scenarios. The survey said "0 of 10 ruled" two days later and this register was built saying `reported`. That is the unread-inbox failure running in the opposite direction: they answered and we did not collect it. The instrument's first run surfaced it. They are `ruled`, not `applied` -- lifting the now-settled provisional flags is owed and is not done, and make design shows them open until it is. T07. evidence/CB-EV-0021. Two of six catches in this pass came from execution rather than process (the role distinction from building it, the ten uncollected rulings from running it), which is InnerLoop §Design goal's prediction holding. make self-tests, facts-check, loop-lint: clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>		2026-08-05 15:22:33 +02:00
..
cb-play	CB-WP-0020: the table you can read	2026-08-03 20:20:38 +02:00
cb-sim	CB-WP-0015: the two inert clauses, AM-7 scaling and AM-8 N=10	2026-08-02 14:07:08 +02:00
cb-cost.py	CB-WP-0013-T02/T03: retire SH-3 as a gate; correct AM-4a and its target	2026-08-02 07:30:14 +02:00
dep-weight.py	CB-WP-0019 T01/T02: AM-4b asks what a contributor acquires	2026-08-03 19:04:54 +02:00
design-baseline.py	CB-WP-0022 T05/T06/T07: the register, and what its first run found	2026-08-05 15:22:33 +02:00
design.py	CB-WP-0022 T05/T06/T07: the register, and what its first run found	2026-08-05 15:22:33 +02:00
edition-check.py	CB-WP-0021 T01/T02/T05: the engine plays its own data — AM-7 blocks	2026-08-04 00:47:56 +02:00
facts.py	CB-WP-0006 T07: implement K18, amend K14	2026-08-01 12:47:16 +02:00
gate-review.py	CB-WP-0009-T02: gates.toml and make gate-review	2026-08-01 15:42:13 +02:00
loop-lint.py	CB-WP-0019 T03/T04: the cost rule written down, and the lifecycle	2026-08-03 19:25:18 +02:00
mutation-check.py	CB-WP-0021 T06: fix AM-7's measurement, not its floor	2026-08-04 01:10:38 +02:00
replay-test.py	CB-WP-0006 T06: K10 replay bundles, --replay, and AM-7 re-earned	2026-08-01 11:05:37 +02:00
repo.py	CB-WP-0004 T01: fix environment friction at the root	2026-07-31 10:13:52 +02:00
rule-coverage.py	CB-WP-0006 T07: implement K18, amend K14	2026-08-01 12:47:16 +02:00
runtime-metrics.py	Fix the AM-5 instrument to measure quietly; the breach was not real	2026-08-01 10:37:25 +02:00
size-metrics.py	CB-WP-0006 T02: instrument AM-2; report AM-3 blocked, with the argument	2026-07-31 18:38:15 +02:00
status.py	status: a cancelled task is a closed one	2026-08-03 18:55:11 +02:00
task-done.py	chore: mark T01/T02 done (measured: $2.33 + $1.68, 46 responses, opus-5)	2026-07-31 10:18:34 +02:00