Skip to content

swarm-pipeline

Use when work flows sequentially through stages where each stage’s output feeds the next. Also use when building content pipelines, data transformations, build/deploy sequences, or any multi-stage processing chain.

ModelSource
opuspack: swarms
Full Reference

Sequential hand-off. Stage N completes → its output becomes Stage N+1’s input. No parallelism between stages — each stage is a gate. A failed stage halts the entire pipeline; never continue past failure. Best for workflows with strict ordering dependencies: ETL, content ingestion, build/deploy chains.


ItemValue
PatternSequential — Stage N output → Stage N+1 input
ParallelismNone between stages
Failure ruleHard halt — fix then resume, never skip
Max retries per stage2× then escalate
State trackingLog artifact after each stage for resumability
Dispatch moderun_in_background: false

I want to…File
See the topology diagram and common pipeline patternsreference/topology-and-patterns.md
Implement stage dispatch, checkpoint validation, and backpressurereference/implementation.md

Usage: Read the reference file matching your current task from the index above. Each file is self-contained with code examples and inline gotchas.


┏━ ⚡ swarm-pipeline ━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ [one-line description of the pipeline being run] ┃ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛