CB-WP-0022 T02: the separate reviewer found the showcase finding was false

First adversarial review in this repo run by a genuinely separate agent.
CB-RES-0006's reviewer opened by conceding it could not be, and called its
own findings "a lower bound on what a genuinely separate reviewer would
find." This is the measurement: the separate reviewer ran git log against
the survey's central example and found 2da19a4 had falsified it four days
earlier, while the author -- who wrote that commit -- quoted the dead
number twice.

Seven challenges: four conceded, two conceded in part, one answered.

C1 changes the design. "GR-E01 is admissible because 4/6/9 against 5/7/9
is a computation anyone can rerun" was a computation already rerun: the
edition import measured 6/9/12, the conclusion inverted, and the scenario
was renamed -unreachable- to -reachable-. That finding was one of the TWO
that passed the reproduction rule. So three wrong premises have now
reached ground-game and the third satisfied an existence test -- existence
is not the property that was missing. The rule gains shape (ground-game's
row-level deal table, promoted from a T04 addendum) and a clause the
survey never contemplated: a reproduction must be able to fail. Ours went
green and stayed admissible.

C1 also caught a defect in flight. T06's payload, status todo, still named
4/6/9 and was queued to send it to ground-game as "no dataset reconciles
them." Withdrawn before sending -- the fourth wrong premise, and the only
one stopped.

C2 withdraws the baseline's precision: design-baseline.py is a
hand-maintained dict counting itself, has_reproduction never checks the
file exists (its YES-control is green against a deleted path), and
Makefile:127 runs only --self-test so the reporting path has no CI. The
direction survives; 33% is not a measured rate and T05 must not build on
it. C3: "six provisional defaults" is five, GR-E01 double-counted. C4:
GroundRules §Underdetermined was never evaluated as a candidate and
already delivers four of five benchmarks -- T03's burden flips to arguing
extension over replacement.

Survived: the rule's affordability, and reuse of the provisional
machinery.

loop-lint: no findings.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

workplans/CB-WP-0022-the-design-instrument.md

@@ -57,9 +57,21 @@ register that collects opinions would reproduce it in a new medium.
 
 Concretely: a scenario that fails, an arithmetic check that prints the
 contradiction, a recorded game the reader can replay, or a named test.
-*"This feels unbalanced"* is a note, not a finding. **GR-E01 is admissible
-because 4/6/9 against 5/7/9 is a computation anyone can rerun; the SOLVE
-inertness is admissible because a recorded session shows three no-ops.**
+*"This feels unbalanced"* is a note, not a finding. **The SOLVE inertness
+is admissible because a recorded session shows three no-ops.**
+
+> **The example that stood here was GR-E01, and the adversarial review
+> killed it (C1, 2026-08-05).** *"4/6/9 against 5/7/9 is a computation
+> anyone can rerun"* was a computation that had already been rerun:
+> `2da19a4` measured **6/9/12 against 5/7/9** and renamed the scenario
+> `-unreachable-` → `-reachable-`. The finding's conclusion inverted, and
+> it was one of the two findings that **passed** this rule.
+>
+> So existence is not the property that was missing — three wrong premises
+> have now reached `ground-game`, and the third satisfied an existence
+> test. T03 must adopt the shape requirement as part of the rule, plus a
+> clause the survey never contemplated: **a reproduction must be able to
+> fail.** Ours went green and stayed admissible.
 
 This is what would make clay-borg a design tool rather than a suggestion
 box, and it is the one part of this proposal that must not be traded away
@@ -147,7 +159,7 @@ than duplicate.
 
 ```task
 id: CB-WP-0022-T02
-status: todo
+status: done
 priority: high
 state_hub_task_id: "d2597895-fe2e-4f1e-a3db-a5fb8833434c"
 ```
@@ -173,6 +185,46 @@ above, and require an attempt at:
 
 Record the trail in `history/`, unpolished.
 
+**Done 2026-08-05.** Trail:
+[challenge](../history/260805-design-instrument-challenge.md),
+[response](../history/260805-design-instrument-response.md).
+
+**Run by a separate agent** — the first in this repo that was. CB-RES-0006's
+review opened by conceding it could not be, and called its own findings
+*"a lower bound on what a genuinely separate reviewer would find."* That
+was measurable, and this is the measurement: the separate reviewer ran
+`git log` against the survey's central example and found our own commit
+had falsified it four days earlier, while the author — who wrote that
+commit — quoted the dead number twice.
+
+**Seven challenges: four conceded, two conceded in part, one answered.**
+
+- **C1 lands hardest and changed the design.** The rule's showcase finding
+  was false and had *passed* the rule. Existence is not the missing
+  property; **shape** and **falsifiability** are. Folded into §The
+  load-bearing rule above, and it is T03's to settle.
+- **C1 also caught a defect in flight** — T06's payload, `todo`, still
+  named the dead number. Withdrawn above before sending.
+- **C2 withdrew the baseline's precision.** `tools/design-baseline.py` is a
+  hand-maintained dict counting itself (`:16-36`, `:89`); `has_reproduction`
+  (`:38-43`) never checks the file exists, so the self-test's YES-control
+  (`:63`) is green against a path `2da19a4` deleted. `Makefile:127` runs
+  only `--self-test`, so the reporting path has no CI. The direction
+  stands — 11 files, no index, 0 of 10 ruled are all checkable without the
+  tool — but **33% is not a measured rate and T05 must not build on it.**
+- **C3**: "six provisional defaults" is five, and GR-E01 is double-counted
+  in the `2/6`. No corrected rate is quoted here; the instrument that would
+  produce it is the one C2 withdrew.
+- **C4**: `§Underdetermined` was never evaluated as a candidate, and it
+  already delivers four of five benchmarks including the Oracle property
+  the survey went to Magic to find. **T03's burden flips: argue why it is
+  extended, not replaced.**
+- **C5**: the engine-evolution "third thing" is visible in
+  `specs/InnerLoopReference.md` and `history/`'s retrospectives, neither of
+  which my redundancy inventory named. Conclusion narrowed, not settled.
+- **Survived**: the reproduction rule's *affordability*, and §4's reuse of
+  the provisional machinery. Both with stated falsifiers.
+
 ## Task: decide
 
 ```task
@@ -278,12 +330,20 @@ So the report must land somewhere that persists: a file in `ground-game`
 under its own workplan, not only an inbox entry. GROUND-WP-0002 already
 holds the ten U-items; this should extend it rather than duplicate it.
 
-Include the two sharpened findings this pass has already produced:
+Include the findings this pass has sharpened:
 
-- **GR-E01 vs GR-S01** — the deal count puts 4/6/9 points in play against
-  thresholds of 5/7/9, so either the count or the thresholds are wrong and
-  no dataset reconciles them;
-- **SOLVE's legality** against a face-down Problem or an unmatchable suit.
+- **SOLVE's legality** against a face-down Problem or an unmatchable suit —
+  and note that the case we *reported* was not the case that fired
+  (CB-WP-0023 T01).
+- ~~**GR-E01 vs GR-S01** — 4/6/9 against 5/7/9, no dataset reconciles
+  them~~ — **withdrawn 2026-08-05, before sending.** The adversarial
+  review (C1) found `2da19a4` had already measured **6/9/12 against
+  5/7/9**: the dataset reconciles them and the scenario is now
+  `-reachable-`. Sending this would have been the **fourth** wrong premise
+  to reach `ground-game`, and the only one caught before transmission.
+  **Report the withdrawal, not the finding** — GROUND-WP-0002 holds the
+  original, and a claim retracted silently is how the first three
+  survived.
 
 ## Task: evidence