WPEngine, Inc.  🔗 **Source:** [WPEngine, Inc.](https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.297.2.pdf) > [!note]+ Document Notes > tags: [wp-engine-automattic, sealing-motion, discovery-dispute, mullenweg-deposition, protective-order, wordpress-governance, confidential-information, administrative-motion] > author: WPEngine, Inc. > source: CourtListener RECAP - N.D. Cal. 4:24-cv-06917-AMO > filing_type: proposed order > docket: 297.2 > > # 🏷️ WPEngine's Administrative Motion to Seal Portions of Mullenweg Deposition Discovery Letter Exhibit > > # 🧭 Table of Contents > - Summary of sealing request > - Governance implications of sealed deposition materials > - Procedural analysis of protective order enforcement > - Questions about transparency in WordPress leadership disputes > > # 🔗 References > - **Dockets**: 297.2 (this filing) > - **Parties**: WPEngine, Inc. (plaintiff/movant), Automattic Inc., Matthew Charles Mullenweg, WooCommerce Inc. (defendants) > - **Court**: N.D. Cal. No. 4:24-cv-06917-AMO (Judge Martinez-Olguin; Mag. Judge Krishnan) > - **Discovery Deadline**: May 14, 2026 (closed) > > # 📝 Summary > WPEngine seeks to seal portions of Exhibit 3 to Michael Dore's Declaration supporting defendants' position in a joint discovery letter regarding Matthew Mullenweg's deposition. The proposed order would seal one highlighted portion (marked in GREEN) on page 3 of the exhibit. This administrative motion represents routine enforcement of existing protective orders governing confidential discovery materials, but occurs in the sensitive context of deposing WordPress's de facto leader about his "nuclear war" campaign against WPEngine. The sealing request suggests Mullenweg's deposition materials contain commercially sensitive or strategically damaging information that WPEngine considers protected under the case's confidentiality framework. > > # 📖 Main Content > <!-- deep-read:sections start --> ## 🗒️ Notes **Procedural Context**: Filed May 21, 2026, after fact discovery closed May 14, 2026, indicating this relates to end-of-discovery disputes about deposition testimony or exhibits. **Sealing Scope**: Limited to "first highlighted portion (in GREEN) at page 3" of Exhibit 3 to Michael Dore's Declaration, suggesting surgical redaction rather than wholesale sealing. **Joint Discovery Letter Framework**: The sealed exhibit supports defendants' portion of a joint letter regarding Mullenweg's deposition, indicating ongoing disputes about his testimony's scope, conduct, or admissibility. **Quinn Emanuel Representation**: WPEngine's motion filed by experienced IP/antitrust firm with six attorneys listed across Los Angeles, Redwood Shores, and San Francisco offices. **Magistrate Judge Oversight**: Discovery disputes handled by Mag. Judge Krishnan under standard referral for non-dispositive matters. # 📚 References - Michael Dore's Declaration in Support of Defendants' Portion of Joint Discovery Letter Re Mullenweg Deposition - Case protective order (referenced but not attached) - Administrative sealing procedures for N.D. Cal. # 🗣️ Paraphrase WPEngine filed a standard request to keep secret one specific section of a document that defendants used to argue their side of a disagreement about Matt Mullenweg's deposition. The court form shows they want to hide whatever is highlighted in green on page 3 of that document. This happened right after the discovery deadline, suggesting it's part of wrapping up fights about what testimony and evidence can be used at trial. # 📰 Governance Digest **What happened**: WPEngine wants to seal part of a court document about Matt Mullenweg's deposition in their lawsuit. **Why it matters**: Whatever Mullenweg said under oath was apparently sensitive enough that even references to it in legal briefs need protection. This suggests his deposition covered damaging territory about his WordPress leadership decisions or his campaign against WPEngine. **Bottom line**: The public won't get to see everything about how WordPress's leader justified his actions in this dispute, at least not yet. # 🧪 Hypotheses 1. **Commercially Sensitive Testimony**: Mullenweg's deposition revealed confidential business information about Automattic, WordPress.org operations, or strategic decisions 2. **Governance Admissions**: Sealed portions contain admissions about improper coordination between Automattic and WordPress Foundation 3. **Personal Financial Entanglement**: Content relates to Mullenweg's personal investment vehicles (Audrey Capital/HC) and their WordPress-related activities 4. **Strategic Communications**: Deposition covered internal communications about the "nuclear war" campaign that defendants want protected 5. **Third-Party Confidentiality**: Sealed material implicates confidential information about other parties (potentially Silver Lake or other WordPress ecosystem players) # 📊 Methodology **Procedural Basis**: Administrative motion under existing protective order framework; no substantive briefing on sealing standards suggests routine application of agreed-upon confidentiality protocols. **Evidentiary Foundation**: Not applicable - this is a sealing motion, not substantive evidence presentation. **Declaration Basis**: Michael Dore's declaration provides factual support for defendants' discovery position, but specific contents are sealed. # ❓ Questions - What did Mullenweg say under oath that requires sealing even in legal briefs? - Does the sealed content relate to WordPress Foundation governance or Automattic business strategy? - Will sealed deposition excerpts become public at trial or remain confidential throughout? - How does this sealing request compare to other confidentiality disputes in the case? - What discovery disputes remain about Mullenweg's deposition testimony? # 🔮 Future Research **Litigation Threads**: - Monitor for additional sealing disputes around Mullenweg deposition materials - Track whether sealed content emerges in summary judgment or trial filings - Watch for reciprocal sealing requests by defendants **WordPress Governance Threads**: - Assess whether deposition revelations affect WordPress Foundation independence claims - Monitor community reactions to leadership accountability gaps from sealed proceedings - Evaluate impact on WordPress trademark governance transparency # 💡 Implications **Practice**: Reinforces expectation that WordPress leadership disputes will involve significant confidential business information requiring protective orders. **Policy**: Highlights tension between public interest in WordPress governance transparency and legitimate confidentiality needs in commercial litigation. **Security**: Sealed materials may contain information about WordPress.org infrastructure, plugin directory security, or ecosystem vulnerabilities. **Education**: Limited public access to leadership deposition materials constrains community understanding of governance decisions. **Funding**: Confidential testimony may reveal business models, revenue sharing, or investment structures affecting WordPress ecosystem sustainability. # 🧠 Learning Styles Assessment **Visual**: Document structure with clear headings and case formatting supports visual learners; proposed order format provides clear outcome visualization. **Aural**: Legal terminology and procedural language may require verbal explanation for optimal comprehension. **Verbal**: Heavy legal jargon requires strong reading comprehension; benefits from plain-language paraphrasing. **Kinesthetic**: Static document provides limited hands-on engagement opportunities. **Logical**: Clear procedural framework and systematic sealing request structure appeals to logical learners. **Social**: Limited collaborative elements; benefits from group discussion of governance implications. **Solitary**: Well-suited for individual analysis and research. **Naturalistic**: Pattern recognition opportunities in comparing sealing requests across similar cases. **Reading Level**: Legal professional (graduate level) due to procedural complexity and case-specific terminology. # 📊 Accessibility Assessment **Text Extraction**: Fully text-extractable PDF with standard court formatting. **Structure**: Clear hierarchical organization with consistent headings and numbering. **Artifacts**: Minimal formatting artifacts; standard legal document structure. **WCAG 2.2 AA**: Meets basic accessibility standards for text-based legal documents; could benefit from enhanced heading structure for screen readers. # 🌍 DEIB Assessment **Cultural Breadth**: Standard U.S. federal court procedures; limited cultural context consideration. **Inclusive Language**: Formal legal language without obvious bias, but may exclude non-legal audiences. **Neurodiversity Support**: Structured format supports some neurodivergent preferences; dense legal language may create barriers. **Representation**: Corporate legal dispute between well-resourced parties; limited diversity considerations visible. **Psychological Safety**: Sealing motion itself promotes confidentiality, but reduces transparency for community stakeholders. # ✅ Logical Validity **Strong Reasoning**: Clear procedural basis for sealing request under existing protective order framework. **Fallacies**: None identified - straightforward administrative request without substantive argumentation. **Tone**: Professional, neutral legal tone appropriate for court filing. # 🛡️ DARVO Analysis Not applicable - this is an administrative sealing motion without substantive dispute characterization or blame attribution. # 🎯 Conclusion WPEngine's sealing motion represents routine discovery confidentiality enforcement but occurs in the critical context of WordPress leadership accountability. The surgical nature of the sealing request suggests strategically sensitive rather than broadly confidential information. Watch for: (1) court's ruling on the sealing request, (2) additional disputes over Mullenweg deposition materials, and (3) whether any sealed content surfaces in public trial proceedings. The broader question remains whether WordPress governance disputes can maintain necessary transparency while protecting legitimate business confidentiality. # 🧱 Refactor Appendix ## 📚 Literature Atoms > [!quote] "WPENGINE, INC.'S ADMINISTRATIVE MOTION TO SEAL PORTIONS OF EXHIBIT 3 TO MICHAEL DORE'S DECLARATION IN SUPPORT OF DEFENDANTS' PORTION OF JOINT DISCOVERY LETTER RE MULLENWEG DEPOSITION" > Document title establishing scope of sealing request > [!quote] "First highlighted portion (in GREEN) at page 3" > Specific identification of material to be sealed, indicating surgical rather than broad redaction > [!quote] "fact discovery closed May 14, 2026" > Timing context showing this as post-discovery cleanup rather than active investigation dispute ### 🧠 Permanent Candidates - Administrative sealing procedures in complex IP litigation - Protective order enforcement for executive depositions - Confidentiality tensions in open-source governance disputes - Discovery deadline management in multi-party litigation ### ✏️ Fleeting Queue - Relationship between sealed content and "nuclear war" campaign communications - Potential coordination between this sealing request and defendants' litigation strategy - Community transparency expectations versus litigation confidentiality requirements <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/WPEngine, Inc..md|WPEngine, Inc. by Rachel Herrick Kassabian, Yury Kapgan, Margret M. Caruso, Brian Mack, Michael E. Williams, Kevin Y. ...]] ## Highlights - 1 2 3 4 5 Before the Court is the Administrative Motion to Seal Portions of Exhibit 3 to Michael Dore's Declaration in Support of Defendants' Portion of Joint Discovery Letter Regarding Mullenweg Deposition (the "Administrative Motion") filed by Plaintiff WPEngine, Inc. ("WPE"). After reviewing the moving papers, the supporting declaration, and the document sought to be sealed (or portions thereof), the Court ORDERS as follows. ([View Highlight](https://read.readwise.io/read/01ksfvbmyb9jtwjf107jzjwz3t)) - Note: Docket 297.2: Proposed order on the seal motion. - Tags: wp-engine-automattic, legal