Evidence

Claim string and attestation summary

A single-line claim string carries the full scope of a conformance result; the attestation summary renders it for assessors on one page.

Every conformance result is expressible as one line. The claim names the framework version, assurance level, family, corpus, checked required axes, verdict, release identity, and the content address of the report that substantiates it — the complete scope travels with the claim.

Claim string

The axes field lists checked required axes; the report field lets any holder verify every other field.

Claim string
text
TSS-CF/1.0 CAL-2 family=dkls23-aff3 corpus=core@2026.06
  axes=publication-frontier,leakage-boundary verdict=conformant
  release=git:2f454691 report=cid:blake3:9f2c...

Attestation summary

The attestation summary is a fixed one-page rendering with eight sections in order: Claim, Verdict, Scope, Required-axis table, Exceptions, Counterexamples, Scope statement, Reproduction. It is the entry point for assessment; the machine report carries full detail.

Attestation summary (abridged)
text
TSS-CF ATTESTATION SUMMARY
CLAIM    TSS-CF/1.0 CAL-2 family=dkls23-aff3 corpus=core@2026.06
         axes=publication-frontier,leakage-boundary
         verdict=conformant release=git:2f454691 report=cid:...
VERDICT  CONFORMANT - on the scenarios and axes in scope, the
         implementation matched the machine-checked formal model.
SCOPE    317 scenarios; 309 admissible; runners + adapter versions
REQUIRED publication-frontier  MATCHED  checked     block_release
AXES     leakage-boundary      MATCHED  proof_open  block_release
REPRODUCE  dvm-conformance verify cid:blake3:9f2c...

Scope statement

Every attestation carries a fixed scope statement naming the obligations tracked outside the claim: cryptographic hardness, side-channel behaviour, formal-model fidelity, RNG quality, secure erasure, and inputs beyond the stated corpus. Each of these carries its own evidence track in the assurance stack.

Presentation rules

Renderings use the three verdict states and the standard colors — green Conformant, yellow Indeterminate, red Violated. An Indeterminate rendering names its typed cause. Aggregations combine fail-closed: a corpus with a Violated verdict renders red; a required-axis Indeterminate renders yellow.