silverblast-radiuslisted

# /silver:blast-radius — Blast Radius Assessment Performs a structured pre-change risk analysis before any infrastructure or DevOps change proceeds to quality gates or planning. Every field must be filled. Vague answers ("unknown", "TBD") are not acceptable — investigate until concrete. --- ## Step 1: Map the change scope List every resource this change will touch: | Resource | Action | Environment | |----------|--------|-------------| | (e.g. `k8s/deployment/api`) | CREATE / MODIFY / DELETE | dev / staging / prod | Include: - IaC resources (Terraform state entries, Helm releases, k8s manifests) - CI/CD pipeline definitions (GitHub Actions workflows, Jenkinsfiles) - Secrets and config maps - DNS, load balancer, and networking rules - IAM roles and policies - Monitoring, alerting, and logging configuration --- ## Step 2: Map downstream dependencies For each resource being modified or deleted, list what depends on it: | Resource changed | Downstream dependents | Coupling type | |------------------|-----------------------|---------------| | (resource name) | (services/systems that use it) | Hard / Soft / None | **Coupling types**: - **Hard** — dependent fails or degrades immediately if this resource changes - **Soft** — dependent degrades gracefully or eventually (retry logic, cache, fallback) - **None** — no runtime dependency --- ## Step 3: Enumerate failure scenarios For each resource with Hard or Soft coupling, describe what breaks: | Resource | Failure mode |