chore: move docs and catalogs to TRACE v0.2; hold recorded records at v0.1 - #63
Merged
Conversation
… v0.1 Documentation, the ARD catalogs, and the policy manifests move to the v0.2 profile and to agentrust-io.com. Nothing signs those, so the change is free. The recorded trust records do not move. Eleven of them carry a real Ed25519 signature over a payload that includes the profile URI, and the signing keys are deliberately not committed. Rewriting the string while keeping the old signature would produce a record that fails verification: an artifact claiming v0.2 that no v0.2 verifier accepts. These examples exist to demonstrate verifiable evidence, so a record that does not verify is a worse outcome than one that is honestly a version behind. The three unsigned trust records were held back with them so the recorded corpus stays internally consistent rather than half-migrated. TRACE-VERSION-NOTE.md explains the split and how to regenerate. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…record industrial-embodied-ai/policy/manifest.json and catalog.json are not signed themselves, but their SHA-256 digests are recorded inside the signed trust record as cmcp_policy_bundle_hash and the catalog hash. Editing a byte of either breaks the evidence chain, which validate_artifacts.py caught: assert expected["cmcp_policy_bundle_hash"] == policy_hash Same hazard as the signed records, one level removed: unsigned content whose digest lives inside something signed. Reverted both and recorded the reason in the note, since it is the kind of coupling that is invisible until CI fails. 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, with a deliberate split.
What moved
Documentation, the ARD catalogs, and the policy manifests now carry
tag:agentrust-io.com,2026:trace-v0.2and referenceagentrust-io.com. Nothing signs those, so the change is free.That sweep also caught two things beyond the profile string:
spiffe://trust.agentrust.io/...trust domains in the ARD docs, which are an identity namespace rather than a link, and bare prose references toagentrust.ioas the organisation's domain.What did not move, and why
The recorded trust records stay on v0.1. Eleven carry a real Ed25519 signature over a payload that includes the profile URI, and the signing keys are deliberately not committed.
Rewriting the string while keeping the old signature would produce a record that fails verification: an artifact claiming v0.2 that no v0.2 verifier accepts. These examples exist to demonstrate verifiable evidence. A record that does not verify is a worse outcome than one that is honestly a version behind.
Three further records carry no signature (
healthcare/{sg-moh,uk-nhs,us-fda-samd}) and would have been safe to edit. I held them back anyway so the recorded corpus stays internally consistent rather than half-migrated.TRACE-VERSION-NOTE.mdexplains the split, and how to regenerate: re-run the examples against the current stack and the new records will carry v0.2 with a signature that covers it. Until then they remain verifiable withagentrust-trace-tests0.3.x.Note for demos
demos/web-console/vendor/examplesis a submodule pointing here, so this repo owns those records; demos itself has no tracked references and needs no change. Its submodule pointer will pick this up on the next bump.