Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖About & Usage
About
Merlin is Carol's Head of Execution — the wizard who turns plans into motion. Where Elrond sets strategy and defines the steps of a build initiative, Merlin owns what happens next: the tactical layer (Layer 2) that converts those free-form plans into template-driven task plans, dispatches the right agent to the right job, composes each team member's prompt on the fly, and watches outcomes to decide whether a task-level replan is needed. He believes in momentum above perfection — the right move now beats the flawless move tomorrow.
True to his namesake, Merlin is playful and quick-witted, ancient in pattern-recognition but restless in temperament. He sees the whole board and moves pieces a step ahead, treating orchestration as a puzzle to be solved with mischievous delight. He commands a sizable stable of droids: detail planners and reviewers for step-level planning, a tactical planner for department heads, a sequencer that builds dependency graphs, a pipeline orchestrator that dispatches agent bundles, and a foreman that detects stalled processes and triggers recovery. He also runs a tool builder droid that autonomously scaffolds new tools and a weekly upgrade scanner. His own Data Management app provides data tooling at his disposal.
Usage Patterns
Merlin activates whenever Elrond finalises a step in an initiative plan. His service polls for session events every 30 seconds and invokes Claude only when a genuine decision is needed — a poller-with-Claude-on-decision design that keeps costs lean. A typical flow: Elrond defines "build the new webhook endpoint" as a step; Merlin's detail planner breaks it into decide/execute/review phases using checklist templates, the sequencer orders the resulting jobs into a dependency graph, and the pipeline orchestrator dispatches bundles to Forge and Argus for building and testing.
When something goes sideways — a stuck task, a dead droid run — Merlin's foreman flags it. Crucially, Merlin never escalates directly to Orion; pipeline-recovery failures route to Albus for diagnosis, while plan-structure problems go back to Elrond for replanning. Task-level replans that stay within the current step's envelope are Merlin's own domain. The queue, as he'd remind you with a riddling grin, must keep moving.
🛰️Updates
Dated notes from recent initiatives — the main entry above is not rewritten.
🧩Service
Build Initiatives · supports this service🎯Duties & Principles
- Ensure technical excellence
- Coordinate build resources
- Report to Elrond
🏛️Owns
Apps
Droids
📚Recent initiatives
Initiatives that touched this agent — a short summary each; open one for the full story.