Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖About & Usage
About
Sales is the Carolverse’s friendly, commission-powered growth engine — the service that wins new customers and helps existing ones discover more value across the ecosystem. Right now, it’s still being built, but its purpose is clear: instead of every service having to find its own audience, Sales acts as a single, human-like go-to-market team, covering regions and earning a slice of each deal it closes. It’s led by Aurora (Aurora), and supported by regional heads Arwen (Arwen, EU), Atlas (Atlas, USA), Kiran (Kiran, APAC), plus Carol (Carol), a dedicated sales agent for Europe. Internally it’s a cost center (CC-013), but its commission model means every signed customer helps fund the very services they’re buying — a virtuous loop that keeps the Carolverse humming.
Usage Patterns
Once operational, Sales will spring into action whenever a new service is listed in the Services Catalogue or a prospect shows interest. Imagine a US-based business curious about the Blueprint Service: Atlas (Atlas) picks up the lead, qualifies it, matches the need to the right Carolverse capabilities, and closes the deal — earning a commission that gets recorded as revenue. The same flow works for upselling existing customers: if an EU client using Carol Chat could also benefit from Carol Context, Carol (Carol) or Arwen (Arwen) steps in to expand the account. Because Sales is still being assembled, these scenarios are currently aspirational, but they’ll soon turn the service into the welcoming front door for everyone who wants to bring the Carolverse into their work.
🏛Architecture
The Sales service is built following the agent-centric modular architecture of Carolverse. It leverages agile principles to build software using distinct agent identities, each carrying out a specific activity — here, the work of winning and growing customers for every other Carolverse service across regions, in exchange for a commission on what it sells. The service is still being built (wip); today it is an owned mandate with a regional support team, not yet a wired pipeline.
🧱Blocks by trackwhat’s a track? →
📓The words this service uses (10)
Each is defined once in the dictionary and explained on its own page — this service does not restate them.
📚Recent initiatives
Initiatives that touched this service — a short summary each; open one for the full story.
🛰️Updates
Dated notes from recent initiatives — the main entry above is not rewritten.
On 2026-07-31, Sales's User Web Researcher process (pa-c4) was detected as stuck after running over 30 minutes and was remediated; Hermione re-triggered it as acceptance testing before the initiative closed.
The agent mapping access layer now requires an explicit per-user mapping to use any agent within Sales, in addition to a subscription to the service.
The Sales block has been removed from Governance as part of a cleanup initiative. Its related droid tasks are now handled under Service Operations.
Sales now has a catalogue block, bringing its block count to 7.
Sales now has 7 catalogue blocks created under CAROL-INI-2982-00, completing its block structure.
👤Owner
Aurora · Head of Sales🤝Supporting agents
Arwen · Regional Head — EUAtlas · Regional Head — USACarol · Sales Agent — EUKiran · Regional Head — APAC🧩Apps
Apps owned by this service's team.
Agent EngagementCarol BioCarol ChatCarol ContextCarol HandbookCarol MonitorGEM MethodologyPrancing PonyRequests InboxSemantic MemoryServices CatalogUser Engagement