Conversational Infrastructure: The Three Planes Behind Memory

Autonomous Agents without infrastructure are "charismatic interns without a badge, a system, or supervision": they talk a good game, but don't deliver consistency or preserve context. Conversational infrastructure is the layer that underpins everything. This isn't a chapter for programmers—it's for anyone who needs to understand what to sponsor, what to demand, and what never to outsource without governance.

It does three things constantly: captures real-time events, preserves operational memory, and orchestrates actions and handoffs. It's what transforms MCI from a method dependent on heroism into a growth operating system.

The Crime of the Batch

Most stacks still operate with batch logic: integrations that run "every X minutes," spreadsheets that consolidate "at the end of the day," reports that arrive after the decision is already dead. This works for accounting. It doesn't work for conversation. When an event occurs (a click, a reply, an objection, a buying signal), the window for action is short. If the stack only finds out later, the company shows up late with the right message—which is the same as showing up with the wrong message.

Conversational infrastructure begins with an obsession: time-to-context. How long does it take for the system to understand what is happening and decide on the next step? This only changes when you replace batch with event—an event-driven architecture (webhooks, streams, queues) instead of periodically fetching data.

The Three Planes

Data Plane — the equity. This is where assets that need to outlive channels and vendors reside: the Identity Graph (identity resolution—person, company, channels, consent), the Knowledge Graph (structured context—intent, state, pain points, objections, promises), and the audit trail. It’s what transforms "data traffic" into "intelligence ownership"—and where sovereignty begins.

Decision Plane — the brain. This is where MCI functions as an engine: reading events in real time, classifying intent with confidence, detecting state in the graph, calculating risk via Semáforo, intelligent routing, and generating the next step with guardrails. It is the most critical and least common component in today's stacks—most companies have a Data Plane (CRM, ERP) and an Action Plane (channels), but not the layer that connects the two with intelligence.

Action Plane — the execution. This is where the decision becomes an action: a message in the right channel, an updated ticket, a scheduled meeting, a generated proposal, a notification to a human with the Bandeja de Contexto (context tray). It ensures that "deciding" doesn't get stuck on a dashboard.

The golden rule of architecture: The CRM records. MCI decides. Channels execute. When someone asks, "do we need to replace the CRM?", the answer is almost always no—you need a decision layer (overlay) on top of the existing CRM. Nothing gets replaced; coordination gets added.

Layered Memory

Saving "everything about everything" creates an expensive and useless monster; saving "nothing" creates amnesia. The infrastructure solves this with three layers: session memory (ephemeral, expires when the conversation ends), cycle memory (operational—state, locks, Score, next step, SLAs, Crachá de Contexto (context badge)—the most important layer, which prevents resets between interactions), and client memory (strategic—preferences, history, accumulated value, governed by GDPR/LGPD). "Forgetting is a feature": retention and purging are part of data hygiene.

AI is the Processor, Not the Hard Drive

A crucial architectural decision for sovereignty: the AI can summarize, classify, and suggest—but its output must return as a structured asset in the Data Plane. If the intelligence lives only "inside the AI model," the company doesn't own its memory—it rents it. When the AI classifies "intent: enterprise purchase with a compliance lock," that classification needs to be recorded as structured data in the Knowledge Graph. If the company switches models tomorrow, the accumulated intelligence remains. If the AI were the hard drive, switching models would mean formatting the disk.

Identity Resolution

Infrastructure without identity resolution turns into operational schizophrenia: the same customer communicates via WhatsApp, email, and the website, and each channel treats them as a different person. This isn