A.15.3:5.1 - Planned holder designation against one direct system-role-assignment species

An inspection team plans a future assignment of Robot_8. It names InspectionRobotSystemRoleAssignment as the species and Robot_8_Ref as the intended holder. Plan result: one row points to the cited InspectionRobotSystemRoleAssignmentSignature edition and its HolderSystemSlot; Robot_8_Ref : U.EntityRef resolves to admitted Robot_8 : U.System. The species declares InspectionRobotSystemRoleKindDomain as the domain of its local assigned-kind slot and uses InspectionRobotSystemRole as the required value. This plan item records only the planned holder designation. The enclosing A.15.2 WorkPlan separately states InspectionRobotSystemRole as the intended local system-role-kind condition; naming the species fills no occurrence participant. A.2.1 defines the species predicate and occurrence identity, while A.6.5 defines the declaration-local SlotKinds, ValueKinds, and reference modes.

The row establishes neither a U.SystemRoleAssignment occurrence nor actual participation. Later, an affirmative assignment assertion is available only when the direct species predicate holds for its complete real participant set and its occurrence law is satisfied. A type-compatible planned holder can therefore remain the baseline while that predicate either fails under a stated negative criterion or cannot yet be resolved; taxonomy, reference scheme, or generic context is not added as a world-side participant.

Blocked near-miss: Bearing_C isPartOf Pump_P cannot supply a relation row. A.6.5:5.2 keeps PartHolonSlot and WholeHolonSlot hypothetical until a part-relation pattern defines their meanings, predicate, applicability, and occurrence identity. Return missing-governor: planned part-relation participant designation for <Bearing_C, Pump_P> or keep the choice as ordinary A.15.2 plan content; do not present the sketch as an admitted RelationSignature.