Named evidence profiles for the kinds of external input a workflow can attest to under §23: which attestation types apply, how fresh the evidence is expected to be, and which shipped chains already consume it. Not new infrastructure, just a map over the existing vc-2.0 / c2pa-manifest / rfc3161-snapshot attestation types and the §23.4 freshness/consent metadata.
Each profile is a reference pairing of attestation type + expected freshness, not a schema extension. A workflow attesting to one of these input kinds should declare the listed attestation type(s) and set §23.4 freshness_class to the expected value; verifiers report freshness_status: fresh|stale|undeclared accordingly.
chaingraph/evidence-profiles.manifest.json, validated against chaingraph/schemas/evidence-profile.manifest.schema.json via node scripts/validate-evidence-profiles.mjs. This page's data mirrors the manifest inline (zero fetch after load, per CONTRACT §0); the manifest is the machine-readable artifact for agents and tooling.