Exhibit B  🔗 **Source:** [Exhibit B](https://readwise.io/reader/document_raw_content/449369965) > [!note]+ Document Notes > tags: [discovery-dispute, letter-brief-process, protective-order, wordpress-foundation, financial-discovery, privilege-claims, document-production, wordpress-governance] > author: Gibson Dunn (Automattic's counsel) > source: CourtListener RECAP - N.D. Cal. 4:24-cv-06917-AMO > filing_type: exhibit > docket: 293.3_1 > > # 🏷️ Automattic's Defense of Discovery Disputes and WordPress Foundation Privilege Claims > > # 🧭 Table of Contents > - [References](#-references) > - [Summary](#-summary) > - [Main Content](#-main-content) > - [Paraphrase](#-paraphrase) > - [Governance Digest](#-governance-digest) > - [Hypotheses](#-hypotheses) > - [Methodology](#-methodology) > - [Questions](#-questions) > - [Future Research](#-future-research) > - [Implications](#-implications) > - [Assessments](#-learning-styles-assessment) > - [Conclusion](#-conclusion) > - [Refactor Appendix](#-refactor-appendix) > > # 🔗 References > - **Docket:** 293.3_1 (Exhibit B) > - **Referenced Docket:** 270 (WPE's prior argument about standing order violations) > - **Court Rule:** Standing Order requiring joint letter brief process > - **Document IDs:** A8C01236177, A8C01519175 (AEO designated), A8C00960055, A8C00964484, A8C00972765 > - **Discovery Cutoff:** August 15, 2025 > > # 📝 Summary > > Gibson Dunn's Ariel Fishman responds to three WP Engine discovery letter briefs filed at the last minute, arguing that WPE violated the Court's joint letter brief process by sending drafts too late for meaningful collaboration. The letter reveals key WordPress governance issues: Automattic claims no financial benefit from WordPress.org operations, asserts attorney-client privilege over WordPress Foundation communications with counsel engaged in November 2025, and argues that no audit report exists. The filing exposes the contested relationship between Automattic and the WordPress Foundation while defending against document production demands that could reveal the true governance structure of WordPress.org. > > # 📖 Main Content > <!-- deep-read:sections start --> ## 🗒️ Notes **Procedural Violations:** - WPE sent three draft letter briefs at 10:54pm, 2:28am, and 3:04am on filing deadline - Gibson Dunn claims this precluded required joint letter brief process under Court's Standing Order - Automattic provided their portions "well in advance" of deadline - Forces WPE to file unilaterally if they proceed **Sealing/Privilege Issues:** - Documents A8C01236177 and A8C01519175 designated "AEO" (Attorney Eyes Only) - Davies deposition transcript provisionally designated AEO - WPE's draft brief failed to identify material requiring sealed filing **WordPress Foundation Governance:** - Grayson & Company counsel engaged November 2025 (post-discovery cutoff) - No audit report completed - Related communications claimed as privileged - Automattic refuses to log post-cutoff privileged documents **Financial Relationship Claims:** - Automattic categorically denies financial benefit from WordPress.org: "No documents exist. WordPress.org does not operate for Automattic's financial benefit." - This directly contradicts WPE's theory of the case about Automattic's control **Document Production:** - "Pricing Trademarks for Hosting Companies" documents were produced (A8C00960055, A8C00964484, A8C00972765) - No response document from Mullenweg exists - Automattic claims WPE didn't conduct basic searches before demanding documents # 📚 References Primary sources: Court Standing Order (joint letter brief requirement), discovery cutoff agreement (August 15, 2025), protective order governing AEO designations, Docket 270 (WPE's prior procedural arguments). # 🗣️ Paraphrase Automattic's lawyers are essentially saying: "WP Engine waited until the last minute to send us their draft legal briefs about discovery disputes, giving us no time to work together as the court requires. If they want to complain to the judge, they'll have to do it alone, and we'll tell the court they didn't follow the rules. Also, they forgot to mark confidential information that needs to be sealed. Regarding the WordPress Foundation, we hired lawyers in November 2025 after discovery ended, no audit is done, and those conversations are privileged attorney-client communications. We don't have to list privileged documents that came after the discovery deadline. Most importantly, Automattic gets no financial benefit from running WordPress.org - no such documents exist because it doesn't happen. And those trademark pricing documents WP Engine claims we're hiding? We already gave them three versions." # 📰 Governance Digest The WordPress civil war's discovery phase reveals Automattic's official position: WordPress.org operates independently without financial benefit to Automattic. Meanwhile, the WordPress Foundation lawyered up with Grayson & Company after this lawsuit heated up, and those conversations are now locked behind attorney-client privilege. Translation: Automattic claims the open-source project it de facto controls doesn't actually benefit it financially (surprising exactly no one who's watched this drama unfold), while the Foundation that's supposed to be independent immediately hired lawyers when the governance questions got serious. The privilege claims suggest some very interesting conversations happened about WordPress Foundation operations that the community will never see. # 🧪 Hypotheses 1. **Privilege Shield Hypothesis:** WordPress Foundation's November 2025 legal engagement creates an attorney-client privilege shield around governance documents that would otherwise reveal Automattic's control mechanisms. 2. **Financial Separation Theory:** Automattic's categorical denial of WordPress.org financial benefits indicates either genuine operational separation or careful structural insulation from direct monetary flows. 3. **Discovery Timing Strategy:** The post-cutoff Foundation counsel engagement suggests reactive legal positioning rather than proactive governance documentation. 4. **Document Production Gaps:** WPE's failure to locate already-produced documents indicates either inadequate discovery management or strategic pressure tactics. 5. **Procedural Warfare Hypothesis:** Late-night brief submissions represent deliberate circumvention of collaborative discovery processes to gain tactical advantage. # 📊 Methodology This exhibit represents correspondence between opposing counsel during fact discovery phase (closed May 14, 2026). The evidentiary basis consists of: procedural deadlines and standing orders, document production logs with specific Bates numbers, deposition transcript designations, and privilege logs. The methodology is correspondence-based rather than declaration-based, so no personal knowledge foundation is required. # ❓ Questions - What governance changes occurred at WordPress Foundation between August and November 2025 that triggered legal counsel engagement? - How does Automattic's "no financial benefit" claim reconcile with its control over WordPress.org plugin directory and trademark enforcement? - What substantive governance discussions are now protected by the Foundation's attorney-client privilege? - Why did WPE fail to locate already-produced trademark pricing documents in their own discovery review? - What audit was contemplated for WordPress Foundation, and why was it never completed? # 🔮 Future Research **Litigation threads:** Joint letter brief process disputes, potential sanctions motions, sealed filing procedures, privilege challenges over Foundation communications, document production enforcement. **WordPress governance:** Foundation independence claims, financial separation between Automattic and WordPress.org, governance audit proposals, legal representation decisions, trademark pricing policies for hosting companies. # 💡 Implications **Practice:** WordPress plugin developers should understand that WordPress.org governance structures remain contested, with Automattic claiming operational independence while WPE alleges control. **Policy:** The Foundation's immediate legal engagement suggests governance policies may be developed reactively through litigation rather than proactive community input. **Security:** Privilege claims over Foundation governance communications reduce transparency into decision-making processes affecting the WordPress ecosystem. **Education:** The community should recognize that financial relationships between Automattic and WordPress.org remain disputed facts, not settled governance principles. **Funding:** Understanding of how WordPress.org operations are funded and whether they benefit Automattic remains unclear pending litigation resolution. # 🧠 Learning Styles Assessment **Visual:** Document ID references and timeline structure support visual learners. **Aural:** Legal argument structure follows logical progression suitable for auditory processing. **Verbal:** Technical legal language requires high reading comprehension. **Kinesthetic:** Limited hands-on elements; primarily text-based. **Logical:** Strong logical structure with cause-effect relationships. **Social:** Adversarial context highlights stakeholder conflicts. **Solitary:** Dense legal content requires individual focus. **Naturalistic:** Pattern recognition valuable for understanding discovery disputes. **Reading Level:** Graduate/professional (legal terminology, complex procedural concepts). # 📊 Accessibility Assessment **Structure:** Well-organized with clear sender/recipient/subject headers and numbered points. **Extractability:** Fully text-extractable email format. **WCAG Compliance:** Standard email format meets basic accessibility requirements. **Barriers:** Legal jargon and document ID references may challenge comprehension without context. # 🌍 DEIB Assessment **Cultural Breadth:** Limited - primarily US legal system context. **Inclusive Language:** Professional but adversarial tone may create barriers. **Neurodiversity:** Dense legal text without summary or plain language alternatives. **Representation:** Corporate legal perspective dominates. **Psychological Safety:** Adversarial framing could inhibit community engagement with governance issues. # ✅ Logical Validity **Strong Reasoning:** Clear procedural arguments about standing order compliance and timeline management. **Fallacies:** Potential strawman fallacy in characterizing WPE's document requests as unreasonable without addressing underlying merits. **Tone:** Professional but defensive, appropriate for legal correspondence context. # 🛡️ DARVO Analysis **Deny:** Automattic denies financial benefit from WordPress.org operations and existence of responsive documents. **Attack:** Criticizes WPE's discovery practices and procedural compliance. **Reverse:** Positions WPE as the party violating court procedures while defending Automattic's privilege claims. Classic DARVO pattern in litigation context where substantive governance questions are reframed as procedural disputes. # 🎯 Conclusion This discovery correspondence reveals the contested nature of WordPress governance, with Automattic claiming operational independence from WordPress.org while asserting privilege over Foundation governance communications. The procedural disputes mask substantive questions about financial relationships and control mechanisms that remain central to WordPress's future governance structure. Watch for privilege challenges and document production enforcement as the case progresses. # 🧱 Refactor Appendix ## 📚 Literature Atoms > [!quote] Financial Independence Claim > "No documents exist. WordPress.org does not operate for Automattic's financial benefit." > [!quote] Foundation Privilege Shield > "Counsel at Grayson & Company was engaged in November 2025, after the parties' agreed-upon August 15, 2025 end date for productions. No audit report has been completed. And, as explained, any related communications are privileged." > [!quote] Procedural Violation Allegation > "These draft briefs are deficient and violate this Court's Standing Order, as you precluded the joint letter brief process required under the Standing Order." ## 📚 Permanent Candidates **WordPress Foundation Legal Engagement:** November 2025 timing suggests reactive legal positioning during active litigation rather than proactive governance counsel. **Financial Separation Claims:** Categorical denial of Automattic financial benefits from WordPress.org operations represents core governance dispute. **Privilege-Protected Governance:** Attorney-client privilege now shields WordPress Foundation governance discussions from public scrutiny. ## ✏️ Fleeting Queue - Connection between Foundation audit discussions and legal engagement timing - Relationship between trademark pricing policies and hosting company governance - Strategic implications of post-discovery legal counsel engagement <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/Exhibit B.md|Exhibit B by readwise.io]] ## Highlights - Counsel, Defendants have made a document production available on an FTP site which you were invited to on March 7. Defendants’ production is marked A8C01534202 - A8C01537969. The password for the zipped productions will follow separately. The production completes Defendants’ and Counterclaimants’ production from Matt Mullenweg’s custodial files. Consistent with the disclosure we made to you in January 2026, the production contains the as-yet unproduced responsive, non- privileged documents identified pursuant to a reasonable search of the following sources, which contained data in the timeframes identified below, subject to our disclosure of search terms and date-limiters, including the parties’ agreed-upon cut- o� of August 15, 2025. ([View Highlight](https://read.readwise.io/read/01kqd0adrzwyj455971k8xmcnz))