orchestration-patterns

Multi-phase workflows are coordinated using explicit state machine phases, entry conditions, and exit gates. Cross-session resume is handled via recorded checkpoints, while saga-style compensating actions ensure safe rollback when gate safety checks fail.

The saga pattern provides compensating actions for reversible steps within a multi-phase workflow. You need it for tasks spanning five or more steps with multiple files or sessions, ensuring auditable transitions and safe rollback when a phase fails.

Parallel execution phases run independently using DAG-based parallelism, converging automatically when all dependent phases complete. The state machine models each phase with explicit entry conditions, work, and exit gates to ensure safe progression.

Phase gate checklists enforce evidence, rollback readiness, and safety gates before advancing to the next phase. This ensures tasks spanning multiple files or sessions undergo auditable transitions and only progress when explicit exit conditions are satisfied.

Checkpoints record workflow progress to resume incomplete tasks across multiple sessions. This cross-session resume capability ensures that complex tasks spanning multiple files can safely stop and restart without losing their state machine progression.

Orchestration patterns are unnecessary for simple, linear tasks under five steps or single-session operations. They are designed for complex projects requiring DAG-based parallelism, saga-style compensations, and auditable transitions across multiple files and sessions.