F.17:12.1 - System-role-kind name becomes public across two project contexts

One project has an exact local DesignReviewerSystemRole kind and another has an independently governed ExternalAuditReviewerSystemRole kind. Both local expressions say reviewer, but one classifies an admitted System that may perform design-review Work and the other classifies an admitted assurance System that may produce an audit report. Any actual assignment and Work are separately identified.

The UTS row does not declare one universal reviewer kind. It creates two rows. Only when a named use really needs correspondence between their two exact sense cells may it cite an obtaining F.9 Bridge plus an affirmative C.2.1 claim that names direction, label rule, and tolerated loss. Each row cites the pattern that defines or constrains its local system-role kind, its SystemRoleKindDescription when current, and the F.18 NameCardRef. Use A.10 or B.3 to state reliance on the use claim; no row or card creates an assignment or review Work.