The AI Agent Factory

4.1 Five layers, five verbs

Status
stable
4 min read
Owner
Panaversity
Approved
Panaversity ·

In everyday life. Think of a restaurant. The front door and phone line are its channels, and the cook is its runtime. The cook's own habits are its memory, and the recipe book is its KSoR. The manager's key to the cash register and the stockroom is its DSoR.

Every AI Worker in this book is drawn the same way: five layers, one job each.

LayerIts verbWhat it holds or doesBrightline example
ChannelsconnectWhere people and systems reach the worker: a chat app, team messaging, email, a web portal, an APIThe AP inbox, the team chat
RuntimeexecutesThe replaceable harness that reasons and actsThe AI vendor's app running a task
MemoryremembersContinuity: preferences, experience, where to look"Maria wants the register sorted by due date"
KSoRknowsThe governed, authoritative knowledge: policies, procedures, thresholds, definitionsAP policy, approval limits
DSoRactsThe governed door to real systems: it checks, acts, and keeps the evidenceRegister updates, payment status

Two things sit outside the five layers. Above them is the human principal, who owns the first 10 and the final 10 percent of every task (Chapter 3). Below DSoR are the company's own systems: the accounting system, the bank and the vendor records. They stay the authority on their data.1 DSoR does not replace them. It governs the worker's access to them.

Where is the worker itself? It is not one box. The worker is the Role Contract from Chapter 2, and the contract ties the layers together. It names the knowledge sources, the memory rules, the operations the worker may request, the runtime it needs and the channels it serves.

The canonical (standard) architecture. A human principal at the top owns the first 10 and final 10 percent. Below are two rented layers, channels and runtime. A dashed ownership line follows, with memory sitting on it. Below the line are the owned layers, KSoR and DSoR, side by side, with the company's systems under DSoR. The runtime reads from KSoR and memory and sends requests to DSoR. A dashed arrow carries DSoR's evidence back up to the human's final 10 percent. A band along the bottom names the Role Contract, which ties the layers together.

Figure 4.1. The canonical (standard) architecture. Channels connect, runtimes execute, memory remembers, KSoR knows and DSoR acts. Rented layers sit above the line and owned layers below it.

This is the only architecture diagram in the book. Later chapters zoom into one layer at a time. When a chapter introduces a product or a technique, ask one question first: which layer is this?

Check yourself

Question 1 / 8 · current

0 answered

Which layer of the canonical architecture executes the work?

  1. The System of Context, Panaversity, first edition.↑

On this page