Architecture
The Road, Not One Vehicle's Stack
Find the perspective that matches what you're actually trying to do
Architecture, here, means what it means for a building: not the materials, but the plan that decides how the parts relate — what connects to what, what has to pass through what, what's load-bearing.
Most conversations about AI infrastructure default to "the stack" — a specific tower of tools, built for one vehicle, tied to one vendor. This is a different claim. A stack is one vehicle. This is the road. The point isn't which agent drives on it. The point is that any agent could — merging in at a marked on-ramp, under the same signals as everyone else.
Find your on-ramp
The Three Perspectives
Systems Perspective
The engineering theory underneath everything else — feedback, requisite variety, why this shape holds together at all. For anyone who wants the "why," not just the "what."
Process Perspective
Signalling, safety, governance, identification, boundaries. The rules of the road — checkpoints, right-of-way, who has to identify themselves before merging in.
Infrastructure
The carrier itself. What's actually read, passed, and forwarded — and what makes it something a distributed operation can trust to keep carrying it. If you're bringing your own stack, this is the one page you need.
Each perspective goes as deep as you want to follow it, down to the individual mechanisms themselves. For the precise definitions, see the Lexicon. For why plain language wasn't always enough to begin with, see Philosophy. And for the essay this whole hub's traffic metaphor was first argued in full, see The Infrastructure of Reasoning.