CB-WP-0022 T03: ADR-0012 -- the register already existed, and the rule was
one clause short
Nine decisions. Two were not on T03's list; both are the review's.
D2: specs/GroundRules.md §Underdetermined IS the register. C4 pointed out
it was never evaluated as a candidate, and against the survey's own five
benchmarks it already delivers four -- including the Magic Oracle property
("a ruling flips the scenario, not the kernel", :231-233) that the survey
travelled to Magic to discover and we had written down ourselves eight
days earlier. What it lacks is reproductions. So this pass extends a
section rather than building a register: no new file, no new schema, and
no second mechanism to disagree with the first.
D3: admissibility is three clauses. It exists; it has the ruled shape
(GROUND-WP-0004 T02's row-level table, never a sum -- promoted from a T04
addendum because two of three wrong premises were sums without tables);
and it CAN FAIL. The third is C1's. GR-E01's scenario went green when the
edition landed, and the finding stayed admissible and stayed queued for
transmission, because nothing in the rule said a passing artifact was a
signal. A green reproduction is an alarm, not a reassurance.
D1 applied: INTENT gains a fourth property, Instrument, worded as a
mechanism rather than an ambition and carrying its own falsifier -- if a
pass tolerates an undecided rule by quietly picking a default, the
property is false.
D4 five kinds, each forced by an existing finding; a sixth during backfill
means the taxonomy was invented. D5 lifecycle where `applied` means the
source changed, the queue empties while the log accumulates, and
withdrawals are reported rather than deleted -- GR-E01 is why. D6 notes
admitted but never reportable, 30-day expiry on the existing age
machinery; refusing them would discard the only class of finding the
engine cannot produce itself, which is CB-WP-0025's whole input. D7 no
engine-evolution register, on an inventory C5 corrected -- narrowed, not
settled. D8 design-baseline.py retired, kept as a dated snapshot because
deleting it erases the evidence for how 33% got in. D9 the artifact stays
here, ground-game gets a generated file under its own workplan.
loop-lint: no findings. facts-check: no findings.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
04c3a4977f
commit
580081ef71
3 changed files with 316 additions and 2 deletions
|
|
@ -229,7 +229,7 @@ commit — quoted the dead number twice.
|
|||
|
||||
```task
|
||||
id: CB-WP-0022-T03
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "a2e85810-e949-4ea0-81fc-36b912af326c"
|
||||
```
|
||||
|
|
@ -250,6 +250,39 @@ state_hub_task_id: "a2e85810-e949-4ea0-81fc-36b912af326c"
|
|||
as a note** — and if admitted, how it is prevented from aging into an
|
||||
apparent finding.
|
||||
|
||||
**Done 2026-08-05.**
|
||||
[ADR-0012](../decisions/ADR-0012-the-design-instrument.md), nine
|
||||
decisions. The two that were not on this list are the two the review
|
||||
forced:
|
||||
|
||||
- **D2 — `§Underdetermined` *is* the register; nothing parallel is built.**
|
||||
C4's point, checked and conceded: against the survey's own five
|
||||
benchmarks the incumbent already delivers four, including the Oracle
|
||||
property the survey went to Magic to find and we had written down
|
||||
ourselves eight days earlier (`GroundRules.md:231-233`). What it lacks
|
||||
is reproductions. So the pass **extends** a section instead of building a
|
||||
register — no new file, no new schema.
|
||||
- **D3 — admissibility is three clauses, not one.** Exists, has the ruled
|
||||
shape (row-level table, never a sum), **and can fail.** The third is
|
||||
C1's: GR-E01's artifact went green when the edition landed and the
|
||||
finding stayed admissible and stayed queued, because nothing said a
|
||||
passing artifact was a signal. **A green reproduction is an alarm.**
|
||||
|
||||
The rest: **D1** INTENT gains property 4, *Instrument* — applied, with the
|
||||
falsifier in the text. **D4** five kinds, each forced by an existing
|
||||
finding, and a sixth appearing during backfill means the taxonomy was
|
||||
invented. **D5** lifecycle with `applied` meaning *the source changed*, the
|
||||
queue emptying while the log accumulates, and **withdrawals reported, not
|
||||
deleted** — GR-E01 is why. **D6** notes admitted but never reportable, with
|
||||
a 30-day expiry on the existing age machinery; refusing them would have
|
||||
thrown away the only class of finding the engine cannot produce itself,
|
||||
which is CB-WP-0025's entire input. **D7** no engine-evolution register,
|
||||
on an inventory C5 corrected — argued and narrowed, not settled. **D8**
|
||||
`design-baseline.py` retired, not extended; kept as a dated snapshot
|
||||
because deleting it erases the evidence for how 33% got in. **D9** the
|
||||
finding and its artifact stay here; ground-game gets a generated file
|
||||
under its own workplan, citing the reproduction by path.
|
||||
|
||||
## Task: specify
|
||||
|
||||
```task
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue