F.18:5.1 - System-Role-Kind Names

A durable system-role-kind name designates one exact local kind admitted through C.3 and A.2. Recover that kind through its candidate domain, operative membership condition, intended member/non-member boundary, and continuity rule. A practice or source reference can locate the definition or signal that two definitions should be compared; it does not identify the kind. Candidates are entities already admitted under A.1 as U.System, including a person, team, organization, or non-human technical object. The Tech designation normally ends in ...SystemRole, for example ReviewerSystemRole, ShipbuilderSystemRole, or ServiceProviderSystemRole. SystemRole is compound morphology, not a universal governed value. The name creates no system admission, kind membership, assignment, agency, capability, or Work.

A system-role-kind name must not include:

• the holder of an assignment or the assignment occurrence;
• capability evidence or skill level;
• method or method-family selection;
• performed Work;
• status value or gate result;
• source, evidence, publication, or assurance use.

If a phrase such as SeniorReviewer, NightOperator, or source wording such as evidence role appears, recover the current claim first. The result may be an exact local system-role kind, one direct assignment occurrence, a status assertion, an evidence-use relation, a Work admission condition, another governed value, or a local source phrase. Do not force all of them into one system-role-kind name.