A team cannot meaningfully organize its own work if every decision must be approved elsewhere. A circle with a domain combines a group of people with an explicit area of responsibility: what it is expected to accomplish, what resources it may use, and which decisions belong to it.

In Sociocracy 3.0's circle pattern, members share responsibility for governing their domain within agreed constraints. The circle is more than a new name for a department. Its practical significance comes from authority that members can actually exercise together.

The edge of the circle matters

A community center might give a programming circle responsibility for events and a building circle responsibility for the premises. The first could choose speakers within its budget; the second could arrange repairs. A large evening event creates an overlap involving opening hours, noise, and staffing.

Domains therefore need interfaces, not just borders. Teams must know when to coordinate, when another circle's consent is needed, and where an unresolved conflict goes. Excessively narrow domains send every useful change across several approval boundaries; vague ones let confident people expand their authority informally. Clear domains make initiative more realistic by showing both what a circle can decide and what it cannot promise on everybody else's behalf.

Real cases