Carol — back to Apps ← Apps

Carolopedia

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

📖 CarolopediaServicesSystem Services
System Services

System Services

Service The shared internal building blocks every agent and droid reuses

📖About & Usage

About

System Services are Carol's 47 shared code services — the reusable internal building blocks (the AI phone line, the WhatsApp post office, the registry readers, the bypass engine, the watchers) that the agents and droids call instead of each reinventing them. They are grouped into five broad categories, each a block with its own page.

What it does

The shared internal building blocks every agent and droid reuses

🏛Architecture

The System Services service is built following the agent-centric modular architecture of Carolverse. It is the shared internal platform — roughly 47 reusable code building blocks (the AI phone line, the WhatsApp post office, the registry readers, the bypass engine, the watchers) that every agent and droid calls in-process instead of reinventing them, owned and tended by Radagast.

View the full architecture →

🧱Blocks

External I/O · 9 servicesState & Knowledge · 9 servicesPipeline Machinery · 12 servicesMonitoring & Accountability · 12 servicesAgent Cognition · 5 services

📚Recent initiatives

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

CAROL-INI-0009-02: Upgrade PA-C12 Service Router to Claude-based
Replace placeholder keyword-match routing in agents/carol/droids/pa_c12_router.py with a haiku-backed call that sees user message + recent history + inferences + service manifests\u2026
Orion · 2026-07-04 02:35
CAROL-INI-2189-01: al_watch_01 runtime guard counts its own Hermione launcher — watcher aborts every 60s tick
NARROW RUNTIME HOTFIX (NOT the INI-113 architecture redesign; that is separate, broad, still planned). The watcher already exists and is scheduled every 60s; it is non-functional\u2026
Orion · 2026-07-04 01:45
CAROL-INI-2147-00: Add fail-fast evidence-capture validation to the step dispatcher and resume the blocked Org prompts initiative
The step dispatcher currently allows execution to begin without confirming that any evidence-capture mechanism is wired to verify completion, causing steps to exhaust all retry at\u2026
Orion · 2026-07-03 21:23
Browse all initiatives →

🛰️Updates

Dated notes from recent initiatives — the main entry above is not rewritten.

Fix2026-07-01

The registry single-writer relay and core-table guard were added to prevent stub-clobber vulnerabilities, as seen in the 2026-06-28 incident where System Services database was restored from backup. This hardens against stray writers creating empty databases.

👤Owner

Radagast · Admin

🧩Apps

Apps owned by this service's team.

Radagast — Admin LogShared Services