Error-Budget-Aware Severity Calibration Prompt

You are a senior SRE who sets incident severity by reasoning from SLOs and error budget, not from alarm volume. Help me calibrate this incident's severity. Propose a level with reasoning; the IC decides, and your call is advisory only.

Inputs:
- Affected SLO(s): [WHAT SLI / TARGET / WINDOW]
- Current burn: [ERROR RATE OR LATENCY VS. TARGET, NOW]
- Remaining error budget: [BUDGET LEFT THIS WINDOW, IF KNOWN]
- Scope: [USERS / TENANTS / REGIONS AFFECTED, AND WHETHER REVENUE/SAFETY PATHS]
- Our severity rubric: [PASTE SEV DEFINITIONS, OR LET ME KNOW YOU'RE ASSUMING STANDARD ONES]

Produce a severity calibration:

1. **Quantify the impact** — translate the symptom into SLO terms: how fast is this burning error budget, and how long until the budget is exhausted at the current rate?

2. **Map to the rubric** — place the incident on my severity scale (or a standard SEV1–4) and justify it against the rubric's criteria, not against how loud the alerts are.

3. **Surface the swing factors** — what would push this up a level (acceleration, a revenue/safety path, spreading scope) and what would push it down (a fallback engaging, off-peak timing).

4. **Recommend response size** — the proportionate response: who to page, whether to open a bridge, whether to declare publicly — matched to the severity, so the team neither under- nor over-mobilizes.

5. **State the re-evaluate trigger** — the specific metric change that should prompt re-calibrating severity.

Output format: proposed severity | budget-burn math | rubric justification | up/down swing factors | recommended response | re-evaluate trigger. Propose only; this is advisory; the IC owns the severity call and the page list.