infrastructure claim
The socio-emotional layer
Emotional safety, ritual design and conflict resolution treated as engineered infrastructure with the same rigour as the ledger — and the specific ways that goes wrong.
The most distinctive claim in the framework is also the easiest to dismiss: that psychological safety, ritual, and conflict resolution are infrastructure — designed, maintained, and load-bearing — rather than culture.
The argument is that every organization already runs on this layer. It is simply undesigned, which means it defaults to whatever the founders happened to model and whatever the most forceful personalities enforce. Refusing to design it does not produce neutrality; it produces an unowned system nobody can debug.
So the framework specifies it: explicit conflict-resolution mechanisms, designed rituals that carry meaning rather than filling calendar slots, and emotional safety as a maintained property with named failure modes.
CECOSESOLA is the proof of concept, and it is a serious one — roughly twenty thousand members across dozens of cooperatives, coordinated for decades with no permanent managerial roles and no formal votes, held together by continuous open-ended conversation about operations and values. Not a thought experiment.
Where it is fragile
This layer has two documented ways of turning toxic, and both are worth stating as plainly as the benefits.
Therapy creep. Personal healing gets confused with collective organizational mandate. Operational work grinds to a halt inside open-ended relational processing that has no completion condition. The organization stops being able to ship, and objecting to that makes you the problem.
Feedback weaponization. Under the banner of safety, peer feedback and alignment metrics become instruments for asserting status, settling grievances, and enforcing shadow hierarchies. This is strictly worse than transparent management, because the power is real and the accountability is not.
Both are failure modes of the mechanism working as designed, not of it being ignored. Any serious implementation needs hard boundaries on scope — and someone with standing to say this conversation is not an organizational matter.