F.18:5.4 - System-Role-Kind Relations, Method Relations, System-Role–Method Relations, and Lens Names
System-role-kind-relation expressions remain ordinary expressions or direct relations unless their exact local kinds and relation predicates are already admitted. An algebraic, graph, matrix, embedding, distributed, or neural description is a lens over the selected SystemRoleKindRelationStructure; it is not automatically the named kind, holder, assignment, Method, or Work.
First recover what the name is for:
| Expression or source phrase | What can be named | Naming rule |
|---|---|---|
R1 <= R2 | one exact directional admission-substitution relation occurrence between two independently admitted local system-role kinds, identified by the ordered kinds, receiving-use rule, applicability, and only meaning-changing semantic-basis editions | Name or cite the exact relation occurrence or a selected SystemRoleKindRelationStructure; keep any assertion or policy record, current assignment, receiving check, and outcome separate. Admit another system-role kind only when its own C.3 identity and membership basis warrant it. |
R1 incompatibleWith R2 | one exact symmetric incompatibility relation occurrence between two independently admitted local system-role kinds, identified by the unordered pair, same- or different-holder rule, Work identity, overlap test, applicability, and only meaning-changing semantic basis | Name or cite the exact relation occurrence or a selected SystemRoleKindRelationStructure, not another system-role kind. Exact assignments and the receiving Work remain separate inputs and do not replace the two kind participants. |
R1 and R2 | two independently admitted system-role kinds; any assignment occurrences are separate and are required only when the receiving sentence also claims them | Use “and” in ordinary prose. Keep the two kind claims recoverable, and do not infer assignments or make a compound kind by hyphenating the labels. |
R1 bundle R2, or quoted source shorthand RoleBundle := R1 and R2 | one order-insensitive finite-set relation among exact system-role kinds, with a joint-admission and holder-allocation predicate | Keep it as a bundle relation. A convenient bundle name does not admit a compound system-role kind; such a kind would need its own independent C.3 identity and use. |
R1 qualified by a domain, practice, Method family, or ordinary work field | either one independently admitted local system-role kind or a residual A.2.7 qualification relation between two kinds | Before naming a kind, recover its C.3 candidate domain, operative membership condition, intended member/non-member boundary, and continuity rule. A domain, practice, ordinary work field, Method, Work family, or performed Work occurrence remains a separate value or comparison cue. Keep a non-monotonic restriction as its exact relation and do not infer admission substitution. |
| Method-like phrase derived from a system-role label | Method, Method family, MethodDescription, WorkPlan, or Work occurrence | Name the recovered object through A.3.1, A.3.2, or A.15; cite the exact system-role-kind relation separately when it constrains admission or performance. |
| algebraic, graph, matrix, embedding, distributed, or neural representation of system-role kinds or their relations | mathematical or representation description of a selected SystemRoleKindRelationStructure | Name the lens only when the representation itself is the object being named; otherwise name the recovered kind, relation occurrence, selected structure, Method, assignment, or Work. |
| Method algebra, Method graph, Method matrix, process calculus, selector calculus, or Method embedding | mathematical or representation description of exact method-side relations or their selected MethodRelationStructure | Name the lens only when the representation itself is the object being named; otherwise name the exact relation, selected structure, Method family, MethodDescription, WorkPlan, Work occurrence, or neighboring relation. |
Ordinary speech may say “surgeon”, “reviewer”, or “operator” when the local sentence makes the intended system-role kind or assignment obvious. Use the concrete ...SystemRole designation when stable technical reference to the kind is needed. Do not infer kind identity, assignment, relation, Method, capability, or Work from the ordinary word alone. Add a qualifier only when it distinguishes a live neighboring reading.