Carol — back to Apps ← Apps

Carolopedia

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

📖 CarolopediaServicesBuild InitiativesAll activitiesINI-1000754
📋

CAROL-INI-0678-00: Full Carol-architecture checklist as default service template + silent assumption

Initiative
Open in Initiatives →

📖About

Today Gandalf's pre-roadmap checklist is thin (cookbook entry 48): three Value cards + three Architecture cards. Misses entire non-functional dimensions — org structure, org app, WhatsApp tunnel, build pipeline, monitoring, policies, etc.

FIX: codify the full Carol architecture as a structured checklist of components organised by category. Every new service inherits ALL components as DEFAULT=ON. The user is NEVER asked about these — they focus on functional aspects. Gandalf assumes the full Carol architecture by default. Trim only happens if the user is curious and explicitly asks; then Carol surfaces the trim options. Budget forecast reads the checklist; the default budget reflects the full architecture; trimming reduces it.

DELIVERABLES: 1. New table carol_component_catalog with the canonical component list (id, category, name, description, default_cost_usd_per_month, is_core). 2. Seed catalog with Carol's major components across categories: Identity & Auth (WhatsApp tunnel, web chat, Google OAuth), User-facing surfaces (Blueprint, Migration, Initiatives apps), Build infra (build pipeline, planner, dispatcher), Monitoring (Guardian Monitor, Carol Monitor, Azure backups), Governance (constitution, policies, agentbook), Org structure (org app, agents registry, agent identity files), Data layer (registry.db, projects.db, roadmap.db, designs.db), Operations (cookbook apps, scheduled processes app, sst app). 3. New table service_component_checklist (service_id, component_id, included, rationale, decided_by, decided_at). Default state: every component included=1 for every service. 4. Auto-populate the checklist on new-service creation — hook into the new-service registration helper. 5. Add cookbook entry codifying: default-full-architecture, silent-assumption (Carol does NOT ask user; user focuses on functional), trim-only-on-direct-question. 6. Add cookbook entry codifying the taxonomy. 7. Strategy Drafter prompt update: when the user asks an architecture question or about cost, Carol consults the checklist; otherwise she stays silent on it.

SUCCESS CRITERIA: - Catalog table seeded with at least 30 Carol components across ~8 categories. - Checklist table exists. - New service automatically gets all components=included on registration. - Two cookbook entries added. - Sanity test: registering a fake service inserts full checklist; querying shows all=included.

OUT OF SCOPE: chat-side UX for trim conversations, budget forecaster hookup (those are follow-ons).

BUDGET: 45 min.