📖 Source→⚡ Observation·Where the pattern works/Where the pattern breaks·Interpretation ≠ Conclusion

Peeragogy in Practice

Stasis

⏱ 2 min

Definition:

Actually, living beings are never really in stasis. It just sometimes feels that way. Other anti-patterns like Isolation and Navel Gazing have described different aspects of the experience of feeling like one is in stasis. Typically, what is happening in such a case is that one or more dimensions of life are moving very slowly.

Problem:

When important things are moving slowly or not at all, and when they are mostly or entirely out of your control, this can be frustrating.

(Bogus) Solution:

It’s tempting in this case just to be upset and to feel disempowered.

Example:

We were not able to get programming support to improve the first version of the Social Media Classroom, since all developer energy was allocated to the next version of the system. It becomes frustrating if a specific small feature is desired, but unavailable.

Challenges:

Of course, it’s very unpleasant to be frustrated all the time. The hint to pick up is that there is always some dimension on which you can make progress. It might not be the same one you’ve been working on – you might have “over-harvested” that niche (see Carrying Capacity).

What’s Next:

We’re working on a new handbook chapter about the relationship of open source software and peeragogy. This will include some more specific ideas about ways of making change.

⚡ Unpeeragogy · Friction · Observation

Stasis Is Group Suicide

⏱ 4 minaudit-v2stasisparalysisdecision

The Assumption

Groups fall into stasis when decision-making stagnates, leading to lack of production and change. External stimuli are needed to break stasis. A group in stasis may disappear without being noticed due to authority attrition.

Perturbatore: “What if stasis isn’t a coma — it’s a governance design bug masquerading as a natural phenomenon — and internal design prevents it more reliably than external crisis?”

Stasis is not something that happens to a group. It is something a group does.

Operational Reality

Stasis is not a coma. It is a governance design bug masquerading as a natural phenomenon.

OpenStreetMap’s Data Working Group breaks decision paralysis through binding dispute resolution — not waiting for external stimulus. GitLab’s stewardship handbook prevents stasis by documenting who decides when consensus fails. The Linux kernel’s Code of Conflict shows that external pressure can force governance changes that create new friction patterns rather than resolving old ones. WebAssembly’s lighter governance model demonstrates that stasis is the default when authority is deliberately distributed.

The pattern assumes stasis requires external crisis to resolve. The evidence shows that internal governance design — explicit authority, defined escalation, decision-making that does not depend on mood — prevents stasis more reliably than external shocks.

Empirical Evidence

Resilience Cases (Confirming):

  • OpenStreetMap Data Working Group — Formal dispute resolution bodies with binding authority break decision paralysis. Internal governance design prevents stasis more reliably than external shocks.
  • GitLab Stewardship Handbook — Explicit documentation of governance boundaries reduces friction. Documenting who decides when consensus fails prevents stasis.

Fracture Cases (Complicating):

  • Linux Kernel Code of Conflict — External pressure can force governance changes that create new friction patterns rather than resolving old ones.
  • WebAssembly Community Group — Lighter governance models trade authority for speed. Stasis is the default when authority is deliberately distributed.

Operational Heuristics

Positive Boundary: Stasis is resolved when diagnosed as a governance design problem rather than a natural group lifecycle phase — explicit decision-making authority and defined escalation prevent stasis.

Negative Boundary: Do not assume stasis requires external crisis to resolve — external pressure can force governance changes that create new friction patterns rather than resolving old ones.

Epistemic Synthesis

Stasis is not a coma. It is a governance design bug masquerading as a natural phenomenon. OpenStreetMap breaks decision paralysis through binding dispute resolution. GitLab prevents stasis by documenting who decides when consensus fails. Internal governance design — explicit authority, defined escalation — prevents stasis more reliably than external shocks.

Evidence Status

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

Traceability

Run: audit-v2 · Delta: 1.6 → 1.62 (±0.02) · Diversity D: 2

References

💬 Field Report: Stasis Is Group Suicide

Every pattern in the Handbook has been tested in the real world — and the real world usually has something to say about it. If you tried something similar, or saw it fail differently, share the story here.

Write in your native language — the browser will translate. Lowering the entry barrier is more important than choosing the "right" language. GitHub translates threads automatically so everyone can follow along.
Read how evidence is collected →

✏️ Share your story🔍 Structural analysis📋 Browse field reports
What happens after I share my story?

1. Your post appears in GitHub Discussions in the Field reports category.

2. Once a week, the project reads new threads and checks for patterns worth integrating.

3. If your story reveals a new Failure Vector, a revision to tension_index, or a sharper edge for the Perturbator — the entry gets updated.

4. The change is logged at /log and goes live on the next deploy.

Don't have a GitHub account? Here's how it works

GitHub Discussions is free. You need a GitHub account (30 seconds to create one).

Once you're signed in, click "Share your story" above. Write in your own language — the thread will be translated for everyone else automatically.

You don't need to know how to code. You don't need to know what "git" is. You just need an observation that the theory didn't match reality.

What are GitHub Discussions? →

Every pattern raises more questions than it answers.
Read the theory. Then look at what happened.

🗂️ Browse all patternsWhy this project? →← Back home