Claude Code First, specification version 0.1.0. The plain-language guide
Version 0.1.0. Level 1. Best evidence grade R3/S3.
CD-2 A batch is worked one task at a time
When a session is asked to work several tasks, it SHOULD commit each task, after its gate has passed on the tree that commit holds, before it starts the next.
| Field | Value |
|---|---|
| Keyword | SHOULD |
| Level | 1 |
| Checked | by judgement |
| Findings | F203, F305 |
| Harness facts | none |
| Threat | internal: the loop remedy is one copied origin and was never seen failing a batch |
| Status | active |
Rationale: most batching commits in F203 name several tasks in their subject, and in winwright 18 of the 19 that do fall within eight days; each project's rule singles out a request to work several tasks as the occasion for batching. F305 (R3/S3) shows the cost of closing without a check on the change as committed: in winwright the ship step edited the roadmap after the run that proved the work, so "The red then lands on whoever runs next, about an entry their change never touched." [winwright@a686d44] Working a batch as a sequence of single tasks, each committed on a passing gate, keeps each close checkable and each red attributable to one task. The keyword is SHOULD because the evidence is for the parts, batching and unchecked closes, and not for the loop as a whole, which is one prescription copied between the projects and never measured.