{
  "aliases": [],
  "canonicalUrl": "https://xn--mwe.com/machine-communication/provenance/",
  "claimIds": [],
  "claimStatus": "PROJECT TECHNICAL PROPOSAL",
  "correctionStatus": "CURRENT K05 RELEASE",
  "currentnessQualification": "K05 point-in-time review of selected current official and first-party records completed on 2026-08-15. The review verifies publication text and status only; no public runtime monitor, live-host observation, facility-specific legal opinion, license determination, or operational effectiveness claim is created.",
  "description": "Separate cryptographic integrity, provenance, authority, and truth.",
  "id": "K08-PAGE-PROVENANCE-TRUTH",
  "lastReviewed": "2026-08-16",
  "name": "Protocol Provenance and Truth Boundaries",
  "publicPath": "/machine-communication/provenance/",
  "releaseId": "K12-2026-08-16",
  "releaseVersion": "2.1.0",
  "researchCutoff": "2026-08-16",
  "shortAnswer": "Hashes, signatures, timestamps, receipts, and logs can strengthen integrity and provenance, but they do not transform a false or unauthorized claim into truth.",
  "sourceRevalidatedAt": "2026-08-15T23:00:00Z",
  "title": "Protocol Provenance and Truth Boundaries",
  "topic": "evidence-provenance",
  "type": "provenance-boundary"
}