WP Engine, Inc. V. Automattic Inc. Et Al., No. 3:24-Cv-06917  🔗 **Source:** [WP Engine, Inc. V. Automattic Inc. Et Al., No. 3:24-Cv-06917](https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.309.0.pdf) > [!note]+ Document Notes > tags: [wp-engine-litigation, discovery-dispute, document-production] > author: [MISSING] > source: U.S. District Court for the Northern District of California > reference: https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.309.0.pdf > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: Joint Letter Brief on Discovery Dispute - WP Engine v. Automattic > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [🎯 Conclusion](#-conclusion) - [🔄 Refactor Appendix](#-refactor-appendix) ## 📝 Summary - Joint letter brief filed May 21, 2026 regarding WP Engine's alleged failure to produce financial documents from CEO Heather Brunner and VP Victor Yuan - Defendants seek documents showing WP Engine's pre-September 2024 financial distress to counter $400M+ damages claim - WP Engine argues most requests fall outside parties' March 2026 reciprocal discovery agreement - Discovery closed May 14, 2026; dispute involves board materials, investor communications, and valuation documents - Key tension: Defendants claim WP Engine was "doomed to fail anyway" vs. WP Engine's "nuclear war" damages theory ## 📖 Main Content Defendants argue WP Engine concealed evidence that would "demolish" its damages claims by withholding contemporaneous financial records showing business distress before September 2024. They seek eight categories of documents including board deck drafts, investor communications, and valuation materials. WP Engine counters that most requests exceed their March 2026 reciprocal agreement scope, noting they've already produced 630,000+ pages including 13,000 finance-related documents. They characterize the motion as an attempt to "manufacture an alternate causation narrative" and "shift attention away from their own misconduct." The dispute centers on competing narratives: Defendants claim WP Engine was failing independently, while WP Engine maintains Defendants' "admitted nuclear war" caused their damages through intentional destruction efforts. ## 🗒️ Notes - Fact discovery closed May 14, 2026 - Brunner deposed April 29-30, Yuan May 6-7 - WP Engine claims close to $400M+ in damages - Multiple failed sale attempts in 2022-2023 - Silver Lake involvement as controlling investor - Production agreement reached after "months of negotiations" ## 📚 References - Case No. 3:24-cv-06917 (N.D. Cal.) - Wallace Declaration - Jenkins Declaration - Federal Rules of Civil Procedure 1, 26 ## 🗣️ Paraphrase This is a discovery dispute where Automattic/Mullenweg want financial documents they claim show WP Engine was struggling before their alleged misconduct began. WP Engine says they already agreed on document scope and produced massive amounts. Both sides accuse the other of bad faith - Defendants say WP Engine is hiding evidence of pre-existing problems, while WP Engine says Defendants are trying to escape liability for deliberate harm. ## 📰 Newsletter The WP Engine v. Automattic litigation continues with a heated discovery dispute over financial documents. The case involves fundamental questions about corporate governance, trademark licensing, and competitive practices in the WordPress ecosystem. For WordPress professionals, this litigation may reshape how hosting providers, agencies, and plugin developers operate within the community. The outcome could affect trademark usage, revenue sharing models, and the relationship between commercial WordPress businesses and the open-source project. ## ✅ Action Items #### DevRel Not applicable — legal filing #### OSPO Not applicable — legal filing #### Community - Monitor litigation impact on WordPress trademark usage guidance - Track implications for hosting provider relationships with WordPress Foundation #### WordPress Not applicable — legal filing #### The WPCC - Assess potential governance implications from litigation outcome - Consider funding impact on WordPress ecosystem neutrality ### FAIR - Document corporate capture risks exposed by litigation - Evaluate trademark governance as technical independence factor ## 🧪 Hypotheses - WP Engine's pre-September 2024 financial health will determine damages calculations - Discovery scope disputes indicate both parties fear certain evidence - The reciprocal agreement may have been strategically insufficient for both sides - Document withholding allegations suggest deeper governance and transparency issues ## 🎯 Conclusion This discovery dispute reveals the high stakes in determining whether WP Engine's claimed damages resulted from Defendants' conduct or pre-existing business problems. The outcome may establish important precedents for trademark enforcement and competitive practices in open-source ecosystems. ## 🔄 Refactor Appendix — Joint Letter Brief on Discovery Dispute ### 📚 Literature Atoms #### WP Engine conceals financial evidence contradicting damages narrative > [!quote] ID:rw_filing1 > WP Engine's case rests on a single proposition: that Defendants' conduct beginning in September 2024 destroyed an otherwise healthy business and caused close to $400M+ in damages. The documents Defendants seek demolish that proposition. **Context & use**: Core of Defendants' argument that WP Engine is hiding pre-existing financial distress **Tags**: #xref #litigation-strategy **Highlight**: Discovery dispute filing <!-- atomicity: 1 idea ✓ --> #### Discovery agreements create binding limits on document production scope > [!quote] ID:rw_filing2 > After months of negotiations over the scope of financial discovery, the parties reached a reciprocal agreement in late March, 2026. Neither side reserved any rights to later seek additional categories of financial documents. **Context & use**: WP Engine's defense that agreed-upon discovery scope should be honored **Tags**: #xref #legal-procedure **Highlight**: Legal procedural safeguards <!-- atomicity: 1 idea ✓ --> #### Corporate misconduct narratives compete through document production battles > [!quote] ID:rw_filing3 > This case is about Defendants' admitted "nuclear war" launched against WPE, with Defendants' stated goal of destroying WPE "brick by brick," for WPE's failure to capitulate to Defendants' extortionate monetary demands. **Context & use**: WP Engine's framing of deliberate harm vs. business failure **Tags**: #xref #corporate-governance **Highlight**: Competing causation theories <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates #### Discovery disputes reveal litigation strategy through evidence control **Claim**: Parties' fights over document production scope expose which evidence each side fears will undermine their narrative. **Evidence pointer**: [[#Corporate misconduct narratives compete through document production battles]] **Scope & conditions**: Applies when substantial damages claims depend on causation timing; less relevant for straightforward liability cases **Links**: - [[Litigation tactics]] — because applies-in adversarial proceedings - [[Evidence preservation]] — because extends to strategic disclosure <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - Document preservation obligations in open-source corporate disputes — potential OSPO guidance area - Trademark licensing agreements and discovery scope — how much financial transparency should be required? ### → Things 3 - [ ] Monitor final court ruling on discovery dispute for WordPress ecosystem implications #things - [ ] Track how trademark enforcement cases affect open-source project governance models #things <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/WP Engine, Inc. V. Automattic Inc. Et Al., No. 324-Cv-06917.md|WP Engine, Inc. V. Automattic Inc. Et Al., No. 3:24-Cv-06917 by Ajay S. Krishnan]] ## Highlights - WP Engine's case rests on a single proposition: that Defendants' conduct beginning in September 2024 destroved an otherwise healthy business and caused close to in damages-. (Wallace Decl., 23.) The documents Defendants seek demolish that proposition. They are WP Engine's own contemporaneous records—created by its management, controlling investor, banker, and strategy consultants- ([View Highlight](https://read.readwise.io/read/01ksstht7vmxqfvkhstmbfzh5y)) - Note: Defendants' core damages-theory rebuttal: WPE's case "rests on a single proposition" — that Defendants destroyed an otherwise healthy business since September 2024. Defendants argue WPE's OWN contemporaneous records (management, Silver Lake, bankers, strategy consultants) demolish that proposition. Direct attack on the damages framing. - Tags: wp-engine-financial-health, atom/literature/h1, damages-theory - negotiations were an effort to "resolve" the disputes, "close this out," avoid "motion practice," and implement a "balanced agreement" reached after "both sides made concessions." Declaration of Sara Jenkins ("Jenkins Decl."), \P 3-5. Neither side reserved any rights to later seek additional categories of financial documents and both parties proceeded in accordance with the agreement. ([View Highlight](https://read.readwise.io/read/01kssthtsrx8ddmxjzwx5ess1d)) - Note: Defendants' history of the reciprocal-agreement: "resolve" / "close this out" / "balanced agreement" / "both sides made concessions" / no rights reserved by either side. The procedural-history argument against WPE now seeking to expand financial-document categories beyond what was negotiated. - Tags: reciprocal-agreement, discovery-negotiations, atom/literature/h2