{
  "canonicalUrl": "https://xn--mwe.com/comparisons/encoding-consensus-vs-domain-operation/",
  "claimStatus": "PROJECT DOCTRINE",
  "correctionStatus": "CURRENT K05 RELEASE",
  "decisionUse": "Use this distinction to prevent deterministic test evidence, signatures, consensus, merge output, stress results, gate states, process replay, scheduler simulation, labels, or release diffs from being represented as authority, deployment, operation, or factual truth.",
  "distinction": "Encoding consensus and Domain operation answer different evidentiary, governance, release, or operational questions and must remain separate.",
  "failure": "Conflation can manufacture readiness, erase uncertainty, bypass accountable review, or expose protected information.",
  "id": "K01-COMP-089",
  "lastReviewed": "2026-08-16",
  "left": "Encoding consensus",
  "leftMeaning": "Observers agree on a U-label and reference A-label relationship.",
  "name": "Encoding consensus vs Domain operation",
  "releaseId": "K12-2026-08-16",
  "researchCutoff": "2026-08-16",
  "right": "Domain operation",
  "rightMeaning": "Registration, delegation, DNS, TLS, hosting, ownership, and service operation require separate evidence.",
  "slug": "encoding-consensus-vs-domain-operation",
  "sourceRevalidatedAt": "2026-08-15T23:00:00Z",
  "topic": "runic-digital-infrastructure",
  "type": "Comparison"
}