Independence, by Design
King George III wrote in his diary on July 4, 1776: "Nothing important happened today." Centralized systems are often remarkably efficient. They also create remarkable fragility and blind spots. Empires fail the same way mono-cultures fail: they mistake efficiency for resilience.
Over-dependence on centralized systems creates unnecessary vulnerabilities in our daily lives. The same design principles that create resilient permaculture ecosystems also create resilient digital infrastructure, resilient local economies, and resilient communities. Independence emerges from these patterns of interdependence. Every durable system, whether it's a forest, a community, or a communications network, converges on the same architecture.
Redundancies help us maintain our standard of living and avoid the disruptions that centralized systems can create. The most resilient communities aren’t the ones with the biggest budgets, they’re the ones with the fewest single points of failure.
Both permaculture and open-source technology communities are asking the same question: what kind of infrastructure allows people to cooperate without becoming fragile? Both are ultimately about designing communities that can remain free because they are difficult to break.
| Permaculture | Open-Source Technology |
|---|---|
| Value plant diversity | Value protocol diversity |
| Save and share seeds | Share open source code |
| Design for drought | Design for outages |
| Avoid monocultures | Avoid single points of failure |
| Stack functions | Layer systems |
| Observe and adapt | Fork, iterate, and improve |
| Mutual aid | Peer-to-peer networks |
| Water finds many paths | Data packets find many routes |
| Foster resilient landscapes | Foster resilient information systems |
| Cultivate relationships between species | Cultivate relationships between nodes |
A resilient food system cannot compensate for a fragile information system. A resilient information system cannot compensate for a fragile local economy. A resilient local economy cannot compensate for a community that has forgotten how to grow food.
This is why the Queen City Resiliency Salon is designed around four teams: Food & Land; Goods & Repair; Communication & Technology; and Money & Exchange. A community has to circulate biological energy via food, material value via goods, and knowledge and coordination via information. Money is simply a language for exchange we agree upon, it could be dollars or hOUR Economy tokens or just informal exchanges of favors.
Redundancies are key to resilience and the Queen City Resiliency Salon could use some redundancy in leadership. So I am currently looking for four Catalyst Captains for each of my teams. Not to run the Salon entirely, but to make sure it never depends on one person again.
Historically salons weren’t organizations with formal presidents, vice presidents, etc. They were places where ideas cross-pollinate among peers. You just need to show up so other people can show up when I cannot show up.
A forest doesn't become resilient because it grows one giant oak. It becomes resilient because thousands of organisms share the work. Communities aren't any different. That’s what I’m asking you to help build.
If this resonates with you, I'd love to hear from you: signal [at] kamresearch [dot] global