The Assumption
Antipatterns are recognizable dysfunctional patterns that lead to negative outcomes despite appearing reasonable at first glance. The handbook catalogs specific failure modes — consensus-paralysis, authority-attrition, free-rider problems — with the implicit claim that recognition enables prevention.
Operational Reality
The Peeragogy Handbook lists six antipatterns like items in a field guide to dysfunction. Stuck. Magical Thinking. Stasis. Each gets its own definition, its own boundaries. The assumption runs deeper than the categories: that naming the problem solves half of it.
But Wikipedia’s consensus processes expose the gap. The project formally operates on peer equality, yet participation inequality creates de facto hierarchies. Those who show up consistently gain disproportionate influence — not through declared authority but through sustained presence. This antipattern is not in the handbook. It emerges from the very solution the handbook would prescribe.
GitLab shows that designing governance boundaries in advance prevents the most common antipatterns. OpenStreetMap shows that formal dispute resolution bodies are required for what informal consensus cannot resolve. WebAssembly shows that every governance choice prevents one antipattern while creating another. Wikipedia Articles for Deletion shows that consensus processes produce de facto hierarchies through participation inequality — the antipattern is not a bug but an emergent property of how peer production scales.
Empirical Evidence
Resilience Cases (Confirming):
- GitLab Stewardship Handbook — Explicit documentation of governance boundaries between corporate sponsor and community reduces friction. Designing boundaries in advance prevents the most common antipatterns.
- OpenStreetMap Data Working Group — Formal dispute resolution bodies with binding authority resolve peer production conflicts that informal consensus cannot. Some antipatterns require formal mechanisms, not just awareness.
Fracture Cases (Complicating):
- WebAssembly Community Group — Lighter governance prevents bureaucracy but creates speed-versus-consensus trade-offs. Every governance choice prevents one antipattern while creating another.
- Wikipedia Articles for Deletion — Consensus processes produce de facto hierarchies through participation inequality. The antipattern is not a bug but an emergent property of how peer production scales.
Operational Heuristics
Positive Boundary: Apply antipattern analysis only when combined with explicit governance trade-off documentation — identifying failure modes is useful when paired with design decisions that address them.
Negative Boundary: Do not use antipattern recognition as a cure for governance dysfunction — antipatterns are emergent properties of governance choices, and knowing their name does not prevent them.
Epistemic Synthesis
The central assumption — that recognizing antipatterns prevents their recurrence — is structurally contradicted by the evidence. Antipatterns are not bugs to fix but emergent properties of governance choices. Every governance choice prevents some antipatterns and creates others. The theoretical pattern is useful only if reread as a map of trade-offs, not as a diagnosis.
Perturbatore: “What if knowing the name of your dysfunction does not cure it — it just makes you sound smarter while you repeat it?”
Naming the wound does not close it.
Evidence Status
| Status |
Count |
| Confirmed cases |
2 |
| Cases under study |
2 |
| Unverified cases |
0 |
| Ambiguous cases |
0 |
Traceability
Run: audit-v2 · Delta: 1.5 → 1.52 · Diversity D: 2
References