Proposed Order Re: Defendants' and Counterclaimants' Administrative Motion to Seal  🔗 **Source:** [Proposed Order Re: Defendants' and Counterclaimants' Administrative Motion to Seal](https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.303.2.pdf) > [!note]+ Document Notes > tags: [wp-engine-automattic, discovery-dispute, sealing-motion, acf-plugin, deposition-documents, wordpress-governance, poulson-deposition, protective-order] > author: Defendants and Counterclaimants (Automattic, Mullenweg, WordPress Foundation, WooCommerce) > source: CourtListener RECAP - N.D. Cal. 4:24-cv-06917-AMO > filing_type: proposed order > docket: 303.2 > > # 🏷️ Proposed Sealing Order for ACF Deposition Documents > > # 🧭 Table of Contents > - [Summary](#-summary) > - [Main Content](#-main-content) > - [Governance Digest](#-governance-digest) > - [Implications](#-implications) > - [Conclusion](#-conclusion) > > # 🔗 References > - **Dockets**: 303.2 (this filing), unspecified joint letter brief docket > - **Rules**: Fed. R. Civ. P. 30(b)(6) (corporate depositions) > - **Parties**: Automattic Inc., Matthew Mullenweg, WordPress Foundation, WooCommerce Inc. (movants); WPEngine Inc. (opposing party) > - **Personnel**: Mag. Judge Ajay S. Krishnan, Iain Poulson (deponent), Ilissa Samplin (declarant), Kaitlin Keohane (declarant) > > # 📝 Summary > This proposed order would seal documents related to Iain Poulson's April 10, 2026 Rule 30(b)(6) deposition concerning ACF (Advanced Custom Fields) plugin materials. The WordPress parties seek partial sealing of a joint letter brief and full sealing of an exhibit from WPEngine's counsel's declaration. The magistrate judge has preliminarily found "good cause to seal," indicating sensitive information emerged during discovery about Automattic's controversial takeover of the ACF plugin. This sealing motion suggests the deposition revealed commercially sensitive or strategically damaging information about how Automattic forked WPEngine's ACF plugin into "Secure Custom Fields" and assumed control of its wordpress.org directory listing. > > # 📖 Main Content > <!-- deep-read:sections start --> ## 🗒️ Notes **Procedural Posture** - Filed May 22, 2026, within discovery phase (closed May 14, 2026) - Administrative motion to seal under Mag. Judge Krishnan's authority - References April 10, 2026 Rule 30(b)(6) deposition of Iain Poulson - Joint letter brief filed regarding "ACF-related documents identified during" deposition **Sealing Scope** - **Partial sealing**: Joint letter brief (docket number not filled in) - **Full sealing**: Exhibit 2 to Declaration of Kaitlin Keohane (WPEngine counsel) - WordPress parties bear burden to substantiate sealing need - Court preliminarily finds "good cause to seal" **Key Personnel** - **Iain Poulson**: Corporate deponent under Rule 30(b)(6), likely Automattic representative - **Ilissa Samplin**: Declarant supporting sealing motion (WordPress parties' counsel) - **Kaitlin Keohane**: WPEngine counsel whose exhibit faces full sealing **ACF Context Significance** - ACF (Advanced Custom Fields) was WPEngine's valuable plugin - Automattic forked it into "Secure Custom Fields" - Automattic assumed control of ACF's wordpress.org directory listing - This represents core disputed conduct in Mullenweg's "nuclear war" campaign # 📚 References - Case caption: WPEngine, Inc. v. Automattic Inc., et al., Case No. 4:24-cv-06917-AMO-ASK - Federal Rules of Civil Procedure Rule 30(b)(6) - N.D. Cal. sealing procedures and good cause standard # 🗣️ Paraphrase The WordPress companies want to hide some documents that came up during a deposition about the ACF plugin takeover. They're asking the court to keep secret parts of a legal brief they wrote together, and to completely seal an exhibit that WPEngine's lawyers submitted. The magistrate judge has tentatively agreed there's good reason to keep this information under wraps. This suggests the April deposition of Iain Poulson revealed sensitive details about how Automattic seized control of WPEngine's valuable plugin and its official WordPress directory presence. # 📰 Governance Digest **Plugin Directory Power Play Goes Under Seal** The court battle over WordPress governance just got more secretive. Automattic and friends want to hide documents from a deposition about their controversial takeover of WPEngine's popular ACF plugin—you know, the one they renamed "Secure Custom Fields" while somehow gaining control of its official WordPress.org listing. A magistrate judge has tentatively agreed there's "good cause" to seal these materials, which probably means the April deposition revealed some pretty damaging details about how the plugin directory can be weaponized. When even the legal briefs need to be partially redacted, you know someone said the quiet part out loud about how WordPress.org's governance really works behind the scenes. # 🧪 Hypotheses 1. **Poulson deposition revealed internal Automattic communications** showing deliberate strategy to seize ACF plugin and directory control 2. **WordPress.org directory governance mechanisms** are more centrally controlled by Automattic than publicly acknowledged 3. **Commercial sensitivity** involves Automattic's revenue calculations from ACF plugin takeover 4. **Joint letter brief contains admissions** about Automattic/WordPress Foundation coordination that undermines claimed independence 5. **WPEngine's exhibit** documents specific technical steps Automattic used to assume directory control 6. **Sealing motion timing** (post-discovery closure) suggests most damaging materials emerged in final depositions # 📊 Methodology **Procedural Basis**: Administrative motion under magistrate judge authority for discovery-related sealing. **Evidentiary Foundation**: Declaration of Ilissa Samplin supporting sealing need, though specific grounds not detailed in proposed order. **Personal Knowledge**: Not specified for declarants, though Samplin likely has attorney knowledge of case strategy and Keohane has counsel knowledge of client materials. # ❓ Questions 1. What specific ACF-related revelations emerged in Poulson's deposition requiring sealing? 2. How does Automattic's internal decision-making process for plugin directory control compare to public WordPress governance narratives? 3. What role did WordPress Foundation play in facilitating ACF plugin takeover? 4. Are there other WPEngine plugins subject to similar directory control mechanisms? 5. How will sealed materials affect summary judgment arguments about trademark and plugin directory governance? # 🔮 Future Research **Litigation**: Monitor whether sealing order affects public understanding of summary judgment briefs; track if sealed materials leak through other discovery or testimony. **WordPress Governance**: Investigate plugin directory submission/control procedures; examine other instances of directory listing disputes; assess WordPress Foundation's actual independence from Automattic operational decisions. # 💡 Implications **Practice**: Plugin developers face uncertainty about directory listing security and control mechanisms. **Policy**: WordPress.org governance structures may need transparency reforms if sealed materials reveal excessive Automattic control. **Security**: Plugin ecosystem stability threatened if directory control can be arbitrarily transferred. **Education**: Community needs clearer documentation of plugin directory governance procedures. **Funding**: Commercial plugin developers may seek alternative distribution channels if directory control is unreliable. # 🧠 Learning Styles Assessment **Visual**: Court filing structure with clear docket organization. **Aural**: Moderate—legal terminology may need verbal explanation. **Verbal**: High—technical legal language throughout. **Kinesthetic**: Low—abstract procedural concepts. **Logical**: High—systematic sealing motion framework. **Social**: Moderate—multi-party coordination evident. **Solitary**: High—individual document analysis suitable. **Naturalistic**: Low—artificial legal categorization system. **Reading Level**: Legal professional (graduate level 16-18). # 📊 Accessibility Assessment **Format**: Text-extractable PDF with standard court formatting. **Structure**: Clear headings and numbered sections support screen readers. **Artifacts**: Minimal line number interference. **WCAG 2.2 AA**: Generally compliant though legal language creates cognitive load barriers. # 🌍 DEIB Assessment **Cultural Breadth**: Limited to U.S. federal court procedures. **Inclusive Language**: Standard legal terminology, not exclusionary. **Neurodiversity Support**: Structured format aids processing, though legal complexity creates barriers. **Representation**: Corporate litigation context limits diverse perspectives. **Psychological Safety**: Adversarial legal context inherently creates tension. # ✅ Logical Validity **Strong Reasoning**: Procedural motion follows established court sealing protocols. **Fallacies**: None apparent in procedural document. **Tone**: Neutral administrative court language appropriate for proposed order format. # 🛡️ DARVO Analysis Not applicable to this source—administrative sealing motion contains procedural requests rather than victim/perpetrator narratives. # 🎯 Conclusion This sealing motion signals that Automattic's ACF plugin takeover involved more damaging internal deliberations than previously public. The magistrate's preliminary "good cause" finding suggests Poulson's deposition revealed commercially or strategically sensitive information about WordPress.org directory control mechanisms. **Watch next**: Whether the actual sealing order issues, and how redacted materials affect public portions of summary judgment briefing about plugin directory governance and WordPress Foundation independence claims. # 🧱 Refactor Appendix ## 📚 Literature Atoms > [!quote] "Joint Letter Brief ("Letter Brief") regarding ACF-related documents identified during the April 10, 2026 Rule 30(b)(6) deposition of Iain Poulson" > [!quote] "finds good cause to seal" > [!quote] "WordPress Parties" bear "burden to substantiate need to seal" ### 🧠 Permanent Candidates **Plugin Directory Control Mechanisms**: How WordPress.org directory listings can be transferred or seized, as revealed in sealed Poulson deposition materials. **Rule 30(b)(6) Corporate Deposition Strategy**: Use of corporate representative depositions to obtain institutional knowledge about plugin governance decisions. **ACF Plugin Takeover Documentation**: Internal Automattic materials about forking WPEngine's plugin and assuming directory control. ## ✏️ Fleeting Queue - Connection between WordPress Foundation's claimed independence and actual plugin directory governance - Timing significance of sealing motion after discovery closure - Relationship between Poulson's role and ACF-related decision-making authority <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/Proposed Order Re Defendants' and Counterclaimants' Administrative Motion to Seal-2.md|Proposed Order Re: Defendants' and Counterclaimants' Administrative Motion to Seal by Araceli Martinez-Olguín]] ## Highlights - The Court has considered Defendants' and Counterclaimants' Administrative Motion to File Under Seal in connection with the Joint Letter Brief ("Letter Brief") regarding ACF-related documents identified during the April 10, 2026 Rule 30(b)(6) deposition of Iain Poulson [Dkt. \_\_], the Declaration of Ilissa Samplin in Support thereof, and finds good cause to seal. ([View Highlight](https://read.readwise.io/read/01ksfva503kh1rapw5e8gk4h5m)) - Note: Docket 303.2: Proposed order granting sealing. - Tags: legal, wp-engine-automattic