coulomb/clay-borg
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

CB-WP-0005 T08: attribution note — one commit, one task id

Browse source 
T07 and T08 shipped in one commit, so CA-08 attributed the substantive
work of both to T07 and left T08 with no bucket. task-done refused to
close it rather than invent a number, which is the contract working as
designed. Recorded in the workplan.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-07-31 18:06:02 +02:00
parent fd19f4e878
commit 2fe577213c
1 changed files with 9 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

10
workplans/CB-WP-0005-assertion-coverage.md
View file

@ -279,7 +279,7 @@ state_hub_task_id: "774b1c8a-3b26-4c4f-a2c8-46cb0b7ba5a7"
```task
id: CB-WP-0005-T07
status: todo
status: done
priority: high
state_hub_task_id: "a34baa46-fbfd-473b-9e15-811e17697791"
```
@ -390,6 +390,14 @@ having**. `mutation-check` fails that test and still produced the most
valuable findings of the pass. T06 stated it too strongly; this pass is
the counter-example.
**Attribution note.** T07 and T08 shipped in one commit, and CA-08 keys on
the first qualified task id in the subject — so T07's bucket ($3.06 over
13 responses) covers the substantive work of both, and T08's own figure
covers only its close. `make task-done` refused to close T08 at all until
a commit named it, which is the "no estimates" contract working as
designed rather than a defect. The lesson is cheap: **one commit, one
task id**.
**InnerLoop v1.4** adopted: where a claim rests on numbers, the
adversarial reviewer must read the assertion behind each quoted number and
**mutate it**. Re-running the command that prints a number is not