Claude Code First, specification version 0.1.0. The plain-language guide
Version 0.1.0. Level 1. Best evidence grade R3/S3.
CD-1 One task per commit
A commit that ships work SHOULD ship one task, and carry that task's code, its tests and its ledger entry together.
| Field | Value |
|---|---|
| Keyword | SHOULD |
| Level | 1 |
| Checked | automatically |
| Findings | F203, F206 |
| Harness facts | none |
| Threat | internal: the written rule and its loop are one origin copied across the projects |
| Status | active |
Rationale: F203 (R3/S3) counts, at each pin, the commits that add two or more shipped entries to the ledger: 21 of 486 in winwright, 8 of 1,177 in roadkeep and 3 of 281 in freewilly, all under a written rule against it. The grade would admit a MUST, but polyweave is a contrary case, with no such commit in 110, and no source explains the difference by a property of the cases, so the rule is one level lower. A commit that holds one task and its ledger entry is what lets the history be read back against the ledger by task id (F206, R2/S3), which is how the counts in F203 were made. Conformance is decided from the repository: count, per commit, the shipped entries it adds to the ledger, as F203's command does. The count is a lower bound, since it cannot see a second task's code carried under one ledger line.