Build a reproducible acceptance harness for confidential workflows across components
Los mantenedores suelen responder en 1 día
@rajnisht7 ya está trabajando en esto.
Desde el 20/10/2026.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 20/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Python
- Estrellas
- 5
- Forks
- 27
- Merge medio
- 1 d 13 h
- PR fusionados (30 d)
- 104
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de agentrust-io/integrations
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
agentrust-io/integrations#333 · 10 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
agentrust-io/integrations#290 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de agentrust-io/integrations
Issues similares
-
comp/tools P2 type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
NousResearch/hermes-agent#142908 · 1 comentario ·
-
[oblt-aw][autodoc] Fix malformed headings in new Buildkite docs pagesPosiblemente ocupada @github-actions la tomó hoy. Abiertodocumentation
Dificultad 1/5 Menos de una hora Aptitud para principiantes 83/100
Los mantenedores suelen responder en 1 día
-
[Bug]: fileUploadMatrix.test.ts URL case does a real DNS lookup and fails offlinePosiblemente ocupada @r2jaff la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
ComposioHQ/composio#5054 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
pytorch/tensordict#3286 ·
Los mantenedores suelen responder en 1 día