# WordPress Foundation Institutional Independence — Tracking Note > **Canonical location notice**: the WordPress Foundation entity and its structural analysis already exist in Courtney's dedicated wp-governance wiki at `1. Projects/llm-wiki-wp-governance/wiki/entities/WordPress Foundation.md` and `…/concepts/WordPress Foundation Structure.md`. This Tracking Note serves a different purpose — it sits in the broader 2nd Brain vault to coordinate cross-domain Permanent Notes ([[3. Resources/Permanent Notes/Concentrated Authority Without Accountability Produces the Same Failure Patterns Across Religious and Software Ecosystems]], [[3. Resources/Permanent Notes/BDFL Litigation Necessarily Implicates Personal Corporate and Foundation Roles Because the BDFL Has Concentrated Them]]) and the OSS Governance MOC's WordPress Saga section. The wp-governance wiki is authoritative on the entity's structural and historical record; this note synthesizes that record into testable hypotheses for cross-domain pattern-matching. > **Tracking status (2026-05-29)**: provisional. This note exists to accumulate evidence about a specific empirical question — is the WordPress Foundation operationally independent from Automattic, or is it (per Trent Lapinski's first-person account AND the wp-governance wiki's documented findings) functionally a "shell nonprofit"? The note is structured so new evidence can be added as it comes; current conclusions are working hypotheses, not settled claims. ## What the wp-governance wiki already documents (canonical findings) This tracker draws heavily on prior research in [[1. Projects/llm-wiki-wp-governance/wiki/entities/WordPress Foundation]]. Key findings already established there as of 2026-04 to 2026-05-29: ### Board composition (3 members) - **Matt Mullenweg** — President. Dual role with Automattic CEO. No published conflict-of-interest policy. - **Mark Ghosh** — board member. No public Foundation activity traced since 2013. - **Chele Chiavacci Farley** — board member. No documented Foundation involvement. Source: [[1. Projects/llm-wiki-wp-governance/wiki/sources/two-kings-one-mirror-dhh-mullenweg]]. ### Ownership boundary - **WordPress.org** is **NOT** the Foundation's asset. Mullenweg personally owns it ("just me." — direct quote on X). - **WordPress trademark** is the Foundation's primary documented asset. - Operational infrastructure splits ambiguously between Automattic and personal Mullenweg ownership. ### WPCC critique (December 2024) The WP Community Collective's 2024-12-03 internal feasibility study lists five structural grievances: 1. Opaque governance 2. Centralized control 3. **Inactive Foundation** — unresponsive to donations and community 4. No conflict-of-interest policy 5. BDFL volatility The WPCC study uses Foundation structural thinness as argument for a decentralized alternative with a 15-member board. ### Observable operational signals - **Donation cancellation flow broken**: Dave Loodts (2026-04-15) reports two unanswered attempts to cancel a $50/year recurring Foundation payment. Suggests administrative thinness OR unresponsive finance function. - **"The Foundation has nothing to do with core"** (Loodts): community framing of operational distance. - **No conflict-of-interest policy** governing Mullenweg's dual role as Foundation President + Automattic CEO. - **Trademark without infrastructure**: Foundation holds the trademark but does not own the domain, limiting enforcement leverage. ### ProPublica 990 history (2026-05-29 — new this update; full 14-year extraction) **Confirmed institutional data**: - **EIN: 20-5498932** - **State of incorporation: California** - **501(c)(3) status since: June 2009** - Classification: "Education N.E.C." - ProPublica organization ID: 205498932 **Board composition (2024 filing)** — three directors, **all reporting $0 compensation across every year 2011-2024**: - Matt Mullenweg (Director) - Mark Ghosh (Director) - Chele Chiavacci Farley (Director) **Historical board (no longer serving)**: - Rose Goldman (CFO/Secretary) — 2013-2018 - Jason Hoffman (Director) — 2014-2015 **The 2015→2016 revenue cliff is the headline finding**: | Year | Revenue | Expenses | |---|---|---| | 2015 | **$2,878,475** | $2,256,530 | | 2016 | **$3,038** | $27,453 | The Foundation's revenue collapsed 99.9% in a single year and has never recovered (2024: $55,153). This establishes two distinct operational eras: - **Era 1 (2011-2015): Operating Foundation.** Revenue grew from $194K to $2.88M. Active CFO role. Multi-million-dollar operational scale. - **Era 2 (2016-2024): Skeleton Foundation.** Revenue $3K-$55K range. CFO role wound down. Two of three directors documented as inactive. This empirically anchors what the WPCC and Lapinski testimony described qualitatively. The Foundation **became** a shell in 2016 — it did not start that way. Something specific happened in 2015-2016 that hollowed out its operational role. **The structural question this opens**: where did the operational work go? Hypotheses worth testing: - (a) WordPress.org (which Mullenweg owns personally — confirmed on X: "just me") - (b) Automattic absorbed Foundation functions - (c) A separate 501(c)(3) (WordPress Community Support PBC or similar) took over WordCamp operations - (d) Five for the Future moved to Automattic-direct sponsorship rather than Foundation-flow Mary Hubbard's role as **Executive Director of WordPress.org** (not Executive Director of the Foundation) is consistent with (a) or (b) — the operational ED role sits on infrastructure that is personally owned, not on the trademark-holding entity. **Per-year detail** (full table in wp-governance wiki canonical entity page): 2014: $1.70M rev, 2013: $1.03M rev, 2012: $586K rev, 2011: $194K rev (growth era 2011-2015) → 2016: $3K, 2017: $3.5K, 2018: $11K, 2019: $7.6K, 2020: $11K, 2021: $19K, 2022: $24K, 2023: $26K, 2024: $55K (skeleton era 2016-2024). The $55,153 revenue figure is operationally significant: it is unusually small for the steward of the trademark powering 43% of the public web. Either Hypothesis A (shell nonprofit) gains weight, or Hypothesis B/D would require explaining why a genuinely-active foundation operates at this scale. ### Supplemental data added 2026-05-29 (ProPublica API, IRS BMF) **Registered address**: 660 4th Street Apt 119, San Francisco, CA 94107-1618 — **this is Mullenweg's residence, not a Foundation office**. The IRS Business Master File lists "Care Of: Matt Mullenweg" — Foundation mail routes through Mullenweg personally. Operating foundations of the Foundation's putative scale typically maintain an office address distinct from any director's home. A residential c/o-the-president address is consistent with skeleton operation, not operating-foundation operation. **NTEE classification**: B99 (Education N.E.C.) — the most generic educational nonprofit code available. Operating foundations with developed programs typically refine into more specific NTEE codes (B82 for scholarships, B41 for community colleges, B43 for universities, etc). The Foundation's B99 code is consistent with no specific program focus. **Net asset trajectory (2011-2024)**: | Year | Net Assets | Year-over-year change | |---|---|---| | 2011 | $70,856 | (baseline) | | 2014 | $152,888 | growth phase | | **2015** | **$1,121,394** | **+$968K (peak)** | | 2016 | $987,425 | -$134K | | 2018 | $906,784 | drawdown | | 2019 | $861,023 | trough | | 2024 | (extrapolated ~$891K) | recovered | The skeleton-era operations (2016-2024) have drawn down approximately $230K of accumulated net assets across 8 years, partially offset by ~$170K in cumulative contributions over the same period. The Foundation is sustaining its small operations partly by spending down 2015-era reserves. At current burn rates, the $891K reserve would sustain roughly 14-22 more years of skeleton-scale operation. This is operationally durable but is not the financial posture of an organization growing into substantive program work. **Consistent ~$78,940 liability** appears across 2011-2023 filings (rising to $90,746 in 2016 and $121,361 in 2015 — the operating-era peak). The persistent ~$79K liability across the skeleton era suggests a long-running structured obligation — possibly a deferred-grant commitment, a long-term lease/note, or a payable to a related party. The amount being identical year-over-year for 12+ years is unusual and worth flagging for the trademark-license agreement review. **Program revenue 2011-2015 was substantive**: $95K (2011) → $228K (2012) → $182K (2013) → $519K (2014) → **$588K (2015)**. From 2016 forward, program revenue is **$0 in every year except trace amounts in 2019 ($1,225) and 2020 ($465)**. Whatever programs were generating $588K in 2015 (likely WordCamp tickets/sponsorships flowing through the Foundation) stopped flowing through the Foundation entirely after 2015. This is the dispositive empirical signal: program activity didn't shrink, it relocated. **Acquisition gaps still outstanding**: WebFetch attempts on the actual 2015 and 2016 Form 990 PDFs returned only the ProPublica landing-page metadata, not the filing PDFs themselves (display_990 URLs render JS-driven viewers, not the raw PDF stream). The California AG Registry of Charitable Trusts search interface returned its instructions page rather than results (JS-rendered .NET WebForms search). The IRS direct EOS search returned HTTP 403. These items remain pending alternate acquisition (Bash + curl for PDFs read via Read tool, or Firecrawl for JS-rendered registry pages). ## The Question Being Tracked **Is the WordPress Foundation an operationally independent 501(c)(3) non-profit with genuine governance autonomy, or is it functionally a legal-entity wrapper that operates as Automattic's instrument with separate paperwork?** The question matters now for three reasons: 1. **Reported claim (pending verification)**: According to information shared in conversation 2026-05-29, WP Engine may be seeking dissolution of the WordPress Foundation as part of its litigation strategy. Whether this is a formal filed request, a settlement-position lever, or community speculation has not yet been confirmed against primary sources. The "shell nonprofit" framing has been publicly made in non-litigation contexts (Lapinski tweet, May 2026); the formal litigation request — if it exists — would be distinct. 2. **Mullenweg's WP23 framing (May 26-27, 2026)**: In his WordPress 23rd-anniversary post, Mullenweg framed Silver Lake / WP Engine as "trying to dissolve the WordPress Foundation." Whether this framing is accurate or rhetorical is itself an open question; the framing is on record in the WP23 post but the underlying litigation filings have not yet been produced to verify it. 3. **The Foundation's role in the underlying litigation**: The WordPress Foundation is a named defendant in *WP Engine v Automattic* (docket 3:24-cv-06917) and is being defended through the same counsel coordinating with Automattic + WooCommerce + Mullenweg personally. The Foundation's separate legal personality is being procedurally asserted in discovery (per the Kaul Declaration enumerating interrogatories to "WordPress Foundation" as a distinct defendant — Doc 312.1); whether that procedural separateness reflects substantive operational separateness is the question. ## What We Know About the Foundation ### Basic structure (per public knowledge as of 2026-05-29) - **Founded**: 2010 by Matt Mullenweg - **Legal status**: 501(c)(3) non-profit corporation (state of incorporation: not yet verified in this tracker) - **Stated mission**: Educate the public about WordPress and related open source software - **Trademark holdings**: Holds the WordPress trademark; Automattic operates under exclusive commercial license - **Foundation Board**: Mullenweg serves as primary board member (per Duerrenberger five-roles diagnosis); full board composition needs primary-source verification ### What the existing wiki sources document - [[3. Resources/Readwise/Articles/Timeline of the WordPress Drama - DevLog]] (Duerrenberger): names the Foundation as one of Mullenweg's five concentrated roles - [[3. Resources/Readwise/Tweets/I Obviously Don’t Want Any Harm to Come to WordPress]] (Lapinski): first-person account of volunteering for .org and Foundation work; describes the Foundation as "basically just used as a shell nonprofit that never reached its potential or promise" ### What the existing wiki sources do NOT document - The Foundation's actual independent activities (or lack thereof) in calendar years 2020-2026 - The Foundation's current board composition (beyond Mullenweg) - The Foundation's annual budget and IRS Form 990 filings (these are publicly available but not yet ingested) - The Foundation's stated educational programming and what fraction of it operates through Automattic resources vs Foundation-direct resources - The Foundation's bylaws governing board composition, succession, and removal mechanisms - The trademark-license agreement between the Foundation and Automattic (likely contains substantive Foundation-vs-Automattic boundary detail) - The Foundation's historical record of independent decisions that diverged from Automattic's positions (if any exist) The gap between what we know and what's required to answer the question is substantial. ## Working Hypotheses ### Hypothesis A: Shell Nonprofit The Foundation has formal legal existence as a 501(c)(3) but in operation is indistinguishable from Automattic. Its board is composed of Mullenweg + nominally-listed but inactive members; its decisions track Automattic's positions; its independent programming is limited or nominal; its trademark-holding function operates as exclusive licensor to Automattic rather than as independent steward of community interest. **Supporting evidence in vault** (revised 2026-05-29 with wp-governance wiki findings): - Lapinski's first-person account ("shell nonprofit that never reached its potential or promise") - **Documented board inactivity**: Mark Ghosh has no traced public Foundation activity since 2013; Chele Chiavacci Farley has no documented Foundation involvement (per wp-governance wiki entity page sourced to [[1. Projects/llm-wiki-wp-governance/wiki/sources/two-kings-one-mirror-dhh-mullenweg|two-kings-one-mirror-dhh-mullenweg]]) - **No published conflict-of-interest policy** governing Mullenweg's dual Foundation-President + Automattic-CEO role (per wp-governance wiki concept page) - **Broken donation cancellation flow**: Dave Loodts's two unanswered cancellation attempts suggest administrative thinness OR unresponsive finance function - **WPCC structural critique** (2024-12-03 feasibility study): "Inactive Foundation" named as one of five structural grievances justifying decentralized alternative - Schroeder's critique that Mullenweg's posting personal advocacy on WordPress.org during litigation about Mullenweg's use of WordPress.org is "beyond the pale" — implies role-blurring across personal/.org/Foundation that wouldn't occur if institutional independence were operative - Foundation being defended by same counsel (Joseph Rose) coordinating with Automattic + Mullenweg-personal + WooCommerce in May 2026 discovery filings - The five-roles concentration documented elsewhere - **ProPublica 2024 revenue**: $55,153 — operationally tiny for an organization holding the trademark to software running 43% of the web **Aggregate position (revised 2026-05-29 after 990 review)**: Hypothesis A has substantial empirical support, but the framing requires sharpening. The Foundation is not a shell that **was** designed as a shell — it is an operating foundation that **became** a shell in 2016. Revenue collapsed 99.9% between 2015 ($2.88M) and 2016 ($3K) and has stayed at the small-foundation scale ($3K-$55K) ever since. This produces a refined hypothesis variant: ### Hypothesis A' (refined): Skeleton Foundation Post-2015 Transition The Foundation operated at multi-million-dollar scale through 2015, then transferred its operational functions (most plausibly to WordPress.org-as-Mullenweg-personal-property and/or to Automattic) while retaining its legal existence and trademark-holding function. After 2015 it is operationally a skeleton: legal personhood + trademark + three directors with $0 comp + no CFO + sub-$60K annual revenue. **Supporting evidence for the refined claim**: - 99.9% revenue collapse 2015→2016 (990 history) - CFO role wound down 2018, never replaced (990 history) - 14 years of $0 compensation across all directors (990 history) - Two of three current directors documented as inactive (wp-governance wiki) - Operational ED role lives on WordPress.org (Mary Hubbard), not Foundation - WordPress.org confirmed as Mullenweg's personal property ("just me." on X) - WPCC names Foundation inactivity as structural grievance (Dec 2024) - May 2026 litigation defense through unified Automattic-coordinated counsel **What this implies**: The Foundation's continued legal existence appears to serve primarily as trademark-holding vehicle, with operational community functions having moved to entities (WordPress.org / Automattic / possibly other) that are not subject to 501(c)(3) governance requirements. The dissolution-as-remedy question becomes operationally moot if the Foundation does not actually operate community functions — dissolving it would not affect the community work, only the trademark-holding arrangement. **Strongest counter-evidence still needed**: - The actual 2015 990 program-services description (where the $2.26M expenses went) - The actual 2016 990 explanation for the revenue collapse - Documentation of whatever entity (if any) absorbed the post-2015 operational functions - The trademark-license agreement between Foundation and Automattic (would clarify trademark-holding-function reality) - Ghosh or Farley exercising substantive post-2015 board role - Foundation Schedule O disclosures (board changes, significant transactions, major events) ### Hypothesis B: Genuine But Constrained The Foundation has real institutional existence with some independent operations but its capacity is limited by founder-direction and resource-flow from Automattic. It would, in principle, be capable of independent action but in practice rarely takes positions that diverge from Automattic because the founder coordinates both. **Supporting evidence in vault**: - The Foundation is procedurally distinct in the litigation (separate party, separate interrogatories) - The 5% trademark royalty proposal that surfaced in 2024 (referenced in earlier WordPress saga coverage) suggested Foundation-mediated revenue flow distinct from Automattic-direct revenue - The Foundation's continued legal personality across the saga (it's been a defendant since the case began) **Strongest counter-evidence needed**: - Documented record of Foundation operating decisions distinct from Automattic operating decisions - Foundation budget and IRS 990 showing independent revenue and expense streams ### Hypothesis C: Genuine and Substantive The Foundation is a real institutional non-profit with material independent operations, distinct governance, and substantive autonomy from Automattic. The "shell nonprofit" framing reflects observer ignorance rather than institutional reality; the litigation defense coordination reflects efficient counsel rather than operational consolidation. **Supporting evidence in vault**: minimal so far. This hypothesis would require positive evidence currently absent from the vault. **Strongest counter-evidence needed**: - Documented record of Foundation decisions independent of Automattic (annually, with examples) - Independent governance review or board minutes ### Hypothesis D: Hybrid The Foundation's autonomy varies by domain. Trademark-licensing operations may be coordinated tightly with Automattic; education-and-events operations may run more independently; WordPress.org operations may be effectively Automattic-operated despite Foundation-owned. Specific judgments require domain-specific evidence. This hypothesis is currently the most consistent with available evidence but is also the least diagnostic — it accommodates many possible operating realities without committing to specifics. ## The Reported "WP Engine Wants Foundation Dissolution" Claim **As of 2026-05-29, the claim that WP Engine is formally seeking Foundation dissolution has not been verified against primary sources in this vault.** The Mullenweg WP23 post (May 26-27, 2026) frames Silver Lake's litigation goal as "trying to dissolve the WordPress Foundation." Two distinct questions follow: 1. **Is Mullenweg's characterization accurate?** A formal dissolution remedy would need to appear in WP Engine's complaint, amended complaint, or specific motion. The current discovery-disputes phase doesn't address dissolution directly. Whether dissolution is in WP Engine's prayer for relief at the original complaint, in the amended complaint (Doc 175, March 2025 — not yet ingested in this vault), or has been raised in subsequent filings, is unknown to this tracker. 2. **What would dissolution actually look like as a remedy?** Trademark transfer to a different governance entity? Trademark abandonment? Court-ordered restructuring of the Foundation's governance? Court-ordered separation of Foundation and Automattic? Each is a substantially different remedy with different operational consequences for the WordPress community. **Sources to acquire to verify this claim**: - WP Engine's original complaint (Doc 1, October 2024) — examine prayer for relief - WP Engine's amended complaint (Doc 175, March 2025) — examine prayer for relief - Any subsequent motion explicitly addressing the Foundation as remedy target - Court orders or proposed orders that engage Foundation governance specifically These are publicly available via CourtListener; ingesting them would substantively answer the verification question. ## Empirical Tests to Watch ### Test 1: Foundation Board Composition If the Foundation board is composed exclusively or nearly exclusively of Mullenweg + Mullenweg-employed figures (Automattic employees or affiliated counsel), the shell-nonprofit hypothesis gains weight. If the board includes substantive non-Mullenweg-aligned community voices with genuine voting power, Hypothesis B or C gains weight. **Data source**: IRS Form 990 (publicly available); WordPress Foundation bylaws (may require state-corporate-filing lookup); historical board-membership announcements. **Status**: not yet acquired in this vault. ### Test 2: Independent Decisions History If a review of 2010-2026 reveals zero documented Foundation decisions that materially diverged from Automattic positions, the shell-nonprofit hypothesis gains weight. If even a few clear independent decisions exist, Hypothesis B becomes more credible. **Data source**: Historical Foundation press releases, blog posts, programming announcements; comparison with Automattic announcements in the same periods. **Status**: not yet acquired in this vault. ### Test 3: Litigation-Period Independence If the Foundation, throughout the WP Engine v. Automattic litigation, takes ZERO positions that distinguish its interests from Automattic's interests, the shell-nonprofit hypothesis gains substantial weight. If the Foundation files any separate response, expresses any independent litigation interest, or takes any community-facing position distinct from Mullenweg's WP23 framing, Hypothesis B or D becomes more credible. **Data source**: Foundation filings in the litigation; Foundation public statements during 2024-2026; any independent Foundation response to the WP Engine dispute. **Status**: not yet acquired in this vault. The May 2026 discovery-disputes batch shows Foundation being defended through unified counsel with Automattic + Mullenweg; this is consistent with Hypothesis A but not conclusive. ### Test 4: Trademark Stewardship If the Foundation's trademark stewardship demonstrates community-interest-balancing distinct from Automattic-commercial-interest, Hypothesis B-C gains weight. If trademark decisions consistently track Automattic commercial positions, Hypothesis A gains weight. **Data source**: The trademark-license agreement between Foundation and Automattic; the Foundation's actual trademark-enforcement decisions historically; the Foundation's posture during the WP Engine trademark-use dispute specifically. **Status**: the trademark dispute IS the underlying litigation, so resolution of this test is partly the resolution of the case. ### Test 5: Resource Independence If the Foundation operates with revenue/budget genuinely separate from Automattic-controlled resources, Hypothesis B-C gains weight. If the Foundation's financial operations depend substantially on Automattic-flow, Hypothesis A gains weight. **Data source**: IRS Form 990 revenue/expense schedules; Foundation budget statements; any documentation of Foundation-direct funding flows. **Status**: not yet acquired in this vault. 990s are publicly available. ### Test 6: Governance Mechanism Independence If the Foundation has formal mechanisms for board succession, accountability, and removal that operate independently of Mullenweg's direction, Hypothesis B-C gains weight. If formal governance mechanisms route through Mullenweg with no credible alternative, Hypothesis A gains weight. **Data source**: Foundation bylaws (state-corporate filing); historical record of board changes. **Status**: not yet acquired in this vault. ## Forward Monitoring ### Primary sources to ingest - **WP Engine's original complaint** (CourtListener Doc 1, October 2024) — for original prayer for relief - **WP Engine's amended complaint** (CourtListener Doc 175, March 2025) — for current prayer for relief - **The WordPress Foundation's IRS Form 990** for tax years 2020-2025 (publicly available) - **The WordPress Foundation bylaws** (via state-of-incorporation corporate filing) - **The trademark-license agreement** between Foundation and Automattic (may be in the litigation record under seal or partially redacted) - **Foundation board composition history** (via public announcements + Form 990 disclosures) ### Litigation milestones to watch - The June 1 / June 3 / June 10, 2026 deadlines set in Doc 319 — produces structured records about Audrey HC, Silver Lake, and Foundation-related discovery - Court rulings on summary judgment (timing not yet established) - Any settlement positions made public (typically via court filings or coordinated press release) - Any specific motion addressing Foundation governance as remedy ### Public-sphere events to monitor - Foundation board changes or resignations - Foundation programming announcements - Foundation responses to community criticism - Any community calls for Foundation governance reform separate from the litigation - Any actions by state attorney general or IRS regarding Foundation non-profit status ## Links - [[Open Source Governance MOC]] — connects evidence about institutional independence to the larger WordPress governance record. ### To existing Permanent Notes - [[3. Resources/Permanent Notes/Concentrated Authority Without Accountability Produces the Same Failure Patterns Across Religious and Software Ecosystems]] — the Foundation question is a specific instance of the broader concentrated-authority diagnostic - [[3. Resources/Permanent Notes/BDFL Litigation Necessarily Implicates Personal Corporate and Foundation Roles Because the BDFL Has Concentrated Them]] — the Foundation being procedurally distinct but operationally unified is the specific Foundation-role expression of this thesis - [[3. Resources/Permanent Notes/Public Credit Mechanisms Are the Visible Skeleton of Open Source Social Contracts]] — the Foundation could in principle operate the kind of credit infrastructure that makes social contracts legible (Drupal model); whether it does or doesn't is one diagnostic of its substantive independence - [[3. Resources/Permanent Notes/Open Source Project Market Share Tracks Founder Trust]] — Foundation independence and founder trust are inseparable in the current WordPress structure - [[3. Resources/Permanent Notes/Trust Erosion in Concentrated Systems Is Slow to Build and Fast to Manifest]] — the Foundation question is partly a function of the broader trust erosion ### To existing Literature Notes - [[3. Resources/Literature Notes/WP Engine v Automattic Discovery Disputes May 2026 - Litigation Roundup - Literature Note]] — the procedural posture documents the Foundation being defended through unified counsel; this tracker engages the underlying substantive question ### To MOCs - [[3. Resources/MOCs/Open Source Governance MOC]] — primary location; this tracker is anchored under the WordPress Saga section ## What This Tracker Does and Does Not Claim ### Does claim - The question of Foundation institutional independence is empirically open and underdetermined by current available evidence - The Lapinski first-person account is a real data point that should be weighted but not treated as dispositive - The Mullenweg WP23 framing of Silver Lake's dissolution goal is on record but not verified against the actual litigation filings - The procedural posture of the May 2026 discovery-disputes phase is consistent with multiple working hypotheses ### Does not claim - That the Foundation IS a shell nonprofit (insufficient evidence; the strong claim is hypothesis-A territory) - That the Foundation IS substantively independent (insufficient evidence; the strong claim is hypothesis-C territory) - That WP Engine has formally requested Foundation dissolution (reported but unverified) - That Mullenweg's WP23 framing is accurate or inaccurate (verification requires primary-source litigation review) - That the Foundation's defense by unified counsel necessarily reflects operational consolidation (could equally reflect efficient litigation strategy) ### Update protocol This note should be updated when: - New primary-source litigation material becomes available (especially WP Engine complaints, motion practice addressing Foundation, court rulings on Foundation governance) - IRS Form 990 data is ingested - Foundation board composition changes - Substantive Foundation actions occur that distinguish its position from Automattic's - New community testimony or public commentary substantially extends what's documented above Each update should: name the new source; identify which hypothesis it strengthens, weakens, or leaves unchanged; preserve prior reasoning rather than overwriting it. ## Open Questions - Does the WordPress Foundation maintain Form 990 filings that show distinct revenue and expense streams from Automattic? - Has the Foundation ever taken a public position that materially distinguished its interests from Automattic's interests? - What's the actual trademark-license agreement between the Foundation and Automattic, and what governance levers does it preserve to the Foundation? - Does WP Engine's amended complaint (Doc 175) actually request Foundation dissolution as remedy, and if so, in what form? - If the Foundation's governance is reformed (whether by court order, by settlement, or by founder-initiated structural change), what governance design would produce credible independence going forward — and what governance models from other OSS foundations (Apache, Linux, Eclipse, Mozilla, OpenInfra) are the relevant comparisons? - What's the role of state attorney general oversight of 501(c)(3) governance, and has the WordPress Foundation faced any such oversight historically? - Does the IRS treat the Foundation's exclusive trademark license to Automattic as compliant with non-profit purpose-of-organization requirements? ## What This Tracker Does Not Cover (yet) - The Foundation's relationship to other major OSS foundations comparatively - The Foundation's specific programming track record in 2020-2026 - Detailed legal analysis of 501(c)(3) governance requirements - The full procedural history of WP Engine v. Automattic from October 2024 through May 2026 - Any non-WordPress comparisons (other founder-led foundations facing similar institutional-independence questions — e.g., the Apache Foundation's relationship to specific PMCs and their corporate sponsors)