# 4.1 Six layers, six verbs (/ai-worker-paradigm/the-architecture-in-one-picture/five-layers)

---
type: Document
title: "4.1 Six layers, six verbs"
description: "The six layers every AI Worker in this book is drawn with, the one job of each, and where the worker itself is in the picture."
status: stable
order: 104.1
ksor:
  owner: team:panaversity
  audience: [ public ]
  approval:
    by: process:panaversity
    at: 2026-10-12T23:51:41Z
chapter: "04"
part: I
expert_status: required
concepts: [ "4.1" ]
last_verified: 2026-10-04
sources:
  - id: v1-system-of-context
    title: "The System of Context (Panaversity, first edition, verified 2026-10-04)"
    resource: https://agentfactory.panaversity.org/docs/ecosystem/system-of-context
generated:
  at: 2026-10-12T23:51:41Z
  by: esl-rewrite/1.2.0+ksor.1
trust_tier: unverified
build_id: sha256:2f1e14f2a0f11dbc37eb5856ca9b7d35b4ce4894da74c3328cf61a3c17c03861
dirty: true
ksor_version: 0.0.60
---

**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 order tickets on the rail show what each table ordered and what is done, so they are its SSoR. 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: six layers, one job each.

| Layer | Its verb | What it holds or does | Brightline example |
| --- | --- | --- | --- |
| Channels | connect | Where people and systems reach the worker: a chat app, team messaging, email, a web portal, an API | The AP inbox, the team chat |
| Runtime | executes | The replaceable harness that reasons and acts | The AI vendor's app running a task |
| Memory | remembers | Continuity: preferences, experience, where to look | "Maria wants the register sorted by due date" |
| KSoR | knows | The governed, authoritative knowledge: policies, procedures, thresholds, definitions | AP policy, approval limits |
| SSoR | tracks | Governed memory of the work: one case file for each matter, with where it stands, what was tried, who approved what, and why | The case file for invoice 5120, step by step |
| DSoR | acts | The governed door to real systems: it checks, acts, and keeps the **evidence** | Register updates, payment status |

Two things sit outside the six 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.[^v1-system-of-context] 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 three owned layers side by side, KSoR, SSoR and DSoR, with the company's systems under DSoR. The runtime reads from KSoR, reads and records in SSoR, 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.](img/architecture.png)

*Figure 4.1. The canonical (standard) architecture. Channels connect, runtimes execute, memory remembers, KSoR knows, SSoR tracks where the work stands, 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?

[^v1-system-of-context]: The System of Context, Panaversity, first edition.