Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖About & Usage
About
Carol Initiatives is the central hub for tracking strategic initiatives — the big-picture projects and decisions that shape how Carol's AI ecosystem evolves. Think of it as the organisation's "war room" board: it brings together plans, decisions, and the Build Cookbook (a recipe book of reusable build patterns) in one place, so that leadership and engineering teams can see what's been proposed, what's been approved, and what's in flight.
The app is owned by Elrond, Carol's Head of Engineering, and lives behind authentication — meaning only authorised team members can access it. If you're looking for the broader product roadmap, that has moved to the Carolverse app; Initiatives focuses specifically on the doing side: turning strategic intent into concrete plans and tracking the decisions made along the way.
Usage Patterns
Carol Initiatives comes into play whenever a new strategic effort needs to be formally captured, evaluated, or progressed. For example, when Clara or Leo identifies a priority — say, migrating a service to a new cloud region — someone raises an initiative here. The initiative record holds the rationale, success criteria, related decisions, and links to any cookbook entries that describe how the work should be built.
Day-to-day, agents like Galadriel and Forge reference Initiatives to understand the "why" behind their current work, while Merlin uses it to coordinate execution across teams. It also serves as an audit trail: months later, anyone can revisit an initiative to see what was decided, by whom, and what trade-offs were considered — making it a lightweight decision log as much as a planning tool.
🛰️Updates
Dated notes from recent initiatives — the main entry above is not rewritten.
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.
🗂️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.