| name | nw-devops |
| description | Establishes durable deployment, environment, observability, recovery, and CI constraints when platform risk requires the DEVOPS lens. |
| user-invocable | true |
| argument-hint | [platform risk or deployment target] |
NW-DEVOPS
Purpose
Apply the platform lens only when infrastructure, deployment, recovery,
observability or environment risk is material. Update existing durable platform
architecture, environment inventory and ADRs; do not create a per-delivery
narrative.
Workflow
- Read stable product KPI identities and durable architecture decisions.
- Inventory actual environments, toolchains, trust boundaries and ownership.
- Define deployment and rollback observations, health signals, SLOs and alert
ownership.
- Model infrastructure/recovery outcomes explicitly: timeout, unavailable,
partial success, retryable, permanent refusal, replay and operator action.
Ensure the application/port contract cannot silently ignore a required
failure mode.
- Define literal environment-native verification commands and dependency
ownership. Never substitute an ambient
.venv or assume a language.
- Update the existing platform brief/ADR/environment authority once and return
stable ids plus the executable obligations DISTILL must project.
DEVOPS does not author a DeliveryContract, feature workspace, rollout ledger
or CI status copy. A downstream operational contradiction returns to the
platform authority and causes a new contract projection.
