clay-borg/evidence
tegwick 0b8599bd88
Some checks failed
ci / check (push) Failing after 4s
CB-EV-0033 + GROUND-RPT-0006: report the boards and modes to ground-game
Five things worth their time, four of them asks rather than statements:

F29 SCN_01 and SCN_02 are the SAME BOARD -- identical suit and value at
every priority, every cell matching exactly. Not called a defect (a
reskin is legitimate) but "four scenarios" is three boards. Asked
whether it is intended.

F30 SCN_04 is materially harder at 2p: 52/100 against 67 and 73, with
every other parameter held by the edition itself -- same deal shape,
same 6 available points, same threshold, same starting Stress. The lone
difference is that it is the only 2p deal needing two of one suit.
Causation explicitly NOT claimed; the falsifier is stated. Sensitivity:
at 4p SCN_04 is 97 against 94/99, so it is not the hard board there.

The modes finding, corrected in their favour: we previously reported the
three modes produced identical play. That was OUR INSTRUMENT, not their
game -- the bot never read the Mode card. With a mode-aware bot, group
success is unchanged in 34 of 36 cells but coalition size moves by half
again at 4p. So the modes decide the distribution of the win and the
threshold decides survival independently of it.

F28 (mastery counts cards where the shared score counts points) and F26
(a package that adds a FILE is invisible to a consumer) promoted to
reported -- both need their ruling, neither changed on our side.

F17 and F26 move raised -> reported now that they are in a delivered
report.

The register crossed the ~400-line loadability limit, so prose for
CLOSED findings moved to FindingRegister-closed.md. The rows are
untouched and `make design` still reads one file -- ADR-0012 D5's
reasoning about mixing open and closed applies to files too.

Report left UNCOMMITTED in ground-game: their tree has live uncommitted
work from their own agent.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-08 23:43:43 +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-0019-import-the-edition.md CB-WP-0021 T04: evidence -- the endings are tight, and the cost chain snapped 2026-08-05 15:56:31 +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
CB-EV-0022-collect-the-rulings.md CB-WP-0026: collect the rulings -- ten answers that arrived and were never applied 2026-08-05 16:13:37 +02:00
CB-EV-0023-the-table-you-can-watch.md CB-WP-0024: the table you can watch 2026-08-05 17:32:48 +02:00
CB-EV-0024-could-we-have-won.md ADR-0017: window 2's verdict — the mechanism worked, my account of it did 2026-08-07 10:55:54 +02:00
CB-EV-0025-the-commentary-track.md ADR-0017: window 2's verdict — the mechanism worked, my account of it did 2026-08-07 10:55:54 +02:00
CB-EV-0026-the-table-you-sit-at.md ADR-0017: window 2's verdict — the mechanism worked, my account of it did 2026-08-07 10:55:54 +02:00
CB-EV-0027-the-tokens-on-the-table.md ADR-0017: window 2's verdict — the mechanism worked, my account of it did 2026-08-07 10:55:54 +02:00
CB-EV-0028-a-number-that-does-not-move.md CB-WP-0030: a control for the wrong-subject family 2026-08-07 11:35:41 +02:00
CB-EV-0029-the-fourteen-unread-files.md CB-WP-0037 done: T03 classification and T04 evidence 2026-08-08 00:33:24 +02:00
CB-EV-0030-h1-measured.md CB-REV-0002: round 2, and the corrections were not approvable either 2026-08-08 09:44:00 +02:00
CB-EV-0031-a-seat-that-does-not-regulate.md CB-REV-0003: round 3, and three of four FATAL came from round 2's fixes 2026-08-08 10:26:25 +02:00
CB-EV-0032-h2-measured.md H2's ATTACK dynamics, and a construction hazard found while measuring them 2026-08-08 16:56:27 +02:00
CB-EV-0033-boards-and-modes.md CB-EV-0033 + GROUND-RPT-0006: report the boards and modes to ground-game 2026-08-08 23:43:43 +02:00