Documentation

Domains / iac-basic

IaC domain

Tool-agnostic infrastructure knowledge: topology, changesets, and operational runbooks.

Use it when: You manage infrastructure with Terraform, Pulumi, Kubernetes, or similar tools.

cumaru install agent <agent> --domain iac-basic

Pillars

PillarLifetimeHolds
topology/DurableProviders, accounts, stacks, and modules. depends-on is also the apply order.
runbooks/DurableOperational procedures such as secret rotation or failover.
intake/TransientMirror of change requests and incidents.
plans/TransientChangesets with blast radius, rollback plan, and promotion path.
exploring/TransientPre-change spikes. Never loaded by default.

Roles

  • Lead (platform): plans changes, maintains topology/, owns runbooks/ and exploring/, dispatches Dev agents.
  • Dev (operator): executes a changeset apply steps inside the active plan.

Lifecycle

  • intake/ and exploring/ -> plans/ -> topology/; runbooks/ relate to topology.
  • After absorption the plan is removed; only consumed intake and exploring entries are cleanup candidates.

Skills

Domain-specific skills, in addition to the universal ones: cumaru-intake,cumaru-explore,cumaru-plan,cumaru-topology,cumaru-absorb,cumaru-arch.

Bootstrap

No domain bootstrap document. cumaru bootstrap prints the universal rules.

Domain rules

  • targets: lists environments (dev, staging, prod, all, meta), not components.
  • There is no Ghost role.
  • meta.specification_dir is topology for coverage.

Example: Promote a network change

  1. A changeset plan declares blast radius, rollback, and the promotion path dev -> staging -> prod.
  2. Dev applies each step and records evidence in its handoff.
  3. cumaru-absorb updates the networking node in topology/ and removes the plan.

Source: domain.md, config.yaml, roles, skills at revision 37ad79f. The example is a summary of the shipped recipes, not CLI output.

Back to the comparison