factory-resume

To resume a pipeline after an interruption, the system reads the current state and automatically selects the correct phase to continue execution. It handles states like paused or failed, reactivating the appropriate phase from where it left off.

The automatic recovery flow supports idle, running, paused, completed, and failed pipeline states. It determines the current status and schedules the resumption from the identified phase.

Phase-by-phase orchestration maps pipeline phases to specific tasks: BREAK routes to intake, MODEL to spec, PLAN to plan, and BUILD handles pending tasks. It delegates remaining work to developers with clear status updates.

Yes, you can restart a failed build workflow without losing progress. The deterministic recovery flow reads the failed state, selects the correct phase, and continues execution while providing a resumption report.

The best way to handle pending development tasks after a pipeline pause is to trigger the BUILD phase. It manages pending tasks automatically and delegates remaining execution to developers with clear status updates.

Use a deterministic recovery flow for workflow orchestration when you need to guarantee phase consistency after an interruption. It enforces a strict recovery path by reading the current state and reactivating the appropriate phase.