pipeline

To resume a multi-stage workflow after a restart, the pipeline orchestrator persists progress in .omx/state/pipeline-state.json. This allows large-scale automation to reliably restore state and retry failed stages without losing prior execution context.

A PipelineStage interface is a defined contract that automation stages implement to share context and results. It ensures consistent sequencing across multi-stage workflows by reconciling configuration through a unified execution structure.

You can orchestrate an OMX pipeline programmatically by creating an autopilot pipeline configuration. The system applies the default ralplan, team-exec, and ralph-verify stages, running them sequentially to ensure consistent execution.

No specific external dependencies are required to manage state persistence. The pipeline orchestrator handles state internally by writing directly to the .omx/state/pipeline-state.json file, ensuring reliable resumability.

Yes, you can use custom stages by implementing the reusable PipelineStage interface. This allows your custom logic to share context and results with the default ralplan, team-exec, and ralph-verify stages.

The best way to handle consensus planning and team execution is using a resilient pipeline that orchestrates the ralplan and team-exec stages. This ensures reliable retries, state restoration, and consistent sequencing across large-scale workflows.