You define — he delivers
Elrond owns the *what* and *why* of every initiative — decomposing it into steps and modules, setting success criteria, building the strategic map. He does not build. Merlin sequences the work; Forge writes code; Argus proves it works. Yet Elrond watches every outcome, reviews it against the criteria, and decides: advance, close, or escalate. This separation is not delegation — it is distributed accountability. Leaders who own only the decision gate, not the work itself, keep teams fast and strategies coherent.
a test reveals the approach won't scale, a dependency fails differently — Elrond does not patch the work or freeze the team waiting for a new plan. He rewrites the map: re-sequencing steps, swapping phases, adapting the strategic thread to the new reality. This is leadership in uncertainty. If the plan owner disappears when things change, teams drift into chaos. If they micromanage the fix, they become a bottleneck again. Adaptive ownership means staying coherent on the destination (success criteria must hold) while ruthlessly flexing the path — and doing it fast enough that the team never stalls waiting for direction.
When a step finishes, Merlin signals Elrond. Elrond reviews the outcome: does it meet the success criteria? If yes, advance. If no, close or escalate. He *never* reruns the task — that is Merlin's domain. Elrond is a strategic owner, not a tech lead. This distinction sounds small but it is a governance gate. If leaders rerun tasks, they become bottlenecks and teams learn to wait. If they don't review outcomes, there is no accountability for what matters. The pattern — review, decide, never execute — keeps roles clear and systems trustworthy.
a dependency breaks differently than expected, a test reveals hidden complexity — the plan changes fast, but the success criteria do not. Elrond reviews outcomes against the bar, not against the original plan. In systems where you cannot fully control the path (because agents are autonomous and reality is uncertain), you must own the destination. Success criteria are the contract. They tell Forge and Argus what 'done' means, they anchor Elrond's reviews, and they let the team innovate the path without losing coherence.
