False Separation

It describes the misperception that parts of a system operate independently of each other. Two departments in the same company, or two nations sharing a border, aren't separate systems just because they have separate names, separate leadership, and separate accounting — they're exchanging resources, consequences, and constraints across whatever boundary was drawn between them. Acting on the assumption of separation doesn't sever the actual connection; it just means the decision gets made without accounting for effects that are still going to land. That's not a structural condition of the system. It's an error in how the system is being read.

This tends to get reinforced by whatever position someone is standing in. From inside a single department, or a single country, actions really can look self-contained — the broader relationships aren't visible from that vantage point, which makes the separation feel real rather than assumed. That's what allows the error to persist without feeling like an error: the local view is internally consistent even while it's missing the connections that make it wrong.

This is the assumption sitting underneath most of what this framework treats as incoherence — not a separate failure alongside the others, but the thing that makes the others possible. A system keeps generating costs it can't explain because it's tracking outcomes as though its parts don't touch, when they do. Correcting it doesn't require dissolving any actual boundary between parts — departments, nations, or individuals can stay genuinely distinct. It requires updating the model each part is using to include what the other parts are actually doing.