Recursion

Everything in the rest of the model describes building a product. But the four actors, the two faces, the delegation surfaces, and the gate are invariant — point the same machine at a different object and it still runs. The model is self-applying: it builds not only the product but the process and the toolchain that build the product.

Three objects matter:

Object	What it is	Oracle decides	Builder makes	Architect structures	Strategist distills
Product	the concrete, substantive outcome	which product	a feature	the codebase	product & domain knowledge
Process	the way of working	which practices	a workflow or runbook	how the practices fit	process lessons
Toolchain	tools & agent configuration	which tooling	a skill, plugin, or harness	the toolchain	tooling patterns

The loop is identical in each; only its object differs. So a “senior” anyone is not a bigger role — it is the same role worked across more of these objects.

Overlapping sets, not stacked levels

Process and toolchain interpenetrate — a commit discipline encoded as a hook is process and toolchain at once; the toolchain is often how the process is enacted. A domain pattern codified as a skill is product knowledge and toolchain. The three intersect, union, and influence one another, and the same artifact frequently lives in more than one.

flowchart TB
  PROC["<b>PROCESS</b><br/>the way of working"]
  TOOL["<b>TOOLCHAIN</b><br/>tools and agent configuration"]
  PROD["<b>PRODUCT</b><br/>the concrete outcome that ships"]
  PROC <-->|overlap & co-evolve| TOOL
  PROD -->|experience distilled · Strategist| PROC
  PROD -->|experience distilled · Strategist| TOOL
  PROC -->|capability supplied| PROD
  TOOL -->|capability supplied| PROD
  class PROD artifact
  classDef artifact stroke:#0d9488,stroke-width:1.75px

Product is the concrete outcome; process and toolchain are means that serve it and are refined by it. Influence runs every way at once.

The one asymmetry: product is the concrete, substantive outcome — the thing that ships. Process and toolchain are means that serve it and are refined by it. Influence runs every way at once: building the product teaches process and tooling (the Strategist distills), while better process and tooling make the next product cheaper.

Three things this clears up

An outsized “Architect” definition resolves. “Own codebase health, and the process governing AI contributions, and the AI workflow/harness” was never one giant role — it is the Architect motive worked across all three sets. One motive, three objects.

Codification is how knowledge crosses between the sets — not an elevator up a ladder. The Strategist distills a product lesson into a process convention or a toolchain artifact — agent configuration — which lands in process, toolchain, or their overlap, and is wielded back in product-building.

The Strategist unifies the model. “Accumulate” is lifting product experience into a reusable process or toolchain asset. So the Strategist foundation tier, the codification law, agent configuration, and this self-application are one pattern: knowledge made reusable and carried across a seam — the seam between actors (Strategist → the other three, within one build) and the seams between sets (product ↔ process ↔ toolchain). Same motive, two kinds of seam.

Next: Glossary →