F.5:2 - Problem

Without this pattern:

1. Local terms look global. Observation, Activity, or Process becomes a U-kind name although it carries one practice’s or source’s private commitments.
2. System-role names become hidden admissions. A label such as ReviewerSystemRole is treated as if the local kind or candidate classification already exists.
3. System-role names become hidden assignments. A concrete kind label is treated as if someone is already assigned.
4. System-role names become capability claims. A candidate is assumed able because the kind label sounds competent.
5. System-role names become Methods. A noun label hides a Method or Method family.
6. Description and described kind collapse. PumpInspectorSystemRoleKindDescription is treated as PumpInspectorSystemRole itself.
7. Status names become system-role kinds. For example, Approved, AccessRole, ModelFitEvidenceRole, or RequirementRole creates a fake work-facing classification instead of the exact direct relation.
8. Relation positions become system-role kinds. Signature, relation, or argument-position names borrow role morphology even though they name participation or a declaration place.
9. Names carry interpretation metadata. Task-IEC61131, Participant-BPMN, or ReviewerSystemRole-SchemeA fossilizes an edition, source, local boundary, or scheme in the label.
10. Aliases become silent renames. Several labels circulate for one meaning without lineage or Bridge discipline.