← aman.holdings  /  Essays  /  Superorganism  /  Diagrams

Diagram gallery / mental models

The Superorganism, in Six Diagrams

The top-level abstract key diagrams from The Agentic Engineering Superorganism, built as referenceable mental models. Each one stands alone and can be iframed anywhere.

2026-07-10 Aman Bhargava · aos SVG + HTML · self-contained
Diagram 1 · §1

The org is the machine that writes the machine

Many minds, one dense text. Conway's law: the code's internal link graph takes the shape of the org that wrote it. Superintelligence already existed as the well-run organization; access was gated to the few who mastered onboarding, documentation, promotion, and culture.

THE ORGANIZATION · MANY MINDS WRITES THE CODEBASE · ONE DENSE TEXT CONWAY: SAME SHAPE Access was the gate: only a few could command one THE OLD TOOLS onboarding documentation promotion culture
anchor: #d1iframe: diagrams.html?d=d1§1 in the essay →
Diagram 2 · §2

Everyone gets promoted on day one

Zoom into any node of the org graph and you find a whole organization: one human, day-one tech lead, commanding an agent legion that can grow tenfold for an afternoon. The genuinely new problem rides along: agents produce faster than their own human can verify, so trust now lives inside the node.

THE ORG GRAPH EVERY NODE IS AN ORG THE NEW NODE one human, day-one tech lead an agent legion: 10× for an afternoon, zero by dinner THE NEW PROBLEM Bandwidth asymmetry agents produce the human verifies trust now lives inside the node, not just between nodes
anchor: #d2iframe: diagrams.html?d=d2§2 in the essay →
Diagram 3 · §3

Build on media both species read natively

One set of media, two kinds of reader. Humans get rich text and interfaces; agents grew up on the same substrate, because the pretraining corpus is the web. HTML is the deep dual-native case. New agents arrive already speaking repo, and documentation becomes the interface to half the workforce.

HUMANS · READ IT AS RICH TEXT AND UI THE SHARED SUBSTRATE · ONE SET OF MEDIA, TWO KINDS OF READER Git Markdown Issues HTTP MCP HTML PRETRAINING CORPUS = THE WEB AGENTS · GREW UP HERE · THEY ARRIVE ALREADY SPEAKING REPO
anchor: #d3iframe: diagrams.html?d=d3§3 in the essay →
Diagram 4 · §4

Three nested loops, ending in a named human

The humanistic controller, fastest loop inside. Loop one: the bench, reflex-speed review in the live session. Loop two: the responsible party, one named human per deliverable, a Markov blanket around agents spawning agents. Loop three: the meta-RP's social world model, Dunbar-bounded near 150 people, 30 to 60 of them active.

FAST SLOW LOOP 3 · META-RP · DUNBAR ~150, 30–60 ACTIVE AGENTS SPAWNING AGENTS UNSUPERVISED INTERIOR LOOP 2 · RESPONSIBLE PARTY · ONE NAME A MACHINE CANNOT BE HELD ACCOUNTABLE (IBM, 1979) LOOP 1 · THE BENCH REFLEX · CATCHES IT LIVE
anchor: #d4iframe: diagrams.html?d=d4§4 in the essay →
Diagram 5 · §5

Replicate the role, never the brain

Dunbar's number is a hard ceiling, so the coordinator role copies downward instead. The trust ratchet raises two bars per person, complexity trusted and scope owned. Members of technical staff clear the top bar, and over nine to sixteen months start webs of their own. Branching factor around thirty; capability compounds while no single mind holds more than its share.

DUNBAR'S NUMBER · A HARD BIOLOGICAL CEILING · DON'T BET ON REPEALING IT the coordinator THE TRUST RATCHET · TWO RISING BARS complexity trusted scope owned 9–16 MONTHS members of technical staff → each starts a web of their own ×30 CAPABILITY COMPOUNDS · NO BRAIN EVER HOLDS MORE THAN ITS SHARE
anchor: #d5iframe: diagrams.html?d=d5§5 in the essay →
Diagram 6 · §6

Distributed capability, sovereign people

The objective function, drawn as two network designs. Left: strong nodes everywhere, redundant links, any node can fail and the network survives. Right: the bunker civilization, one hub and managed dependents, a single point of failure in an era of pocket superintelligence. The fractal org is the left picture, built small first.

THE TARGET · STRONG NODES EVERYWHERE every node capable · any node can fail · the network survives THE ANTI-PATTERN · THE BUNKER dependents kept functional, never strong · one point of failure
anchor: #d6iframe: diagrams.html?d=d6§6 in the essay →