Skip to content

Product Fleet Operations — workflows

Target

This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.

W1 — A product is onboarded

The product owner's Workspace admin onboards a generated product under a managed edition; the subscription (BC-34) must cover it. The inventory resolves the current release from delivery, the instances from environments and observed state, registers the edition's objective floors with SloService, and starts probing health through the product gateway.

W2 — A release rolls out in waves

sequenceDiagram
    participant RS as ReleaseService
    participant RO as FleetRolloutService
    participant RC as RunControlService
    participant E as EnvironmentPromotionService
    participant S as SloService
    participant INV as FleetInventoryService
    RS-)RO: ReleaseReady (product P 2.4.0)
    RO->>RO: plan: wave 1 = 10 % (no ManagedPlus production unless opted in), wave 2 = 40 %, wave 3 = 50 %
    RO->>RC: approval (production class)
    RC-)RO: ApprovalDecided
    RO->>E: RequestPromotion × wave-1 instances
    E-)INV: PromotionCompleted × instances
    RO->>RO: bake 60 min watching guards
    RO-)INV: RolloutWaveCompleted
    Note over RO: waves 2 and 3 likewise
    RO-)INV: RolloutCompleted
Hold "Alt" / "Option" to enable pan & zoom

W3 — A template release triggers a re-scaffold

flowchart LR
    AR[AssetReleasePublished · template 3.2.0] --> RQ[ReScaffoldRequester]
    RQ --> RUN[Factory run: regenerate product with 3.2.0 · sandbox]
    RUN --> PR[propose-change-set → pull request → pipeline]
    PR --> REL[ReleaseReady · product 4.0.0 with evaluation evidence]
    REL --> RO[rollout planned as W2]
Hold "Alt" / "Option" to enable pan & zoom

W4 — A guard breaches during bake

SloBreached on a guard objective halts the rollout: the wave's promotions are rolled back through EnvironmentPromotionService, RolloutHalted opens a Sev2 incident linked to the rollout, the on-call is paged, affected customers are notified, and the Operator decides whether to resume (after a fix released as a new version) or roll back fully.

W5 — An incident runs to review

stateDiagram-v2
    [*] --> Open
    Open --> Acknowledged: responder acknowledges within the edition's target
    Acknowledged --> Mitigated: mitigation applied through a rollout or promotion
    Mitigated --> Resolved: objectives recovered
    Resolved --> Reviewed: post-incident review recorded (Sev1, Sev2)
    Reviewed --> [*]
Hold "Alt" / "Option" to enable pan & zoom

W6 — A customer tenant is off-boarded

sequenceDiagram
    participant WA as Product owner (Workspace admin)
    participant INC as FleetIncidentService
    participant RC as RunControlService
    participant DE as RetentionResidencyService
    participant C as Customer
    WA->>INC: RequestOffboarding (product P, customer tenant T)
    INC->>RC: approval
    RC-)INC: ApprovalDecided
    INC->>DE: export order (scope: T in P)
    DE-)INC: ExportCompleted (bundle)
    INC->>C: bundle delivered through a connector
    C->>INC: AcknowledgeHandover
    INC->>DE: deletion order (30-day window), instances Suspended
    DE-)INC: DeletionOrderCompleted
    INC-)WA: OffboardingCompleted (evidence)
Hold "Alt" / "Option" to enable pan & zoom