{
  "canonicalUrl": "https://xn--mwe.com/comparisons/runic-token-vs-cryptographic-token/",
  "claimStatus": "PROJECT DOCTRINE",
  "correctionStatus": "CURRENT K05 RELEASE",
  "decisionUse": "Use the distinction to prevent notation, encoding, test, trace, or cryptographic evidence from being represented as authority, truth, interoperability, field readiness, or operation.",
  "distinction": "Runic protocol token and Cryptographic token answer different technical or evidentiary questions and must not be collapsed.",
  "failure": "Conflation can create unsafe execution, false domain status, unsupported readiness, inaccessible content, or unreviewable evidence.",
  "id": "K01-COMP-056",
  "lastReviewed": "2026-08-16",
  "left": "Runic protocol token",
  "leftMeaning": "A visible Unicode identifier assigned a bounded message meaning.",
  "name": "Runic protocol token vs Cryptographic token",
  "releaseId": "K12-2026-08-16",
  "researchCutoff": "2026-08-16",
  "right": "Cryptographic token",
  "rightMeaning": "A cryptographically protected value or credential whose security properties depend on algorithms, keys, validation, and protocol context.",
  "slug": "runic-token-vs-cryptographic-token",
  "sourceRevalidatedAt": "2026-08-15T23:00:00Z",
  "topic": "machine-communication-protocols",
  "type": "Comparison"
}
