{
  "canonicalUrl": "https://xn--mwe.com/comparisons/centrality-vs-vulnerability/",
  "claimStatus": "PROJECT DOCTRINE",
  "correctionStatus": "CURRENT K05 RELEASE",
  "decisionUse": "Use this distinction to prevent a state model, source request, observation chain, merge, centrality result, workbook, case file, scheduler chain, release projection, or trend from being represented as authority, deployment, operation, or factual truth.",
  "distinction": "Dependency centrality and Operational vulnerability answer different evidentiary, governance, or operational questions and must remain separate.",
  "failure": "Conflation can manufacture readiness, erase uncertainty, bypass accountable review, or expose protected information.",
  "id": "K01-COMP-082",
  "lastReviewed": "2026-08-16",
  "left": "Dependency centrality",
  "leftMeaning": "Counts abstract mission-thread dependence.",
  "name": "Dependency centrality vs Operational vulnerability",
  "releaseId": "K12-2026-08-16",
  "researchCutoff": "2026-08-16",
  "right": "Operational vulnerability",
  "rightMeaning": "Requires protected technical assessment of real systems and adversary opportunities.",
  "slug": "centrality-vs-vulnerability",
  "sourceRevalidatedAt": "2026-08-15T23:00:00Z",
  "topic": "cyber-physical-mission-assurance",
  "type": "Comparison"
}