--- title: "Circles are a basic unit of shared governance" description: "When agents adopt the collective decision-making protocols together around a shared domain, the governance structure that emerges is a circle" url: "/circles-are-a-basic-unit-of-shared-governance/" tags: [foundation] readingPathPosition: 22 --- # Circles are a basic unit of shared governance The relational protocol architecture does not prescribe organisational forms. It provides a grammar – [three-layer protocols](/every-protocol-has-three-inseparable-layers.md), voluntary adoption, shared commitments – from which structure emerges. But some structural patterns recur, and it is worth naming them. The most recognisable is the *circle*. ## Circles emerge from shared protocol adoption When a group of agents adopt the [Collective decision-making](/collective-decision-making.md) protocol cluster together – [consent-based decision-making](/consent-as-default.md), [mandate clarity](/mandate-clarity.md), [open decision records](/open-decision-records.md), [role tending](/tending-shared-roles.md), [weaving](/weaving-between-circles.md) – around a shared domain, they are constituting a circle. A circle is the *name for the governance pattern that becomes visible* when this particular cluster of protocols is enacted by a group that shares accountability for an area of work and decision-making. This is not a definition imposed from above. It is a recognition: the sociocratic tradition has independently developed and tested this pattern for decades, calling it a *circle* – a self-governing group of equivalent people who collaborate to account for a domain. What Fabric adds is the three-layer discipline: every circle's governance is held through accord, ritual, and critique & contemplation, not just through rules. ## Circles are one structural form among several Circles are not the only pattern that can emerge from protocol adoption. A dyad that adopts conflict engagement protocols is not a circle – it is a relationship with committed structure. A loose network that shares information flow protocols is not a circle either. Circles are what you get specifically when a group adopts the collective decision-making cluster. Other protocol clusters produce other forms. This matters because it preserves the architecture's core freedom: agents choose which protocols to adopt, and the structural forms that result are consequences of those choices, not preconditions for them. No one needs to "join a circle" before they can participate in the network. They adopt protocols, and circles – among other patterns – crystallise from that adoption. ## What makes a circle a circle Drawing on sociocratic practice, a circle is distinguished from a working group or task team by its governance function. A team *does work* together. A circle *makes and evolves the agreements* that guide how work is done within its domain. This distinction – between *operations* and *governance* – is foundational. A group that coordinates tasks but never reflects on or revises the agreements governing those tasks is a team. A group that does both is operating as a circle. Every circle has a *[domain](/mandate-clarity.md)*: a distinct area of influence, activity, and decision-making. The circle clarifies what it is responsible for and empowered to decide – and what falls outside its boundary. Domains can contain sub-domains. When a circle delegates a sub-domain to a smaller group that also adopts the decision-making cluster, that group becomes a circle in its own right – self-governing within the constraints set by consent. This recursive capacity is one mechanism through which the network [scales](/design-for-scale.md). ## Three-layer expression Like every structural commitment in Fabric, circles are held through all [three layers](/every-protocol-has-three-inseparable-layers.md): **Accord.** A circle has a named domain, documented mandate, and explicit membership. It makes decisions by [consent](/consent-as-default.md). It maintains [Open decision records](/open-decision-records.md). Roles within the circle are selected by consent and held for defined terms (see [Tending shared roles](/tending-shared-roles.md)). **Ritual.** Circle members develop the embodied disciplines of meeting in rounds, checking in somatically before governance decisions, and holding the difference between role and person – the *role vs. soul* distinction. These practices are not add-ons; they are what make the accord layer liveable. **Critique & Contemplation.** The circle periodically asks: Has this domain become a site of accumulation? Whose voice is absent from our rounds? Does our boundary serve life or reproduce separation? Is the circle's governance enabling creative emergence or merely administering compliance? ## How circles relate to each other When multiple circles exist in the network, their domains will overlap and interlock. The decision-making cluster includes two protocols specifically for this: **Weaving.** The [Weaving between circles](/weaving-between-circles.md) protocol connects circles whose domains affect one another, through a person who participates fully in both – holding both relationships simultaneously. **Delegation.** When multiple circles need to align governance across their domains, they can form a delegate circle – each constituent circle selects a member to participate in a shared governance space. This is one possible mechanism for network-wide functions like the [wisdom function](/protocol-stewardship-is-distributed.md). ## Sources - Circle concept, governance/operations distinction, and domain model from Bockelbrink, Priest & David (2019), *Sociocracy 3.0 – A Practical Guide* - Circle concept, "role vs. soul" distinction, and governance/operations distinction from Rau (2023), *Collective Power: Patterns for a Self-Organized Future* ## In this vault - Previous: [Naming experiences is how protocols learn](/naming-experiences-is-how-protocols-learn.md) - Next: [Living systems become protocol areas](/living-systems-become-protocol-areas.md) - Referenced by: [Collective decision-making](/collective-decision-making.md), [Design for scale](/design-for-scale.md), [Living systems become protocol areas](/living-systems-become-protocol-areas.md), [Mandate clarity](/mandate-clarity.md), [Open decision records](/open-decision-records.md), [Protocol stewardship is distributed](/protocol-stewardship-is-distributed.md), [Tending shared roles](/tending-shared-roles.md), [Weaving between circles](/weaving-between-circles.md)