WPEngine, Inc. V. Automatic Inc. Et Al. 🔗 **Source:** [WPEngine, Inc. V. Automatic Inc. Et Al.](https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.295.0.pdf) > [!note]+ Document Notes > tags: [wp-engine-automattic, discovery-dispute, trademark-enforcement, wordpress-governance, wordpress-foundation, interrogatories, selective-enforcement, retaliatory-conduct] > author: WPEngine, Inc. (Quinn Emanuel) > source: CourtListener RECAP - N.D. Cal. 4:24-cv-06917-AMO > filing_type: motion > docket: 295.0 > > # 🏷️ WPEngine Motion to Compel Discovery Responses on WordPress Governance and Trademark Enforcement > > # 🧭 Table of Contents > - [References](#-references) > - [Summary](#-summary) > - [Main Content](#-main-content) > - [Governance Digest](#-governance-digest) > - [Hypotheses](#-hypotheses) > - [Questions](#-questions) > - [Future Research](#-future-research) > - [Implications](#-implications) > > # 🔗 References > **Dockets:** 295.0 > **Rules:** Federal Rules of Civil Procedure (discovery rules) > **Cases:** WPEngine, Inc. v. Automattic Inc. et al., No. 4:24-cv-06917-AMO > **Claims Referenced:** TAC ¶¶ 42, 122-135, 196, 206-227, 347, 437-440, 445, 447, 456, 458, 516-541, 519 > > # 📝 Summary > WPEngine moves to compel substantive discovery responses from Automattic, Mullenweg, WooCommerce, and WordPress Foundation after failed meet-and-confer sessions. The motion targets eight core interrogatories seeking facts about trademark enforcement patterns, WordPress Foundation governance history, Mullenweg's communications platforms, customer retaliation efforts, and corporate control structures. WPEngine argues defendants are using "flat refusals" and "partial answers that withhold the very information the interrogatories require" on issues central to antitrust, trademark, and promissory estoppel claims. The discovery dispute reveals the litigation's focus on proving Automattic's de facto control over nominally independent WordPress entities and selective trademark enforcement as anticompetitive weapons. > > # 📖 Main Content > <!-- deep-read:sections start --> ## 🗒️ Notes **Trademark Enforcement Timeline Disputes** - Interrogatory No. 2: WPEngine seeks specific date when alleged trademark infringement began - Defendants respond only "early 2020s" - a four-year window WPEngine calls inadequate - Critical for laches and estoppel defenses per TAC ¶¶ 42, 456, 458 **Selective Enforcement Evidence** - Interrogatories No. 3 (Defendants/WooCommerce): Seek instances of trademark licensing requests - Responses described as "non-answers" with incomplete lists lacking dates, circumstances, terms - Interrogatory No. 10 (Automattic), No. 4 (WooCommerce/Foundation): Seek instances of identified but unenforced infringement - Defendants invoke work product protection for "non-privileged, nonattorney-driven facts" **Mullenweg Communications Discovery** - Interrogatory No. 10: Seeks complete inventory of Mullenweg's messaging platforms - Mullenweg hedges with "may have," omits activation dates, provides no usernames for Telegram/Signal/WhatsApp/iMessage - WPEngine needs definitive inventory to test production completeness **Retaliation Evidence** - Interrogatory No. 11 (Mullenweg), No. 12 (Automattic): Seek details of customer interference - Defendants refuse subparts seeking "statements made to disrupt WPE's business relationships" - Claim requests call for "legal conclusions" despite seeking factual statements - Core evidence for interference and antitrust claims per TAC ¶¶ 122-135, 519 **WordPress Foundation Governance** - Interrogatory No. 13: Seeks Foundation governance history since 2005 - Mullenweg provides only current board, omits prior members, trustees, major donors, officer histories, selection processes - Central to proving de facto control over "nominally independent entities" per TAC ¶¶ 6, 89, 196, 347 **"Free and Open" Representations** - Interrogatory No. 15 subparts (a)-(b): Seek facts about WordPress "free"/"open" and non-commercial control claims - Mullenweg refuses as "not relevant" despite centrality to promissory estoppel and antitrust claims per TAC ¶¶ 437-440, 516-541 **Corporate Structure Discovery** - Interrogatory No. 13 (Automattic): Seeks corporate structure and ownership history since 2005 - Response called "skeletal" - omitting board members, subsidiaries, affiliates, equity holder history - Relationships among Mullenweg, Automattic, Foundation, wordpress.org central per TAC ¶¶ 6, 57-67 # 📚 References - Third Amended Complaint (TAC) paragraphs 6, 42, 57-67, 89, 122-135, 196, 206-227, 347, 437-440, 445, 447, 456, 458, 516-541, 519 - Meet and confer sessions: March 6, 2026 and May 20, 2026 - Discovery close date: May 14, 2026 # 🗣️ Paraphrase WPEngine is frustrated that after two years of litigation, the defendants are still dodging basic questions about how WordPress governance actually works. When asked "when did you first think WPEngine was infringing?" Automattic essentially answered "sometime in a four-year period." When asked about the WordPress Foundation's governance history, Mullenweg provided only current board members, ignoring 20+ years of organizational development. The defendants claim attorney-client privilege over factual questions like "who at your company first noticed WPEngine's website?" WPEngine argues these evasive tactics prevent discovery of the core issue: whether Automattic uses nominally independent WordPress entities as weapons against competitors while claiming WordPress is "free and open." # 📰 Governance Digest The WordPress community's governance transparency just hit a legal stress test—and the results aren't pretty. Court documents reveal that when pressed for basic facts about WordPress Foundation governance history, trademark enforcement patterns, and corporate control structures, key WordPress leaders are providing what one filing calls "non-answers" and "skeletal" responses. WPEngine's lawyers are essentially asking: "How does WordPress governance actually work, and who really controls what?" The evasive responses suggest either that the governance is more complicated than publicly represented, or that defendants don't want those details in the public record. Either way, the community's "radical transparency" ethos appears to stop at the courthouse door. # 🧪 Hypotheses 1. **Selective enforcement hypothesis**: Defendants maintain incomplete records of trademark enforcement decisions, suggesting ad hoc rather than systematic policy implementation 2. **Corporate entanglement hypothesis**: The "skeletal" corporate structure responses indicate complex, potentially undisclosed relationships between Automattic and WordPress entities 3. **Communication opacity hypothesis**: Mullenweg's hedged responses about messaging platforms suggest extensive informal communications outside discoverable corporate channels 4. **Governance control hypothesis**: The sparse WordPress Foundation governance history indicates concentrated, informal control mechanisms rather than documented institutional processes 5. **Legal strategy hypothesis**: Work product claims over factual trademark enforcement data suggest litigation strategy drove enforcement decisions rather than consistent policy 6. **Timeline coordination hypothesis**: The vague "early 2020s" trademark timeline suggests defendants cannot pinpoint enforcement decisions without revealing problematic strategic coordination # 📊 Methodology The motion relies on comparison between interrogatory requests and responses, with WPEngine characterizing gaps as evasive. No declarations support the motion; it proceeds on procedural grounds under FRCP discovery rules. The evidentiary basis consists of written interrogatory responses, meet-and-confer communications, and references to Third Amended Complaint allegations. WPEngine's characterization of responses as inadequate represents legal argument rather than factual testimony. # ❓ Questions - Will Magistrate Judge Krishnan compel production of Mullenweg's complete communication platform inventory including usernames and activation dates? - Can defendants successfully maintain work product protection over trademark enforcement non-decisions? - What governance details about the WordPress Foundation since 2005 might emerge under compulsion? - How will defendants justify the "early 2020s" timeline vagueness for trademark enforcement? - What corporate structure complexities is Automattic avoiding disclosure of in its "skeletal" responses? - Will the court find customer interference communications discoverable despite legal conclusion objections? # 🔮 Future Research **Litigation threads**: Discovery motion resolution; potential sanctions for inadequate responses; privilege log challenges; deposition scheduling for corporate representatives. **WordPress governance**: Foundation board composition history; trademark enforcement policy documentation; relationship agreements between Automattic and WordPress entities; decision-making process transparency; community input mechanisms in governance disputes. # 💡 Implications **Practice**: WordPress trademark usage becomes riskier without clear enforcement standards. **Policy**: Foundation governance opacity undermines community trust in institutional independence. **Security**: Informal communication channels complicate compliance and legal risk management. **Education**: Developer community needs clearer guidance on trademark boundaries and enforcement patterns. **Funding**: Corporate relationships with WordPress entities may require greater disclosure for investment and partnership decisions. # 🧠 Learning Styles Assessment **Visual**: Legal document structure, numbered interrogatories, paragraph references. **Aural**: Courtroom argument preparation, meet-and-confer discussions. **Verbal**: Legal terminology, procedural language, discovery rules. **Kinesthetic**: Document production, email/platform searches, corporate record compilation. **Logical**: Legal reasoning, privilege analysis, discovery rule application. **Social**: Multi-party litigation dynamics, community governance implications. **Solitary**: Individual interrogatory response preparation, legal research. **Naturalistic**: Corporate ecosystem relationships, trademark enforcement patterns. **Reading level**: Legal professional (graduate level complexity with specialized terminology). # 📊 Accessibility Assessment Text appears fully extractable from legal filing format. Standard legal document structure with clear headings and numbered sections. No tables or complex formatting artifacts noted. Meets basic accessibility standards though legal terminology creates comprehension barriers for general audiences. # 🌍 DEIB Assessment **Cultural breadth**: Limited to U.S. legal system context. **Inclusive language**: Standard legal terminology without apparent bias. **Neurodiversity support**: Dense legal format challenging for attention/processing differences. **Representation**: Corporate legal dispute among predominantly male tech leadership. **Psychological safety**: Adversarial litigation context inherently creates defensive positioning. # ✅ Logical Validity **Strong reasoning**: WPEngine systematically addresses each interrogatory with specific deficiency examples and legal relevance citations. **Fallacies**: Potential strawman in characterizing all defendant responses as evasive without acknowledging legitimate privilege concerns. **Tone**: Professionally aggressive, appropriate for discovery dispute motion. # 🛡️ DARVO Analysis Not applicable to this discovery motion - focuses on procedural compliance rather than substantive victim/offender dynamics. # 🎯 Conclusion This discovery motion exposes fundamental tensions between WordPress's "open" governance rhetoric and litigation realities. WPEngine's systematic documentation of evasive responses suggests defendants are protecting sensitive information about WordPress governance structures, trademark enforcement patterns, and corporate relationships. The motion's success could force unprecedented transparency about WordPress institutional control, while failure might enable continued governance opacity. Watch for Judge Krishnan's ruling on work product claims and whether defendants must provide detailed Foundation governance history and corporate structure documentation. # 🧱 Refactor Appendix ## 📚 Literature Atoms > [!quote] "Defendants' and Counterclaimants' have responded with one of two improper tactics: flat refusals to answer, or partial answers that withhold the very information the interrogatories require." > [!quote] "The Foundation's governance bears directly on WPE's allegations that Mr. Mullenweg and Automattic exercised de facto control over nominally independent entities to advance their anticompetitive scheme" > [!quote] "Mr. Mullenweg identifies only the current board and general descriptions of their responsibilities. He provides none of the detail the interrogatory requires—prior members, trustees, major donors, officer histories, or selection processes dating to the Foundation's founding." > [!quote] "Automattic cannot convert factual awareness into privilege merely because lawyers were later consulted." ## 🧠 Permanent Candidates - Discovery evasion patterns in open source governance disputes - Work product privilege boundaries for trademark enforcement decisions - WordPress Foundation governance documentation requirements - Corporate structure transparency in nominally independent foundations ## ✏️ Fleeting Queue - Mullenweg's extensive messaging platform usage suggests informal governance channels - "Early 2020s" timeline vagueness potentially indicates coordinated enforcement timing - WordPress Foundation governance opacity contradicts community transparency values - Corporate structure discovery resistance suggests complex Automattic relationships <!-- deep-read:sections end -->