Claude Code First, specification version 0.1.0. The plain-language guide
Version 0.1.0. Level 2. Best evidence grade R3/S3.
VG-5 CI on every push
A gate that decides whether work is done MUST run in CI on every push to the branches work lands on.
| Field | Value |
|---|---|
| Keyword | MUST |
| Level | 2 |
| Checked | automatically |
| Findings | F303, F304 |
| Harness facts | none |
| Threat | internal: two origins, one of them uncounted |
| Status | active |
Rationale: in Shio every workflow was dispatch-only, and two suites stayed red at the head of the branch while "Eleven commits landed over the first and eight over the second, and no commit message" [shio@821f18d74:.github/workflows/suites.yml#L4] mentioned either; freewilly deleted its lint workflow and drift reached main until it came back (F303, R3/S3). Both restored the gate to every push. This follows decision D4 in ../evidence/divergences.md. A gate that cannot run on a hosted runner, such as winwright's suite half that needs an interactive desk (F304), is a documented deviation that names the gate, the reason, and where it does run. A script can decide conformance from the workflow files' triggers and the gates they call.