Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 10:17:34 UTC · last check 2026-10-03 10:30:16 UTC
C.2.2a:7 - Conformance Checklist
CC-C.2.2a-1U.LanguageStateSpaceSHALL be treated as the declared language-state chart over U.CharacteristicSpace, not as a rival kernel space and not as a disguised F progression.
CC-C.2.2a-2 Published positions SHALL cite explicit facet subject patterns when those positions matter for movement, routing, or endpoint entry.
CC-C.2.2a-3 Position claims SHALL use slot-explicit values, ValueSet claims, or intervals; uncertainty SHALL NOT be hidden inside stage words such as ready, early, or mature.
CC-C.2.2a-4 A position claim in the chart MUST NOT be conflated with the current ground, witness, publication form, publication face, or carrier.
CC-C.2.2a-5 Cross-context use SHALL recover the two exact F.17 local senses and test the direct F.9 predicate. Cite a Bridge only when it obtains; keep the bounded-use claim, reliance, and any optional loss note separate. If it does not obtain, keep the local positions distinct and name the missing comparison or translation governor.
CC-C.2.2a-6 Corridor and navigation notes MUST NOT be read as relocation of facet, seam, bridge, or downstream subject-pattern semantics into the chart subject-pattern set.
CC-C.2.2a-7 If a position claim is used for routing, endpoint entry, or gate-adjacent reasoning, the threshold note and the bearer-lane distinction between positioned episteme publication, publication form, face, and carrier SHALL remain explicit or explicitly inherited from a pinned upstream publication.