Part V — REFERENCE
13.Drawing the Stack
The whole architecture on one page. Every term links to the section that teaches it.
The architecture drawn as one stack. Layer 1, Infrastructure (Sections 7 and 8): the open-source commons assembled into an organization-controlled Intelligence Hub, with Organizational Memory accumulating under the organization’s governance. Layer 2, Execution (Sections 3 to 5): Frames carry context, Cogs perform bounded work, Ops orchestrate complete jobs. The Interface (Section 9): the application through which knowledge workers run Ops and converse with Cogs. Layer 3, Economy (Sections 10 to 12): artifacts exchanged across independent Hubs. Cross-cutting Validation (Section 6) spans every layer: Guards check, Gates decide, Tracks preserve evidence.
View as text diagram
┌──────────────────────────────────────────────────────────────────┐ │ LAYER 3 — ECONOMY (§10–12) │ │ The marketplace: Ops, Cogs, Frames, and Guards published, │ │ discovered, installed across sovereign Hubs. Tracks stay home. │ ├──────────────────────────────────────────────────────────────────┤ │ INTERFACE — The Desktop Application (§9) │ │ Where knowledge workers run Ops, converse with Cogs, │ │ and compose and share Frames. │ ├──────────────────────────────────────────────────────────────────┤ ┌─────────────────┐ │ LAYER 2 — EXECUTION (§3–5) │ │ VALIDATION (§6) │ │ Ops — installable, supervised jobs │ │ cross-cutting │ │ Cogs — AI workers oriented by Frames │◄──►│ Guards: check │ │ Frames — organizational context, versioned and inheritable │ │ Gates: decide │ ├──────────────────────────────────────────────────────────────────┤ │ Tracks: record │ │ LAYER 1 — INFRASTRUCTURE (§7–8) │ └─────────────────┘ │ Organizational Memory — the context the Hub accumulates │ │ Intelligence Hub — the sovereign deployment perimeter │ │ Nebari — curated open-source stack Nebi — packaging/installs │ │ Compute, open-weight models, the organization's data │ └──────────────────────────────────────────────────────────────────┘
Each layer, restated as the problem it exists to solve:
- Infrastructure exists because rented intelligence leaks auditability and context (§1–2); the Hub is the perimeter where both stay home (§7), built from the open-source commons (§8).
- Execution exists because models alone are capability without accountability: Frames capture the context that makes AI work valuable (§3), Cogs make the work assignable and auditable (§4), Ops make whole jobs installable and supervised (§5).
- Validation exists because generation and verification are different things: Guards check, Gates decide, Tracks preserve the evidence (§6).
- The economy exists because packaged + contextualized + verifiable = exchangeable (§10), and because open standards are how strangers come to trust each other's artifacts (§11).
The paper's six-verb summary is the whole system in one breath:
"Frames guide the work. Cogs perform the work. Ops orchestrate the work. Guards verify the work. Gates decide whether the work proceeds. Tracks make the work accountable."
Self-test, in the field-guide spirit: cover the diagram and explain to a colleague why an Op written by a stranger can be safely installed in your organization. If your answer touches a manifest, a Frame, a Guard, and a Track, you have the architecture.