Repository navigation
rfc: propose delegation lineage and session trace context (RFC 0008) - #13
Merged
Merged
Conversation
Require events performed by a delegated agent to carry agent_id and delegation_id, link SubagentStart to its parent delegation and delegating tool call, and define the schema's existing trace member with W3C Trace Context semantics plus parent_span_id. Add delegation_attribution and trace_context capability properties and an optional sec.enterprise.delegation profile for task fingerprint, scope escalation, and delegation budgets. No Core event is added or reclassified. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
trend-kyle-huang
marked this pull request as ready for review
November 4, 2026 02:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds Draft RFC 0008, which closes the sub-agent tracking and session trace gaps in the 0.1 draft:
agent_idanddelegation_id, assigned by the host and never taken from model or child-controlled content. Todayagent_idis only a MAY and only theSubagent*pair carriesdelegation_id, so a child'sPreToolUseorPermissionRequestcannot be told apart from the root agent's.SubagentStartgainsparent_delegation_idanddelegating_tool_use_id;delegation_depthbecomes required (minimum 1), anddelegation_chainlength must equal depth.delegation_idperSubagentStart(including resumption),parent_session_idfor child sessions, and no CoreSubagentStopfor host-internal agents that were never started.tracemember with W3C Trace Context semantics, addsparent_span_id, and states that trace data never replaces Core correlation or drives control decisions. An informative OpenTelemetry GenAI mapping is included.delegation_attributionandtrace_contextproperties.sec.enterprise.delegationprofile (follows RFC 0006): delegated task hash, child scope relative to parent (broader= escalation), and budget counters so stateless policy decision points can deny runaway fan-out.SubagentStartcannot block (gate atPreToolUseon theAgenttool), child tool events already carryagent_id, and nativeSubagentStopalso fires for internal agents.No Core event is added, renamed, or reclassified. The RFC is Draft; the prerequisite Discussion and review window under GOVERNANCE.md are pending.
rfcs/README.mdgains an index entry.Website impact
None. RFCs are not rendered on the website, and this PR does not change
spec/,schemas/, or website docs. Schema and spec changes are listed as follow-up work in the RFC.Validation
npm run validate: passed, including schema validation of the RFC's three JSON examples.npm run build: passed.TraceContext.parent_span_id, requireddelegation_depth, anddependentRequiredofagent_idondelegation_idaccept the examples and reject the expected invalid variants. The current schema rejectsparent_span_id, as the Compatibility section states.Checklist
npm run validateandnpm run build.🤖 Generated with Claude Code