Permacomputing Collective (LM-Dawn class)

Class card for the LM-Dawn coordination form in which practitioners build, maintain, and share digital infrastructure within biophysical limits: renewable-energy ceilings, repair-as-protocol, radical longevity of devices and software, and slow-pedagogy transmission of craft knowledge. Emergence subtype: meritocratic_hierarchy (skilled practitioners self-sort by demonstrated repair and design competence; no credential system; no telos of Progress drives production — motor=null). Canonical instances: Hundred Rabbits collective (2017, off-grid sailing vessel computing), Collapse OS / Dusk OS projects (2019/2022, survivable computing on scavenged Z80/68k hardware), Low-Tech Magazine solar-powered website (2018, running on a Raspberry Pi with battery cutout at low solar yield), OLPC XO successor repair networks, and the broader permacomputing.net community discourse (2021–present). Distinguishing features versus DM-era cloud infrastructure: (1) motor is absent — practitioners are driven by eudaimonic craft values, post-collapse readiness, and ecological alignment, NOT by efficiency maximisation or capital returns; (2) energy budget is a hard ceiling, not a variable to optimise away (renewable-energy ceiling logic is definitional); (3) repair- as-protocol: devices and software must be fixable by the operator using local materials and documented techniques — no black-box opaque stacks; (4) slow-pedagogy: knowledge transmission favours deep competence re-internalization over high-throughput tutorial consumption — the Stiegler tertiary- retention loop is explicitly managed, not left to market forces; (5) capture_resistance_index is structurally high because the coordination form produces no extractable surplus, runs on commodity-scavenged hardware, and has no IP to capture. LM-Dawn framing: permacomputing represents a Liveness-Machine coordination pattern where the ecological-constraint logic exceeds the DM's resource-throughput maximisation frame. The LM-class view sees the collective not as a fringe hobbyist community (the DM observer's frame) but as a carrier of competence for post-DM computing infrastructure — a technical-memory institution whose proletarianization_risk is low precisely because repair-as-protocol keeps living competence in-loop. Cross-era position: [CANON] permacomputing emerged from DM-era OSS culture (Linux/Unix toolchain, C/Forth/Lua as repair-grade languages, git as distributed archival substrate) but reframes OSS logic under biophysical constraints the DM era did not impose. Hostile_inheritance from DM cloud infrastructure: the dominant DM technology stack (AWS, container ecosystems, JavaScript dependency graphs with thousands of transitive deps) is architecturally antithetical to permacomputing's longevity and repairability norms. Zombie_dependency toward MM industrial semiconductor fabrication: the collective's hardware substrate (scavenged silicon from pre-2010 chips, solar panels, batteries) is physically produced by MM/DM foundry infrastructure that the collective cannot itself reproduce — zombie, because the fab industry has migrated to nanometer nodes irrelevant to permacomputing's preferred 500nm–90nm "good-enough computing" range. Substrate_provision from DM open-source ecosystem: the OSS toolchain (gcc, Linux kernel, git, Python) is the foundational technical substrate the collective takes as unquestioned given. All quantitative state-variable values are [EXTRAP]; LM-Dawn framing is [CANON] per Wave-6 cross-era-coupling-typology §1.4.