Anarchy Paralysis

Why We Couldn't Act: Authority, Data, and Do-ocracy

I. INTRODUCTION: The Pattern of Paralysis

You know how sometimes in a community, multiple people recognize that harm is happening, people document it, mediators try to intervene... and yet nothing actually changes for a really long time?

This isn't because people didn't care or weren't trying. It's not because there wasn't enough evidence. It's because certain organizational infrastructures were missing.

Theoretical frame:

As Jo Freeman documented in "The Tyranny of Structurelessness" (1970),<ref>Freeman, Jo. "The Tyranny of Structurelessness." 1970.</ref> the absence of formal structure doesn't eliminate power - it makes power invisible and therefore unaccountable. In this case, the community's commitment to anarchist principles became the very mechanism that prevented anarchist action. We confused "no hierarchy" with "no one can act," turning our horizontal structure into a trap.

The anarchist paradox:

Freeman argued that "to strive for a structurelessness group is as useful, and as deceptive, as to aim at an 'objective' news story." In our case, striving for "pure consensus" became a smokescreen that allowed informal hierarchies to operate unchallenged while preventing those with legitimate standing from acting.

The question this document answers:

What structural and cultural elements need to be in place for a do-ocratic consensus anarchy to actually protect itself when harm is occurring?

II. THE FOUR MISSING INFRASTRUCTURES

A. Respect for Mediator Data

Here's something we need to talk about: we choose mediators because we trust them. We don't pick random people off the street - we ask people with experience, good judgment, and a track record of being fair. We're trusting them to do difficult, emotionally exhausting work.

So when a mediator comes back and says "this mediation failed because the person weaponized the process," that's not just their opinion. That's a professional assessment from someone we specifically chose because we trust their judgment.

What was missing:

• Recognition that failed mediation IS dispositive evidence
• Understanding that process abuse during mediation warrants immediate escalation
• Trust in the mediator's assessment as authoritative data - you know, the thing we asked them to provide

What happened instead:

• First mediator's failed mediation → "Let's try a different mediator"
• Second mediator's failed mediation → "Maybe we need more time?"
• Mediator testimony treated as "their subjective experience" rather than "diagnostic data from the expert we asked"

Why this matters:

When we dismiss mediator assessments, we're not just ignoring data - we're disrespecting their labor. We asked them to do this work, they did it, and then we act like their findings don't count. That's not just ineffective, it's disrespectful.

Mediators have the most detailed observation of behavioral patterns. They see things in that room that no one else sees. When they report back that someone is abusing the process itself, that should carry weight.

The principle:

"Failed mediation due to process abuse is conclusive data for escalation, not an invitation to try again with a different mediator."

B. Understanding Do-ocracy vs. Consensus

Let's be real: a lot of people misunderstand what "do-ocratic consensus anarchy" actually means. And that confusion can paralyze us.

Noisebridge is do-ocratic FIRST. That means: you have authority to act when you see something that needs doing. Then consensus comes in as the CHECK - the community can challenge your action, discuss it, and potentially block it. But consensus doesn't grant you permission to act in the first place.

The order is: Authority → Action → Consensus (validation)

NOT: Consensus → Authority → Action

What was missing:

• Clear understanding of what do-ocracy actually means
• Confidence that individual authority comes before consensus
• Recognition that waiting for consensus before acting isn't how this works

What happened instead:

• People waited for consensus before feeling authorized to act
• Looked for "enough agreement" to justify individual action
• Confused "consensus process" (the accountability check) with "consensus requirement" (asking permission)

The do-ocracy model:

Individual Authority → Act → Document → Community Validates/Challenges
        ↓                                           ↓
  "I see harm"                              "We agree/disagree"

The misconception:

Gather Evidence → Build Consensus → Someone Acts
                        ↓
                "Waiting for permission that never comes"

The principle:

"Do-ocracy means: Act on your authority. Consensus means: The community can challenge your action. Not: Wait for consensus to grant authority."

C. "We Are The Ones We've Been Waiting For"

Here's a hard truth: there is no "someone more legitimate" who's going to come save the day.

In anarchist spaces, authority doesn't come from your title, your seniority, or how long you've been around. It comes from doing the work. If you see harm, document it, and can defend your decision to the community, you ARE the authority. You're not waiting for permission from "the real adults in the room" - because there are no adults in the room, just peers.

What was missing:

• Recognition that authority comes from action and accountability, not position
• Understanding that "centrality" is performative, not real
• Confidence to act without waiting for validation from "someone more important"

What happened instead:

• Some community members deferred to perceived "steward consensus"
• Others waited for reactions to their proposals before moving forward
• Multiple people implicitly waited for someone perceived as "more central" to give the green light
• When a more central-seeming person took over mediation, earlier assessments seemed less legitimate by comparison

The centrality trap:

When people treat someone as "central," that person's actions and inactions become bottlenecks - even though they have no formal authority. In anarchist spaces, centrality is performative, not structural. Anyone can act. Anyone can be challenged. The moment we start waiting for "the center" to do something, we've created an informal hierarchy that doesn't officially exist but functionally paralyzes us.

The principle:

If you see harm, document it, and can defend your action - you ARE authorized. Stop waiting for someone "more important" to do it.

D. There Is No True Center

This builds on the last point, but it's important enough to say separately: we need to actively reject the idea that anyone is "central" to our community.

The moment we treat someone as the final arbiter, their inaction becomes our paralysis. And here's the kicker: they didn't ask for that role. We imposed it on them by treating them as more legitimate than ourselves. Now their willingness or unwillingness to act becomes the bottleneck.

What was missing:

• Active, conscious rejection of informal hierarchy
• Recognition that "perceived centrality" creates bottlenecks just as much as formal hierarchy does
• Understanding that treating someone as central literally makes them central

What happened instead:

• One person got treated as the final arbiter even though they had no formal authority to be one
• Their willingness to attempt mediation somehow superseded previous failed attempts
• People assumed their assessment would be "more legitimate" just because of who they were

Why this is toxic:

In anarchist spaces, informal hierarchy is actually MORE dangerous than formal hierarchy because:

1. It's invisible and therefore unaccountable - you can't challenge a structure that nobody admits exists
2. It concentrates decision-making without acknowledging it - we're doing hierarchy while claiming we're not
3. It makes people doubt their own legitimate authority - "I can't act because X hasn't weighed in yet"

The principle:

No one is "central" enough that their inaction should prevent your action. Act on your authority, defend your decision, accept challenge - but don't defer to phantoms.

III. HOW THESE FAILURES COMPOUND

The cascade effect:

1. Mediator data not respected → When a mediator's failed attempt doesn't trigger escalation
2. Waiting for consensus → Documentation efforts stop when validation doesn't materialize
3. "Someone else will do it" → People wait for validation from perceived "center"
4. Perceived centrality bottleneck → Subsequent attempts can delegitimize previous assessments → When multiple attempts fail, the system becomes stuck

Typical result:

Harm continues. People burn out. Community members leave. The person causing harm gains "missing stair" status.

IV. WHAT BREAKS THE PATTERN

The intervention:

The pattern breaks when someone:

• Treats mediator data as dispositive
• Acts on do-ocratic authority without seeking permission
• Doesn't wait for "the center" to validate
• Creates documentation as defense, not permission slip

The mechanism:

1. Respecting mediator data: "Multiple mediators failed - that IS the evidence"
2. Claiming authority: Announcing action rather than asking permission
3. Creating coordination infrastructure: Making patterns legible to enable support
4. Demonstrating there is no center: Just acting, proving centrality is performative

Why it works:

Not because of better evidence or more consensus, but because someone exercises the authority that was ALWAYS available to everyone in the community.

V. PRINCIPLES FOR FUTURE ACTION

When harm is occurring:

1. Trust mediator assessment
   • If mediation fails due to process abuse, escalate immediately
   • Don't retry with different mediators - that enables process weaponization
2. Exercise do-ocratic authority
   • Act on what you see
   • Document your reasoning
   • Be prepared to defend your decision
   • Accept that community can challenge you
3. Don't wait for the center
   • There is no one "more authorized" than you
   • If you see it, you have standing
   • Others' inaction doesn't invalidate your action
4. Create coordination infrastructure
   • Make patterns legible for others
   • But don't mistake "making it legible" for "asking permission"
   • Documentation enables others to support you, not to authorize you

The anarchist responsibility:

In anarchist spaces, authority is distributed. This means:

• You HAVE authority to act
• You MUST accept accountability for your actions
• You CANNOT defer to hierarchy (formal or informal)
• The community validates/challenges AFTER, not before

VI. THE TWO KINDS OF "NAMING"

Why "I documented it" isn't always enough:

There are two types of articulation:

Phenomenological naming:

• "They misrepresent things"
• "They create confusion"
• "They attack when disagreed with"
• "They're manipulative"

This describes EXPERIENCE but doesn't create FRAMEWORK.

Structural naming:

• Maps specific behaviors to conflict escalation stages
• Provides comparative frequency data
• Names recognizable antipatterns
• Offers diagnostic criteria

The difference:

Phenomenological naming lets people validate your experience ("yes, I feel that too").

Structural naming lets people coordinate action ("here's what we're responding to").

Why this matters:

In technical spaces, coordination requires systematic frameworks. Not because feelings aren't valid, but because people need translatable patterns to defend decisions they make.

The documentation doesn't replace feelings as authorization. It makes feelings coordinatable.

VII. APPLICATION BEYOND ANY SPECIFIC CASE

This pattern repeats whenever:

• Someone causes diffuse harm that's hard to articulate
• Multiple people recognize it but feel unable to act
• Informal hierarchy creates bottlenecks
• "Consensus" is confused with "permission to act"

The test:

If you're waiting for someone else to act because:

• They're "more central"
• They're "more legitimate"
• "Everyone needs to agree first"
• "I need more evidence"

→ You're in this failure mode.

The check:

Ask yourself:

1. Can I articulate the harm? (yes/no)
2. Can I defend my action? (yes/no)
3. Am I prepared to be challenged? (yes/no)

If yes to all three: You have authority to act.

VIII. CONCLUSION

Anarchist authority is:

• Distributed (everyone has it)
• Exercised through action (not granted through consensus)
• Validated through community response (not pre-authorized)
• Based on standing (you did the work to see/document)

What this pattern teaches us:

The infrastructure we need isn't:

• More evidence
• More consensus
• More central authority

It is:

• Respect for expertise (mediator data as dispositive)
• Understanding of our own model (do-ocracy first, consensus second)
• Confidence in distributed authority ("we are the ones")
• Rejection of informal hierarchy ("no center exists")

Going forward:

When you see harm, you don't need permission to act. You need courage to claim the authority you already have, and discipline to defend your decision to the community.

That's what anarchist responsibility looks like.

References

<references />