Claude Code First, specification version 0.1.0. The plain-language guide
Version 0.1.0. Level 2. Best evidence grade R2/S2.
CS-1 A session claims its task and its paths
A session working in a checkout that other sessions share SHOULD hold a claim naming its task and the paths its commit will own.
| Field | Value |
|---|---|
| Keyword | SHOULD |
| Level | 2 |
| Checked | by judgement |
| Findings | F201 |
| Harness facts | none |
| Threat | external: one person running several sessions, no teams |
| Status | active |
Rationale: in roadkeep the first incident, two commits each holding the other's task, was answered the same day by a claim that "carries the paths its commit owns" [roadkeep@3655014c], so that a second session is sent to other work and each commit knows which paths are its own (F201, R2/S2). Shio's sessions reached the same separation without a claim, by stating in each commit what another session had in flight, as in "Hand-authored and staged by path: another session has seven Java files in flight." [shio@871410748] The failure recurred in one project only, and whether the claim ended it is not recorded, so the keyword is SHOULD. How long a claim lasts is an open question.