Skip to content

Cloud and reliability operations

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
Vertical Cloud & Reliability
Prototype reference Cloud & Reliability prototype (ConnectSoft.DesignPrototypes)
Managed edition Managed (D33, D34)
Data residency tenant-region (D31)
Catalog Examples catalog · Vision-to-Production path for this vertical

Business problem

Teams lack a single view of environments, objectives, incidents and cost across their products.

Product intent

An internal reliability product: environment inventory, objectives, incidents, cost views — the Factory's Runtime Cloud, Observability and Fleet patterns as a customer product.

What the Factory makes different here: reuses the Factory's inventory, SLO, alert and incident models.

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane Infrastructure Architect Agent, Observability Engineer Agent vision
Architecture and domain Template & Library (BC-02) Enterprise Architect Agent service, module
Experience Template & Library, Factory Studio UX track UX Designer Agent, Frontend Developer Agent —
Recipe and generation Template & Library (BC-15), Agent Mesh, Tools & MCP Infrastructure Architect Agent, Observability Engineer Agent, Backend Developer Agent, QA Agent module plan from the context map
Quality Observability (BC-22), DevOps / GitOps QA Agent observability, test
Delivery and provisioning DevOps / GitOps (BC-23, BC-24), Runtime Cloud (BC-25) DevOps Agent, Infrastructure Architect Agent infrastructure
Operations Product Fleet Operations (BC-35..37) — handover, objectives, rollouts, incidents, off-boarding

Delivery workflows exercised: deployment-and-observability-workflows, platform-cost-optimization-workflows.

Generated product shape

C4Context
    title Cloud and reliability operations system context
    Person(user, "Users", "Cloud & Reliability users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Cloud and reliability operations") {
        System(ctx_Inventory, "Inventory", "environments, workloads, drift")
        System(ctx_Objectives, "Objectives", "SLOs, budgets")
        System(ctx_Incidents, "Incidents", "incidents, on-call, reviews")
        System(ctx_Cost, "Cost", "attribution, budgets")
    }
    Rel(user, ctx_Inventory, "uses through the product gateway GW-07")
    Rel(factory, ctx_Inventory, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Inventory environments, workloads, drift DriftDetected
Objectives SLOs, budgets SloBreached
Incidents incidents, on-call, reviews IncidentResolved
Cost attribution, budgets BudgetExceeded

Modules and templates

Module Template Notes
Microservice ×4 connectsoft-microservice
Health aggregator connectsoft-healthchecks-aggregator
Ops shell connectsoft-blazor-shell
Every product also gets the SaaS foundations (tenants, editions, entitlements, billing, metering) and the product host shape (descriptor, health, operations handover) unless it is a library-only product.

Prototype reference

Cloud & Reliability prototype in ConnectSoft.DesignPrototypes shows the intended screens; the UX track (U1–U4) maps prototype destinations to the UX model's screens with keep, merge, rename, retire or new decisions.

Operations as a managed product

Managed.