{
  "id": "fleet_incident_registry",
  "label": "Fleet Incident Registry Canonical",
  "phase": "phase-14",
  "category": "fleet_monitoring_mirror_failover",
  "status": "ACTIVE_DH_MIRROR",
  "purpose": "Fleet Incident Registry Canonical is the Phase 14 authority that records fleet-level incidents for YEFF AI v1 servers as governed operational objects.",
  "function": "Classify, register and track incidents with affected server, customer account, signal source, severity, owner, evidence, status transitions and recovery relation before notification or failover can act.",
  "technology_requirements": [
    {
      "technology": "Fleet Incident Registry",
      "required_for": "Fleet Incident Registry Canonical is the Phase 14 authority that records fleet-level incidents for YEFF AI v1 servers as governed operational objects.",
      "required_by_phase": "phase-14",
      "required_by_category": "fleet_incident_registry",
      "required_by_buckets": [
        "Prerequisites",
        "Installation",
        "Configuration",
        "Validation",
        "Observable Evidence",
        "Failure Modes & Recovery",
        "Completion & Promotion"
      ],
      "expected_version": "MISSING until Fleet Incident Registry is implemented and validated in the future Execution & Monitoring Panel",
      "validation_command": "MISSING until fleet_incident_registry can prove scope, evidence, execution state and promotion decision",
      "evidence_path": "/home/yeff/public_html/devon/canon/execution/state/dh_sources/fleet_incident_registry.json",
      "status_source": "Documentation Hub + future Execution & Monitoring Panel",
      "blocking_if_missing": true,
      "failure_impact": "If this gate fails, Devon cannot prove which server was affected, why severity was assigned, who owns correction or whether the incident is still open."
    }
  ],
  "depends_on": [],
  "used_by": [],
  "overview": {
    "summary": "Fleet Incident Registry Canonical is the Phase 14 authority that records fleet-level incidents for YEFF AI v1 servers as governed operational objects.",
    "function": "FUNCTION: Classify, register and track incidents with affected server, customer account, signal source, severity, owner, evidence, status transitions and recovery relation before notification or failover can act.",
    "system_position": "This category owns incident identity. It is not notification and not recovery execution. The exclusive risk here is incident ambiguity. Without a registry, alerts become messages and failures become memories.",
    "failure_impact": "If this gate fails, Devon cannot prove which server was affected, why severity was assigned, who owns correction or whether the incident is still open."
  },
  "failure_impact": "If this gate fails, Devon cannot prove which server was affected, why severity was assigned, who owns correction or whether the incident is still open."
}