A.15:2 - Problem

Without this alignment, several category errors recur:

1. System-role-kind as part. AuditorSystemRole is placed in structural partOf decomposition although it is a local kind used to classify systems.
2. Description as execution. A recipe, algorithm, SOP, or MethodDescription is treated as proof that Work occurred.
3. Capability as Work. Ability and actual performance are collapsed.
4. Incomplete Work basis or attribution. A Work claim lacks its required performer, assignment, or Method basis, or a precise assignment-bound attribution claim lacks its holder-equality check.
5. Assignment as responsibility or authority. Holding a system-role assignment is treated as if it established a duty, permission, responsibility, authority, or approval relation.
6. Universal assignment record. A permissive root signature hides different direct species and turns taxonomy, scheme, context, or source into generic participants.
7. Actor by association. A kind, assignment, capability, Method, description, plan, or record is made to act. Only the admitted holder system performs Work.
8. Process soup. One overloaded source word stands for classification, assignment, Method, description, plan, Work, result, and record at once.