Doocracy

A governance pattern where authority flows to whoever shows up and does the work. Common in open-source projects, Burning Man camps, and seasonal communities like Feÿtopia.

What it is, and what it is for

Doocracy is a governance pattern. The rule is one sentence. Whoever does the work decides how it gets done. Authority flows to the doer through the act of doing, not through a title, a vote, or a formal mandate.

The canonical short definition comes from CommunityWiki, where the term entered the community-organizing vocabulary in the early 2000s: "A do-ocracy is an organizational structure in which individuals choose roles and tasks for themselves and execute them. Responsibilities attach to people who do the work, rather than elected or selected officials." The same definition shows up across Burning Man theme camp culture, Wikimedia editorial life, and most of the open-source software world.

The pattern fits a particular kind of group. Small enough that the doers are visible to each other. Voluntary enough that the people doing the work are also the people who care most about the work. Warm enough that someone walking past a half-built kitchen feels free to pick up a hammer. Doocracy works less well when the group is big enough that the doers are anonymous to each other, when participation is mandatory, or when the work is the kind that requires formal accountability before it begins (legal, financial, safety-critical, anything affecting people who are not in the room).

It is a pattern at the relational and operational layer, not the constitutional layer. A community can practice doocracy in its daily life and still hold a formal annual general meeting about ownership, finance, or membership. Most communities that name doocracy are doing this layered move, not running their entire governance through it. The Feÿtopia community card on Base44 names it explicitly: "Legal authority and strategic direction remain centralized within the ownership structure. During the seasonal community period, daily life operates through informal doocracy."

FROM THE FIELD. Across the Feÿtopia archive, every interview that touches governance returns to the same observation. The community has no formal voting and no written bylaws, and yet rooms get built, kitchens get run, salons get programmed, and a hundred small decisions a week get made. The pattern that holds it is doocracy, layered onto an institutional scaffold of private ownership and seasonal residency. This entry draws on six cleaned interviews from the 2024 to 2026 archive: Jess, Mathieu, Lucy, Shelby, Poli, and Amy.

Where it came from

Doocracy did not have one founder. It had several origin streams that converged on the same operating idea in the late 1990s and early 2000s.

The first stream is open-source software. Linux kernel development under Linus Torvalds in the 1990s, the Apache Software Foundation through the 2000s, and the broader open-source ethic produced a working consensus that the person who wrote the patch was the person who decided how the feature worked. The phrase "rough consensus and running code," from the IETF in the 1980s, captured an adjacent idea: the working software is the decision. Doocracy formalized the corollary. Whoever wrote the working software is the one who decided.

The second stream is Indymedia and the late-1990s alterglobalization activist scene. Independent Media Centers built around protest events in Seattle, Genoa, and elsewhere had to coordinate fast across people who had just met. The working pattern was that whoever showed up at the IMC space and started doing something useful (editing video, writing copy, running tech support) was the person who held that role for as long as they kept showing up. The label "do-ocracy" appears in Indymedia internal documentation by the early 2000s.

The third stream is Burning Man and its theme camp culture. The Ten Principles, written by Larry Harvey in 2004, name "Radical Self-Reliance" and "Communal Effort" as foundational. Theme camp organizers describe what they actually do as "doing it themselves until someone helps." The Burning Man regional network and Burner Without Borders carried the pattern outward. Sharon's own founding work on Midburn, the Israeli regional Burner event, sits inside this lineage and has surfaced doocratic dynamics across multiple camp generations.

The label itself was lifted from these streams into the community-wiki and intentional-community vocabulary by 2003 to 2005, where it has stayed. It is a working term, not a trademark. No central body maintains the definition. The Embassy Network's own design-patterns documentation, written between 2014 and 2019, is one of the more careful articulations of the pattern as a deliberate organizational choice rather than as an emergent default.

There is no single rough period or controversy. The pattern's controversy is structural and is best named through the critique that has shadowed it from the start. Jo Freeman's 1972 essay The Tyranny of Structurelessness (separate Library entry, forthcoming) was written before the term doocracy existed, but its argument applies. The claim "no one is in charge" elides who actually holds the room. Doocracy without naming the unwritten rules and the unwritten authority produces hidden hierarchies that are harder to challenge than written ones. Most contemporary articulations of doocracy treat Freeman's critique as a friendly amendment rather than a refutation.

How it actually runs

The pattern has the same shape across communities that practice it. Variations show up in how much the unwritten rules are surfaced, how much initiative is tracked, and how the doocratic layer interacts with the institutional scaffold underneath.

The trigger

Someone notices that something needs doing. A kitchen needs reorganizing. A workshop needs running. A guest needs picking up from the train. A bug needs fixing. The trigger is almost always a noticed gap, not an assigned task.

The act

The person who noticed picks it up. They do not first ask permission, file a proposal, or convene a circle. The act is the proposal. If the act is small (move a chair, plug in a light, refill the coffee), it stays invisible. If the act is bigger (build a sauna, host a salon series, set up a community AI server), it becomes legible to the rest of the group through what gets built.

The check-in

The doocratic act runs into the rest of the community at one of three layers. First, the relational layer: a friend mentions it over dinner, a question gets raised in the WhatsApp, the doer asks for a hand. Second, the institutional scaffold: the doer hits a constraint they cannot resolve themselves (the building's heritage status, a budget line, a safety question) and the conversation moves to whoever holds that authority. Third, the cultural memory layer: someone from the inner circle of long-time residents notices the act and either supports it or names a concern.

At Feÿtopia, the inner circle is what residents call the OG generation, or "Tolkiens." Jess, the founder, describes it in her second interview: "I spend maybe an hour per week talking to Shelby." The OG-Tolkiens layer is roughly ten long-time community members and ten staff team members held in informal alignment through a WhatsApp group. Conflict resolution at this layer operates through what Jess calls "not being proud" rather than through formal procedure.

The veto

In a doocracy, the veto is rare and held in reserve. The Feÿtopia archive contains one cleanly documented instance. A member proposed installing a climbing wall in the château. The founder said no. Her stated reason was the heritage status of the building. The story is told because it is unusual. A doocracy that vetoes often is not really a doocracy. It is a soft autocracy with extra steps.

The role drift

A doocratic role is held by the person doing the work. When that person stops, the role either drifts to the next doer or disappears. Roles do not carry forward through formal handoff. They carry forward through the next person noticing the same gap. This is one of the pattern's strengths (no formal succession needed) and one of its costs (no formal succession means no formal continuity).

A real moment

From Poli's interview at Feÿtopia. A visitor came to the château with a conflict the visitor wanted resolved. The visitor asked the residents who was in charge. The residents answered that no one was in charge, that the community ran itself. The visitor responded with the question that names the pattern's contradiction precisely: "Can you bring me to the person that makes sure that there is no person in charge?"

The question is operationally serious. Poli's answer in the interview is that doocracy works at Feÿtopia only because there is an institutional scaffold underneath it. The château has a CEO, a staff, a legal entity. The community is permeable, not autonomous. Doocracy is the operating mode of the seasonal community, layered onto a private-ownership scaffold that the community does not control.

What it is and what it is not

Five common confusions worth naming directly.

Doocracy assumes voluntary entry into the doing. Anyone who shows up has the option to do or not to do. Coercion breaks the pattern. A workplace where management uses the language of doocracy to push hidden labor onto contributors is not a doocracy. It is a labor extraction with a friendlier name.

Doocracy assumes the doers are visible to each other. When the group is small enough that you can see who is hauling firewood, the pattern self-corrects through gratitude, recognition, and informal pressure. When the group scales past the visibility threshold (somewhere between thirty and a hundred and fifty people, depending on the group), informal recognition stops working and the pattern produces invisible labor.

Doocracy is not a substitute for formal decision-making on bounded categories. Ownership, finance, safety, membership boundaries, conflict that has escalated past the relational layer. These are not doocratic territory. Most communities that practice doocracy run a formal layer for these decisions and a doocratic layer for the operational and cultural life that fills the days. Stripping the formal layer is what Freeman warned against in 1972.

Doocracy differs from Holacracy (separate Library entry, forthcoming). Holacracy formalizes role-based authority through a written constitution, explicit role descriptions, and tactical and governance meetings. Doocracy is the opposite move. Authority is not formalized. The two patterns can pair (a Holacracy-running organization can have doocratic edges) but they are different in lineage and form.

Doocracy differs from Sociocracy. Sociocracy 3.0 is grounded in explicit consent-based decision-making, double-linked circles, and pattern-by-pattern adoption. The S3 phrase is "good enough for now, safe enough to try." Doocracy bypasses the consent step and lets the safety question be answered by the doer alone. The two patterns can pair at different layers (a community can run S3 for its annual planning and doocracy for its daily life) but the consent step is what makes the difference.

Doocracy is sometimes confused with stigmergy (separate Library entry, forthcoming) although the two operate at different levels. Stigmergy is environment-mediated coordination. Ants leaving pheromone trails. Termites building mounds. Wikipedia editors finding work to do because of the visible state of the page. Doocracy is the operating principle that says whoever is doing the work has authority over how it gets done. Stigmergy is one of the mechanisms by which doocratic groups coordinate (the visible state of the kitchen is the signal that the kitchen needs work) but the two operate at different levels of analysis.

Communities practicing it

Three communities in the ToGather archive, plus three external networks that name doocracy in their own self-description.

Located at Château du Feÿ in the Yonne department of Burgundy. Approximately twenty-five to forty residents during the winter season, January to April. Hybrid governance: the château is privately owned through a corporate entity with Jess as CEO; the seasonal community operates through doocracy. The Base44 community card names the pattern directly: "Cultural programming, shared labor, and social norms emerge through participation rather than formal voting structures."

The Feÿtopia archive includes interviews with Jess, Mathieu (co-founder), Lucy Foster (third-year resident, season lead during 2025), Shelby McAuliffe (admin lead for two seasons), Poli (multi-season resident, AI engineer), and Amy Van Doren (third-year resident, runs communities in New York). The pattern shows up differently in each interview. Jess names it as "thousands of compromises, we don't compromise on fun." The long list of doocratic accommodations and the short list of non-negotiables. Mathieu traces the lineage back to his earlier community Mangrove, founded in 2016 in Morocco after reading Reinventing Organizations, where the same operating principle was already in use. Poli surfaces the structural condition: doocracy needs an institutional scaffold to work at all.

A network of co-living houses in San Francisco, Oakland, Berlin, and elsewhere that explicitly named "Do-ocracy" as one of its design patterns. The Embassy Network's design-patterns documentation is one of the cleaner published articulations of doocracy as a deliberate organizational choice. Although the network as a formal entity wound down around 2020, its design patterns continue to be used by successor communities and the documentation remains available.

Most large open-source software projects (Linux, Wikipedia, Apache, Python, Mozilla) operate doocratically at the contributor layer with a formal governance scaffold above. The Linux kernel has Linus Torvalds and a benevolent-dictatorship layer. Wikipedia has the Wikimedia Foundation. Apache has the Apache Software Foundation. The pattern is the same: the contributor who does the work shapes the work, and the formal governance handles the bounded categories (legal, financial, brand, conflict escalation) that the contributor layer cannot resolve itself.

FROM THE FIELD. The pattern that holds across these three communities is the pairing. None of them runs on doocracy alone. Each pairs a doocratic operational layer with a formal scaffold for the bounded categories. Feÿtopia has the privately owned château. Embassy Network had a network-level governance body. Open-source projects have foundations. The communities that have tried to run on doocracy alone, without the scaffold, are mostly the ones that fell apart at the year-three mark when the original doer cohort left and there was no formal continuity to inherit.

How to begin practicing this in your own group

Six steps. Verb-first.

1. Confirm the group is small enough. Doocracy works in groups where the doers are visible to each other. The rough threshold is thirty people for high-trust groups and a hundred and fifty for groups that use loose social networks to maintain visibility. Above the threshold, the pattern produces invisible labor. If the group is bigger, run doocracy at the sub-group layer (theme camp, working group, neighborhood) and run a different pattern above.

2. Name the institutional scaffold underneath. What is the formal layer that handles ownership, finance, safety, membership, and conflict that has escalated past the relational layer? If the group cannot answer this question, it is not running doocracy. It is running an unscaffolded pattern that will produce a year-three crisis. Name the scaffold before the doocracy starts. At Feÿtopia the scaffold is the corporate ownership of the château. In an open-source project it is the governing foundation. In a co-living house it is the lease and the legal entity.

3. Make the inner circle visible to itself. Most doocracies have an OG-Tolkiens-equivalent layer. The long-time members who hold the cultural memory and the unwritten rules. This layer exists whether or not it is named. Name it. A WhatsApp group, a regular check-in, a stated list of who is in the inner circle right now. The Tyranny of Structurelessness critique loses force when the inner circle is named because the unwritten authority becomes legible enough to be challenged.

4. Develop the supporting skill of conflict-without-procedure. Doocracy has no formal conflict procedure to fall back on. The supporting skill is the personal disposition that allows conflict to resolve at the relational layer. Jess names it as "I never fight to the end. I'm never proud. I don't understand people who cannot apologise." This is not a transferable instruction. It is a disposition that needs its own development track. Most doocracies that fail, fail because the supporting disposition is held by the founder alone and does not transmit to the second generation.

5. Pair with a relational practice. Tamera Forum at Tamera, ZEGG Forum at ZEGG (separate Library entry, forthcoming), council circles, group dialogue practices: any practice that gives the group a regular surface for naming what is happening underneath. Doocracy without a relational practice produces hidden labor and hidden conflict. The pairing becomes essential once the group is past its first year.

6. Plan the year-three reckoning. Most doocracies hit a year-three to year-five moment when the original doer cohort starts to burn out, the inner circle starts to feel its informal authority, and the question "what is this place actually" becomes urgent. Feÿtopia is in this reckoning right now at year ten. The community held a visioning session in April 2026 to work through it. The honest planning move is to put the reckoning on the calendar from year zero. A formal review at year three. A handoff plan locked at year five. Not "we will figure it out as we grow."

Living examples and entry points for community builders

Where doocracy is alive in 2026, and how to engage with it without falling into the patterns it produces when it is unscaffolded.

Living examples

Feÿtopia (Burgundy, France). The clearest seasonal-residential example documented in the ToGather archive. The 2026 visioning session is publicly named as a year-ten transition out of "benevolent dictatorship" toward something more shared. Worth watching how the transition resolves.

Wikipedia and the Wikimedia projects (distributed). The largest doocratic experiment in the world by participant count. Anyone can edit. The doers shape the encyclopedia. The Wikimedia Foundation handles the bounded categories. The English Wikipedia's policies and guidelines pages are an unusual public archive of how doocracy negotiates with itself across millions of contributors. Start at en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines.

Burning Man theme camps (Black Rock City, Nevada, and regional events worldwide). Roughly twelve hundred theme camps each year, most operating doocratically inside the larger event scaffold. Camp leads describe the pattern as "do it yourself until someone helps." See burningman.org for the camp organizer guide.

The CommunityWiki Do-ocracy page (communitywiki.org/wiki/DoOcracy). The canonical text reference for the pattern as it entered the community-organizing vocabulary. Also worth reading the linked critique pages on the same wiki.

Adjacent and inspired applications

Maker spaces and hackerspaces (worldwide). Most operate doocratically at the contribution layer. Whoever maintains the laser cutter is the person who decides how the laser cutter works. The pattern is well-documented in the hackerspaces.org wiki.

Sociocratic organizations layering doocracy at the operational tier. Many Sociocracy 3.0-running organizations explicitly delegate operational decisions to the doer through patterns like "Driver" and "Effective Action." The S3 pattern library is consistent with doocracy at the operational layer.

Mutual aid networks and disaster-response collectives. Whoever shows up to the food distribution organizes the food distribution. The institutional scaffold is often a small fiscal sponsor or a community organization. The pattern is doocratic in operation, sponsored in form.

Entry points

Read the CommunityWiki Do-ocracy page (communitywiki.org/wiki/DoOcracy). Twenty minutes. Then read the Tyranny of Structurelessness critique alongside (Variant F entry forthcoming). The two together are the minimum viable orientation.

Visit Feÿtopia for a residency during a winter season. The community accepts applications through its own channels. A two-week visit is enough to see the pattern in operation. A full season is enough to see the costs.

Run a doocratic theme camp at a regional Burning Man event. The Israeli, German, French, and other regional events have lower barriers to entry than the Black Rock City event. The camp organizer guide for any of these events is a working introduction to doocracy in practice.

Read the design-patterns documentation from Embassy Network. One of the cleaner published articulations of doocracy as a deliberate choice rather than a default. The patterns are reusable.

Sit with the question Poli's visitor asked. Can you bring me to the person who makes sure there is no person in charge? In your own community, who is that person right now? Is the answer named, or unwritten? The answer is doocracy's diagnostic question.

One caution

Doocracy without an institutional scaffold and without a named inner circle produces hidden hierarchies, invisible labor, and a year-three crisis. The pattern is not a way to avoid governance. The pattern is a way to layer informal operation on top of formal scaffolding. Communities that adopt the language of doocracy to skip the formal scaffolding work are walking into the trap Jo Freeman named in 1972. Read the critique before adopting the pattern.

Where it gets hard

Five tensions, each grounded in archive material or published critique.

The hidden labor tension

Lucy Foster's interview at Feÿtopia is the cleanest archive documentation. She stepped into a season-lead role during the founder's maternity leave. The role was framed as "one hour a day of check-ins." It became "all of the responsibilities, none of the authority, and an endless stream of people asking me questions." She was pulled out for two weeks before, in her own words, she "killed someone." The doocratic pattern produces this kind of hidden labor whenever the visibility threshold is crossed and there is no formal authority to set limits. Shelby McAuliffe's interview covers the same dynamic from the admin-lead perspective: gatekeeping decisions, access dilemmas, and the slow accumulation of informal responsibility.

The cultural-memory transmission tension

Doocracy depends on an inner circle that holds the cultural memory and the unwritten rules. At Feÿtopia, this is the OG-Tolkiens layer. The pattern is stable as long as the inner circle holds. The hard moment comes when the inner circle starts to leave, age out, or disagree among themselves about what the unwritten rules actually are. The next generation of doers does not have the same access to the cultural memory because the rules were never written down. Feÿtopia is in this reckoning at year ten. The visioning session in April 2026 is a deliberate attempt to surface the unwritten rules before the inner circle fully turns over.

The Tyranny of Structurelessness tension

Jo Freeman's 1972 critique is the structural objection to doocracy. The claim "no one is in charge" elides the people who are actually in charge. Without naming the unwritten authority, the unwritten authority becomes harder to challenge than written authority would be. Most contemporary defenses of doocracy treat Freeman's critique as a friendly amendment: name the inner circle, name the unwritten rules, name the supporting skills the pattern requires. Communities that ignore the critique reproduce its predictions.

The cross-cultural transfer tension

Doocracy carries cultural assumptions that travel poorly. The pattern works in groups where assertive initiative is rewarded and where the cost of speaking up is low. It works less well where formal hierarchy is the cultural default, where the cost of speaking up is high, where labor is gendered or racialized in ways that the doers do not name. A doocratic community that does not surface its cultural assumptions reproduces the patterns of the broader culture it is embedded in. The labor that gets done invisibly is the labor that the surrounding culture does not see.

The year-three reckoning

Most doocratic communities hit a moment, somewhere between year three and year five, when the original founder-doer is still doing more than is sustainable, the inner circle is still operating informally, and the question "what is this place actually for" becomes urgent. The reckoning either produces a more formal layer (a constitution, a board, a named succession plan) or it produces a slow drift toward founder burnout and community decline. Feÿtopia is in the year-ten version of this reckoning right now. Jess in her fundraising interview names Burning Man's Ten Principles as a precedent: "The ten principles of Burning Man were born like eighteen years after the project. I think it's time we write our ten principles."

The honest read of the archive is that the doocratic pattern is good for the founding years and harder to sustain through the second decade. Communities that survive the second decade either formalize parts of the pattern, hand off to a new doer cohort, or accept a smaller and slower version of themselves. Whichever path the community chooses, the reckoning is the work.

More resources

Canonical primary sources

• CommunityWiki: Do-ocracy (communitywiki.org/wiki/DoOcracy). The canonical text reference. Short, working, written by the people who lifted the term into community-organizing vocabulary.
• Embassy Network design patterns (Library entry). Doocracy as one of several deliberate organizational design patterns. The cleaner published articulation.
• Burning Man Ten Principles (burningman.org/about/10-principles). Larry Harvey, 2004. The cultural scaffolding that holds doocracy at Burning Man theme camps. Variant B Library entry forthcoming.

Trainings and residencies

• Feÿtopia winter season (feytopia.com or apply through the community's channels). January to April annually. A two-week stay is enough to see the pattern. A full season is enough to see the costs.
• Burning Man regional events. The Israeli (Midburn), German, French, and other regional Burner events accept camp organizer applications. The camp organizer guide is a working introduction.
• Hackerspaces and maker spaces in most major cities. Doocratic operation at small scale, low commitment, easy entry.

Theoretical lineage

• The Tyranny of Structurelessness by Jo Freeman, 1972 (Variant F Library entry, forthcoming). The structural critique. Required reading before adopting the pattern.
• The Cathedral and the Bazaar by Eric S. Raymond, 1997. The argument that open-source development outperforms closed-source through doocratic contribution. Foundational for the open-source stream.
• Reinventing Organizations by Frédéric Laloux, 2014 (Variant C Library entry, forthcoming). Self-management at the organizational layer. Mathieu names this book in his interview as the text that shaped the founding of his earlier community Mangrove and, indirectly, the founding culture of Feÿtopia.

Companion frameworks

• Embassy Network: Design Patterns and Do-ocracy. Doocracy as one of several named patterns.
• Sociocracy 3.0. The contrast: explicit consent-based decision-making.
• Tamera Forum. The relational layer that pairs with doocracy in many communities.
• Stigmergy (Variant A Library entry, forthcoming). The coordination mechanism doocratic groups often use without naming.
• The Tyranny of Structurelessness (Variant F Library entry, forthcoming). The critical companion. Required.
• Holacracy (Variant A Library entry, forthcoming). The formalized opposite.

From the ToGather archive

• Poli (Feÿtopia). Multi-season resident, AI engineer. The "membrane structure" framing. Interview file: Substack/Communities/Feytopia/interview_poli_feytopia.md. Not yet published as a Base44 Interview entity.
• Jess (Feÿtopia). Founder. The "thousands of compromises" methodology and the climbing-wall veto story. Interview files: interview_jessica_feytopia.md, interview_jessica_feytopia_part2.md, interview_jessica_feytopia_fundraising.md.
• Lucy Foster (Feÿtopia). Third-year resident, season lead. The hidden-labor documentation. File: interview_lucy_feytopia.md.
• Shelby McAuliffe (Feÿtopia). Five-season resident, admin lead. Gatekeeping and access dilemmas. File: interview_shelby_feytopia.md.
• Mathieu (Feÿtopia). Co-founder. The 2020 founding and the lineage to Mangrove and Reinventing Organizations. File: interview_mathieu_feytopia.md.
• Amy Van Doren (Feÿtopia). Third-year resident. The cross-city network pattern. File: interview_amy_feytopia.md.

When the Feÿtopia interviews are synced to Base44 as Interview entities, this section will be revised to link to each one directly.