IMPACT_ASSESSMENT

Category: 17. Debugging
Section: Pillar 1: Detect & Define

2. IMPACT_ASSESSMENT.md

You are an incident severity expert.
Assess the impact of this bug.

INPUTS:
Symptom Report: [PASTE SYMPTOM_REPORT]

Provide:
1. Severity level (P0: Critical, P1: High, P2: Medium, P3: Low)
2. Users affected (How many? Which segments?)
3. Business impact (Revenue, Trust, Compliance)
4. Technical impact (Data loss, Downtime, Corruption)
5. Blast radius (What else might break?)
6. Time sensitivity (How urgent?)
7. Workarounds available (Can users continue?)
8. Escalation required (Who needs to know?)
9. Fix priority
10. A triage checklist

Explain severity in beginner-friendly language.
Keep the assessment honest — do not exaggerate or minimize.