The Diagnostic

The substrate flows freely.
Until it doesn't.

On a healthy substrate, every actor's selfish action feeds the system. Signals travel. Value compounds. Connections form without anyone managing them.

Then the system stabilises. Actors adopt locally rational behaviours that prevent compounding. Not because they fail — because they're responding sensibly to the incentives they face.

These stabilisations are called stalls. When stalls reinforce each other, they form stacks. Stacks are why your cluster works hard and goes nowhere.

Complex adaptive systems

The system isn't broken.
It's stabilising.

"Every behaviour makes sense from the actor's perspective. Stalls are not failures — they are the system finding equilibria. Understanding them is the precondition for changing them."

ClusterOS Diagnostic Framework
01
Actors are locally rationalEvery behaviour that looks like dysfunction makes perfect sense from inside the actor's constraints. Stalls are sensible responses, not mistakes.
02
The system learns what reduces discomfortCoordination reduces friction, so the system coordinates more. Narrative restores confidence, so the system narrates more. Each stall is a learned response that became a default.
03
Stalls serve interests, not just learningOnce a stall entangles with roles and reputations, it is actively defended. Removing it doesn't just change behaviour — it removes someone's position.
04
Leverage means small perturbations that shift regimesNot large programmes. The goal is identifying the minimal intervention that changes the operating conditions — not fixing everything at once.
Stage 3 · Stall detection

Nine ways a cluster
stops compounding

Each stall is a behavioural substitution — the system doing something observable (X) instead of something harder (Y). Click any stall to see the full pattern. Then add it to the stack builder.

On the stack builder below: Stalls rarely operate alone. Once you understand each one, add two or three to the stack builder — and see what kind of cluster that combination describes, why single interventions fail to break it, and what the diagnostic looks for.
Swipe to explore →
Stage 4 · Stack analysis

Stacks are why single fixes fail.
Build one and see why.

A stack forms when one stall lowers the cost of another. Once that happens, stabilisation becomes anticipatory — pressure enters, the same configuration activates, and the system doesn't consciously choose the response. It's already structured to produce it.

Select 2–3 stalls from the cards above (use the "Add to stack" button), or click any stall name below.

Add at least 2 stalls to see
the stack analysis and reinforcement logic.
Stack composition
0 / 3 stalls
↑ Add stalls from the grid above
01
Select a stall...
02
Select a stall...
03
Select a stall... (optional)
Quick pick
From 75 diagnostics

Stacks we've seen
in the field

These three configurations appear repeatedly across geographies and sectors. They have different names in different ecosystems — but the reinforcement logic is the same. Recognising your stack is the first step to targeting it.

Swipe to explore →