LumenFlow orchestration is the evidence-based control plane that coordinates multi-WU initiatives across humans, local agents, and compatible remote orchestration surfaces. It separates planning from launch, lets any vendor drive it from the same state contract, and reconciles live state from durable evidence instead of trusting emitted prompts.
Why this is its own feature area
An initiative that spans 5–20 WUs is not just a bigger TODO list. It’s a concurrency problem, an integrity problem, and a capacity problem. LumenFlow treats those concerns as first-class control-plane state — not emergent behavior agents have to figure out on their own.
One state model, many drivers
The same state vocabulary (planned, eligible, handoff_emitted, active, worker_returned, ready_for_finish, awaiting_merge, blocked, contaminated, stalled, needs_relaunch, done) runs locally, through remote control surfaces, and across agent vendors.
Prompt emission is not launch
Orchestrators record durable launch receipts and reconcile from evidence (stamps, worktrees, gate outcomes, delegation registry, signals). A prompt you copy-pasted is documentation; a stamp is truth.
Capacity + integrity are first-class
Cap concurrent workers with --max-active-workers. Main-checkout contamination and stalled
worktrees surface as their own states — the orchestrator refuses to advance instead of silently
piling on.
Logical wave vs launch attempt
Your dependency graph’s “wave 2” is a fact. “The third time you launched wave 2” is also a fact. The artifact bundle tracks both independently so resume, audit, and retry stay unambiguous.