Elrond Block owner

Before any step work begins, the whole initiative needs an initial plan, and Elrond owns that first planning pass. The Initiative Planner reads new initiatives marked planned with no plan yet and automatically produces the structured skeleton — modules, phases, plan steps and success criteria — links the plan steps to roadmap references, flips the initiative status from planned to active, alerts Merlin that the initiative is ready for task-level planning, and escalates to Orion if it gets stuck. The Author droid performs Elrond's authoring execute-phases for planning (constitution text, the plan compile, the dependency map, and so on), compiling the planning artifact the rest of the flow consumes. This matters because without an initial whole-initiative plan there are no phases or steps for the execution layer to break down and dispatch — the initiative would sit inert in planned status. It fires right after filing, on initiatives that are planned but unplanned, and hands off to Merlin's per-step planning once the skeleton exists and the status has flipped to active. The escalate-to-Orion path covers the case where the planner can't produce a coherent plan on its own.