The moment you add a third person, the rules change.
A group of two has a dynamic. A group of three has a system — and systems need architecture to function, or they collapse into something else: politics, drift, informal hierarchies, private recovery loops running in the background while the actual work tries to happen in the foreground.
Most collectives fail not because the people are wrong but because there is no governing architecture underneath them. No shared identity infrastructure. Just individuals running their private systems in proximity and calling it a team.
Patterns of Collective Architecture is the structural manual for building identity infrastructure at scale — organizations, communities, movements, teams. What holds a collective together when it grows beyond what relationships alone can carry. How roles are built so they hold under pressure. How shared recovery works. How collective identity evolves without fracturing into competing factions.
If you’re building something that needs to outlast the people who started it, the architecture has to be designed for that from the beginning. Most collectives build on momentum and intention. Both run out.
Architecture doesn’t.