Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.auvy.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Delegation pattern (native tools)

Orchestrator neurons can delegate structured work to worker neurons using write_* native tools. The worker completes the task and returns a typed result via send_back; the parent persists durable state (versioned objects). This is an internal + dashboard contract today. Public SDK exposure for neurons and toolkits is planned separately.

​
Tools and kinds

Parent toolKindPersistence
write_pathwaypathway_editPathway versioned object head
Additional write_* delegation tools may be registered in the same module; kind registrations and tool metadata live in packages/internal/src/core/toolsets/native/delegation.ts. The send_back payload shape is validated against packages/internal/src/core/delegatedToolResult.ts.

​
Worker contract

Workers invoked by a parent must call send_back with:
  • kind — one of the registered delegation kinds
  • summary — human-readable outcome
  • data — optional structured fields (per-kind schema)

​
Pathway context (write_pathway)

For HTTP receptor or neuron invoke, pass neuron_task_options (JSON object) so the API merges it into the job: use pathwayContext when the worker needs pathway graph tools (pathway_id), and optionally trace_type: "system" (or camel traceType) for background runs so durable engrams stay off the default thread listing plane. In-trace delegate_* tools cannot set this—delegated work stays a child of the parent thread. Details: Invoke neuron.

​
Trace UI

Parent write_* tools use traceBlockType: delegation_block so trace chat shows delegate path, task, kind, summary, and version metadata. See the repository doc docs/dev-docs/trace-tool-ui.md (delegation_block).

​
Dashboard types

@auvy-synapse/private-client exports DelegationKind and DelegatedResult for typing job outputs that include send_back in tool results.