Carolopedia

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

📖 CarolopediaServicesSystem ServicesExternal I/OGuide page
External I/O

External I/O

Block · Service category in System Services

📖About & Usage

About

External I/O is Carol’s single, governed point of contact with the outside world. Whenever any part of the ecosystem needs to talk to an external service — sending an email, calling a CRM API, posting a Slack message, or querying a payment gateway — the request passes through this pipeline stage. It acts like a universal switchboard, taking every outbound call and making sure it’s safe, correctly formatted, and tracked before it ever leaves the building. Built into the core system services pipeline and watched over by Hagrid (Keeper of Keys), it exists to avoid a tangle of ad‑hoc connections and to give the team one place to enforce policies, monitor usage, and control costs.

Because it sits between Carol’s internal logic and the public internet, External I/O handles authentication, rate‑limiting, logging, and retries for all external traffic. This means individual agents or apps don’t need to re‑invent security or billing checks — they simply hand the intended request to the switchboard and trust it to deliver. In Carol’s architecture, “every call that leaves Carol” is not an exaggeration; it’s the literal design.

Usage Patterns

External I/O fires automatically whenever a legitimate outbound connection is needed. A typical scenario: Carol (Sales Agent — EU) finishes a chat with a customer in Carol Chat and marks the deal ready for a follow‑up offer. The offer needs to be sent via the company’s external email service. Carol’s reasoning module prepares the email content, then hands a “send email” request to External I/O. The block looks up the correct API key from a secure vault, respects the service’s rate limits, formats the request, logs the attempt, and finally transmits it. If the call fails, it can retry or alert the operations team.

This pattern repeats for any outward‑facing activity — pushing data to a data warehouse, triggering a payment, updating a customer’s record in the CRM, or even pinging a cloud monitoring service. The block never initiates calls on its own; it’s purely reactive, springing into action only when another internal component (like a sales agent, a migration engine, or a scheduled process) explicitly asks to reach the external world. That makes External I/O a quiet but indispensable postal service inside the Carolverse.

🧩Member services

API Router · Outside Calls Switchboard

Sends every message to outside helpers down one safe, reliable line.

Azure Utilities · Cloud Bill Watcher

Looks up cloud costs and warns when spending runs high.

Claude CLI Helper · The AI Phone Line

The one phone line everyone uses to ask the AI for help.

Gmail Client · Email Mail Desk

Sends and reads email on behalf of the team.

Media Ingest · Incoming Media Reader

Turns incoming photos and files into plain words the team can read.

Relay-to-Carol · Speak-Through-Carol Relay

Routes other helpers' messages through Carol so she keeps one voice.

Voice Gate (Outbound) · Outgoing Voice Gatekeeper

Checks and protects every spoken reply before it reaches a person.

Voice Transport · Live Voice Line

Carries Carol's live voice conversations back and forth in real time.

WhatsApp Client · WhatsApp Post Office

Sends and receives all WhatsApp messages and attachments for the team.

👤Owner

Radagast · Admin

🧱Other blocks in System Services

State & KnowledgePipeline MachineryMonitoring & AccountabilityAgent Cognition