Our proposed reference architecture · v1.0

The future of engineering is the architecture — not the agent.

The Enterprise Agentic Reference Architecture is our proposed, vendor-neutral blueprint for running agents at enterprise scale: seven layers and nine principles that hold whether your agents write code, close the books, or triage claims. SLAW and Botfather are our open-source implementation of it — shared as a starting point for the field, not an industry standard.

Is the future of engineering inside Copilot, Claude, or Codex — or is it in the deliberate placement of agents, humans, gates, and budgets across the enterprise?

Only one layer of this architecture is engineering-specific. Swap the agent mesh for finance, claims, or ops and the architecture holds. Engineering is just the hardest proof.

The blueprint

Seven layers, vendor-neutral

enterprise-agentic-reference-architecture · v1.0
The Enterprise Agentic Reference Architecture — seven stacked layers from Human Control Plane down to Enterprise Infrastructure, with the Agentic Control Plane highlighted.

The seven layers

Where SLAW and Botfather sit

They are the two halves of Layer 2 — the Agentic Control Plane: a pluggable slot, never a lock-in.

Layer 2 · the Agentic Control Plane

Orchestration is not fleet governance.

Running agents and governing them at scale are distinct concerns — so they are distinct components. We built and open-sourced both.

SLAW — the orchestration runtime

Squads, routines, memory, and tools. The local control plane that runs an agent workforce and coordinates work toward a goal.

Botfather — the centralised control plane

Budgets, skill distribution, policy, and audit across every instance. The governance half — distinct from orchestration by design.

The spec chain

Intent flows down. Attribution flows back up.

Humans own intent; agents own execution. An explicit chain — intent brief → requirements → solution design → agent config — keeps it that way, and the loop closes itself.

enterprise-agentic-integration-flow
The enterprise agentic integration flow — intent and acceptance criteria flowing from humans through the control plane to the agent mesh, with attribution and review feeding back into the next cycle.

Technology-agnostic

The nine principles of enterprise agentic engineering

The architecture exists to enforce these. Any implementation that satisfies all nine is a valid instantiation.

A reference architecture you can actually run.

The Agentic Control Plane is open source. Read the blueprint, then download the implementation.