{
  "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",
  "id": "AC-K05-CRITICAL-DATACENTER-001",
  "lastReviewed": "2026-08-16",
  "name": "Critical Datacenter Mission and Safety Assurance Case",
  "nonClaims": [
    "No facility is certified by this pattern",
    "No reactor or datacenter deployment is claimed",
    "No offensive operation is authorized",
    "No lethal-force authority is created",
    "No mapping is a compliance determination"
  ],
  "releaseId": "K12-2026-08-16",
  "scope": "Public, non-classified reference pattern. A facility must replace every generic assumption with site evidence, license conditions, actual topology, competent authority, and current test results.",
  "sourceIds": [
    "SRC-INL-CCE",
    "SRC-NIST-800-82R3",
    "SRC-NIST-800-207",
    "SRC-NRC-10CFR-73-SUBPART-J-2026",
    "SRC-NERC-CIP-CATALOG-2026"
  ],
  "topClaim": "A named critical datacenter can preserve approved safety and mission functions under defined cyber, physical, electromagnetic, power, cooling, autonomy, and recovery stressors without transferring authority to an autonomous system."
}