feat(trace): emit the TRACE v0.2 profile URI - #424
Merged
Conversation
TRACE Claims now carry tag:agentrust-io.com,2026:trace-v0.2 and agentrust-trace is pinned to >=0.5. The v0.1 URI named agentrust.io, a domain this project never controlled, which RFC 4151 does not permit for a tag URI. The conformance suite cut over rather than dual-accepting, so a v0.2 verifier rejects a v0.1 claim and producers move with it. Nothing else about the claim format changed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Downstream of agentrust-io/trace-spec#107 and agentrust-io/trace-tests#44.
TRACE Claims now carry
tag:agentrust-io.com,2026:trace-v0.2, andagentrust-tracemoves to>=0.5.The v0.1 URI named
agentrust.io, a domain this project never controlled. RFC 4151 permits a tag URI only where the minting authority controlled the named domain on the stated date, so it was invalid rather than misspelled.The conformance suite cut over rather than dual-accepting, so a v0.2 verifier rejects a v0.1 claim. Producers have to move with it, which is what this does. Nothing else about the claim format changed.
Also moved the schema
$idhost and the remaining doc links offagentrust.io.Verification
893 passed, 8 skipped, against
agentrust-trace0.5.0 installed from PyPI. I checked for JSON fixtures carryingeat_profilewith an embeddedsignaturefirst, since changing the profile would invalidate a signature over the record: there are none in this repo.