Steps and activation

Documentation Index

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

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

​

Step → task

Each work step 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

​

Predecessor activation

Steps can declare activates when a specific predecessor task reaches a state (e.g. done). The orchestrator:

1. Waits for the predecessor task to complete
2. Copies relevant artifacts into the successor’s input_files.json
3. Creates or updates the successor task and dispatches to the Bridge

Folder-only manifest rows from predecessors are skipped when cloning inputs to avoid duplicating pipeline links.

​

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 the loaded steps include an activatesOnTaskId for this task. Next: Status & recovery