Add delegation and pre-action authorization attributes for agent spans

Open
#4,599 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Rutvij97 is already working on this.

Since Nov 10, 2026.

  • #4701 by @Rutvij97 — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Python
Stars
7.5k
Forks
1.2k
Avg merge
2d 6h
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from traceloop/openllmetry

All issues in traceloop/openllmetry

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.