{
  "canonicalUrl": "https://xn--mwe.com/comparisons/decoder-agreement-vs-security/",
  "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": "Decoder agreement and Protocol security 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-087",
  "lastReviewed": "2026-08-16",
  "left": "Decoder agreement",
  "leftMeaning": "Canonical behavior matched for tested inputs.",
  "name": "Decoder agreement vs Protocol security",
  "releaseId": "K12-2026-08-16",
  "researchCutoff": "2026-08-16",
  "right": "Protocol security",
  "rightMeaning": "Authentication, authorization, confidentiality, integrity, availability, and abuse resistance are separately evidenced.",
  "slug": "decoder-agreement-vs-security",
  "sourceRevalidatedAt": "2026-08-15T23:00:00Z",
  "topic": "machine-communication-protocols",
  "type": "Comparison"
}