Fediverse Protocol Collective (LM-Dawn class)

Class card for the LM-Dawn cluster of operative collectives that run federated social infrastructure — the people-running-protocols layer above the protocol-architecture-as-design-principle layer (that is machine:capture-resistance-protocol-class, a sister LM card on disk). Where the sibling card models the ActivityPub/AT Protocol/Matrix specs as artifact machines, THIS card models the distributed human collectives that deploy, govern, fund, and maintain those protocols in practice: Mastodon instance admins (8,000+ servers as of 2024), Pixelfed federation operators, PeerTube instance operators (~1,000+ instances), Lemmy admins (Reddit-alternative; LemmyNet 2019+), WriteFreely publishers, Funkwhale audio-hosting operators, Mobilizon event-instance operators, and BookWyrm (GoodReads-alternative) hosts. Adjacency-lift mechanic (Wave-6 §3 Hidalgo): the DM substrate info-substrate-social-platform-1995 (X/Twitter/Meta/YouTube) provides the social-coordination input categories and UGC production patterns that Fediverse operator collectives re-instantiate at human scale. The open-source-ecosystem-class (LM) provides the governance templates (meritocratic patch culture, community moderation, license discipline) and technical substrate (Mastodon = Ruby on Rails OSS; PeerTube = Node.js OSS; Lemmy = Rust OSS). The W3C/IETF/ICANN internet-governance layer provides the protocol-commons substrate. The Hidalgo lift: φ(info- substrate-social-platform, fediverse-operator-collective) ≈ 0.45 — shared input categories (UGC, social-graph, content-moderation, ad-hoc funding), distinct output categories (no behavioral-surplus extraction, no algorithmic engagement maximization, no advertising OPP). Operator-collective anatomy (2026): (1) Instance admins: individual volunteers or small teams running ActivityPub-compatible servers. hachyderm.io (community-funded; ~45k users; Kris Nova founded 2022), infosec.exchange (~25k users; information-security community), mastodon.lol (general-purpose), eu.mastodon.social (European users). Funding: Patreon, OpenCollective, instance-membership fees, personal subsidy. (2) Instance moderation cooperatives: Fediverse Server Covenant (baseline terms — active moderation of hate speech, daily backups, responsible shutdown notice). Instance-block coordination: defederation is the primary governance mechanism; no central authority controls who federates with whom. (3) Bridge operators: ActivityPub↔AT Protocol bridge operators; Threadiverse bridges (Lemmy↔Mastodon); relay operators (Mastodon relay networks that propagate posts between instances). (4) Code/protocol contributors: W3C Social Web Working Group (ActivityPub maintenance); AT Protocol Working Group (Bluesky PBC); Matrix.org Foundation; individual contributors to Mastodon/PeerTube/Lemmy codebases on GitHub. (5) Governance-layer actors: Fediverse Server Covenant signatories; defederation-list maintainers (blocklist.fedisafe.space, the Bad Space); instance-level Terms of Service authors; content-warning norms established by community practice. Key instance-level monopoly risk: Mastodon.social (run by Mastodon gGmbH, Eugen Rochko) hosts ~20%+ of total ActivityPub MAU in 2024 — the largest single server creates server-monopoly concentration risk at the operator- collective layer, even as the protocol-architecture layer remains capture-resistant. This is the principal distinguishing stress from machine:capture-resistance-protocol-class: the protocols are structurally non-capturable; the operator layer is not — dominant instances CAN de-facto set norms for the federation. Meta (Threads) joined ActivityPub federation 2024 via ActivityPub bridge: the largest DM platform wading into the federation layer is the primary hostile_inheritance signal at the OPERATOR layer (not just the protocol layer). Threads can asymmetrically participate — receive ActivityPub content, limit outbound federation — putting normative pressure on operator collectives to either defederate Threads or accept its participation on asymmetric terms. Bluesky AT Protocol (Jack Dorsey 2023+) represents an alternate protocol-family within Fediverse-adjacent space — different technical architecture (crawler-based vs. push federation) with stronger account- portability guarantees and an algorithmic-feed marketplace. AT Protocol operator collectives are structurally analogous to ActivityPub operator collectives but with a heavier PDS (Personal Data Server) operator role. Funding discipline: the operative-collective layer is dominated by donation-funded models (Patreon, OpenCollective) that are structurally fragile. The December 2022 Mastodon surge (~7M new signups post-Twitter- acquisition) exposed operator burnout: volunteer admins of mid-size instances faced sudden load without proportional funding increases. Proletarianization risk MEDIUM (0.55 [EXTRAP]): admin competence is informal (no systematic knowledge transfer); burnout leads to instance shutdowns with data loss risk; new admins must re-acquire community- governance competence from scratch for each instance. LM mechanism signatures: capture_resistance_index HIGH at protocol layer (per sibling card) but MEDIUM (0.50) at operator layer due to dominant- instance concentration risk; proletarianization_risk MEDIUM (0.55); rewilding_fraction LOW (0.05 — this is a digital infrastructure machine, not a physical rewilding machine); liveness_temporal_coupling MEDIUM (0.60 — federation events are real-time but instance-policy evolves slowly; operator-collective culture changes at governance pace); pace_layer=infrastructure (social-substrate provision for the federated public sphere). emergence_subtype: operator-collective (distinct from crowdsourced UGC production and from algorithmic-feed architecture; the Fediverse operator- collective is a GOVERNANCE-FORM emergence: distributed human coordination around shared protocol standards without a profit motive). [EXTRAP] per §B.9 — absorption into Machine.description per v0.2 constraint. Cross-era position: hostile_inheritance from DM meta-social-media and X-Twitter (Threads/Meta joining ActivityPub asymmetrically; X-Twitter's API lockdown was the precipitating event for the 2022 Mastodon surge); substrate_provision from DM linux-open-source-ecosystem (all Fediverse server software runs on Linux/OSS stacks — Mastodon on Ruby/Rails, PeerTube on Node.js, Lemmy on Rust, all deployed on Debian/Ubuntu servers); zombie_dependency from MM national-electrical-grid (operator instances run on physical servers requiring MM-era electrical infrastructure); adapted_inheritance from DM github-code-collaboration (Fediverse server code developed and hosted on GitHub, a DM platform, which has adapted to serve LM-Dawn open-source community projects); mutualistic_coupling (intra-LM) with capture-resistance-protocol-class (the operative collectives ARE the instantiation layer for the protocols; the protocols provide the technical substrate the collectives govern). All quantitative state-variable values are [EXTRAP]; factual records of Mastodon instances, Fediverse Server Covenant, and ActivityPub adoption are [CANON].