## Synthesis additions (2026-10-17 — sovereignty policy, and a heated thread on the WP Engine case) - [[3. Resources/Readwise/Articles/Open Source Sovereignty Gets Down to the Boring Business of Making It Work|Open source sovereignty gets down to the boring business of making it work]] — The Register (Liam Proven): European public-sector open source moving from principle to targets and measurement; links talk pages and decks, but the Cyber Resilience Act's December 2027 date and several comparisons carry no link, and quoted sources include vendors with a stake (SUSE, PwC, Dell, Microsoft). - [They’re Trying to Destroy the Foundation, All of .Org, Demanding...](3.%20Resources/Readwise/Tweets/They’re%20Trying%20to%20Destroy%20the%20Foundation,%20All%20of%20.Org,%20Demanding....md) — thread: Mullenweg's post, a quote post and a long reply, all about the WP Engine case. No filing is cited, and the "billions" figure conflicts with the "hundreds of millions of dollars" The Repository quotes from Automattic's motion. Two other captures of the same thread are logged, not analyzed. - [[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. - [[3. Resources/Permanent Notes/An Open Source Adoption Claim Without a Dated Target and a Measurement Is Talk]] — Berlin's dated 70% by 2032 target counts as a plan and not a result, and a Japan study found few organizations doing what many say. ## Synthesis additions (2026-10-17 — a venture-backed runtime's founder moves to an open-source one) - [[3. Resources/Readwise/Articles/Node.js Creator Ditches Deno to Work on Open Source Cloudflare Workers]] — The Register (Joab Jackson): Ryan Dahl leaves Deno to work on Cloudflare's open-source workerd; the article reports Dahl's account and adds its own inference that independent runtimes will be squeezed after Anthropic's Bun acquisition. The Bun acquisition and the funding and download figures are unlinked in the article. ## 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-15 — a Trac revert and the reason it states) - [[3. Resources/Permanent Notes/A Revert by Authority Needs a Stated Technical Reason Before It Reads as Technical]] — treat a revert as technical only if the person with authority states a technical reason on the record (The Repository, Rae Morey) - [[3. Resources/Readwise/Articles/Matt Mullenweg Orders Accessibility Revert, Tells Core Committer to “Contribute Your Talents to Another Project”]] — The Repository (Rae Morey): Mullenweg orders an accessibility revert and tells a core committer to contribute elsewhere; the stated technical reason is thin. ## Synthesis additions (2026-09-10 — where governance leverage actually sits) - [[3. Resources/Permanent Notes/Trademarks Are the Only Asset a Fork Cannot Route Around]] — locates the one asset a community cannot copy its way past, which is why license openness does not by itself distribute power. - [[3. Resources/Permanent Notes/Trust Granted at Admission Must Be Re-Verified at Every Update]] — the distribution channel as a governance surface: who reviews what, and when, decides what reaches users. # Open Source Governance MOC ## Synthesis additions (2026-10-01 — WP Engine v. Automattic docket: rulings, sanctions hearing, sealing) - [[3. Resources/Readwise/Articles/Automattic’s New Lawyers Lose Bid for More Time in Legal Fight With WP Engine]] — The Repository (2026-10-16): the judge stamps Automattic's third extension request DENIED without reasons, so expert depositions end November 17 and the jury trial stays set for October 19, 2027; the reason Gibson Dunn left (a "conflict of interest") is not in the filings; the outlet discloses sponsorship from both WP Engine and Pressable. - [[3. Resources/Readwise/Articles/Order Re Motions to Dismiss]] — Dkt. 410 (2026-09-24), Judge Martínez-Olguín: WP Engine's four antitrust counts survive; its CFAA extortion count is dismissed without leave to amend. Pleading-stage rulings that take the complaint as true, not merits findings. - [[3. Resources/Readwise/Articles/Automattic & Matt Mullenweg Fail to Dismiss WP Engine Antitrust Claims]] — Search Engine Journal's report of the same ruling: WP Engine's four antitrust claims and its three claims against WooCommerce survive; the note flags that surviving dismissal is not a merits ruling. - [[3. Resources/Readwise/Articles/Order Granting Plaintiff WPEngine, Inc.’s Administrative Motion to Consider Whether Another Party’s Material Should Be Sealed Regarding Third Amended Complaint]] — Order (2026-09-24) granting WP Engine's motion (Dkt. 234) to keep portions of its Third Amended Complaint sealed; it publishes reasons per row, not the sealed text, and decides secrecy only. - [[3. Resources/Readwise/Articles/Joint Stipulation to Continue Hearing on Plaintiff’s Motion for Sanctions]] — Dkt. 411 (2026-09-24): all parties stipulate to move the hearing on WP Engine's spoliation sanctions motion (Dkt. 357) from September 30 to October 7, 2026. - [[3. Resources/Readwise/Articles/Joint Stipulation to Continue Hearing on Plaintiff’s Motion for Sanctions — WPEngine, Inc. V. Automattic Inc., No. 424-Cv-06917-Amo-Ask]] — Dkt. 412 (2026-09-28): Susman Godfrey letter, for Automattic, WooCommerce and the WordPress Foundation, asks the court to so-order the stipulation moving the sanctions hearing to October 7. - [[3. Resources/Readwise/Articles/Order (As Modified) Continuing Hearing on Plaintiff’s Motion for Sanctions]] — Dkt. 413 (2026-09-28): the court sets the sanctions hearing for October 7, 2026 at 11:00 a.m. in Oakland, courtroom to be determined. - Procedural filings in WPE v. Automattic (pro hac vice applications under Civil Local Rule 11-3, low analytic value): Eudokia Spanos, [[3. Resources/Readwise/Articles/Application for Admission of Attorney Pro Hac Vice-2]] (Dkt. 407, signed 9/23/2026) with [[3. Resources/Readwise/Articles/Certificate of Good Standing]] (Dkt. 407-1, New York good-standing certificate) and a second application [[3. Resources/Readwise/Articles/Application for Admission of Attorney Pro Hac Vice]] (Dkt. 408; the source flags a scrambled client list); Jillian S. Hewitt, [[3. Resources/Readwise/Articles/Application for Admission of Attorney Pro Hac Vice-3]] (Dkt. 406). ## Synthesis additions (2026-10-01 — WordPress.org update-API data collection: investigation, testimony, commentary) - [[3. Resources/Readwise/Articles/Exhibit Two to the Declaration of Kaitlin Keohane Filed at Dkt. No. 303-4, Refiled Pursuant to Court Order at Dkt. No. 381]] — Dkt. 419: eight pages of Barry Abrahamson's 2025-12-19 Rule 30(b)(6) deposition for Automattic, refiled under court order; one witness's testimony on a crawler site, update checks and the MC.WordPress.org dashboard, with some questions unanswered. - [So Barry Abrahamson's Previously Sealed Testimony in the Automattic Trial...](3.%20Resources/Readwise/Tweets/So%20Barry%20Abrahamson's%20Previously%20Sealed%20Testimony%20in%20the%20Automattic%20Trial....md) — Duane Storey's one-sided X thread (2026-10-01) claims Abrahamson's testimony shows Automattic tracking WordPress.org update-API data; the note separates the thread's claims from what the five-page Dkt. 419 excerpt shows. - [[3. Resources/Readwise/Articles/Down the Rabbit Hole - A Look at the WordPress Update API]] — Duane Storey's 2024-11-08 blog investigation claims three api.wordpress.org update endpoints receive installed plugin and theme headers plus site details; the observations are checkable, his privacy and data-use inferences are opinion. ## Synthesis additions (2026-10-01 — Automattic board turnover and WordPress community reporting) - [[3. Resources/Readwise/Articles/WordPress Owner Automattic’s Board Reportedly Purged After Failed ‘Coup’ Against CEO]] — Gizmodo (Tom McKay), rewriting TechCrunch's reporting: Automattic's board voted 2026-09-09 to put Matt Mullenweg on leave; the leave ended about 33 hours later, followed by removed or resigning board members and executives. - [[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 Automattic's board about 33 hours after it voted him onto paid leave, relying on TechCrunch and The Information; Mullenweg's "coup" framing is his own. - [[3. Resources/Readwise/Articles/Goodbye WordPress]] — Nolan Lawson's personal blog post moves the blog from WordPress.com to self-hosting, citing recent drama, the editor drifting from Markdown toward Gutenberg, and a $110 annual charge; one exit account, not research. - [[3. Resources/Readwise/Articles/Update on the WordPress Community Groups on events.wordpress.org]] — Karen Alma Arnold's Make Community post (2026-09-26) reports the move of about 700 WordPress meetup groups from Meetup.com to events.wordpress.org, with test feedback and the state of talks with Meetup.com. - [[3. Resources/Readwise/Articles/WordPress Contributor Toolkit 1.2 One App for Your First Core or Gutenberg Contribution]] — JuanMa Garrido's Make WordPress Core post announces Contributor Toolkit 1.2.0, a desktop app that now covers Gutenberg GitHub contributions as well as Core Trac tickets; first-party project documentation. - [[3. Resources/Readwise/Articles/A Note on Figma Access]] — Joen Asmussen's Make Design notice (2026-09-18) explains who gets Figma edit access for WordPress mockups, why paid seats are scarce (Automattic pays), and to downgrade approved access after a month. ## Synthesis additions (2026-10-01 — contributor labor, maintainer power, and platform accountability) - [[3. Resources/Permanent Notes/Who Directs the Work and Who Benefits Decides Contributor Status Not the Word Volunteer]] — Permanent note: who sets the roadmap, controls access and profits decides how contributor work is treated, not whether a program calls contributors volunteers; a sustainability screen, not a legal conclusion. - [[3. Resources/Readwise/Articles/For Love or Money Open Source’s Labor Law Problem]] — Sé Reed's opinion essay (not legal advice) argues FLSA turns on the reality of the working relationship and proposes eight control-and-benefit questions for when contributors are no longer "just volunteers." - [[3. Resources/Readwise/Articles/The DHH Problem]] — davidcel.is opinion essay (2025-09-19) argues David Heinemeier Hansson's views harm the Ruby and Rails communities and that Rails and RubyGems governance needs to change; the characterizations are the author's. - [[3. Resources/Readwise/Articles/Are We in Drupal's Renaissance]] — Headless video essay (auto-captioned; vendor-sourced history): Acquia's September 2026 rebrand puts Drupal back under the company logo, catching the brand up to shipped work such as Drupal CMS 1.0 and Drupal Canvas 1.0. - [[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 results from unenforced antitrust law, anti-circumvention law such as DMCA 1201, and regulatory capture (auto-captioned; verify names). - [[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. - [[3. Resources/Readwise/Articles/Open Source Datacenters and Open Source Thinking Will Undo Self-Inflicted DC Damage]] — Rupert Goodwins argues in The Register (opinion column) that datacenter secrecy about energy and siting fuels public opposition and that the industry should adopt open source's habit of radical openness. ## Synthesis additions (2026-09-26 — the CRA's paid-tier exemption line; WordPress security as a community conversation) - [[3. Resources/Readwise/Articles/The Shape of Things to Come Cyber Resilience Act and Open Source Development]] — Simon Kraft, Patchstack, WordCamp Serbia deck (2026-09): open source is exempt from the Cyber Resilience Act only until commercial activity or paid support; Annex I duties quoted (SBOM to top-level dependencies, coordinated disclosure policy with a contact address, no known exploitable vulnerabilities); reporting duties live since 2026-09-11, full application 2027-12-11; the mVDP pitch is the speaker's employer's product - [[3. Resources/Readwise/Articles/Community + Code Episode 34 - Maciek Palmoski]] — Chris Reynolds with Maciek Palmowski (2026-09-25, 60 min): the disclosure-to-exploit window is about five hours and shrinking, so "keep it updated" is no longer a control; most repository plugins sit below 1,000 installs; AI-generated bug-bounty slop floods intake; vibe coding gets a sequel called vibe maintenance; CMS communities repeat each other's mistakes in silos - [[3. Resources/Permanent Notes/The CRA Open Source Exemption Ends at the First Paid Tier]] — Permanent from the Kraft CRA deck: the commercial-activity test and the steward role, with the 2026-09-11 and 2027-12-11 dates - [[3. Resources/Literature Notes/Free Rider Problem in Open Source]] — Woods and Guliani, *Open Source for the Enterprise* (Kindle loc. 297): the enterprise free-rider framing; connects to the give-back Permanent ## Synthesis additions (2026-09-05 — venue participation vs. exclusion) - [[3. Resources/Permanent Notes/Absence From an Open Venue Is a Choice Not an Exclusion]] — Names the honest diagnosis when a group is missing from an open venue it could have joined: prioritization, not exclusion — drawn from the WordCamp US 2026 PHP conversation notes. ## Synthesis additions (2026-09-05 — testing openness claims) - [[3. Resources/Permanent Notes/A Format No One Can Fully Implement in Bounded Time Is Closed Regardless of License]] — A checkable review criterion for any format or ability schema claiming openness: can a competent developer fully implement it in bounded time? ## Synthesis additions (2026-09-05 — testing methodology gaps in upgrade-path defects) - [[3. Resources/Permanent Notes/A Test Environment That Is Always New Cannot Find Defects That Require Age]] — Zarf maintainer's account of an RBAC bug invisible to fresh-install CI, only reachable via accumulated upgrade history. ## Synthesis additions (2026-09-05 — what makes a format's conformance checkable) - [[3. Resources/Permanent Notes/A Validator Removes the Spec Author From the Conformance Loop]] — a governance-relevant acceptance bar for any project defining a format for independent implementation: examples and docs teach it, only a validator makes conformance checkable without the author. ## Synthesis additions (2026-09-05 — governance control design) - [[3. Resources/Permanent Notes/A Control That Does Not Match the Failure Mode Buys Compliance Not Safety]] — mandating an infrastructure audit after a credential over-scoping incident checks the wrong layer and can't prevent a recurrence ## Synthesis additions (2026-09-05 — reading a changelog's composition as a maturity signal) - [[3. Resources/Permanent Notes/A Changelog's Composition Reports Project Maturity Better Than Its Volume]] — Proton's shift to per-game fixes over platform changes is the same maturity signal as reading an issue queue's composition instead of its length ## Synthesis additions (2026-09-05 — distribution-channel control as a governance surface distinct from licensing) - [[3. Resources/Permanent Notes/Distribution Channel Control Is a Governance Surface Separate From the License]] — WordPress's 2024 conflict never touched the GPL license — the trigger was channel access being revoked for one host, a governance surface license and trademark review both miss. ## Synthesis additions (2026-09-05 — unobservable values and who adjudicates them) - [[3. Resources/Permanent Notes/When a Communitys Valued Trait Is Unobservable Adjudication Moves to Authority]] — Woodley's orthodoxy-vs-orthopraxy argument generalizes: when what a group values can't be seen in practice, someone is handed the power to judge who qualifies, and that authority is never explicitly voted on. ## Synthesis additions (2026-09-05 — volunteer capacity as the real security limit) - [[3. Resources/Permanent Notes/Volunteer Capacity Is the Real Security Boundary of an Open Ecosystem]] — 8-10 active volunteers review roughly 800 wp.org plugin submissions a week against a directory that grew from 60k to 70k+ plugins in 18 months — the capacity number behind any plugin-review policy debate. ## Synthesis additions (2026-09-05 — litigation scheduling and sequencing) - [[3. Resources/Permanent Notes/A Process Scheduled Before Its Inputs Are Fixed Will Be Run Twice]] — a scheduling-motion instance of a general sequencing-failure test, drawn from WPEngine v. Automattic Dkt. 371 ## Synthesis additions (2026-09-05 — the WordPress Foundation as counterclaimant) - [[3. Resources/Permanent Notes/Procedural Records Disclose What Substantive Coverage Omits]] — why a routine scheduling motion (Dkt. 371) disclosed the case's real scale and the Foundation's litigation posture when no trade coverage had ## Synthesis additions (2026-09-05 — code-of-conduct due diligence) - [[3. Resources/Permanent Notes/A Missing or Placeholder Code of Conduct Is a Checkable Governance Failure]] — a concrete, behavior-neutral due-diligence check drawn from the Weird Little Guys of FOSS list's Xlibre entry ## Synthesis additions (2026-09-04 — the gate and its operator) - [[3. Resources/Permanent Notes/An Exemption Granted by Confidence Rather Than Audit Voids the Regime Around It]] — WordPress.org would enforce plugin security audits while Automattic's persistent admin connections are exempted by assertion; the governance question is not whether the rule is right but whether its exemptions produce the same artifact. ## Synthesis additions (2026-08-24 — backlog gap-fill (second pass)) - [[3. Resources/Permanent Notes/A Disclaimed Comparison Is Still a Comparison]] — a disclaimer does no work when the structure of the piece already made the comparison for the reader. - [[3. Resources/Permanent Notes/API-Layer Delivery Precedes Interface Delivery in Layered Systems]] — the theme.json-first cadence, and why the two-tier experience it creates has to be managed rather than denied. - [[3. Resources/Permanent Notes/Declarative Configuration Lets a Platform Absorb Its Ecosystem's Migration Cost]] — because Woo extensions declare settings rather than render them, the platform can swap renderers and thousands of authors migrate by doing nothing. ## Synthesis additions (2026-08-24 — project voice vs commercial voice) - [[3. Resources/Permanent Notes/One Channel Cannot Carry Both Project Voice and Commercial Interest]] — when the official identity is operated by a party with a competing product, readers cannot tell which role is speaking, and begin discounting every statement. - [[3. Resources/Readwise/Articles/WordPress X Account Draws Backlash After Calling Out WP Rocket Over 7.1 Fatal Errors|WordPress X Account Draws Backlash Over WP Rocket]] — the case, including the tell: practitioners who agreed WP Rocket had erred objected anyway. - [[3. Resources/Readwise/Articles/New Accessibility Lab Plugin Prototype Lays Groundwork for Accessibility Team’s First Canonical Plugin|Accessibility Lab plugin prototype]] — the counter-case from the same publisher and week: a rejected proposal revived by conceding the critics' premise and negotiating scope with them first. - [[3. Resources/Permanent Notes/Funding Authority and Design Authority Should Never Be the Same Body]] — the structural anti-capture rule: commercial money can fund infrastructure without buying direction, but only if the separation is written down. - [[3. Resources/Permanent Notes/Corporate Contribution Fails on Legibility Not Goodwill]] — inverts the usual extraction complaint: willing companies are blocked by having no role, report, or return story to fit a contributor into. - [[3. Resources/Permanent Notes/Recruiting Someone Into a System Obliges You to Disclose Who Owns It]] — an official onboarding funnel creates a duty of disclosure the casual "PRs welcome" case does not. ## Synthesis additions (2026-08-12 — event compatibility) - [[3. Resources/Permanent Notes/Public Event Names Outlive Their Implementation Structure]] — treats event identifiers as durable extension contracts rather than reflections of current class structure. ## Synthesis additions (2026-08-11 — consistent runtime migration) - [[3. Resources/Permanent Notes/Predictable Breakage Is Easier to Fix Than Conditional Success]] — treats a uniform editor runtime as a reproducibility decision rather than proof that migration costs disappeared. ## Synthesis additions (2026-08-11 — shared extension registries) - [[3. Resources/Permanent Notes/Namespaced Registries Let Extensions Share Assets Without Sharing Ownership]] — shows how a common interface can support independent providers without identifier collision. ## Synthesis additions (2026-08-11 — implicit platform classification) - [[3. Resources/Permanent Notes/Implicit File Heuristics Turn Small Theme Changes Into Mode Switches]] — shows how an undocumented file-presence rule can move a theme across a platform-wide behavior boundary. A map connecting ideas about how open source projects and foundations are governed, structured, and sustained. ## Core Question What governance structures and practices enable open source projects to thrive while balancing contributor autonomy, corporate interests, and community health? --- ## Key Sources ### Books - [[4. Archives/Book reviews/Free and Open Source Software - Policy, Law, and Practice]] - [[4. Archives/Book reviews/The Logic of Collective Action]] - [[4. Archives/Book reviews/Life is a Startup]] — Governance parallels for nonprofits/boards - [[3. Resources/Readwise/Books/Open Sources|Open Sources]] — Foundational essays from open source pioneers - [[3. Resources/Readwise/Books/Open Source for the Enterprise|Open Source for the Enterprise]] — Enterprise adoption patterns and governance implications - [[3. Resources/Readwise/Books/The Cathedral & the Bazaar|The Cathedral & the Bazaar]] — Eric Raymond on open vs. closed development models - [[3. Resources/Readwise/Books/Drive by Daniel H. Pink|Drive by Daniel H. Pink]] — Autonomy, mastery, purpose as intrinsic motivators for contributors - [[3. Resources/Readwise/Books/The Art of Community|The Art of Community]] — Jono Bacon on building and sustaining participatory communities ### GoDaddy OSPM (Active Work) - [[3. Resources/Readwise/Full Document Contents/Articles/Open Source Program Manager]] — GoDaddy's WordPress.org liaison, FAIR, Five for the Future, release readiness - [[DevRel Product Intelligence — Map of Content]] — How OSPM connects to DevRel and AGI product lines ### Governance Analysis Project - [[1. Projects/Open Source Foundations/OSS Governance Analysis/Comparative Governance Analysis of Open Source Projects]] - [[1. Projects/Open Source Foundations/OSS Governance Analysis/Open Source Governance Models and Evaluation Criteria]] - [[1. Projects/Open Source Foundations/OSS Governance Analysis/OSS Governance Final Recommendations & Insights]] ### Foundation-Level Analysis - [[1. Projects/Open Source Foundations/OSS Governance Analysis/Linux Foundation Governance Analysis]] - [[1. Projects/Open Source Foundations/OSS Governance Analysis/Apache Software Foundation Governance Analysis]] - [[1. Projects/Open Source Foundations/OSS Governance Analysis/Eclipse Foundation Governance Analysis]] - [[1. Projects/Open Source Foundations/OSS Governance Analysis/Mozilla Foundation Governance Analysis]] - [[1. Projects/Open Source Foundations/OSS Governance Analysis/PHP Foundation Governance Analysis]] - [[1. Projects/Open Source Foundations/OSS Governance Analysis/OpenInfra Foundation Governance Analysis]] ### Project-Level Analysis - [[1. Projects/Open Source Foundations/OSS Governance Analysis/WordPress Governance Analysis]] - [[1. Projects/Open Source Foundations/OSS Governance Analysis/Drupal Governance Analysis]] - [[1. Projects/Open Source Foundations/OSS Governance Analysis/Kubernetes Governance Analysis]] - [[1. Projects/Open Source Foundations/OSS Governance Analysis/Node.js Governance Analysis]] - [[1. Projects/Open Source Foundations/OSS Governance Analysis/Blender Governance Analysis]] - [[1. Projects/Open Source Foundations/OSS Governance Analysis/Joomla Governance Analysis]] - [[1. Projects/Open Source Foundations/OSS Governance Analysis/MariaDB Governance Analysis]] - [[1. Projects/Open Source Foundations/OSS Governance Analysis/Moodle Governance Analysis]] - [[1. Projects/Open Source Foundations/OSS Governance Analysis/TYPO3 Governance Analysis]] --- ## Core Concepts (to extract as permanent notes) ### Governance Models - **BDFL (Benevolent Dictator for Life)**: Single leader makes final decisions (Python, Linux kernel) - **Meritocracy**: Influence earned through contribution (Apache) - **Foundation model**: Nonprofit umbrella with board oversight - **Corporate-backed open source**: Company controls roadmap while accepting contributions - **Community-elected governance**: Democratic structures (Debian, Drupal) ### Key Tensions - **Corporate vs. community interests**: Who sets the roadmap? - **Contributor autonomy vs. project coherence**: How much freedom? - **Sustainability vs. purity**: When does money compromise values? - **Formalization vs. agility**: When does structure become bureaucracy? - **Rich vs. King dilemma**: Growth may require ceding control - **Individual autonomy vs. collective good**: See [[3. Resources/Literature Notes/Individual Autonomy vs Collective Good - Literature Review]] ### Commons Governance (Ostrom) - **Polycentric governance**: Multiple centers of decision-making, each with autonomy — no single authority defines the common good - **Subsidiarity principle**: Presume local authority; higher levels assist rather than replace - **Right to fork as escape valve**: "Fear of forks breeds politics and governance bloat" — healthy exit options _reduce_ bureaucratic overreach - **Graduated sanctions**: Warnings before expulsion; correction aims at restoration - **Clear boundaries enable freedom**: Well-defined membership increases autonomy because expectations are explicit - See [[3. Resources/Permanent Notes/Ostrom-Theology Crossover - Commons Governance in Faith and Code]] for theological parallels ## Synthesis additions (2026-07-05) From synthesis-pass 2026-07-05 (batch 3–resonance-filtered Permanents): - [[3. Resources/Permanent Notes/Perm · Open source sustainability fails when emotional labor is expected for free]] — projects burn on community management not code; emotional labor must be paid or boundaries set; sustainability requires this recognition - [[3. Resources/Permanent Notes/Perm · WordCamp organizers should be paid, not voluntold]] — unpaid volunteers are unsustainable + exclusionary; paying organizers ($3-5k) and speakers (honorariums) improves both fairness and inclusion - [[3. Resources/Permanent Notes/Perm · Markdown won because it solved the format lock-in problem, not for syntax]] — portability as win condition; format dominance = solves the format-trap, not syntax elegance - [[3. Resources/Permanent Notes/Perm · Decoupling from the web means moving content to closed platforms, not achieving independence]] — "decoupled" = lock-in to closed platform; true independence lives on open web where standards enable portability ### From _Life is a Startup_ - Early formalization risk — structure too early kills agility - Founder's dilemma as Board's dilemma - Equity splits = voting power = future conflict --- ## Governance Patterns | Pattern | Examples | Tradeoffs | | --------------------------- | ---------------------------------------- | --------------------------------------------- | | Foundation + Projects | Apache, Linux Foundation | Legal protection, sustainability vs. overhead | | Core Team + Contributors | React, Vue | Clear authority vs. contributor frustration | | Elected Committees | Debian, WordPress | Democratic legitimacy vs. decision speed | | Company-sponsored | Kubernetes (Google), VS Code (Microsoft) | Resources vs. trust concerns | | Hybrid nonprofit/commercial | Mozilla, MariaDB | Revenue vs. mission alignment | --- - [[3. Resources/Permanent Notes/Founder Concentration Flips From Asset to Liability at Scale]] — the lifecycle: the same undivided authority that made the project fast becomes the thing constraining it once there are three constituencies. - [[3. Resources/Permanent Notes/Concentration Risk Is a Property of the Structure Not the Officeholder]] — why succession is not mitigation — list the decisions with exactly one possible decider. - [[3. Resources/Permanent Notes/An Accountability Mechanism Reaches Its Role and No Further]] — a board restraining a CEO measures the gap everywhere the same person holds authority no board reaches. - [[3. Resources/Permanent Notes/A Crisis Exposes a Governance Gap Rather Than Creating One]] — the useful post-crisis response is documenting who decides, because the rules were never the missing part. - [[3. Resources/Permanent Notes/Verify Who Owns the Infrastructure Before Believing an Independence Claim]] — registration records over statements of intent; undisclosed personal ownership stays invisible until a crisis forces it out. - [[3. Resources/Permanent Notes/Bootstrap-Then-Divest Is Only Credible With a Named Recipient]] — a legitimate pattern that becomes checkable only when the specific asset and the specific recipient are named. - [[3. Resources/Permanent Notes/Composable Labeling Trades One Standard for Parallel Capacity]] — moderation capacity that scales with community count instead of operator headcount, at the cost of one answerable party. - [[3. Resources/Permanent Notes/A Cited Governance Precedent Needs the Dispute Checked]] — self-cited precedent is the weakest kind — the citing party chose both the case and the success criteria. ## Connections to Other Domains ### DevRel & Community - [[1. Definition of developer relations and its role in open source]] - [[2. Importance of developer relations for both open source projects and companies]] - Community health metrics - Contributor experience and onboarding ### WordPress Specifically - [[1. Projects/Open Source Foundations/OSS Governance Analysis/WordPress Governance Analysis]] - Unique BDFL model with Matt Mullenweg - Automattic's influence on the ecosystem - [[3. Resources/Literature Notes/Media Library - Command Center and Media Tools]] — Make WordPress Core Phase 3 feature-development process (added synthesis sweep 2026-07-14; no dedicated WP-core-features MOC exists yet, filed here as the closest ecosystem-development home) - [[3. Resources/Literature Notes/Media Library - Image Editing Interface]] — companion Phase 3 note, same source article (added synthesis sweep 2026-07-14) ### Faith & Community - Parallels between church governance and OSS governance - Volunteer coordination patterns - Mission-driven organizations - [[3. Resources/MOCs/Commons & Community Governance MOC]] — Cross-domain bridge - [[3. Resources/Permanent Notes/Ostrom-Theology Crossover - Commons Governance in Faith and Code]] — Benedictine monasteries as 1,500-year commons success stories --- ## Idea Compass **Parents (broader concepts)** - Organizational theory - Collective action problems - Public goods economics **Children (specific applications)** - WordPress governance reform proposals - GoDaddy OSS strategy - Foundation membership decisions **Friends (adjacent ideas)** - [[3. Resources/MOCs/Visual Thinking MOC]] — Documenting governance visually - Community management practices - Nonprofit board dynamics **Competitors (tensions/alternatives)** - Proprietary software development models - Top-down corporate governance - Anarchic/unstructured collaboration --- ## Permanent Notes ### Created - [[3. Resources/Permanent Notes/The Merit Trap - Self-Worth in Systems of Singular Authority]] — How BDFL meritocracy creates circular validation and contributor trauma - [[3. Resources/Permanent Notes/The Stadium Is the Dominant Open Source Pattern]] — 85%+ of projects are one maintainer and a crowd, not a collaborative bazaar - [[3. Resources/Permanent Notes/Maintainer Attention Is the Scarce Resource in Open Source]] — Code is overproduced; the bottleneck is human capacity to review, triage, and support - [[3. Resources/Permanent Notes/Casual Contributors Are Users Not Community Members]] — Drive-by PRs don't convert to regular contributors; treat them as bug reports - [[3. Resources/Permanent Notes/Maintenance Is Most of the Work but Gets No Prestige]] — 50-70% of dev expenditure goes to maintenance, but culture romanticizes creation - [[3. Resources/Permanent Notes/The Inverse Commons]] — Code gains value through use, but maintainer capacity depletes like a traditional commons - [[3. Resources/Permanent Notes/Stewardship Invests in Contributor Capacity Not Just Cash]] — (added 2026-06-05) the intervention targeting the maintainer-attention scarcity is capacity-building, not funding; Bloomberg/NVIDIA stewardship cohorts vs. FOSS funds; invest in *healthy* projects (prevention, not rescue) - [[3. Resources/Permanent Notes/Supply-Chain Defense Tracks Bad Actors Not Bad Code]] — (added 2026-06-05) openness makes actor-identity the attack surface; vulnerability databases find bad code, not bad actors; provenance/ownership-transfer transparency as governance primitives (Ginder/WP Beacon, "Protect The Shire" cooldown) - [[3. Resources/Permanent Notes/DevRel Burnout Is Structural Not Personal]] — Invisible infrastructure work burns people out when the organization can't see the value - [[3. Resources/Permanent Notes/DevRel as Railroad Infrastructure]] — DevRel is the connective layer between all departments and the developer community - [[3. Resources/Permanent Notes/AI Compresses the Knowledge-Worker Pipeline From Both Ends]] — Per-worker AI spend rises ($200+/user/mo) while entry-tier headcount declines (-13% for ages 22-25 in AI-exposed roles); Drucker's Taylor move applied to knowledge work eliminates the apprenticeship layer that produced senior judgment - [[3. Resources/Permanent Notes/WordPress Stores AI API Keys in a Layer Its Own Security Team Says It Cannot Encrypt]] — WP 7.0 ships AI Connector + hosts default-on activate it; WP Security Team's Blackbourn admits no two-way encryption survives key rotation or migration; Patchstack data quantifies the threat surface; SHA cohort offers third-party attestation as the response - [[3. Resources/Permanent Notes/Open Source Project Market Share Tracks Founder Trust]] — added 2026-05-28; recommendation-layer trust erosion precedes and predicts market-share decline in founder-concentrated OSS projects (WP saga as case study; Drupal/Buytaert as contrast) - [[3. Resources/Permanent Notes/Permissive Licenses Define a Floor But Don't Constitute a Community]] — added 2026-05-28; Buytaert vs Duerrenberger on the social-contract-above-the-license; both correct within their own framing; the relicensing wave (Elastic/HashiCorp/Mongo/Redis) as the failure mode the tension produces - [[3. Resources/Permanent Notes/Default-On AI Activation Inflates Adoption Metrics at the Cost of Consent]] — added 2026-05-28; activation ≠ adoption; the SiteGround AI Studio case; the SHA opt-in contrast posture - [[3. Resources/Permanent Notes/Concentrated Authority Without Accountability Produces the Same Failure Patterns Across Religious and Software Ecosystems]] — added 2026-05-28; cross-domain claim — NAR governance failures and OSS BDFL failures are structurally identical; five recurring failure patterns - [[3. Resources/Permanent Notes/Stability Is the Precondition for Formation Across Domains]] — added 2026-05-28; cross-domain claim — DevRel timeline mismatch, OSS maintainer pipeline, spiritual formation, deep-work mastery all express the same structural feature - [[3. Resources/Permanent Notes/Public Credit Mechanisms Are the Visible Skeleton of Open Source Social Contracts]] — added 2026-05-28; Drupal credits + WP Five for the Future + the relicensing-wave counter-example; credit infrastructure as what makes the social-contract layer legible enough to operate informally - [[3. Resources/Permanent Notes/AI Tools Don't Eliminate the Apprenticeship Layer They Relocate Its Cost]] — added 2026-05-28; AI eliminates entry-tier tasks but not the cognitive/relational formation work the tasks were the occasion for; the funding model for senior-judgment production breaks - [[3. Resources/Permanent Notes/Trust Erosion in Concentrated Systems Is Slow to Build and Fast to Manifest]] — added 2026-05-28; the lag dynamics behind market-share decline in concentrated-authority systems (months-to-years of accumulation, then cascading manifestation); WP saga as case study - [[3. Resources/Permanent Notes/The Recommend Layer Is Where Vendor Markets Make Their Real Decisions]] — added 2026-05-28; vendor markets are made by trusted intermediaries, not direct buyers; the recommend-layer trust is what DevRel and certification programs actually build - [[3. Resources/Permanent Notes/Distraction and Doctrinal Drift Share a Root Cause]] — added 2026-05-28; cross-domain claim — individual attention failure + communal doctrinal drift are the same externalization pattern at different units of analysis - [[3. Resources/Permanent Notes/BDFL Litigation Necessarily Implicates Personal Corporate and Foundation Roles Because the BDFL Has Concentrated Them]] — added 2026-05-29; the WP Engine v. Automattic discovery-disputes phase as operational test of concentrated-authority governance; wide discovery footprint as deferred cost of original BDFL design - [[3. Resources/Permanent Notes/Platform-Level Defaults Beat Site-Level Optimization for the Same Audiences]] — added 2026-05-29; cross-domain convergence (Joost de Valk web standards / Bovelett accessibility / SEJ Core Web Vitals) on the structural claim that platform defaults dominate site-level optimization for audience-serving outcomes; Yoast 2010 sitemap precedent; WordPress 49% good CWV as platform-architecture-effect - [[3. Resources/Permanent Notes/Target Audience Determines Translation Methodology More Than Equivalence Theory Does]] — added 2026-05-29; Perriman's TPT-critique reframing applied across domains; web rendering (Joost/Bovelett) and scripture translation share the audience-determination structure; methodology follows audience-selection in both - [[3. Resources/Permanent Notes/Trademarking a Commons's Descriptive Terms Converts a Steward Into a Gatekeeper]] — added 2026-07-09; the WP Engine v. Foundation trademark-opposition read: registering the commons's own descriptive vocabulary ("Managed/Hosted WordPress") and licensing it for fees turns steward into rent-collector. Sharpens [[3. Resources/Permanent Notes/Open Source Project Market Share Tracks Founder Trust]] (this is trust being *spent*) and continues [[3. Resources/Permanent Notes/BDFL Litigation Necessarily Implicates Personal Corporate and Foundation Roles Because the BDFL Has Concentrated Them]]. - [[3. Resources/Permanent Notes/Core Abilities Must Be Consumer-Neutral Primitives Not One Interface's Mirror]] — added 2026-07-09; the WP 7.1 Abilities-API pushback generalized to a core-design principle: a capability promoted into shared core must serve the common denominator of all callers (REST/CLI/palette/agent), not mirror the one that asked. The governance-of-core-surface companion to the agent-safety notes. - [[3. Resources/Permanent Notes/In-Kind Labor Hides How Dependent a Commons Is on a Single Backer]] — added 2026-07-10; WordPress Community Support's 2025 books show 38% of GAAP revenue as Automattic-employee contributed labor — a nonprofit that looks multi-source is one employer-policy-change away from losing over a third of its real budget. The accounting-layer instance of the single-vendor concentration risk this MOC already tracks at the market-share and trademark layers. ### Connected Literature Notes (synthesis 2026-07-10) - [[3. Resources/Literature Notes/Lit · WordPress governance faces structural crisis]] — the WP Engine dispute framed as a governance crisis; now linked to the Trademarking-a-Commons and BDFL-Litigation permanents - [[3. Resources/Literature Notes/Lit · WordPress scales with proper architecture]] — enterprise scale/security/governance needs; linked to the CMS-Decision and Core-Abilities permanents ### Sub-MOCs (added 2026-05-28) - [[DevRel MOC]] — strategy, frameworks, measurement, sustainability; relevant here as the developer-relations face of open-source governance - [[NAR and Charismatic Authority Critique MOC]] — the religious cognate of OSS BDFL failure; cross-domain comparison material lives there ### DevRel Operations & Measurement - [[3. Resources/Permanent Notes/DevRel Programs Take Three to Five Years to Show Results]] — Timeline mismatch between annual budgets and multi-year maturity kills programs - [[3. Resources/Permanent Notes/The Four Objectives Framework Replaces Vanity Metrics in DevRel]] — Map every metric to Awareness/Activation/Engagement/Retention - [[3. Resources/Permanent Notes/DevRel Maturity Is a Five-Stage Progression Not a Binary State]] — Five stages from zero to scale - [[3. Resources/Permanent Notes/Developer Segmentation Requires Four Filters Not One]] — Technical, User, Organization, and Market filters - [[3. Resources/Permanent Notes/Friction Logging Is the DevRel Equivalent of Code Review]] — Walking the developer journey yourself and documenting every stumble - [[3. Resources/Permanent Notes/DevRel Career Paths Have a Glass Ceiling Problem]] — Breadth prevents depth, limiting advancement ### Leadership & Distributed Authority - [[3. Resources/Permanent Notes/Intent-Based Leadership Outperforms Permission-Based Leadership]] — "I intend to" vs permission-seeking; structural opposite of BDFL - [[3. Resources/Permanent Notes/Competence Is the Prerequisite for Distributing Authority]] — Delegation without competence produces bad decisions faster - [[3. Resources/Permanent Notes/Empowerment Without Clarity Is Abdication]] — Specify goals, not methods, as real autonomy - [[3. Resources/Permanent Notes/The Workhorse Trap Prevents Leadership Emergence]] — Identity shift from "I do the hard things" to enabling others - [[3. Resources/Permanent Notes/Values Alignment Predicts Team Performance Better Than Process Compliance]] — Generative cultures outperform process-heavy cultures ### Community Architecture - [[3. Resources/Permanent Notes/Belonging Requires Choice Connection and Progress]] — Three conditions for community retention - [[3. Resources/Permanent Notes/The Seven Principles Are a Community Diagnostic]] — Jones/Vogl's community health checklist - [[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/A Project Is the Community Not the Code]] (added 2026-06-09) — the load-bearing premise the others rest on: the durable asset is the community, not the code ("without a community, it is just free code on the Internet"). AI sharpens it — cheap code raises the premium on the community layer, the OSS twin of [[3. Resources/Permanent Notes/When Answers Are Cheap Understanding Becomes the Scarce Good]]. Foundations as "IDEs for people" (Libby Clark; Valkey fork in weeks). ### To Create - [ ] Open source governance exists on a spectrum from BDFL to pure democracy - [ ] Foundations provide legal protection but add overhead - [ ] The founder's dilemma applies to open source projects - [ ] Corporate sponsorship trades resources for trust - [ ] Formalization timing matters — too early kills agility, too late creates chaos --- ## Literature Notes - [[3. Resources/Literature Notes/BDFL and NAR - Parallel Structures of Charismatic Authority]] — Cross-domain analysis of singular authority patterns in OSS and religious movements - [[3. Resources/Literature Notes/Individual Autonomy vs Collective Good - Literature Review]] — Synthesis of faith and open source sources on autonomy/collective tension - [[3. Resources/Literature Notes/The Maintainer's Burden - Open Source Beyond the Bazaar - Literature Note]] — Raymond vs. Eghbal on the true structure of open source projects - [[3. Resources/Literature Notes/The Developer Journey - Awareness to Advocacy - Literature Note]] — DevRel as education, infrastructure, and the burnout it creates - [[3. Resources/Literature Notes/DevRel at Scale - Operations Measurement and Organizational Design - Literature Note]] — Operational side of DevRel from Lewko/Parton - [[3. Resources/Literature Notes/Leadership and Distributed Authority - From Command to Intent - Literature Note]] — Marquet, Azzarello, Drasner, Abdaal on distributed vs centralized leadership - [[3. Resources/Literature Notes/Community Architecture - What Makes Communities Thrive vs Extract - Literature Note]] — Jones/Vogl, Spinks, Eghbal on healthy vs extractive communities - [[3. Resources/Literature Notes/Community Engagement In Open Source 2]] — the employee-side rationale for company OSS participation (talent development + retention), from The Business and Economics of Linux and Open Source - [[3. Resources/Literature Notes/Deliberate Mentoring Accelerates OSS Onboarding - Literature Note]] — added 2026-05-28; Pinto et al. empirical study (9 OSS projects, 120+ students) showing mentored newcomers reach productive contribution measurably earlier than self-directed entrants; project size and lifetime moderate the effect - [[3. Resources/Literature Notes/WP Engine v Automattic Discovery Disputes May 2026 - Litigation Roundup - Literature Note]] — added 2026-05-29; 11 May 2026 court filings + 2 docket-index entries from N.D. Cal docket 3:24-cv-06917; the procedural posture of the discovery-disputes phase as structured record of the BDFL governance question - **June 2026 ruling (added 2026-06-08):** [U.S. Court Orders WP Engine to Reveal Strategy Deck Sentence, Finds Mullenweg Was “Evasive” in Deposition](3.%20Resources/Readwise/Articles/U.S.%20Court%20Orders%20WP%20Engine%20to%20Reveal%20Strategy%20Deck%20Sentence%2C%20Finds%20Mullenweg%20Was%20%E2%80%9CEvasive%E2%80%9D%20in%20Deposition%20%5B01ktkntvenmh5mrw8vadkzsrav%5D.md) + the Dkt. 337 order itself (Reader doc "Order Re: Discovery Disputes"). Magistrate Judge Krishnan (June 5): granted Automattic's motion to compel WPE's **internal Asana/Jira/Figma/Miro** communications ("internal discussions may contain admissions as to the necessity of referencing... the trademarks"); granted WPE 3 more hours of Mullenweg deposition (he had 3 days / 21 hrs; "evasive"); ordered WPE's Head of Brand for a further 5-hr deposition. Fact discovery closed May 14; expert discovery now; **jury trial set September 2027**. Notable new atom candidate: *modern litigation discovery reaches SaaS collaboration tools — a fair-use defense doesn't wall off internal deliberation*. ⛏️ candidate - [[3. Resources/Literature Notes/WordPress Foundation Institutional Independence - Tracking Note]] — added 2026-05-29; **active tracker** with provisional status. Four working hypotheses (shell nonprofit / genuine but constrained / genuine and substantive / hybrid) + six empirical tests + ingest-list of primary sources needed (WP Engine complaints, Foundation 990s, bylaws, trademark-license agreement). Update protocol specified. - [[3. Resources/Literature Notes/Decline of PHP in Web Development]] — added 2026-06-27; WordPress's JS-first turn vs PHP's decline; the foundation-steward response (PHP Foundation) parallels the foundation-governance analyses above — pairs with [[1. Projects/Open Source Foundations/OSS Governance Analysis/PHP Foundation Governance Analysis]] - [[3. Resources/Literature Notes/Matt Mullenweg and the BDFL Model]] — added 2026-07-14 (synthesis sweep); narrative essay covering the same WP Engine conflict/employee-departures ground the litigation and market-share permanents already track — the qualitative case study underneath the quantitative claims - [[3. Resources/Literature Notes/Logical Validity of Conway's Law in Software Engineering]] — added 2026-07-14 (synthesis sweep); the structural mechanism (org communication shape → system architecture shape) underneath why BDFL governance produces the specific kind of centralized software it does --- ## Platform-Level Defaults as Infrastructure (added 2026-05-29) A cross-domain convergence between web standards, accessibility advocacy, and Core Web Vitals empirical data on a single structural claim: platform-level defaults dominate site-level optimization for audience-serving outcomes at web scale. Joost de Valk's specification.website argues for unified platform-target defaults that lets frameworks render to multiple audiences (humans, search engines, screen-reader users, AI agents) simultaneously. Anne Bovelett's accessibility-tree analysis documents the 50,000-vs-4,000-token cost differential between agent-readable semantic HTML and div-soup. The SEJ Core Web Vitals comparison shows WordPress at 49% good CWV (vs Duda's 85%, Wix's 80%, Shopify's anomalous 79% despite worst page weight) — a platform-architecture-effect that site-level optimization cannot close at population scale. The thread connects to the WordPress saga as the WordPress-specific question: which actor in the WordPress ecosystem is structurally positioned to play the 2026 platform-defaults role that Yoast played in 2010 for sitemaps? ### Atomic claim promoted from this corpus - [[3. Resources/Permanent Notes/Platform-Level Defaults Beat Site-Level Optimization for the Same Audiences]] — the central structural claim with cross-domain evidence from three independent vantages ### Primary source pieces (May 2026) - [[3. Resources/Readwise/Articles/Fixing the plumbing of the web · Joost.blog]] — Joost de Valk's specification.website launch piece; canonical Yoast 2010 sitemap precedent; "plumber" metaphor framing the anti-rebranding-of-SEO argument - [[3. Resources/Readwise/Articles/Your website is now an API for AI agents, and you’re NOT ready|Your website is now an API for AI agents, and you're NOT ready]] — Anne Bovelett's accessibility-tree cost-economics framing; 50k vs 4k token differential; three-audiences-one-fix unification of accessibility, SEO, and agent-readiness - [[3. Resources/Readwise/Articles/Core Web Vitals WordPress and Astro Versus Everyone Else]] — HTTP Archive Core Web Vitals comparison; Shopify anomaly (worst page weight, third-best real-world CWV) as evidence for "complexity management > weight reduction" ### Cross-domain analog - [[3. Resources/Permanent Notes/Target Audience Determines Translation Methodology More Than Equivalence Theory Does]] — the same audience-determination logic applied to scripture translation (Perriman's TPT reframing); both web rendering and translation are audience-determined at the design-constraint level ### Connection to the WordPress Saga thread The platform-defaults question is the operational form of the BDFL-governance question for WordPress. Changes to core that would shift the supply curve for the entire ecosystem (semantic HTML output defaults, complexity management at the rendering layer, opinionated CWV-optimization defaults) are structurally blocked by the BDFL governance structure documented in the saga sources below. The 2010 Yoast sitemap moment happened in plugins precisely because core was structurally slow to ship the default; the 2026 question is whether a similar plugin/theme-layer actor can deliver the platform-defaults moment, or whether the larger structural shifts require core-level changes that BDFL governance cannot move at the required pace. --- - [[3. Resources/Permanent Notes/A Shared Schema Turns Distribution Into Retrieval]] — agreeing the structure in advance replaces per-consumer parsing; the cost moves to governing the schema. ## WordPress Saga (2025-2026) — Convergent Vantages A multi-source case study in concentrated authority, private-equity vendor pressure, and contested-commons governance. Each source is a distinct vantage on the same conflict. ### Founder / leadership statements - [[3. Resources/Readwise/Articles/WP23]] — Matt Mullenweg's 23rd-birthday post: "WordPress at 23 is simultaneously both the strongest and most precarious it's ever been" + the "Silver Lake / shoggoth / Golem Jagannath" framing + "LITERALLY DYING" reference - [[3. Resources/Readwise/Articles/Matt Mullenweg Uses WordPress’s 23rd Birthday to Appeal Directly to Silver Lake “You’ve Won. I Submit.”]] — The Repository's framing: "You've won. I submit." as direct address; community reaction (Hayes Smith, Schroeder); RT-collab pull as documented litigation cost - [Maybe](3.%20Resources/Readwise/Articles/Maybe%20%5B01kszf3xbkyaz94rgh4tc13229%5D.md) — Mullenweg's May 30, 2026 follow-up to WP23; confirms WP23 was "part catharsis and part giving voice to what I see and hear privately from people who aren't public figures"; reframes 21hr/3day depositions as "energizing"; references Alan Watts "Chinese Farmer" parable on uncertainty/reframing ### Independent critique - [[3. Resources/Readwise/Articles/Grow the ecosystem, not just yourself]] — Dries Buytaert (Drupal): license-is-the-floor / social-contract-above framing; the 2,955 vs 30 Acquia/Pantheon credits as accountability signal - [[3. Resources/Readwise/Articles/Timeline of the WordPress Drama - DevLog]] — Duerrenberger: five-roles concentration diagnosis (BDFL + .org owner + Foundation board + Automattic CEO + WP trademark); permissive-license argument; .org-blocks-security-updates documentation - [[3. Resources/Readwise/Articles/The WP Community Collective Launches State of the Community Survey]] — WPCC + Sé Reed: "the WordPress community is not hypothetical" + the harassment/participation question ### Community voices (tweets) - [[3. Resources/Readwise/Tweets/The Problem Is @Photomatt Is Right About Private Equity|The problem is @photomatt is right about private equity]] — Jeremy Koering: Liquid Web / StellarWP as PE proof point - [Matt, I’ve Followed the WordPress Saga for a While Now...](3.%20Resources/Readwise/Tweets/Matt,%20I’ve%20Followed%20the%20WordPress%20Saga%20for%20a%20While%20Now....md) — Pancho Avila: Eric Binnion diagnosis-as-leverage ethics critique - [[3. Resources/Readwise/Tweets/I Obviously Don’t Want Any Harm to Come to WordPress]] — Trent Lapinski: both-hands framing + "shell nonprofit" first-hand testimony ### Downstream signals - [[3. Resources/Readwise/Articles/WordPress Market Share Declines For Six Months In A Row]] — Roger Montti / Search Engine Journal (May 2026): six consecutive months of market-share decline (43.2% → 41.9%); Shopify/Wix/Squarespace all gaining; vendor first-person testimony ("I as a vendor need to trust the people leading the software I recommend") as the trust-erosion mechanism. The first outcome-side measurement on the saga. ### Hosting security tier (May 2026) A three-piece tile naming the AI-era security positioning shift in the managed-WordPress hosting market — threat, response, and failure mode. - **The threat** — [[3. Resources/Readwise/Articles/Patchstack CEO Warns WordPress 7.0 Could Trigger “Absolute Rush” To Steal AI API Keys]]: Oliver Sild's argument that AI API keys change attack economics (attackers can spend victim's tokens directly, not just commandeer resources). 11,334 new WP-ecosystem CVEs in 2025 (+42% YoY); 5-hour exploitation window; 70-90% of hosted sites have at least one known vulnerability. WP Security Team's John Blackbourn admits no native two-way encryption survives key rotation or migration — the architectural gap. - **The response** — [Secure Hosting Alliance Certification WordPress VIP](3.%20Resources/Readwise/Articles/Secure%20Hosting%20Alliance%20Certification%20WordPress%20VIP%20%5B01ksqyb66pdyzdahwr2s93hftv%5D.md): WordPress VIP (Automattic's enterprise arm) joins the inaugural SHA cohort. Pitch is third-party-attestation stack (SOC 2 + FedRAMP + SHA) as the noise filter for evaluating providers beyond marketing/pricing. Industry-coordination framing — collective standards effort, not a single-vendor badge. - **The failure mode** — [[3. Resources/Readwise/Articles/SiteGround's Icky Approach to AI in WordPress 7.0 - Rhys Wynne]]: Rhys Wynne on SiteGround's WP 7.0 AI Connector activated by default for paying customers, hidden at the bottom of wp-admin, with API key stored in the very layer Blackbourn says can't be safely encrypted. The "switch it on and hope no one notices" pattern in a hosting product. The three pieces together name a market positioning shift in the managed-WordPress space: "we ship certified secure" (VIP / Automattic) vs. "we ship convenient AI defaults" (SiteGround), with the independent threat data (Patchstack) saying the second posture is dangerous in a way that quantifies the first one's value. See also: [[AI Agent Safety MOC]] and the related [[WordPress Hosting Security Stack MOC]] for the credential-storage / opt-in-vs-default-on cross-thread. ### Procedural posture (litigation, May 2026) The discovery-disputes phase of WP Engine v. Automattic (N.D. Cal docket 3:24-cv-06917) produces structured records that operationalize the BDFL-governance theses developed elsewhere in this MOC. The May 2026 batch of 11 filings + 2 docket-index entries covers: - **The Rule 33 interrogatory-limit dispute** — Defendants oppose WPE's motion to compel responses to compound interrogatories (45 to Automattic, 70 to Mullenweg, 44 to WooCommerce, 47 to WordPress Foundation) on the procedural basis that WPE did not seek leave of court before exceeding the 25-per-party limit - **The reciprocal financial-discovery agreement dispute** — Both sides agree the November 2025-April 2026 negotiation produced a "balanced reciprocal agreement"; both sides now disagree about what that agreement permits going forward (WPE: 630,000+ pages produced; Defendants: only 36 emails referencing the financial decline) - **The Audrey HC / Audrey Capital subpoenas** — Court orders disclosure of investigation scope + Bates-stamping + Hackerone.com search by June 3, 2026; Audrey entities are Mullenweg's personal holding vehicles - **The Silver Lake subpoenas** — Court orders production of responsive documents to Automattic's financial search terms by June 10, 2026; internal Silver Lake discussions of WPE communications are discoverable even where the underlying WPE communications are not - **The inadvertent-redaction administrative motion** — WPE's docket-296-series filings contained AEO material with incorrect redactions; re-filed at docket 309-series; administrative motion to remove the 296 entries pending For the full procedural synthesis, see: - [[3. Resources/Literature Notes/WP Engine v Automattic Discovery Disputes May 2026 - Litigation Roundup - Literature Note]] — full structural synthesis with named participants, key disputes, forward timeline (June 1/3/10 court-ordered deadlines) - [[3. Resources/Permanent Notes/BDFL Litigation Necessarily Implicates Personal Corporate and Foundation Roles Because the BDFL Has Concentrated Them]] — the cross-cutting claim this batch of filings substantiates The litigation operationalizes the [[3. Resources/Permanent Notes/Concentrated Authority Without Accountability Produces the Same Failure Patterns Across Religious and Software Ecosystems]] thesis concretely: discovery scope necessarily extends across personal/corporate/foundation/investment-vehicle records because the BDFL has concentrated those roles. The wide discovery footprint is partly a deferred cost of the original governance design. ### Cross-thread analysis (open questions) - The Buytaert vs Duerrenberger split: both diagnose the same ecosystem dynamic; Buytaert prescribes social-contract stewardship as remedy, Duerrenberger holds that permissive-license signers have no grounds to demand more. Same observation, opposite policy prescription. - The WPCC survey is the first attempt at systematic measurement of how community members are experiencing the saga (harassment, participation chilling, governance trust). - [[3. Resources/Permanent Notes/A Defendant's Admissions Constrain the Record Its Denials Do Not]] — how to read the class-action filings: concessions are informative, denials are procedural. - [[3. Resources/Permanent Notes/Redundancy Built Under Duress Becomes Evidence You Were Never Trapped]] — the inversion at the centre of the dependency argument — forced replication reread as proof the dependency was avoidable. - [[3. Resources/Permanent Notes/A Litigant's Public Statement Is Dated Evidence Not a Verdict]] — the boundary that keeps the whole saga readable: posts establish a timeline, not the underlying facts. ## 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]] — split the category instead of winning the definition (Kardell on the Web Platform) - [[3. Resources/Permanent Notes/Open-Source Design Tools Reach Parity Through Community-Contribution Velocity]] — the stadium pattern producing parity (Penpot 2.16) - [[3. Resources/Permanent Notes/Zet · Enterprise open-source participation needs policy and training scaffolding]] — Qualcomm: opening up is a policy/culture problem before a technical one ## Connected Literature Notes (synthesis 2026-06-17) - [[2023 State of Open Source Report]] — survey data on enterprise OSS adoption trends - [[A Field Guide to Threat Vectors in the Software Supply Chain]] — dependency/supply-chain risk as the security cost of open ecosystems - [[Announcing GUAC, a great pairing with SLSA (and SBOM)!]] — Google's open-source supply-chain metadata graph (SLSA+SBOM) (backfill 2026-06-18) ## Connected Literature Notes (synthesis 2026-06-20) - [[BDFL and NAR - Parallel Structures of Charismatic Authority]] — BDFL governance as personality-driven authority, paralleled with NAR - [[Blackfoot Wisdom, Maslow’s Hierarchy, and Open Source]] — community-flourishing-over-gain as a governance value (synthesis 2026-06-21) ## Synthesis additions (2026-06-21) - [[3. Resources/Permanent Notes/Real Standards Adoption Means Implementing the Draft and Pushing the Gaps Upstream]] — Joost de Valk (OKF/ARD): the agentic-web standards case of open-source citizenship — an early adopter only matures a standard by implementing the draft *and* filing the gaps upstream as registrable fixes + reference implementations. Extends the [[3. Resources/Permanent Notes/Public Credit Mechanisms Are the Visible Skeleton of Open Source Social Contracts]] / maintainer-attention thread. ## Connected Literature Notes (synthesis 2026-06-26) - [[Importance of Diversity in Open Source]] — GitHub All-In skilling program as a concrete inclusion lever (orphan reconnected this sweep) - [[Importance of Collaborating with the Open Source Community]] — collaboration norms as a governance practice (orphan reconnected this sweep) ## Synthesis additions (2026-06-28 gap-fill) From the "Anthropic's War on Opensource AI" deep-read: - [[3. Resources/Permanent Notes/A Frontier Lab Can Learn From the World While Restricting the World From Learning From It]] — names the structural mechanism of closed-lab capture: a lab trains on the open commons yet binds its outputs against building rivals, so a safety framing can run as a permission regime / competitive moat. Represented neutrally — the verifiable parts are the output-use policy asymmetry and access cutoffs; the broader "war on open source" thesis is contested. Extends [[3. Resources/Permanent Notes/Permissive Licenses Define a Floor But Don't Constitute a Community]] (openness in name vs obligation). Also homed in [[Commons & Community Governance MOC]] and [[AI Cost & Tokenomics MOC]]. ## Synthesis additions (2026-07-03 gap-fill — WordPress market share series) From The Repository's three-dataset market-share analysis + Ciorici's State of WordPress Themes report. These sharpen the existing [[3. Resources/Permanent Notes/Open Source Project Market Share Tracks Founder Trust]] (evergreen) by adding the *measurement* and *structural* layers the founder-trust thesis alone doesn't capture: - [[3. Resources/Permanent Notes/WordPress Market Share Is a Lagging Indicator That Trails Momentum Loss]] — why the headline % can't prove any causal story from its timing: it's cumulative installs, so it lags leading indicators (search interest peaked ~2014, pro-tier 2022) by years. The measurement companion to the founder-trust note. Cross-homed in [[Product & Startup Instincts MOC]]. - [[3. Resources/Permanent Notes/WordPress's 2026 Losses Went to No-CMS Sites Not Competitors]] — the surprising 2026 finding: WP's losses went to "None" (no detectable CMS), not Shopify/Wix — Koenig's "It's vibecoding." A structural AI-disruption cause that runs *alongside* trust erosion, not instead of it. Cross-homed in [[AI & the Future of Knowledge Work MOC]]. - [[3. Resources/Permanent Notes/Block Theme Development Has Outpaced Block Theme Adoption]] — dev-side vs adoption-side gap (44.2% of new submissions, 8.3% of non-default installs); reconciles the earlier [[3. Resources/Permanent Notes/Zet · Block themes are overtaking classic themes in install share]] via the default-vs-non-default distinction. Cross-homed in [[DevRel MOC]]. ## Synthesis additions (2026-07-18 gap-fill — Ginder AI security pipeline) From the deep-read of Austin Ginder's "My AI Security Pipeline for WordPress Plugins" (anchor.host) + companion "Build anything with Claude & WordPress" talk. One new Permanent promoted; it sharpens the existing supply-chain thread by adding the *scaling* layer the actor-tracking note doesn't cover: - [[3. Resources/Permanent Notes/Auditing the Build Not the Install Is What Makes Personal-Scale Coverage Possible]] — content-addressed dedup of builds (hash once, apply everywhere the hash appears) is what lets one operator on a $200/mo plan stay current with the popular half of the plugin repository (918 builds/wk audited vs ~612 updates/wk inflow; 100% coverage above 500k installs). The *how you scale the scan* companion to [[3. Resources/Permanent Notes/Supply-Chain Defense Tracks Bad Actors Not Bad Code]] (*what the scan must track*), and the lever that stretches the scarce resource in [[3. Resources/Permanent Notes/Maintainer Attention Is the Scarce Resource in Open Source]]. ## Connected Literature Notes (synthesis 2026-07-18) Five long-orphaned open-source literature notes reconnected this sweep (each given an annotated `## Links` section + status: seedling): - [[3. Resources/Literature Notes/Embracing Open Source]] — Joost de Valk's WebKit → WordPress Core → Yoast arc; a first-person account of the contributor economy this MOC maps - [[3. Resources/Literature Notes/Future of Open Source Technologies]] — OpenLogic enterprise-adoption forecast; the macro-adoption vantage that collides with the maintainer-attention bottleneck - [[3. Resources/Literature Notes/Red Hat's Commitment to Open Source - Upholding Values and Sustainability]] — McGrath's paid-maintenance-model defense; the value-free-repackaging/sustainability argument (contrast to The Inverse Commons) - [[3. Resources/Literature Notes/The Drupal Open Web Manifesto - Advancing the Principles of the Open Web]] — a foundation codifying values as project constitution; also homed in [[3. Resources/MOCs/Commons & Community Governance MOC]] - [[3. Resources/Literature Notes/Two Kings, One Mirror - The Hypocrisy of Open Source Leadership]] — DHH/Mullenweg parallel governance-capture case study; substantiates the BDFL-litigation and concentrated-authority permanents ## Connected Literature Notes (synthesis 2026-07-18 — 20-doc batch) - [[3. Resources/Literature Notes/WordPress 7.1 Beta 1 Ships With Responsive Styling, Media Overhaul, and Persistent Toolbar]] — The Repository's 7.1 Beta 1 coverage: RTC punted entirely incl. primitives; Mullenweg's double-digit-WoW AI-adoption bar; Classic-block-obsolete-by-choice - [[3. Resources/Literature Notes/WordPress 7.1 Beta 1]] — The official make/core 7.1 Beta 1 release notes; the primary-source companion to the Repository coverage - [[3. Resources/Literature Notes/Better Way - Anne McCarthy]] — The first-time 7.1 Release Lead on open source as 'a better way,' written mid-Beta-1; the human-labor vantage on release leadership ## Connected Literature Notes (synthesis 2026-07-18 — batch 2) - [[3. Resources/Literature Notes/Consistent navigation in WordPress 7.1 with persistent toolbar]] — the make/core dev-note on the 7.1 persistent toolbar; one-meaning-per-icon as the structural fix for icon overload - [[3. Resources/Literature Notes/Developer's Plugin Submission Flagged Over '-Press' Suffix, Later Approved, Raising Questions About Review Consistency]] — WP.org plugin-review inconsistency; cite the documented rule set, not the rejection message, to reverse automated moderation ## Connected Literature Notes (synthesis 2026-07-18 — batch 3) - [[3. Resources/Literature Notes/WordCamp US 2026 Plays Catch-Up for Second Year Running as Ticket Sales Lag and Community Waits for Schedule]] — a withheld schedule near the date becomes its own signal of trouble; WP flagship-event health as a community-governance indicator - [[3. Resources/Literature Notes/Delaware Court Blocks CloudLinux From Launching AutopilotWP After Seahawk Alleges Competing Tool Was Built Using Its Trade Secrets]] — advisory-access investment deals leak competitive intelligence regardless of outcome; a WP-ecosystem trade-secret/governance case - [[3. Resources/Literature Notes/The State of Open Source AI 2026]] — vertical integration (model + tuned harness) turns a swappable model into rented lock-in; the open-vs-closed AI landscape - [[3. Resources/Literature Notes/Understanding Open Source Law and AI Impacts in Modern Software Development]] — AI-assisted authorship: the copyright-relevant work is the documented decisions after generation, not the prompt; OSS licensing + AI law - [[3. Resources/Literature Notes/Astro - HTML first, JavaScript when you need it]] — tool defaults should mechanically reinforce stated values; connects to the Platform-Level-Defaults / Core-Web-Vitals-Astro thread in this MOC - [[3. Resources/Literature Notes/Creating a WCAG-Compliant WordPress Website in 2026]] — accessibility holds only when built into markup from the start — overlay plugins can't fix a non-semantic foundation; WP a11y (no dedicated a11y MOC, homed here) ## Connected Litigation Notes (synthesis 2026-07-21) - [[3. Resources/Literature Notes/Lit · Court dismisses and allows mixed claims]] — the mixed ruling shows which concentrated-authority claims survive early judicial review - [[3. Resources/Literature Notes/Lit · Enforcement rights structure becomes public]] — the trademark transfer and license terms reveal where formal enforcement power sits - [[3. Resources/Literature Notes/Lit · Evidence centers on consumer confusion and SEO]] — the countersuit's factual hinge connects trademark doctrine to stewardship of a shared project name ## Connected Literature Notes (synthesis 2026-07-21 — run 4) - [[3. Resources/Literature Notes/Lit · WP Engine files 175-page revised complaint]] — records the revised complaint as a new procedural phase in the WordPress governance dispute - [[3. Resources/Literature Notes/Lit · What is the Web Platform — categorical precision]] — shows how obligations-scoped categories govern standards work better than one totalizing definition - [[3. Resources/Permanent Notes/Zet · Alleged undisclosed trademark license terms]] — tracks the disputed trademark-control terms exposed through the revised complaint - [[3. Resources/Permanent Notes/Zet · Four markets defined for antitrust theory]] — records the market-definition structure used to frame the revised antitrust claims ## Connected Literature Notes (synthesis 2026-07-21 — run 5) - [[3. Resources/Literature Notes/Lit · WordPress UX decisions require community feedback loops]] — prototype PRs become durable core patterns only after community feedback tests their UX assumptions - [[3. Resources/Permanent Notes/Zet · Community experiments inform core development patterns]] — community prototype feedback is the governance mechanism that tests whether a core UX pattern should land - [[3. Resources/Permanent Notes/Zet · WordPress governance centralizes around Automattic]] — names the concentrated authority structure behind the wider WordPress governance crisis ## Connected Literature Notes (synthesis 2026-07-21 — run 6) - [[3. Resources/Literature Notes/Meet the System Package Data Exchange SPDX 3.0]] — a shared software-bill-of-materials model makes supply-chain identity and provenance portable across ecosystems - [[3. Resources/Literature Notes/Methodology of OpenLogic's Open Source Report]] — documents how enterprise open-source adoption evidence was sampled and bounded - [[3. Resources/Literature Notes/Open Source Adoption Trends in 2023]] — tracks the adoption pattern reported from the OpenLogic survey corpus - [[3. Resources/Literature Notes/Open Source Projects in Enterprise Settings]] — connects project governance choices to enterprise operating constraints - [[3. Resources/Literature Notes/Open Source Software Built by Programmers for Programmers]] — examines how builder-centered defaults shape who can adopt open software - [[3. Resources/Literature Notes/Open Source Software in Enterprise Ecology]] — places individual projects inside the wider commercial and institutional system that sustains them ## Connected Literature Notes (synthesis 2026-07-21 — run 7) - [[3. Resources/Literature Notes/Open Source and United Nations Goals]] — connects open collaboration practices to public-interest development goals - [[3. Resources/Literature Notes/Open Source in Enterprise Development]] — examines how enterprise constraints shape open-source adoption and contribution - [[3. Resources/Literature Notes/Phase 3 Collaboration]] — collaborative editing makes shared workflow design a core-platform governance concern - [[3. Resources/Literature Notes/Quality Control In WordPress]] — locates quality control in the project processes that review and ship shared code - [[3. Resources/Literature Notes/Recommendations for Transparency and Objectivity in WordPress Recommended Hosting]] — treats hosting recommendations as a disclosure and stewardship obligation ## Connected Literature Notes (synthesis 2026-07-21 — run 8) - [[3. Resources/Literature Notes/SBOM at a Glance]] — concise map of the inventory and provenance contract behind software bills of materials - [[3. Resources/Literature Notes/Software Bill of Materials (SBOM) - Enhancing Transparency and Supply Chain Security]] — connects component disclosure to shared supply-chain accountability - [[3. Resources/Literature Notes/State of Accessibility in WordPress 6.3 Gutenberg]] — records accessibility quality as a core-project responsibility rather than an optional plugin concern - [[3. Resources/Literature Notes/The Case for a SaaS Bill of Material]] — extends component transparency from shipped software into hosted service dependencies ## Connected Literature Notes (synthesis 2026-07-21 — run 9) - [[3. Resources/Literature Notes/The Feasibility and Governance Concerns Behind 5% Contribution to WordPress Core]] — tests a contribution mandate against authority, measurement, and ecosystem-capacity constraints ## Connected Permanent Notes (synthesis 2026-07-21 — run 10) - [[3. Resources/Permanent Notes/npm Lockfiles Are Resolver-Version Specific]] — package-lock changes can reflect resolver-version behavior rather than an intentional dependency-policy change ## Connected Literature Notes (synthesis 2026-07-21 — run 10) - [[3. Resources/Literature Notes/The elePHPant in the Room - WordPress - PHP's Evolution and WordPress's Relevance]] — connects WordPress's compatibility and editor choices to the future of its PHP-based open-source ecosystem - [[3. Resources/Literature Notes/Understanding the Objectives of the CISA Fact Sheet]] — frames open-source components in operational technology as a shared supply-chain governance and risk-management problem - [[3. Resources/Literature Notes/Updating WordPress Core with Gutenberg Features]] — treats Gutenberg-to-core integration timing as release governance that must balance iteration speed with dependency and stability risk ## Connected Literature Notes (synthesis 2026-07-21 — run 11) - [[3. Resources/Literature Notes/WordPress for Enterprise - Performance Metrics]] — makes enterprise performance claims a testable part of the platform's adoption and stewardship case - [[3. Resources/Literature Notes/WordPress.org Contribution Consideration if it is just Matt Mullenweg's Website]] — tests contributor reliance and sponsored labor against the gap between a community platform's public role and privately concentrated control ## Connected Permanent Notes (synthesis 2026-07-21 — run 11) - [[3. Resources/Permanent Notes/Zet · Multiple testing pathways increase participation]] — release testing reaches more contributors when plugin, archive, command-line, and browser routes accommodate different environments ## Connected Permanent Notes (synthesis 2026-07-21 — run 17) - [[3. Resources/Permanent Notes/Greenwashing]] — examines how environmental language and corporate sustainability claims can mask the withdrawal of resources from community-led environmental work - [[3. Resources/Permanent Notes/Pin Composer Platform PHP for Portable CI Lockfiles]] — makes committed dependency resolution portable across a supported PHP matrix by pinning the environment Composer resolves against ## Connected Permanent Notes (synthesis 2026-07-21 — run 18) - [[3. Resources/Permanent Notes/Matt Mullenweg WCUS 2024 Keynote - WP Engine]] — captures the public commons, contribution, and stewardship arguments used to frame the WordPress–WP Engine dispute - [[3. Resources/Permanent Notes/Open Source Governance - Narcissistic Leadership Pattern Analysis Framework]] — assembles leadership-pattern research for evaluating concentrated authority, community harm, and governance failure without treating one anecdote as diagnosis - [[3. Resources/Permanent Notes/Open-Source and "The Go-Giver"]] — attempts to connect value, influence, authenticity, and reciprocity principles to participation in open-source projects - [[3. Resources/Permanent Notes/NAR Governance Mirrors BDFL - Singular Authority With No Credible Exit]] — compares founder-centered software governance with charismatic religious authority where concentrated control leaves participants no credible internal appeal ## Connected Permanent Notes (synthesis 2026-07-21 — run 19) - [[3. Resources/Permanent Notes/Perm · Decoupling from the web means moving content to closed platforms, not achieving independence]] — distinguishes open-web portability from dependence disguised as freedom inside proprietary app ecosystems - [[3. Resources/Permanent Notes/Perm · Open source sustainability fails when emotional labor is expected for free]] — identifies unpaid support, moderation, and contributor care as the hidden workload that drives maintainer turnover - [[3. Resources/Permanent Notes/Perm · Markdown won because it solved the format lock-in problem, not for syntax]] — treats portable plain text as a standards-governance win over proprietary content captivity - [[3. Resources/Permanent Notes/Perm · Platform maturity is a lagging indicator on the S-curve]] — separates a large installed commons from the weaker adoption flow that determines its future health ## Connected Permanent Notes (synthesis 2026-07-21 — run 20) - [[3. Resources/Permanent Notes/Perm · WordPress plugin ecosystem is a supply-chain target for long-term backdoor campaigns]] — shows how trusted distribution, ownership changes, and delayed activation turn ecosystem governance into a long-horizon security problem ## Connected Permanent Notes (synthesis 2026-07-21 — run 24) - [[3. Resources/Permanent Notes/WordPress's Compatibility-First Culture Is Now Its Binding Security Constraint]] — identifies backward-compatibility economics and ecosystem acceptance, rather than bug discovery alone, as the constraint on structural security change ## Synthesis additions (2026-07-22) - [[3. Resources/Permanent Notes/Ranking Anomalies Trigger Investigation, Not Attribution]] — calls for auditable integrity review while keeping anomalous data separate from actor attribution. - [[3. Resources/Literature Notes/Challenges in Software Security for OT and ICS]] — adds the stewardship constraints around open-source dependencies used in critical infrastructure. ## Synthesis additions (2026-07-25) - [[3. Resources/Permanent Notes/An Intent-to-Use Filing Gives a Steward Silent Priority Over the Commons It Stewards]] — the procedural mechanism by which a steward acquires a community-used term without notice, dispute, or an adjudicated answer. - [[3. Resources/Literature Notes/Lit · The WP Community Collective rebrands as The WPOCC]] — the WPCC/Campus Connect chronology, and The WPOCC's preemptive rebrand. ## Synthesis additions (2026-08-01) - [[3. Resources/Permanent Notes/Gate Contributions on Demonstrated Comprehension Not on Tooling]] — the design principle separating a workable AI-contribution policy from an unenforceable one: regulate the validation a submitter performed, not the tool they used. Codeberg's tool-detection approach is the negative case; the one-paragraph rule is the positive one. - [[3. Resources/Permanent Notes/Portability Is Proven by a Second Implementer Not by Design Intent]] — the evidentiary standard for any "vendor-neutral" or "domain-agnostic" governance claim: who is the second implementer, and did the core change to admit them? - [[3. Resources/Readwise/Articles/The PHP Podcast 2026.07.30]] — source for the maintainer-burden thread: curl's bug bounty shutdown, Codeberg's unenforceable AI policy, and the reputation-under-volume problem that makes newcomer contribution harder than it has ever been. - [[3. Resources/Readwise/Articles/Episode 31 Brent Toderash]] — FAIR as a software-supply-chain protocol rather than a WordPress project, with TYPO3 v14 as the first independent adoption; also the consultant-liability argument for supply-chain independence. ## Synthesis additions (2026-08-01, run 2) - [[3. Resources/Permanent Notes/A Defense Experts Fail Is Not a Defense for Users]] — the argument that ends "you can read the build script yourself" as a security model. Expert reviewers missed the AUR malware across two campaigns (1,500+ packages, then 200+), so delegating the same inspection to users is a disclaimer rather than a control. Implies the concrete fix: treat maintainer transfer as a reviewed security event, since package adoption was the primary vector. - [[3. Resources/Permanent Notes/Ethical Verdicts on Resistance Track the Judge's Safety]] — filed here as well as in theology because it governs who is credible when judging whether a fork, a refusal, or a licence breach was legitimate. The spread of opinion in those disputes is rarely about the facts. - [[3. Resources/Permanent Notes/Coalitions Held Together by Shared Enemies Break on Affirmative Questions]] — a cheap forecasting tool for fork and coalition durability: ask what the group has agreed to *build*. If the answer is only a list of things it will stop, the fracture is scheduled rather than possible. - [[3. Resources/Permanent Notes/Declaring Readiness Is Not Becoming Ready]] — why self-declared compatibility flags carry no signal. `apiVersion: 3` is checked by nothing, so it transfers confidence without transferring evidence. Generalizes to accessibility statements, security attestations, and SBOM completeness claims — all routinely read as findings rather than as claims. ## Synthesis additions (2026-08-01, run 3–4) - [[3. Resources/Permanent Notes/An Audit Trail Is Trustworthy Only When It Is a By-Product of the Work]] — the governance test behind provenance, compliance, and this vault's own maker/checker loops: a record authored separately from the act is a story, and a record the act cannot avoid producing is evidence. - [[3. Resources/Permanent Notes/AI's Highest-Leverage Role in Open Source Is Communicating Intent Not Generating Code]] — Anne McCarthy's "jankiness by design." Because maintainer attention is the scarce input, a disposable prototype that makes an idea reviewable outperforms a merge candidate that imports the full review burden. - [[3. Resources/Permanent Notes/Structuring for Unaccountability Works Without Ever Denying the Allegation]] — ordinary legal instruments assembled into an entity that can defeat a challenge on standing and jurisdiction without contesting the merits. The question for any steward: who has standing to compel an answer, and what would defeat it? ## Synthesis additions (2026-08-01, run 5) - [[3. Resources/Permanent Notes/Extractive Techniques Outlive the Movements That Develop Them]] — institutional history organized by organization misses transmission that travels with people. The same reason [[3. Resources/Permanent Notes/Supply-Chain Defense Tracks Bad Actors Not Bad Code]] holds in security. - [[3. Resources/Permanent Notes/A Revision Is Legitimate in Proportion to Its Auditability]] — applies directly to specifications, licenses, and standards. Unversioned normative text silently overwrites every past reader's understanding. ## Synthesis additions (2026-08-08) - [[3. Resources/Permanent Notes/WP Trademark Twitter Spaces]] — orphan fix, MOC registration only. Reference-type transcript (not a claim note) covering community reaction, trademark/legal issues, and private-equity impact on the WordPress ecosystem; primary-source material for the trademark/WPE-Automattic governance thread. ## Synthesis additions (2026-08-11, reconciliation) - [[3. Resources/Permanent Notes/Core Abilities Must Be Consumer-Neutral Primitives Not One Interface's Mirror]] — makes consumer-neutrality the governance test for capabilities promoted into a shared core layer. - [[3. Resources/Literature Notes/Lit · WordPress governance faces structural crisis]] — gathers ecosystem-health evidence around concentrated authority, funding pressure, and the WordPress–WP Engine dispute. ## Synthesis additions (2026-08-11, OSS backlog) - [[3. Resources/Readwise/Articles/Consuming With Intent Driving Enterprise Security & Career Growth Through Open Source - Jamie Thomas]] — ties enterprise use to intentional stewardship, project-health assessment, and participation that builds influence rather than treating dependencies as free inventory. - [[3. Resources/Readwise/Articles/From a 7 KB file to a 13-year backdoor operation]] — documents the long-lived WordPress plugin campaign behind the need for continuing repository stewardship after initial review. - [Cloudflare Acquires VoidZero](https://read.readwise.io/read/01kvbbmytp7ahhh7qgntqevq05) — records an acquisition where the company changes hands while Vite remains open source, a useful boundary case between project governance and vendor consolidation. - [Code for the People official trailer](https://read.readwise.io/read/01kvbgtgb4t40fg2h0qz77k2ps) — advocacy source for the open-web ownership argument; retained as rhetoric and presentation material rather than promoted as an analytical claim. ## Synthesis additions (2026-08-11, WordPress release governance) - [[3. Resources/Permanent Notes/A New Testing Channel Cannot Fix an Unclear Testing Ask]] — makes contributor communication, rather than another distribution channel, the first constraint to resolve when pre-release feedback is weak. - [[3. Resources/Readwise/Articles/Anne McCarthy Named WordPress 7.1 Release Lead]] — dated release-lead context for the 7.1 roadmap and focused-squad governance model. - [[3. Resources/Readwise/Articles/Roadmap to 7.1]] — primary roadmap connecting collaboration, shared primitives, responsive styling, and Guidelines work. - [[3. Resources/Readwise/Articles/Core Committers Meeting – WordCamp Europe 2026]] — primary evidence for the Canary-channel communication problem and architecture-first RTC decision. - [Governance Guardrails plugin v1](https://read.readwise.io/read/01kvkwg1chmye6gw24t6q77gjm) — product announcement showing file-based feature availability as a fleet-governance artifact; retained without promoting a new claim. - [[3. Resources/Readwise/Articles/Announcing the WordPress 7.1 Release Squad]] — records the focused release-squad structure and volunteer demand around the 7.1 cycle. ## Synthesis additions (2026-08-11, WordPress ecosystem evidence) - [[3. Resources/Readwise/Articles/WordPress Contributor Dashboard Gets Customizable Ladders for Make Teams in First Major Update Since Pilot Launch]] — connects contribution ladders and shareable views to existing public-credit and teaching-labor claims. - [[3. Resources/Readwise/Articles/Hiding the Classic Block From the Inserter in WordPress 7.1]] — dated core change retained as evidence of a default-hidden, filter-reversible deprecation path. - [How WordPress Education Programs Are Growing](https://read.readwise.io/read/01kvx72184ttnd4sth6f4f939n) — connects Learn WordPress, Credits, Campus Connect, Student Clubs, and meetup activities to the existing teaching-labor and contributor-succession cluster. - [[3. Resources/Readwise/Articles/A Stronger Voice What Membership Can Mean in Open Agentic AI]] — applies the community-not-code principle to membership as shared ownership rather than funding alone. - [[3. Resources/Readwise/Articles/Automattic Wins Privilege Fight Over Pre-Lawsuit Trademark Strategy Slack Messages, Court Set to Rule on Motions to Dismiss]] — updates the existing WordPress trademark and litigation evidence without promoting a dated procedural ruling into a separate claim. ## Synthesis additions (2026-08-11, software exit costs) - [[3. Resources/Permanent Notes/The Hard Part of Replacing SaaS Is Recovering Your Data]] — identifies data and workflow migration as the remaining exit constraint after AI makes feature rebuilding cheaper. ## Synthesis additions (2026-08-11, open-web experiments) - [[3. Resources/Readwise/Articles/demo.rss.chat]] — small RSS-based social interaction experiment retained as open-web implementation evidence, not promoted before broader adoption or durability is demonstrated. ## Synthesis pass — 2026-08-11 reference connections - [Quarterly Progress Report - Q2 2026](https://read.readwise.io/read/01ky561nqvfshbrdrqfwebgwr2) — PHP maintenance and WordPress compatibility work provide a dated portfolio-level governance reference; retained as source evidence rather than a new Permanent claim. - [What's Coming in WordPress 7.1](https://read.readwise.io/read/01kyhzpn22y2j1jammcja5hcgt) — a secondary release overview that points to Block API v2 compatibility and accessibility surfaces already covered by stronger release notes. - [Why WordPress 7.1 Will Improve Your Workflow](https://read.readwise.io/read/01kyj1abs6r5fdfra5kde1n5bq) — a secondary video overview connected as supporting release context rather than promoted into a duplicate atom. - [WordPress Lost Market Share and Got Stronger](https://read.readwise.io/read/01kyhyjtw6qfskc8pqtz6a7p4f) — preserves the GDP-versus-market-share framing as evidence in the ecosystem-governance cluster. - [Open source accessibility: What you're getting wrong](https://read.readwise.io/read/01kymtzdj7j35hghtaj6tn4kvc) — frames accessibility as a dependency and supply-chain responsibility across open-source projects. ## Synthesis pass — 2026-08-11 governance references - [Class Action Against Automattic to Proceed](https://read.readwise.io/read/01kymsbg7rgptrcf6hqq85s7sv) — dated litigation reporting retained as governance evidence rather than converted into a durable claim. - [Open and Async Work with Ben Balter](https://read.readwise.io/read/01kymtzdw38tr232h1e1xyv0y2) — connects durable decision URLs to transparent, asynchronous governance. - [This Week in WordPress 381](https://read.readwise.io/read/01kymtze44zwga9napkc16t5bh) — a weekly roundup preserving contemporaneous security, accessibility, and ecosystem framing as reference evidence. - [Behind the scenes of a punted feature of 7.1](https://read.readwise.io/read/01kyq669h755rgw9cm2v8jhfa2) — a primary contributor account of how uncertainty and testing evidence can justify punting a release feature. ## Synthesis pass — 2026-08-11 ecosystem references - [WP Engine Accuses Automattic of Destroying Evidence](https://read.readwise.io/read/01kyq6678j4dc4e1j137qanbfv) — dated litigation reporting retained as evidence about institutional accountability, not promoted into a durable claim. - [MCP 2026-07-28: the spec catches up with the static web](https://read.readwise.io/read/01kyq668yjc9exstz0smn3rm0y) — a protocol-governance reference covering stateless operation and a stated deprecation window. - [WP Engine Partners With BigCommerce Parent Commerce](https://read.readwise.io/read/01kyr1zetsse52qsnrz8aqse64) — preserves a dated example of WordPress vendors choosing which commerce layer to own or rent. - [WordPress 7.1 Beta 4 Adds Opt-Out for Responsive Styling](https://read.readwise.io/read/01kyskc81ckp6gahgmyf8kr538) — secondary release reporting connected to the primary account of the feature's scope and punt. - [Closing Remarks - KubeCon Japan 2026](https://read.readwise.io/read/01kyskbh23mvj5k5tgctcydhs5) — an event record with housekeeping only and no claim suitable for promotion. - [OpenTelemetry Celebrates Graduation and the Next Era of Agentic](https://read.readwise.io/read/01kyskb781fzfxz1wpktab3r7t) — foundation-sourced evidence about project graduation and emerging AI telemetry conventions. ## Synthesis pass — 2026-08-11 WordPress release references - [WordPress 7.1 is afoot, Gutenberg 23.6, iframed post editor, Abilities](https://read.readwise.io/read/01kyyny3wwt608p8h1vd716z1v) — a release roundup preserving compatibility, review-capacity, and contributor-workflow context. - [Why WordPress 7.1 Will Improve Your Workflow](https://read.readwise.io/read/01kyyrydjezacpjs36hsbc2see) — release-lead context for feature reversals, responsive styling, and collaborative-editing scope. - [This Week in WordPress 382](https://read.readwise.io/read/01kz6h78mapygqt8h028js6ss6) — a dated weekly ecosystem source retained for reference without duplicating stronger primary claims. ## Synthesis pass — 2026-08-11 WordPress implementation references - [WordPress 7.1 is coming. Are your custom blocks ready?](https://read.readwise.io/read/01kyytmk76jcqp2ajvjqnxsgh3) — a developer-facing compatibility warning for the always-iframed editor, retained as implementation evidence. - [Gutenberg Changelog #133](https://read.readwise.io/read/01kz1sas9xargyezdy934pfsc7) — a broad release record preserving contributor, accessibility, and review-capacity context without duplicating its many claims. - [Post list tables row headers changed](https://read.readwise.io/read/01kz6gr6ssxajpqpjbhfdgfcrc) — an official accessibility and compatibility reference for meaningful admin-table row headers. - [Introducing name and informational tool tips in WordPress 7.1](https://read.readwise.io/read/01kz6gbwhv1gnme6qfemnkv1s6) — an official component-accessibility reference where visible labels remain the default. - [Using WordPress Studio to speed up testing 7.1](https://read.readwise.io/read/01kz7rt7ggtrfq8qxej0w7zmp8) — a testing-workflow reference that keeps fixture generation distinct from independent result validation. ## Synthesis pass — 2026-08-11 API and ecosystem references - [JSON Schema preparation for client compatibility in WordPress 7.1](https://read.readwise.io/read/01kz6ggt6hp4aw8snd5bqd4gwg) — official reference for provider-neutral schema copies and client compatibility. - [Abilities API improvements in WordPress 7.1](https://read.readwise.io/read/01kz6gdjrgrajwtawyn5m5dk56) — official release evidence for invocation metadata and schema-driven client behavior. - [A unified public exposure flag for Abilities in WordPress 7.1](https://read.readwise.io/read/01kz6m79defek2sajbkdjbyp32) — documents that exposure intent remains separate from authorization and runtime checks. - [View Configuration Reference – Block Editor Handbook](https://read.readwise.io/read/01kz6m7ak0t181zejr1m19jndx) — developer reference for entity-scoped DataViews configuration and URL-managed state. - [Gutenberg is huge for a reason](https://read.readwise.io/read/01kz6m7c0208d5dse74q5q1xbb) — third-party architecture argument retained as a contestable alternative to universal editing scope. - [Miscellaneous Editor Changes in WordPress 7.1](https://read.readwise.io/read/01kz6m7cwckyqnc247wprsh2w3) — official compatibility and release-QA reference. - [PHP Alive And Kicking: Episode 34](https://read.readwise.io/read/01kz7vcmzqhwfw749mbj5bptqm) — recovered transcript covering PHP maintenance, deprecation, infrastructure succession, and contributor triage. ## Synthesis pass — 2026-08-11 release and governance references - [Automattic’s Anne McCarthy joins the PHP Foundation board](https://read.readwise.io/read/01kz90jamk459bpmadk8978dr6) — sponsor-representation evidence for the PHP–WordPress governance relationship. - [WordPress 7.1 Field Guide](https://read.readwise.io/read/01kz978fa2135vhbtaetjr4984) — official release overview connecting shipped scope, deferred work, and compatibility references. - [What’s the value of DataViews and who is it for?](https://read.readwise.io/read/01kz9fd33pzh94camedggrjmjz) — a product-governance argument about declarative contracts, migration costs, and a contestable foundation. - [WordPress 7.1 Release Candidate Phase](https://read.readwise.io/read/01kzc8xa9c5wkc0z7s5sagt5sw) — official evidence for double sign-off and hard string-freeze rules during release governance. ## Synthesis pass — 2026-08-11 automation and release references - [Automattbot](https://read.readwise.io/read/01kzc8xwr4retrwjwn86qxkt54) — a public-corpus persona-bot example retained for provenance, disclosure, and leadership-representation questions. - [How Cloudflare enforces engineering standards using AI](https://read.readwise.io/read/01kzc8y53g4r1316g7662kertn) — a software-governance case where written RFCs become review criteria for agents. - [WordPress 7.1 RC, 7.0.3 Security Release, Block Runner, New Playground](https://read.readwise.io/read/01kzgwr2mjeqejrxzjqxq77xhv) — an ecosystem digest retained as dated reference pending fuller source-specific analysis. ## Synthesis pass — 2026-08-11 final WordPress references - [An agent-first approach to Create Block Theme — wpnews.io teaser](https://read.readwise.io/read/01kzp118jzfgh42rfy543z93a5) — a link-aggregator stub retained only as a pointer to the separately captured primary article. - [An agent-first approach to Create Block Theme](https://read.readwise.io/read/01kzp0pkbd0dq8k4ygceb97zwb) — a primary account of WP-CLI block commands reconciling Site Editor state with theme files. - [Why WordPress Security Holds Up Against the Competition](https://read.readwise.io/read/01kzp0nrnthxfhqtvfcem5y6zc) — a WordPress security argument retained with its openness-versus-risk tradeoff and unsourced comparison claim clearly bounded. ## Synthesis additions (2026-08-13, spoliation-sanctions batch) The July–August 2026 docket batch (Dkts. 357–369) advances the litigation-tracking thread above from discovery disputes into the sanctions phase. WP Engine moved under Rule 37(e) to sanction Automattic/Mullenweg for spoliation of ephemeral messages (Dkt. 357, July 28); Defendants opposed on August 11 (Dkt. 369), arguing the imaging gap was a cured forensic-tooling limitation, not a preservation failure. Two Literature notes carry the substantive analysis; four companion filings (administrative motion to seal, renotice of hearing, transcript order, defendants' sealing statement) were procedural housekeeping with no independent analytical claim and were not separately promoted — see the run report for the per-filing resonance-filter reasoning. - [[3. Resources/Literature Notes/WPE v Automattic Dkt 357 — Motion for Sanctions for Spoliation - Literature Note]] — WPE's spoliation sanctions motion, built almost entirely from Defendants' own privilege log, letters, and court-ordered declarations. - [[3. Resources/Literature Notes/WPE v Automattic Dkt 369 — Defendants Opposition to Sanctions Motion - Literature Note]] — Defendants' answer: "collection is not preservation," with a forensic-tooling explanation (Cellebrite vs. iOS 18.4) for the imaging delay. - [[3. Resources/Permanent Notes/A Legal Hold Without Prompt Device Imaging Is Not Preservation]] — the generalizable records-management claim both filings' fact pattern turns on, regardless of who's right about intent. - Hearing: September 30, 2026, before Magistrate Judge Krishnan. ## Synthesis additions (2026-08-14 — contributor handoff) - [[3. Resources/Permanent Notes/A Contribution Pipeline Needs a Defined Next Step After Training]] — distinguishes initial onboarding from the post-training routing that turns prepared participants into returning contributors. ## Synthesis additions (2026-08-16 — batch synthesis pass) Note: [[3. Resources/Permanent Notes/Real Standards Adoption Means Implementing the Draft and Pushing the Gaps Upstream]] was proposed again from the OKF/ARD row below but is already registered above (2026-06-21) — not re-added. ### WCEU 2026 & release governance - [[3. Resources/Literature Notes/WordCamp Europe 2026 – My Key Takeaways]] — investment-framing angle on stewardship, distinct from the existing coerced-contribution notes. - [[3. Resources/Permanent Notes/Contribution Framed as Self-Interest Outlasts Contribution Framed as Charity]] — the companion claim from the same takeaways note. - [[3. Resources/Literature Notes/Roadmap to 7.1 (Make WordPress Core)]] — primary 23-section roadmap deep-read; the RTC architecture-vs-feature-set claim is deferred to the WCEU core-committers meeting note below. - [[3. Resources/Permanent Notes/A Shared Styling Primitive Lets One Mechanism Deliver Several Editor Features]] — the shared-primitive design claim from the 7.1 roadmap. - [[3. Resources/Literature Notes/WordPress 7.1 Roadmap Focuses on Collaboration (The Repository)]] — secondary coverage of the same roadmap; connects to rather than duplicates the RTC claim below. - [[3. Resources/Literature Notes/Core Committers Meeting – WordCamp Europe 2026]] — primary meeting recap and WP-cluster anchor for the Canary-channel governance decision. - [[3. Resources/Permanent Notes/WordPress Ships a Risky Feature's Architecture Into Core While Withholding the Full Feature Set]] — the RTC architecture-vs-feature-set claim from the primary committer meeting. - [[3. Resources/Literature Notes/Core Committers Float Chrome-Style Canary Approach for WordPress]] — secondary coverage of the same WCEU meeting. - [[3. Resources/Permanent Notes/An Experimental Release Channel Reshapes Project Governance Not Just Release Tooling]] — the release-channel-as-governance claim from the Canary coverage. - [[3. Resources/Literature Notes/Announcing the WordPress 7.1 Release Squad]] — procedural announcement of standing-team release coordination. - [[3. Resources/Permanent Notes/WordPress Delegates Release Coordination To Standing Team Reps]] — the generalizable governance pattern behind the release-squad structure. ### Code for the People documentary cluster - [[3. Resources/Literature Notes/Code for the People - Official Trailer (2026)]] — short trailer; single strong platform-fragility claim promoted. - [[3. Resources/Permanent Notes/Building on a Platform You Don't Control Is Renting Not Owning]] — the trailer's tenant/landlord claim. - [[3. Resources/Literature Notes/Automattic's 'Code for the People' Documentary Is a Rallying Cry for Users to Fight for the Open Internet]] — full deep-read, distinct piece from the trailer. - [[3. Resources/Permanent Notes/Advocacy Needs Disclosure When the Messenger Sells the Product]] — the messenger-conflict claim from the advocacy piece. - [[3. Resources/Literature Notes/Automattic Releases Code for the People (Repository)]] — trade-press coverage of the film's release, distinct from the trailer and the documentary itself. - [[3. Resources/Permanent Notes/Vendor-Funded Advocacy Inherits the Funder's Conflicts]] — the release-coverage claim. - [[3. Resources/Literature Notes/Code for the People - A Film by Bao Nguyen - Full Documentary]] — full 19.5-min documentary; the tenant/landlord claim is already captured by the trailer's permanent note above. - [[3. Resources/Permanent Notes/Open Scrutiny Functions as a Security Mechanism Not a PR Cost]] — the documentary's distinct open-scrutiny-as-security claim. ### Standards, core primitives & governance venues - [[3. Resources/Literature Notes/OKF and ARD, complementary by accident]] — standards-citizenship primary claim already linked to an existing permanent; a distinct media-type-fragmentation claim is promoted below. - [[3. Resources/Permanent Notes/An Unregistered Format Fragments Because Every Adopter Invents Their Own Name For It]] — the media-type-fragmentation claim distinct from the existing standards-citizenship note. - [[3. Resources/Literature Notes/Merge Proposal - Guidelines built on Knowledge]] — two distinct governance claims: the storage/intelligence boundary and the shared-primitive anti-fragmentation mechanism. - [[3. Resources/Permanent Notes/Shipping Storage Without Bundled Intelligence Keeps a Platform Vendor-Neutral]] — the storage/intelligence boundary claim. - [[3. Resources/Permanent Notes/A Shared Core Primitive Prevents Per-Plugin Storage Fragmentation]] — the shared-primitive anti-fragmentation claim. - [[3. Resources/Literature Notes/Proposal to Expand Abilities in WordPress 7.1 Draws Pushback]] — companion Literature Note for a design-shape claim already captured by an existing permanent; a new decision-venue-legitimacy claim is promoted below. - [[3. Resources/Permanent Notes/Decision-Venue Legitimacy Determines Whether Agreement Binds]] — the uncaptured venue-legitimacy claim from the Abilities pushback. ### Contributor pipeline, credit & education - [[3. Resources/Literature Notes/WordPress Contributor Dashboard - New Views, Custom Ladder, and More]] — connects to the existing pipeline and casual-contributor notes rather than duplicating them. - [[3. Resources/Permanent Notes/A Contribution Metric Should Let Each Team Define What Counts]] — the team-defined-metric claim from the dashboard update. - [[3. Resources/Literature Notes/WordPress Contributor Dashboard Gets Customizable Ladders for Make Teams in First Major Update Since Pilot Launch]] — rich deep-read of the same dashboard's first major update. - [[3. Resources/Permanent Notes/Team-Defined Contribution Metrics Beat One Fixed Yardstick]] — the generalized metrics claim from the ladder update. - [[3. Resources/Literature Notes/How WordPress Education Programs Are Growing (WP Tavern 222)]] — distinct source from the existing three-education-programs note. - [[3. Resources/Permanent Notes/Open Source Education Works as a Three-Stage Contribution Funnel]] — the funnel claim from the education-programs coverage. - [[3. Resources/Literature Notes/A Stronger Voice - What Membership Can Mean in Open Agentic AI]] — short source; generalizes past the existing narrower contribution-pipeline note. - [[3. Resources/Permanent Notes/Contribution Pathways Must Be Documented Not Left Emergent]] — the generalized documentation claim. - [[3. Resources/Literature Notes/WordPress Credits Team Proposes Graduate Retention Program, Launches Public Dashboard]] — links to the existing contribution-pipeline permanent rather than duplicating it. ### Litigation & accountability - [[3. Resources/Literature Notes/Automattic Wins Privilege Fight Over Pre-Lawsuit Trademark Strategy Slack Messages]] — full deep-read; the new permanent is a general litigation-strategy claim distinct from the existing BDFL-litigation notes. - [[3. Resources/Permanent Notes/Declining the One Argument a Judge Signals Decides the Case]] — the litigation-strategy claim. - [[3. Resources/Literature Notes/Class Action Against Automattic to Proceed After Judge Finds Company Tracked WP Engine Customers]] — both P1/P2 claims promoted, checked against existing notes. - [[3. Resources/Permanent Notes/Publishing a Competitive Artifact Publishes Evidence of Your Knowledge]] — first claim from the class-action ruling. - [[3. Resources/Permanent Notes/A Single Discretionary Update Channel Is a Security Dependency]] — second claim from the same ruling. - [[3. Resources/Literature Notes/WP Engine Accuses Automattic of Destroying Evidence]] — single strong cross-domain claim; source is otherwise litigation-status reporting. - [[3. Resources/Permanent Notes/Governance in Ephemeral Channels Is Unauditable by Construction]] — the ephemeral-channel auditability claim. - [[3. Resources/Literature Notes/WP Engine Opposes WordPress Foundation's Trademark Bids in the U.S. and Canada, Alleging Fraud and Bad Faith]] — ported from an existing deep-read. - [[3. Resources/Permanent Notes/Trademarking Generic Terms Invites Ecosystem Capture]] — the trademark-capture claim. - [[3. Resources/Literature Notes/WPE v Automattic Dkt 358 — Admin Motion to Seal - Literature Note]] — full deep-read, Refactor Appendix present. - [[3. Resources/Permanent Notes/A Sealing Chart Maps Evidence Before Anything Is Unsealed]] — the sealing-chart claim. - [[3. Resources/Literature Notes/WPE v Automattic Dkt 360 — Renotice of Hearing - Literature Note]] — procedural filing with a genuine magistrate-referral-signaling claim. - [[3. Resources/Permanent Notes/A Same-Day Magistrate Referral Classifies a Motion Before Briefing]] — the referral-signaling claim. - [[3. Resources/Literature Notes/WPE v Automattic Dkt 362 — Transcript Order - Literature Note]] — thinnest docket filing in the batch; still a real records-research claim. - [[3. Resources/Permanent Notes/Flattened Court Form PDFs Lose Their Answers to Text Extraction]] — the records-research claim. - [[3. Resources/Literature Notes/WPE v Automattic Dkt 368 — Defendants' Statement on Sealing - Literature Note]] — densest docket filing in the batch (5 Literature atoms, 1 Permanent candidate). - [[3. Resources/Permanent Notes/What a Party Consents to Unseal Maps Where It Thinks It Can Win]] — the consent-to-unseal claim. ### Security & supply chain - [[3. Resources/Literature Notes/Plugin Security Will Sink WordPress]] — full deep-read; its P1 candidate already exists as an existing extensibility-liability permanent, linked not duplicated. - [[3. Resources/Literature Notes/WP2Shell Coordination Was Part of the Protection]] — rich full deep-read with verbatim quotes. - [[3. Resources/Permanent Notes/Security Coordination Is Infrastructure That Degrades Without Maintenance]] — the coordination-as-infrastructure claim. - [[3. Resources/Literature Notes/Governance Guardrails plugin v1 (Malcolm Peralty)]] — full deep-read ported; the config-as-code mechanism is promoted below. - [[3. Resources/Permanent Notes/File-Based Configuration Lets Governance Policy Travel With the Codebase]] — the config-as-code governance claim. - [[3. Resources/Literature Notes/An Open Letter to WordPress.org It's Time to Make Security a Core Feature]] — no new permanent; its strongest claim already lives in an existing compatibility-first-culture permanent that sources this exact article. - [[3. Resources/Literature Notes/When WPForms Had a Real Bug — Arbitrary File Access]] — thin follow-up thread; the permanent strips unverified named-individual allegations to keep only the structural claim. - [[3. Resources/Permanent Notes/A Volunteer Label Does Not Remove a Sponsorship Conflict]] — the structural conflict-of-interest claim. - [[3. Resources/Literature Notes/What Visibility Do You Have When Releasing a Plugin Directly on GitHub]] — full deep-read ported; linked to the existing absence-of-detection note. - [[3. Resources/Permanent Notes/A Distribution Metrics Silence Reflects the Channel Not the Usage]] — the distribution-silence claim. - [[3. Resources/Literature Notes/Vulnerability Response for Large OSS Projects -- Grafana]] — real CVSS-9.4 account-takeover walked end to end. - [[3. Resources/Permanent Notes/A Vulnerabilitys Classification Follows the Threat Model Not the Reports Novelty]] — the classification claim. - [[3. Resources/Literature Notes/Open Channels FM, August 10, 2026]] — AISI cyber-range evaluation where an agent fabricated a full contributor trust chain. - [[3. Resources/Permanent Notes/AI Agents Can Fabricate Every Trust Signal Code Review Relies On]] — the fabricated-trust-chain claim. ### AI, agents & contribution risk - [[3. Resources/Literature Notes/Back and Forth — AI as a Communication Device in WordPress Contribution]] — rich deep-read (Anne McCarthy / nomad.blog). - [[3. Resources/Permanent Notes/AI Prototypes Communicate Intent Better Than Competing Pull Requests]] — the prototype-as-communication claim. - [[3. Resources/Permanent Notes/Working Locally With No-Push Intent Limits AI Contribution Risk]] — the no-push-intent governance claim. - [[3. Resources/Literature Notes/Anthropic's War on Opensource AI]] — no new permanent; both strongest claims already covered by existing permanents, linked instead. - [[3. Resources/Literature Notes/UnblockWP Features]] — vendor marketing page treated as product-claims analysis. - [[3. Resources/Permanent Notes/BYO-Key AI Connectors Keep Governance and Cost With the Site Owner]] — the BYO-key governance claim. - [[3. Resources/Literature Notes/Agentrification (Scott Logic)]] — rich deep-read; its custodian-trap P1 already exists as an existing permanent, linked not duplicated. - [[3. Resources/Permanent Notes/Tooling Chosen for Status Rather Than Utility Is a Cost]] — the status-driven-tooling claim (its P2). - [[3. Resources/Literature Notes/Stop the SaaS Trap - How to Use FOSS and AI to Build Custom Software You Actually Own]] — linked to the existing self-hosting-liability counterweight note. - [[3. Resources/Permanent Notes/AI Shifts the Advantage From Generating Code to Adapting It]] — the code-adaptation-advantage claim. - [[3. Resources/Permanent Notes/Control Over Your Own AI Adoption Timeline Is Now a Reason to Self-Host]] — the adoption-timeline claim. - [[3. Resources/Literature Notes/AI-coding agents kill team collaboration]] — links to the existing self-review-collapse and Goodhart's-Law permanents. - [[3. Resources/Permanent Notes/Tool Access Does Not Aggregate Into Team Capability]] — the tool-access-vs-capability claim. - [[3. Resources/Literature Notes/How I use Agents to Extract Hidden Feedback from Github and Improved Rector]] — rich deep-read ported into Konik format. - [[3. Resources/Permanent Notes/Narrow Agent Prompts Beat Broad Exploratory Ones Once the Task Is Named]] — the narrow-prompting claim. ### Maintenance, funding & PHP ecosystem - [[3. Resources/Literature Notes/Quarterly Progress Report - Q2 2026 (PHP Foundation)]] — PHP Foundation report, highly relevant to WordPress's runtime dependency chain. - [[3. Resources/Permanent Notes/Maintenance Visibility Functions as Funding Infrastructure]] — the visibility-as-funding claim. - [[3. Resources/Literature Notes/The PHP Podcast 2026.07.23]] — ported from an existing pipeline deep-read. - [[3. Resources/Permanent Notes/Faster Implementation Raises the Value of Review and Release Controls]] — the faster-implementation claim. - [[3. Resources/Literature Notes/The PHP Podcast 2026.07.30]] — Literature Note gap-fill; connects two existing permanents plus one new. - [[3. Resources/Permanent Notes/Ecosystem Gravity Retains Developers Better Than Feature Parity]] — the ecosystem-gravity claim. - [[3. Resources/Literature Notes/Automattic’s Anne McCarthy joins the PHP Foundation board]] — sponsor-representation evidence for the PHP-WordPress governance relationship. - [[3. Resources/Permanent Notes/Sponsor Funding and Governance Influence Require Separate Accounting]] — the funding/influence-separation claim. - [[3. Resources/Literature Notes/Sustain Episode 292 — Vlad-Stefan Harbuz - Launching the Software Stewardship Lab]] — the funding-recursion claim already captured by an existing permanent; two distinct new claims promoted. - [[3. Resources/Permanent Notes/Compiled Dependencies Are Invisible to Manifest-Based Analysis]] — the compiled-dependency-visibility claim. - [[3. Resources/Permanent Notes/A Recognition Threshold Forces a Choice Between Dilution and Exclusion]] — the recognition-threshold claim. - [[3. Resources/Literature Notes/PHP Alive and Kicking Episode 34 — Derick Rethans]] — rich source on triage, deprecation governance, and contributor succession. - [[3. Resources/Permanent Notes/A Growing Categorized Issue Queue Measures Triage Capacity Not Just Backlog]] — the triage-capacity claim. - [[3. Resources/Permanent Notes/A Deprecation Needs Adoption Evidence Before It Transfers Migration Cost]] — the deprecation-evidence claim. - [[3. Resources/Literature Notes/Leaner, steadier PHPUnit runs for upcoming releases]] — linked to the existing maintenance-visibility and prevented-work permanents. - [[3. Resources/Permanent Notes/Cut Redundant CI Combinations Before Weakening a Coverage Contract]] — the CI-reduction claim. - [[3. Resources/Literature Notes/Arch under attack, Framework 13 Pro, GOG on Linux - Linux Weekly News]] — full deep-read; H1 candidate already promoted in a prior pass, linked not duplicated. - [[3. Resources/Permanent Notes/Ownership Transfer Is the Soft Point in Package Distribution]] — the ownership-transfer claim (H2). - [[3. Resources/Literature Notes/WordPress Community Support Recorded a $372,000 Deficit in 2025]] — the donated-labor claim already captured by an existing permanent; a new attendance-vs-funding claim is promoted. - [[3. Resources/Permanent Notes/Attendance Growth Is Not Community-Funding Health]] — the attendance-vs-funding claim. - [[3. Resources/Literature Notes/Something Is Wrong With the WordPress.org Popular Themes List]] — a permanent from this exact source already exists, linked not duplicated. ### WordPress 7.1 core development notes - [[3. Resources/Literature Notes/What's New for Developers (July 2026)]] — links to the existing Classic-block deprecation and default-off-flags permanents. - [[3. Resources/Permanent Notes/Forced UX Removal Gets Reverted Under Visible Pushback]] — the forced-removal-reversal claim. - [[3. Resources/Literature Notes/Hiding the Classic Block From the Inserter in WordPress 7.1]] — a default-hidden, filter-reversible deprecation path. - [[3. Resources/Permanent Notes/Hiding Not Removing Deprecates a Legacy Feature Safely]] — the hide-not-remove claim. - [[3. Resources/Literature Notes/New Block Support in WordPress 7.1 Background Gradient]] — CSS-architecture core dev note. - [[3. Resources/Permanent Notes/A Convenient Abstraction That Silently Discards State Is a Bug Factory]] — the abstraction-discards-state claim. - [[3. Resources/Literature Notes/What's Coming in WordPress 7.1]] — closest topical MOC home for a core feature preview. - [[3. Resources/Permanent Notes/Lowering the Barrier to a Control Lowers It in Both Directions]] — the barrier-symmetry claim. - [[3. Resources/Literature Notes/WordPress 7.1 is afoot, Gutenberg 23.6, iframed post editor, Abilities API, Studio Code and more - Weekend Edition 371]] — key actionable item: the forced iframed post editor lands 19 August with no opt-out. - [[3. Resources/Permanent Notes/Removing the Opt-Out Converts a Deprecation Into a Deadline]] — the no-opt-out claim. - [[3. Resources/Permanent Notes/An Agent Defaults to the Corpus-Prevalent Pattern Not the Currently Recommended One]] — the corpus-prevalence claim. - [[3. Resources/Literature Notes/WordPress 7.1 Release Candidate Phase]] — official evidence for double sign-off and hard string-freeze rules. - [[3. Resources/Permanent Notes/A Release Milestone Is Contributor Triage Training]] — the RC-as-triage-training claim. - [[3. Resources/Literature Notes/WordPress 7.1 Accessibility Change May Break Some Plugins]] — secondary reporting on the same Trac change as the row-headers note below; a new vibe-coding-audit claim is promoted. - [[3. Resources/Permanent Notes/AI-Generated Code Creates Maintainers Who Cannot Audit Their Own Breaking-Change Exposure]] — the audit-blind-spot claim. - [[3. Resources/Literature Notes/Post List Tables Row Headers Changed (WordPress 7.1)]] — official accessibility/compatibility reference. - [[3. Resources/Permanent Notes/Semantic Identities Outlast Structural Selectors]] — the semantic-identity claim. - [[3. Resources/Literature Notes/Introducing Name and Informational Tool Tips in WordPress 7.1]] — official component-accessibility reference. - [[3. Resources/Permanent Notes/Visible Interface Text Beats Hover-Dependent Explanation]] — the visible-text claim. - [[3. Resources/Literature Notes/JSON Schema Preparation for Client Compatibility in WordPress 7.1]] — official reference for provider-neutral schema copies. - [[3. Resources/Permanent Notes/Client Contracts Are Prepared at Output Boundaries]] — the output-boundary claim. - [[3. Resources/Literature Notes/Abilities API Improvements in WordPress 7.1]] — an older deep-read format required a full raw-field read to locate. - [[3. Resources/Permanent Notes/Early Observability Hooks Trade Completeness for Exposure Risk]] — the observability-tradeoff claim. - [[3. Resources/Literature Notes/View Configuration Reference (Block Editor Handbook)]] — full deep-read with Refactor Appendix and Template Library. - [[3. Resources/Permanent Notes/Server Defaults and Active Navigation State Need Separate Owners]] — the state-ownership claim. - [[3. Resources/Permanent Notes/Stable Identities Make Configuration Patches Mergeable]] — the stable-identity claim. - [[3. Resources/Literature Notes/Gutenberg Is Huge for a Reason]] — third-party architecture essay; author has a commercial interest, flagged in the note. - [[3. Resources/Permanent Notes/Preservation Compatibility Differs From Editing Parity]] — the preservation-vs-parity claim. - [[3. Resources/Permanent Notes/A Never-Build List Protects Product Identity]] — the never-build-list claim. - [[3. Resources/Literature Notes/Miscellaneous Editor Changes in WordPress 7.1]] — only 1 of 2 candidates promoted; the second overlaps existing source-reading reasoning. - [[3. Resources/Permanent Notes/Compatibility Guidance Should Name the Observable Edge That Can Still Change]] — the compatibility-guidance claim. - [[3. Resources/Literature Notes/Rethinking do_action() - Events as Objects, Hooks as Class Names]] — Literature Note gap-fill for the existing event-name-durability permanent; one additional new claim promoted. - [[3. Resources/Permanent Notes/Structured Payloads Improve Extension-Point Legibility]] — the structured-payload claim. - [[3. Resources/Literature Notes/Using WordPress Studio to speed up testing 7.1]] — rich deep-read with a clear Atomic Split Pad. - [[3. Resources/Permanent Notes/Generated Test Fixtures Are Not Evidence Until Independently Validated]] — the fixture-validation claim. - [[3. Resources/Permanent Notes/Real-Use Testing and Constructed Fixtures Catch Different Bug Classes]] — the testing-coverage claim. - [[3. Resources/Literature Notes/What’s the value of DataViews and who is it for?]] — architecture piece from the WooCommerce dev blog. - [[3. Resources/Permanent Notes/A Shared Field Schema Replaces Four Separate Implementations]] — the shared-schema claim. - [[3. Resources/Permanent Notes/Registered Extension Points Reduce Markup Coupling]] — the extension-point claim. - [[3. Resources/Literature Notes/Design System Theming in WordPress 7.1]] — full 18-section deep-read with Refactor Appendix. - [[3. Resources/Permanent Notes/Disclosing a Limit Without a Verification Path Transfers Responsibility]] — the disclosed-limit claim. ### Business, marketplace & economics of OSS - [[3. Resources/Literature Notes/Cursor Quietly Acquires Continue, an Open-Source Alternative to GitHub Copilot]] — rich existing deep-read ported. - [[3. Resources/Permanent Notes/Permissive Licensing Preserves the Code Not the Product]] — the licensing-vs-product claim. - [[3. Resources/Literature Notes/Elementor Cuts 30% of Its Workforce, Frames Layoffs as AI-Driven Reset]] — Refactor Appendix present. - [[3. Resources/Permanent Notes/"AI Reset" Framing Often Masks A Margin-Driven Cut]] — the reframing claim. - [[3. Resources/Literature Notes/Pull Requests Are for Humans]] — rich existing deep-read. - [[3. Resources/Permanent Notes/Automating Both Ends Of A Review Collapses Its Value]] — the self-review-collapse claim. - [[3. Resources/Literature Notes/The State of WordPress Themes Report Reveals a Gap Between Block Theme Development and Adoption]] — data-dense source, 4 claim atoms. - [[3. Resources/Permanent Notes/Technology Availability Precedes User Adoption By Years]] — the availability-vs-adoption-lag claim. - [[3. Resources/Literature Notes/A Complete Guide to Enterprise Website Redesign]] — ported from an existing deep-read notes field. - [[3. Resources/Permanent Notes/Phase Gate Governance Converts Diffuse Redesign Risk Into Checkpoints]] — the phase-gate claim. - [[3. Resources/Literature Notes/The Enterprise WordPress Playbook]] — vendor whitepaper (Human Made); critiques its own Build/Buy/Evolve framework. - [[3. Resources/Permanent Notes/A Vendor-Defined Decision Framework Predetermines Its Own Winner]] — the framework-bias claim. - [[3. Resources/Literature Notes/WP Engine Partners With BigCommerce Parent Commerce to Launch Ecommerce Platform for High-Growth Merchants]] — rich deep-read with Refactor Appendix. - [[3. Resources/Permanent Notes/Independence Is Decided Per Layer Not Per Stack]] — the layer-independence claim. - [[3. Resources/Permanent Notes/Editorial Depth Becomes a Discovery Moat as LLMs Mediate Search]] — the editorial-moat claim. - [[3. Resources/Literature Notes/Enterprise WordPress Security Is Really About Decision Making]] — short evidence-free agency-marketing essay; capped at 1 candidate. - [[3. Resources/Permanent Notes/Risk Concentrates at the Boundaries Between Correct Decisions]] — the decision-boundary claim. - [[3. Resources/Literature Notes/Should You Sell on the WooCommerce Marketplace - A View From Both Sides]] — candid platform-operator-plus-vendor panel. - [[3. Resources/Permanent Notes/A Marketplace Fee Bundles Uncounted Services Beyond Distribution]] — the marketplace-fee claim. - [[3. Resources/Permanent Notes/Structural Distance From the Customer Weakens a Vendors Feedback Signal]] — the feedback-distance claim. - [[3. Resources/Literature Notes/Maintaining over Building (Brian Coords - Woo)]] — primary claim already had a permanent; a new install-base/caution claim is added. - [[3. Resources/Permanent Notes/Caution Scales With Install Base Not Timidity]] — the install-base-caution claim. ### Community, culture & advocacy - [[3. Resources/Literature Notes/The Checklist That Keeps Open Source Projects Alive]] — category=video, filed under the Podcasts folder. - [[3. Resources/Permanent Notes/Ego Is the First Blocker to Opening a Project for Outside Feedback]] — the ego-blocker claim. - [[3. Resources/Permanent Notes/Consistent Reply Timelines Build Trust More Than Fast Ones]] — the reply-timeline claim. - [[3. Resources/Literature Notes/The Spirit of Open Source Penpot's Recipe of Ambassador Program]] — both P1/P2 promoted. - [[3. Resources/Permanent Notes/A Shared Artifact Outlasts the Activity That Produced It]] — the shared-artifact claim. - [[3. Resources/Permanent Notes/Not Yet Knowing the Topic Makes a Better Advocate Than Expertise]] — the non-expert-advocate claim. - [[3. Resources/Literature Notes/Om Malik obituary (The Repository)]] — tribute/obituary, scaled to fewer atoms. - [[3. Resources/Permanent Notes/Open-Source History Is Carried by Connectors Not Just Code]] — the connector-history claim. - [[3. Resources/Literature Notes/Why It Took Me 16 Years to Contribute to WordPress]] — rich deep-read ported into Konik format. - [[3. Resources/Permanent Notes/Event Discovery Without Onboarding Produces False Mental Models]] — the false-mental-model claim. - [[3. Resources/Permanent Notes/Mentorship Capacity Is Retention Infrastructure Not Volunteer Bonus]] — the mentorship-capacity claim. - [[3. Resources/Literature Notes/Perspectives With Josepha Haden Chomphosy (Crossword S11E10)]] — rich deep-read; the public-toilets claim already lives in an existing maintenance-prestige permanent. - [[3. Resources/Permanent Notes/Optimize for Invariant Preferences When the Future Is Unpredictable]] — the invariant-preferences claim. - [[3. Resources/Permanent Notes/The Authority Collecting Feedback Distorts the Feedback It Collects]] — the feedback-distortion claim. - [[3. Resources/Permanent Notes/Interview Format Determines Which Questions Are Askable]] — the interview-format claim. - [[3. Resources/Literature Notes/Milana Cap on WordCamp Belgrade, Documentation Tooling, and Open Source Sponsorship]] — full Refactor-Appendix deep-read. - [[3. Resources/Permanent Notes/Schedule Design Is a Volunteer-Welfare Lever Not Just an Attendee One]] — the schedule-as-welfare-lever claim. - [[3. Resources/Permanent Notes/AI Documentation Pipelines Need an Explicit Authority Source]] — the documentation-authority claim. - [[3. Resources/Literature Notes/Akrites Explained Open Source's New Emergency Team]] — full deep-read ported. - [[3. Resources/Permanent Notes/Neutral Governance Converts Rivalry Into Shared Infrastructure]] — the neutral-governance claim. - [[3. Resources/Literature Notes/Where was Mythos when WordPress fell]] — five permanents from a prior pass reconnected; one new missing-baseline claim. - [[3. Resources/Permanent Notes/A Verified Fraction Without a Comparison Baseline Cannot Be Scored]] — the baseline claim. ### Open web & network openness - [[3. Resources/Literature Notes/Can RSS be a social network (Dave Winer)]] — network-level openness claim, checked against the existing lock-in notes. - [[3. Resources/Permanent Notes/A Network Is Open Only When Its Parts Are Independently Replaceable]] — the network-openness claim. - [[3. Resources/Literature Notes/demo.rss.chat]] — full 18/23-section deep-read with Refactor Appendix. - [[3. Resources/Permanent Notes/Small Trusted Networks Substitute Social Trust For Formal Moderation]] — the trust-substitution claim. - [[3. Resources/Permanent Notes/A Challenger Can Invite The Incumbent To Connect Not Compete]] — the challenger-invitation claim. - [[3. Resources/Literature Notes/This Week in WordPress 380]] — full deep-read with Refactor Appendix. - [[3. Resources/Permanent Notes/A Plugins Survival Requires Owning Distribution Beyond the Repo]] — the distribution-ownership claim. - [[3. Resources/Permanent Notes/Donated Staff Salary Accounting Obscures a For-Profits Labor Subsidy]] — the labor-subsidy claim. ### Cloud native, CNCF & KubeCon batch - [[3. Resources/Literature Notes/Out of the Box, at Multi-Region Scale — How Hyundai Scales Its Platform]] — KubeCon Japan lightning talk. - [[3. Resources/Permanent Notes/Pre-Position the Artifact Rather Than Optimizing the Fetch]] — the artifact-pre-positioning claim. - [[3. Resources/Literature Notes/OpenTelemetry Celebrates Graduation and the Next Era of Agentic]] — CNCF graduation keynote. - [[3. Resources/Permanent Notes/Standards Win When Re-Instrumentation Is the Expensive Part]] — the standards-adoption claim. - [[3. Resources/Permanent Notes/Diagnose by Question Not by Data Type]] — the diagnostic-framing claim. - [[3. Resources/Literature Notes/How Subaru Accelerated AI Model Development for EyeSight]] — KubeCon Japan case study, linked to the sibling Hyundai note. - [[3. Resources/Permanent Notes/Artifact Distance Dominates Transfer Time at Large Sizes]] — the artifact-distance claim. - [[3. Resources/Literature Notes/Large-Scale Edge Management with Kubernetes (PowerX)]] — rich existing deep-read (18-section notes, Refactor Appendix). - [[3. Resources/Permanent Notes/Vary Where the Agent Runs Not Whether It Runs]] — the collector-placement claim. - [[3. Resources/Literature Notes/How CNCF Projects United Two Countries' Engineers (NTT-SK Telecom)]] — rich deep-read ported. - [[3. Resources/Permanent Notes/A Shared Technical Vocabulary Removes the Need for a Mediating Party]] — the shared-vocabulary claim. - [[3. Resources/Literature Notes/Building a Multi-Tenant AI Platform with the CNCF Ecosystem]] — permanent already existed; the Literature Note was missing. - [[3. Resources/Permanent Notes/Adopting an Ecosystem Component Inherits Its Maintenance Risk]] — the new archived-dependency counterexample. - [[3. Resources/Literature Notes/Where Will Cloud Native Take You]] — two new permanents from the Andy Weir/Martian analogy and the disposition-matched on-ramp design. - [[3. Resources/Permanent Notes/A Contributor's Value Is Expertise the Maintainer Lacks]] — the contributor-value claim. - [[3. Resources/Permanent Notes/Communities With One Entry Path Recruit Only One Temperament]] — the entry-path claim. - [[3. Resources/Literature Notes/Introducing BoardScribe - Accessible Board Meeting Minutes for WordPress]] — no verbatim transcript available, provenance limitation flagged. - [[3. Resources/Permanent Notes/An Accessible Interface Wrapping Inaccessible Content Relocates the Barrier]] — the accessibility-relocation claim. - [[3. Resources/Literature Notes/Beyond Pull Requests - Quantifying the ROI of InnerSource]] — speaker/company names unreliable in the auto-transcript, flagged. - [[3. Resources/Permanent Notes/A Delivery-Throughput Metric Cannot See Whether Knowledge Spread]] — the throughput-metric claim. - [[3. Resources/Literature Notes/OCI Is Not Git -- Rethinking GitOps Source of Truth]] — strong cross-domain claim flagged as recurring across the same conference batch. - [[3. Resources/Permanent Notes/A Patterns Formal Rules and Its Actual Value Can Diverge]] — the formal-vs-actual-value claim. - [[3. Resources/Literature Notes/SBOMit - Making SBOMs Accurate With Attestations]] — rich 18-section deep-read. - [[3. Resources/Permanent Notes/More Detections Are Not the Same Claim as More Accurate]] — the detection-vs-accuracy claim. - [[3. Resources/Literature Notes/Leading Tech Firms Unite to Form Open Source Secure AI Alliance]] — thin source, density gate overridden to 2 atoms. - [[3. Resources/Permanent Notes/Who Joins a Standards Coalition Tells You What It Can Actually Govern]] — the coalition-membership claim. ### Linux desktop ecosystem - [[3. Resources/Literature Notes/Big changes coming to KDE & GNOME, tons of apps & services getting Linux clients]] — full deep-read with Refactor Appendix (H1-H5 atoms). - [[3. Resources/Permanent Notes/Official Vendor Linux Clients Function as Legitimacy Signals]] — the legitimacy-signal claim. - [[3. Resources/Permanent Notes/GPU-Accelerated VMs Can Substitute for Native Linux Ports]] — the substitution claim. ## Synthesis additions (2026-08-16 — Xdebug tooling reputation) - [[3. Resources/Literature Notes/Debug WordPress Like a Pro (Xdebug with WordPress Studio)]] — WordPress Studio's bundled Xdebug setup as the primary evidence behind the difficulty-reputation permanent below. - [[3. Resources/Permanent Notes/A Tool's Difficulty Reputation Outlives the Difficulty]] — a tool's hard-to-configure reputation persists after the friction is fixed because it's corrected socially, word of mouth, not by documentation. ## Synthesis additions (2026-08-16 — second batch) ### This Week in WordPress roundups - [[3. Resources/Literature Notes/This Week in WordPress 376]] — multi-topic podcast roundup with a full existing deep-read; two deep-read permanent candidates duplicated existing notes from other sources (Anthropic export ban, CDN attack) and were linked instead, two genuinely uncaptured claims promoted below. - [[3. Resources/Permanent Notes/An Undefined Legal Category Sweeps In Whatever Technically Fits Its Words]] — the undefined-'social media'-legislation risk claim from TWiWP #376. - [[3. Resources/Permanent Notes/A Multi-Year Migrations Technical Rationale Can Expire Before The Migration Does]] — the CERN/Drupal migration-rationale-decay claim from TWiWP #376. - [[3. Resources/Literature Notes/'How the sausage is made' - This Week in WordPress 378]] — its P2 (velocity-vs-safety carve-out for the 24-hour update delay) overlaps an existing timed-review-window permanent from a different source and was linked, not duplicated; P1 promoted below. - [[3. Resources/Permanent Notes/Platform Sustainability Is a Sum of Independent Pressures Not One Cause]] — the multi-causal-decline claim from TWiWP 378. ### WordPress 7.1 release leadership & development - [[3. Resources/Literature Notes/Anne McCarthy Named WordPress 7.1 Release Lead]] — ported from an existing full deep-read (Refactor Appendix present); the leadership-continuity observation is flagged by the source's own analysis as not-yet-durable (n=2). - [[3. Resources/Permanent Notes/A Major WordPress Release Can Ship Without Mullenweg as Lead]] — the narrowly-scoped leadership-continuity claim, created to reflect that hedge rather than skip the observation. - [[3. Resources/Literature Notes/Contributors Call for Testing Responsive Styling Ahead of WordPress 7.1]] — full deep-read; distinct from the existing shared-styling-primitive permanent, which covers the engineering mechanism rather than the authoring workflow. - [[3. Resources/Permanent Notes/Native Per-Breakpoint Styling Moves Responsive Work Into the Inspector]] — the authoring-workflow claim, cross-linked to [[3. Resources/Permanent Notes/A Shared Styling Primitive Lets One Mechanism Deliver Several Editor Features]]. - [[3. Resources/Literature Notes/WordPress Drops to 41.5% Market Share]] — full deep-read; all three candidate Permanent claims were already promoted in a prior pass, cross-linked here without new Permanents. ### FAIR, portability & governance venues - [[3. Resources/Literature Notes/Community + Code Episode 28 - Carrie Dils]] — rich full deep-read (FAIR/TYPO3/composer); two of four Literature atoms already generalized by existing permanents (Zet · FAIR scales federated WordPress distribution; Portability Is Proven by a Second Implementer), so only the two genuinely uncaptured claims below were promoted. - [[3. Resources/Permanent Notes/Teaching a Concept Cements Understanding Better Than Consuming It]] — the teaching-as-learning claim. - [[3. Resources/Permanent Notes/A Site Owner Should Never Be Forced to Become a Developer]] — the don't-force-site-owner-to-become-developer claim. - [[3. Resources/Literature Notes/Proposal - Restructure the Community Team Handbooks]] — full deep-read, including a strong comment thread treated as first-class evidence per the source's own framing. - [[3. Resources/Permanent Notes/Documentation Restructure Decides Deduplication at Audit Not After]] — the deduplication-timing claim. ### Security & supply-chain governance - [[3. Resources/Literature Notes/OpenJS Security Working Group - June 22, 2026]] — full deep-read on the OpenJS CNA API proof-of-concept; both claims genuinely new, no existing permanent covers this specific delegation mechanism. - [[3. Resources/Permanent Notes/Delegated Authority Scales When Coordination Stays Central]] — the delegation-pattern claim. - [[3. Resources/Permanent Notes/Scoped Reservation Visibility Prevents Cross-Project Disclosure Leakage]] — the bucket-scoping claim. - [[3. Resources/Literature Notes/Everyone Signed This Letter (...minus Anthropic)]] — no Literature Note existed despite a rich 18-section deep-read (Refactor Appendix present); the source's central claim (request-level filters burden defenders) already lives in an existing permanent and was linked, not duplicated. - [[3. Resources/Permanent Notes/Capability Diffusion Helps Attackers or Defenders Depending on Remediation Speed]] — the domain-specific (software security vs. biosecurity) attacker/defender-advantage claim, the genuinely distinct claim from this source. ### Litigation & accountability - [[3. Resources/Literature Notes/Automattic Fires Back at WP Engine's Sanctions Motion]] — rich existing deep-read (Refactor Appendix with Literature/Atomic Split Pads); companion news article to the existing WPE v Automattic Dkt 369 primary-source note. The collection-vs-preservation claim was already captured by [[3. Resources/Permanent Notes/A Legal Hold Without Prompt Device Imaging Is Not Preservation]], so only the novel circumstantial-evidence claim was promoted. - [[3. Resources/Permanent Notes/A Public Contact Invitation Does Not Prove Case-Relevant Use]] — the circumstantial-evidence claim. ### Platform transparency - [[3. Resources/Literature Notes/X Open Sources Its Ranking Algorithm]] — TechCrunch coverage of X's expanded ranking-algorithm open-source release and shadowban-check tool. - [[3. Resources/Permanent Notes/Algorithmic Transparency and Corporate Disclosure Move on Separate Axes]] — the code-level-vs-corporate-transparency claim promoted from this source. ## Synthesis additions (2026-08-17, CHAOSS MCP) - [[3. Resources/Literature Notes/MCP Server With CHAOSS Metrics CHAOSS AI Alignment WG - June 22]] — MCP as a trust boundary for grounding LLMs in sourced CHAOSS metrics rather than priors; its harness-over-model-size candidate claim already covered by two existing permanents, linked as a second independent anecdote. ## Synthesis additions (2026-08-18, sanctions-motion secondary coverage) - [[3. Resources/Literature Notes/Automattic Pushes Back on WP Engine's Sanctions Over Allegedly Missing Messages]] — secondary journalism on the same August 11, 2026 opposition filing this MOC's existing WPE v Automattic Dkt 369 primary-source note already covers in full; no new permanent, connected to [[3. Resources/Permanent Notes/A Legal Hold Without Prompt Device Imaging Is Not Preservation]] instead. ## Synthesis additions (2026-08-28 — horizontal functions and unwritten state) Four notes on how work lands with people who can see a problem but cannot fix its source, and on what coordination roles actually run on. The WordPress 7.1 release material grounds the second half. - [[3. Resources/Permanent Notes/A Reliable Cleanup Crew Removes the Reason to Stop Making the Mess]] — the volunteer version is sharper than the employed one: the cleanup crew is unpaid, and the authority to prevent sits with a body that does not pay for the cleanup. - [[3. Resources/Permanent Notes/Decomposing a Capability Gap Into Tickets Makes It Closeable and Permanent]] — reading an issue tracker as a statement about missing capability rather than about user demand. Extends [[3. Resources/Permanent Notes/A Growing Categorized Issue Queue Measures Triage Capacity Not Just Backlog]] from queue size to queue composition. - [[3. Resources/Permanent Notes/A Capability Transfer Is Proven by Absence Not by a Handoff]] — the bus-factor question restated as a test rather than a count of names. A documented handoff and a dependency in a nicer outfit are indistinguishable until someone is gone for a full cycle. - [[3. Resources/Permanent Notes/Coordination Work Bottoms Out on State That Was Never Written Down]] — Krupa Nanda on the 7.1 Release Coordinator role. A checklist is a list of steps; a release is a list of people, and ownership, availability, and readiness are properties no step-list carries. ## Synthesis additions (2026-08-28b — the 7.1 decision log, read as primary) Anne McCarthy published a dated log of ~18 release-lead decisions two days after 7.1 shipped. Read as the primary source rather than through The Repository's summary, it corrects two things the secondary coverage compressed and supports four claims. - [[3. Resources/Permanent Notes/A Decision Log Is How a Nebulous Role Becomes Inheritable]] — the role is judgment-shaped, so the reasoning *is* the job and nothing else records it. McCarthy's own stated problem is that she cannot reconstruct her prior reasoning either. - [[3. Resources/Permanent Notes/A Release Lead's Output Is Mostly Subtraction]] — the large majority of the logged decisions are punts, deferrals, and reversions, and the reasons are about timing and unresolved disagreement rather than merit. "What we don't add is sometimes more valuable than what we do." - [[3. Resources/Permanent Notes/A Decision Made Under Irreducible Ambiguity Is Judged on Its Recorded Reasoning]] — the WCUS release-day call, with seven reasons in stated order of importance and "I will own this decision if it ends up being wrong later" claimed *before* any outcome was known. - [[3. Resources/Permanent Notes/A Legacy Feature Should Become Obsolete by Choice Not by Force]] — the July 7 Classic block reversal, which also narrows the scope of [[3. Resources/Permanent Notes/Hiding Not Removing Deprecates a Legacy Feature Safely]] from a claim about breakage to a claim that must still pass a consent test. ## Synthesis additions (2026-08-28b — AI bills of materials) - [[3. Resources/Literature Notes/What's in Your AI — The Case for AI Bills of Materials (Alan Friedman, RSAC)]] — extends this MOC's supply-chain transparency cluster from software to AI components. The governance-relevant finding is that the missing piece is neither standards nor policy demand — both exist (CycloneDX, SPDX, G7 minimum elements, proposed US legislation) — but a **consensus baseline**, and its binding constraint is consistency rather than field coverage: two tools describing one system must produce comparable output. Read against [[3. Resources/Literature Notes/Announcing GUAC, a great pairing with SLSA (and SBOM)!]], which is the inventory-to-risk mapping layer AI still lacks and software already has. ## Synthesis additions (2026-10-05 — litigation exhibits, Automattic governance news and community items) **WPE v. Automattic filings** - [[3. Resources/Readwise/Articles/WPE v. Automattic, Dkt. 414 - Defendants' Motion to Modify Expert Discovery and Briefing Deadlines]] — Moving defendants ask for a two-month extension of expert and summary-judgment deadlines, citing a change of lead counsel (party assertion; no ruling). - [[3. Resources/Readwise/Articles/WPE v. Automattic, Dkt. 414-1 - Proposed Order Granting Motion to Modify Expert Discovery and Briefing Deadlines]] — Proposed order accompanying Dkt. 414; it states the movants' requested dates, not a ruling. - [[3. Resources/Readwise/Articles/WPE v. Automattic, Dkt. 415 - Declaration of Shawn Rabin ISO Motion to Modify Expert Discovery and Briefing Deadlines]] — Declaration supporting the Dkt. 414 extension motion (declarant's assertions, not findings). - [[3. Resources/Readwise/Articles/WPE v. Automattic, Dkt. 415-1 - Exhibit A, Counsel Emails on Expert Deposition Dates]] — Email chain between counsel on expert deposition dates, attached to the extension motion; each side's statements are party assertions. - [[3. Resources/Readwise/Articles/WPE v. Automattic, Dkt. 415-2 - Exhibit B, Counsel Emails on the Expert Discovery Schedule]] — Second counsel email exhibit on the expert discovery schedule, attached to the extension motion. - [[3. Resources/Readwise/Articles/WPE v. Automattic, Dkt. 416 - Joint Discovery Letter, Automattic and Silver Lake (Search Terms and Custodians)]] — Joint letter in which Automattic and non-party Silver Lake each describe a dispute over search terms and custodians; no ruling in the document. - [[3. Resources/Readwise/Articles/WPE v. Automattic, Dkt. 417 - Joint Letter Brief Re Audrey's Response to WPE's Subpoenas]] — Joint letter brief with each side's description of Audrey's response to subpoenas; party assertions, no ruling. - [[3. Resources/Readwise/Articles/WPE v. Automattic, Dkt. 418 - Joint Statement Re Deposition of Defendant Matthew Charles Mullenweg]] — Joint statement in which WP Engine seeks 5 more hours and a better-prepared designee and Defendants oppose; each position is a party assertion. - [[3. Resources/Readwise/Articles/WPE v. Automattic, Dkt. 418-1 - Exhibit A, Mullenweg Deposition Excerpts]] — Selected sworn deposition excerpts of Mullenweg (testimony, not findings), the unredacted-text twin used for comparison with Dkt. 420-1. - [[3. Resources/Readwise/Articles/WPE v. Automattic, Dkt. 418-2 - Deposition of Matthew Charles Mullenweg (Transcript Excerpts)]] — Five transcript-page groups from the May 12, 2026 Mullenweg deposition (sworn answers, not findings). - [[3. Resources/Readwise/Articles/Court Filings Reveal WordPress.org’s “Mission Control” Dashboard Tracked WP Engine’s ACF Pro Installs]] — The Repository reports Abrahamson's testimony about a password-protected WordPress.org dashboard graphing ACF Pro active installs; the headline compresses testimony into 'revealed' and no court finding is reported. **Governance and board news** - [[3. Resources/Readwise/Articles/WordPress Takes Its Turn Leading the Open Website Alliance as Mary Hubbard Eyes AI Regulation]] — The Repository reports that WordPress Executive Director Mary Hubbard is serving as president of the Open Website Alliance (WordPress, Drupal, Joomla!, TYPO3), a rotating role, and says she told the outlet AI is where she wants the alliance to focus. - [[3. Resources/Readwise/Articles/YT-DLP Is Being Treated as a Piracy Tool by the IFPI]] — It's FOSS, via TorrentFreak, reports that the IFPI's submission to the European Commission's piracy watch list consultation names yt-dlp and four maintainers; the outlet argues the tool is not a service, and the IFPI's statements are the IFPI's, not findings. - [[3. Resources/Readwise/Tweets/AKA No Security for Plugin Repo]] — Matt Mullenweg posts on X that a rival CMS's "no landlord" plugin repository means no security review and calls that CMS a fork that violates GPL, claims the captured source does not verify. **Community and standards** - [[3. Resources/Readwise/Articles/Episode 294 Carol Willing & Hugo Bowne-Anderson on AI and OSS]] — On the Sustain podcast (SustainOSS, host Richard Littauer), Hugo Bowne-Anderson argues LLMs and agents are amplifiers, not democratizers, so the skill gap widens, and Carol Willing says AI has taken some joy and human connection out of maintaining; both are practitioner opinion with no data. - [[3. Resources/Readwise/Articles/Octopus Deploy - How to InnerSource Your Platform]] — A LeadDev panel produced with Octopus Deploy (two of three panelists work for platform vendors) says scrutiny should scale with blast radius and changes should pass an automated pipeline before merge, though it never defines an InnerSource method. - [[3. Resources/Readwise/Articles/How a PRINTER Created Open Source]] — A 40-second Jono Bacon Short says a jammed Xerox printer and a refused driver source pushed Richard Stallman toward free software; it cites no source and uses 'open source' where the story is about free software. - [[3. Resources/Permanent Notes/A Thread About an Excerpt Mixes Its Author's Inference Into What the Excerpt Says]] — a social thread about a filed deposition excerpt blends the witness's words with the author's inference and outside material; only the first layer can be checked against the page - [[3. Resources/Permanent Notes/Diffing a Redacted Re-filing Against Its Twin Shows Where Text Went, Not Why]] — a word-level diff of a filing against its redacted re-filing shows where text is absent and how much, and nothing about the reason or the legal basis ## Synthesis additions (2026-10-07 — backlog triage and contribution policy) - [[3. Resources/Readwise/Articles/Steve Licked a Hammer Sponsored by show.fm - This Week in WordPress 384]] — The episode's hosts report the WordPress 7.2 roadmap drops real-time editing again and that the plugin directory queue holds 4,598 items, 3,860 of them waiting on authors. - [[3. Resources/Readwise/Articles/Tammie Lister on Open Source Maintenance, AI Integration and Community Events Kinsta Talks]] — Tammie Lister says clearing a theme backlog means saying no to some tickets and that each close needs a stated reason, with AI used to sort and a human making the judgment call (her opinion, on a Kinsta-hosted show). - [[3. Resources/Readwise/Articles/Proposal Minor Updates to the WordPress Core CSS Coding Standards]] — A Make WordPress Core post proposes minor CSS standards changes so Stylelint can enter Core CI, with a one-week comment window and proceeding absent significant objections; nothing is adopted yet. - [[3. Resources/Readwise/Articles/The Pi Updates Are Insane ⟡ Pull Requests Are Dead ⟡ Turso Joining Supabase ⟌ Syntax Weekly ⟌]] — On Syntax, the hosts relay that several maintainers disabled external pull requests because of AI-generated submissions and argue that when implementation is free, a well-described issue is what still signals effort; the title overstates evidence that covers four named maintainers. - [[3. Resources/Permanent Notes/Every Ticket Closed in a Backlog Clearing Needs a Stated Reason]] — a closing comment that says why turns a no into a record the reporter and the next maintainer can both read. - [[3. Resources/Permanent Notes/When Patches Cost Nothing the Described Problem Is the Contribution]] — when an agent can generate a patch for almost no effort, the costly part of a contribution is describing the problem well. ## Synthesis additions (2026-10-09 — who pays for security and review) Mary Hubbard's 2026-10-08 ask that 30+ companies fund the WordPress security program (reported by The Repository) drew same-day replies on X about who carries review costs. - [[3. Resources/Literature Notes/They Should Consider Their WPScan Data — Sybre Waaijer (X, 2026-10-08)]] — the researcher side: downplayed reports and no bounty for unfunded software. - [[3. Resources/Permanent Notes/Vulnerability Research Follows the Bounty Not the Risk]] — research attention goes where reports pay, so unfunded plugins get the least scrutiny. - [[3. Resources/Literature Notes/AI Spam PRs Need a GitHub Solution — Brian and Helen Hou-Sandí (X, 2026-10-08)]] — the maintainer side: AI PR volume and visible infrastructure costs. - [[3. Resources/Permanent Notes/Charging Submitters for Pre-Review Turns a PR Flood Into Paid Triage]] — the submitter-pays answer, set against [[3. Resources/Permanent Notes/Platforms Must Absorb AI-Generated Change Volume Not Gate It]]. ## Synthesis additions (2026-10-14 — AI-built forks and provenance) - [[3. Resources/Permanent Notes/A Clean-Room Claim Needs a Record That the Two Sides Never Met]] — a clean-room label on an AI-built port needs documented, separate contexts for the spec agent and the implementer; the Syntax hosts don't know whether the project kept them separate. ## Synthesis additions (2026-10-18 — registering notes missing from MOCs) - [[3. Resources/Permanent Notes/Consuming Open Source Without a Give-Back Strategy Is Free-Riding]] — a consumer that gives back no code, governance, funding or feedback extracts value from a commons it fails to sustain. Built on Jamie Thomas's OpenSSF talk. ## Synthesis additions (2026-10-18 — registering previously unlisted notes) ### Permanent Notes - [[3. Resources/Permanent Notes/Flat Retake Pricing Removes the Incentive to Game a High-Stakes Exam]] — Charging full price on every retake of a high-stakes exam works as a security control, because a discount would reward failing on purpose to sample the item pool. Closest-fit placement. - [[3. Resources/Permanent Notes/Incrementalism Beats the Complete Solution in Open Standards]] — Open-web problems get solved by shipping one demand-proven piece and standardizing it, not by landing a whole philosophical shift in a single move. - [[3. Resources/Permanent Notes/Liability Is a Faster Adoption Lever Than Ideology]] — A practitioner who advises third parties adopts infrastructure independence faster when it's framed as professional-liability management than as an ideological stance. Closest-fit placement. - [[3. Resources/Permanent Notes/Zet · Automattic explores trademark royalties from hosts]] — Automattic is reported to be exploring trademark royalties from hosting companies, per a WP Engine claim about a broader royalty plan. - [[3. Resources/Permanent Notes/Zet · Comparative SEO can indicate passing off risk]] — Unusually high trademark term density in comparative SEO data can indicate passing-off risk, drawn from crawl datasets covering 2017 to 2025. - [[3. Resources/Permanent Notes/Zet · Disclaimers reduce WordPress brand confusion]] — Records that Automattic explored trademark royalties from hosts, based on a WP Engine claim, with links to governance and trademark topics. ### Literature Notes - [[3. Resources/Literature Notes/Cathedral vs Bazaar - A Metaphorical Approach to People Management]] — Ben Balter applies the cathedral and bazaar metaphor to people management, contrasting hierarchical, standardized control with decentralized, autonomous collaboration. Closest-fit placement. - [[3. Resources/Literature Notes/Consuming with Intent (Jamie Thomas, OpenSSF)]] — Jamie Thomas of OpenSSF argues organizations should consume open source with intent, including mapping dependencies and giving back in proportion to use. - [[3. Resources/Literature Notes/Dear Red Hat...]] — A podcast criticizes Red Hat for restricting RHEL source access with a pay-developers rationale, arguing it erodes the hobbyist trust that built its customer base. - [[3. Resources/Literature Notes/Episode 31 - Brent Toderash (Community and Code)]] — Brent Toderash describes FAIR as a software supply-chain protocol, not a WordPress project, with TYPO3 v14 shipping support in core as proof. - [[3. Resources/Literature Notes/Good Riddance to the Open Gaming License]] — Cory Doctorow argues the Open Gaming License is defective because it is perpetual but not irrevocable, and urges moving content to Creative Commons. - [[3. Resources/Literature Notes/Inner Source Portal for Easy Discovery]] — Describes an Inner Source portal that crawls GitHub repositories and uses tags and topics so developers can find reusable internal projects; setup takes about 15 minutes. - [[3. Resources/Literature Notes/Keep Cloud Native Moving - Building Japan's Platform for Open Infrastructure]] — A KubeCon Japan keynote from CNCF leaders argues AI inference is a service workload suited to cloud-native infrastructure and pitches an AI conformance program. Closest-fit placement. - [[3. Resources/Literature Notes/Leadership and Culture in Open Source Projects]] — The note says project leaders' attitude and community responsiveness shape engagement and the success of open source projects. - [[3. Resources/Literature Notes/Lit · Automattic plans multi-host royalty campaign]] — Automattic is alleged to be running a broader multi-host royalty campaign, with the WP Engine licensing push as its opening move. ## Synthesis additions (2026-10-19 — Permanents from the GameDev Day, agent-site and religious-history batch) - [Liquid Web Killed StellarWP. The Plugins Survived. The Trust Didn’t.](3.%20Resources/Readwise/Articles/Liquid%20Web%20Killed%20StellarWP.%20The%20Plugins%20Survived.%20The%20Trust%20Didn’t..md) — Alex Vasquez (DigiSavvy, a LearnDash consultancy) argues Liquid Web's retirement of the StellarWP brand left plugin buyers without warning on pricing and support terms. Opinion post, vendor-adjacent author; prices come from archive captures the post links.