COMMUNITY RESILIENCE BLUEPRINT

Document Structure

• Sections 1–2: Assessment framework — understand your community before you build
• Section 3: Mesh communications — the nervous system of everything else
• Section 4: Power infrastructure — what keeps it all running when the grid fails
• Section 5: Water infrastructure — the most climate-variable section in this guide
• Section 6: Food cultivation — massively different by climate zone, read your variant carefully
• Section 7: Physical hub infrastructure — kitchen, garden, workshop, tool library
• Section 8: Digital infrastructure — software layer, largely universal with offline-first requirements
• Section 9: Economic alternatives — barter, time banking, cooperative procurement
• Section 10: Community care and crisis response
• Section 11: Resistance and counter-surveillance
• Section 12: Democratic governance
• Section 13: Implementation roadmap templates by community scale
• Appendices: Seed libraries by region, native food plants, mesh decision trees, budget templates

Before you touch a tool, buy a radio, or plant a seed, you need to understand your operating environment. This section gives you a structured way to assess your community across the four dimensions that determine which variants of everything else in this guide apply to you.

1.1 Climate Zone Self-Assessment

Find your zone. Every section in this guide uses these designations to direct you to the right variant.

1.2 Terrain Assessment

Terrain is the primary driver of mesh network topology. Answer these questions for your area:

1.3 Population Density & Coverage Goals

Rural county note: do not attempt to cover an entire rural county uniformly. Build clusters around existing community anchors (feed stores, churches, community centers, grain co-ops) and connect clusters with AREDN directional links between elevated points. Accept gaps between clusters.

1.4 Threat Model Assessment

Different communities face different immediate threats. Your threat model shapes your implementation priority order.

1.5 Resource Inventory — What Do You Already Have?

Before spending money, audit what exists. The most effective communities build on existing relationships and infrastructure, not from scratch.

Community infrastructure that depends on the grid is not resilient infrastructure. Every hub site must be capable of operating critical loads for a minimum of 72 hours without grid power. Complete independence is the goal; 72 hours is the minimum viable floor.

4.1 Universal Power Stack

This is the standard architecture for any hub site regardless of climate. Climate variants modify sizing only.

4.2 Critical Load Prioritization

When power is constrained, these are the loads that must stay on. Everything else is shed.

4.3 Climate-Specific Sizing

4.3.1 Desert Southwest

• Peak sun hours: 5.5–7.5/day year-round (Phoenix averages 6.5) — best solar resource in North America
• AC load: critical in summer — factor a 3-ton mini-split (1,000W avg running) into your load calculation for any space that must be habitable in July–August
• Evaporative cooling: where possible, use swamp coolers instead of AC — they use 1/4 the power and work excellently in dry heat (below 30% humidity). They fail above 50% humidity — do not use during monsoon season
• Battery heat: batteries in unshaded enclosures can reach 120°F+ — insulate battery enclosures from direct sun, consider below-grade battery installation (basement or buried box) where ground temperature is 70–80°F year-round
• Panel sizing: because of excellent sun hours, you need fewer panels for the same daily output. A 5kW array in Phoenix produces more energy than a 7kW array in Seattle. Use this to reduce initial cost.
• Panel angle: fixed panels at latitude angle (33° for Phoenix) optimize year-round production

4.3.2 Mountain / High Altitude

• Altitude solar boost: every 1,000ft of elevation increases solar irradiance by ~1.5% due to thinner atmosphere. Denver at 5,280ft sees ~8% more solar than sea-level equivalent location.
• Snow load: solar panels must be mounted on racking rated for your local ground snow load. Steep tilt angles (50–60°) help snow slide off naturally — critical for winter generation.
• Winter production: short days + snow shading = low production December–February. Size battery bank for 3–5 day autonomy in mid-winter. Supplement with generator if needed.
• Wind: mountain sites often have excellent wind resources — a 400W–1kW small wind turbine provides meaningful winter generation when solar is weakest. Wind + solar is a strong mountain combination.
• Heating load: significant. Wood stove is the most resilient heating solution — no electricity required, local fuel, community skill base exists. Propane backup. Electric resistance heating only if generation is abundant.
• Generator fuel: propane stores indefinitely, does not gel in cold like diesel — use dual-fuel propane/gasoline generator, maintain 250+ gallon propane tank on site.

4.3.3 Pacific Northwest

• Winter solar: Seattle December averages 1.5 peak sun hours/day — design your system around this, not the summer average of 6+ hours. A system sized for PNW winter needs is nearly free-running in summer.
• Grid dependency risk: PNW depends heavily on hydroelectric — drought years reduce grid reliability. Do not assume grid is always available.
• Micro-hydro: if your site has a year-round stream with 5+ feet of head (vertical drop) and reasonable flow, a micro-hydro system produces continuous power day and night, rain or shine — often the best resource in the PNW
• Wind: coastal and ridge sites have excellent wind. Inland Puget Sound is moderate. Assess your specific location.
• Battery sizing: PNW requires larger battery banks than equivalent desert deployments — 5-day autonomy minimum for winter resilience.

4.3.4 Midwest / Great Plains

• Four seasons: system must handle both winter (low sun, cold) and summer (high sun, moderate load). Size for winter production, summer is comfortable excess.
• Tornado: all rooftop installations must use proper racking rated for 130+ mph uplift. Anchor to structural members, not roof decking alone. Have a rapid-removal procedure for imminent tornado warnings — some installations allow tilting to near-flat to reduce uplift.
• Ice storms: ice accumulation on panels can block generation for 2–3 days — size battery for this. Steep panel tilt (40–50°) helps ice shed. A push-broom pole helps clear panels safely from the ground.
• Peak sun hours: 4–5/day annual average, 3.5 in winter — solid solar resource with appropriate sizing.
• Quincy, IL baseline system: 10kW solar + 20kWh LiFePO4 + 7,500W dual-fuel generator covers full hub operation with 3-day winter autonomy.

4.3.5 Gulf Coast / Southeast

• Hurricane hardening is mandatory: all rooftop installations rated for 150+ mph winds. Flush-mounted panels with no gap underneath (uplift reduction). Secure all wiring in conduit. Have emergency panel-removal procedure for Category 3+ storms.
• Humidity and corrosion: all outdoor hardware stainless steel. Enclosures inspected and resealed annually. Salt air in coastal areas is extremely corrosive — double inspection cadence within 10 miles of coast.
• Solar resource: excellent — 5–6 peak sun hours/day in most of the region. Good year-round production.
• Grid resilience: the Gulf Coast has repeatedly demonstrated multi-week grid outages after hurricanes. Your community absolutely needs 7–14 day battery/generator autonomy for critical loads.
• Pre-storm protocol: when hurricane warning is issued, run generator to top off battery bank, fill all fuel containers, harvest any ripe produce, stock water.

Water is the most climate-variable infrastructure challenge in this entire guide. In the Pacific Northwest, the problem is managing abundance. In Phoenix, the problem is that there is almost nothing to manage. Every climate variant below is designed around the actual physical reality of water in that environment — not wishful thinking.

5.1 Universal Principles

• Every hub site needs minimum 2 independent water sources — failure of one must not end operations
• Potable water storage: minimum 14-day supply for expected hub population at 1 gallon/person/day
• Garden water: separate from potable — can use greywater, rainwater, or lower-quality sources with appropriate filtration
• Gravity pressure: where possible, elevated cisterns eliminate pump power dependency
• Water testing: all non-municipal water sources tested for coliform, nitrates, pH, and heavy metals at least annually
• First-flush diverter: on all rainwater catchment systems — discards first dirty runoff before filling storage

5.2 Desert Southwest — The Hardest Case

Phoenix receives an average of 7–8 inches of rain per year. That is roughly 1/7th of Chicago's annual rainfall. The vast majority falls in violent monsoon storms from July to September and in mild winter rains from November to March. Between April and June, rainfall is near zero and temperatures routinely exceed 110°F. Water strategy here is a survival matter, not a convenience question.

5.2.1 What Actually Works in the Desert

5.2.2 Monsoon Catchment System

The single most important water investment for a desert community hub. Phoenix's monsoons drop 4–5 inches in 6–8 weeks. A 2,000 sq ft roof can capture 1,200–2,500 gallons in a good monsoon season if properly set up.

• Gutters: continuous aluminum gutters on all roof edges, 6-inch width minimum, cleaned before monsoon season
• First-flush diverter: sized at 1 gallon per 100 sq ft of roof — diverts initial dirty water, then fills cistern
• Cistern: 2,500–10,000 gallon poly tank or ferro-cement cistern — buried or bermed for temperature stability. Underground stays 65–75°F year-round in the desert — crucial for water quality.
• Overflow: sized to handle a 3-inch/hour rain event — direct overflow to swale system
• Pump: 12V solar-powered submersible for cistern-to-drip distribution
• Filtration for potable use: sediment filter → activated carbon → UV sterilizer (in that order) — no skipping steps

5.2.3 Greywater System (Arizona Law is Your Friend)

Arizona has some of the most progressive greywater laws in the country. Under ARS 49-104, laundry-to-landscape greywater systems under 400 gallons/day require no permit. This is a massive legal advantage — use it.

• Laundry-to-landscape: direct washing machine drain to subsurface irrigation — most cost-effective first step
• Sink and shower greywater: routes to mulched basin, 2-inch minimum mulch cover over distribution pipes — legal in AZ with simple permit
• Toilet water (blackwater): requires full treatment — do not mix with greywater system
• Soap selection: greywater irrigated plants need sodium-free, plant-safe detergents — sodium is toxic to desert soil over time. Use potassium-based soaps.
• Community hub capacity: a hub with a commercial kitchen, bathrooms, and laundry can generate 200–500 gallons/day of reusable greywater — this is a significant irrigation resource

5.2.4 Swales and Earthworks

A swale is a level trench dug on contour across a slope. When monsoon water flows across the land, it enters the swale, slows down, and infiltrates into the soil instead of running off. A well-placed swale system can turn a 2-inch monsoon storm into weeks of soil moisture — the desert equivalent of an irrigation system that requires zero ongoing water input.

• Survey your site on contour — a bunyip level (two buckets connected by clear hose, filled with water) is a $5 tool that works as well as a surveyor's instrument
• Dig swales along contour lines, place excavated soil on downhill berm
• Plant the berm with deep-rooted perennial food plants: mesquite, wolfberry, prickly pear, desert willow
• Connect swales with overflow spillways — in a monsoon the system must handle intense short-duration rainfall
• A 100-foot swale on a 1% slope can infiltrate 500–1,500 gallons in a single rain event and hold soil moisture for 2–6 weeks

5.3 Semi-Arid (Albuquerque, Boise, Colorado Eastern Plains)

• Rainwater harvesting: more viable than full desert — 10–16 inches/year. Target 3,000–5,000 gallon cistern for a hub site.
• Snowmelt (where applicable): in higher semi-arid areas with winter snow, spring melt is a significant water event — have earthworks and storage in place to capture it
• Greywater: same principles as desert, typically similar legal framework in western states
• Atmospheric water: marginally viable in humid semi-arid areas — check your actual average RH. If summer daytime RH is below 35%, do not plan around it.
• Drip irrigation mandatory: surface watering loses 30–50% to evaporation in hot semi-arid conditions — ollas and drip are both appropriate

5.4 Mountain (Colorado Rockies, Montana, Vermont, Appalachians)

Mountain water situations are generally abundant but require management around seasonality, contamination risk from runoff, and freeze protection.

• Spring snowmelt: the largest single water input of the year — earthworks and storage must be ready by March to capture it. Install storage and swales in fall.
• Gravity-fed spring: if a natural spring exists uphill from your site, this is your best water source — gravity-fed, no pump required, typically year-round. Test for coliform and nitrates, install a spring box, pipe downhill to cistern.
• Seasonal stream diversion: legal complexity varies by state — check water rights law in your state. Colorado water law is especially complex (prior appropriation doctrine). Get legal advice before building diversion infrastructure.
• Rainwater harvesting: Colorado historically banned rainwater collection — this was reformed in 2016 to allow 110 gallons per household. Know your state law — it varies widely.
• Freeze protection: all water infrastructure must be buried below local frost depth (24–48 inches in mountain regions) or insulated. Above-ground pipes fail in winter — plan all piping underground or in heated spaces.
• Root cellar: mountain communities can build effective root cellars at 4–6 feet depth where soil temperature stays 35–45°F year-round — natural refrigeration for food storage without electricity

5.5 Pacific Northwest

The PNW has a water abundance problem — most rain falls October through April, then summer is dry and fire-prone. The challenge is storing winter abundance for summer use, not finding water in the first place.

• Large cisterns: 10,000–25,000 gallon cisterns are viable and necessary to bridge the summer dry season
• Micro-hydro: if a year-round stream with adequate head exists, this is the ideal water and power source combined — gravity-fed water + continuous electricity
• Winter roof collection: a 2,000 sq ft roof in Seattle captures 40,000–60,000 gallons per year — dramatically more than any other climate in this guide
• Summer drought management: even with large storage, water-wise gardening practices (drip, mulch) are necessary in PNW summers which can be surprisingly dry
• Water rights: unlike the West, most eastern states (including Oregon and Washington) use riparian water rights — more flexible for small-scale catchment but still requires understanding local law

5.6 Midwest / Great Plains

• Municipal water: typically reliable, but contingency plan for contamination events (Flint model — it will happen elsewhere)
• Well water: many Midwest rural properties have existing wells — test annually for nitrates (agricultural runoff), coliform, arsenic, and lead. Install whole-house filter and UV sterilizer.
• Rain barrel system: 2–4 55-gallon barrels at downspouts covers most garden irrigation needs in normal rainfall years
• Cistern for drought years: Midwest experiences periodic drought — a 2,500–5,000 gallon cistern provides a buffer. The 2012 drought caused severe municipal water stress in many Midwest cities.
• Freeze: all above-ground water infrastructure must be winterized by November — drain rain barrels, disconnect hoses, insulate outdoor faucets
• Flooding: low-lying areas in river valleys face periodic flooding — any underground storage must be designed for flood conditions (waterproof lids, sealed fittings)

5.7 Gulf Coast / Southeast

• Abundant rainfall but hurricane contamination: after a major storm, municipal water systems can be contaminated or offline for days to weeks. Store 14+ days of potable water.
• Post-storm water: do not drink standing flood water — assume contamination with sewage, chemicals, and pathogens. Gravity filter + bleach treatment minimum, UV preferred.
• Cisterns: 5,000–10,000 gallon above-ground or buried polyethylene — must be anchored against flood uplift if in flood zone
• Hurricane prep: fill all water storage containers before storm arrives — municipal water pressure may drop or cut out
• Humidity and algae: standing water in warm humid climates grows algae rapidly. Cover all cisterns, add food-safe algaecide if needed, rotate stored water.
• Rainwater law: most southeastern states allow rainwater collection without restriction — check your state. Texas, Florida, and Louisiana are all permissive.

Food production strategy varies more by climate than any other section in this guide. The same garden plan that works beautifully in Quincy, IL will fail catastrophically if applied in Phoenix, AZ without modification. This section gives each major climate zone a full treatment — read your zone, ignore the others until you are advising a community in a different region.

6.1 Universal Foundation

6.1.1 Soil Building (Climate-Independent)

• Compost: a 3-bin system (active hot / curing / finished) is the backbone of every garden. No exceptions.
• Worm bin: vermicompost is the most nutritionally complete amendment available — 4x8ft flow-through bin converts kitchen scraps to castings in 60–90 days
• Cover crops: plant nitrogen-fixers (crimson clover, vetch, cowpeas) in every empty bed. They are free fertilizer.
• No-till principle: once beds are established, do not till. The fungal network in healthy soil is destroyed by tilling. Add amendments on top, let biology incorporate them.
• Seed saving: for every crop you grow regularly, save seed from your 3 best-performing plants. Your seed bank becomes locally adapted within 3–5 generations.
• Open-pollinated only: hybrid seeds (F1) do not breed true — you are dependent on a seed company next year. Open-pollinated and heirloom varieties give you sovereignty.

6.1.2 Universal Garden Infrastructure

• Raised beds: 4x8ft, 12" deep minimum — applicable in every climate with local material modifications
• Compost thermometer, soil thermometer, pH meter: these three tools cost $30 combined and eliminate most crop failure from guessing
• Seed starting area with grow lights: 2x T5 fixtures per 4x8ft shelf — starts in any climate
• Cold frames: 4x4ft aluminum frames with polycarbonate glazing — universally useful for season extension
• Seed library: organized by plant family, stored cool and dry — the most important single resource in any food system

6.2 Desert Southwest — The Inverted Garden

6.2.1 Desert Growing Calendar

6.2.2 Desert-Adapted Food Plants (Permanent Plantings)

These plants require little or no supplemental irrigation once established (1–2 year establishment period with initial watering support). They are the permanent backbone of any desert food system.

6.2.3 Desert Water-Efficient Irrigation Techniques

Ollas — The Most Important Desert Garden Tool

An olla (pronounced OY-ya) is an unglazed clay pot buried in the soil with only the neck exposed. It is filled with water, which weeps slowly through the porous clay directly to plant roots at the pace the roots consume it. Surface evaporation is near zero. No spray, no runoff, no over or under watering. This technology is 4,000 years old and is still the most water-efficient irrigation method available for desert conditions.

• Commercially available: Olla Pots (Native Seeds/SEARCH, Tucson) or any unglazed terracotta pot
• DIY ollas: two unglazed terracotta pots glued rim-to-rim with waterproof terracotta sealer — plug the drainage holes with wine corks
• Sizing: 1 olla per 4 sq ft of bed — one 1-gallon olla refilled every 3–7 days replaces daily surface watering
• Placement: bury 90% of pot, leave neck exposed for filling — surround with 4 inches of wood chip mulch
• Water reduction: studies show 50–70% reduction in irrigation water compared to surface drip with equivalent or better yields

Deep Mulching

• 4–6 inches of wood chip mulch over all bed surfaces — not straw (too light), not rock (increases heat)
• Reduces soil temperature by 20–30°F — the difference between viable root zone and cooked root zone
• Reduces evaporation by 60–80% — dramatically reduces watering frequency
• Source free wood chips: contact local tree trimming services — they will often deliver a truck load free

Shade Cloth

• 30–50% shade cloth over beds April through October — reduces sun load, reduces water need by 25–35%
• Orient beds east-west — use north side of a wall or structure for afternoon shade (the brutal period in Phoenix is 1–6pm)
• Reflective mulch: white or silver mulch under plants reflects light upward — useful for fruiting crops

6.2.4 Indoor/Controlled Environment Summer Growing

In Phoenix, the only viable summer food production is in a controlled environment. This is not a luxury — it is the practical reality of 115°F days.

• Aquaponics: fish + plants in a recirculating water system — dramatically lower water use than soil gardening, climate-controlled environment, year-round production. Tilapia are heat-tolerant to 90°F+ water temperature.
• Hydroponic/NFT system: nutrient film technique in an evaporatively cooled or air-conditioned space — lettuce, herbs, greens year-round
• Microgreens: small-space, fast-turn, high-nutrient — growing tray indoors, 7–14 day harvest cycle, no soil required
• Mushroom cultivation: logs or blocks in a cool basement or shaded outbuilding — oyster mushrooms tolerate 65–80°F, extremely productive per square foot
• Power note: indoor growing requires electricity for lighting and climate control — solar system sizing must account for this load

6.3 Semi-Arid (Albuquerque, Boise, Colorado Plains)

• Growing season: typically April–October — four real seasons, frost danger both ends
• Water-wise techniques from desert section apply: ollas, drip, deep mulch — all relevant here
• Higher elevation = cooler temps = more viable summer growing than full desert
• Dry bean advantage: semi-arid is ideal for dry bean production — minimal summer rain, harvest dry naturally on the vine
• Dryland wheat and grain: Great Plains/eastern Colorado dryland farming produces grain without irrigation using moisture conservation techniques — deep tillage in fall, firm seedbed in spring
• Wind: semi-arid areas frequently have strong winds — windbreaks (hedgerows of fruiting shrubs) protect garden beds and reduce soil moisture loss
• Hugelkultur: buried rotting logs act as sponges, storing water from rain or irrigation and releasing it slowly — excellent for semi-arid gardens, reduces irrigation by 30–50% once wood decomposes

6.4 Mountain (Colorado Rockies, Montana, Vermont, Appalachians)

6.4.1 Mountain Growing Calendar (Colorado Rockies, 6,000–9,000 ft)

6.4.2 Season Extension Infrastructure (Mountain Required)

• Cold frames: 4x4ft aluminum frame with twin-wall polycarbonate glazing — extends season 4–6 weeks each end
• Hoop house (low tunnel): 6-foot wide, 3-foot tall wire hoops covered with 1.5oz row cover — 8–10°F frost protection, extends season 3–4 weeks each end
• High tunnel (unheated greenhouse): 12–14ft wide gothic arch tunnel, polycarbonate or 6-mil greenhouse plastic — grows tomatoes and peppers at altitude, year-round greens
• Root cellar: 4–6 feet below grade, 32–40°F stable, 85–95% humidity — stores carrots, beets, turnips, potatoes, celeriac from harvest through April with zero energy input
• Short-season variety selection is mandatory: look for 55-day tomatoes (Stupice, Glacier), 50-day peppers (Lipstick), 60-day winter squash (Delicata, Bush Delicata)

6.4.3 Mountain-Adapted Food Plants

• Potatoes: produce abundantly at altitude, frost-tolerant leaves, high caloric density — most important staple crop
• Kale and chard: handle light frost, produce through mountain growing season
• Jerusalem artichoke (sunchoke): native North American tuber, extremely cold hardy, aggressive spreader — plant in dedicated contained bed
• Serviceberry (Amelanchier): native mountain shrub, produces blueberry-like fruit in June–July, no care required
• Currants and gooseberries: extremely cold hardy (Zone 3–4), productive in mountain conditions, no-spray required
• Conifers for food: pine nuts from pinyon pine (lower elevation), spruce tips (spring growth), fir tips — foraging supplements garden production

6.5 Pacific Northwest

The PNW is the most forgiving gardening climate in North America for a community food system. Mild temperatures, abundant rain, and year-round growing potential make it possible to produce food in every month of the year with minimal infrastructure investment. The primary challenges are pests (slugs especially), disease pressure from humidity, and limited winter light.

• Year-round production: a PNW garden produces something edible every month — plan a continuous succession rather than a single growing season
• Slug management: the Pacific slug is the primary adversary of PNW gardens — copper tape barriers, iron phosphate bait (organic-approved), diatomaceous earth, and duck patrols (seriously — ducks are excellent slug predators)
• Brassica culture: kale, cabbage, broccoli, kohlrabi, Brussels sprouts are king in the PNW — the cool, moist conditions they love are precisely what the PNW provides
• Garlic: plant in October, harvest July — the most profitable and storable crop for a PNW community garden
• Fruit trees: apples, pears, plums, and cherries thrive in the PNW — perennial food infrastructure that requires almost no irrigation once established
• Fermentation culture: PNW produce abundance combined with high moisture content means fermentation (sauerkraut, kimchi, pickles) is both a preservation necessity and a cultural tradition
• Powdery mildew and blight: humidity drives fungal disease — space plants for airflow, avoid wetting foliage, choose blight-resistant varieties for squash and tomatoes

6.6 Midwest / Great Plains (Quincy, IL Baseline)

The Midwest is the baseline environment for this guide. It has four distinct seasons, good soil, adequate rainfall (25–40 inches), and a long history of agricultural practice. The main challenges are temperature extremes at both ends of the season, tornado and severe weather risk, and agricultural chemical contamination of waterways and soils near conventional farming operations.

• Soil testing: Illinois Extension Service provides soil testing at low cost — test every 3 years, adjust pH (Midwest soils tend to be neutral to slightly alkaline)
• Tomato blight: late blight (Phytophthora) is a consistent Midwest threat in wet summers — grow blight-tolerant varieties (Defiant, Mountain Merit, Iron Lady)
• Corn rootworm, bean beetles, squash vine borer: know your local pests, plant resistant varieties and use row cover during egg-laying periods
• Perennial foundation: asparagus (20-year productive life), rhubarb, strawberries, raspberries, blackberries, fruit trees (apple, pear, plum, cherry) — all thrive in the Midwest and provide food year after year with minimal input

6.7 Gulf Coast / Southeast

• Two primary seasons: spring (Feb–May) and fall (Aug–Nov) are the main productive windows — summer heat and humidity make many standard crops struggle or fail
• Heat-tolerant varieties essential for summer: Malabar spinach (thrives in heat, vining), sweet potato (loves heat), okra, Southern peas (black-eyed peas, crowder peas), peppers, eggplant
• Tropical food plants: fig, muscadine grape, pawpaw, persimmon, loquat, kumquat — these are permanent food infrastructure that thrive in the Southeast without the care northern equivalents require
• Humidity and disease: southern blight, powdery mildew, and nematodes are the primary disease pressures — raised beds with excellent drainage, crop rotation, and soil solarization (covering soil with clear plastic in summer to heat-kill pathogens) are the primary tools
• Hurricane readiness: have a rapid harvest protocol — when a hurricane is 48 hours out, harvest everything ripe and process or store. Board or stake climbing plants. Remove shade cloth before 50+ mph winds.
• Sweet potato: the most important food security crop in the Gulf South — produces abundantly in heat and humidity, highly caloric, stores 6 months at room temperature without any special equipment, and the leaves are edible greens
• Cassava (zones 8–10): grows like a weed in the deep South, produces enormous quantities of starchy tubers, drought tolerant once established, frost kills top but roots survive to zone 8

Every community network needs at least one physical anchor — a place people can gather, store shared resources, learn skills, and receive mutual aid. This section describes the requirements for a community hub, with climate-specific modifications. The Stone Soup Kitchen model in Quincy, IL is the baseline.

7.1 Minimum Viable Hub

7.2 Climate Modifications to Hub Design

7.3 Tool Library — Universal Inventory

This inventory applies universally. Climate additions noted where relevant.

7.3.1 Garden Tools

7.3.2 Community Tool Library (Non-Garden)

The digital layer of this blueprint is the most universal section in the guide — the software stack largely does not care what climate you are in. The hardware hosting it must be protected from climate extremes, but the applications themselves are portable. This section describes the full stack and its offline-first requirements.

8.1 Core Stack (Deploy in Order)

8.2 Offline-First Design Requirements

Every community-facing application must meet these minimum offline requirements before being deployed as a community tool:

• Service worker registered and caching critical assets — app must load without network
• All user data writes to local storage (IndexedDB) before any network call — never block the user on sync
• Sync queue: when connectivity returns, push local changes to server with conflict resolution
• Graceful degradation: features that require connectivity must degrade to a usable offline mode, not crash
• Printable fallback: every critical reference (medical info, rights guides, contact directory) must have a print-to-PDF option

8.3 Hardware Requirements by Community Scale

9.1 Barterra Time Bank — Universal Model

The time bank operates on a simple principle: 1 hour of your work = 1 hour of someone else's work, regardless of what the work is. A plumber's hour and a childcare hour are equal. This is not barter of goods — it is the exchange of labor without money.

9.1.1 Operating Principles

• 1 time credit = 1 hour of labor — no exceptions, no premium rates
• New members receive 5 starter credits — everyone can participate immediately
• Credits expire after 2 years if unused — prevents hoarding, encourages circulation
• No negative balances allowed beyond -10 credits — prevents extraction
• Dispute resolution by community assembly — no corporate arbitration

9.1.2 Skill Categories (Seed List — Expand by Community)

9.2 Cooperative Procurement — Universal Model

Bulk buying co-op for the community. Members contribute to a pooled fund, the co-op purchases in bulk at wholesale prices, distributes at cost. No markup. No profit. No Amazon.

10.1 Universal Crisis Response Model

The goal is a trained human showing up when someone is in crisis — not a police officer. This requires trained people, clear dispatch protocols, and the communications infrastructure (mesh + BaoFeng radios) to make contact.

10.2 Climate-Specific Crisis Scenarios

11.1 Universal OpSec Principles

Security culture is not paranoia. It is an appropriate response to a documented threat. State and corporate surveillance of community organizing is real, well-funded, and ongoing. These practices apply everywhere.

11.2 Legal Observer Network — Universal Model

• Training: 4-hour workshop — know your rights as an observer, documentation protocol, evidence chain of custody
• Equipment: phone or action cam, bright green LEGAL OBSERVER vest, notepad, emergency legal contact card
• Secure upload: encrypted upload to community legal case server immediately after action
• Legal fund: target $5,000 reserve in Year 1 — allocate a fixed percentage of hub revenue
• Partner orgs: National Lawyers Guild has chapters in most cities. They train legal observers and provide direct legal support at actions.

12.1 Community Assembly Model

Any community infrastructure that is not governed by the community it serves will eventually be captured by someone else's interests. Governance is not a later problem. Build it first.

12.2 Financial Transparency (Non-Negotiable)

• Monthly financial report published to decisions archive — all income, expenses, reserves, allocation percentages
• Cooperative procurement pool accounting publicly visible to all members
• Time bank ledger audit trail — all members can see all transactions (no private balances)
• Annual independent review by a trusted community ally — not a corporate accounting firm
• 60/40 model: 60% of revenue to direct social services, 40% to infrastructure operations — this ratio is voted on annually by the Assembly and can be changed

Use the template that matches your community's starting scale. These are not rigid — adapt to your specific resources, threat model, and community priorities.

13.1 Village Scale (<500 people, rural or small community)

13.2 Town Scale (500–10,000 people)

13.3 Urban District Scale (10,000–100,000 people)

• Step 1: Mark all population clusters on topo map with 0.5 mile circles
• Step 2: Identify 3–5 highest elevation points within each cluster — these are candidate backbone nodes
• Step 3: For each pair of planned backbone nodes, draw the line of sight path on topo map. Any terrain obstruction within 60% of Fresnel zone radius blocks the link. Use Radio Mobile to verify.
• Step 4: Place gateway nodes at verified backbone positions. These anchor AREDN and provide Meshtastic gateway for the cluster.
• Step 5: Fill coverage gaps with standard Meshtastic nodes at 500m–1km spacing in residential, 300m in dense urban. Every location must have 2-hop path to a gateway.
• Step 6: Verify with test radios before purchasing full deployment hardware — walk the planned coverage area with a T-Beam and a phone running Meshtastic, verify signal strength at planned node locations.
• Step 7: Install, test, adjust. Mesh topology is never fully predictable from planning — expect to relocate 10–20% of nodes after testing.