feat: conform to TRACE v0.2 profile URI - #44
Merged
Conversation
imran-siddique
force-pushed
the
feat/trace-v0.2-profile
branch
from
July 28, 2026 03:53
53dfe9f to
1f7156b
Compare
TR-ENV now requires tag:agentrust-io.com,2026:trace-v0.2 and fails a record carrying the v0.1 identifier. The v0.1 URI named agentrust.io, a domain this project never controlled, which RFC 4151 does not permit for a tag URI. Cutover rather than dual acceptance, deliberately: a conformance suite that passed both identifiers would certify records minted under a domain we do not own, which is the thing being corrected. v0.1 records are checked with the 0.3.x releases, which stay published. Nothing else about the record format changed. Also adds .venv/ to .gitignore. The repo ignored __pycache__ and dist but not virtualenvs, so a local .venv was staged by a `git add -A` in this branch's first attempt. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This was referenced Jul 28, 2026
Merged
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.
First of the downstream cascade from agentrust-io/trace-spec#107. This repo goes first because it is the conformance suite: until it moves, it fails every v0.2 record, and it is what other implementations check themselves against.
What changed
TR-ENVrequirestag:agentrust-io.com,2026:trace-v0.2and fails a record carrying the v0.1 identifier.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.Cutover, not dual acceptance. A conformance suite that passed both identifiers would certify records minted under a domain we do not own, which is precisely the thing being corrected. v0.1 records are checked with the 0.3.x releases of this suite, which stay published.
Nothing else about the record format changed, so a producer migrates with a profile string and a dependency bump to
agentrust-trace0.5.0.Also moved the registry, verifier, and docs hosts off
agentrust.io, including the package author field.Verification
116 passed, 5 xpassed. I checked the fixtures for embedded signatures before editing them, since changing
eat_profilewould invalidate a signature over the record: four fixtures carryeat_profileand none carries an embeddedsignature, so nothing stale was left behind.