The Assumption

The index presents all patterns as equally viable and active, functioning as a neutral catalog of peeragogical approaches without indicating which patterns have proven effective or which have been abandoned.

Operational Reality

The Peeragogy Handbook opens with a welcome mat and a Google form. Two links, one promise, zero indication of what actually works inside. This is how most peer learning projects present themselves — as if the invitation itself were the method.

Not a curriculum. Not a tested sequence. Not even a warning about what breaks.

The handbook treats its own index like neutral territory. Each pattern gets equal billing, same formatting, democratic placement. But three years of watching groups attempt peeragogy reveals the opposite: some patterns kill projects, others save them, most do nothing at all. The index refuses to admit this.

GitLab demonstrates that documentation works precisely because it names what will not be tolerated — not what will be celebrated. Drupal shows that an index presenting all patterns as equal hides the crucial distinction between patterns that survive scaling and those that do not. MakerDAO’s Black Thursday demonstrates that indices without failure metadata are dangerous when it matters most.

Perturbatore: “What if an index that does not tell you which patterns are dead is just a graveyard with no headstones — and concealing failure rates is actually protecting something more fragile than success?”

Empirical Evidence

Resilience Cases (Confirming):

• GitLab Stewardship Handbook — Explicit documentation of governance boundaries between corporate sponsor and community reduces friction in open-core projects. Documentation works precisely because it names what will not be tolerated — not what will be celebrated.

Fracture Cases (Complicating):

• Drupal Governance — Intentional governance transition from BDFL to community model required years of structural work, not organic emergence. An index presenting all patterns as equal hides the crucial distinction between patterns that survive scaling and those that do not.
• MakerDAO Black Thursday — DAO governance mechanisms designed for normal operations can fail catastrophically under stress, requiring emergency governance that existing processes do not cover. Indices without failure metadata are dangerous when it matters most.

Operational Heuristics

Positive Boundary: The index works when it explicitly documents governance boundaries and structural requirements for each pattern — documenting pattern constraints is more useful than neutral cataloging.

Negative Boundary: Do not present all patterns as equally valid when evidence shows distinct failure modes — pattern selection without validation metadata — survival rate, dead patterns, combinations that regularly fail — produces harm, not orientation.

Epistemic Synthesis

Governance documentation works because it names what will not be tolerated — not what will be celebrated. Explicit boundaries reduce friction by making power visible, not by making it disappear. An index that classified patterns by survival rate, marked dead ones, admitted which combinations regularly fail — would serve learners better. But it would also expose how little we know about what we ask people to attempt.

Perturbatore: “What if an index that does not tell you which patterns are dead is just a graveyard with no headstones — and concealing failure rates is actually protecting something more fragile than success?”

An honest index is a map of wreckage. Not a catalog.

Evidence Status

Traceability

Run: audit-v2 · Delta: 1.2 → 1.3792 (±0.1792) · Diversity D: 2

References

• GitLab Stewardship Handbook
• MakerDAO Black Thursday
• Drupal Governance