Skip to content

Runtime Cloud — overview

Target

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

Rewritten 2026-10-09 (design plan P11)

This page replaces the June-2026 overview with its seven runtime services and the separate GitOps service of the DevOps platform. The 2026 design has one provisioning owner (BC-25), one inventory, and one capacity service (BC-26). The old page is archived under catalogs 2026-06.

The Runtime Cloud platform is where the Factory touches infrastructure, and it touches it in exactly one way: a recorded provisioning run of a declared specification. Everything else it does is observe, compare, propose and lease.
Platform PF-09 Runtime Cloud (Execution)
Bounded contexts BC-25, BC-26
Services 12 (1 hosts, 10 modules, 1 external, 0 later) — 4 modelled
Gateways —
Status target

Purpose

  • Desired state in Git, receipts in the Factory. Specifications reference the IaC program and its version (Pulumi, ADR-0004); every plan and apply leaves a receipt with inputs hash, program version, outputs and result.
  • Production applies are approved. A promotion's production-class approval covers its apply; baseline and reconciliation applies in production need their own (D21, ADR-0015).
  • Reconciliation proposes, people decide. GitOps re-plans on a schedule; non-destructive differences outside production may apply automatically; destructive or production differences become reviewable proposals.
  • Observed, never assumed. The inventory is read from clusters and cloud APIs; a stale environment is marked stale; drift is a finding resolved only by re-observation.
  • Capacity is governed. Pools with security boundaries and regions, quotas from the edition that may only tighten, leases that make placement explicit and show a requester why a run waits.

Bounded contexts and services

Context Owns Services (granularity)
BC-25 Provisioning & Reconciliation Deployment specifications, provisioning runs and receipts, reconciliation; runtime inventory, drift findings, reconciliation proposals IaCProvisioningService (module; deployment manifest, deployment and GitOps sync rows merged) · RuntimeEnvironmentService (module; drift detection and runtime service catalog rows merged); RuntimeConfigurationService external canonical (Config Platform)
BC-26 Execution Capacity Worker pools, quotas, capacity leases ExecutionCapacityService (module, added; agent pool manager and runtime scaling rows merged)
Host Composition, cloud identity RuntimeCloudHost (standalone)
Service Context Granularity Status
AgentPoolManager BC-26 module of host unmodelled
DeploymentManifestService BC-25 module of host unmodelled
DeploymentService BC-25 module of host unmodelled
GitOpsSyncService BC-25 module of host unmodelled
IaCProvisioningService BC-25 module of host target
RuntimeCloudHost BC-25 standalone host target
ExecutionCapacityService BC-26 module of host target
RuntimeConfigurationService BC-25 external / canonical unmodelled
RuntimeDriftDetectionService BC-25 module of host unmodelled
RuntimeEnvironmentService BC-25 module of host target
RuntimeScalingService BC-26 module of host unmodelled
ServiceCatalogRuntimeService BC-25 module of host unmodelled

Context

flowchart LR
    subgraph P["Runtime Cloud"]
        RuntimeCloudHost["RuntimeCloudHost"]
    end
    P --> ext_pulumi["ext-pulumi"]
    P --> SecretBrokerService["SecretBrokerService"]
    P --> ext_config_platform["ext-config-platform"]
    P --> PolicyEngineService["PolicyEngineService"]
    P --> RunControlService["RunControlService"]
    P --> ArtifactService["ArtifactService"]
    P --> DeliveryHost["DeliveryHost"]
    P --> ControlPlaneApi["ControlPlaneApi"]
    P --> GovernanceHost["GovernanceHost"]
    P --> KnowledgeHost["KnowledgeHost"]
    P --> ext_identity_platform["ext-identity-platform"]
    P --> FactoryCommercialService["FactoryCommercialService"]
    P --> RetentionResidencyService["RetentionResidencyService"]
Hold "Alt" / "Option" to enable pan & zoom

Containers

See microservices for the container view of hosts and modules.

Boundaries with neighbours

Neighbour They own This platform owns
DevOps / GitOps (BC-24) the decision to promote, gates, approval, verification the apply and its receipt
Control plane (EnvironmentService) the environment as a scope (class, state, project) what is provisioned and observed in it
Config Platform (canonical) configuration values and flags references to them in specifications and inventory
Secret Broker (BC-40) secret values and issuance references resolved at apply time
Model & Compute (BC-41) model-serving compute pools execution pools for agents, sandboxes, builds, browsers
Product Fleet Operations (P12) operating generated products across environments per-environment inventory and provisioning they build on