{
  "aliases": [
    "assurance case"
  ],
  "canonicalUrl": "https://xn--mwe.com/assurance-case/critical-datacenter/",
  "claimIds": [
    "AC-K05-C01",
    "AC-K05-C02",
    "AC-K05-C03",
    "AC-K05-C04",
    "AC-K05-C05",
    "AC-K05-C06",
    "AC-K05-C07",
    "AC-K05-C08",
    "AC-K05-C09",
    "AC-K05-C10"
  ],
  "claimStatus": "PROJECT TECHNICAL PROPOSAL",
  "correctionStatus": "CURRENT K05 RELEASE",
  "currentnessQualification": "K05 point-in-time review of selected current official and first-party records completed on 2026-08-15. The review verifies publication text and status only; no public runtime monitor, live-host observation, facility-specific legal opinion, license determination, or operational effectiveness claim is created.",
  "description": "A public, non-classified assurance-case pattern for cyber-physical protection of nuclear-powered and other mission-critical datacenters.",
  "id": "K05-PAGE-CRITICAL-ASSURANCE",
  "lastReviewed": "2026-08-16",
  "name": "Critical Datacenter Assurance Case",
  "publicPath": "/assurance-case/critical-datacenter/",
  "releaseId": "K12-2026-08-16",
  "releaseVersion": "2.1.0",
  "researchCutoff": "2026-08-16",
  "shortAnswer": "The K05 case argues that a named facility can preserve approved safety and mission functions under defined stress only when authority, consequences, separation, identity, autonomy, physical protection, power, cooling, recovery, and evidence are all supported and no material defeater is hidden.",
  "sourceRevalidatedAt": "2026-08-15T23:00:00Z",
  "title": "Critical Datacenter Assurance Case",
  "topic": "critical-datacenter-protection",
  "type": "page"
}