v0.3: let a record name the agent manifest it ran under
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- json, python
- Domain
- documentation, security
Research direction
Read schema/trace-claim.json, schema/trace-token-experimental-v1.json, and schema/trace-claim-v0.3-draft.json, then compare them with Agent Manifest spec §6.3.2 and TRACE §3.1.2. The issue leaves the verification-result and spec-alignment questions open, so the v0.3 shape needs a decision before implementation; done means one agreed manifest representation that satisfies the relevant specs.
Written by the indexing model from the issue text.
Description
A TRACE v0.2 record cannot say which approved agent deployment produced it. schema/trace-claim.json has no manifest field and the top level is additionalProperties: false, so a producer cannot add one. Agent Manifest spec §6.3.2 says TRACE envelopes MUST carry agent_manifest_id and manifest_verification_result, which a v0.2 record cannot satisfy, so the two specs disagree today.
This matters for external receipts too. A PACT receipt or any other authorization receipt can only reach a record through references[], and §3.1.2 says a verifier MUST NOT treat a resolved reference as attested evidence.
Proposal for v0.3: an optional top-level manifest object with id, digest and media_type, covered by the record signature. Two drafts already point this way: ManifestRef in schema/trace-token-experimental-v1.json and runtime.evidence.binds: "manifest-digest" in schema/trace-claim-v0.3-draft.json. One shape should serve both.
Open questions:
- Does the record carry the verification result, or only the reference, leaving appraisal to the verifier?
- Should the Agent Manifest §6.3.2 MUST be relaxed to match whatever v0.3 adopts?
- Dominant language
- Python
- Stars
- 37
- Forks
- 33
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 120
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 · 11 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 2 days 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 2 days 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 2 days 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
-
comp/tools P2 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#142908 · 1 comment ·
-
[oblt-aw][autodoc] Fix malformed headings in new Buildkite docs pagesPossibly taken @github-actions claimed this today. Opendocumentation
Difficulty 1/5 Under an hour Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
[Bug]: fileUploadMatrix.test.ts URL case does a real DNS lookup and fails offlinePossibly taken @r2jaff claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ComposioHQ/composio#5054 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pytorch/tensordict#3286 ·
Maintainers usually reply within 1 day