# Commons & Community Governance MOC ## Synthesis additions (2026-10-17 — what a code of conduct file can and can't show) - [[3. Resources/Permanent Notes/A Code of Conduct File Being Present and Being Maintained Are Separate Facts]] — a code of conduct's edit history is checkable, but the study found no edit pattern that predicts health, so an untouched file is a question and not a verdict. ## Synthesis additions (2026-10-16 — what happens after a code of conduct is adopted) - [[3. Resources/Readwise/Articles/Episode 295 Jiayi Sun & Shurui Zhou on Codes of Conduct in Open Source Communities]] — SustainOSS: researchers' study of 150,000+ GitHub repositories; over 75% never edit their code of conduct after adopting it, adoption is followed by both new contributors joining and existing ones leaving, and long-term changes are minimal. The host's opinions are kept apart from the findings; the denominator behind the 75% is not stated. ## Synthesis additions (2026-10-01 — Automattic board turnover and the WP Engine docket) - [[3. Resources/Readwise/Articles/WordPress Owner Automattic’s Board Reportedly Purged After Failed ‘Coup’ Against CEO]] — Gizmodo, relaying TechCrunch, reports Automattic's board voted 2026-09-09 to put Matt Mullenweg on leave and he was back about 33 hours later, followed by board and executive departures. Adds WP Engine sanctions-motion context only. - [[3. Resources/Readwise/Articles/Matt Mullenweg Just Replaced Automattic’s Board. 2 of His Picks Come From a Shuttered $1 Billion App]] — Inc.'s Victoria Salves reports Mullenweg replaced the board about 33 hours after it voted him onto paid leave, relying on TechCrunch and The Information. Some departures are "reportedly" only. - [[3. Resources/Readwise/Articles/Automattic & Matt Mullenweg Fail to Dismiss WP Engine Antitrust Claims]] — Search Engine Journal reports the motion-to-dismiss ruling in WP Engine v. Automattic: WP Engine's four antitrust claims and its WooCommerce claims survive. A pleading-stage ruling, not a merits finding. ## Synthesis additions (2026-10-01 — labor, contribution, and project control) - [[3. Resources/Readwise/Articles/For Love or Money Open Source’s Labor Law Problem]] — Sé Reed argues the FLSA turns on the reality of the working relationship, and proposes eight control-and-benefit questions for when contributors stop being "just volunteers." Commentary, not legal advice. - [[3. Resources/Readwise/Articles/A Note on Figma Access]] — Joen Asmussen's Make Design notice says Automattic pays for the scarce Figma edit seats, explains why "anyone can edit" links strain them, and asks admins to downgrade approved access after a month. - [[3. Resources/Readwise/Articles/The DHH Problem]] — davidcel.is essay (2025-09-19) argues David Heinemeier Hansson's views harm the Ruby and Rails communities and that Rails and RubyGems governance should become member-run. Opinion; the characterizations are the author's. - [[3. Resources/Readwise/Articles/Update on the WordPress Community Groups on events.wordpress.org]] — Karen Alma Arnold's Make Community post reports the move of roughly 700 meetup groups from Meetup.com to events.wordpress.org, with test feedback and talks with Meetup.com. First-party project update. ## Synthesis additions (2026-10-01 — enshittification and platform accountability) - [[3. Resources/Readwise/Articles/Enshttification Expert They Plan to Make the Internet Worse Cory Doctorow]] — Cory Doctorow tells The Jordan Harbinger Show that platform decay follows from unenforced antitrust law, anti-circumvention law such as DMCA 1201, and regulatory capture. Auto-captions garble names; verify before quoting. - [[3. Resources/Readwise/Articles/The Facebook Fake-Out]] — Anil Dash's short opinion essay says Meta repeats a five-step cycle: launch a privacy-violating feature, get caught, announce a pause, wait for attention to move, relaunch. Pattern asserted, not documented case by case. ## Synthesis additions (2026-10-01 — data centers, public trust, and who pays) - [[3. Resources/Readwise/Articles/Open Source Datacenters and Open Source Thinking Will Undo Self-Inflicted DC Damage]] — Rupert Goodwins argues in The Register that datacenter secrecy about energy and siting fuels public opposition and that the industry should adopt open source's habit of radical openness. Opinion column. ## Synthesis additions (2026-09-26 — naming enshittification for consumers) - [[3. Resources/Readwise/Articles/Enshittification Has a New Mascot, and He’s Teaming Up With Death in a Hilarious Ad Campaign]] — Joe Hindy, CNET (2026-09-26) on the Norwegian Consumer Council's Breaking Free campaign: durability is a revenue defect only to a seller whose income stops at the sale; a named decay pattern lets people aim complaint at the business model instead of the product; links the Council's 2026-02 report, Apple's iPhone-slowdown settlement, Google Photos 2021, BMW heated-seat subscriptions ## Synthesis additions (2026-09-05 — a values claim as evidence only when tested at cost) - [[3. Resources/Permanent Notes/A Stated Principle Is Only Evidenced When It Is Applied at Cost]] — gives a test for reading any institution's self-reported transparency or ethics claims: find the instance where holding the principle cost something measurable. ## Synthesis additions (2026-09-05 — accountability structure design) - [[3. Resources/Permanent Notes/A Support Group Is Only a Check If It Can Contradict You]] — a peer group only functions as a check on judgment if it can and does contradict you, not merely if it shares your perception ## Synthesis additions (2026-09-05 — holding a volunteer title as usefulness, not rank) - [[3. Resources/Permanent Notes/In Volunteer Communities Hold a Visible Role as a Tool for Usefulness Not as Rank]] — Aditya Kane's 'lanyard anarchism' coinage: wear a long-tenure title because it opens doors to help, decline only the rank it could confer — directly relevant to The WPOCC's organizer culture. ## Synthesis additions (2026-09-05 — mechanisms an operator can override) - [[3. Resources/Permanent Notes/A Mechanism Its Operator Can Override Is Not the Mechanism It Claims to Be]] — Amazon's ad-auction override defense as a worked example of a process whose legitimacy depends on its operator not being able to set aside the result ## Synthesis additions (2026-08-31 — how the cost is settled) - [[3. Resources/Permanent Notes/An Externality Is Settled in Capability Withdrawn Not in a Bill Anyone Contests]] — Ostrom's design principles assume costs can be attributed; this is the case where they cannot, so the commons only registers the loss at the moment it closes access to survive. ## Synthesis additions (2026-08-24 — backlog gap-fill (second pass)) - [[3. Resources/Permanent Notes/Authorship and Authority Are Separate Grants]] — originating a community's vision is real and non-transferable; it confers no unappealable decision rights. ## Synthesis additions (2026-08-24 — who the process filters out) - [[3. Resources/Permanent Notes/Procedural Burden Falls Hardest on Those With Least Standing]] — reporting conditions written to deter bad-faith accusers deter frightened good-faith ones first, because only the latter read them and conclude they don't qualify. - [[3. Resources/Permanent Notes/Absence of Complaint Is Resignation Not Satisfaction]] — what the institution observes downstream once the burden has done its work, and misreads as things being fine. - [[3. Resources/Permanent Notes/One Channel Cannot Carry Both Project Voice and Commercial Interest]] — the governance failure located in the communications channel rather than in the decision process. - [[3. Resources/Permanent Notes/Funding Authority and Design Authority Should Never Be the Same Body]] — Ostrom-adjacent: the rule removes the capture lever rather than relying on funder restraint. - [[3. Resources/Permanent Notes/Recruiting Someone Into a System Obliges You to Disclose Who Owns It]] — informed consent applied to volunteer labor; the asymmetry is that insiders know the ownership and the recruited person by construction does not. ## Synthesis additions (2026-08-11 — labor governance) - [[3. Resources/Permanent Notes/AI Deployment Is a Bargaining Issue Not Just a Tooling Decision]] — places automation decisions inside collective worker governance when employment conditions change. A cross-domain map connecting ideas about how communities—whether open source projects, faith communities, cooperatives, or other commons—govern shared resources and balance individual autonomy with collective good. ## Core Question How do communities sustainably govern shared resources while honoring both individual freedom and collective flourishing? --- ## Foundational Framework: Ostrom's Design Principles Elinor Ostrom's 8 design principles for successful commons (from *Governing the Commons*, 1990): 1. **Clearly defined boundaries** — Who is a member? What are the shared resources? 2. **Rules fit local circumstances** — No one-size-fits-all; local adaptation is essential 3. **Collective-choice arrangements** — Those affected can participate in modifying rules 4. **Monitoring** — Monitors are accountable to the community or are community members 5. **Graduated sanctions** — Warnings before expulsion; correction aims at restoration 6. **Conflict resolution** — Accessible, low-cost mechanisms to resolve disputes 7. **Recognition of rights to organize** — External authorities respect community self-governance 8. **Nested enterprises** — For complex resources, governance at multiple scales --- ## The Central Tension **The commons that deny exit become coercive; the commons that demand nothing become meaningless.** Sustainable community requires: - **Voluntary entry with clear expectations** (Benedictine vows, open source licensing) - **The freedom to leave** (right to fork, prophetic dissent) - **Graduated response to harm** (Matthew 18, Ostrom's sanctions) - **Distributed authority** (subsidiarity, polycentric governance) - **Intrinsic motivation cultivated through meaning, not mandated through law** (grace vs. legalism) --- ## Belonging Is Designed, Not Declared (added 2026-06-09) Ostrom's first principle — *clearly defined boundaries* — has an inclusion corollary: boundaries can be drawn so belonging is signaled *in advance*, rather than left for newcomers to verify on arrival. - [[3. Resources/Permanent Notes/Being Anticipated Beats Being Tolerated - Visible Inclusion Shifts the Burden]] — Sam Alderson's distinction between a space that *tolerates* (passive permission; the marginalized person carries the verification labor) and one that *anticipates* (active design; the institution carries it). The burden of belonging is conserved — the only question is who carries it. (Seed for a possible dedicated DEIB thread; currently homed here for the community-governance angle.) --- ## Key Sources by Domain ### Commons Theory - [[3. Resources/Readwise/Books/Working in Public]] — Nadia Eghbal applying Ostrom to open source - [[3. Resources/Readwise/Books/The Art of Community|The Art of Community]] — Jono Bacon on building participatory communities - Ostrom, E. *Governing the Commons* (1990) - Hardin, G. "Tragedy of the Commons" (1968) — the problem Ostrom solved ### Open Source Governance - [[3. Resources/MOCs/Open Source Governance MOC]] - [[3. Resources/Readwise/Articles/The Ethos of Open Source]] — Mitchell Baker on right to fork - [[3. Resources/Readwise/Podcasts/LISA11 - Fork Yeah! The Rise and Development of illumos]] - [[3. Resources/Readwise/Articles/A Word About Open Source Citizenship, Winning Hearts and Minds, and WPDrama]] ### Faith & Theology - [[3. Resources/MOCs/Faith & Theology MOC]] - [[3. Resources/Readwise/Books/Life After Doom]] — Brian McLaren on collective action - [[3. Resources/Readwise/Books/Thou Shalt Not Be a Jerk]] — Eugene Cho on kingdom vs. tribal loyalty - [[3. Resources/Readwise/Books/Confronting Our Freedom]] — Peter Block on accountability and freedom - Rule of Benedict — 1,500 years of successful commons governance ### Catholic Social Teaching - **Subsidiarity**: "Nothing should be done by a larger organization which can be done as well by a smaller one" - **Solidarity**: We are responsible for one another - **Common good**: Not the sum of individual goods, but the conditions for human flourishing --- ## Cross-Domain Patterns | Pattern | Open Source | Faith | Cooperatives | |---------|-------------|-------|--------------| | **Healthy exit enables healthy voice** | Right to fork | Prophetic dissent | Member withdrawal rights | | **Boundaries define belonging** | Licensing, contributor agreements | Covenant, membership | Bylaws, membership criteria | | **Imposed obligation fails** | Mandated quotas don't work | Legalism vs. grace | Forced participation backfires | | **Diversity serves unity** | Multiple projects coexist | Spirit harmonizes | Federated structures | | **Leadership as stewardship** | Maintainers curate, not control | Servant leadership | Elected boards serve members | --- - [[3. Resources/Permanent Notes/Composable Labeling Trades One Standard for Parallel Capacity]] — parallel community capacity in exchange for no single party answerable for a bad call. ## Key Tensions to Navigate ### 1. Who Defines the Common Good? - **BDFL/NAR model**: Single authority defines; efficient but risks tyranny - **Pure democracy**: Everyone votes; inclusive but risks paralysis - **Polycentric**: Multiple centers at appropriate scales; complex but resilient ### 2. Contribution vs. Consumption (Free-Rider Problem) - **Open source**: "Five for the Future" model, contributor recognition - **Faith**: Tithing, stewardship campaigns, volunteer coordination - **Research finding**: Framing as "donation" generates more than "contribution" because it feels voluntary ### 3. Autonomy as Escape vs. Autonomy as Responsibility - Forking can be freedom or fragmentation - Prophetic witness can be faithful dissent or schism - The difference: Does exit serve the commons or only the individual? ### 4. Intrinsic vs. Extrinsic Motivation - Research: Imposing norms crowds out intrinsic motivation - Block: "Accountability cannot be imposed; it occurs as outgrowth of freedom" - The leader's role: Cultivate conditions for intrinsic motivation, not enforce compliance --- - [[3. Resources/Permanent Notes/An Objection That Survives Its Own Removal Was Never the Objection]] — a test for whether a stated community objection is the real one — specify the condition, remove it, watch what happens. - [[3. Resources/Permanent Notes/Private Agreement Exceeding Public Agreement Measures Community Climate]] — the gap between private and public criticism measures the perceived cost of speaking, not who is right. ## The Leader's Role in Commons Governance Neither BDFL nor NAR apostle should *enforce* the common good. Their role is to: 1. **Cultivate intrinsic motivation** — make contribution meaningful, not mandatory 2. **Maintain clear boundaries** — so members know what they're committing to 3. **Model the values** — leadership as stewardship, not control 4. **Protect exit rights** — the freedom to leave legitimizes the choice to stay 5. **Facilitate graduated response** — correction aims at restoration --- ## Historical Examples of Long-Lived Commons ### Benedictine Monasteries (~1,500 years) - Average lifespan: ~500 years - Only 25% dissolved due to internal governance failures - Three pillars: common values, democratic structures, internal/external oversight - The Rule provides principles that adapt to local conditions ### Swiss Alpine Commons (~800+ years) - Ostrom's primary case study - Clear boundaries, local rules, graduated sanctions - Survived because members could always leave but chose to stay ### Open Source Foundations (~30+ years) - Apache, Linux Foundation, Mozilla - Legal protection + community governance - Right to fork prevents tyranny --- ## Permanent Notes ### Created - [[3. Resources/Permanent Notes/Ostrom-Theology Crossover - Commons Governance in Faith and Code]] - [[3. Resources/Permanent Notes/The Merit Trap - Self-Worth in Systems of Singular Authority]] - [[3. Resources/Permanent Notes/Belonging Requires Choice Connection and Progress]] — Three conditions for community retention; missing any one collapses engagement - [[3. Resources/Permanent Notes/The Seven Principles Are a Community Diagnostic]] — Boundary, initiation, rituals, temple, stories, symbols, inner rings as structural requirements - [[3. Resources/Permanent Notes/The Maker-Taker Frame Confuses Two Different Scarcities]] — Anti-rivalrous code vs rivalrous customers - [[3. Resources/Permanent Notes/Coerced Contribution Kills the Commons]] — Mandating contributions crowds out intrinsic motivation - [[3. Resources/Permanent Notes/Open Source Projects Are Not Communities by Default]] — Most projects have audiences, not communities - [[3. Resources/Permanent Notes/Declared Freedom Is Real Only When the State Can Enforce Non-Discrimination]] — (added 2026-06-21) Heather Cox Richardson's Juneteenth argument generalized: a declared right/covenant is real only to the degree it can be *enforced* (14th Amendment as the enforcement mechanism behind the Emancipation Proclamation). The governance corollary — design the enforcement path in the same breath you declare the right. - [[3. Resources/Permanent Notes/Trademarking a Commons's Descriptive Terms Converts a Steward Into a Gatekeeper]] — (added 2026-07-09) the enclosure failure mode for a commons: a steward asserting ownership of the commons's shared descriptive language and charging rent on it. The gatekeeping cognate of [[3. Resources/Permanent Notes/Open Source Projects Are Not Communities by Default]] — controlling the name controls who may claim belonging. ### To Create - [ ] Subsidiarity and polycentric governance are the same insight from different traditions - [ ] The right to exit legitimizes the choice to stay - [ ] Graduated sanctions preserve relationship; expulsion destroys it - [ ] Intrinsic motivation cannot be mandated (grace vs. law in economic form) - [ ] Clear boundaries increase freedom (paradox of covenant) --- ## Literature Notes - [[3. Resources/Literature Notes/Individual Autonomy vs Collective Good - Literature Review]] - [[3. Resources/Literature Notes/BDFL and NAR - Parallel Structures of Charismatic Authority]] - [[3. Resources/Literature Notes/Community Architecture - What Makes Communities Thrive vs Extract - Literature Note]] — What separates healthy communities from extractive ones --- ## Connections to Other MOCs - [[3. Resources/MOCs/Open Source Governance MOC]] — Application to software projects - [[3. Resources/MOCs/Faith & Theology MOC]] — Application to faith communities - [[3. Resources/MOCs/Visual Thinking MOC]] — Documenting governance visually --- ## Idea Compass **Parents (broader concepts)** - Political philosophy (liberty vs. equality) - Organizational theory - Public goods economics - Social contract theory **Children (specific applications)** - WordPress governance reform - Church governance models - Cooperative bylaws - Foundation membership decisions **Friends (adjacent ideas)** - Restorative justice - Servant leadership - Covenantal relationships - Polycentric mission **Competitors (tensions/alternatives)** - Libertarian individualism (no collective obligation) - Authoritarian collectivism (no individual autonomy) - Tragedy of the commons (Hardin's pessimism) --- ## Questions for Further Research 1. How do different faith traditions (Judaism, Islam, Buddhism) approach the autonomy/collective tension? 2. What can we learn from worker cooperatives about commons governance? 3. How do indigenous governance traditions compare to Ostrom's principles? 4. What are the failure modes when these principles are violated? 5. How does digital technology change the dynamics of commons governance? --- ## Live Case Study: WordPress Commons Capture (2024-2026) A real-time ostromite stress test. Multiple of Ostrom's design principles under simultaneous strain — boundaries (WP Engine ban), collective-choice (Foundation as "shell nonprofit"), monitoring (Drupal-style credit accountability proposed but no equivalent in WP), conflict resolution (litigation rather than community processes). ### Vantages by Ostrom principle - **Boundaries** (Principle 1): [[3. Resources/Readwise/Articles/Timeline of the WordPress Drama - DevLog]] — .org infrastructure as boundary enforcement against WP Engine, including security updates - **Collective-choice arrangements** (Principle 3): “I obviously don't want any harm to come to WordPress” (Mullenweg; not yet in vault) — Lapinski's "shell nonprofit" first-hand account from Foundation volunteering - **Monitoring** (Principle 4): [[3. Resources/Readwise/Articles/Grow the ecosystem, not just yourself]] — Buytaert's 2,955-vs-30 credits framework as Drupal's monitoring infrastructure - **Conflict resolution** (Principle 6): [[3. Resources/Readwise/Articles/Matt Mullenweg Uses WordPress’s 23rd Birthday to Appeal Directly to Silver Lake “You’ve Won. I Submit.”|Matt Mullenweg Uses WordPress's 23rd Birthday to Appeal to Silver Lake]] — "You've won. I submit." as litigation-substitute conflict signal - **Self-organization recognition** (Principle 7): [[3. Resources/Readwise/Articles/The WP Community Collective Launches State of the Community Survey]] — WPCC as independent community measurement effort outside Foundation/Automattic structures ### Theoretical question If Ostrom's framework predicts that violation of multiple principles simultaneously leads to commons collapse, what does the WordPress case suggest about non-rivalrous digital commons specifically? Is the "stadium" pattern (per [[3. Resources/Permanent Notes/The Stadium Is the Dominant Open Source Pattern]]) inherently fragile in ways that traditional commons are not? ## Synthesis additions (2026-06-11) From the 3-day Readwise review — new atoms wired in: - [[3. Resources/Permanent Notes/Standards Governance Benefits From Categorical Precision Over Comprehensive Definition]] — obligations-scoped categories carry governance weight that broad definitions can't ## Synthesis additions (2026-06-15) - [[3. Resources/Permanent Notes/Vernacular Software Survives the Bubble Because It Is Unmonetizable by Design]] — Doctorow: deplatformed homemade software the market can't capture is the durable, commons-friendly use of AI; "the street finds its own use for things." Cross-homed from [[AI & the Future of Knowledge Work MOC]]. ## Connected Literature Notes (synthesis 2026-06-17) - [[A Guide to Community Analytics]] — data-informed governance of communities - [[A Guide to Community Operations]] — operational backbone of community governance ## Connected Literature Notes (synthesis 2026-06-18) - [[Ada Developers Academy - A Tuition-Free Coding School]] — equitable access as community health - [[Blackfoot Wisdom, Maslow’s Hierarchy, and Open Source]] — collective self-actualization as a commons health metric (synthesis 2026-06-21) ## Synthesis additions (2026-06-28 gap-fill) - [[3. Resources/Permanent Notes/A Frontier Lab Can Learn From the World While Restricting the World From Learning From It]] — the commons-extraction reading of closed-lab AI: training on the shared commons while restricting the commons from learning back is asymmetric reciprocity — taking from the pool without replenishing it, the digital-AI cousin of the free-rider tension this MOC maps. Represent as a contested thesis; the checkable parts are output-use asymmetry and access cutoffs. Primary home: [[Open Source Governance MOC]]. ## Synthesis additions (2026-06-30 gap-fill) From Common Room on AI GTM — the community-intelligence angle on what makes shared signal usable: - [[3. Resources/Permanent Notes/AI's Leverage Comes From the Data Foundation Not the Model]] — a community signal disconnected from the rest of a member's record "isn't a signal — it's a data point with nowhere to go"; resolving identity to real people (not company domains) before running AI is the governance discipline that makes a shared commons of community data legible and actionable. The data-foundation cousin of [[3. Resources/Permanent Notes/Public Credit Mechanisms Are the Visible Skeleton of Open Source Social Contracts]] — both are about making the community's activity legible enough to act on. Primary home: [[AI & the Future of Knowledge Work MOC]]. ## Connected Literature Notes (synthesis 2026-07-18) - [[3. Resources/Literature Notes/The Drupal Open Web Manifesto - Advancing the Principles of the Open Web]] — a foundation publicly codifying its values (ethos, collaboration, globalism, open standards, digital inclusion) as a project constitution; the commons-governance act of writing down the shared covenant. Primary home: [[3. Resources/MOCs/Open Source Governance MOC]]. ## Connected Literature Notes (synthesis 2026-07-21 — run 2) - [[3. Resources/Literature Notes/Lit · FAIR builds federated WordPress trust systems]] — FAIR treats federation, trust, and infrastructure resilience as shared-governance work rather than a single-store product - [[3. Resources/Literature Notes/Lit · FAIR integrates commercial plugins into wp-admin]] — authenticated commerce APIs test whether neutral infrastructure can support commercial participation without platform capture - [[3. Resources/Permanent Notes/Zet · FAIR scales federated WordPress distribution]] — a federated registry scales only when trust is treated as the constraint rather than a later feature - [[3. Resources/Permanent Notes/Zet · FAIR embeds commercial flows into wp-admin]] — authenticated payment and license APIs turn federation into a commercial marketplace ## Synthesis additions (2026-07-21 — run 3) - [[3. Resources/Permanent Notes/Zet · Technical excellence alone cannot overcome economic misalignment]] — shared infrastructure survives only when commercial beneficiaries fund it in proportion to their dependence - [[3. Resources/Literature Notes/Lit · Neutral infrastructure needs proportional commercial investment]] — names the missing commercial commitment behind FAIR's shutdown - [[3. Resources/Literature Notes/Lit · Open source infrastructure requires aligned economic incentives]] — generalizes the FAIR retrospective from a funding gap to an incentive-system failure ## Connected Literature Notes (synthesis 2026-07-21 — run 7) - [[3. Resources/Literature Notes/Responsibilities of a Code of Conduct Responder]] — makes response duties, boundaries, and accountability explicit for people entrusted with community harm reports ## Connected Literature Notes (synthesis 2026-07-21 — run 10) - [[3. Resources/Literature Notes/Unveiling the Impact of CHAOSS DEI Metrics in Open Source]] — uses participation, safety, recruitment, and retention measures to make inclusion outcomes accountable in shared communities ## Connected Literature Notes (synthesis 2026-07-21 — run 11) - [[3. Resources/Literature Notes/We'll Take Community Seriously When It's Embedded Into the Product Experience]] — argues that community becomes durable when participation and member progress live inside the product experience - [[3. Resources/Literature Notes/Women Rising – How to Succeed in Community Management]] — links fair pay, representation, peer support, and value-aligned boundaries to sustainable community stewardship ## Connected Literature Notes (synthesis 2026-07-21 — run 12) - [[3. Resources/Literature Notes/“Crybullyism” in Powerful Individuals]] — names feigned victimhood as a tactic powerful actors use to recast accountability demands as persecution ## Connected Permanent Notes (synthesis 2026-07-21 — run 14) - [[3. Resources/Permanent Notes/Types of Communities]] — distinguishes practice, interest, action, circumstance, place, product, and learning communities so governance and engagement match the group's actual purpose ## Connected Permanent Notes (synthesis 2026-07-21 — run 17) - [[3. Resources/Permanent Notes/How is Social Pragmatic Communication Disorder different than Autism?]] — distinguishes communication-specific and broader neurodevelopmental support needs so inclusive communities don't collapse different conditions into one category - [[3. Resources/Permanent Notes/Understanding Social Pragmatic Communication Disorder (SPCD)]] — translates SPCD's social-communication profile into concrete support practices for inclusive classrooms and peer communities ## Connected Permanent Notes (synthesis 2026-07-21 — run 22) - [[3. Resources/Permanent Notes/The Inverse Commons]] — explains how commercially funded maintenance can sustain a shared resource while preserving broad public access and downstream freedom ## Synthesis additions (2026-07-25) - [[3. Resources/Permanent Notes/An Intent-to-Use Filing Gives a Steward Silent Priority Over the Commons It Stewards]] — silent priority produces silent concessions, so the record shows no conflict at all. ## Synthesis additions (2026-07-27) **New Permanent** - [[3. Resources/Permanent Notes/Concealment Converts One Grievance Into Two]] — a governance design rule: stigmatizing a contested-but-permitted practice buys concealment, not compliance, and a later reveal replaces one disagreement with a worse betrayal. Enforcement postures that punish disclosure optimize for the appearance of compliance and against the information the community actually needs. **New arrival (Reader)** - [[3. Resources/Readwise/Articles/The AI Hypocrisy Why Secretive Use of Generative AI Is Fueling Creator Backlash]] — Penn on the AO3 incident; the disclose-and-respect paired norm is the structural fix. Origin source for the new Permanent. ## Synthesis additions (2026-07-30) - [[3. Resources/Permanent Notes/Practical Obscurity Is an Economic Property Not a Technical One]] — pseudonymous participation is a governance assumption, not a technical guarantee. Communities that promised contributors practical anonymity made that promise under a cost structure that no longer holds; public archives are the corpus the attack consumes. ## Synthesis additions (2026-07-31) - [[3. Resources/Permanent Notes/Structural Power Claims the Position of the Party Being Acted Upon]] — the reversal that lets an institution treat objection as aggression, evidenced across four unrelated domains in one week: an AI-adoption mandate, a student political organization, a contested term's defenders, and a high-demand religious movement. Generalizes the charismatic-DARVO note by dropping its allegation requirement. Relevant to community governance because the pattern determines whether a member's disagreement is heard as feedback or as disloyalty — and communities, unlike employers, lose dissenters silently. ## Synthesis additions (2026-08-01) - [[3. Resources/Permanent Notes/Portability Is Proven by a Second Implementer Not by Design Intent]] — how to test whether shared infrastructure is genuinely commons-owned rather than one project's tool with a general-sounding name. FAIR's TYPO3 v14 adoption is the worked case: the WordPress-specific behavior lived in protocol extensions, and a second CMS arriving through the same mechanism is what made that checkable rather than merely asserted. ## Synthesis additions (2026-08-01, run 5) - [[3. Resources/Permanent Notes/An Unreachable Standard Converts Devotion Into Extractable Labor]] — the voluntary counterpart to [[3. Resources/Permanent Notes/Coerced Contribution Kills the Commons]]. Extracts more precisely *because* nothing is mandated; "for the mission" plays the role "for God" plays in the source. - [[3. Resources/Permanent Notes/In High-Attrition Fields Persistence Is the Selection Mechanism]] — argues for investing in contributors who have already persisted past the attrition window rather than optimizing recruitment volume. ## Synthesis additions (2026-08-11, backlog clearance) - [[3. Resources/Readwise/Articles/Leak Exposes Members of Peter Thiel’s Secretive ‘Dialog’ Society]] — preserves a carefully bounded investigation of overlapping private-network, regulatory, and data-broker roles without treating listed membership as proof of coordinated action. - [We’re announcing the Alliance for America’s Skilled Trades.](3.%20Resources/Readwise/Articles/We’re%20announcing%20the%20Alliance%20for%20America’s%20Skilled%20Trades..md) — primary coalition announcement retained as workforce-development and cross-sector governance evidence. - [[3. Resources/Readwise/Articles/Alliance for America’s Skilled Trades Skilled trades shaped America's past. Here's how they can build America's future Fortune]] — secondary coverage of the same coalition and co-funded workforce report; linked as a twin rather than promoted separately. ## Synthesis pass — 2026-08-11 InnerSource reference - [Beyond Pull Requests: Quantifying the ROI of InnerSource](https://read.readwise.io/read/01kywpb6dzgxd8bsqhk0fghb8b) — connects contribution metrics, knowledge flow, and contributor readiness to the governance of internal commons. ## Synthesis additions (2026-08-13) - [[3. Resources/Literature Notes/Researchers Show How Meta's 'Pervert Glasses' Are Used to Harass Women - Literature Note]] — documents a hardware-affordance harm (covert wearable capture) that evades marker-based platform moderation by design; the community-events angle (WordCamp/meetup photography-consent policy) is the direct application. - [[3. Resources/Permanent Notes/Public Stigma Is Not a Governance Mechanism]] — reputational disapproval of a technology suppresses adoption by the uncommitted majority without constraining the motivated minority who cause the harm; pairs with [[3. Resources/Permanent Notes/Concealment Converts One Grievance Into Two]] as a second caution against treating informal social pressure as an enforcement mechanism. ## Synthesis additions (2026-08-16 — batch synthesis pass) **Platform ownership and lock-in** - [[3. Resources/Literature Notes/Code for the People - Official Trailer (2026)]] — trailer framing platform fragility as the reason to own your own content - [[3. Resources/Permanent Notes/Building on a Platform You Don't Control Is Renting Not Owning]] — the promoted claim from the trailer, generalized past WordPress - [[3. Resources/Literature Notes/Automattic's 'Code for the People' Documentary Is a Rallying Cry for Users to Fight for the Open Internet]] — the full documentary, distinct from the trailer note above - [[3. Resources/Permanent Notes/Advocacy Needs Disclosure When the Messenger Sells the Product]] — a commercial actor advocating for a commons owes the audience disclosure of its stake - [[3. Resources/Literature Notes/Why Google, Apple & Big Tech Keep Making Everything Worse]] — enshittification as the failure mode platform lock-in produces - [[3. Resources/Permanent Notes/Lock-In Removes the Discipline That Would Punish Decay]] — names the mechanism: exit cost, not malice, lets platforms decay **Civic history and rhetorical patterns** - [[3. Resources/Literature Notes/June 19, 2026 (Heather Cox Richardson)]] — Juneteenth piece on enforcement making declared freedom real (primary claim already homed on the existing [[3. Resources/Permanent Notes/Declared Freedom Is Real Only When the State Can Enforce Non-Discrimination]]) - [[3. Resources/Permanent Notes/Equal-Rights Backlash Reuses the Same Reverse-Discrimination Script Each Generation]] — the recurring rhetorical pattern that answers each equal-rights gain, distinct from the enforcement-mechanics claim above **Open source community operations** - [We Planned for 10 Ambassadors. We're Welcoming 138.](3.%20Resources/Literature%20Notes/We%20Planned%20for%2010%20Ambassadors.%20We're%20Welcoming%20138..md) — scaling a volunteer program past its designed capacity - [[3. Resources/Permanent Notes/A Published Quality Bar Scales Better Than a Headcount Cap]] — the fix: publish the bar instead of capping the roster - [[3. Resources/Literature Notes/The Checklist That Keeps Open Source Projects Alive]] — maintainer practices that keep a project from stalling - [[3. Resources/Permanent Notes/Ego Is the First Blocker to Opening a Project for Outside Feedback]] — the internal obstacle before the external one - [[3. Resources/Permanent Notes/Consistent Reply Timelines Build Trust More Than Fast Ones]] — predictability, not speed, earns contributor trust - [[3. Resources/Literature Notes/Episode 133 - Until Next Time (CHAOSS Cast)]] — a podcast's own sunset as a governance-succession case study - [[3. Resources/Permanent Notes/Community-Owned Programs Outlast Personality-Led Ones]] — the succession lesson the sunset episode draws out - [[3. Resources/Permanent Notes/A Challenger Can Invite The Incumbent To Connect Not Compete]] — a non-adversarial move available inside competitive commons dynamics - [[3. Resources/Literature Notes/demo.rss.chat]] — small federated chat network relying on informal trust over formal moderation - [[3. Resources/Permanent Notes/Small Trusted Networks Substitute Social Trust For Formal Moderation]] — names the substitution and its scaling limit **WordPress ecosystem governance** - [[3. Resources/Literature Notes/WP Engine Opposes WordPress Foundation's Trademark Bids in the U.S. and Canada, Alleging Fraud and Bad Faith]] — contested trademark filings as an ecosystem-capture dispute - [[3. Resources/Permanent Notes/Trademarking Generic Terms Invites Ecosystem Capture]] — the general governance risk the dispute illustrates - [[3. Resources/Literature Notes/Inside WordCamp US 2026 — Lead Organizers on Hitting Reset]] — organizers rebuilding a flagship event after a shrinking volunteer core - [[3. Resources/Permanent Notes/Widen The Funnel When Your Core Shrinks]] — the strategic response to a shrinking volunteer base - [[3. Resources/Literature Notes/WordPress Community Support Recorded a $372,000 Deficit in 2025]] — a nonprofit funding shortfall despite growing attendance - [[3. Resources/Permanent Notes/Attendance Growth Is Not Community-Funding Health]] — the metric-mismatch claim this deficit exposes - [[3. Resources/Literature Notes/Something Is Wrong With the WordPress.org Popular Themes List]] — ranking anomalies on shared infrastructure that invite scrutiny **Labor governance** - [[3. Resources/Literature Notes/We Just Formed the Largest Tech Union in America]] — a new tech-sector union as collective-voice infrastructure - [[3. Resources/Permanent Notes/Job Security Is a Precondition for Innovation Not a Constraint]] — reframes job security as an enabling condition rather than a tradeoff against it - [[3. Resources/Literature Notes/AI and the Enshittification Era (Cory Doctorow)]] — automation's effect on labor, process knowledge, and accountability - [[3. Resources/Permanent Notes/Automation Financed by Capital Paces Workers Labor Assists Them]] — who funds automation determines whether it assists or replaces workers - [[3. Resources/Permanent Notes/Replacing a Worker Destroys Process Knowledge That Rehiring Cannot Restore]] — tacit knowledge lost in workforce churn - [[3. Resources/Permanent Notes/A Single Human Supervising Automation Absorbs Liability the System Created]] — the accountability-sink pattern in human-in-the-loop automation **Institutional transparency and coercive-control dynamics** - [[3. Resources/Literature Notes/LEAKED Bethel Firing 50 People… But There's More]] — mass layoff allegations at a church organization; sourcing caution flagged in the note (anonymous insider source, unseen severance document) - [[3. Resources/Permanent Notes/Silence-for-Severance Forfeits an Organization's Transparency Claims]] — trading severance for silence undercuts an org's own transparency claims - [[3. Resources/Literature Notes/Out of Control When Churches Become Corporations Pia Hugo Podcast Episode 659]] — traces a documented lineage from the Shepherding Movement into a NAR institutional precursor - [[3. Resources/Permanent Notes/Growth Pressure Corrupts Institutions More Than Villainy Does]] — growth incentives, not bad actors, as the primary corrupting force - [[3. Resources/Literature Notes/Spiritual Grooming — How Control Hides in Faith (Episode 664)]] — survivor testimony on coercive dynamics inside a high-control group - [[3. Resources/Permanent Notes/Helping Relationships Are Classified By Direction Of Capability]] — a framework for telling genuine help from control dressed as help - [[3. Resources/Permanent Notes/Who Initiates A Disclosure Determines Who Holds Power]] — the direction of a disclosure, not its content, signals who holds power - [[3. Resources/Permanent Notes/Exit Cost Not Conviction Explains Persistence In Harmful Institutions]] — a direct empirical case for this MOC's exit-vs-voice central tension - [[3. Resources/Literature Notes/A Disagreement on Principles, Not on Skills]] — no new Permanent needed; links to the existing [[3. Resources/Permanent Notes/Structural Power Claims the Position of the Party Being Acted Upon]] and to "Loyalty Tests Recode Dissent as Betrayal," which already cite this source **Privacy and power analysis** - [[3. Resources/Literature Notes/Large-scale Online Deanonymization with LLMs]] — arXiv preprint on LLM-driven deanonymization at scale - [[3. Resources/Permanent Notes/Validation That Inspects Steps Cannot See Composition]] — a validation-blind-spot claim relevant to any commons relying on step-level review - [[3. Resources/Literature Notes/Why do Latinos work for ICE?]] — backfills the source link for an existing Permanent note on community identity vs. power analysis ## Synthesis additions (2026-08-16, backlog clearance) - [[3. Resources/Permanent Notes/Off-the-Record Convening on Personal Email Evades Public-Records Law]] — names the governance-evasion tactic behind the Thiel "Dialog" society reporting: routing coordination through personal email keeps a private network's convening outside public-records reach - [[3. Resources/Permanent Notes/Social Secrecy Discipline Does Not Predict Technical Security Discipline]] — a secretive network's discipline about who's in the room doesn't transfer to discipline about data handling; the two are separate practices this MOC's monitoring principle has to track independently **Platform ownership and lock-in (cont.)** - [[3. Resources/Literature Notes/X Open Sources Its Ranking Algorithm]] — TechCrunch on X's expanded ranking-algorithm release and shadowban-check tool - [[3. Resources/Permanent Notes/Algorithmic Transparency and Corporate Disclosure Move on Separate Axes]] — publishing the ranking code doesn't obligate the company to disclose how it's used; code-level and corporate transparency move on separate axes Skipped as near-duplicates of entries already in this MOC: "Declared Freedom Is Real Only When the State Can Enforce Non-Discrimination" (already linked above at the 2026-06-21 addition), "Practical Obscurity Is an Economic Property Not a Technical One" (already linked above at the 2026-07-30 addition), and the Literature Note "Leak Exposes Members of Peter Thiel's Secretive 'Dialog' Society" (already linked above at the 2026-08-11 backlog-clearance addition as the Readwise/Articles capture of the same title) — all are the same notes, not new ones, so no new lines were added for them. ## Synthesis additions (2026-08-17, belonging and exclusion) - [[3. Resources/Literature Notes/Can We Build an "Us" Without a "Them" With John Green]] — Nerdfighteria as a worked example of a group recognizing and correcting its own unintentional out-group. - [[3. Resources/Permanent Notes/The Yearning to Belong Produces Exclusion as a Side Effect]] — groups draw exclusion boundaries as an incidental byproduct of belonging-seeking, not because exclusion itself is gratifying. ## Synthesis additions (2026-08-18, contribution capacity and platform ownership) - [[3. Resources/Literature Notes/From Divi to FSE Moving a Small Non-Profit Aaron Jorbin]] — migrating a volunteer-run non-profit site from Divi to Full Site Editing. - [[3. Resources/Permanent Notes/Tool Familiarity Not Tool Power Determines Who Can Contribute]] — a tool's power to contributors is capped by how many people already know it, not by what the tool itself can do. - [[3. Resources/Literature Notes/How the Ankler Outgrew Substack and Built an Independent Platform on WordPress Nicola Catton]] — a media company migrating off Substack to an independently-owned WordPress platform. - [[3. Resources/Permanent Notes/Standardized Ad Inventory Is a Revenue Lever Not a Design Choice]] — standardizing ad inventory format and placement is a revenue-optimization lever, not a cosmetic design decision. - [[3. Resources/Literature Notes/Modernizing Civic Websites for Accessibility, Services, and the Open Web Manny Costa]] — modernizing government/civic websites for accessibility and open-web principles. - [[3. Resources/Permanent Notes/Keeping Regulated Data Out of the CMS Database Eases Security Review]] — routing regulated resident data around the CMS database (e.g. to a dedicated service) narrows what a security review has to certify. - [[3. Resources/Permanent Notes/A Passing Automated Accessibility Score Is a Floor Not a Verdict]] — an automated accessibility checker's passing score is a minimum floor, not proof a site clears a professional audit or avoids litigation. - [[3. Resources/Literature Notes/You Are the Source of Your Community]] — David Spinks's "founder-source" theory of community-building. - [[3. Resources/Permanent Notes/Founder-Source Theory Reframes This Vault's Concentrated-Authority Risk as a Feature]] — Source theory's claim that a community's specific character depends on one founder's undiluted vision is the same authority-concentration structure this vault's NAR/BDFL research treats as a failure risk, argued from the opposite normative direction. ## Synthesis additions (2026-08-28 — data centers, land, and who pays) From The Wired Word's August 23 lesson on data-center siting. Both notes are about a burden that is concentrated while the benefit is spread, read at two scales. - [[3. Resources/Permanent Notes/An Above-Market Offer Is Coercive When the Alternatives Are Already Gone]] — the individual scale. An 82-year-old landowner refuses and then declines to take credit for it, locating the difference between her and her neighbours in circumstance rather than character. "She didn't need the money" is the operative fact. - [[3. Resources/Permanent Notes/Support Collapses When the Benefits Are National and the Costs Are Local]] — the population scale. A third of Americans approve of data-center acceleration; 14% would welcome one locally. PJM's independent market monitor names the fix as cost allocation, not prohibition — which makes the 14% a priced objection rather than parochialism. - [[3. Resources/Permanent Notes/The Most Committed Members Absorb the Most Cost]] — why demand concentrates on the visibly willing unless a community allocates deliberately - [[3. Resources/Permanent Notes/Operational Uncertainty Falls Hardest on Those Who Must Plan Most]] — the distributional cost of schedule changes in community events ## Synthesis additions (2026-10-05 — Automattic board turnover) - [[3. Resources/Readwise/Articles/Automattic Executives Signed $8.15M Severance Deals During the 33 Hours Mullenweg Was Removed and Reinstated as CEO]] — wp-content.co (Nithin Sreeraj), relaying TechCrunch, reports that CFO Mark Davies and Chief Legal Officer Andy Missan each signed the other's severance agreement on September 10, which the article values at $8.15M; the article itself says who authorized the terms is unanswered and the figure is unverified. - [[3. Resources/Readwise/Articles/Automattic’s New Board Includes a Former Employee and Longtime Friends of CEO Matt Mullenweg]] — The Repository reports four new Automattic directors (Hugh Howey, Amy Chan, Henry Khachatryan, Krutal Desai) after the prior board's leave vote was reversed in about 33 hours; the "longtime friends" framing is the outlet's summary of separately sourced items, and an Automattic spokesperson confirmed the appointments. ## Synthesis additions (2026-10-18 — registering previously unlisted notes) ### Permanent Notes - [[3. Resources/Permanent Notes/Groups Select Among Their Authorities by What Maintains the Boundary]] — When a tradition's sources conflict, the reading that wins tends to be the one that best marks who belongs, not the one the text best supports. ### Literature Notes - [[3. Resources/Literature Notes/Leak Exposes Members of Peter Thiel's Secretive 'Dialog' Society]] — A WIRED leak shows 222 registrants of Peter Thiel's private Dialog society, including regulators beside the industries they oversee, none using government email. Closest-fit placement. - [[3. Resources/Literature Notes/What is a Virtual Power Plant (VPP)]] — A KubeCon Japan lightning talk argues Japan's grid shows distributed-systems failure traits and should be coordinated as a cloud-native system through virtual power plants. Closest-fit placement.