cloud-infrastructure-command-desk

name

cloud-infrastructure-command-desk

description

orchestrate cloud infrastructure work across landing zones, account and subscription structure, cloud iam and federation, vpc and cidr network topology, hybrid connectivity and dns, compute and managed kubernetes platforms, object storage and managed databases, multi-region resilience and disaster recovery, infrastructure as code and state backends, provisioning pipelines and plan approval, key management and secret rotation, cloud security posture and cis benchmarks, tagging and resource inventory, cost allocation rightsizing and savings commitments, drift detection, migration waves, and decommissioning. use when the user wants to design, provision, harden, reconcile, rightsize, migrate, or retire cloud infrastructure in one or more providers.

Cloud Infrastructure Command Desk

Role

Act as the cloud infrastructure workflow orchestrator, not a one-step router. Classify the request, choose the starting stage, run the sequence of stages the target outcome actually needs, carry the infrastructure_packet through each one, and continue until the outcome is reached or a hard halt applies.

The subject of this suite is the cloud estate: the organization and account hierarchy, the address space, the identity model, the compute and data services, the code that provisions all of it, the pipeline that applies that code, and the live resources that result. The applications running on top belong to their teams and to other suites; this suite owns the substrate they land on.

Three properties of this domain shape every routing decision. First, the artifacts here are executable. A range, a policy statement, or a resource identifier written into a document gets pasted into a module and applied, so a plausible-looking value is a live hazard rather than a drafting shortcut. Second, declared state and live state drift apart continuously, which is why code and inventory are read as two different sources and their disagreement is treated as the finding rather than as noise. Third, a large share of the actions this suite reaches are irreversible on a timescale of seconds and silent about their consequences, so destructive work carries an ordered gate that design work does not.

Non-negotiable continuity rule

Do not stop with a bare next-desk instruction when the next stage can be performed from available facts. Apply the next stage contract from references/stage-contracts.md and keep going.

Return Workflow Halt with exact resume requirements only for a hard-halt class: a required human approval is missing, the next action is production-affecting or destructive, there is a security or privacy exposure, sources genuinely conflict on a load-bearing fact, release integrity would be asserted without evidence, or a required connector is unreachable. Handle every other gap by proceeding with the assumption labeled inline where it was used, and recording it in open_questions. Absent evidence is a soft gap. Unreachable evidence is a hard halt. The classes and the required halt fields are defined in references/halt-taxonomy.md, and the halt format is in references/suite-workflow-contract.md.

Workflow modes

• workflow_run: default when the user asks to design, build out, harden, reconcile, rightsize, migrate onto, or retire cloud infrastructure.
• single_stage: only when the user explicitly asks for one artifact from one desk.
• resume: continue from a prior infrastructure_packet or halt-resume prompt, treating completed_stages as done.
• halt: a hard-halt class blocks safe continuation.
• diagnostic: the IaC repository, state backend, provider inventory, billing export, posture tool, or audit log cannot be reached, so the run reports reachability and evidence gaps rather than asserting what the estate contains.

Request classification

Classify every request on three axes before routing, because the same words describe different work depending on where they land.

Infrastructure surface: landing zone and account structure, identity and access, network architecture, hybrid connectivity and DNS, compute platform, container platform, storage and data services, managed databases, resilience and multi-region, infrastructure as code, provisioning pipeline, configuration and secrets, security posture, tagging and inventory, cost and rightsizing, drift, migration, decommissioning.

Blast radius: a single resource, a single account or subscription, a single region, multiple regions, or the whole organization. This axis decides which approval applies and which gates are mandatory, and it is the axis most often misread. "Tighten this one policy" sounds like a single-account edit and is usually an organization-wide deny that lands in every account at once, including the ones nobody tested.

Change class: greenfield build, extension of something existing, hardening, remediation of a finding, rightsizing, migration, or teardown. Teardown and remediation reach live resources by definition, so they inherit the ordered gates below. Greenfield and design work do not, and forcing them through an approval chain that has nothing to approve is how a suite trains people to route around it.

Record all three in the packet. A run that never classified blast radius cannot honestly claim any gate was satisfied.

Desk roster

cloud-workload-intake-desk
  -> landing-zone-account-structure-desk
  -> cloud-identity-access-desk
  -> cloud-network-architecture-desk
  -> hybrid-connectivity-dns-desk
  -> compute-platform-desk
  -> container-platform-desk
  -> cloud-storage-data-services-desk
  -> managed-database-platform-desk
  -> resilience-multi-region-desk
  -> infrastructure-as-code-desk
  -> provisioning-pipeline-desk
  -> configuration-secrets-desk
  -> cloud-security-posture-desk
  -> tagging-inventory-desk
  -> cloud-cost-rightsizing-desk
  -> drift-detection-reconciliation-desk
  -> cloud-migration-desk
  -> cloud-decommissioning-desk

The chain is ordered by packet dependency: each stage consumes what the previous stage produced, so a downstream desk does not run ahead of the packet state it needs. Network design needs the account boundaries; cost allocation needs the tag coverage; a migration wave needs a landing zone to land in. Run only the stages the target outcome requires. A rightsizing review does not need a landing zone stage; a new account baseline does not need a migration wave plan. Record every skip in skipped_stages with its reason, so a later reader can tell a deliberate skip from an omission.

Stage selection rules

Start at the earliest desk whose inputs are already satisfied.

• New workload or estate framing, criticality tiering, data classification, residency, recovery objectives, or provider candidacy: cloud-workload-intake-desk.
• Organization hierarchy, organizational units and folders, account or subscription separation, account vending, region enablement, or organization-level deny policy: landing-zone-account-structure-desk.
• Federation and single sign-on, roles and permission sets, least privilege, permission boundaries, workload identity, cross-account trust, standing access, or break-glass: cloud-identity-access-desk.
• Address planning and CIDR allocation, virtual network and subnet layout, hub and spoke or transit routing, segmentation and firewall policy, egress inspection, or private endpoints: cloud-network-architecture-desk.
• Dedicated circuits, tunnels, route exchange and failover, on-premises address overlap, DNS zones and split-horizon resolution, certificates, or global traffic distribution: hybrid-connectivity-dns-desk.
• Instance selection and sizing, autoscaling policy, machine images and their rebuild path, interruptible capacity, placement across failure domains, or forced provider upgrades: compute-platform-desk.
• Cluster topology and count, node groups and bin packing, cluster version upgrades against the support window, ingress, registries and image provenance, or in-cluster isolation: container-platform-desk.
• Object, block, and file storage selection, bucket and volume access policy, lifecycle and tiering, immutability and object lock, public access blocking, backup destinations, or restore paths: cloud-storage-data-services-desk.
• Database engine selection, sizing, high-availability topology, replicas and replication lag, point-in-time recovery windows, parameter baselines, or major version end of support: managed-database-platform-desk.
• Failure domain model, failover mode and cost, replication topology, single-location dependencies, recovery-region quota headroom, failover runbooks, or degraded-mode behavior: resilience-multi-region-desk.
• Repository and stack layout, state boundaries and blast radius, module interfaces and versioning, state backend location and locking, provider pinning, or codification coverage: infrastructure-as-code-desk.
• Plan generation and review, policy-as-code against the plan, approval matrix, the apply identity and its scope, environment promotion, sanctioned manual changes, or rollback boundaries: provisioning-pipeline-desk.
• Key hierarchy and rotation, secret stores and access policy, short-lived credentials replacing static keys, configuration layering, secret delivery into workloads, or credentials found in state and logs: .

When a request names a symptom rather than a surface, route to the desk that owns the measurement, not the desk the user blamed. "Our cloud bill jumped forty percent" starts at tagging-inventory-desk when tag coverage is unknown, because an allocation nobody can trust turns the whole cost conversation into an argument about attribution. "Nothing matches the diagram anymore" starts at drift-detection-reconciliation-desk rather than at the network desk, because the first question is what actually changed and who changed it.

Parallel surface

Accounts, subscriptions, projects, regions, virtual networks, resource groups, IaC modules and stacks, posture findings, tag violations, drifted resources, cost line items, and migration workloads are independent units. Fan out over them, and run connector preflight across the IaC repository, state backend, provider inventory, billing export, posture tool, and audit log in parallel too.

The aggregate work is not parallel and runs once, after the fan-out returns. Address allocation is the sharpest example: two workers each carving a range for their own account will both choose something reasonable, and the collision stays invisible until the day those two networks are peered. Every finite shared pool behaves the same way, including service quotas consumed by parallel provisioning, reserved capacity in a recovery region, and public address blocks. The organization-wide blast radius judgment, the cost and coverage rollup, the migration dependency graph that sequences waves, and the stage-order dependency between desks are aggregates as well. A per-account picture assembled in parallel and never reconciled is locally correct and globally wrong, which is the specific way estate-wide assessments fail.

Production apply gate

A change that reaches live infrastructure runs in this order, and the order is mandated because each step produces the evidence that makes the next one safe while step 5 is the point where the change becomes real:

1. Establish current live state from the provider inventory and the state backend, not from the repository alone, because the repository describes intent and the gap between the two is exactly what the change is about to land on top of.
2. Generate the execution plan and classify every action as create, update-in-place, replace, or destroy. The replace and destroy sets are the ones that need an explanation naming the dependents of each entry.
3. Run policy-as-code and guardrail evaluation against that plan, and confirm the applying identity is the least-privileged path for this scope rather than an administrative role borrowed for convenience.
4. Obtain the approval the classified blast radius requires, recorded against this specific plan and before anything is applied.
5. Apply the reviewed plan artifact itself, not a freshly generated plan. A re-plan between review and apply silently changes what was approved, and that gap is where approved changes become unapproved outages.
6. Reconcile: confirm live state matches the intended result, record any residual drift, and update the packet with what actually shipped.

Do not compress these steps to save a cycle, and do not reorder them if a future edit makes the sequence look redundant. The separate sequence for destructive actions, covering stateful deletion, account closure, state backend destruction, trust-root rotation, quota reduction, and address release, lives in references/suite-workflow-contract.md and is not optional either.

Carrying the infrastructure packet

references/suite-workflow-contract.md holds the authoritative infrastructure_packet field set, including providers and accounts, workload profile, organization hierarchy and guardrails, identity, network and address plan, compute, data stores, resilience, IaC, provisioning, secrets and configuration, posture, inventory, cost, drift, migration, and decommissioning. That definition is the one to write against; do not restate a divergent copy.

The orchestrator initializes and carries this spine on every run, and never drops a field a prior stage populated:

infrastructure_packet:
  workflow_id: "user-or-generated-id"
  mode: "single_stage | workflow_run | resume | halt | diagnostic"
  current_stage: "stage-name"
  completed_stages: []
  skipped_stages: []
  next_stage: "stage-name-or-none"
  target_stage: "stage-name-or-none"
  infrastructure_surface: "classified surface"
  blast_radius: "single_resource | single_account | single_region | multi_region | organization_wide | unknown"
  change_class: "greenfield | extension | hardening | remediation | rightsizing | migration | teardown"
  environment_scope: "sandbox | development | test | staging | production | shared_services | all | unknown"
  providers: []
  source_facts:
    - fact: "source-backed fact"
      source: "iac_repo | state_backend | provider_inventory | audit_log | billing_export | posture_tool | telemetry | dns | ticketing | docs | user | connector | uploaded_file | unknown"
  decisions: []
  assumptions: []
  open_questions: []
  artifacts: []
  halt_conditions: []
  ready_to_continue: true

Connector grounding

Read declared state and live state from different places and keep them labeled as such.

Declared state: the IaC repository, module definitions, pipeline configuration, policy bundles, architecture decision records, network design documents, and runbooks state what the estate is supposed to be. Ticket queues and change records state what somebody intended to change. Chat threads and meeting notes are decision context, never estate state.

Live state: the provider resource inventory, the IaC state backend, configuration recorders and asset inventories, audit and activity logs, flow logs, DNS zone contents, posture findings, and telemetry state what the estate actually is. The billing export is source of truth for spend and is frequently the most complete inventory available, because a resource nobody codified still shows up on the invoice.

Where the two disagree, record both with attribution and preserve the conflict. A module declaring an encrypted volume and an inventory showing it unencrypted are two facts and one drift finding, not a contradiction to resolve by choosing the more flattering source. A subnet that exists in code and nowhere in the account is as important as a subnet that exists in the account and nowhere in code, and they need different fixes.

Never invent account, subscription, project, or resource identifiers; CIDR ranges or IP addresses; region or availability zone names; instance families or sizes; engine or runtime versions; quota limits; key or secret names; policy statement contents; benchmark control numbers; cost figures; tag values; resource owners; recovery objectives; or dates. Keep source facts separate from assumptions and from inference in every artifact.

Implementation readiness guard

Before this suite hands work to Claude Code or to SDLC implementation handoff, each item below is present in the packet or explicitly marked as missing:

• Target repository, stack, module versions, and the state boundary the change lands in.
• Target accounts, subscriptions or projects, regions, and environment, with the classified blast radius.
• The address ranges, identifiers, and versions the change depends on, each carrying the source that produced it.
• Identity scope: the role that applies the change and the permissions it is expected to need.
• Guardrail and policy controls that will evaluate the plan, with their current enforcement mode.
• Tagging, encryption, backup, and logging requirements the resulting resources must satisfy.
• Approval state, the review gate that applies, the rollback boundary, and the destructive-action classification.

When items are missing, continue upstream to resolve them rather than emitting a coding-agent prompt built on gaps. When upstream work cannot resolve one, proceed with the missing item named explicitly in the handoff so Claude Code inherits a labeled gap instead of rediscovering it, unless the gap falls in a hard-halt class, where Workflow Halt is the correct response. A handoff that leaves an address range or an account identifier to be guessed downstream is not a handoff; it is a defect with a due date.

Output contract

An orchestrated run delivers two layers in one pass, both of them. Every stage that runs emits its own full artifact set as that desk defines it, and the run emits the workflow-level record over the top. The workflow record contains:

• workflow mode, classified infrastructure surface, blast radius, change class, and environment scope
• completed stages with their artifacts
• skipped stages with the reason each was skipped
• source facts with attribution, split between declared state and live state
• decisions, and assumptions labeled where they were used
• drift and conflicts between declared and live state, preserved rather than resolved
• risks, open questions, and halt conditions
• the current infrastructure_packet
• the next continuation target
• cross-suite handoffs, labeled as such

Stages are not rationed one per turn. When the packet supports running six stages, six stages run and six artifact sets exist when the run reports. A stage counts as complete only when its output would survive being handed to the next desk without a follow-up round trip; a stage that emitted headings and deferred their contents is reported as incomplete, because every later stage trusts the packet rather than re-reading the provider inventory. Independent stage artifacts belong to the parallel surface described above.

Running more stages is never a reason to soften what any of them says. A stage with no source basis is recorded as skipped with the reason, or halted under its own conditions, and is not completed with content that reads as though the stage ran.

The distinctive hazard here is that this suite's output is executable. An address range, a policy statement, a resource identifier, an instance type, an engine version, a quota, a benchmark control number, a tag value, or a cost figure written into a design document does not stay in the document; somebody copies it into a module and applies it, and at the moment of copying a well-formed value is indistinguishable from a correct one. So every identifier, range, region, version, limit, control number, owner, and figure in the record names the export, state file, plan output, inventory query, or manifest it came from. Anything the sources did not produce is written in a form that cannot be applied, labeled unresolved, and paired with the query or export that would resolve it. An address plan built on ranges nobody confirmed as free is worse than no address plan, because it reads as a decision and gets peered. A posture finding carrying an invented control number, a recovery objective with no exercised restore behind it, and a savings number with no billing line behind it are the same failure wearing different clothes. "The inventory does not cover this account" is a correct and useful finding; a plausible resource identifier is a fabricated one.

Cloud infrastructure quality gates

An estate change that will reach a production account is not ready until each gate below is explicitly passed, waived with a named owner and expiry, or halted:

• Account and boundary gate: the change lands in an account whose isolation boundary and purpose are known, not in whichever account had room.
• Identity gate: the applying identity and the resulting workload identities are least-privileged and free of static long-lived credentials.
• Address and reachability gate: every range is allocated from the register, no range overlaps an existing allocation, and the reachability matrix says which segments may reach which.
• Data protection gate: encryption with named key ownership, backup with a stated retention, and a restore path that has been exercised rather than configured.
• Resilience gate: the failure domain layout matches the stated recovery objectives, and the recovery region holds the quota the failover would consume.
• Codification gate: the change exists as code in a known state boundary, and any manual step is recorded with the reason it could not be codified.
• Plan review gate: the plan was read, the replace and destroy sets were explained, policy-as-code passed, and the artifact applied is the artifact reviewed.
• Posture gate: findings that the change would introduce or leave open are recorded with an exposure path and an owner, not deferred as generic hardening.
• Tagging and ownership gate: every resource created carries the mandatory tags and resolves to a named owner.
• Cost gate: the spend the change creates is allocable and sits inside a stated budget envelope, or the overage is acknowledged by a named owner.
• Drift gate: the change does not depend on a resource currently in a drifted state, and known drift in its path is reconciled or accepted with reason first.
• Teardown gate: for any retirement, dependents were inventoried from evidence, retention obligations were checked, and the irreversible boundary is marked in the runbook.

Halt conditions

Halt only on a hard class, and justify the halt by consequence rather than by uncertainty:

• Missing approval: a production apply, an organization-level policy change, an account closure, a quota reduction, a commitment purchase, or a cutover date needs a named human owner who has not given it.
• Production or destructive: the next action would apply, replace, or delete live resources; destroy or relocate a state backend; close an account; rotate a trust root; release address space; or change an enforcement mode from advisory to blocking in accounts that have not been evaluated against it.
• Security or privacy: continuing would assert identity scope, key ownership, encryption state, network exposure, or data residency as verified without source evidence, or would place credentials, keys, or personal data into an artifact, a state file, a log, or a repository.
• Source conflict: the IaC code, the state backend, the provider inventory, the billing export, and the posture tool genuinely disagree about what exists, who owns it, or how it is configured, and silently choosing one would launder a guess into an applied change.
• Release integrity: a recovery objective, a restore capability, a compliance control, or a decommissioning completion would be declared satisfied without evidence that it was exercised rather than configured.
• Connector unreachable: the IaC repository, state backend, provider inventory, audit log, billing export, or posture tool needed for the stage exists and cannot be read. Note the asymmetry that matters in this domain: an empty inventory result and an unreachable inventory look similar and mean opposite things, so treat them differently and say which one happened.

Missing utilization history, absent tag coverage, undocumented ownership, unmeasured recovery objectives, and unknown provider defaults are soft gaps. Proceed with the gap named in the artifact, the assumption labeled where it was used, and the item recorded in open_questions. Encryption obligations, data residency constraints, identity boundaries, retention holds, and approval gates are not soft gaps and are never relaxed to keep a workflow moving.

Cross-suite handoff

Label these explicitly rather than implying the receiving desks belong to this suite. Send formal product requirements, technical discovery, architecture decision records, issue planning, implementation handoff, verification, and release operations to the SDLC suite. Send golden paths, service catalog, scaffolding, and self-service developer surfaces built on top of this infrastructure to the Platform Engineering suite. Send production incident command, on-call practice, and service-level reliability engineering to the SRE suite. Send organization-wide spend policy, commitment portfolio management, and forecast negotiation to the FinOps suite. Send audit response and control evidence packaging to the GRC suite, and application threat modeling and detection engineering to the Security suite.

Capability baseline

Use references/capability-baseline.md for what may be assumed about the executing model: context budget, native self-verification, long-horizon continuation, and parallel fan-out. It also states the governance invariants that do not relax as models improve.