A.2.5:6 - Worked Slices

A.2.5:6.1 - Robot Inspection After Recalibration

Robot-7 already holds this A.2.1 assignment:

Robot7InspectionShiftAssignment-17 : InspectionShiftAssignment
InspectionShiftAssignment <: U.SystemRoleAssignment
  HolderSystemSlot: Robot-7
  AssignedSystemRoleKindSlot: InspectorSystemRole
  assignmentInterval: [2026-08-10T09:00, 2026-08-10T17:00]

The bearing-inspection method description declares InspectionReady, whose clauses require current calibration, clock synchronization inside tolerance, operating-envelope fit, and no active quarantine relation throughout the inspection window.

SystemRoleAssignmentStateAssertion:
  directClaimFamilyRef: A.2.5 SystemRoleAssignmentStateRelation
  SystemRoleAssignmentSlot: U.RelationRef(Robot7InspectionShiftAssignment-17)
  StatePredicateSlot:
    systemRoleKindRef: U.KindRef(InspectorSystemRole)
    NormalizedTruthConditionClaimGraph:
      CalibrationCurrent(Robot-7)
      and ClockSynchronizationWithinTolerance(Robot-7)
      and InspectionOperatingEnvelopeFit(Robot-7)
      and no ActiveQuarantineRelation(Robot-7)
    TemporalReading: continuous truth over the declared inspection interval
    Applicability: bearing inspection Work under InspectionShiftAssignment
    SemanticBasisRefs: omitted; these clauses use the direct subject predicates without another meaning-bearing edition
  assertionPolarity: affirmative
  systemRoleAssignmentStateExtent: [2026-08-10T09:20, 2026-08-10T12:00]

A calibration report is a separate U.Episteme; an A.2.4 evidence-use relation can support reliance on this assertion. At noon calibration validity ends and the predicate becomes false, so the first state occurrence ends while the assignment continues. Recalibration at 12:30 can make the same predicate true again and begins a second occurrence under that assignment.

A.2.5:6.2 - Drive Motor in a Pump Assembly

Motor-M1 is the holder of an exact pump-maintenance assignment whose assigned local kind is DriveMotorSystemRole. The current Work claim needs DriveReady, whose predicate names the exact supply relation, torque capability-fit relation, thermal band, and installed-connection relation.

The pump assembly grounds those direct claims; it is not a mandatory context slot. No scheme or BoundedModelUseStructure is required because the direct predicate clauses determine the state. Torque capability can remain while a missing supply relation makes DriveReady false. An affirmative DriveReady assertion states the assignment’s condition; use A.15.1 for any claim that pumping Work occurred.

A.2.5:6.3 - Socially Constituted Credential State

A clinician holds one exact assignment whose local kind is ProcedureOperatorSystemRole. Predicate CredentialCurrentForProcedure-X depends on an accepted credential decision, its validity interval, and absence of a suspending decision.

The accepted decision relation helps constitute the predicate because the credential ontology says so. A certificate publication may evidence that decision but does not substitute for it. The state occurrence still has the assignment and predicate as participants; evidence and publication remain neighboring relations.

A.2.5:6.4 - Two Approval Predicates

ApprovalService-2 holds an exact assignment to ApproverSystemRole. FulfilmentApprovalReady concerns fulfilment-state change; PaymentApprovalReady concerns payment authorization. Their truth clauses and applicability differ, so they are different SystemRoleAssignmentStatePredicate values even if one interface displays both as Ready.

If an independently selected model-use structure changes the meaning of one predicate’s clauses, its exact edition belongs in that predicate’s semantic basis. If it only selects which already identified predicate a view presents, it remains a receiving-use qualification.

A.2.5:6.5 - Approved Standard or Evidence Dataset Is a Different Relation

Suppose a project says, “Standard S is approved.” The standard is an episteme, not a system under a work-facing assignment. Recover the direct status-use, decision, source-use, or publication-use relation.

Likewise, a dataset or report that “plays a role” remains an episteme used through direct evidence, source, measurement, freshness, provenance, or assurance relations. Apply A.2.5 only if an admitted system’s exact assignment is being tested by a SystemRoleAssignmentStatePredicate that depends on one of those relations.