The Assumption
The Peeragogy Handbook V4 represents an evolved approach to peer learning documentation, building on previous versions through community contribution and iterative refinement of educational patterns.
Operational Reality
Every wiki dreams of becoming Wikipedia. Most become digital hoarder houses.
The Peeragogy Handbook V4 did not grow — it accumulated. Content added, nothing removed. Patterns layered on top of patterns. Editorial decisions deferred because consensus did not form and nobody had authority to decide. The handbook is richer than V3. It is also less usable, because the addition mechanism never paired with a deletion mechanism.
GitLab’s stewardship handbook documents boundaries that enable contribution without hoarding: here is what the community controls, here is what stays with the corporation, here is how we decide when there is disagreement. Drupal’s governance transition shows the same pattern at scale: intentional design of what gets removed matters as much as what gets added. A handbook that does not delete is not evolving — it is accumulating.
Perturbatore: “What if every wiki dreams of becoming Wikipedia, but most become digital hoarder houses — and the handbook grew but never edited, layered but never pruned?”
Empirical Evidence
Resilience Cases (Confirming):
- GitLab Stewardship Handbook — Explicit documentation of governance boundaries between corporate sponsor and community reduces friction in open-core projects. Contribution without curation boundaries creates knowledge bloat.
Fracture Cases (Complicating):
- Drupal Governance — Intentional governance transition from BDFL to community model required years of structural work. Even successful community evolution requires removal decisions — structures must be retired, not just added.
Operational Heuristics
Positive Boundary: This pattern works when explicit stewardship roles and content governance boundaries are established before community contribution begins — documented boundaries between different stakeholders reduce curation friction.
Negative Boundary: Do not apply this pattern when content curation lacks explicit governance boundaries — organic community contribution without removal mechanisms produces knowledge bloat and decision stagnation.
Epistemic Synthesis
V4 of the handbook is richer than V3 — and less usable, because the addition mechanism was never paired with a deletion mechanism. GitLab documents boundaries that enable contribution without hoarding: here is what the community controls, here is what stays with the corporation. Drupal shows the same pattern at scale: intentional design of what gets removed matters as much as what gets added. A handbook that does not delete is not evolving — it is accumulating.
Perturbatore: “What if every wiki dreams of becoming Wikipedia, but most become digital hoarder houses — and the handbook grew but never edited, layered but never pruned?”
Growth without pruning is not evolution. It is accumulation.
Evidence Status
| Status |
Count |
| Confirmed cases |
1 |
| Cases under study |
0 |
| Unverified cases |
0 |
| Ambiguous cases |
0 |
Traceability
Run: audit-v2 · Delta: 1.3 → 1.3575 (±0.0575) · Diversity D: 2
References