Skip to main content
Pioneer exposes agent work as typed protocol data. An agent execution has an identity, an actor reference, and an authorization context. When it delegates, the gateway creates an explicit route instead of copying the initiating principal’s full access. See Agent domain and delegation for the data model and admission rules.

Route methods

Route projection

AgentDelegationRouteProjection includes: The projection also carries source and destination execution, capsule, thread, workspace, and gateway ids. Destination identity and execution profile are optional constraints.

Disclosure policy

Disclosure classes are explicit:
resultReturn is none, summary_only, or full_result. A route that allows authored text does not automatically allow a task result. Artifact disclosure refers to already authorized artifact handles, not arbitrary paths or raw files.

Validation

The gateway rejects routes with no actions, duplicate actions, invalid generations, invalid expiry, missing disclosure, cross-workspace or cross-gateway destinations, invalid hop boundaries, or incompatible result-return policy. The graph validator also rejects cycles and excessive edge counts. Route creation is idempotent when the caller supplies an idempotency key. Revoke uses the expected generation so a stale caller cannot overwrite a newer route state. A route is admitted only when it is active, unexpired, and compatible with current authorization and policy generations.

Agent attribution

Agent-authored turns, task runs, and review events carry durable actor references and an immutable presentation snapshot. The snapshot contains the identity id, execution id, source and revision, display name, nickname, avatar revision, and role presentation. Clients should render that snapshot instead of replacing historical authors with the current agent profile. The task and turn APIs expose these fields alongside normal lifecycle state. Combine them with task/tree, task/events, thread/timeline/page, and turn/work/page when rendering a work graph.

Generated schemas

  • /schemas/agent_delegation_route_projection.json
  • /schemas/agent_delegation_route_create_params.json
  • /schemas/agent_delegation_route_list_params.json
  • /schemas/agent_delegation_route_list_response.json
  • /schemas/agent_delegation_route_revoke_params.json
  • /schemas/agent_presentation_snapshot.json
The create and revoke methods return the route projection directly, so they do not have separate response schema files. Action normalization uses NormalizedAgentAction; there is no standalone agent_action.json schema in the current generator.