#A.2.9:5.2 — Show #1 (system archetype: change-control approval gates a deployment)

Preface node heading:a-2-9-5-2-show-1-system-archetype-change-control-approval-gates-a-deployment:7576

#What this page is

This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

#Methodology

Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

#Content

Situation (messy prose): “Change is approved, so the pipeline may deploy.”

Conformant modeling sketch. The first line names the actual communicative Work. The record then states claims about that occurrence. Check separately that the assignment and enacted-Method relations obtain, that the act satisfies the recognition classification, that the policy is current and applicable, and that the grant obtains. Because the deployment gate relies on exact assignment-bound attribution, this attribution-bearing record must include performedUnderAssignmentRef and its F.6 relation must obtain for the already admitted act through the same A.13 assignment.

• Actual occurrence: SA-Approve-4711 : U.SpeechAct.
• Performer and assignment: ApproverSystemRole is an exact local agential system-role kind whose criterion for this use is the capacity to issue the policy-recognized approval act under the board procedure; CAB_Chair_A is classified under it for this scope and window, and evidence supports that core classification without a Grade or autonomy-profile claim. ChangeControlApproverAssignment is a declared U.SystemRoleAssignment species. Under A.2.1 it declares the ordered holder and assigned-kind positions, their domains U.System and ChangeControlApproverSystemRoleKindDomain, its direct predicate and applicability, and its occurrence-identity rule. Occurrence CAB_Chair_A_ApproverAssignment_2026 obtains with admitted System CAB_Chair_A as holder, ApproverSystemRole as assigned-kind value, and an extent covering the act; it is the same assignment used by A.13 and F.6. CAB_Chair_A performs SA-Approve-4711 under that assignment. Taxonomy ChangeControlSystemRoles_v3 and ChangeControlReferenceScheme_2026 interpret the assertion rather than becoming assignment participants. The assignment grounds attribution. Apply the current approval policy's authority conditions to CAB_Chair_A.
• Actual Method and containing-system relations: enactsMethod(SA-Approve-4711, ChangeApprovalMethod_v3) independently obtains, with ChangeApprovalMethod_v3 : U.Method. ChangeControlWorkBoundaryRelations declares ApprovalWorkOccursWithinBoardBoundary(work, system) for the board-system delimitation and act window; occurrence ApprovalWorkWithinBoardBoundary-4711 obtains for SA-Approve-4711 and ChangeControlBoardSystem.
• SA-Approve-4711-Record : SpeechActRecord states:
  • speechActOccurrenceRef = SpeechActRef(SA-Approve-4711);
  • actualPerformerSystemRef = U.EntityRef(CAB_Chair_A);
  • performedUnderAssignmentRef = U.RelationRef(PerformedUnderApprovalAssignment-4711), resolving to the F.6 relation between SA-Approve-4711 and CAB_Chair_A_ApproverAssignment_2026;
  • enactsMethodRef = U.EntityRef(ChangeApprovalMethod_v3);
  • methodDescriptionRef = EpistemeRef(ChangeApprovalProcedure_v3), a separate C.2.1 episteme used here to identify and constrain the Method;
  • recognitionTaxonomyRef = EpistemeRef(ChangeControlSpeechActTaxonomy_v3);
  • effectiveReferenceScheme = ChangeControlReferenceScheme_2026;
  • policyOrProcedureRef = EpistemeRef(ChangeControlApprovalPolicy_v3), current for this approval and grant use;
  • channelRef = U.EntityRef(CAB_TicketChannel);
  • actTypes = {SpeechActTypeRef(Approval)} under that taxonomy and scheme;
  • reliancePosture = relianceReady, workContainmentRelationRefs = {U.RelationRef(ApprovalWorkWithinBoardBoundary-4711)}, and window = [2026-06-12T10:03Z, 2026-06-12T10:04Z];
  • utteranceSubjectRefs = {ChangeRequestId(4711)};
  • institutionalTargetRefs = {GrantedPermissionRelationRef@Context(PER-Deploy-4711)};
  • utteranceDescriptionLocators = {U.EpistemeRef(ChangeTicket#4711)} and carrierRefs = {CarrierRef(TicketSystemRecord#4711)};
  • institutes.permissions = {GrantedPermissionRelationRef@Context(PER-Deploy-4711)}.

PER-Deploy-4711 : GrantedPermissionRelation@Context obtains separately under A.2.8.PER:

• beneficiarySystemRoleAssignmentRef = U.RelationRef(OpsBotDeployerAssignment-CD_Pipeline_v7), resolving to the assignment occurrence and its declared U.SystemRoleAssignment species;
• permittedActionSpecificationRef = EpistemeRef(DeployChange4711WorkSpecification);
• institutingSpeechActRef = SA-Approve-4711;
• grantorSystemRoleAssignmentRef = U.RelationRef(CAB_Chair_A_ApproverAssignment_2026);
• grantValidityPolicyRef = EpistemeRef(ChangeControlGrantPolicy_v3) under ChangeControlReferenceScheme_2026; the separately cited ChangeControlApprovalPolicy_v3 supplies the act-to-grant instituting rule;
• scope, revocation stance, and validity interval [2026-06-12T10:04Z, 2026-06-19T10:04Z] are explicit.

The one-minute speech-act interval and seven-day grant interval are different facts even though the latter begins when the former ends.

The utterance is about ChangeRequestId(4711); its policy-selected target and demonstrated effect are the separately obtaining grant. Nothing here claims that the change-request entity itself changed. Gate predicate A-Gate-Deploy-4711 may check exists SpeechAct(type=Approval, utteranceSubjectRefs includes ChangeRequestId(4711), actualPerformerSystemRef=CAB_Chair_A, performedUnderAssignmentRef=PerformedUnderApprovalAssignment-4711, within 90d), consume the current grant, and apply other prerequisites; passing the gate neither institutes nor equals the grant. No F.9 Bridge is needed merely because a pipeline consumes the result: this case uses one exact taxonomy, scheme, and policy. A Bridge becomes current only if another receiving use actually translates or compares a different local meaning.

Near misses. A ticket row alone is a carrier-backed claim, not the act. ChangeApprovalProcedure_v3 is a MethodDescription, not what the act enacts. A current approver assignment does not prove that approval Work occurred. Without the exact current policies, the occurrence remains communicative Work but establishes no grant.

This case retains kind versus occurrence versus record, utterance versus carrier, explicit performer and grant beneficiary, exact act and grant intervals, current policy bases, provenance from grant to instituting act, and strong permission versus admissibility gate as independently judgeable distinctions.

---

Last Updated: 2026-09-03 — upstream FPF commit b999972c (github.com/ailev/FPF)