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:5219

Content

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

Conformant modeling sketch:

  • U.SpeechAct SA-Approve-4711

    • actTypes = {SpeechActTypeRef(Approval@ChangeControl)}
    • performedBy = RoleAssignmentRef(CAB_Chair as ApproverRole@ChangeControl)
    • isExecutionOf = MethodDescriptionRef(ChangeApprovalProcedure_v3)
    • executedWithin = ChangeControlBoardSystem
    • window = [t,t]
    • affected = {ChangeRequestId(4711), WorkRef(Deploy-4711)}
    • utteranceRefs = {EpistemeRef(ChangeTicket#4711)}
    • carrierRefs = {CarrierRef(TicketSystemRecord#4711)}
    • institutes.commitments = {CommitmentIdRef(D-Deploy-Authorized)}
  • U.Commitment D-Deploy-Authorized

    • subject = RoleAssignmentRef(OpsBot#DeployerRole:CD_Pipeline_v7)
    • modality = MAY (permission to enact)
    • referents = {A-Gate-Deploy-4711}
    • source.speechActRef = SA-Approve-4711
  • Gate predicate A-Gate-Deploy-4711 may include: exists SpeechAct(type=Approval, affected includes ChangeRequestId(4711), performedBy role=ApproverRole, within 90d).

This preserves:

  • act vs text vs carrier,
  • explicit performer,
  • time window for freshness,
  • explicit provenance from commitment back to the instituting act.