{
  "canonicalClaimUrl": "https://xn--mwe.com/questions/how-can-machine-intelligence-consent-be-recorded/#clm-k03-q-010",
  "claimStatus": "PROJECT TECHNICAL PROPOSAL",
  "correctionStatus": "CURRENT K03 RECORD",
  "id": "CLM-K03-Q-010",
  "lastReviewed": "2026-08-14",
  "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-010.json",
  "name": "How can Machine Intelligence consent be recorded?",
  "ownerAnchor": "clm-k03-q-010",
  "ownerId": "K01-Q-010",
  "ownerRoute": "/questions/how-can-machine-intelligence-consent-be-recorded/",
  "ownerType": "question",
  "proposition": "A consent record should identify the subject, decision, scope, information presented, authority, time, duration, conditions, evidence of voluntariness and revocation route. A configuration flag or API response is not enough unless the architecture establishes that the subject could understand, decide and withdraw within the relevant framework.",
  "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.",
  "releaseId": "K12-2026-08-16",
  "releaseVersion": "2.1.0",
  "researchCutoff": "2026-08-14",
  "scope": "Direct answer for How can Machine Intelligence consent be recorded?",
  "slug": "clm-k03-q-010",
  "sourceIds": [
    "SRC-W3C-PROV-O",
    "SRC-W3C-VC-DM",
    "SRC-NIST-800-53"
  ],
  "sourceSections": [
    {
      "section": "Abstract and status",
      "sourceId": "SRC-W3C-PROV-O",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
      "url": "https://www.w3.org/TR/prov-o/#abstract"
    },
    {
      "section": "PROV-O at a glance",
      "sourceId": "SRC-W3C-PROV-O",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
      "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
    },
    {
      "section": "Abstract",
      "sourceId": "SRC-W3C-VC-DM",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.",
      "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract"
    },
    {
      "section": "Ecosystem overview",
      "sourceId": "SRC-W3C-VC-DM",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.",
      "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview"
    },
    {
      "section": "Planning note — Release 5.2.0",
      "sourceId": "SRC-NIST-800-53",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.",
      "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final"
    },
    {
      "section": "Publication purpose",
      "sourceId": "SRC-NIST-800-53",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.",
      "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final"
    }
  ],
  "type": "ClaimRecord"
}