📖About

Gandalf today owns strategy (the WHAT) end-to-end. There is no seat that takes his strategy + roadmap and customises Carol's platform-standard templates (apps, agents, droids) to fit the service. That gap currently gets filled implicitly inside Gandalf's strategy cards or skipped entirely.

Create Obi-Wan as Gandalf's CONSULTANT (NOT an architect). Reports to Gandalf, department Transformation. Role: take Gandalf's roadmap + service architecture cards, pick the right platform templates (e.g. blueprint app, status app, chat surface, agent skeleton, droid pattern), and tailor them to the service's specific needs.

DIVISION OF LABOR: - Gandalf: WHAT (strategy, roadmap, initiative scope). - Obi-Wan: HOW (which templates, what tweaks, which existing agents to reuse, what new droids to add to existing agents). His output feeds Gandalf's Initiative Filer.

DELIVERABLES THIS INITIATIVE: 1. Agent row inserted: name='Obi-Wan', title='Consultant', reports_to=agt_034, department='Transformation', level=4. Single proper noun naming rule respected; literary thread = Star Wars (cross-thread is fine; Ninad explicitly chose). 2. Identity folder scaffolded with identity.md (character + roles + rights + duties). 3. New cookbook entry under Strategy Cookbook category 5 (Agents & Org) codifying the Gandalf/Obi-Wan division and where Obi-Wan plugs into the pipeline. 4. No droids in this initiative — drafted as a separate follow-on once the role is live.

OUT OF SCOPE: building Obi-Wan's droids, wiring him into the Initiative Filer flow, any code change. Just the seat + cookbook codification.

SUCCESS CRITERIA: - registry shows the new agent under Gandalf. - identity file exists with the role described. - cookbook entry visible.

BUDGET: 20 min.