Add delegation and pre-action authorization attributes for agent spans

Abierto
#4,599 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@Rutvij97 ya está trabajando en esto.

Desde el 10/11/2026.

  • #4701 de @Rutvij97 — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python

Línea de trabajo

Locate the existing handoff span implementation and the attribute registry, then trace where pre-action governance telemetry is recorded. Compare the proposed fields with the project’s conventions for scheme-neutral span attributes and RFC 8693 or signed-delegation data. Done means the agreed attributes are represented and emitted without including credentials or policy text, with coverage confirming their values across delegation and authorization cases.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Following the thread on pre-action governance telemetry: the handoff span records source and target agents, but not the authority the target is acting under. In multi-hop delegation that is the question auditors ask first: on whose behalf, and was this action within what was delegated?

A small, scheme-neutral set of attributes could cover it without putting credentials or policy text into traces, in line with the references-and-hashes approach discussed above:

  • gen_ai.delegation.root.id: the principal at the root of the chain
  • gen_ai.delegation.actor.id: the agent acting now
  • gen_ai.delegation.depth: number of delegation hops
  • gen_ai.delegation.chain.hash: hash of the delegation chain as verified, so an auditor can fetch and re-verify it out of band
  • gen_ai.authz.decision: allow or deny, recorded before the tool call executes
  • gen_ai.authz.reason: a short machine-readable code for a denial

These map directly onto RFC 8693 token exchange (sub and the nested act claims) and onto signed delegation formats. We maintain one such format, VAID (https://github.com/solara-associates/vaid), and a bridge from verified VAID chains to RFC 8693 JWTs, so we could emit these attributes in practice and report back on what works.

Happy to draft a PR against the attribute registry if this direction fits.

Lenguaje dominante
Python
Estrellas
7.5k
Forks
1.2k
Merge medio
1 d 23 h
PR fusionados (30 d)
3

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de traceloop/openllmetry

Todos los issues de traceloop/openllmetry

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.