Carolopedia

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

๐Ÿ“– Carolopedia โ€บ Droids โ€บ Carol Intent DrafterMain page
โ€ฆ

Carol Intent Drafter

Droid Generates Carol's WhatsApp and web chat replies via LLM. The hot-path droid that drafts every user-facing response in Carol's voice, incorporating system prompt, conversation history, tool results, and service routing context.
Go to droid โ†’

๐Ÿ“–About & Usage

About

PA-C0 is Carol's voice. Every WhatsApp message and web-chat reply that Carol sends passes through this droid. It takes the full conversation context โ€” system prompt, chat history, tool results, and service routing โ€” and generates a natural, warm reply in Carol's tone.

How it works

1. Builds the prompt โ€” assembles conversation history, user message, and any attachment context into a structured LLM prompt 2. Calls the LLM โ€” sends the prompt through the active provider (currently DeepSeek) with Carol's system prompt 3. Handles failures โ€” if the primary LLM fails, falls back to OpenAI for a degraded but still-useful response 4. Parses and returns โ€” cleans the response and returns it to the caller (agent_loop.py)

Where it fits

PA-C0 is droid #1 in Carol's reply pipeline. It runs synchronously in the hot path โ€” the user is waiting while it works. It does NOT decide what to say (that's PA-C12's routing job) or whether to say it (that's QG-01's quality gate). It just drafts the words.

| Upstream | Downstream | |---|---| | agent_loop (orchestration) | PA-C11 (reviewer, decommissioned โ€” pass-through) | | PA-C12 (service router) | QG-01 (quality guard, strips artifacts before send) |

Owner

Carol (agt_008) โ€” Sales agent, Carolverse OS's WhatsApp and web presence.

๐Ÿ‘คOwner

Carol ยท Sales Agent โ€” EU

๐Ÿ“šRecent initiatives

Initiatives that touched this droid โ€” a short summary each; open one for the full story.

CAROL-INI-3679-00: Carol's WhatsApp is pinned to Codex and declared Codex, and still resolves to DeepSeek
FOUND AT THE END OF CAROL-INI-3678 (CLI-226), while proving that a per-droid pin still outranks a track declaration. It could not be proved, because the pins do not do what they s\u2026
Orion · 2026-08-06 18:51
Browse all initiatives →