Mutual-Aid Protocol Extension (LM-Dawn class)

Class card for the LM-Dawn PROTOCOL LAYER that sits above and extends mutual-aid networks (sibling machine:mutual-aid-network-scale-class). Where the sibling encodes the ground-level community/network form of mutual aid (neighborhood pods, COVID surge networks, disaster-response cells), THIS card encodes the INSCRIBED PROTOCOL SUBSTRATE that enables those networks to coordinate at scale across pods, cities, and crises without dissolving into either charity formalism or capture by DM platform infrastructure. FOUR PROTOCOL SUB-FAMILIES IN SCOPE: (1) CARE-PROTOCOLS: standardized, open-licensed procedures for delivering specific mutual-aid services — food-distribution protocols, medical-supply-request protocols, translation/interpretation protocols, childcare-pod protocols, mental-health peer-support protocols. These are the inscribed procedure artifacts that allow a network in Boston to share protocols with a network in Los Angeles and reproduce coordination effectiveness without personnel transfer. Examples: Big Door Brigade open-source mutual-aid protocols (~50 documented templates, post-2018); CrimethInc / Black Rose / Tilted Scales mutual- aid handbooks; ROAR mutual-aid templates (~30 documented). (2) FEDERATION / CROSS-NETWORK COORDINATION PROTOCOLS: protocols for inter-network resource sharing, mutual-network referral, and crisis-surge coordination across geographically distributed pods. Examples: Mutual Aid Disaster Relief (~150 affiliates coordinating under shared disaster-response protocol); Solidarity Networks Boston- NYC-LA federation protocols; Hands On Network (~2.5M volunteers under shared protocol framework); Climate Emergency Mutual Aid (~80 UK groups via shared protocol structure). (3) CAPABILITY-DISCOVERY PROTOCOLS: mechanisms for pods to publish and discover each other's capabilities, resource surpluses, and need gaps without centralized registry control. Examples: Open Source Care Network (post-2020 COVID; ~5K care protocols documented); Care Cooperative inter-network registry; Resilience Hubs network (~200 US cities, shared capability-disclosure framework). (4) GOVERNANCE-OVER-RESOURCE-POOLS PROTOCOLS: protocols for collective decision-making over pooled mutual-aid resources — timebanks, shared tool libraries, emergency funds — that preserve horizontal accountability without donor-recipient hierarchy. Examples: Distributed Cooperative Aid Group (~300 contributors under shared governance protocol); MEND Project (~40 implementing communities). DISTINCTION FROM SIBLING NETWORK CARD: machine:mutual-aid-network-scale-class models the PRACTICE LAYER: coordinators, recipients, WhatsApp groups, food drops. THIS card models the PROTOCOL LAYER: the inscribed procedures, handbooks, data standards, and federation structures that make the practice layer reproducible and federatable at civilizational scale. The two are constitutively coupled: the protocol layer provides operational scaffolding for the network form (intra-LM mutualistic); the network form provides empirical use cases that drive protocol iteration (reverse coupling). Neither can reach LM scale without the other. THEORETICAL ANCHORS: Kropotkin "Mutual Aid: A Factor of Evolution" (1902): MM-Dusk theoretical anchor for the reciprocal-aid evolutionary logic; the protocol layer IS Kropotkin's "mutual aid as civilizational machinery" made technically legible. Dean Spade "Mutual Aid: Building Solidarity During This Crisis" (2020): DM→LM operational anchor — Spade's appendix on organizing structures constitutes an early protocol-layer document (handbook as protocol template). Wave-6 generators §2.4 mutual-aid-network-scale-class seed; Wave-0 LM coordination signature. EMERGENCE SUBTYPE (mutual_aid_protocol_extension — description-only flag): Protocols emerge from both bottom-up practitioner codification (crowdsourced: networks write down what worked) AND top-down specialist curation (meritocratic_hierarchy: protocol editors review + merge submissions). EmergenceSubtype enum has only 2 values; this is a hybrid. PROLETARIANIZATION RISK is MODERATE (0.58 [EXTRAP]): care protocols are inscribed artifacts that persist even when the practitioner community thins (Stiegler tertiary retention). However, EFFECTIVE protocol USE requires living competence — knowledge of local context, relationship trust, translation between protocol template and community situation. A dead protocol library with no active practitioner re-internalization is the proletarianization-terminus scenario: inscribed protocol persists; no living community reproduces it in practice. CAPTURE RESISTANCE: protocols are the primary mechanism by which mutual-aid networks resist DM capture vectors. Open-licensed protocol templates (Creative Commons, GPL) prevent single-actor ownership; federation protocols distribute decision-making; capability-discovery protocols eliminate single-registry bottlenecks. capture_resistance_index HIGH (0.68 design intent [EXTRAP]). All quantitative values are [EXTRAP]; framing and named instances are [CANON-framing; EXTRAP-classification] per Wave-6 seed and Spade (2020).