A.2.8.PER:5 - Archetypal Grounding

Assignment, permission, access, and authority. AdminAssignment is a declared U.SystemRoleAssignment species. Occurrence AdminAssignment-4 has admitted System ServiceOperator-4 as holder and AdminSystemRole as assigned-kind value. That fact alone establishes no grant, access, or decision authority. A policy-valid speech act can separately institute one GrantedPermissionRelation@Context for AdminSystemRole, RestartServiceActionSpec, the declared scope, and the declared window. Matching dated Work exercises that grant only through a separate PermissionExerciseRelation@Context. If service access is claimed, cite its domain access predicate and participants; when no such predicate is available, return A.6.RCD missing-governor[direct service-access relation]. Permission, exercise, access, authority, assignment, and Work therefore remain separate.

Strong grant and exercise. PlantPermissionGrantorAssignment is a declared U.SystemRoleAssignment species. Occurrence MaintenanceCoordinator-A@DayShift has admitted System MaintenanceCoordinator-A as holder, and that System performs a policy-valid grant speech act under the assignment. The act institutes MaintenanceCalibrationGrant-2026-07-19 : GrantedPermissionRelation@Context for MaintenanceTechnicianSystemRole to run CalibrationProcedure-v3 during one service window. Its beneficiary uses beneficiarySystemRoleKindRef.

PlantCalibrationTechnicianAssignment is another declared species. Occurrence Tech-17@Shift-B has admitted technician System Tech-17 as holder and MaintenanceTechnicianSystemRole as assigned-kind value. Tech-17 performs dated CalibrationWork-17B under that assignment. The Work instantiates CalibrationProcedure-v3 within the grant’s zone, window, and scope, so the action-match predicate holds. The assignment covers the Work and satisfies the policy’s eligibility rule for that kind, so the beneficiary predicate holds.

CalibrationExercise-17B : PermissionExerciseRelation@Context therefore connects CalibrationWork-17B to MaintenanceCalibrationGrant-2026-07-19, cites beneficiarySystemRoleAssignmentRef=Tech-17@Shift-B, and states the Work interval and scope. The assignments supply holder and assigned-kind facts for the grant and Work attribution; any required authority relation obtains independently. The grant remains current for the rest of the window because the policy is not single-use. Claims about obligation, readiness, capability, gate passage, a safe result, or successful calibration need their own grounds.

Weak finding. A policy reviewer checks a named, current, sufficiently complete plant-access frame and finds no prohibition applicable to the exact system-role kind, action specification, zone, and window. The result is NonProhibitionFinding@Context(result=nonProhibited), not an instituted grant. If the emergency-policy register cannot be checked, the result is unresolved.

Actual-Work non-violation. After CalibrationWork-17B is performed, CalibrationComplianceEvaluation-17B : U.Work checks that Work against PlantCalibrationNormativeFrame-2026-07-19-e3, whose currentness and sufficient completeness for the technician, procedure, zone, and service-window use are named and whose applicable prohibitions are checked. The result is NonViolationFinding@Context(workRef=CalibrationWork-17B, performerSystemRoleAssignmentRefs={Tech-17@Shift-B}, normativeFrameRef=PlantCalibrationNormativeFrame-2026-07-19-e3, evaluationWorkRef=CalibrationComplianceEvaluation-17B, result=nonViolating). The covering assignment already relates the performer system to the beneficiary system-role kind. The separate exercise relation shows which grant the Work exercised; exercise alone does not establish non-violation, and non-exercise alone does not establish it either. If the frame is stale or insufficiently complete for this use, the non-violation result is unresolved.

Conflict and non-use. The system-role-kind-level calibration grant still obtains under §4.4 while ContaminatedZoneEntryProhibition-7 forbids the same beneficiary and calibration action in Zone 7 during an overlapping interval. In the direct-rule case, EmergencyCalibrationPrecedencePolicy-e5 contains applicable claim CZ7-Prohibition-Overrides-CalGrant. The rule’s conditions match, so the finding is settledByApplicableRule, cites that rule, and returns “do not enter Zone 7” for the blocked Work.

In a discretionary Zone 8 case, PlantSafetyDecisionAssignment is a declared U.SystemRoleAssignment species. Occurrence SafetyDirector-3@EmergencyShift has admitted System SafetyDirector-3 as holder, and that System performs CalibrationConflictDecisionWork-8 under the assignment. The separately obtaining PlantEmergencyExceptionAuthority-8 relation authorizes that decision, and current CalibrationConflictResolutionResult-8 selects the prohibition claim for the stated scope and window. Only then is the finding settledByDecisionResult.

A second Zone 8 request that merely names the Safety Director but has no dated decision Work or current result remains unresolved. A visible permit and green readiness tile cannot repair either gap. If no calibration Work occurs, the permission is neither exercised nor violated.