Theory

Preface

The theory is not that AI simply accelerates existing departments. It is that AI changes the task chain before the org chart, and agents need designed workflows rather than loose adoption theatre.

Build Loop comes out of that claim. If work should move through an execution graph instead of a stack of inherited roles, then the system has to be designed around context, routing, validation, approval, release, and learning.

Argument

From inherited forms to execution graphs.

The pattern is older than AI: every new medium begins by imitating what came before, until the mismatch becomes too visible to ignore.

New technology arrives in old forms

We always use new technology like the old world until it forces us to change.

Early film did not invent cinema. It simply recorded theatre. The camera sat still, the stage remained intact, and actors performed outward as if nothing fundamental had changed. It looked new, but behaved exactly like what came before.

Only over time, through use, constraint, and experimentation, did the medium begin to assert itself. Techniques emerged that were not translations of theatre but departures from it.

At some point, someone cut into the set, lowered the camera, and pointed it upward to capture something that could never exist on a stage. That was not just a new angle. It was the beginning of a new grammar. The camera stopped documenting performance and started shaping it.

This pattern repeats more often than we admit. The printing press initially mimicked handwritten manuscripts. Early cars were designed like carriages. Computers reproduced paper-based workflows, only digitized. The first instinct is always to fit the new technology into the old paradigm because that is what is legible and safe.

That phase never lasts. Eventually the mismatch becomes too obvious. The capabilities of the technology begin to strain against the constraints of the inherited model, and the question shifts from how to use the new thing inside what already exists to what becomes possible now that this thing exists at all.

AI agents are at that turning point

That is where the real transformation begins, and that is where AI agents sit now.

Most implementations still map agents directly onto organizational structures. An agent becomes a role: sales, support, operations. It inherits responsibilities as if it were simply a digital employee slotting into an existing org chart.

That is familiar, but it is fundamentally misaligned. Agents are not people, and they are not constrained by the same boundaries. They do not need the same wrappers around them for work to move coherently.

The better frame is closer to what Actor-Network Theory describes: actors inside a network of actions and relationships, where the outcome is produced by the path through the system rather than the position inside a hierarchy.

From org chart to execution graph

The efficient structure is not hierarchical but flow-based. Work becomes a sequence of transformations coordinated by dependencies, context, permissions, and state rather than handed off between predefined roles.

The system organizes around execution, around the movement and shaping of information, rather than around titles or departments.

Humans do not disappear in this model, but their position changes. They enter the system where judgment, context, or accountability are required, rather than serving as the primary scaffolding that defines how work is structured in the first place.

So the mistake is not adopting AI. It is using AI to preserve the past. If you do that, you only end up going relatively slow, faster.

The real opportunity is to design for the nature of the technology itself: a system where the path of work is primary, and both humans and agents are participants within that path.

That is the shift now underway. From org chart to execution graph. Most teams are still filming the stage.

Old default

Assign the agent to a department, role, or seat on the org chart.

Better unit

Design the route: questions, context, validation, approval, release, and learning.

Human role

Stay present where consequence, judgment, and accountability have to be named.

Commitments

What the theory commits to in practice.

The manifesto only matters if it changes how systems are designed. These are the practical commitments underneath the essays and the framework itself.

The workflow is the unit

AI changes steps, handoffs, bottlenecks, exceptions, and responsibilities before it cleanly changes job titles.

Judgment moves upstream

When execution gets cheaper, the scarce work becomes framing the problem, reading the context, and choosing what should exist.

Authority stays named

Agents can expand options and run bounded paths, but consequential change still needs visible human ownership.

The system must learn

Each trace should improve the next pass: better questions, better context, better routes, better checks, and clearer stop rules.

Library

The essay set

Latest first by default. Switch to series order when you want the original argument sequence.

13Ownership and process

The Human Requirement Goes Up

Why cheaper execution shifts advantage toward people who understand humans, workflows, process, and accountable ownership.

Read essay →
12Gateway and governance

AI Is Becoming The Gateway

Why AI becomes powerful when it mediates access to knowledge, action, and workflow rather than merely assisting inside them.

Read essay →
11Context surfaces

Dashboards and Flow Feeds

Why durable context, ephemeral motion, review, and trace should live on different information surfaces.

Read essay →
10Measurement and ownership

OKR Design for Humans and Agents

Why OKRs can unify humans and agents only when the shared objective is separated from controls, review, and ownership.

Read essay →
09Actors in the system

Agents Are Actors

Why agents should be treated as participants in a designed system, not passive features waiting for commands.

Read essay →
08Operator judgment

Build vs Deliver

The outward-facing case for why every team must navigate the tension between shipping now and investing in structure.

Read essay →
07System cost

The Coordination Tax

Why adding agents often increases coordination load before it reduces it.

Read essay →
06Trace and governance

Traces, Power, and Mediated Work

How visibility, distributed agency, and representational drift shape AI-heavy organizations.

Read essay →
05Distributed action

Standalone Complexes of Work

How coordinated action emerges from shared signals, environments, and local roles rather than central command.

Read essay →
04Role partition

Designed Complementarity

Why human-AI teams work only when role partition and authority are deliberately designed.

Read essay →
03Design principle

Human-Framed, AI-Expanded, Human-Authorized

The design principle: human initiation and accountability with AI expansion.

Read essay →
02Named method

The Build vs Deliver Gradient

How to decide when tooling investment is worth the drag it introduces.

Read essay →
01Workflow before structure

The Org Chart Is Not The Point

Why workflow redesign matters more than reporting-line redesign.

Read essay →

External Reading

Papers and signals behind the essays

The essays are the authored argument. These outside papers sit underneath them as reference signals on coordination, complementarity, authority, and how work actually shifts under AI.

Observations

The org chart is a theory. The workflow is the experiment. The operating surface is the product.

SaaS is going headless. The pane of glass is what you build on top.

AI changes the task chain before the org chart. The task chain now runs on APIs, not vendor UI.

Any business not building its own operating surface is standing still.

If you cannot trace the coordination, you cannot put it on a pane of glass.