Paper 008 · Chapter Eight
Technology appears last in this framework. Deliberately.
Seven papers of theory, method and patterns precede this one because architecture in the wrong order becomes the anti-patterns of Paper 006, Age Six artefacts bolted to Age Three foundations. This paper is the reference architecture for organisations that have done the preceding work: five layers, memory-first, specified by responsibility rather than by product, and designed to a single survivability test, every vendor, model and platform in the implementation must be replaceable without the organisation losing its memory. The architecture is drawn vendor-neutral because the framework is; the reference implementation's particular choices belong to Paper 005 and its successors.
1 · The Five Layers
Each layer has one responsibility, strict rules about what it may not do, and an interface to the layers beside it. The discipline is in the separations.
The load-bearing insight is that intelligence is layered above the systems of record, never instead of them. The ERP remains the system of record; the estate becomes the system of memory; the agents become the system of intelligence. Organisations that conflate these rebuild their transactional backbone in pursuit of AI and arrive, years later, back at Age Four.
2 · The Knowledge Layer: the Memory Estate
Layer 2 is the paper's centre of gravity, because it is where the Six Duties (Paper 004) become infrastructure. The estate holds all three memories, each in the store suited to its nature, joined by a semantic layer that makes them one.
3 · The Reasoning Layer
Reasoning is context assembly before it is model invocation. For every reasoning task, triggered by an event (an arrival, an anomaly, a schedule), the layer assembles a context: the relevant slice of each memory, resolved through the semantic layer, filtered through permissions, and bounded by the requesting agent's specification. Only then are rules and models applied. The Equation's Context term is exactly this act of assembly, and most reasoning failures in the field are context failures wearing a model's name.
Grounding is internal citation. Every finding the layer produces carries references to the memory it reasoned from, agents cite the estate the way the discipline's own research assistant cites the papers. This is what makes recommendations inspectable at the Approve gate: the owner sees not just what the agent concluded but what it read. Models are pluggable behind a single interface; the citations, contexts and findings are the organisation's, whichever model produced them, the survivability test applied to the layer most tempting to marry.
4 · The Agent Runtime
The runtime turns Paper 007 from doctrine into enforcement. Each agent's nine-field specification and Boundary Sheet are machine-readable configuration, not policy documents: the runtime will not deliver an observation an agent's spec does not grant, will not release an action below the agent's granted rung, and records every cycle, observation, context, finding, recommendation, approval or dismissal, action, outcome, to an immutable audit log that is itself part of organisational memory. The Autonomy Ladder is a permission model in the runtime; promotion and demotion are configuration changes with an approval trail, which is why demotion can be graceful (Paper 007 §4). Dismissals are first-class data: an owner declining a recommendation, with a reason, is the Learn step's richest signal.
5 · The Governance Plane
Four concerns cut across every layer and are specified once, centrally:
6 · Build Order: Thin Slices, Never Layer-Cake
The architecture is built as the Transformation Sequence (Paper 006) instructs, and never as a layer-at-a-time programme. Steward stands up the estate's core, transactional replica, semantic layer, provenance, for the domains the first loops need, not for everything. Capture begins filling the experiential store from day one, because interviews and decision records need no platform to start. Loop then builds one thin vertical slice per agent, the slice of estate, reasoning and runtime that one loop requires, so that value ships while the architecture grows. Govern installs the plane's rules with the first slice, when they are cheap. Compound widens slices into shared infrastructure as loops multiply. An organisation that builds the full estate before its first loop has chosen the layer-cake, and will be explaining an empty architecture to an impatient board within a year.