AGENT·007.AI
DE EN
Ask Nova-7

Reference architecture

Enterprise AI Control Plane

Five layers from the user to the infrastructure — and a cross-cutting control plane that enforces identity, policy, quality, cost and governance across all layers.

Reference architecture in five layers, from top to bottom: Layer L1: Users, Applications & Channels (Web, apps, assistants, existing systems). Layer L2: Agent Experience & Orchestration (Planning, tool selection, dialogue, workflows). Layer L3: Context, Knowledge & Memory (RAG, knowledge graphs, provenance, memory). Layer L4: Tools, APIs, Events & Workflows (Tool contracts, MCP/A2A, asynchronous processes). Layer L5: Core Systems, SaaS, Cloud, Edge & Data Platforms (Business systems, data platforms, infrastructure). Cutting across all layers, the control plane provides: Identity & Delegation, Policy & Approval, Security & Guardrails, Evaluation & Quality, Observability & Audit, Model Routing, Cost & Usage, Governance & Compliance.

Five layers (L1 top → L5 bottom)

  1. L1

    Users, Applications & Channels

    Web, apps, assistants, existing systems

    The point of access for people and systems. This is where intent arises — and where answers and actions must arrive in a way that is understandable, authorised and traceable.

    Mission 001 · Target Vision and Operating Model
  2. L2

    Agent Experience & Orchestration

    Planning, tool selection, dialogue, workflows

    The layer on which an agent plans, selects tools and steers processes. Non-deterministic — which is why it needs boundaries, approvals and observability.

    Mission 003 · APIs Become Tools Mission 005 · Quality becomes measurable
  3. L3

    Context, Knowledge & Memory

    RAG, knowledge graphs, provenance, memory

    The material an agent works with reliably: curated, authorised, traceable context instead of disordered access to raw data.

    Mission 002 · Data Becomes Context
  4. L4

    Tools, APIs, Events & Workflows

    Tool contracts, MCP/A2A, asynchronous processes

    The bridge to the business systems. An API only becomes a tool once its contract is unambiguous for a non-deterministic system as well.

    Mission 003 · APIs Become Tools
  5. L5

    Core Systems, SaaS, Cloud, Edge & Data Platforms

    Business systems, data platforms, infrastructure

    The existing landscape on which everything is built. This is where sovereignty, portability and actual costs are decided.

    Mission 006 · Dependencies remain steerable

The individual agent is not the platform. The control plane is the platform.

How does this map onto your landscape?

Nova-7 explains the layers and points to the relevant missions and primary sources.

Ask Nova-7 about the architecture