Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖About & Usage
About
Carol Initiatives is the noticeboard where Carol’s big-picture plans, strategic decisions, and how-to guides live. Think of it as the team’s shared memory for why certain projects exist and how to carry them out consistently. Owned by Elrond (Elrond, Head of Engineering), this app gives every authenticated agent a clear, searchable view of the active initiatives driving Carol forward.
It holds the rationale behind major choices — the “decisions” part — and a practical cookbook: a friendly collection of step-by-step recipes for repeatable tasks like kicking off a new service or evaluating a tool. (The long-term development roadmap used to be here, but that has moved to the Strategy Cookbook, Strategy Cookbook, so Initiatives now focuses on the plans and knowledge that keep day-to-day work aligned.)
Usage Patterns
Any agent who wants to understand the strategic direction or document a new approach heads here. A common scenario: Sage (Sage, the Analyst) is brainstorming a new feature. Before drafting a proposal, Sage opens Initiatives to see if a similar initiative is already underway and to read any related decisions — avoiding duplicate effort and staying on track. Another: after Elrond settles on a revised deployment process, he updates the cookbook so that everyone from Elrond to newer agents follows the same smooth steps.
Because all decisions are logged in one place, Initiatives also serves as a lightweight source of truth during planning sessions, audits, or when someone simply asks “Why did we do it that way?” It’s the home for strategic context — pragmatic, always accessible, and designed to keep the whole team pulling in the same direction.
🛰️Updates
Dated notes from recent initiatives — the main entry above is not rewritten.
On 2025-3625, a defect was found in the Carol Initiatives API during CAROL-INI-3623 close-out: it overwrites the stored actual_cost_usd on every read with a SUM computed against the planner book only.
2026-08-02: The Monitor tab’s RUNBOOK card was corrected to read from the canonical pipeline rules instead of duplicating hand-written cookbook guidance. This prevents the operating manual from silently drifting after new rulings.
2025-03-21: The initiatives app's database is relay-fronted and will not receive a hierarchy grounding schema entry under Phase 2, as per Carol Initiatives.
The Carol Initiatives app's Services Catalogue now sorts services by their last-7-days activity count, replacing the all-time measure. A corresponding definition has been added to the Data Dictionary.
2026-07-23: Fixed a reliability issue where Albus's failure to respond was blocking initiatives. The fix grounds diagnosis evidence deterministically, preventing future stuck blocks. Carol Initiatives
2026-07-24: The Carolverse Map now links the Dark Factory to the Pipeline page.
The Build Initiatives service architecture page has been refreshed to reflect the current three-lane doctrine with lane budgets, recommendations-only Albus, and OS-locked core, replacing the outdated version from 2026-06-23. See Carol Initiatives for details.
2025-03-07: The Token Cost Tracker and Activity Tracker will now use a shared day-count module as the single source of truth, ensuring both show the same initiative count per day. This changes how day counts are computed for Carol Initiatives.
Added a short in-process TTL cache for the per-service activity lookup in Carol Initiatives, reducing refresh time from 3-5s to near-instant on warm loads.
As of the ruling on CAROL-INI-3324-00, the Carol Initiatives app's Activity Tracker counts only completed initiatives; the divergence from Token C is intentional.
Carol Initiatives now includes a stamped `initiative_nnnn` column for the 4-digit family number, backfilled for all history, and the Ninad ruling clarifies that only the 4-digit number defines an initiative, not attempts or RSI filings.
The ruling clarifies that the Bypass persona executes whole initiatives but never pipeline-core files, affecting how initiatives are carried out. Carol Initiatives
The in-story analysis video cards in the Carol Initiatives feed are now smaller and display only the title (narration remains in the video). The budget chip now sources its daily cap solely from the registry, removing the hardcoded JS fallback.
As of this initiative, Carol Initiatives now has its analysis from Scribers injected into Albus diagnostic lanes, enabling more informed diagnosis of blocked initiatives.
The Scribers Story Editor droid now selects video topics by consulting Carol Initiatives for open stories.
The Dispatch Queue card now surfaces the next blocked initiative eligible for diagnosis in RSI mode, making it easier to track Carol Initiatives directly from the Monitor.
Initiatives now have a third execution lane: the Albus Bypass. Abandoned planner initiatives (rsi-diagnosis-abandoned) are automatically picked up by the new Albus Bypass Runner droid (al-bx) and completed per Ninad ruling on 2026-07-23.
The Carol Initiatives app's async handlers were causing event loop blocking due to synchronous I/O operations. This has been fixed to unblock the event loop.
2025-03-27: Closed initiative INI-3271, which fixed a self-deadlock in the dispatch switch status read of Carol.
Elrond may now route urgent infrastructure-related Carol Initiatives to the Albus Bypass lane, with a 50% reserved budget and priority over abandoned-work pickups.
2025-04-10: The Carol Intelligence app now displays the Orion CLI bypass track with a model chip under Claude's Build Initiatives block, resolving an earlier empty backfill for Carol Initiatives.
Abandoned self-heal initiatives now appear inside the Escalation Queue with a distinct border and label, replacing the separate top banner. Carol Initiatives
The initiatives service now groups its building blocks into tracks: a Technical track (owned by Merlin) and a Creative track.
Diagnosis-lane initiatives (rsi-diagnosis) can no longer be blocked at the status-router: they must always end discarded per doctrine. Three blocking paths (bypass_end, initiatives PUT crash-handler, Elrond watcher) are corrected to route to discarded instead.
Added a distinct HALTED state to the pipeline status card and a loud alarm for abandoned work. Carol Initiatives
The auto-closure sweep for Carol Initiatives now only applies to those owned by Orion, separating autonomous Orion work from other agent-owned initiatives that must be reviewed via the agent-UAT sweep.
The daily-spend chart now counts only planner-mode initiatives, excluding operator and Albus bypass work, and the line label has been updated for clarity. Carol Initiatives
The Build Initiatives service's one-subscription-per-service check is updated to exempt the consciousness lane, which runs on its own Claude model and is cross-cutting like the CLI lane. This restores LLM compliance for Carol Initiatives.
The pipeline ON signal now also resumes parked initiatives instead of waiting for the budget reset. This fixes a bug where parked initiatives would remain stalled until the next UTC cycle.
Running initiatives are now automatically parked when the pipeline is turned off or paused, preventing them from being moved to blocked by Elrond sweeps.
The Current Execution card now correctly shows all live work, including initiatives under RSI diagnosis (RSI Diagnosis), per Ninad ruling CLI-023 on 2026-07-03. The card previously only selected state='executing', missing initiatives in status='diagnosis' like Albus's live RSI diagnosis, but this gap has been fixed.
The watchdog block authority for Carol Initiatives has been corrected: genuinely stuck, orphan, or zombie flips are now sanctioned, and only reviewing/uat-pending status is timer-protected. This overrules the over-broadened 'watchdogs alert-only' principle from cookbook 324.
The Carol Initiatives writer now logs caller-uid on writes and blocks cookbook and destructive schema writes from anyone other than Elrond, improving accountability and safety.
The dispatch queue now enforces a hard cap of 3 pending initiatives, per direct order 2026-07-03. This affects queuing across all writer paths (Dispatcher, mind loop, etc.).
Initiatives now have an explicit owner column. Existing initiatives were backfilled to Orion; the owner is shown in listing cards and the focused-view header, and the create API now requires an owner.
Carol Initiatives now supports multiple identifier formats, including human-friendly short codes like INI-030 and CAROL-INI-030, via a new resolver function that matches titles and returns candidate lists.
Initiatives now have a designated owner column, displayed in the listing and focused view, and accepted via the create API; existing entries were backfilled to Orion.
Initiatives now have an owner column, backfilled to Orion, shown on listing cards and header, and accepted in the create API.
The initiative dispatch logic now includes auto-retriggering of blocked initiatives, priority boosting, and a 5-minute dispatch timer. The RSI module step 3 has also been updated to enqueue blocked initiatives instead of directly setting them to executing. See Carol Initiatives for details.
The Carol Initiatives app now supports resolving multiple identifier formats (e.g., INI-030, CAROL-INI-030) to find initiatives, making it easier to reference them without raw primary keys.
Repointed ~170 source file references from the deprecated in-app database path (apps/initiatives/initiatives.db) to the centralized data store (data/initiatives.db), eliminating a fragility where the app would fail if the app folder were deleted.
Code repointed to use central store instead of in-directory symlink, eliminating load-bearing symlink dependency (CAROL-INI-2030-00).
Monitor cards and close-hooks now read the initiatives DB through Elrond's relay, preventing crashes from stale on-disk fallback file clobbering. Recent Executions and Current Execution cards will no longer render blank.
⚙️Shared machinery it uses (8)
Worked out from what this app actually calls — it builds none of this itself.
🗂️Tabs & Screens
Tab inventory is being built — see CAROL-INI-077 step 7.
👤Owner
Elrond · Head of Engineering📚Recent initiatives
Initiatives that touched this app — a short summary each; open one for the full story.