Patterns

A pattern names a problem that keeps coming up in some situation and says what to do about it. Together they form a language for building and running technology in common.

Each pattern sits in one cell of the table: its thread, and the column for its level. More about the patterns · Write one · Start a pattern on GitHub

All patterns

1. 1
   Two Keyholders

   No shared system should depend on one person.

   Liberatory tech · collective-choice · Governance

2. 2
   Small Enough to Understand

   People can only govern what they can understand.

   Liberatory tech · metaconstitutional · Theory

3. 3
   Talk Before You Enforce

   Let the group talk before anyone builds a fence.

   Institutions · collective-choice · Governance

4. 4
   Every Thread at Every Level

   Write for every level where rules are made.

   Institutions · metaconstitutional · Theory

5. 5
   Every Page Links Out

   A page with no links out isn't finished.

   Institutions · operational · Guides

6. 6
   Patterns Are Tested in Practice

   A pattern is a claim until someone uses it.

   Design patterns · metaconstitutional · Theory

7. 7
   Any Cell, Any Time

   Small contributions are welcome contributions.

   Institutions · collective-choice · Governance

8. 8
   A Language Users Can Speak

   Patterns are for the people who live with the system.

   Design patterns · metaconstitutional · Theory

9. 9
   Solution First

   Start with what you'd tell a newcomer.

   Design patterns · operational · Guides

10. 10
    Workshop the Pattern

    Hear what works before you hear what's wrong.

    Design patterns · collective-choice · Governance