CentralCloud Docs

Human map for CentralCloud products, ownership, and runtime boundaries.

This site is a docs and catalog portal. It reads from repo docs and CentralCloud source-of-truth systems; it does not own customer, billing, incident, monitoring, or runtime state.

CentralCloud repo Infra repo Response Monitoring

Sections

Core

Orgs, customers, users, memberships, API keys, global billing ledger, subscriptions, entitlements, quotas, audit, customer portal, and support links.

Does not own product runtime behavior.

Response

Incidents, responder schedules, escalation policies, paging, acknowledgements, status pages, stakeholder comms, postmortems, maintenance windows, and AlertLedger.

Does not own global customer identity, invoices, or monitor execution.

Monitoring

Monitor inventory, probe fleet, check schedules, result history, uptime evidence, dashboards, domain/DNS monitoring, and alert source evidence.

Does not own incident command, responder policy, or customer comms approval.

AI Workflows

Durable workflow records, routing, approvals, tool grants, handoffs, and agent action records across CentralCloud services.

Coordinates Holmes and specialists; does not replace them.

HolmesGPT

Read-only diagnosis, hypothesis and falsifier tracking, blast-radius analysis, RCA packets, and proposal packets.

No mutation, incident ownership, product ownership, or approvals.

Product Data Planes

VectorDrive, Inference Fabric, AI Gateway/Hosted MCP, Singularity Forge, FlakeCache, compute capacity, managed databases, Continuity, and Security Ops.

CentralCloud owns subscription truth; data planes own behavior.

Specialist Agents

Kubernetes/platform, security, communications, and agent-fleet specialist work at real team boundaries.

They receive scoped work from workflows; they are not the central source of truth.

Singularity Engine

Workflow execution, agent runtime, MCP federation, approval gates, run ledgers, and deployment/runtime coordination.

Not customer, subscription, billing, or product-contract truth.

Operating Rules

Core owns business truth. Product domains own product behavior. Runtime systems run things. Holmes diagnoses. Response reacts. Monitoring watches.

Billing split: Core owns the canonical subscription ledger. Product billing views derive limits and provisioning defaults from Core entitlements.

Portal rule: docs.centralcloud.com is a human portal. It links, renders, and explains. It must not become an authority for incidents, subscriptions, monitoring results, approvals, secrets, or runtime policy.

Boundary Matrix

Question	Owner	Reason
Who is the customer?	CentralCloud Core	Customers, orgs, memberships, and service entitlement span all products.
Is this org entitled to Response?	Core Billing	Response billing views derive limits; Core owns the subscription ledger.
Did a check fail?	Monitoring	Monitoring owns probes, schedules, results, and source evidence.
Is this an incident?	Response	Response owns dedupe, escalation, timeline, status, comms, and postmortem.
What happened and why?	HolmesGPT	Holmes owns read-only RCA and proposal packets.
Who executes approved platform work?	Specialist agents, GitOps, operators	Execution belongs to domain owners and deterministic controllers.