A.2:4.1 - Recognize a System-Role Kind

A local kind is a system-role kind only when all of these conditions hold:

1. its candidate ValueKind is U.System;
2. its operative membership condition states the stable, assignable, work-facing contribution and uses directly governed candidate features;
3. at least one intended member and one relevant non-member or boundary case make the distinction testable;
4. its continuity rule says which changes preserve that distinction and which require another kind; and
5. its KindSignature does not treat a label, taxonomy row, description, assignment record, classification judgment, extension row, or proposed U.SubkindOf edge as the feature by form.

The kind asks what continuing distinction classifies candidate systems. A particular C.3.2 judgment asks whether one system satisfies the current signature now. Practice or source provenance shows where to inspect the definition; it neither creates nor splits the kind. CoolingPumpKind is not thereby a system-role kind. Its identity can be a physical or functional pump distinction rather than an assignable work-facing contribution. ShortAssignmentKind, if declared to classify assignment occurrences by duration, is also not a system-role kind because its candidates are assignments rather than systems.