clay-borg/evidence
tegwick 47e7941057
Some checks failed
ci / check (push) Failing after 3s
H2's ATTACK dynamics, and a construction hazard found while measuring them
The H2 panel measured wins, variance and DARVO but not ATTACK selection —
which is F17's actual question. attack-value now runs H2 too.

The shape is the finding. Under H1 a seat that sometimes attacks loses
everything at 3p and above. Under H2 rank-75 wins 112/173/199 against
greedy's 120/175/199, while attacking and arming DARVO. So H2 makes
occasional ATTACK affordable — it does not make it pay. rank-75 never
beats greedy in any cell, and rank-95 (always attack) still wins 0
everywhere in all three variants, so "not always-attack-optimal" holds.

F17 therefore stands: ATTACK earns its place in no mode. What changed is
that choosing it is no longer catastrophic. Whether affordable is what the
design wants is ground-game's judgement.

And a hazard: with_variant() exists because H2 assigns Problem owners at
setup and `state.variant = v` leaves them unassigned, so scoped pressure
ticks nobody and H2 measures as INERT. Three call sites had the bare
write, including cb-play's driver.

No published figure is affected, and that was checked rather than assumed:
h2-panel used the builder, and the two harnesses with the bare write had
only ever run baseline and H1, neither of which has a setup step; the
driver has never played H2. All three fixed, and
a_bare_variant_write_leaves_h2_inert now states the difference so a
regression is caught by a named test rather than by a reader wondering why
H2 did nothing.

The builder was not enough — the field is public, so the old form still
compiles. Worth knowing before the next variant.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-08 16:56:27 +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