---
title: The architecture at a glance
url: https://revworx.ai/architecture/1/
date: 2026-10-19T08:25:31+00:00
modified: 2026-11-08T03:23:54+00:00
lang: en_US
---

I

Part one

## Why composable, why now

The architecture first, in one picture, so that everything after it has a place to land. Then the four developments that make it possible now: a new primary interface for software, a uniform way to integrate it, a way to scale that integration without paying on every request, and a different theory of how an agent finds what it needs to know.

Section 1 · Part one

# The architecture at a glance

In this section

[1.1How to read this document](#1-1)

Part one

§1The architecture at a glance

[§2The interface revolution](/architecture/2)[§3MCP as the integration paradigm](/architecture/3)[§4The load-bearing element](/architecture/4)[§5The adoption signal](/architecture/5)[§6The retrieval shift](/architecture/6)

[Download the PDF →](/wp-content/uploads/2026/10/composable-reference-architecture.pdf)

In brief

The architecture places four layers, called planes, between you and the work. You speak to the top one, the Cognition Plane, and it reaches down through the Tool, Execution and Data Planes to get things done. It comes back to you only when a decision is yours to make.

![Figure 1. The four planes, read from the top down. You: ask in plain language, approve the decisions that are yours, override when needed. Cognition, the system that reasons. Tool, the universal MCP surface, everything it can do. Execution, where it runs. Data, what it knows: your master records, owned outside every tool, plus the external sources it reads.](https://revworx.ai/wp-content/uploads/cra-figure-1-four-planes-co08.png)

*Figure 1 — The four planes, read from the top down*

The whole architecture fits in one picture. Four layers, which this document calls planes, sit between you and the work. You speak to the top one; it reaches down through the other three to get things done, and comes back to you only when a decision is yours to make. Each plane answers a different question, and the rest of the document is organized around those questions.

- **The Cognition Plane** is the part you talk to. It holds the reasoning: a supervising agent, its specialists, the context it keeps about your business, and the guardrails and approval gates that keep it inside the lines. A weekly pipeline review, a draft of outreach copy, a request for a new integration: each lands here first.
- **The Tool Plane** is everything the system can do. Every capability, whether a CRM, an ad platform, a meeting transcript service or the website itself, is reached through a single protocol, the Model Context Protocol (MCP). Because the protocol is uniform, capabilities can be added or replaced one at a time, and because they are discovered only when needed, adding more neither slows the system nor raises its running cost.
- **The Execution Plane** is the infrastructure the tools run on. In this architecture it is owned rather than rented, and it is reachable through the same protocol as everything else, which means the system can extend and repair itself: set up a server, deploy to it, inspect it, restart it.
- **The Data Plane** is what the system knows. It draws a line between the records your business owns, which live outside every tool, and the external sources it merely reads. That line is what makes the architecture composable: swap a tool and the record is untouched.

## 1.1How to read this document

Part One explains why this architecture is possible now: conversation as the primary interface (Section 2), MCP as the integration paradigm (Section 3), the innovation that lets it scale (Section 4), the adoption evidence (Section 5) and how agents find what they need to know (Section 6). Part Two takes each plane in turn. Part Three covers where the system meets people. Part Four states what it covers and what it is not.

Vendor names appear only in callouts marked *Current implementation*, because the pattern outlives any particular choice. Boxes marked *For technical evaluators* can be skipped without losing the thread. Each section closes with a key takeaway.

Key takeaway

Four planes, one protocol between them. You talk to the top; it reaches the rest. Keep the picture in mind and every later section is a closer look at one part of it.

Cite as: revWorx (2026). A Composable Reference Architecture for Autonomous GTM Operations, First Edition, §1. revworx.ai/architecture/1