Nine conformance vectors cannot be reissued by any key in the repository
Maintainers usually reply within 1 day
@lywinged is already working on this.
Since Sep 7, 2026.
Assessment
This issue has not been assessed yet.
Description
What is wrong
Nine of the thirty action-receipt conformance vectors cannot be regenerated by anything in this repository. gen_rule_coverage_vectors.py records why in its own first paragraph: “The 01-09 fixtures pin a key whose private half is not published, so everything here pins its own deterministic test key.” The generator covers 10-30.
Until #171 they also passed the reproduction check, because that check copied the committed fixtures into its work directory before running the generator, so 01-09 were compared against copies of themselves and agreed every time. #171 empties the directory first and names the nine, with the reason, in NOT_GENERATED.
Spec section or file
examples/action-receipts/conformance/01-valid-controller-accepted.json through 09-unsupported-physical-completion.json, and examples/action-receipts/conformance/gen_rule_coverage_vectors.py.
Expected behavior
Every conformance vector reproducible from a key whose private half lives in the repository, which is the pattern gen_rule_coverage_vectors.py already uses for 10-30. Applied to 01-09, NOT_GENERATED empties and the reproduction guard needs no exemptions at all.
Impact
None on conformant implementations today. The nine are read on every run by tests/test_action_receipt_fixtures.py, which globs the whole directory and puts each vector through the verifier, signature included. They are verified; they are only unreproducible.
The cost is deferred rather than absent. A vector nobody can reissue has to be hand-edited every time the spec moves under it, and the first release that revises this corpus instead of adding to it turns all nine into hand edits at once, which is the class of silent divergence #171 exists to catch. #66 and #173 are building that release.
I have deliberately not touched them: reissuing changes pinned key material in vectors other implementations may pin, so the timing belongs to whichever release already touches these files. I am happy to do the mechanical work on request.
Related: #171, #66, #173
- Dominant language
- Python
- Stars
- 37
- Forks
- 33
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 122
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from agentrust-io/trace-spec
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
agentrust-io/trace-spec#593 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs-review:HIGH
Difficulty 5/5 Over a week Newbie friendliness 20/100
agentrust-io/trace-spec#591 · 4 comments ·
Maintainers usually reply within 1 day
-
prototype(manifest_requirements): resolve accepted_methods without duplicating bindings and reject unconfigured binding endpoints with ProfileErrorPossibly taken @drk-ram claimed this 1 day ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 78/100
agentrust-io/trace-spec#580 ·
Maintainers usually reply within 1 day
-
feat(delegation): add parent_record_hash, verify_delegation_link, and verify_delegation_chain to agentrust_tracePossibly taken @drk-ram claimed this 1 day ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 58/100
agentrust-io/trace-spec#581 ·
Maintainers usually reply within 1 day
-
revocation,trust-record-verify: implement es256 and es384 bundle verification and add EC revocation vectors (#448 items 1, 10)Possibly taken @drk-ram claimed this 1 day ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 52/100
agentrust-io/trace-spec#584 ·
Maintainers usually reply within 1 day
All issues in agentrust-io/trace-spec
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
521xueweihan/HelloGitHub#4063 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Vanilla-OS/apx-gui#112 ·
-
Devstral and Voxtral: section 5 fails in us-east-1 with 400 "Model does not support audio modality"Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
aws-samples/sample-per-model-bedrock#409 ·
Maintainers usually reply within 1 day
-
DuckDB 2.0 breaks to_pyarrow_batchesPossibly taken @DG47 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ibis-project/ibis#12196 ·
Maintainers usually reply within 1 day