Sovereign Mutual Aid / Community Infra Atlas (Final)
A structured guide to mutual aid / care / community infrastructure resources, organized as a
stack: kernel patterns → operational guides → physical hubs → pattern banks → telemetry directories,
with explicit capture risk and extension hooks (money, AI-security, energy/water/comms, lifecycle).
Format: HTML + CSS only
Links: inline where referenced
Audience: builders, organizers, infra stewards
Use: fork / remix / teach / operationalize
0 — How to Use This Atlas
This page is designed to be navigated in two modes:
(1) build-mode (you are constructing pods, workflows, and hubs) and
(2) audit-mode (you are defending against capture, surveillance, or domestication).
Operational rule: start with Kernel (K) to align the frame and enemy model,
then add Operational (O) patterns, then build place-based hubs,
and only then touch Telemetry directories (T).
0.1 — Schema & Tags
Every resource entry includes: Role, Tier, License,
Environment assumptions, Capture vectors, Positive singulars,
and Hooks into other stack modules.
What the Tier tags mean (K / O / H / T / A)
- K (Kernel): irreducible patterns; if everything else disappears, these rebuild the core.
- O (Operational): workflows, templates, “how-to” mechanics; use selectively.
- H (History/Depth): lineage, theory, movement memory; prevents “pandemic-only” framing.
- T (Telemetry): maps/directories; extremely useful and extremely exposable.
- A (Adversarial): documents showing how institutions/cities/NGOs will attempt to recode your infra.
What “Environment assumptions” means
- Threat: expected repression level in which the resource still works as written.
- Connectivity: whether it assumes online tools, or can run offline/printed.
- Funding: implicit default (grants, donations, self-funded, mixed).
0.2 — Quickstart Paths
Choose the reading/implementation path that matches your immediate objective.
Each path references the same resources, but in different sequences.
Path A — “Start a Pod This Week”
- 1.1 Big Door Brigade (definition + issue map)
- 2.1 Shareable Mutual Aid 101 (setup + sustain)
- 2.2 #WeGotOurBlock (scripts + neighbor mapping; strip context artifacts)
- 3.2 EFF (digital safety baseline)
- 3.1 SELC (legal landscape—use as reference, not default formalization)
Path B — “Build a Resilience Hub”
- 1.3 MADR Notes on Mutual Aid (enemy model + lineage)
- 4.1 MADR Resilience Hub Toolkit (mutual-aid rooted hub blueprint)
- 4.2 ResilienceToolkit.org (offline-first operations patterns)
- 4.3 Shareable hub + Library of Things (space + shared assets)
- 5.2 MADR Resource Index (expand by disaster type)
Path C — “Defend Against Capture”
- 1.3 MADR Notes Vol. 2 (friends/foes/wolves)
- 3.2 EFF + your AI-threat extension rules
- 6.1 Mutual Aid Hub (telemetry; treat as exposure case study)
- 4.2 CROs toolkit (offline design good; state/grant integration = capture surface)
Path D — “Teach / Train a New Cell”
- 1.2 Mutual Aid: An Introduction (fast onboarding)
- 2.1 Shareable Mutual Aid 101 (sessionized curriculum)
- 2.3 MADR facilitation guides (workshop scripts)
- 5.3 Commons Library (whitelist mutual-aid nodes only)
1 — Concept & Enemy Model (Core)
This layer defines mutual aid as a living infrastructure category and installs an enemy model:
capture by nonprofits, politics, surveillance, and opportunists. Without this layer,
operational templates drift into charity, “service provision,” or platform dependency.
Role: definition + issue-area routing table
•
Primary value: the taxonomy (bail, childcare, copwatch, disability justice, etc.)
What to extract
- Core definition: mutual aid ≠ charity (power-building + survival).
- Toolbox categories as a modular blueprint for multi-issue capability.
- Use linked resources selectively; each link is its own risk surface.
Capture vectors (read adversarially)
- US-centric assumptions (law, policing, institutions).
- Many outbound links live inside NGO/campaign ecosystems.
- “Best practices” can drift into professionalized activism norms.
Role: onboarding handout
•
Use: session 0 for new people
Why it matters
- Fast, printable primer that cleanly separates mutual aid from charity.
- Low friction for onboarding across skill levels.
Limits (don’t over-assign it)
- Does not model AI-era surveillance, financial rails, or hard repression.
- Should not be treated as the conceptual “ceiling.”
Role: political spine + co-optation defense
•
Core function: enemy model (friends/foes/wolves)
Use it for
- Installing an explicit capture model: nonprofits, politicians, fascists, opportunists.
- Grounding mutual aid in a lineage (not “a 2020 novelty”).
- Training organizers to read “help” that arrives with control attached.
Extractable outputs
- A checklist for partnership offers: What do they want? What do they control? What data do they get?
- Internal governance prompts: how groups get captured from the inside out.
- Operational principle: prioritize autonomy over recognition.
Direct links to Volumes
2 — Group Formation & Pod Architecture
This layer is about building functional pods and groups that do real work: intake, delivery, follow-up,
conflict-handling, and continuity. It also flags which “standard tools” create surveillance and lock-in.
Role: step-by-step group creation + sustainability
•
Includes modules: decision-making, power, legal, surveillance/cybersecurity, financial tech
Best way to use it
- Run it as a curriculum (study circle) and convert outputs into local SOPs.
- Use its modules as checklists for building your own documentation.
- Pair it with MADR Notes to keep the anti-capture stance intact.
What to watch
- Nonprofit production context can quietly normalize “program” thinking.
- Digital/financial risk sections are “first-gen” (pre AI-governance threat models).
Download link (PDF) where available
Role: neighborhood pod mechanics (scripts, outreach, mapping)
•
Context: COVID-era (2020); treat as pattern source
What to extract (timeless mechanics)
- Outreach scripts and neighbor contact patterns.
- Pod structure, roles, and intake/delivery flow basics.
- “How to start” steps as a template for your own SOP.
What to strip (context artifacts)
- Branding and politician-adjacent legitimacy cues.
- COVID-specific assumptions that don’t generalize.
- Any tool recommendations that increase surveillance by default.
Role: community workshop scripts + trauma-aware governance patterns
•
Access: zine library hub
Use it for
- Running public or semi-private trainings (workshop facilitation structure).
- Conflict navigation without defaulting to carceral systems.
- Building resilience that doesn’t collapse into “feel-good” depoliticization.
Complement with
- AI-aware security modules (LLM scraping, synthetic identities, graph targeting).
- Lifecycle/fork protocols (clean splits, succession, intentional endings).
Key access points
3 — Governance, Law & Digital Safety
This layer is where groups either become durable and sovereign—or get formalized, captured,
and turned into a managed “program.” Treat law and digital safety as terrain maps,
not as authority to become bureaucratic.
Role: US legal landscape + entity choices + liability + governance patterns
•
License: CC BY-SA 4.0 (ShareAlike)
Extractable value
- Entity options map (informal → unincorporated association → nonprofit/fiscal sponsor) and tradeoffs.
- Appendix patterns: sample bylaws, liability waivers, privacy policies, case studies.
- Barter/tax basics to avoid accidental legal traps.
Capture vectors
- Compliance gravity: “seriousness” can be conflated with formalization.
- US-centric categories can mislead elsewhere.
- Pre-AI data security; must be upgraded for 2026+ threat environments.
Direct references and mirrors
Role: baseline digital hygiene for mutual aid
•
Core principle: data minimization + access control
Non-negotiables to internalize
- Collect less data than you think you need.
- Restrict access by role; don’t share everything with everyone.
- Assume platforms can be subpoenaed, scraped, or leaked.
What must be upgraded (2026+)
- Assume any public content becomes AI training data.
- Assume directories can be graph-analyzed for targeting.
- Assume phishing/social engineering is LLM-enhanced.
Role: design checklist for mutual-aid financial tech
•
Use: evaluate tools; design your own with privacy/community control
Best use
- As a criteria list: who owns data, who can exit/fork, what is logged, what is shared.
- As a threat lens for financial workflows (intake → verification → disbursement).
Watch-outs
- Fintech framing can encourage “platform solutionism.”
- Use it to reduce dependency, not to justify building new centralized systems.
4 — Physical Infrastructure & Resilience Hubs
This layer moves from “group doing tasks” to “place-based infrastructure”:
hubs that hold supplies, communication capacity, tools, and continuity through disaster cycles.
Role: hub blueprint rooted in mutual aid
•
Core move: before/during/after cycles + anti-capture framing
What it enables
- Designing a hub as an autonomous node (not an NGO “service center”).
- Mapping chronic crisis into continuous operations (not one-off “responses”).
- Framing resilience as mutual aid, not city branding.
Adversarial caution
- “Resilience hub” language is easily co-opted by cities and foundations.
- Keep governance local; treat external funding as a control surface.
Role: operational worksheets + offline/private tool design
•
License: CC BY-NC-SA 4.0
Why it’s rare and valuable
- Offline-first: data stays on device; export/import supported.
- Local-first modules you can adapt to your own hub planning.
Why it’s also an adversarial reference
- State and grant integration turns hubs into measurable policy objects.
- NC license constrains commercial use and derivative packaging.
Start points inside the toolkit
4.3 Shareable — Hub Space + Shared Assets
O
Threat: Low
Offline-capable
Role: turning spaces into hubs + operating a Library of Things
•
Links: guide + toolkit
How to use (stack-aligned)
- Use for space layout, inventory logic, and maintenance routines.
- Overlay your own security/visibility strategy (public vs semi-private hubs).
- Bind membership/fees into your Money & Flows module (cash/BTC/etc.).
5 — Operational Pattern Banks
These are not worldview anchors. They are high-yield mines for schemas, workflows, and templates.
Treat tool choices as replaceable; extract the shape, then re-implement with your own stack.
Role: practical templates (intake, schedules, directories, mapping)
•
Warning: heavy SaaS dependency patterns
High-value extracts
- Intake schema: “support needed/offered” categories and workflows.
- Volunteer scheduling + triage patterns from dense urban context.
- Data modeling discussions and standardization attempts.
High-risk exposures
- Public directories are target maps under repression.
- SaaS tools (Google/Airtable/Mapbox) create surveillance and lock-in.
- Use as pattern source; re-implement with self-hosted alternatives.
Useful entry points
Role: expansion layer for specialized situations
•
Use: pick modules by terrain (health, infrastructure, disaster type)
What it’s best at
- Cross-linking zines that operate as field manuals (distribution, safety, DIY infra).
- Providing a “second ring” beyond the kernel when new crises hit.
- Keeping anti-oppression and survival logistics connected.
How to avoid drift
- Don’t treat index breadth as priority; keep Kernel alignment first.
- Extract what you need, then store offline (print/cache).
Role: backend library for organizing skills + mutual aid links
•
Warning: campaign/electoral content can recode your frame
Whitelist these kinds of items
- Mutual aid intros, MADR guides, hub guides, EFF digital-safety material.
- Facilitation skills and conflict transformation that preserve autonomy.
Avoid unless explicitly needed
- Electoral campaigning playbooks.
- NGO “program management” templates and impact-metric scripts.
6 — Telemetry / Directory Nodes (High-Risk, High-Info)
These are useful to find peers and study patterns, but they also produce network graphs.
Treat them as optional and threat-dependent.
Role: discovery map
•
Risk: exposure + research sampling frame
When it’s useful
- Locating existing groups in unfamiliar regions.
- Studying how mutual aid networks self-present publicly.
Why it’s risky
- Centralized directory becomes a dataset for targeting or monitoring.
- Public mapping can expose fragile formations and vulnerable people.
Context links (civic-tech ecosystem)
Role: fund/resource directory + validation of core toolkits
•
Terrain: reproductive justice under hostile law
Use it for
- Understanding how mutual aid integrates with reproductive justice.
- Seeing what resources are actually referenced in practice (toolkit staples).
Telemetry caution
- Public lists of funds and support networks can be targeted.
- Mirror the patterns, not necessarily the visibility model.
7 — Historical & Canon Anchors
These anchors prevent the “mutual aid = pandemic-era volunteerism” collapse.
They point to deeper lineages and help you build memory beyond the current cycle.
Role: canon pointer (Panthers, liberation movements, organizing lineages)
•
Use: seed list for finding open digital equivalents
Extractable value
- Signals what movements and texts are treated as foundational in mutual-aid-adjacent organizing history.
- Provides search seeds: “survival programs,” “mutual aid,” “community self-defense,” etc.
Limits
- Institution-curated canon; expect omissions.
- Often not directly accessible digitally.
8 — Mandatory Extension Modules (Bind Into This Atlas)
The mutual-aid library corpus is strong on organizing and community care, but it is structurally thin in:
(1) monetary sovereignty, (2) AI-aware security/infiltration defense, (3) energy/water/comms,
(4) global/indigenous traditions, and (5) lifecycle/fork/dissolution protocols.
These must be snapped into the atlas from your other Sov-Stack libraries.
Module 1 — Money & Flows
- Cash vs surveilled rails, disbursement privacy, durable donation flows.
- Attach directly to: SELC (tax/barter), Shareable (financial tech), Spark RJ (fund directories).
Module 2 — AI-Aware Security & Infiltration
- Assume public docs become training data; assume graph targeting; assume synthetic identities.
- Attach to: EFF baseline, Shareable surveillance/cybersecurity module, MADR security content.
Module 3 — Energy / Water / Comms
- Mesh networks, radios, offline caches, power storage, water filtration, logistics caches.
- Attach to: MADR hub toolkit, CROs modules, Library of Things patterns.
Module 4 — Global / Indigenous Mutual Aid Traditions
- Explicit inclusion beyond the Anglo/US corpus.
- Attach to: MADR indigenous zines; expand via open digital sources.
Module 5 — Lifecycle / Fork / Dissolution
- Designed endings, succession, clean handovers, fork protocols.
- Attach to: any group formation guide that only teaches “start/sustain.”
Appendix — Print / Offline Notes
If you expect intermittent connectivity or high-risk surveillance, prioritize resources that are printable PDFs/zines:
MADR zines, Sparrow’s intro zine, #WeGotOurBlock toolkit, MADR hub toolkit, and the CROs offline-first modules.
Offline discipline: download → print/cache → remove unnecessary digital logs.
The more your mutual aid operation depends on a single online platform, the more easily it can be mapped, throttled, or recoded.