ferrox-execute-phase

Parallel phase execution works by grouping plans into dependency-aware waves, allowing isolated subagents to run concurrently. The orchestrator collects results and applies final verification before marking the phase complete.

Dependency-aware workflow orchestration sequences software delivery phases so dependent tasks wait while independent tasks run in parallel waves. This prevents sloppy outputs and keeps complex builds verifiable and safely on track.

Safe staged rollouts use strict backend selection and preserve state updates at checkpoints during wave-based execution. Final verification gates ensure the phase only finishes when work is actually done and verified.

Yes, fleet mode is supported as an explicit backend selection alongside inline, interactive, and wave-filtered modes. It enables parallel wave execution for gap-closing runs with explicit flag handling and routing for subagents.

Use wave-based execution when a phase contains multiple isolated plans that can run concurrently. It prevents sloppy outputs common with a single large pass by orchestrating subagents and enforcing final verification before phase completion.

No, phase execution applies orchestrated verification automatically. It preserves checkpoints and completion gates, collecting subagent results and verifying the phase outcome to ensure work is actually done before shipping.