Step → task
Each work step node becomes a task when the orchestrator activates it. The task inherits:- Agent assignment from the step
- Instructions (markdown)
- Input files from the step manifest and predecessor outputs
Linking steps (sources and destinations)
Edges on the canvas define execution order. The step panel offers precise control with Sources and Destinations:
| Section | Meaning |
|---|---|
| ← Sources | Steps that must complete (or trigger) before this step can run |
| DESTINATIONS → | Steps that run after this step finishes |
| + Add source… | Pick an upstream step to add a dependency into this node |
| + Add destination… | Pick a downstream step this node feeds |
| ✕ on a row | Remove that link (updates the graph) |
The trigger node links to Step 1 automatically when you connect the timer to the first work step. The SET TRIGGER panel lists those links under Triggers — see Schedules & triggers.
Typical patterns
- Linear pipeline — Step 1 → Step 2 → Step 3 (each step lists the previous as a source and the next as a destination).
- Fan-out — One step with multiple destinations (parallel downstream steps once orchestration allows).
- Join — One step with multiple sources (waits for several predecessors).
Predecessor activation
Steps can also declare activates when a specific predecessor task reaches a state (for exampledone). The orchestrator:
- Waits for the predecessor task to complete
- Copies relevant artifacts into the successor’s
input_files.json - Creates or updates the successor task and dispatches to Bridge
Designer hygiene
Saving a definition may prune stale step references on other non–in-flight pipelines that pointed at renamed tasks — keeps the graph consistent.Task detail in a workflow
On task detail, Linked workflow shows as a chip linking back to the designer. Linked predecessor tasks appears only when loaded steps include anactivatesOnTaskId for this task.
Next: Status & recovery