Sync hub IDs for CB-WP-0006; T04-T06 cancel not deferred
Some checks failed
ci / check (push) Failing after 3s
Some checks failed
ci / check (push) Failing after 3s
The hub's task status vocabulary is wait|todo|progress|done|cancel, so 'deferred' was rejected by fix-consistency. 'cancel' is the accurate one: these task records are superseded and equivalents live in CB-WP-0006 T05-T07. The work is deferred, not abandoned, and the workplan says so. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
74d9b8ef73
commit
56c0c34d2c
3 changed files with 34 additions and 9 deletions
|
|
@ -13,6 +13,7 @@
|
|||
| workplan | CB-WP-0003 | done | — | workplans/CB-WP-0003-loop-hardening.md |
|
||||
| workplan | CB-WP-0004 | done | — | workplans/CB-WP-0004-mechanical-work.md |
|
||||
| workplan | CB-WP-0005 | proposed | — | workplans/CB-WP-0005-assertion-coverage.md |
|
||||
| workplan | CB-WP-0006 | proposed | — | workplans/CB-WP-0006-instrument-the-table.md |
|
||||
| task | CB-WP-0001-T01 | done | — | workplans/CB-WP-0001-inner-loop.md |
|
||||
| task | CB-WP-0001-T02 | done | — | workplans/CB-WP-0001-inner-loop.md |
|
||||
| task | CB-WP-0001-T03 | done | — | workplans/CB-WP-0001-inner-loop.md |
|
||||
|
|
@ -46,11 +47,20 @@
|
|||
| task | CB-WP-0004-T04 | done | — | workplans/CB-WP-0004-mechanical-work.md |
|
||||
| task | CB-WP-0004-T05 | done | — | workplans/CB-WP-0004-mechanical-work.md |
|
||||
| task | CB-WP-0004-T06 | done | — | workplans/CB-WP-0004-mechanical-work.md |
|
||||
| task | CB-WP-0005-T01 | todo | — | workplans/CB-WP-0005-assertion-coverage.md |
|
||||
| task | CB-WP-0005-T02 | todo | — | workplans/CB-WP-0005-assertion-coverage.md |
|
||||
| task | CB-WP-0005-T03 | todo | — | workplans/CB-WP-0005-assertion-coverage.md |
|
||||
| task | CB-WP-0005-T04 | todo | — | workplans/CB-WP-0005-assertion-coverage.md |
|
||||
| task | CB-WP-0005-T05 | todo | — | workplans/CB-WP-0005-assertion-coverage.md |
|
||||
| task | CB-WP-0005-T06 | todo | — | workplans/CB-WP-0005-assertion-coverage.md |
|
||||
| task | CB-WP-0005-T01 | done | — | workplans/CB-WP-0005-assertion-coverage.md |
|
||||
| task | CB-WP-0005-T02 | done | — | workplans/CB-WP-0005-assertion-coverage.md |
|
||||
| task | CB-WP-0005-T03 | done | — | workplans/CB-WP-0005-assertion-coverage.md |
|
||||
| task | CB-WP-0005-T04 | cancel | — | workplans/CB-WP-0005-assertion-coverage.md |
|
||||
| task | CB-WP-0005-T05 | cancel | — | workplans/CB-WP-0005-assertion-coverage.md |
|
||||
| task | CB-WP-0005-T06 | cancel | — | workplans/CB-WP-0005-assertion-coverage.md |
|
||||
| task | CB-WP-0005-T07 | todo | — | workplans/CB-WP-0005-assertion-coverage.md |
|
||||
| task | CB-WP-0005-T08 | todo | — | workplans/CB-WP-0005-assertion-coverage.md |
|
||||
| task | CB-WP-0006-T01 | todo | — | workplans/CB-WP-0006-instrument-the-table.md |
|
||||
| task | CB-WP-0006-T02 | todo | — | workplans/CB-WP-0006-instrument-the-table.md |
|
||||
| task | CB-WP-0006-T03 | todo | — | workplans/CB-WP-0006-instrument-the-table.md |
|
||||
| task | CB-WP-0006-T04 | todo | — | workplans/CB-WP-0006-instrument-the-table.md |
|
||||
| task | CB-WP-0006-T05 | todo | — | workplans/CB-WP-0006-instrument-the-table.md |
|
||||
| task | CB-WP-0006-T06 | todo | — | workplans/CB-WP-0006-instrument-the-table.md |
|
||||
| task | CB-WP-0006-T07 | todo | — | workplans/CB-WP-0006-instrument-the-table.md |
|
||||
| task | CB-WP-0006-T08 | todo | — | workplans/CB-WP-0006-instrument-the-table.md |
|
||||
| task | CB-WP-0006-T09 | todo | — | workplans/CB-WP-0006-instrument-the-table.md |
|
||||
|
|
|
|||
|
|
@ -238,6 +238,11 @@ downgrade inline, so a reader of the spec cannot reach the old claim.
|
|||
> T04, T05 and T06 stay in this file, unstarted, with their analysis
|
||||
> intact; they move to **CB-WP-0006**, which is scoped to the finding that
|
||||
> was actually measured rather than the one that was predicted.
|
||||
>
|
||||
> They carry `status: cancel` — the hub's status vocabulary is
|
||||
> `wait|todo|progress|done|cancel`, and of those `cancel` is the accurate
|
||||
> one: *these* task records are superseded, and equivalents live in
|
||||
> CB-WP-0006 T05–T07. The work is deferred, not abandoned.
|
||||
|
||||
## Phase C — implement what the instruments expose (deferred)
|
||||
|
||||
|
|
@ -245,7 +250,7 @@ downgrade inline, so a reader of the spec cannot reach the old claim.
|
|||
|
||||
```task
|
||||
id: CB-WP-0005-T04
|
||||
status: deferred
|
||||
status: cancel
|
||||
priority: high
|
||||
state_hub_task_id: "35876b28-97ac-4379-bb71-72e74c4116d4"
|
||||
```
|
||||
|
|
@ -273,7 +278,7 @@ the length prefix → reject. K11's operative clause is *detection*.
|
|||
|
||||
```task
|
||||
id: CB-WP-0005-T05
|
||||
status: deferred
|
||||
status: cancel
|
||||
priority: high
|
||||
state_hub_task_id: "8592b6e7-8b83-4b47-b310-90e16a35eb6a"
|
||||
```
|
||||
|
|
@ -308,7 +313,7 @@ charged to **AM-4b** (9.4% headroom), not AM-4a.
|
|||
|
||||
```task
|
||||
id: CB-WP-0005-T06
|
||||
status: deferred
|
||||
status: cancel
|
||||
priority: medium
|
||||
state_hub_task_id: "774b1c8a-71c1-4e0a-91b1-0247a3e397cf"
|
||||
```
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
id: CB-WP-0006
|
||||
title: "Instrument the acceptance table, then implement what it exposes"
|
||||
status: proposed
|
||||
state_hub_workstream_id: "8a6327cc-fd5c-4e2c-a29b-b437c27d1e71"
|
||||
---
|
||||
|
||||
# Purpose
|
||||
|
|
@ -39,6 +40,7 @@ Per InnerLoop §Step 4, no target moves in the commit that measures it.
|
|||
id: CB-WP-0006-T01
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "a4513794-2f5f-480c-be30-56658711796f"
|
||||
```
|
||||
|
||||
The sharpest single finding of CB-WP-0005. **Nothing in the workspace
|
||||
|
|
@ -67,6 +69,7 @@ to `red`.
|
|||
id: CB-WP-0006-T02
|
||||
status: todo
|
||||
priority: medium
|
||||
state_hub_task_id: "d1572a4f-46e5-49dd-b1ec-7c371a780bb7"
|
||||
```
|
||||
|
||||
AM-2 (≤40 spec lines per rule) and AM-3 (≤50 LOC for the synthetic
|
||||
|
|
@ -88,6 +91,7 @@ restated or withdrawn with an argument rather than left unmeasured.
|
|||
id: CB-WP-0006-T03
|
||||
status: todo
|
||||
priority: medium
|
||||
state_hub_task_id: "6c84a220-cab3-40f1-b35f-b8df79106f6e"
|
||||
```
|
||||
|
||||
AM-5 (clean build ≤60 s) is `recorded not gated` — and not recorded
|
||||
|
|
@ -106,6 +110,7 @@ leaving them blank while the scoreboard reports elsewhere.
|
|||
id: CB-WP-0006-T04
|
||||
status: todo
|
||||
priority: low
|
||||
state_hub_task_id: "a2571314-4c02-41cf-9473-96d3ae2d7b2b"
|
||||
```
|
||||
|
||||
`reported, not targeted`, so there is no property to invert and it counts
|
||||
|
|
@ -135,6 +140,7 @@ threshold *after* seeing that movement would be the retarget InnerLoop
|
|||
id: CB-WP-0006-T05
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "2a357dbf-3861-499d-a12e-f7682b7332f6"
|
||||
```
|
||||
|
||||
Inherited from CB-WP-0005 T04. K9's acceptance property (snapshot at N +
|
||||
|
|
@ -153,6 +159,7 @@ exists and the suite does not.
|
|||
id: CB-WP-0006-T06
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "d459444d-41be-40c5-9101-7a8420b42fb6"
|
||||
```
|
||||
|
||||
Inherited from CB-WP-0005 T05. INTENT design decision 8 of 10,
|
||||
|
|
@ -171,6 +178,7 @@ about.
|
|||
id: CB-WP-0006-T07
|
||||
status: todo
|
||||
priority: medium
|
||||
state_hub_task_id: "d76ad893-520b-44bd-9b77-07dbfb651ce3"
|
||||
```
|
||||
|
||||
Inherited from CB-WP-0005 T06. `CommitWindow` has zero non-test users;
|
||||
|
|
@ -187,6 +195,7 @@ right for K18.
|
|||
id: CB-WP-0006-T08
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "1d4455c3-c642-47d8-916b-ab35bc512207"
|
||||
```
|
||||
|
||||
Commit `evidence/CB-EV-0004`. The baseline is **4 of 14**, committed and
|
||||
|
|
@ -210,6 +219,7 @@ Three tests, all reported:
|
|||
id: CB-WP-0006-T09
|
||||
status: todo
|
||||
priority: medium
|
||||
state_hub_task_id: "4f291d5a-90f0-4f1f-bcaf-7ec28856bfcf"
|
||||
```
|
||||
|
||||
The question CB-WP-0005 T08 raised and this pass is positioned to answer.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue