Deploy And Monitor

This is a Hermes-native deploy-and-monitor workflow skill.

Why This Exists

deploy-and-monitor exists because a deploy is judged healthy by whoever last looked at a dashboard: it fixes the baseline before the change and names the thresholds that mean roll back.

Do Not Use When

• An incident has already been declared and the work is commanding it -- severity, commander, running timeline, recovery verification -- rather than watching a release; use omh-live-incident-response.
• The ask is deciding a release before it ships -- what goes in, its version and tag, the canary stages, or which command rolls it back; use omh-release-cut, which writes the rollback trigger down before it is needed.
• The change is to declared infrastructure itself -- a Terraform plan, a Kubernetes manifest, a Helm chart -- and needs its drift, blast radius, and cost delta read before it is applied; use omh-iac-change.

Examples

Good example: