CC-A2.1 | Every system-role kind is one local U.Kind; no U.Role or universal U.SystemRole is introduced. |
CC-A2.2 | The U.System candidate domain, operative work-facing membership condition, intended member/non-member boundary, and continuity rule recover the kind; practice or source provenance only locates or prompts comparison of the definition. |
CC-A2.3 | Kind identity, KindSignature, classification judgment, extension, vocabulary episteme, and reference scheme remain distinct. |
CC-A2.4 | Each judgment names one system, system-role kind, signature edition, slice, and true/false/unknown result. |
CC-A2.5 | Membership clauses use directly governed candidate features; labels, records, judgments, extensions, and proposed subkind edges are not features by form. |
CC-A2.6 | An assignment is a membership feature only when the signature cites its independently obtaining predicate; no family-wide assignment-membership law exists. |
CC-A2.7 | Every assignment occurrence belongs to one directly declared U.SystemRoleAssignment species with an exact local system-role-kind domain. |
CC-A2.8 | Taxonomy, scheme, signature, assertion, and interval description are interpretation or claim content rather than generic assignment participants. |
CC-A2.9 | Capability, state, Method, Work, responsibility, commitment, permission, authority, evidence, reliance, and publication remain separately governed. |
CC-A2.10 | A U.SubkindOf claim follows independently evaluated aligned signatures and C.3.1 monotonicity. |
CC-A2.11 | Same spelling across local practices, sources, or editions does not decide kind identity; continuity and actual relations are explicit. |
CC-A2.12 | Relation-position or ordinary contribution wording creates no system-role kind or assignment by itself. |
CC-A2.13 | A proposed decomposition is resolved through exact relations among kinds or neighboring subject patterns, not partOf over a system-role kind. |
CC-A2.14 | Cross-local use compares the C.3 definitions first and reuses the same kind when its distinction continues; when two kinds are present, it keeps both kinds distinct, cites the exact C.3.3 kind relation and any needed F.9 local-sense relation, and states the bounded use, direction, preservation rule, tolerated loss, polarity, effective scheme, and current reliance needed by the receiver. Assignment occurrences remain independently governed in either branch; a Bridge Card is not a use licence. |
CC-A2.15 | A selected model-use structure appears only in the receiving claim it changes; it neither classifies nor assigns a system and never enters a generic relation as an optional participant. |