WP Engine, Inc. V. WordPress Parties  🔗 **Source:** [WP Engine, Inc. V. WordPress Parties](https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.287.0.pdf) > [!note]+ Document Notes > tags: [attorney-client-privilege, discovery-dispute, trademark-licensing, wp-engine-automattic, business-strategy, wordpress-governance, privilege-log, in-camera-review] > author: Joint letter brief (WP Engine and WordPress Parties) > source: CourtListener RECAP - N.D. Cal. 4:24-cv-06917-AMO > filing_type: joint letter brief > docket: 287.0 > > # 🏷️ WP Engine v. WordPress Parties: Joint Discovery Letter Brief on Privilege Redactions (Dkt. 287.0) > > # 🧭 Table of Contents > - Summary & Stakes > - Main Content: Privilege Battle Over Business Strategy > - Governance Implications > - Future Threads & Questions > > # 🔗 References > **Dockets:** 287.0 (this filing), 215-2, 196 > **Rules:** FRCP 1, 26(b)(5), 30(b)(6) > **Cases:** *United States v. Graf* (9th Cir. 2010), *In re Grand Jury* (9th Cir. 2021), *Wisk Aero LLC v. Archer Aviation Inc.* (N.D. Cal. 2023), *Upjohn Co. v. United States* (1981) > **Evidence:** WPE Bates nos. WPE00615508, WPE00615479, WPE00615496, WPE00616276, WPE00630098 > > # 📝 Summary > This joint letter brief to Magistrate Judge Krishnan concerns WP Engine's redaction of one sentence from a 10-page business strategy presentation about trademark licensing negotiations with Automattic. WordPress Parties argue the redaction improperly conceals unfavorable business facts under attorney-client privilege. WP Engine counters that the sentence reflects in-house counsel's legal analysis. The dispute reveals WP Engine's internal assessment of trademark licensing benefits—directly contradicting executive testimony that WP Engine never considered such payments necessary. For WordPress governance, this illuminates the business calculations behind trademark licensing disputes and the intersection of legal strategy with open-source project control. > > # 📖 Main Content > <!-- deep-read:sections start --> ## 🗒️ Notes **The Redacted Document** - August 2024 slide deck by VP Corporate Development Victor Yuan to CEO Heather Brunner - Subject: Analysis of Automattic's partnership/trademark licensing proposal - One sentence redacted from Slide 5 under attorney-client privilege claim - Deck marked "Confidential" but not "Privileged" **WordPress Parties' Challenge** - Redaction conceals WP Engine's business assessment of trademark licensing benefits - Contradicts CEO and 30(b)(6) depositions denying WP Engine considered such payments - Document authored by non-lawyer, sent to non-lawyers, no counsel copied - Primary purpose was business strategy, not legal advice **WP Engine's Defense** - Privilege log identifies redacted sentence as legal analysis by General Counsel Chad Costello - Yuan and Costello declarations confirm redaction reflects legal analysis - Privilege protects legal advice even when incorporated into business documents - Attorney involvement need not appear in email chains to maintain privilege **Legal Standard Dispute** - Ninth Circuit: Primary purpose must be legal advice, not business advice - Where clear business purpose exists, communication must not have been made absent privilege - In-house counsel creates heightened scrutiny for privilege claims # 📚 References - *Upjohn Co. v. United States*, 449 U.S. 383 (1981) - corporate attorney-client privilege - *Wisk Aero LLC v. Archer Aviation Inc.*, 2023 WL 2699971 (N.D. Cal. 2023) - business strategy redactions - Yuan Declaration, Costello Declaration, Dore Declaration with exhibits # 🗣️ Paraphrase WordPress Parties say WP Engine is hiding embarrassing business facts behind fake privilege claims. They point to an August 2024 slide deck where WP Engine's business team analyzed why paying Automattic for trademark licenses would benefit WP Engine. This contradicts WP Engine executives who testified they never thought such payments were necessary. The deck wasn't written by lawyers, wasn't sent to lawyers, and wasn't marked privileged. WP Engine responds that one redacted sentence reflects their lawyer's legal analysis, which remains privileged even when included in business documents. They've provided sworn statements from both the document author and their General Counsel confirming the redacted content was legal advice. The judge must decide whether to force WP Engine to reveal the redacted sentence or review it privately first. # 📰 Governance Digest **WordPress's trademark tango gets messier.** Court papers reveal WP Engine's internal strategy documents analyzed the "benefits" of paying Automattic for WordPress trademark licenses—contradicting WP Engine executives who claimed they never considered such payments necessary. One redacted sentence has both sides lawyering hard over attorney-client privilege. Translation: Someone's story about trademark licensing doesn't add up, and the evidence might be in that blacked-out sentence. For WordPress's community governance, this shows how trademark control creates real business leverage that companies calculate in spreadsheets, not just legal theories. # 🧪 Hypotheses 1. **The redacted sentence quantifies specific business benefits of trademark licensing** - Would explain why WordPress Parties view it as contradicting executive testimony 2. **WP Engine's privilege assertion is strategic delay rather than good faith** - Pattern of redacting damaging business facts under privilege claims 3. **In-house counsel involvement was minimal consultation, not primary purpose** - Business team drove analysis with legal review as secondary consideration 4. **The document reveals WP Engine's internal trademark risk assessment** - May show company believed infringement claims had merit 5. **WordPress Parties leaked document context to pressure settlement** - Detailed knowledge of redacted content suggests broader discovery strategy # 📊 Methodology **Evidentiary Basis:** Document discovery with competing privilege assertions supported by declarations from Yuan (document author) and Costello (General Counsel) asserting personal knowledge of legal consultation. WordPress Parties rely on document structure, metadata, and deposition testimony to infer business purpose. No in-camera review conducted yet. # ❓ Questions - Will Judge Krishnan order in-camera review or rule based on the privilege log and declarations? - How does this privilege dispute affect the substantive trademark claims? - What other WP Engine strategy documents might face similar challenges? - Does the timing (August 2024, months into negotiations) suggest calculated privilege assertions? # 🔮 Future Research **Litigation Threads:** Privilege rulings on other WP Engine redactions; substantive discovery on trademark licensing negotiations; CEO and 30(b)(6) testimony impeachment **Governance Threads:** WordPress Foundation's trademark licensing policies; community input on trademark enforcement; separation between Automattic commercial interests and WordPress.org governance # 💡 Implications **Practice:** Privilege logs must provide specific, not boilerplate, justifications for redactions involving in-house counsel **Policy:** Open-source trademark control creates complex business calculations that may undermine community governance claims **Security:** Trademark disputes can expose internal risk assessments and business strategies **Funding:** Companies may budget for trademark licensing as business necessity rather than legal principle # 🧠 Learning Styles Assessment **Visual:** Document structure analysis, slide deck format, redaction patterns **Aural:** Deposition testimony excerpts, legal argument structure **Verbal:** Technical legal terminology, privilege doctrine explanation **Kinesthetic:** Discovery motion practice, document review process **Logical:** Legal standard application, burden of proof analysis **Social:** Corporate team communications, lawyer-client relationships **Solitary:** Individual document creation, privilege assertion strategy **Naturalistic:** Business environment patterns, corporate behavior classification **Reading Level:** Graduate/Professional (complex legal concepts, procedural terminology) # 📊 Accessibility Assessment **Structure:** Well-organized with clear headings and section breaks **Format:** Text-extractable legal document with standard citation formats **Tables:** Minimal table artifacts; primarily narrative text **WCAG 2.2 AA:** Would benefit from enhanced heading hierarchy and list formatting for screen readers # 🌍 DEIB Assessment **Cultural Breadth:** US legal system focus; corporate governance context **Inclusive Language:** Formal legal terminology accessible to legal professionals **Neurodiversity Support:** Clear logical structure with numbered sections **Representation:** Corporate legal dispute among established technology companies **Psychological Safety:** Adversarial legal context with professional tone maintained # ✅ Logical Validity **Strong Reasoning:** Both sides present coherent legal theories with case law support **Fallacies:** WordPress Parties' structural inference about redacted content approaches *post hoc* reasoning without direct evidence **Tone:** Professional adversarial tone appropriate for discovery dispute # 🛡️ DARVO Analysis Not applicable to this source - This is a legal privilege dispute over document redactions, not involving victim-offender dynamics or abuse allegations. # 🎯 Conclusion This privilege battle over one redacted sentence reveals the high stakes in WP Engine's trademark strategy disclosure. The outcome will likely determine whether WP Engine's internal business calculations about trademark licensing become public evidence contradicting their litigation position. For WordPress governance, this case continues to expose how trademark control creates real commercial leverage that companies assess in business terms, not just legal principles. **Watch for:** Judge Krishnan's privilege ruling and any in-camera review scheduling. # 🧱 Refactor Appendix ## 📚 Literature Atoms > [!quote] WordPress Parties' Core Argument > "WP Engine has redacted a key sentence from a ten-page business strategy deck that was not prepared by counsel, not sent to or from counsel, and not marked privileged—and it has done so under a boilerplate 'legal analysis' label." > [!quote] Contradicted Executive Testimony > "CEO Heather Brunner testified that WP Engine [REDACTED]. Victor Yuan, WP Engine's VP of Corporate Development and its Rule 30(b)(6) designee on the term-sheet negotiations, testified that [REDACTED]. The redacted deck shows otherwise." > [!quote] WP Engine's Privilege Defense > "WPE has unequivocally established privilege over the single redacted sentence in the challenged slide deck: it has provided a privilege log identifying the sentence as legal analysis of in-house counsel Chad Costello, and also has provided a sworn declaration from Victor Yuan—the document's author—confirming that the redacted sentence reflects the legal analysis provided by Mr. Costello." > [!quote] Legal Standard - Primary Purpose Test > "To meet that burden, WP Engine must show that 'the primary purpose of' the redacted communication was 'to give or receive legal advice, as opposed to business ... advice.'" ## 🧠 Permanent Candidates #### Privilege Log Specificity Requirements Courts require detailed justification for privilege claims beyond boilerplate assertions #### In-House Counsel Heightened Scrutiny Business-embedded attorneys face additional burden to establish legal advice purpose #### Corporate Intermediary Doctrine Privilege can extend through non-attorney employees when conveying legal advice #### Business Purpose Exception Communications with clear business purpose require showing they wouldn't exist without legal purpose ## ✏️ Fleeting Queue - Connection between trademark risk assessment and open-source governance legitimacy - Pattern of WP Engine privilege assertions across multiple document categories - Role of Silver Lake investment in trademark licensing calculation - Intersection of discovery timing and settlement pressure tactics <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/WP Engine, Inc. V. WordPress Parties.md|WP Engine, Inc. V. WordPress Parties by Dore, Heather Brunner, Victor Yuan]] ## Highlights - WPE has unequivocably established privilege over the single redacted sentence in the challenged slide deck: it has provided a privilege log identifying the sentence as legal analysis of in-house counsel Chad Costello, and also has provided a sworn declaration from Victor Yuan—the document's author—confirming that the redacted sentence *reflects the legal analysis provided by Mr. Costello* . In disregard of this clear record, Defendants' spurious motion urges the Court to ignore sworn testimony and compel production anyway, based on Defendants' sheer speculation that the redacted sentence is "business strategy" rather than legal analysis. Defendants' insistence on burdening the Court with motion practice over a single redacted sentence in a 10-page slide deck, based on pure conjecture, reflects their fundamental failure to honor the letter and spirit of FRCP 1. Defendants' motion should be denied. ([View Highlight](https://read.readwise.io/read/01ksfvgq5d82wn5f58w233mgcz)) - Note: Docket 287: WPE defends privilege over a single redacted sentence (in-house counsel Costello analysis). - Tags: wp-engine-automattic, legal