Commitment structures inherently generate tensions between their explicit content and their actual effects. A consent protocol promises equivalence but in practice some voices carry more weight. A resource-sharing protocol promises solidarity but in practice some contributions go unrecognised. These tensions are not design flaws. They are where the architecture does its work – if they are held rather than suppressed or resolved too quickly.
The architecture currently names two domains for processing what arises in collective life: feedback and learning (surfacing information) and conflict engagement (processing rupture). Between them sits the most generative space:
Feedback surfaces information – what’s happening, what patterns are emerging, what the network is experiencing. This is descriptive: the network learning to see itself.
Tension arises when that information reveals a pull in two directions. Something a protocol promises and something it produces are in conflict. Two goods are in competition. An asymmetry is becoming visible but hasn’t yet produced specific harm. Tension is not yet conflict – no specific incident, no named parties – but it is more than information. It has directionality and energy.
Conflict emerges when a tension involves specific harm, specific parties, or has been suppressed long enough to rupture relationship. The conflict engagement protocols treat this as information and energy, feeding it back into the network’s structural learning.
The escalation from feedback through tension to conflict is not inevitable. Tension that is held – named, explored, used to generate new understanding – drives protocol evolution without becoming conflict. Tension that is suppressed or ignored accumulates until it ruptures. The primary function of critique and contemplation is to create the conditions under which tensions can be held: surfaced without being instrumentalised, explored without being forced to premature resolution.
Not all tension is equally generative. The architecture identifies two specific sources that drive protocol development:
Tension between protocol and reality. Every protocol is a hypothesis about how to relate. When it meets actual conditions of practice – needs, capacities, constraints – the gap between what it promises and what it produces becomes visible. This is the internal tension: the protocol’s aspiration measured against its effects. The current protocol that needs to change is the (internal) status quo against which critique and contemplation inquire and participants can rebel.
Tension between protocol and dominant paradigm. Every protocol also exists in tension with the social and organisational defaults it seeks to interrupt – the separation logic that shapes the conditions within which any alternative practice operates. A consent protocol operates against a background of hierarchical decision-making; a solidarity contribution protocol against extractive resource flows. Any new protocol must challenge these defaults, not merely improve on existing internal arrangements.
Research on collaborative circles confirms that such tensions, understood as shared opposition to an internal or external status quo, are what activates the deep trust and risk-taking capacity from which transformative work emerges. Without them, groups can coordinate but may not transform.
Critique and contemplation must attend to both sources simultaneously. They ask: Is this protocol falling short of its own commitments? (internal). And: Is this protocol actually challenging the dominant defaults, or has it quietly accommodated to them? (external). A protocol that resolves internal tensions but loses contact with external ones has become well-functioning governance rather than prefigurative practice. A protocol that maintains external opposition but ignores internal contradictions has become ideology rather than living commitment.
Tensions arise not only within protocols but between them. Design for asymmetry pulls against Start with simple rules. Make voice cheap pulls against Design for scale. Facilitation before formalisation pulls against the urgency of having something to adopt now. These inter-principle tensions are not bugs in the design – they are the architecture’s immune system. A framework without internal tensions has stopped thinking.
Critique and contemplation are what prevent these tensions from collapsing into either pole. They don’t resolve the tension between asymmetry and simplicity; they create the conditions under which a group can ask, in this specific situation, which pull matters more – and revisit that judgement when circumstances change.
The non-extractive framing matters. You don’t harness tensions – you hold them. Critique and contemplation don’t extract insight from discomfort; they create conditions where what is uncomfortable can speak without being instrumentalised. The ritual layer’s somatic work is precisely the capacity to remain in contact with tension without rushing to resolve it. This is what distinguishes the architecture from optimisation frameworks that treat every tension as a problem to be solved – and it is why the three layers must be inseparable. Without ritual, you lack the embodied capacity to stay with tension. Without critique and contemplation, you lack the reflective space to let it speak. Without accord, the tension has nowhere determinate to land.