A.2.8.PER:4.4 - Declare the strong granted-permission relation
GrantedPermissionRelation@Context <: U.Relation
RelationSignature:
PermissionBeneficiarySlot:
SlotKind: PermissionBeneficiarySlot
ValueKind: U.Entity
refMode: PermissionBeneficiaryRef
PermittedActionSpecificationSlot:
SlotKind: PermittedActionSpecificationSlot
ValueKind: U.Episteme
refMode: U.EpistemeRef
semanticDirection: PermissionBeneficiarySlot -> PermittedActionSpecificationSlot
RelationOccurrenceGroundAndQualifiers:
institutingSpeechActRef: SpeechActRef
grantorSystemRoleAssignmentRef: U.RelationRef constrained to U.SystemRoleAssignment
grantValidityPolicyRef: U.EpistemeRef
scope: U.ClaimScope
validityWindow: QualificationWindowPolicy
revocationOrSupersessionRef?: SpeechActRef
The beneficiary and permitted-action specification are participants. The grantor system-role assignment, instituting act, policy, ClaimScope, validity window, and revocation are constructive grounds or qualifiers.
The relation begins only when an admitted holder U.System performs a U.SpeechAct under the exact grantorSystemRoleAssignmentRef, the act satisfies the current policy’s grant-validity predicate, and it institutes permission for the named participants. The assignment’s HolderSystemSlot resolves to that system: the system performs the act, while the assignment supplies only the holder and assigned-kind fact used by the policy. Any authority claim required by the policy obtains independently. The relation obtains while beneficiary applicability, policy continuation, scope, and window hold and no valid revocation or supersession ends it.
One occurrence is identified by the instituting speech-act occurrence, exact beneficiary ref and ref kind, action-specification edition, policy edition, ClaimScope, and effective interval. Beneficiary change, renewal, materially changed action specification, non-carried policy edition, or revocation ends or splits the occurrence. A policy edition preserves it only through an explicit satisfied carry-forward rule.