{
  "canonicalUrl": "https://xn--mwe.com/contradictions/cryptographic-verification-vs-factual-truth/",
  "claimStatus": "RESOLVED BY DISTINCTION",
  "correctionStatus": "CURRENT K05 RELEASE",
  "id": "CON-K02-001",
  "lastReviewed": "2026-08-16",
  "machineRecordUrl": "https://xn--mwe.com/data/contradictions/cryptographic-verification-vs-factual-truth.json",
  "name": "Cryptographic verification versus factual truth",
  "propositionA": "A signature or credential can be technically valid under its verification method.",
  "propositionB": "The signed or credentialed claim can still be false, unauthorized, stale or unsuitable for the decision.",
  "relationship": "The propositions are compatible only when verification and truth are modeled as separate properties; collapsing them creates a contradiction in the decision record.",
  "releaseId": "K12-2026-08-16",
  "researchCutoff": "2026-08-16",
  "resolution": "The corpus now records source authorization, authenticity, integrity, relevance, reliability, currentness and truth separately.",
  "resolutionStatus": "RESOLVED BY DISTINCTION",
  "slug": "cryptographic-verification-vs-factual-truth",
  "sourceIds": [
    "SRC-W3C-VC-DM",
    "SRC-RFC-5280"
  ],
  "sourceRevalidatedAt": "2026-08-15T23:00:00Z",
  "topic": "evidence-provenance",
  "type": "Contradiction"
}