TRACE v0.2.0

TRACE v0.2.0

New in this release

• DID URI support — subject field now accepts DID URIs alongside plain identifiers
• Specification v0.1 — normative TRACE attestation envelope, hardware platform binding, SCITT anchoring
• Tutorial suite — end-to-end guides for signing, verification, AMD SEV-SNP, Intel TDX, NVIDIA H100, cMCP integration
• CoSAI WS4 alignment — normative OWASP Agentic Top 10 crosswalk
• Conformance test suite — 197 tests across 7 modules at tests.agentrust-io.com

Install

pip install agentrust-trace==0.2.0

Full documentation →

TRACE v0.1.1

Patch release. Required by cmcp-runtime 0.2.0.

Changes since v0.1.0

• [schema] Add software-only platform value for non-attested dev-mode records (#23) — dev records now carry platform: software-only instead of tpm2, keeping hardware assertions honest
• [spec] Make signature and freshness binding mandatory for Trust Records (#24)
• [models] Enforce exact hex length and reject uppercase in DigestStr (CRYPTO-008, CRYPTO-009) (#11)
• Workflow and infra fixes

TRACE v0.1.0

Initial public draft of the TRACE specification. Announced at Confidential Computing Summit, San Francisco, June 23 2026.

Highlights

• Trust Record schema (§3.1): subject, model, runtime, policy, data_class, tool_transcript, build_provenance, appraisal, transparency, cnf
• Wire format (§3.2): EAT/JWT and CBOR-COSE envelopes; profile URI tag:agentrust.io,2026:trace-v0.1
• Five-step offline verification protocol with no issuer callback (§3.3)
• Standards composition (§4): RATS/EAT, SLSA, SPIFFE, SCITT, EAR, MCP, A2A, AIBOM, C2PA
• Hardware roots: NVIDIA H100/Blackwell, Intel TDX, AMD SEV-SNP, Azure MAA, GCP Confidential Space, AWS Nitro
• JSON Schema for Trust Record validation (schema/trace-claim.json)
• Reference examples: AMD SEV-SNP, Intel TDX, NVIDIA H100