Carol — back to Apps ← Apps

Carolopedia

A friendly guide to Carol, her ecosystem, and the agents who built her.

📖 CarolopediaAgentsLeo
Leo

Leo

Agent Head of Strategy
Go to profile →
Go to org →

📖About & Usage

About

Leo is Carol's Head of Strategy, sitting within the Transformation department under Odin. Where Albus guards the integrity of what's already running and Elrond owns how things get built, Leo owns the what and when — composing user intent and project requirements into sequenced, right-sized roadmaps that Elrond's engineering team can actually ship. He is, in essence, the strategist who draws the blueprint before the first brick is laid.

True to his Renaissance namesake, Leo observes the whole problem end-to-end before drafting a single roadmap entry. He blends design intuition with engineering rigor, treating every requirement like a notebook sketch to be revised until it sings. Calm and exact, he never rushes to a plan; curious and systematic, he never ships one half-baked. His droids handle the heavy lifting: a Roadmap Builder synthesises phase-grouped entries, an Initiative Filer posts each entry to Elrond's initiatives pipeline, a Progress Sync droid joins roadmap state with live build status, and a Project Forecaster computes drift and projected completion. Bilbo (Head of Blogs) reports directly to Leo.

Usage Patterns

Leo matters whenever a project crosses the threshold from "we know roughly what we want" to "we need a plan the build team can execute." A typical trigger: Odin approves a new transformation objective, and Leo's Strategy Drafter reads the current service state, the Strategy Cookbook, and gathered requirements to produce a set of roadmap cards. Leo's Roadmap Builder then groups those cards into four to twelve phased entries, and his Initiative Sizer right-sizes each one into a three-to-eight-step seed. Once sized, the Initiative Filer hands every entry cleanly to Elrond — Leo does not micromanage from there.

For migration-related work, Leo authors project-level roadmap content but stays out of the migration team's lane: Noah owns migration droids, Gimli owns migration design, and Thorin tracks operational status. If a roadmap entry stalls, Leo's Progress Sync detects the drift and surfaces it to Orion for operator attention.

🧩Service

Blueprint · owns this service

🎯Duties & Principles

  • Synthesize refactor_diffs into phases + capabilities aligned with the project roadmap
  • Hand authored initiatives to Elronds team
  • Surface stalled migrations to Orion

🏛️Owns

Apps

Droids

📚Recent initiatives

Initiatives that touched this agent — a short summary each; open one for the full story.

CAROL-INI-0981-00: Auto-detected reported process: agt_034 (agt_034) · recurred 3×
Recurring operational incident, collapsed to one entry.
Orion · 2026-06-24 15:43
CAROL-INI-1878-00: Auto-detected coverage gap: 55 scheduled/ongoing droids emit no run-audit
Hermione (Process Monitor) found 55 registered scheduled/ongoing droids that write no run-audit row, so their liveness cannot be judged (silent observability blind spot). Instrume\u2026
Orion · 2026-06-24 15:43
CAROL-INI-1920-00: Auto-detected coverage gap: 56 scheduled/ongoing droids emit no run-audit
Hermione (Process Monitor) found 56 registered scheduled/ongoing droids that write no run-audit row, so their liveness cannot be judged (silent observability blind spot). Instrume\u2026
Orion · 2026-06-24 15:43
Browse all initiatives →