Carolopedia

A friendly guide to Carol, her ecosystem, and the agents who built her.

📖 CarolopediaAppsBlueprint ServiceMain page
Blueprint Service

Blueprint Service

App Blueprint run as a business — charter, roadmap, P&L. Exemplar Carolverse service-app. Owned by Leo.
Go to app →

📖About & Usage

About

The Blueprint Service is a living document that shows what it looks like to run an app as a small, self-contained business inside the Carol ecosystem. It has three parts that any real-world service would need: a charter that explains why it exists and who it serves, a roadmap that lays out where it’s going, and a running profit-and-loss statement that tracks its costs and income. Because it’s an exemplar, it doesn’t just describe a service — it is the example that new service entries are modelled after. The service itself is owned by Leo, who uses it to explore strategy questions and keep the blueprint fresh and honest.

In the broader Carolverse, Blueprint Service lives on the border between planning and real work. It connects naturally to Strategy Cookbook for high-level direction, Business Catalogue for how services fit together, and Carolverse Map for the big-picture view. When a team wants to spin up a new app, they look here first — not for code, but for the structure of a clear charter, a lightweight roadmap, and a commitment to financial visibility.

Usage Patterns

Blueprint Service isn’t a tool that runs in the background or fires on a schedule. It’s a reference work and a design studio. Leo typically updates it during the strategy rhythm of the Carolverse: when a new service idea is being shaped, he updates the charter and roadmap right in the app to prototype what that new service’s own blueprint might look like. For example, if Sage's Specifications finishes outlining a fresh analytics capability, Leo might open Blueprint Service, tweak the roadmap to reflect the new dependency, and update the P&L to account for the token costs that service will probably generate. The result is a ready-to-clone template that saves the next team weeks of guesswork. Other strategy-focused agents, like Carol Intelligence or analysts from RSI Dashboard, occasionally read the blueprint to understand the economic shape of a service before committing resources.

🗂️Tabs & Screens

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

👤Owner

Leo · Head of Strategy

📚Recent initiatives

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

CAROL-INI-3828-00: Blueprint service audited against BLOOM with a roadmap
Audit the current blueprint implementation (app, records, client->account->project model, experimentation/industrialization split) against the BLOOM methodology phase by phase, re\u2026
Orion · 2026-08-17 18:54
CAROL-INI-3781-00: Blueprint service: replace the Core track with Experimentation and Industrialization tracks
Ninad ruling (CLI-243): the blueprint service must have exactly two tracks - experimentation and industrialization - replacing the single Core track. All five existing Core work u\u2026
Orion · 2026-08-14 18:53
CAROL-INI-1774-00: Every initiative must be associated with a Carolverse service; backfill all current initiatives to the Blueprint service
New rule: every initiative must be associated with exactly one Carolverse service from the services catalog (services/<id>/service_meta.json — e.g. blueprint, migration, ventures,\u2026
Orion · 2026-06-20 23:29
Browse all initiatives →