A.2.5:4 - Solution

Start from a readable assertion:

Robot-7’s current assignment to InspectorSystemRole satisfies InspectionReady throughout the inspection window.

When a receiving use needs reusable participant typing, use the declared RelationSignature. When it needs occurrence identity, apply the world-side identity rule in section 4.3.

A.2.5:4.1 - Direct Relation Declaration

This pattern defines the RelationSignature for SystemRoleAssignmentStateRelation:

These are the only two generic participants. SystemRoleAssignmentStateRelation obtains exactly while the assignment obtains and the fixed by-value predicate is true under its temporal reading. Its actual extent is the maximal continuous interval of that obtaining. An affirmative assertion or occurrence description may state the known extent as systemRoleAssignmentStateExtent only for an independently established occurrence; a receiving evaluation may state a separate declaredSystemRoleAssignmentStateEvaluationWindow. Neither temporal value, assertion polarity, reliance posture, taxonomy episteme, reference scheme, bridge, nor model-use structure is another relation participant.

A relied-on assertion uses a direct evidence-use relation. Another world-side occurrence affects predicate truth only when an exact truth-condition clause cites that occurrence through its subject pattern.

A.2.5:4.2 - Predicate Meaning and Semantic Basis

One SystemRoleAssignmentStatePredicate value names:

• the exact local system-role kind for whose assignment species the predicate is defined;
• normalized truth-condition ClaimGraph clauses, each naming its governed quality or relation, actual participants, and subject pattern;
• the temporal reading, such as truth at an instant, throughout a receiving-use window, or for a declared tolerated portion of that window;
• applicability conditions; and
• only the semantic-basis references whose editions can change those clauses or their interpretation.

This content defines one predicate value. The direct qualities and relations keep their own kinds and subject patterns.

Predicates need not be mutually exclusive. Calibrated, Synchronized, and InRange can hold simultaneously; InspectionReady may be a conjunction over them. Use an exclusive state configuration only when the subject-domain model actually needs one.

A shared label does not establish shared meaning. Cross-context reuse needs the same predicate identity or an explicit comparison or bridge stating which truth and admission effects are preserved. A bridge or scheme enters the predicate’s semantic basis only when the predicate clauses really depend on it.

A.2.5:4.3 - Occurrence Identity and Repeated Episodes

Do not replace the identity rule with a tuple key. One SystemRoleAssignmentStateRelation occurrence begins when one fixed assignment starts satisfying one fixed predicate. It continues while the assignment obtains and the predicate remains true without interruption. It ends when the assignment ceases, the predicate becomes false, or either participant changes. A later return to truth starts another occurrence.

An affirmative assertion or occurrence description may state the currently known systemRoleAssignmentStateExtent. Recording an end boundary for a previously open extent refines the description of the same occurrence when assignment obtaining and predicate truth were uninterrupted. A demonstrated predicate gap separates occurrences. Thus true → false → true produces two state occurrences inside one continuing assignment.

A later correction of an assertion interval, changed evidence relation, assertion edition, dashboard display, or publication creates no world-side occurrence while truth was uninterrupted. An evidence gap gives the receiving use unresolved reliance; it does not demonstrate a gap in predicate truth or add a third assertion polarity.

A.2.5:4.4 - Assertion and Evidence Use

For a relied-on state claim, keep this order:

1. name the exact U.SystemRoleAssignment, by-value SystemRoleAssignmentStatePredicate, direct claim family, and affirmative or negative assertion polarity;
2. when A.2.5 independently establishes obtaining and the receiving use needs occurrence identity, individuate the occurrence under section 4.3;
3. state a SystemRoleAssignmentStateAssertion : U.Episteme whose ClaimGraph carries the predicate, direct claim-family reference, polarity, known systemRoleAssignmentStateExtent only for an affirmative claim about an established occurrence, and any separate declaredSystemRoleAssignmentStateEvaluationWindow;
4. include a meaning-bearing semantic-basis reference in the predicate identity, while a non-meaning-changing receiving-use selection stays with that use;
5. use A.2.4 for compact evidence use and A.10 only when fuller evidence-basis detail changes the relied-on use; and
6. let the direct consumer apply the supported assertion under its own subject pattern.

When evaluation itself is current, recover the exact actual evaluator System through A.13 and let A.15.1 independently admit exact dated evaluation W_eval : U.Work. Add F.6 performedUnderAssignment(W_eval, RA_eval) through the same obtaining A.13 assignment only when this account or its receiving use expressly consumes precise assignment-bound attribution; F.6 identifies neither assignment nor performer, and missing or failed F.6 leaves the evaluation Work intact. A separately constituted evaluation result is a C.2.1 episteme whose ClaimGraph states the judgment about the assignment or established occurrence. The evaluation and receiving use add no participants to the state relation: its participants remain the tested assignment and its predicate, and occurrence identity still follows §4.3.

The actual state extent, target evaluation window, and evidence-relevance interval answer different questions. Expired evidence lowers reliance without retroactively rewriting an earlier world-side occurrence.

A.2.5:4.5 - Work-Admission Use

A.2.5 supplies the state relation and exact assertion form. Use the direct subject patterns when Method selection, a gate decision, authority, or a claim that Work occurred is needed.

For a consequence-bearing admission use, the system performing the consumer’s evaluation or decision Work applies that consumer’s direct pattern and checks:

1. the exact U.SystemRoleAssignment obtains throughout the receiving decision or Work window;
2. the consumer selects one exact SystemRoleAssignmentStatePredicate, whose truth condition may be an explicit conjunction;
3. each relevant assignment has an obtaining SystemRoleAssignmentStateRelation whose actual extent covers the receiving-use window;
4. the assertion has the evidence relation and currentness that this consumer requires; and
5. every other admission condition is separately established under its subject pattern.

The consumer’s direct pattern defines any admit, deny, defer, or unresolved outcome. A.2.5 contributes only the exact state relation on which that decision Work may rely.

A.2.5:4.6 - System-Role-Kind Relation Use

When substitution, incompatibility, bundle, or residual qualification among exact local system-role kinds is selected with A.2.7, test state sensitivity through exact assignments, state predicates, and windows.

• Substitution supports one admission condition only when the candidate assignment’s current predicate satisfies the selected receiving rule.
• Incompatibility is stated for the exact same-holder or different-holder rule, Work identity condition, overlapping windows, and predicate conditions under which the conflict appears.
• A Work claim needing several system-role kinds uses the independently obtaining assignments and state occurrences needed by that claim. It does not require a Cartesian product of every possible state label.

A conjunction for one Work claim creates no composite system-role kind, assignment, or state predicate by form.

A.2.5:4.7 - State-Machine and Change Lenses

Use statecharts or state machines when mutually exclusive configurations, orthogonal regions, guarded changes, or event handling improve the subject-domain model. The notation describes possible configurations and changes; it does not replace the direct relation occurrence.

A change arrow represents a proposed or observed change in predicate truth; it is not the world-side change by form. Recover the exact changed object or relation, then use the direct pattern governing that change. Use the Method description for any prescribed Method order.

When the model needs continuous coordinates rather than discrete labels, use A.19 for the characteristic space and let the by-value state predicate select a region, band, ordering condition, or other exact condition. Measurement and evaluation stay with C.16 and their direct patterns.

A.2.5:4.8 - Semantic Basis and Receiving-Use Qualification

Most state claims need no bridge, reference scheme, or bounded-model-use structure. Directly governed truth-condition clauses are enough.

When a KindSignature, reference scheme, bridge, or BoundedModelUseStructure changes the meaning of a predicate clause, include its exact edition in SystemRoleAssignmentStatePredicate semantic basis and therefore in predicate identity. When it changes only how a separate receiving assertion, comparison, or Work use presents or consumes an unchanged predicate, cite it in that receiving use instead. The generic relation signature remains the two-participant declaration in §4.1.