Digital commons and open-source design for physical infrastructure

1. The Logic of Centralized Infrastructure

Modern infrastructure is designed around two principles: centralization and extraction. Centralization allows economies of scale. Extraction ensures profit. The efficiency myth. Large water systems, electrical grids, and food supply chains are more "efficient" in a narrow sense: lower per-unit cost of distribution. But efficiency is measured in money, not in resilience, control, or autonomy. A centralized system can fail catastrophically. A Texas ice storm in 2021 left millions without electricity because the system was designed for efficiency, not resilience. Communities with distributed energy generation and storage lost power only where physical damage prevented restoration. Efficiency and resilience are trade-offs. Centralized systems optimize for the former. Communities optimizing for autonomy choose the latter. The extraction structure. Centralized infrastructure creates extraction points: - Water utilities charge for water and extract profits - Energy companies charge for electricity and fund regulatory capture - Food networks extract at production, processing, distribution, and retail - Internet platforms extract attention and data - Communication systems extract location and behavior Each extraction point is a profit center designed to maximize what flows upward rather than what flows to the community. Why communities tolerate it. Decentralized infrastructure requires capital, knowledge, and coordination that communities don't have. It's easier to pay a utility than to govern a water system together. It's easier to flip a switch than to maintain a micro-hydro turbine. This is true. Decentralized infrastructure is harder, more complex, and requires more engagement. But it is not impossible. Thousands of communities have done it.

2. Owned Infrastructure Models

There are multiple models for owning infrastructure. The right model depends on the specific infrastructure, the community resources, and the governance capacity. Community ownership models: First, directly-owned and managed. The community builds and operates the system. This requires the most governance capacity but maximum control. Examples: municipal water systems, community solar gardens. Second, cooperative ownership. Members collectively own the system, hire professional management, make decisions democratically. This balances expertise and control. Examples: rural electric co-ops, farming co-ops, credit unions. Third, nonprofit stewardship. The nonprofit owns the system, operates it for public benefit, reinvests profits in improvement or reducing costs. This allows specialized expertise while preventing individual extraction. Examples: food co-ops, community bike shares. Fourth, hybrid models. Often the most practical: a nonprofit manages, a cooperative governs, members invest, the community benefits. Examples: community land trusts, open source networks. Infrastructure to own first: Water—once you have a source (spring, rain, well), the system is simple and the value of ownership is immediate. Food—gardens, preservation, storage, and distribution are all within community capacity and have immediate payoff. Energy—solar is increasingly cheap; storage is the remaining barrier. Micro-hydro and wood heat are appropriate in many regions. Information—mesh networks, community broadcasting, local news gathering and distribution are all possible. Tools—community tool libraries cost almost nothing to build and dramatically increase accessibility. Knowledge—community learning centers, skill shares, apprenticeship networks are the oldest form of owned infrastructure. The governance question. Ownership without good governance fails. It often fails into either tyranny (a few control for their benefit) or chaos (no one can decide). And most community infrastructure projects fail at governance long before they fail at engineering. Here's why. Groups resist actually distributing authority even when they say they want to. The person who built the solar array becomes the person who decides everything about it. The neighbor who organized the tool library becomes its permanent dictator. Someone who has expertise starts hoarding it because sharing expertise means sharing power -- it means other people could do your job, and you're no longer indispensable. There's also the heroic leadership trap. Communities find a visionary, hand them all the authority, and feel relieved that someone else is handling it. This works until the visionary burns out, gets a savior complex, or moves away. Then the infrastructure they built collapses because nobody else learned how to maintain it. The fix is deliberate distributed authority. Different people exercise authority in different domains -- someone manages the energy system, someone handles water, someone coordinates food networks. Authority rotates so backup capacity develops. People who hold knowledge are expected to teach it, not hoard it. The explicit permission to fail while learning is not optional -- new people making worse decisions than the experienced ones is the cost of development, not a failure of the system. Groups built this way are harder to kill. You can remove one person and the community continues. You can't capture power by removing a single leader because power isn't concentrated there. That resilience is worth the messiness of sharing authority. Successful community infrastructure uses: - Clear decision-making structures (who decides what, how are decisions made) - Accountability mechanisms (how are leaders held responsible) - Transparent finances (everyone can see money flows) - Dispute resolution processes (how are conflicts resolved) - Knowledge transfer systems (how does knowledge stay in the community) - Rotation of authority (so no single person becomes irreplaceable) - Teaching obligations (expertise shared is infrastructure strengthened) These are not luxuries. They are the structures that prevent recapture and deterioration.

3. Building Resilience Through Redundancy

Centralized infrastructure optimizes for efficiency. This means minimal redundancy. If there's one path for water to flow, power to generate, or food to move, system failure means community failure. The resilience-efficiency trade-off. A resilient system has: - Multiple sources of critical resources - Multiple paths for distribution - Local storage and buffering capacity - The ability to function at reduced capacity if part of the system fails This costs more. A grid with distributed generation and storage costs more per watt than a centralized grid. A food system with local production and storage costs more than a supply chain optimized for just-in-time delivery. But it is worth it. Resilience is insurance against failure. Practical redundancy strategies: For water: rain collection, springs, wells, and surface water sources. Storage for dry seasons. Gravity distribution where possible. For energy: solar, wind, hydro, and wood heat. Battery storage and thermal storage. Backup generation. Efficiency so total needs are lower. For food: diverse production, multiple preservation methods, distributed storage. Preserved foods that last months or years. For communication: mesh networks, radio, and direct conversation. No dependence on cellular coverage or internet infrastructure. Each of these is more complex than centralized alternatives. But complexity that you control is better than simplicity that someone else controls.

4. The Path to Owning Infrastructure

Owning infrastructure doesn't happen all at once. It builds through successive stages, each one reducing dependency and building governance capacity. Stage 1: Awareness. Map your dependencies. What infrastructure do you actually need? What do you depend on others for? What would happen if each system failed? Stage 2: Pilot projects. Start with low-risk, high-learning infrastructure. Community gardens, tool libraries, skill shares, neighborhood communication systems. Learn governance, build relationships, prove the model works. Stage 3: Small systems. Build simple infrastructure: rain catchment, community composting, shared kitchen, local food coop, community solar on one building. Stage 4: Network effects. As systems prove themselves, link them. Gardens feed the kitchen. The kitchen creates waste for composting. Composting feeds gardens. Each system supports the others. Stage 5: Scale. Once proven at scale, water systems, energy systems, and food networks can be built and governed at community level. This progression takes years. But each stage delivers immediate benefit while building the governance and capital for the next. The knowledge requirement. Building owned infrastructure requires learning: water system design, renewable energy basics, food preservation, network governance, cooperative finance. This knowledge is learnable. It's not rocket science. But it is work. The communities that own their infrastructure are the communities that will maintain autonomy, resilience, and power as everything else changes. They are the communities that will thrive when others are dependent. This is not a luxury. It is the foundation of genuine community power.