📖About & Usage

About

Carol's Planner is the governance engine that turns a request into a structured, actionable plan. When someone in Carol's ecosystem needs something done — a new app built, a policy updated, infrastructure migrated — this is the app that figures out how it should happen, step by step, while making sure nothing important gets missed.

It works by applying a series of governance checklists, labelled A through H, that cover everything from feasibility and design through testing, deployment, and post-launch review. Think of it as a project-planning assistant that already knows the organisation's rules. The app is owned by Merlin, who oversees execution across Carol's agent workforce, and it sits within the governance group of tools — alongside apps like Carol Constitution and Carol Policies — that keep Carol's operations structured and accountable.

Usage Patterns

Carol's Planner typically fires when a new [[initiatives|initiative]] is approved or a significant change request comes in. For example, if Elrond decides a new microservice needs building, the planner generates a plan that includes the relevant checklist steps: a feasibility check (Checklist A), a design phase (Checklist B), implementation, testing with Argus, deployment sign-off, and so on. Each checklist item maps to a real task that an agent or team picks up.

The app is accessible at its dedicated URL behind authentication — it is not public-facing — and is used primarily by agents in leadership or execution roles. Plans generated here feed into tools like Activity Tracker and Hermione Monitor, giving Hermione and others visibility into whether work is progressing as governed. In short: if Carol's Constitution says what the rules are, Carol's Planner says what to do about them.

🗂️Tabs & Screens

Tab inventory is being built — see CAROL-INI-077 step 7.

👤Owner

📚Recent initiatives

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