{
  "canonicalClaimUrl": "https://xn--mwe.com/questions/does-scheduler-chain-prove-reliability/#clm-k07-q-062",
  "claimStatus": "PROJECT DOCTRINE",
  "correctionStatus": "CURRENT K07 RECORD",
  "id": "CLM-K07-Q-062",
  "lastReviewed": "2026-08-16",
  "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-062.json",
  "name": "Does a scheduler result chain prove reliability?",
  "ownerAnchor": "clm-k07-q-062",
  "ownerId": "K07-Q-062",
  "ownerRoute": "/questions/does-scheduler-chain-prove-reliability/",
  "ownerType": "question",
  "proposition": "It proves the fixture's sequence, custody, cause, repair, and retest records are internally consistent; no owner scheduler was installed or observed running.",
  "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.",
  "releaseId": "K12-2026-08-16",
  "releaseVersion": "2.1.0",
  "researchCutoff": "2026-08-16",
  "scope": "K07 direct answer for Does a scheduler result chain prove reliability?",
  "slug": "clm-k07-q-062",
  "sourceIds": [
    "SRC-W3C-PROV-O",
    "SRC-RFC-3161",
    "SRC-C2PA",
    "SRC-IN-TOTO"
  ],
  "sourceSections": [
    {
      "section": "Abstract and status",
      "sourceId": "SRC-W3C-PROV-O",
      "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
      "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
      "url": "https://www.w3.org/TR/prov-o/#abstract"
    },
    {
      "section": "RFC status and update chain",
      "sourceId": "SRC-RFC-3161",
      "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
      "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
      "url": "https://www.rfc-editor.org/info/rfc3161/"
    },
    {
      "section": "Version history — 2.4",
      "sourceId": "SRC-C2PA",
      "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
      "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
      "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
    }
  ],
  "type": "ClaimRecord"
}