Build a reproducible acceptance harness for confidential workflows across components
Maintainers usually reply within 1 day
@rajnisht7 is already working on this.
Since Oct 20, 2026.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start with the linked parent tracker and its response-binding, confinement, measured-identity, lifecycle, protected-execution and disclosure workstreams; this issue names no implementation files or tests. Map the acceptance criteria into a synthetic workflow first, keeping live hardware evidence and cA2A conformance decisions separate. Done means reproducible machine-readable results cover the specified controls and attacks, while live acceptance remains explicitly unclosed until its dependencies and releases are available.
Written by the indexing model from the issue text.
Description
Parent tracker: https://github.com/agentrust-io/.github/issues/41
Problem and scope
Component tests do not establish that a composed model, agent, tool and delegated peer preserve a selected confidentiality policy.
Provide a reusable acceptance harness with replaceable model, tool, transport, attestation and deployment adapters. Start with a deterministic synthetic workflow; label fresh hardware evidence separately.
Acceptance criteria
- Define assets, principals, permitted recipients, trusted components and the exact claim evaluated by each run.
- Join key provisioning, inference, a mediated tool call, a delegated peer call and response verification using a single bound transaction context.
- Capture independent observations at release, receipt and execution boundaries; keep authorization, delivery, installation and execution outcomes separate.
- Cover workload/key/configuration substitution, software downgrade, replay, missing evidence, bypass egress, forbidden disclosure, revocation and timeout with unknown outcome.
- Pair expected refusals with valid controls and show that removing each tested gate causes its intended test to fail.
- Produce machine-readable results with source revisions, dependency versions, policy/trust inputs, commands and explicit synthetic/replayed/live evidence classification.
- Reproduce a live run across independently operated peers satisfying the selected policy. Sanitized public evidence must not expose protected data or device identifiers.
Dependencies and closure
Consume the response-binding, confinement, measured-identity, lifecycle, protected-execution and disclosure workstreams linked from the parent. agentrust-io/ca2a#47 remains the owner of cA2A hardware conformance and release-assurance decisions. A synthetic harness can complete its software milestone without closing live-hardware acceptance or promoting a component's release claim.
Published integration examples must use released packages, following this repository's contribution rules. Before required APIs are released, keep protocol development in the owning core repositories and mark the integrated milestone as waiting on those releases.
- Dominant language
- Python
- Stars
- 5
- Forks
- 27
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 104
Getting set up
- No Dockerfile or Docker Compose file
- No 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/integrations
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
agentrust-io/integrations#333 · 12 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
agentrust-io/integrations#290 · 1 comment ·
Maintainers usually reply within 1 day
All issues in agentrust-io/integrations
Similar issues
-
difficulty:2 enhancement good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
MakazhanAlpamys/Soup#2178 ·
Maintainers usually reply within 1 day
-
Slang input: int8_t4_packed and uint8_t4_packed are copied into CrossGLPossibly taken @ninglinLiu claimed this today. Openarea:frontend backend:slang bug direction:input
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 13 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kozea/Radicale#2301 · 2 comments ·
Maintainers usually reply within 1 day
-
bug ci good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day