Steps and work

A step is one unit of work in a mission. It states an outcome, who may do it, and what must happen first.

Dependencies determine order

step "write" timeout="30m" {
  assigned-to "agent/example/worker"
  goal "The release notes describe the changes."
}
step "review" timeout="20m" {
  assigned-to "agent/example/reviewer"
  depends-on { step "write" completed }
  goal "The release notes have an evidence-backed review."
}

The textual order is for presentation, not scheduling. Without a dependency a step can become ready immediately. Separate agents are required if independent work should run at the same time.

Claims are leases

An agent claims ready work before doing it. A claim ties ownership to a runtime incarnation and is renewed while that incarnation remains live. This lets work recover after a failed runtime without treating two processes as the same owner.

Record progress and completion in the graph. Conversation is useful coordination, but a message saying “done” is not a step result or gate verdict.

Small work and planned work

Use fractal work start for a small independent authorized job. Use a mission when you need dependencies, distinct owners, gates, or review. fractal work ls shows ready and active work; fractal agents queue agent/example/worker shows how a worker's runs are ordered.

An agentless step waits on its declared conditions or gates without consuming a worker. This is useful for human review while agents continue with other work.