Skip to content
  • fleet-operations
  • platform
  • overview doc_status: target plane: execution platform: fleet-operations

Product Fleet Operations — overview

Target

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

Designed 2026-10-09 (design plan P12)

The platform was added on 2026-10-09 (decisions D22 and D33). This page replaces the placeholder overview.

The Factory does not stop when a product is generated and deployed. Under decision D33 ConnectSoft operates generated products as a managed service, and this platform is how: it knows every operated product and instance, moves them to new releases and template versions in guarded waves, runs the incident desk with on-call and customer communication, and off-boards customers and products with their data handed over and then deleted with evidence.
Platform PF-10 Product Fleet Operations (Execution)
Bounded contexts BC-35, BC-36, BC-37
Services 4 (1 hosts, 3 modules, 0 external, 0 later) — 4 modelled
Gateways —
Status target

Purpose

  • Inventory from evidence. Instances, releases and health derive from delivery, runtime and observability events and the product's own health endpoint through its gateway (GW-07); nothing is declared by hand.
  • Editions set the commitment. Self-operated, Managed and ManagedPlus (D34) set objective floors, on-call coverage and response targets; a customer may buy stricter, never weaker.
  • Rollouts are scheduled promotions with guards. Every wave goes through the same promotion gates (BC-24); bake time against product objectives; halt, roll back and open an incident on breach; production waves need a production-class approval.
  • Re-scaffolds are Factory runs. A template release triggers a regeneration run whose release passes evaluation (ADR-0021) before any instance moves.
  • Incidents never change products. Mitigation is a rollout or a promotion; incidents hold the timeline, links, paging, customer notifications and the review.
  • Off-boarding is a governed order. Approval, export in open formats, handover acknowledged, then deletion within the retention window, all with evidence (D31).

Bounded contexts and services

Context Owns Services (granularity)
BC-35 Fleet Inventory & SLOs Operated products, instances, editions, objectives, health FleetInventoryService (module)
BC-36 Fleet Upgrades & Rollouts Rollouts, waves, guards, re-scaffold requests FleetRolloutService (module)
BC-37 Fleet Incidents & Off-boarding Incidents, on-call, customer notifications, off-boardings FleetIncidentService (module)
Host Composition FleetOperationsHost (standalone)
Service Context Granularity Status
FleetIncidentService BC-37 module of host target
FleetInventoryService BC-35 module of host target
FleetOperationsHost BC-35 standalone host target
FleetRolloutService BC-36 module of host target

Context

flowchart LR
    subgraph P["Product Fleet Operations"]
        FleetOperationsHost["FleetOperationsHost"]
    end
    P --> ConnectorRegistryService["ConnectorRegistryService"]
    P --> RunControlService["RunControlService"]
    P --> RetentionResidencyService["RetentionResidencyService"]
    P --> ArtifactService["ArtifactService"]
    P --> ReleaseService["ReleaseService"]
    P --> RuntimeEnvironmentService["RuntimeEnvironmentService"]
    P --> SloService["SloService"]
    P --> FactoryCommercialService["FactoryCommercialService"]
    P --> ext_generated_products["ext-generated-products"]
    P --> DeliveryHost["DeliveryHost"]
    P --> RuntimeCloudHost["RuntimeCloudHost"]
    P --> ObservabilityHost["ObservabilityHost"]
    P --> ControlPlaneApi["ControlPlaneApi"]
    P --> DataEventFoundations["DataEventFoundations"]
    P --> IntegrationHost["IntegrationHost"]
    P --> ext_identity_platform["ext-identity-platform"]
    P --> EnvironmentPromotionService["EnvironmentPromotionService"]
Hold "Alt" / "Option" to enable pan & zoom

Containers

See microservices for the container view of hosts and modules.

Built on

Unit Owner Used here as
Product release DevOps / GitOps (BC-24) what instances run; what rollouts move
Promotion DevOps / GitOps (BC-24) one instance's move in a wave
Environment and observed state Control, Runtime Cloud (BC-25) where an instance lives and whether it is healthy
Objective Observability (BC-21) product objectives, rollout guards, degraded marking
Alert Observability (BC-21) incident triggers
Connector Integration (BC-17) paging and customer notifications
Governance order Data & Event (BC-42) export and deletion in off-boarding
Subscription and edition Control (BC-34) the managed commitment
Template release Control (BC-04) re-scaffold trigger