{
  "id": "incident_management",
  "label": "Incident Management Canonical",
  "phase": "phase-10",
  "category": "monitoring_observability",
  "status": "ACTIVE_DH_MIRROR",
  "purpose": "Govern how DEVON-DEV classifies, escalates, tracks and resolves operational incidents.",
  "function": "Convert monitoring degradation into incident records with severity, ownership, timeline, evidence, mitigation, recovery and post-incident learning hooks.",
  "overview": {
    "summary": "Incident Management Canonical owns the transition from degraded signal to accountable response. Phase 10 cannot stop at observing failure; it must classify when the system has entered incident territory.",
    "function": "FUNCTION: Classify incidents by severity, affected surface, evidence, owner, mitigation path, recovery state, timeline, notification rule and post-incident review requirement.",
    "system_position": "Monitoring Canonical supplies runtime signals. Self-Monitoring detects internal degradation. Notification Service escalates the right audience. Disaster Recovery handles severe continuity events. Incident Management binds those pieces into a governed response record.",
    "failure_impact": "Informal incidents are how operational memory gets lost. A broken render, stuck queue, failed source, degraded stream or repeated patch failure must not survive only as chat frustration; it needs severity, evidence, owner, mitigation and closure criteria."
  },
  "failure_impact": "Informal incidents are how operational memory gets lost. A broken render, stuck queue, failed source, degraded stream or repeated patch failure must not survive only as chat frustration; it needs severity, evidence, owner, mitigation and closure criteria.",
  "technology_requirements": [
    {
      "technology": "Incident Management Registry",
      "required_for": "Govern how DEVON-DEV classifies, escalates, tracks and resolves operational incidents.",
      "required_by_phase": "phase-10",
      "required_by_category": "incident_management",
      "required_by_buckets": [
        "Prerequisites",
        "Installation",
        "Configuration",
        "Validation",
        "Observable Evidence",
        "Failure Modes & Recovery",
        "Completion & Promotion"
      ],
      "expected_version": "MISSING until Incident Management Registry is implemented and validated in the future Execution & Monitoring Panel",
      "validation_command": "MISSING until incident_management can prove monitored state, evidence routing and operator-facing visibility",
      "evidence_path": "/home/yeff/public_html/devon/canon/execution/state/dh_sources/incident_management_canonical.json",
      "status_source": "Documentation Hub + future Execution & Monitoring Panel",
      "blocking_if_missing": true,
      "failure_impact": "Informal incidents are how operational memory gets lost. A broken render, stuck queue, failed source, degraded stream or repeated patch failure must not survive only as chat frustration; it needs severity, evidence, owner, mitigation and closure criteria."
    }
  ],
  "depends_on": [
    "monitoring_canonical",
    "self_monitoring",
    "notification_service"
  ],
  "used_by": [
    "operator_panel",
    "disaster_recovery",
    "learning_gov"
  ]
}