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.