E.10.D2:11.1 - Description of a system-role kind

A method author needs readers to recognize the local kind currently named ChangeAuthoritySystemRole before checking any assignment. The kind is recovered through its system-candidate domain, work-facing membership condition, member/non-member boundary, and continuity rule; OperationsReview provenance locates that definition but does not identify the kind. ChangeAuthoritySystemRoleKindDescription is a C.2.1 episteme whose exact EntityOfConcern is that independently admitted kind, whose ClaimGraph describes the distinction in readable terms, and whose effective scheme is the selected operations-review reference scheme.

For the named operations-review use, record the exact operations viewpoint only if it changes which work-facing claims the review reads or checks; otherwise name the use and omit viewpoint selection. The ClaimGraph may cite credential criteria, a mandate window, separation-of-duty constraints, capability expectations, and a direct SystemRoleAssignmentStateRelation when those neighbors are current. The system-role-kind description contains none of the assignment, checklist, graph, criteria, or relation occurrence. The description admits no holder and creates no U.SystemRoleAssignment.

The receiving use needs recognizability, not specification force, so the practitioner stops with the description. A specification use opens only if exact checkable system-role-kind claims and their checking harness are named.