reconcile: contract the concept check's third finding and the lifecycle- reservation

Test-SpecSet.ps1 raises a concept finding when a lifecycle- region names something
outside the derived concept set, and S6.5 tests it, but the contract's Checks table
listed only two concept rows and Authored records said stateless mechanisms are
'judged on the full-audit path' - which reads as the checker staying out of the way.

- 20-contract.md: the third finding row, and the rule that the lifecycle- vocabulary
  is reserved to the derived set, on SS15's precedent and for the same reason

No new SS id: an id is assigned once, and the row plus the sentence already bind.
Decision recorded in 90-decisions.md and design/state/decisions/.

Author: claude

design/20-contract.md

@@ -157,6 +157,14 @@ judged on the full-audit path. This bounds the fourth brief condition to somethi
 the index; the broad reading is not enumerable mechanically at all, and a check that cannot know
 what is missing does not check completeness.
 
+**The `lifecycle-` vocabulary is reserved to the derived set, and a region naming anything else
+is a finding** — SS15's rule one check over, and for the same reason. A stateless mechanism's
+lifecycle is documented in ordinary prose, which is where the full-audit path reads it; a marked
+region is how a *checked* obligation is declared, and one naming a subject no check can enumerate
+declares nothing. What the reservation actually buys is the misspelling: `lifecycle-PlayerStat`
+is otherwise an orphaned region that every check silently skips, on a document the report then
+calls clean.
+
 ### Content path records
 
 Nine record classes, five authored and four derived, and the authored/derived split answers the
@@ -754,6 +762,7 @@ A check produces findings, not errors. Findings yield `State = 'Invalid'`, exit
 | `provisional` | A provisional site has no register row, or a register row has no site |
 | `concept` | A state-bearing concept has no `lifecycle-` region |
 | `concept` | A lifecycle region states creation but not retirement, or retirement but not creation |
+| `concept` | A `lifecycle-` region names something outside the derived concept set |
 | `reference` | A section or document reference resolves to nothing |
 | `reference` | A cross-repository reference carries no pinned sha |
 

design/90-decisions.md

@@ -9,6 +9,33 @@ Append-only. Newest at the top. The rejected alternatives are the point — with
 
 ---
 
+### 2026-08-31 — The `lifecycle-` marker vocabulary is reserved to the derived concept set
+Context: `Test-SpecSet.ps1`'s concept check raises a third finding the contract's § *Checks* table
+does not list — a `lifecycle-` region whose name is outside the derived concept set — and S6.5
+tests it. § *Authored records* meanwhile says stateless mechanisms "are outside the derived
+concept set and are judged on the full-audit path", which reads as the checker staying out of the
+way for them, while the check next door fails the build on one. Two readings of one rule, with the
+code and the prose each holding a different half.
+Chosen: The contract gains the finding row and the rule behind it — the `lifecycle-` vocabulary
+is reserved to the derived set, a stateless mechanism's lifecycle is documented in ordinary prose
+where the full-audit path reads it, and a region naming anything else is a finding. This is SS15's
+rule one check over ("only a closed declaration may carry a mirror obligation") and is kept for
+the same reason: what the reservation actually buys is the misspelling. `lifecycle-PlayerStat` is
+otherwise an orphaned region every check silently skips, on a document the report then calls
+clean. No new `SS` id is minted for it — an id is assigned once and never renumbered, and the
+finding row plus the sentence already bind.
+Rejected: Deleting the third variant and its S6.5 test, which makes the contract true as written
+and lets an author put a stateless mechanism's lifecycle in a marked region. Rejected because it
+removes tested behaviour to match prose rather than the other way round, and because it buys that
+freedom by making the typo case silent — the mirror check flags "names a declaration that does not
+exist" for exactly this reason, and the two checks would then disagree about the same mistake.
+Also rejected: adding the row and leaving § *Authored records* alone — cheapest, and it leaves the
+sentence still reading as though the checker stays out of the way, which is the two-readings state
+this entry exists to end.
+Reversibility: cheap — one table row and one paragraph, and the deletion stays available.
+
+---
+
 ### 2026-08-31 — CP2 and CP3 are scoped to production sources, and the CP3 check is tightened to match
 Context: `/reconcile` found CP3 ("Nothing in this repository reads a file under `content/`",
 Enforcement `Code`, Evidence `src/published-surface.test.ts`) broken in the tree:

design/state-index.md

@@ -159,6 +159,7 @@ This document is a navigation view generated from `design/state/`. Edit the reco
 | decision/2026-08-30-the-game-content-path-enters-design-through-a-design-pass-before-it-is-contracted-or-sliced | `unit/document/design-10-design`, `unit/document/design-20-contract`, `unit/document/design-30-slices` |
 | decision/2026-08-31-a-length-narrowing-on-a-collection-field-is-cp10-compliant-s21-3-is-fully-met | — |
 | decision/2026-08-31-cp2-and-cp3-are-scoped-to-production-sources-and-the-cp3-check-is-tightened-to-match | — |
+| decision/2026-08-31-the-lifecycle-marker-vocabulary-is-reserved-to-the-derived-concept-set | — |
 <!-- decision-affects:end -->
 
 ## Question affects

design/state/decisions/2026-08-31-the-lifecycle-marker-vocabulary-is-reserved-to-the-derived-concept-set.md

@@ -0,0 +1,14 @@
+# decision/2026-08-31-the-lifecycle-marker-vocabulary-is-reserved-to-the-derived-concept-set
+Date: 2026-08-31
+Anchor: 2026-08-31 — The `lifecycle-` marker vocabulary is reserved to the derived concept set
+Status: accepted
+
+## Claim
+A `lifecycle-` region may name only a member of the derived concept set, and one naming anything
+else is a `concept` finding — the row is in `design/20-contract.md` § *Checks* and the rule in
+§ *Authored records*. A stateless mechanism's lifecycle is documented in ordinary prose, which is
+where the full-audit path reads it; a marked region declares a checked obligation, and one whose
+subject no check can enumerate declares nothing. The reservation's real value is that a
+misspelled concept name is a finding rather than an orphaned region every check skips on a
+document the report then calls clean. It is SS15's rule one check over, and carries no `SS` id of
+its own.