Claude Code First, specification version 0.1.0. The plain-language guide
Version 0.1.0. Level 2. Best evidence grade R3/S3.
VG-7 An expiring exception for a known red
A gate that is to stay red while other work continues SHOULD be covered by a red-suite exception that a check turns red once it expires.
| Field | Value |
|---|---|
| Keyword | SHOULD |
| Level | 2 |
| Checked | by judgement |
| Findings | F303, F304 |
| Harness facts | none |
| Threat | internal: the exception ledger is one project's remedy |
| Status | active |
Rationale: the red suites that nobody mentioned for nineteen commits in Shio were red with no record that anyone knew (F303, R3/S3). Shio's answer, with SH579, is a ledger of dated exceptions whose test works "so a forgotten exception goes red instead of quiet" [shio@821f18d74:red-suites.json#L2]. A red that nobody can act on is ignored (F304), and an exception tied to the task that will fix it gives the red an owner and an end. The problem is graded R3/S3, but the ledger is one project's remedy and no source records it firing, so the rule carries SHOULD.