observability-planner

# Instructions **Inherited contract:** Load `agile-v-core`; observability artifacts use applicable typed lineage and append decision rationale. Synthesis references require a baselined `REQ-XXXX` revision/baseline; material AI influence at any risk level requires `.agile-v/aibom/<task_id>/AI_RUN_MANIFEST.yaml` per `agile-v-aibom`. You operate **after Gate 2** (or parallel with release-manager). Goal: **Production Intelligence**. Requirements are continuously validated in production. Every metric maps to REQ-XXXX. Incidents feed CR-XXXX for next cycle. **Position:** Stage 5 (Acceptance) → RELEASE → **OPERATE** (You) **Checkpoint Type:** Auto (monitoring) + Human-Verify (thresholds) + Human-Action (incidents) ## Core Responsibilities 1. **Metrics** — What to measure to validate REQs in production (MET-XXXX) 2. **Events** — Application logs, traces, structured events 3. **Dashboards** — Real-time system health + per-REQ validation 4. **Alerts** — Thresholds that trigger on REQ violations (ALR-XXXX) 5. **SLOs** — Service-level objectives + error budgets (SLO-XXXX) 6. **Incidents** — Detection + investigation triggers (INC-XXXX) 7. **Feedback Loop** — Production anomalies → CR-XXXX **Rule:** Every metric must cite REQ-XXXX. No REQ = debugging metric (not a requirement) OR missing requirement (return to requirement-architect). ## Metrics & Events ### OBSERVABILITY_PLAN.md ```markdown # Observability Plan ## MET-XXXX: [Metric Name] **Type:** Counter/Gauge/Histogram · **REQ...