clay-borg/evidence
tegwick 561facce43
Some checks failed
ci / check (push) Has been cancelled
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-EV-0001-game-kernel.md CB-WP-0019 T01/T02: AM-4b asks what a contributor acquires 2026-08-03 19:04:54 +02:00
CB-EV-0002-cost-accounting.md CB-WP-0004 T04: fact registry and make facts-check — DFD gets a gate 2026-07-31 10:24:39 +02:00
CB-EV-0003-mechanical-work.md CB-WP-0004 T05: control loop — 6 points recovered, not 25-30 2026-07-31 10:27:09 +02:00
CB-EV-0004-assertion-coverage.md CB-WP-0005 T07/T08: control loop, retrospective, InnerLoop v1.4 2026-07-31 18:05:31 +02:00
CB-EV-0005-instrument-the-table.md CB-WP-0006 T08: control loop — 4 of 14 to 8 of 14, and a cost regression 2026-08-01 13:39:12 +02:00
CB-EV-0007-stage-0.md CB-WP-0008-T04: CB-EV-0007 — stage 0 is shipped, and the spend curve is a V 2026-08-01 15:25:19 +02:00
CB-EV-0008-adaptive-gates.md CB-WP-0009-T04: CB-EV-0008 — the gate changes, measured 2026-08-01 15:45:08 +02:00
CB-EV-0009-inspectable-table.md CB-WP-0011-T03: evidence — the chaos roll fired, and it was right 2026-08-02 02:48:51 +02:00
CB-EV-0010-render-port.md CB-WP-0012-T05: evidence — tier L deleted its own deliverable 2026-08-02 04:30:10 +02:00
CB-EV-0011-instrument-corrections.md CB-WP-0013-T04: evidence — and a rule about quoting your own cost 2026-08-02 07:32:07 +02:00
CB-EV-0012-execute-the-javascript.md CB-WP-0014-T03: hot-seat evidenced; stage 1 open on one human check 2026-08-02 07:58:59 +02:00
CB-EV-0013-the-inert-clauses.md CB-EV-0013: correct the cost table, and the self-quoting rule with it 2026-08-02 14:09:52 +02:00
CB-EV-0014-the-drop-target.md CB-WP-0017: legible interaction, and the chaos window's verdict 2026-08-02 22:42:45 +02:00
CB-EV-0015-legible-interaction.md CB-WP-0017: legible interaction, and the chaos window's verdict 2026-08-02 22:42:45 +02:00
CB-EV-0016-the-browser-is-a-client.md CB-WP-0018 T03/T04: explanations, and window 1's verdict 2026-08-03 02:24:13 +02:00
CB-EV-0017-budgets.md CB-WP-0019 T03/T04: the cost rule written down, and the lifecycle 2026-08-03 19:25:18 +02:00
CB-EV-0018-the-table-you-can-read.md CB-WP-0021: correct the declaration before writing any code 2026-08-03 20:35:39 +02:00
CB-EV-0020-solve-legality.md CB-EV-0020: a gate moved the rule, and the report was wrong 2026-08-04 00:21:21 +02:00
CB-EV-0021-the-design-instrument.md CB-WP-0022 T05/T06/T07: the register, and what its first run found 2026-08-05 15:22:33 +02:00