The Exit Architecture

Volume III's constitutional Principle of Exit established that participation must remain voluntary enough that communities and participants can leave. This chapter makes that principle operational: what leaving actually looks like, what participants and communities take with them when they leave, what obligations they retain, and what claims they can make on shared infrastructure they helped build.

The exit architecture must be generous enough that it is a genuine option rather than a theoretical one. If leaving requires forfeiting contributions to the commons, abandoning relationships that depend on continued participation in the network, or losing access to infrastructure that has become integral to a community's functioning, then exit is not voluntary — it is simply costly enough that it rarely happens. A network whose participants cannot realistically exit does not have voluntary participants. It has captured ones.

The exit architecture must also be honest about what is lost in exit. Communities that leave the network lose access to the trust infrastructure, the coordination protocols, the collective intelligence, and the mutual support that membership in the network provides. These losses are real and should be named explicitly rather than minimized. The goal is not to make exit easy but to make it genuinely possible — to ensure that communities remain in the network because the network is worth remaining in, not because the costs of exit are too high to bear.