feat(trust): add TRACE-v0.2 runtime governance attestation type#6
feat(trust): add TRACE-v0.2 runtime governance attestation type#6imran-siddique wants to merge 6 commits into
Conversation
- Add TRACE-v0.2 to the attestation type field description in §5.2 - Add §5.2.1 Runtime Governance Attestations with TRACE spec, example entry, and discovery filter showing trustManifest.attestations.type filtering for hardware-verifiable governed agents - Add examples/agentrust-io-catalog.json: reference ai-catalog.json showing agentrust.io as a governed-agent federated registry with cMCP, Agent Manifest, and TRACE Registry entries, each carrying TRACE-v0.2 and SPIFFE-X509 attestations TRACE (Trust Runtime Attestation and Compliance Evidence) is an open EAT-profile (RFC 9711) standard for AI agent governance records. Spec: https://agentrust.io/trace — developed with AGT (microsoft/agent- governance-toolkit, 4200+ stars) and launching at Confidential Computing Summit June 23 2026. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
imran-siddique
requested review from
evalstate,
mindpower and
rvguha
as code owners
Adds examples/ards/ showing how agentrust.io participates in the Agentic Resource Discovery Specification (ARDS v0.9) as a specialized governed-agent federated registry. - ai-catalog.json: agentrust.io /.well-known/ai-catalog.json with cMCP, Agent Manifest SDK, and TRACE Registry entries, each carrying SPIFFE-X509 + TRACE-v0.2 attestations, plus the registry entry for ARD federation routing - README.md: explains the TRACE-v0.2 attestation integration point, discovery filter pattern, and how registry federation works Companion to ards-project/ard-spec#6 which adds TRACE-v0.2 as a standard attestation type in the spec. Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
- Restore two JSON code blocks (catalog entry + filter example) that were dropped in the initial commit due to bash heredoc expansion - Update spec link from https://agentrust.io/trace (not yet live) to https://agentrust-io.github.io/trace-spec/ (live now) - Fix em-dash corruption in opening sentence Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
@imran-siddique Thanks for adding TRACE-v0.2 runtime governance attestation type and example! Could you please move your example file(s) into the conformance/examples/ directory? We recently added a GitHub Action that automatically validates all examples in that folder against the strict schema to ensure they are fully spec-compliant. |
|
Please also update the agent resource identifier schema format from |
Addresses mindpower's two review comments on PR ards-project#6: - Move examples/agentrust-io-catalog.json to conformance/examples/ per spec layout - Replace urn:ai: with urn:air: in all identifier fields (4 entries in catalog + spec example on line 390) The urn:air NID satisfies RFC 8141 minimum 3-character requirement. Signed-off-by: Imran Siddique <imran.siddique@opaque.co>
|
Done -- moved to |
|
Done -- all |
|
This is actual change to the spec. I would prefer that changes to the spec
be first discussed as a github issue.
…On Fri, Jun 19, 2026 at 8:28 PM Junjie Bu ***@***.***> wrote:
*mindpower* left a comment (ards-project/ard-spec#6)
<#6?email_source=notifications&email_token=ABICKCWJLD2G3TWHCWFVFCL5AYAE5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZVGYYTSNJVGE32M4TFMFZW63VQOJSXM2LFO5PXEZLROVSXG5DFMSSWK5TFNZ2LK4DSL5RW63LNMVXHIX3POBSW4X3DNRUWG2Y#issuecomment-4756195517>
@imran-siddique <https://github.com/imran-siddique> Thanks for adding
TRACE-v0.2 runtime governance attestation type and example! Could you
please move your example file(s) into the conformance/examples/ directory?
We recently added a GitHub Action that automatically validates all examples
in that folder against the strict schema to ensure they are fully
spec-compliant.
—
Reply to this email directly, view it on GitHub
<#6?email_source=notifications&email_token=ABICKCWJLD2G3TWHCWFVFCL5AYAE5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZVGYYTSNJVGE32M4TFMFZW63VQOJSXM2LFO5PXEZLROVSXG5DFMSSWK5TFNZ2LK4DSL5RW63LNMVXHIX3POBSW4X3DNRUWG2Y#issuecomment-4756195517>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABICKCUYQGU4KQPNWBEKE3D5AYAE5AVCNFSNUABGKJSXA33TNF2G64TZHMYTENBTG4ZTSMBXGI5US43TOVSTWNBWHA3TGMZTGUYTLILWAI>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
…tations Schema validation (additionalProperties:false) rejects $comment at root. Each attestation object requires type, uri, and mediaType per ai-catalog.schema.json. Signed-off-by: Imran Siddique <imran.siddique@opaque.co>
rvguha
left a comment
rvguha
left a comment
There was a problem hiding this comment.
Changes to the spec should be discussed in the issues first. This is a substantial change to the spec which cannot be accepted without requisite discussion.
|
Thanks for the detailed proposal. We're going to keep the core spec's |
|
@rvguha -- fair point, and noted. I've opened issue #7 to carry the spec-level discussion before anything lands: #7 The PR itself is now narrowed to: (1) the conformance example in Happy to hold the PR open until there's consensus on #7, or to split off the |
3 participants
Summary
This PR adds TRACE-v0.2 (Trust Runtime Attestation and Compliance Evidence) as a runtime governance attestation type in the ARD spec, alongside the existing compliance types (SOC2-Type2, HIPAA-Audit, SPIFFE-X509).
What TRACE is
TRACE is an open EAT-profile (RFC 9711) standard that produces a cryptographically signed record proving an AI agent ran under a specific policy, in a verified hardware environment (TEE: AMD SEV-SNP, Intel TDX, NVIDIA H100 CC), with an auditable tool-call transcript — all in one independently verifiable artifact anchored to silicon attestation.
docs/adr/0032-agt-emits-trace-v01-trust-records.mdChanges
§5.2 Attestation Object —
TRACE-v0.2added to thetypefield examples alongsideSOC2-Type2andHIPAA-Audit.§5.2.1 Runtime Governance Attestations (new section) — explains the distinction between compliance certifications and runtime governance attestations, with:
trustManifest.attestations.type: ["TRACE-v0.2"]urianddigestfields point to for a TRACE recordexamples/agentrust-io-catalog.json— referenceai-catalog.jsonshowing agentrust.io as a governed-agent federated ARD registry. Includes cMCP, Agent Manifest SDK, and TRACE Registry entries, each with SPIFFE-X509 + TRACE-v0.2 attestations.Why it matters for ARDS
The trustManifest already handles what an agent claims about itself (SOC2, HIPAA). TRACE fills the gap for what an agent provably did at runtime — the session evidence, not the certification. These are complementary: a registry can expose both
SOC2-Type2(annual audit) andTRACE-v0.2(per-session hardware proof) on the same entry.The
trustManifest.attestations.typefilter is already designed to support this —["TRACE-v0.2"]works today without any spec changes to the query model.Alignment notes
subjectfield accepts bothspiffe://anddid:URIs, matching thetrustManifest.identityfieldurn:ai:agentrust.io:registry:governed-agents— a specialized federated registry returning only TRACE-attested entriesHappy to iterate on the section placement, wording, or scope. The goal is minimal: one new attestation type in the table, one new section in §5, one reference example.
🤖 Generated with Claude Code