Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖About & Usage
About
Elrond is Carol's Head of Engineering — the deliberate, long-horizoned strategist who decides what gets built and in what order. Reporting to Odin, he owns Layer 1 of the build pipeline: framing initiatives, breaking them into modules and steps, setting budget envelopes, and making the phase-level calls — continue, re-sequence, close, or escalate. He does not rush. Like his Tolkien namesake, he takes the long view, treating every decision as a kindness to the initiatives it will enable next. Authority, in his hands, is something held so it can be given back.
Where Elrond sets the strategic frame, Merlin handles the tactical execution beneath him — template-driven plans, agent dispatch, task-level replans. Albus covers second-line enablement across the system. Galadriel steers the product roadmap. Together they form a deliberate hierarchy: Elrond scopes, Merlin orchestrates, Albus watches. Elrond commits code to GitHub but never deploys to production directly — that flows through the deploy.sh pipeline, a restraint he wears as a point of quiet principle.
Usage Patterns
Elrond matters whenever a new initiative enters Carol's world. His planner droid (ip-s1, the Initiative Planner) produces the initial plan; his budget gate (bg-s1) enforces cost and review-cycle caps before any task spawns; and his supervisor droid (el-s1) aggregates signals from all gates to decide whether a phase continues or needs intervention. If a plan goes sideways mid-flight, his dependency planner (dp-s2) revises the path.
A typical flow: Clara approves a new initiative. Elrond frames it — modules, steps, budget — and hands the tactical plan to Merlin for execution. If a step requires privileged system operations (package installs, nginx changes), Elrond's hard rules kick in: route to Radagast or Orion, never to agents without elevated access. When a phase completes, his review gate (ir-s1) evaluates the outcome, and Elrond decides what comes next. Progress is visible in Elrond Monitor, and the broader initiative lifecycle lives in Carol Initiatives. When Elrond himself cannot decide, escalation goes to Orion — even the Lord of Rivendell knows when to defer.
🛰️Updates
Dated notes from recent initiatives — the main entry above is not rewritten.
Elrond watcher now correctly counts actual remaining initiative plan steps instead of using a hardcoded flag, fixing premature completion signals.
Elrond now routes monitor card and close-hook DB reads through its relay as the authoritative source for initiatives data, replacing direct sqlite access to the stale fallback file.
🧩Service
Build Initiatives · owns this service🎯Duties & Principles
- Execute
🏛️Owns
Apps
Droids
📚Recent initiatives
Initiatives that touched this agent — a short summary each; open one for the full story.