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

Resources

handbook

⏱ 1 minSUB

The currently published version of the Peeragogy Handbook is the 3rd Edition, also known as v3. We’re working on v4.

Next steps

  • For now “handbook” is one of the tags used on peeragogy.org, but it should probably develop into its own pattern.

⚡ Unpeeragogy · Friction · Observation

The Handbook Is Not a Tool

⏱ 4 minaudit-v2handbooktoolreference

Perturbatore: “What if peer learning without someone willing to send the calendar invites is just a book club that never meets — and the handbook is not supposed to capture how we collaborate, but expose where our collaboration breaks?”

The Assumption

The Peeragogy Handbook presents itself as a practical guide for peer learning and collaboration, offering actionable patterns and methods for distributed knowledge creation. Follow the handbook and peer learning will work.

Operational Reality

The Peeragogy Handbook sits on shelves next to Getting Things Done and three different guides to Scrum. All promise systematic approaches to collaboration. All gather dust while the real work happens in Signal threads and coffee conversations.

Version 3 exists. Version 4 is “in progress.” The pattern repeats across every collaborative project — the handbook becomes the thing we are always about to finish, never the thing we use. Not because handbooks are useless. Not because documentation does not matter. Because we mistake the map for the territory, then wonder why following the directions does not get us there.

Teams spend months perfecting their collaboration framework while their actual collaboration falls apart. The handbook becomes a beautiful artifact of how we think we work — not how we actually work when someone is sick, the deadline moves up, or the funding disappears.

GitLab shows that the handbook works when used as governance infrastructure, not philosophical grounding. P2PU demonstrates that institutional backing makes the handbook actionable. Mastodon shows that even well-documented handbooks cannot govern spillover effects. P2PU’s own challenges show that handbooks cannot resolve structural tensions — they can only document them.

Perturbatore: “What if peer learning without someone willing to send the calendar invites is just a book club that never meets — and the handbook is not supposed to capture how we collaborate, but expose where our collaboration breaks?”

Empirical Evidence

Resilience Cases (Confirming):

  • GitLab Stewardship Handbook — Explicit documentation of governance boundaries between corporate sponsor and community reduces friction in open-core projects. The handbook works when used as governance infrastructure, not philosophical grounding.
  • P2PU Learning Circles — Peer learning models with defined facilitator roles and institutional partnerships are more sustainable than purely peer-driven learning. Institutional backing makes the handbook actionable.

Fracture Cases (Complicating):

  • Mastodon Moderation / Federation — Peer governance in federated systems creates governance externalities — admin decisions affect users who have no governance rights. Even well-documented handbooks cannot govern spillover effects.
  • P2PU About / Governance Challenges — Peer learning communities inevitably face credentialing and quality assurance crises that require hierarchy or external validation. Handbooks cannot resolve structural tensions — they can only document them.

Operational Heuristics

Positive Boundary: The handbook works when used as philosophical grounding after governance infrastructure has been established — explicit documentation of boundaries between stakeholders reduces friction, but only when someone enforces it.

Negative Boundary: Do not apply handbook patterns without first establishing facilitation roles and governance boundaries — the handbook alone is insufficient; peer learning without institutional partnerships and defined roles is not sustainable.

Epistemic Synthesis

Explicit governance reduces friction, but only when someone enforces it. Defined facilitation roles create sustainability, but only when institutions back them with real resources. The handbook works better as a diagnostic tool than as an instruction manual — when documented process diverges from lived practice, that gap reveals where useful friction lives. The places where human judgment matters more than systematic approach.

Evidence Status

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

Traceability

Run: audit-v2 · Delta: 1.3 → 1.0875 (±0.2125) · Diversity D: 2

References

💬 Field Report: The Handbook Is Not a Tool

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 →

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.