Trace a claim to its evidence

These answers are deterministic read-model proof. They do not create evidence, canonical truth, review approval, a governance decision, promotion, certification, release authority, or backend equivalence.

CasePASS

Questions3/3

Evidence checks11/11

Supportsupported-preview

Follow an accepted assertion through its source artifact, evidence, validation, governance, promotion, and version history.

External input files

File	Purpose	Role	Bytes	SHA-256
fixtures/canonical/assertion-evidence-thin-slice.json	Accepted assertion with source, artifact, evidence, validation, review, decision, promotion, and version lineage.	canonical-fixture	13,670	sha256:ebe489c0b5dbdcc490aca7bf76516d3e988e4eaa49ab172500532f003ef6902d

The case manifest is fixtures/reference-cases/trace-a-claim-to-evidence.json with digest sha256:4562210194fbfbdef0cbd8febef7cb12ba14b2bb229ac77db2ae5d3c527cdb06. These identities are taken from the executed suite report, not copied into this page by hand.

1. Where did the accepted claim come from?

Verified answerThe claim came from the vendor-page artifact, which retains its source and extracted evidence references.

Answer state: answered

Why it matters: A reader can inspect the source carrier instead of trusting an ungrounded answer.

Evidence returned by the execution

Proof	Kind	Actual runtime value	Result
Source artifact	artifact	"artifact:vendor-page-001"	PASS
Original source	source	["source:vendor-site"]	PASS
Extracted evidence	evidence	["evidence:extract-001"]	PASS

The source-artifact-lineage reference query executed through rust-canonical-cli. Every value above was resolved from the query's actual output and exactly matched the case contract.

Show the complete verified runtime output

{
  "boundary": {
    "doesNotImplyReviewOrPromotion": true,
    "readModelOnly": true,
    "reviewDecisionPromotionSeparated": true,
    "sourceArtifactEvidenceAssertionSeparated": true
  },
  "candidateAssertionRefs": [
    "assertion:control-support-001"
  ],
  "canonicalStateMutated": false,
  "caveatRefs": [
    "gap:fixture-source"
  ],
  "changeSetRefs": [
    "changeset:control-support-001"
  ],
  "decisionRefs": [
    "decision:control-support-001"
  ],
  "diagnostics": [],
  "evidenceRefs": [
    "evidence:extract-001"
  ],
  "promotionRefs": [
    "promotion:control-support-001"
  ],
  "proposalRefs": [
    "proposal:control-support-001"
  ],
  "queryKind": "source-artifact-lineage",
  "queryOutputPromotedToCanonicalTruth": false,
  "reviewRefs": [
    "review:control-support-001"
  ],
  "sourceArtifactRef": "artifact:vendor-page-001",
  "sourceRefs": [
    "source:vendor-site"
  ],
  "status": "pass",
  "validationResultRefs": [
    "validation:assertion-has-evidence-001"
  ],
  "versionRefs": [
    "version:compliance-demo-v0",
    "version:compliance-demo-v1"
  ]
}

2. What governance lineage made this evidence part of accepted state?

Verified answerThe evidence is linked through validation, review, an approving decision, promotion, and the accepted version history.

Answer state: answered

Why it matters: Evidence presence is kept separate from the governance events that make a version current.

Evidence returned by the execution

Proof	Kind	Actual runtime value	Result
Validation	validation	["validation:assertion-has-evidence-001"]	PASS
Approving decision	governance	["decision:control-support-001"]	PASS
Promotion	governance	["promotion:control-support-001"]	PASS
Version history	current-state	["version:compliance-demo-v0","version:compliance-demo-v1"]	PASS

The evidence-lineage reference query executed through python-canonical-runtime. Every value above was resolved from the query's actual output and exactly matched the case contract.

Show the complete verified runtime output

{
  "evidenceRef": "evidence:extract-001",
  "supportKind": "supports",
  "method": "manual-extraction",
  "createdBy": "actor:max",
  "lifecycle": {
    "evidence": "accepted-as-support"
  },
  "artifactRefs": [
    "artifact:vendor-page-001"
  ],
  "sourceRefs": [
    "source:vendor-site"
  ],
  "candidateAssertionRef": "assertion:control-support-001",
  "candidateAssertion": {
    "assertionRef": "assertion:control-support-001",
    "lifecycle": {
      "assertion": "accepted"
    },
    "epistemicState": "accepted",
    "evidenceRefs": [
      "evidence:extract-001"
    ],
    "challengeEvidenceRefs": []
  },
  "validationResultRefs": [
    "validation:assertion-has-evidence-001"
  ],
  "changeSetRefs": [
    "changeset:control-support-001"
  ],
  "proposalRefs": [
    "proposal:control-support-001"
  ],
  "reviewRefs": [
    "review:control-support-001"
  ],
  "decisionRefs": [
    "decision:control-support-001"
  ],
  "promotionRefs": [
    "promotion:control-support-001"
  ],
  "versionRefs": [
    "version:compliance-demo-v0",
    "version:compliance-demo-v1"
  ],
  "supersession": []
}

3. Can the accepted assertion be traced all the way back to its source?

Verified answerYes. The assertion exposes its evidence, artifact, source, validation, review, decision, promotion, and version references.

Answer state: answered

Why it matters: The answer remains auditable from canonical assertion back to the external source identity.

Evidence returned by the execution

Proof	Kind	Actual runtime value	Result
Assertion evidence	evidence	["evidence:extract-001"]	PASS
Evidence artifact	artifact	["artifact:vendor-page-001"]	PASS
Original source	source	["source:vendor-site"]	PASS
Accepted epistemic state	current-state	"accepted"	PASS

The assertion-lineage reference query executed through python-canonical-runtime. Every value above was resolved from the query's actual output and exactly matched the case contract.

Show the complete verified runtime output

{
  "assertionRef": "assertion:control-support-001",
  "assertionLifecycle": {
    "assertion": "accepted"
  },
  "epistemicState": "accepted",
  "evidenceRefs": [
    "evidence:extract-001"
  ],
  "challengeEvidenceRefs": [],
  "artifactRefs": [
    "artifact:vendor-page-001"
  ],
  "sourceRefs": [
    "source:vendor-site"
  ],
  "validationResultRefs": [
    "validation:assertion-has-evidence-001"
  ],
  "changeSetRefs": [
    "changeset:control-support-001"
  ],
  "proposalRefs": [
    "proposal:control-support-001"
  ],
  "reviewRefs": [
    "review:control-support-001"
  ],
  "decisionRefs": [
    "decision:control-support-001"
  ],
  "promotionRefs": [
    "promotion:control-support-001"
  ],
  "versionRefs": [
    "version:compliance-demo-v0",
    "version:compliance-demo-v1"
  ],
  "supersession": []
}

What this proof means

All 3 questions executed successfully. Their underlying reference queries exactly matched their declared expectations, and all 11 answer/evidence checks resolved against actual runtime output.

What this does not prove

These answers are deterministic read-model proof. They do not create evidence, canonical truth, review approval, a governance decision, promotion, certification, release authority, or backend equivalence.