The Assumption

The Peeragogy Handbook identifies getting stuck as a problem of weak ties. The theory frames it as a network issue: the group lacks connections to diverse perspectives, so it cannot find a way forward. The proposed solution is to activate weak ties — reach beyond the immediate circle — and the bottleneck will dissolve through access to new information and resources.

Operational Reality

Getting stuck has two opposite causes. The wrong diagnosis makes it worse.

Perturbatore: “What if stuckness is not a network problem but an authority problem? Weak ties bring information. But information does not make a decision. Maybe the group is not stuck because it lacks connections. Maybe it is stuck because it lacks a mechanism to convert connections into decisions.”

The handbook does not name that mechanism.

Sometimes a group is stuck because nobody has the authority to decide. Power is too distributed. Everyone can block, nobody can push. The solution would be to concentrate decision-making — but flat governance ideals resist that move.

Other times a group is stuck because everybody gets to decide. Thousands of voices, each with equal weight, and nothing moves. ConstitutionDAO is the case: 17,000 token holders, one vote each, the DAO dissolved without executing its single purpose. Not because they lacked weak ties. Because they had too many decision-makers with equal power.

The weak ties framework is not wrong. It is incomplete. The bottleneck is not always who you know. Sometimes it is who can say yes — and who can say no.

Empirical Evidence

Resilience Cases (Confirming):

• GitLab Stewardship Handbook — Explicit documentation of governance boundaries between corporate sponsor and community reduces friction. When authority boundaries are clear, stuckness dissolves.
• OpenStreetMap Data Working Group — Formal dispute resolution bodies with binding authority resolve conflicts when informal consensus fails. Stuckness ends because someone — not everyone — has the last word.

Fracture Cases (Complicating):

• ConstitutionDAO Dissolution — 17,000 token holders with equal voting rights could not coordinate effectively enough to execute their single purpose. This was a failure of decision-making structure, not weak ties.
• Linux Kernel Reviewed-by Tag System — Formal peer assessment creates accountability, but the bottleneck shifts from writing code to getting it reviewed. Peer review concentrates the waiting.

Operational Heuristics

Positive Boundary: The stuck pattern works when the cause is diagnosed before the cure is applied — if nobody can decide, concentrate authority; if everybody can decide and nothing moves, reduce the number of decision-makers.

Negative Boundary: Do not apply the weak ties framework when the bottleneck is authority, not information — weak ties bring information, but information does not make a decision.

Epistemic Synthesis

Getting stuck has two opposite causes, and the wrong diagnosis makes it worse. Sometimes power is too distributed — everyone can block, nobody can push. Sometimes everybody gets to decide and nothing moves. ConstitutionDAO shows the second case: 17,000 token holders, one vote each, dissolved without executing. The weak ties framework is useful but incomplete. The bottleneck is not always who you know. Sometimes it is who can say yes — and who can say no.

Evidence Status

Status	Count
Confirmed cases	2
Cases under study	0
Unverified cases	0
Ambiguous cases	0

Traceability

Run: audit-v2 · Delta: 1.5 → 1.615 (±0.115) · Diversity D: 2

References

• GitLab Stewardship Handbook
• OpenStreetMap Data Working Group
• ConstitutionDAO Dissolution (Wired)
• Linux Kernel Submitting Patches