Add delegation and pre-action authorization attributes for agent spans

Aperta
#4,599 5 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Rutvij97 ci sta già lavorando.

Dal 10/11/2026.

  • #4701 di @Rutvij97 — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
7.5k
Fork
1.2k
Merge medio
2g 6h
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di traceloop/openllmetry

Tutte le issue di traceloop/openllmetry

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.