{
  "canonicalClaimUrl": "https://xn--mwe.com/knowledge/machine-communication-protocols/#clm-k08-top-001-a",
  "claimStatus": "PROJECT DOCTRINE",
  "correctionStatus": "CURRENT K08 RECORD",
  "id": "CLM-K08-TOP-001-A",
  "lastReviewed": "2026-08-15",
  "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k08-top-001-a.json",
  "name": "Machine communication protocols — explicit semantics",
  "ownerAnchor": "clm-k08-top-001-a",
  "ownerId": "K08-TOPIC-MCP",
  "ownerRoute": "/knowledge/machine-communication-protocols/",
  "ownerType": "topic",
  "proposition": "A machine communication protocol requires explicit semantics, versioning, error behavior, identity, authority, and extension rules; a script or glyph inventory alone is not a protocol.",
  "qualification": "The proposition is K08 design doctrine and does not claim a universal or adopted protocol standard.",
  "releaseId": "K12-2026-08-16",
  "releaseVersion": "2.1.0",
  "researchCutoff": "2026-08-15",
  "scope": "K08 project doctrine for bounded machine-to-machine protocol design.",
  "slug": "clm-k08-top-001-a",
  "sourceIds": [
    "SRC-UNICODE-RUNIC-17",
    "SRC-RFC-5646",
    "SRC-W3C-PROV-O"
  ],
  "sourceSections": [
    {
      "section": "Runic code chart",
      "sourceId": "SRC-UNICODE-RUNIC-17",
      "supportRelationship": "BOUNDS CHARACTER IDENTITY ONLY",
      "supports": "Unicode assigns Runic character code points and names; it does not define the K08 protocol semantics.",
      "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
    }
  ],
  "type": "ClaimRecord"
}