Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-19 22:26:44 UTC · snapshot created 2026-11-19 22:27:31 UTC · last check 2026-11-19 23:10:10 UTC

A.2.7:9 - Rationale

When a receiving check needs several kind relations together, a dependent SystemRoleKindRelationStructure identifies that organization. The assignments remain separate inputs to the check.

The families are separate because their laws differ. Substitution is directional. Incompatibility is symmetric under one joint condition. A bundle uses an order-insensitive finite set and an allocation rule. Monotonic qualification belongs to U.SubkindOf; non-monotonic restriction stays residual. One generic hierarchy cannot preserve those distinctions.

Direct predicates determine obtaining, and identity laws determine whether the same world-side relation occurrence continues; assertions, policies, and diagrams describe those facts. Slot discipline makes context-local participant domains reviewable and keeps the system-role kind, holder, assignment, predicate, slot, and representation position distinct.