pipeline

You can orchestrate an OMX pipeline by sequencing stages like ralplan, team-exec, and ralph-verify. The pipeline coordinates execution and preserves state using a ModeState artifact model to ensure observable progress and safe recovery.

Yes, OMX pipelines support safe resume after failures. The ModeState persistence model tracks stateful progress, enabling the orchestration process to restart automatically from the last incomplete stage without manual overhead.

You configure deterministic operations by adjusting customizable parameters within the pipeline. Autopilot pipelines support configurable settings for max iterations, worker count, and agent type to control execution behavior.

The PipelineStage interface provides a uniform structure for stage-driven execution. It supports built-in stages like ralplan and ralph-verify, and allows you to implement custom stages to extend the end-to-end pipeline.

You run the default OMX pipeline to orchestrate the standard stage sequence end-to-end. This executes the built-in stages automatically, coordinating the workflow and handling state persistence across the entire process.

While stateful orchestration enables safe resume, it requires ModeState persistence to function. You must ensure the pipeline state is properly maintained to guarantee recoverability and deterministic operations across stage executions.