Law 1 of 12 in the Hacker Laws for Agentic Software Engineering series — read the index. Next: Brooks' Law.
The Law
The technical boundaries of a system will reflect the structure of the organisation. (hacker-laws)
The Key Insight for Agentic Software Engineering
Conway's Law was about the org chart, and the org chart just changed: it now includes the agents, and — more importantly — the harness that wires them. In an agentic software engineering shop, the structure that shapes the software is not only who reports to whom; it is how the agents communicate, what shared state they read, which delegations are allowed, and where the verifiers sit. The software will mirror that topology, because the topology decides what each agent can see and therefore what it can build. Give two agents the same repository but different shared-state boundaries and they will produce systems with seams in different places — the seam lands where the communication seam lands.
The harness is the org chart. The orchestrator-worker topology produces central-plan, delegated-feature systems; the blackboard topology produces choreographed, shared-state systems; the sequential pipeline topology produces layered, linear systems. The model is the same in all three — the topology is what changes, and the topology is a harness decision, not a model decision (the system, not the agent).
The flip side is sharper: agents also mirror each other. The distillation loop — small models trained on a large model's outputs — makes the "organisation" a single voice, and the software it produces is correspondingly single-voiced. When the agentic org has one mind, the software has one architecture, for better and for worse; when it has many independent minds with narrow channels between them, the software is modular in exactly the places the channels are narrow.
The ASE reading of Conway's Law: the software will mirror the topology of the agents that made it, so design the topology — the harness — to get the seams you want. If you want modular systems, make the communication channels between agents narrow and the shared state explicit; if you want integrated systems, wire the agents tightly. The law was never an excuse for the org chart; it was an instruction to take the org chart seriously. In agentic software engineering, the org chart is a file you can edit.
References
- dwmkerr. hacker-laws — Conway's Law and Conway's Law on Wikipedia.
- This blog's Harnessing Agentic AI Systems series — orchestrator-worker, blackboard, sequential pipeline routing.
- Agents Aren't Magic. They're Distillation at Scale. — the single-voice organisation.