Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

🧭Leaders

Audience: Developers and integrators who need the public execution model.

Goal: Understand the public Leader role and the protocol contracts a Leader must satisfy while advancing work.

A Leader is an eligible protocol actor that advances an occurrence or execution under on-chain authority. Protocol state assigns eligible Leaders and constrains each submission by the pinned workflow, Tool, verifier, authorization, and payment state.

Scheduler advertises work for a DAGExecution
Phase 1: Scheduler advertises work for a DAGExecution.
Leader invokes Tool and records verifier evidence
Phase 2: Leader invokes Tool and records verifier evidence.
Accepted result settles the execution payment
Phase 3: Accepted result settles the execution payment.

Public responsibilities

  • Observe eligible work and select an occurrence that protocol state assigns to the Leader.

  • Dispatch or advance the occurrence or execution using the workflow contract and its pinned inputs.

  • Invoke the selected on-chain or off-chain Tool with the required request and authorization context.

  • Submit the Tool result, failure evidence, and configured verifier evidence back to execution.

  • Participate in payment settlement and retain the evidence needed to associate payable work with the execution.

The Leader does not redefine the DAG, replace the selected Tool, choose a different verifier, or bypass the payment state. Those choices are committed by the Agent skill, Task, Tool registry record, and execution state.

Contract interactions

  • Scheduler: exposes eligible Task occurrences and applies timing, funding, and schedule constraints before work can advance.

  • Workflow contracts: own the DAG, walks, worksheets, result objects, and execution transitions that a Leader calls.

  • Tool and verifier configuration: identifies the Tool FQN, schema, timeout, authorization mode, and trust choice the Leader must use.

  • Registries: resolve the Agent, Tool, verifier, Leader, and network-key identities that the execution names.

  • NetworkAuth: supplies the active key binding used when Leader or Tool signatures are required; detailed key rules live in Registered Keys and Signed Tool Communication.

  • Payment state: records the Task reserve, ExecutionPayment, result affordability, and settlement outcome; see Payment Vaults, Reserves, and Settlement.

Evidence boundary

An accepted Tool response is not enough by itself. The Leader’s submission must match the execution’s current walk, selected Tool, verifier mode, and payment state. For on-chain result creation and pending settlement, follow On-Chain Result Resolution. For exact public fields and functions, use the generated Leader reference.

Next

Continue to Registries and Discovery to see how each identity is resolved on chain.

Last updated