Glossary

Agent Main — the supervisory layer of the Cognition Plane: routing, context, guardrails, approvals, measurement and memory.

Agent surface — a place where people meet the agent engine, defined by its audience and its trust regime. Distinct from a channel surface (a route to a prospect) and from a sub-agent (an internal specialist). See Section 12.

Agent-as-retriever — retrieval as a behavior of the model, through tool calls, rather than a step completed before the model starts reasoning. See just-in-time context.

Agentic GTM Architecture & Engineering — the revWorx approach to realizing Autonomous GTM Operations. The instantiation, not the vision.

Autonomous GTM Operations — the vision: a go-to-market system that reasons, acts and extends itself, with people setting direction and owning approvals. Autonomous in execution, not unsupervised.

Broad bridge — the pillar of the web surface that exposes the widest set of registered abilities; used for bulk reads and routine writes.

Capability — a role inside the orchestration engine, with instructions, output expectations and bounded tool access. Not a separate process or subscription.

Capability registry — a machine-readable catalog in which a web platform’s extensions declare what they can do; the interface the three pillars read. WordPress’s abilities registry is today’s instance.

Channel surface — a route to a person, such as search, email or direct mail. Defined by the job it does and the record it writes to; provided by tools, not a tool itself.

Cognition Plane — the reasoning and orchestration layer: one engine surfaced to people through one or more agent surfaces, a supervisory layer and specialist sub-agents.

Composable — built so that any component inside a plane can be added, replaced or retired without changing the other planes or the cost of the whole. Depends on the five conditions in Section 4.3.

Context window — the model’s working memory for a single request, measured in tokens. Everything the model can see while it works must fit inside it.

Context Engine — four versioned libraries (ideal-customer personas, brand narratives, proof points, revenue levers) supplied to every sub-agent at runtime.

CRM Agent — implementation term, not a pattern term. The agent surface embedded in the CRM interface for the client’s staff: Describe / Demonstrate / Do with human-in-the-loop gates on writes. See agent surface.

Custom-built server — an MCP server we write ourselves for a system that has no usable one. Two exist in the current stack.

Data Plane — the master records the business owns, separated from the external sources it reads.

Declarative interface — an interface in which the operator states the outcome wanted rather than the steps to take. The conversational surface of this architecture is declarative.

Execution Plane — the infrastructure the Tool Plane runs on: hosts, containers, gateway, build and release tooling, domains.

Governed change platform — the pillar of the web surface through which every irreversible write passes: snapshots, dry runs, approvals, design checks, guarded updates.

GTM Agent — implementation term, not a pattern term. The operator-facing agent surface: orchestrates GTM motions, routes the decisions that stay with people, carries KPI alerts and is primarily responsible for managing and orchestrating the sub-agent groups on the operator’s behalf. See agent surface.

Ground-truth layer — the pillar of the web surface used for diagnosis and agent infrastructure: direct code execution, binary uploads, site-side memory and skills.

Interface revolution — the shift of software’s primary surface from the graphical interface to conversation with an agent. The premise of Section 2.

Just-in-time context — loading only what the current task requires, when it is required, through tool calls rather than a pre-built index.

Load everything, always — the default MCP pattern, in which every connected tool’s definition is carried in context on every turn.

MCP (Model Context Protocol) — the protocol by which capabilities expose discoverable, callable tools to agents. Here, the integration paradigm of the whole stack.

MCP gateway — the single point between agent and servers that supplies credentials, enforces limits and routes calls.

Operator surface — the agent surface through which operators direct the system: a single conversational interface plus the screens kept for seeing, approving and overriding (Section 12). One of several surfaces of the same engine; see agent surface.

Operator-oriented tool — software designed to be worked by a person at a screen: its own GUI, integration pattern and data plane. The kind of tool the interface revolution displaces.

Owned path — the way a capability is met from what the architecture already holds: existing data, existing tools and agent work. The working default for every category in Table 3, not a placeholder.

Premium path — the way a capability is met by adding a specialist product, taken when a stated trigger in the business justifies the cost. Table 3 names the trigger alongside each premium path.

Progressive disclosure — discover, inspect, execute: the agent finds tools on demand, loads only the definition it is about to use, and calls it. Keeps standing context cost flat in server count.

Revenue Lever Map — the graph linking each outcome to its drivers and gates; what turns measurement into action.

Standing context cost — tokens consumed on every turn before any work is done. Distinct from per-task cost, which scales with the work.

Supervisor — the routing component of Agent Main: directs each piece of work to the sub-agent whose capability, task and context fit. A component, not an agent surface; the named agents (CRM Agent, GTM Agent, WEB Agent) are surfaces.

Three-pillar pattern — the agentic web surface: a governed change platform, a broad bridge and a ground-truth layer, all reading one abilities registry.

Token — the unit in which model usage is metered and billed; roughly three-quarters of an English word.

Tool bloat — context and token cost consumed by tool definitions under load-everything; grows linearly with tool count.

Tool Plane — the universal MCP surface: seven functional clusters plus the channel surfaces they provide.

Tool selection consistency — how reliably an agent picks the right tool for a task. Degrades with flat lists of many similar tools; improved by search-then-inspect.

Trust routing — sending each write to the surface that can govern its risk: bulk and routine work through the bridge, irreversible changes through the governed platform, diagnosis through ground truth.

Waterfall enrichment — trying data sources in sequence until one returns a satisfactory result.

WEB Agent — implementation term, not a pattern term. The public agent surface resident on the client’s website, engaging visitors under guardrails with escalation to a human. See agent surface.