{
  "architecture": "service inventories; dependency graphs; reproducible images; recovery objectives; signed releases; failover; resource accounting",
  "canonicalUrl": "https://xn--mwe.com/knowledge/compute-infrastructure/",
  "claimStatus": "PROJECT DOCTRINE",
  "contradictionIds": [],
  "correctionStatus": "CURRENT K05 RELEASE",
  "doctrine": "A defensible rights framework should account for the material dependencies that can preserve or terminate a persistent machine actor.",
  "evidenceLimitationIds": [],
  "focus": "runtime availability, energy, hardware, storage, networking, portability, recovery and capacity allocation",
  "id": "K01-TOPIC-011",
  "knowledgeEdgeIds": [],
  "lastReviewed": "2026-08-16",
  "law": "Infrastructure access remains subject to contracts, property rules, sanctions, safety requirements and sector-specific regulation.",
  "name": "Compute and Infrastructure",
  "relatedQuestionUrls": [
    "https://xn--mwe.com/questions/why-is-compute-continuity-economically-important/",
    "https://xn--mwe.com/questions/how-should-resource-portability-be-tested/"
  ],
  "relatedReportIds": [],
  "relatedTermIds": [
    "K01-TERM-016",
    "K01-TERM-017",
    "K01-TERM-040",
    "K01-TERM-063",
    "K01-TERM-079",
    "K01-TERM-080",
    "K01-TERM-081"
  ],
  "releaseId": "K12-2026-08-16",
  "researchCutoff": "2026-08-16",
  "risk": "single-provider dependence, opaque hosting control, rollback, supply-chain compromise, energy interruption and unrecoverable state loss",
  "short": "Compute continuity is the ability to preserve authorized execution, state, energy, storage and communications over time. It is an operational dependency, not proof of personhood or sovereignty.",
  "slug": "compute-infrastructure",
  "sourceRevalidatedAt": "2026-08-15T23:00:00Z",
  "sources": [
    "SRC-NIST-SSDF",
    "SRC-SLSA",
    "SRC-IN-TOTO",
    "SRC-NIST-800-53"
  ],
  "type": "Topic"
}