Build a reproducible acceptance harness for confidential workflows across components
维护者通常 1 天内回复
@rajnisht7 已经在做这个了。
开始于 2026年10月20日。
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- Python
- 星标
- 5
- 派生
- 27
- 平均合并
- 1 天 13 小时
- 30 天内合并 PR
- 104
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
agentrust-io/integrations 的其他 Issue
-
难度 5/5 一周以上 新手友好度 20/100
agentrust-io/integrations#333 · 12 条评论 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
agentrust-io/integrations#290 · 1 条评论 ·
维护者通常 1 天内回复
查看 agentrust-io/integrations 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
-
bug
难度 2/5 1-3 小时 新手友好度 77/100
AstrBotDevs/AstrBot#10720 ·
维护者通常 1 天内回复
-
cause/upstream comp/cli P2 provider/other tool/file type/bug
难度 2/5 1-3 小时 新手友好度 78/100
NousResearch/hermes-agent#143900 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 85/100
WLAN-Pi/wlanpi-profiler#341 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 1 天内回复