A.2.5:0 - Use This When
Plain designations. Say “this assignment to a system role satisfies this state condition” for the relation and “state condition for an assignment to a system role” for the predicate.
Use this pattern when one exact assignment to a system role already obtains, but a method step, Work occurrence, incompatibility check, or operational gate depends on that assignment satisfying a particular condition during a particular window.
Start with the practical question: Does this exact assignment satisfy this exact state condition throughout the window that matters now? The first useful result is the current SystemRoleAssignmentStateRelation occurrence or its absence. Add an assertion and evidence-use relation only when a later decision must rely on that result.
Typical working moments include these:
- a calibrated inspection robot is assigned to
InspectorSystemRole, but inspection Work should start only while calibration, synchronization, and operating-envelope conditions hold; - an incident commander remains on call, yet a conflict or fatigue condition may make that assignment non-admitting for one response window;
- a method description declares a state condition for an assignment to a system role, while the current assignment has not yet been tested against it;
- two assignments are incompatible only while both satisfy the conditions that make them work-admitting; and
- a model-use structure,
KindSignature, reference scheme, or bridge changes the meaning of one predicate clause and must therefore be included in that predicate’s semantic basis.
Primary EntityOfConcern. The EntityOfConcern is one obtaining SystemRoleAssignmentStateRelation, a direct relation kind admitted under U.Relation. Its two participants are one exact obtaining U.SystemRoleAssignment occurrence and one by-value SystemRoleAssignmentStatePredicate. The relation’s maximal continuous temporal extent comes from uninterrupted predicate truth while that assignment obtains.
Primary working reader. The first reader is an engineer, operator, method designer, safety checker, or manager deciding whether a current assignment can support the next method or Work claim without confusing assignment, capability, state, evidence, gate outcome, and performed Work.
What goes wrong if missed. A system-role label is treated as current readiness. A dashboard value is substituted for the world-side state relation. Missing evidence is read as proof that the predicate is false. Capability is mistaken for Work admission. A state-machine diagram is used as both the ontology and the method order.
What this buys. The reader can identify repeated state episodes inside one continuing assignment, keep evidence and world-side obtaining distinct, combine simultaneous conditions, and pass the exact state claim to the direct pattern governing the next decision or Work use.
Not this pattern when. Use A.2 and C.3 for the exact local system-role kind, A.2.1 for the assignment and its holder, A.2.2 for capability and operating envelope, A.2.7 for relations among system-role kinds, and A.15.1 for Work that actually occurred. Use A.2.4 or A.10 when the current object is the evidence-use relation rather than the assignment-state relation. A displayed status, credential entry, gate decision, or organizational position keeps its own direct pattern.