F.4:5 - Invariants
- One described kind. A
SystemRoleKindDescriptiondescribes exactly one local system-role kind. - Direct kind identity. The candidate domain, operative membership condition, intended member/non-member boundary, and continuity rule remain recoverable. A source, practice, taxonomy row, signature edition, or scheme helps locate, state, or interpret that basis; none decides identity by itself.
- Description boundary. The description is a
U.Episteme; it is not the kind, candidate, classification judgment, assignment, holder system, capability, Method, Work, or status-use relation. - System range. A candidate must independently pass A.1 as
U.System. No description or kind name performs that admission, andSystemRoledoes not narrow the candidate to non-human technical systems. - No hidden assignment. Classification under a local kind neither creates nor proves a
U.SystemRoleAssignmentoccurrence. - No hidden capability. Capability requirements may be cited, but the description proves no capability.
- No hidden Method. Method requirements may be cited, but the description is not a MethodDescription.
- No hidden Work. The description may support later Work-attribution checks, but it is not evidence that Work occurred.
- No status or episteme-use fusion. Status, evidence, source, requirement, publication, and assurance uses remain direct relations, not another description branch.
- Position discipline. Bare role that denotes participation, a declaration slot, interface place, or representation position is recovered through E.10.ROLE and A.6.RSIR rather than made a system-role kind.
- Name after meaning. Durable naming follows F.18 only after the exact kind, description, scheme, and local sense are recovered.