Iac Change

This is a Hermes-native iac-change workflow skill.

Why This Exists

iac-change exists because infrastructure changes had no owner: omh-deploy-and-monitor watches an application release, omh-release-cut decides one, and omh-inference-serving deploys a model server, while a Terraform plan with drift, a Helm chart change, or a manifest edit reached a generic planner with no blast radius, cost delta, or staged apply at all.

First Steps

• Ask for the saved plan or the diff output before assessing anything.
• Separate existing drift from the proposed change before ordering stages.

Do Not Use When

• The ask is shipping a new version of the application and watching its health signals after the deploy; use omh-deploy-and-monitor.
• The ask is deciding a versioned release -- what goes in, its tag, or its canary -- rather than changing declared infrastructure; use omh-release-cut.
• The ask is choosing and deploying a model-serving engine; use omh-inference-serving.
• Production is down or degraded right now and the ask is command of the incident; use omh-live-incident-response.