Claude Code First, specification version 0.1.0. The plain-language guide
Version 0.1.0. Level 2. Best evidence grade R3/S3.
VG-8 A closing check
A task that changes behaviour MUST NOT be recorded as shipped until a check that a gate runs covers that behaviour as committed.
| Field | Value |
|---|---|
| Keyword | MUST NOT |
| Level | 2 |
| Checked | by judgement |
| Findings | F305, F104 |
| Harness facts | none |
| Threat | construct: Shio's own reading ties the failures to its commit rate |
| Status | active |
Rationale: six corrections in Shio shipped half of themselves, three of them shipping the report and leaving the behaviour; in freewilly DD75 shipped, "so the new behaviour was verified by hand and by nothing the build runs" [freewilly@c1c2eaf:docs/CHANGELOG.md#L22]; each project answered by making a check part of closing (F305, R3/S3). The ledger records the shipping session's own claim, so without a check nothing tells a true entry from an untrue one (F104, R3/S3). Shio's form of the remedy, SH527, closes a defect with an assertion carrying its id so the unasserted ones can be computed; whether that form catches what it is built for is an open question below. Where the check cannot run on the machine, because it needs hardware or a person's judgement, the task is not closed by the agent: that is the subject of chapter HR.