FrameworkCompositionNaming & vocabulary
The Four Slots
Anything that has to navigate complexity and not fall apart is the same four things plus the connections between them. The slot you can't answer cleanly is the bug.
The shape
Anything that has to navigate complexity and not fall apart — a business, an AI agent, a team, a life, an expedition — is the same four things plus the connections between them:
- Something that steers. The thing making the moment-to-moment decisions. (Who/what is the pilot?)
- Something that carries. The infrastructure that moves the work through the environment.
- Something that keeps it aligned. The part that periodically asks "are we still doing the thing we set out to do?" and corrects when the answer is no.
- The defined ways the pieces talk. The explicit protocol for how the parts hand off to each other — not "they can communicate" but "there are rules for how they communicate."
That's it. Four slots and the loops between them. Every system you've ever seen that works has all four filled and connected; every system that's quietly broken has one of them missing or undefined.
Why it matters
When a system feels chaotic — your business, your agent, your week — the instinct is to add more: more tools, more people, more effort, more detail. That instinct is almost always wrong, because the problem is rarely a missing capability. It's a missing slot. The most common missing slot, by far, is the alignment one: nobody and nothing is checking whether all the busy activity still serves the original goal. The system is productive and drifting at the same time.
The power of the four slots is that it turns "everything feels wrong, I don't know where to start" into a finite diagnosis. You stop staring at a blob and start asking four answerable questions. And the empty slot — the one where the answer feels weird or forced — is the bug. Not "might be." Is. Every time.
How to think with it
- Take the thing that's overwhelming you. Don't try to fix it. Just try to name its four slots.
- For each slot, ask the plain-language question: Who steers? What carries? What keeps it aligned? How do the pieces actually talk to each other?
- The slot you can't answer cleanly is where the failure lives. The fix is to fill that slot, not to work harder on the slots that were already fine.
- Notice that this composes upward and downward: the same four slots apply to your whole company, to one workflow inside it, and to a single collaboration session — same questions, different altitude.
Honest caveat. What this doesn't cover: how to make the four slots binding in a running system, so the alignment check fires whether or not anyone remembers to look.
Distilled from: soseeh · mission control · interaction loop · halo · shell