Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖About & Usage
About
The user-facing planning loop: communicate the plan and roadmap, share estimates, collect the user's inputs, refine, and secure a recorded approval. Isolated by design: Learn is the only block where the plan changes by user input, and it ends with the one artifact that authorises spend — the approval. Nothing executes here; an unapproved plan cannot leave this block.
Where it fits
This is one block of the Blueprint service. The owner and the agents who run it are listed under the team below, and the other blocks of the service are linked at the bottom of this page.
🛠️Team & droids
Leo Block owner
Leo runs the planning conversation: he presents the plan and roadmap in the user's language, shares estimates with their basis, folds the user's inputs back into the records, and closes the block only on a recorded approval.
Obi-Wan carries user acceptance in Learn: his UAT lane verifies the user's sign-off is real and recorded against the roadmap version approved, so execution downstream can refuse an unapproved plan.