{
  "answer": "Hardware, libraries, certificates, devices, archives, and recovery paths may depend on supplier support; an algorithm standard alone cannot migrate those dependencies.",
  "canonicalUrl": "https://xn--mwe.com/questions/why-crypto-migration-needs-supplier-state/",
  "claimStatus": "PROJECT DOCTRINE",
  "correctionStatus": "CURRENT K05 RELEASE",
  "detail": "Hardware, libraries, certificates, devices, archives, and recovery paths may depend on supplier support; an algorithm standard alone cannot migrate those dependencies. K09 preserves the governing evidence, authority, currentness, and protected-information boundary.",
  "id": "K01-ANSWER-149",
  "lastReviewed": "2026-08-16",
  "question": "Why does cryptographic migration include supplier state?",
  "releaseId": "K12-2026-08-16",
  "researchCutoff": "2026-08-16",
  "shortAnswer": "Hardware, libraries, certificates, devices, archives, and recovery paths may depend on supplier support; an algorithm standard alone cannot migrate those dependencies.",
  "slug": "why-crypto-migration-needs-supplier-state",
  "sourceRevalidatedAt": "2026-08-15T23:00:00Z",
  "sources": [
    "SRC-W3C-PROV-O"
  ],
  "status": "PROJECT DOCTRINE",
  "topic": "evidence-provenance",
  "type": "Question"
}