Silver Lake Controls WPE 🔗 **Source:** [Silver Lake Controls WPE](https://readwise.io/reader/document_raw_content/449370006) > [!note]+ Document Notes > ```markdown > > --- > tags: [litigation, WordPress, discovery] > author: [LaShondra Whitfield, David Zhang] > source: [MISSING] > reference: [https://readwise.io/reader/document_raw_content/449370006] > date created: 2026-04-29 00:00 > > --- > > # 🏷️ Title: Silver Lake Controls WPE > <!-- 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) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - Automattic moves to compel Silver Lake executives Lee Wittlinger and David Zhang to produce documents related to WP Engine (WPE). - Automattic argues Silver Lake has controlled WPE’s strategy and exit attempts and is withholding key discovery. - Stakeholders: Automattic/Mullenweg, WPE, Silver Lake, Wittlinger, Zhang, the court. - Risks: discovery delays, sanctions, adverse inferences, exposure of PE internal strategy. - Bottom line: Automattic seeks expedited, broad-but-targeted production from the two Silver Lake principals before depositions. ## 📖 Main Content - Automattic files a discovery motion asking Judge Krishnan to compel non‑parties Wittlinger and Zhang to search personal devices/accounts and produce documents responsive to narrowed RFPs 1, 4, 6, 9, 14, 22. - Automattic frames Silver Lake (SL) as the controlling investor in WPE since 2018, having bought a majority stake for $250M and placing three executives (including Wittlinger and Zhang) on WPE’s five‑person board, thereby “becoming the controlling force behind WPE’s strategy, finances, and M&A activity.” ([control description](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_00007_00002-00DJ&startLexposition=00000_00007&emphasizeText=becoming+the+controlling+force+behind+WPE%27s+strategy%2C+finances%2C+and+M%26A+activity)) - According to Automattic, SL pursued a lucrative liquidity event for years but failed because WPE’s “product and prospects did not support the inflated price SL wanted,” so SL and WPE allegedly turned to litigation to recoup “lost enterprise value” that actually stems from WPE’s own shortcomings and SL’s failed exit strategy. - Automattic asserts that Wittlinger and Zhang “sit at the center of that story,” controlling WPE’s key decisions, and that WPE itself identified Wittlinger as a person with discoverable information and put his communications at issue in its complaint. Zhang is described as deeply involved in WPE finance and M&A at a granular level. ([central-role description](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_00009_00004-004V&startLexposition=00000_00009&emphasizeText=The+Individuals+sit+at+the+center+of+that+story)) - Automattic says the non‑party executives, represented by the same counsel as WPE and SL, never claim irrelevance; instead they argue Automattic can get everything from WPE/SL productions. Automattic replies that: - The individuals are not WPE custodians; their personal files/devices are not in WPE’s production, and PE firms don’t share all internal deliberations with portfolio companies. - SL’s custodial productions for the individuals are “deficient,” with only ~270 documents, mostly non‑substantive; notable gaps include no text messages between Wittlinger and WPE CEO Heather Brunner despite WPE emails referencing such communications. ([deficient-production description](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_0000H_00002-003n&startLexposition=00000_0000H&emphasizeText=SL+has+produced+only+270+documents%2C+comprising+mainly+non-substantive+news+alerts%2C+calendar+invites)) - Automattic maintains it has significantly narrowed its requests (from 27 to 6 RFPs), limited time periods, and offered tailored search terms, even excluding documents already produced by WPE/SL. The individuals allegedly refused to: - Use the proposed search terms - Provide hit counts or burden details - Propose alternatives - Disclose what terms SL used for its own searches - Automattic cites cases on search terms not being work product and on non‑movants needing to substantiate burden. It argues the individuals’ close connection to the dispute defeats any claim that non‑party status should shield them from reasonable discovery. - Relief requested: an order compelling searches of personal devices/accounts for specific RFPs using Defendants’ search terms, with compliance within 48 hours of the court’s ruling, because depositions begin May 5, 2026 and fact discovery closes May 14, 2026. ([relief section](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_0000T_00002-000i&startLexposition=00000_0000L&emphasizeText=Relief+Requested+.+The+Court+should+compel+the+Individuals+to+search+their+personal+devices)) ### 🗒️ Notes - This is a discovery motion letter filed via ECF to Judge Krishnan, on behalf of Automattic Inc. and Matthew Mullenweg, signed by counsel at Coblentz Patch Duffy & Bass LLP. - Automattic characterizes Silver Lake as an “equity giant” that acquired majority control of WPE in January 2018 for $250M and installed three executives on a five‑member board, including Wittlinger (Managing Director) and Zhang (Director). ([SL control recap](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_00007_00002-00DJ&startLexposition=00000_00007&emphasizeText=In+January+2018%2C+SL+bought+a+majority+interest+in+Plaintiff+WP+Engine)) - Automattic frames SL’s overarching narrative: SL built a liquidity timeline aimed at profit, sought a sale for years, but failed because WPE’s fundamentals allegedly didn’t justify SL’s desired price, not because of Automattic’s conduct. - The motion accuses SL and WPE of using litigation as an alternative liquidity event: they purportedly seek to recover “lost enterprise value” through damages that they couldn’t secure in the market. - Central thesis: because SL controlled WPE’s value‑driving decisions and stands to gain most from any verdict, SL’s principals Wittlinger and Zhang are core witnesses whose private communications are highly relevant to causation and damages. - Automattic notes WPE’s own initial disclosures identify Wittlinger as having relevant information and the complaint references his communications, placing them at issue; discovery shows Zhang is deeply involved in finance and M&A at WPE. - Automattic alleges obstruction: plaintiffs claim Automattic impaired WPE’s value while simultaneously blocking discovery into the two SL executives who steered WPE’s strategy and finances. - On objections, Automattic says the individuals do not claim irrelevance; instead they rely on supposed duplication with WPE/SL productions. Automattic responds that PE firms maintain separate internal deliberations, analyses, and fiduciary‑driven communications that never enter the portfolio company’s files. - Automattic characterizes SL’s prior production as token: ~270 documents, mostly news alerts, calendar invites, one menu photo; critically, no pre‑Aug 2024 substantive documents and no text messages between Wittlinger and CEO Heather Brunner despite emails referencing such texts. - The motion details a lengthy meet‑and‑confer history where Automattic claims it reduced RFPs (27→6), narrowed time frames, proposed search terms, and offered to exclude already‑produced material, but the individuals’ counsel resisted on search methodology and burden without specifics. - Automattic invokes precedent that search terms are not work product and that alleged undue burden must be supported with detail; it cites cases endorsing discovery from closely involved non‑parties. - Urgency: depositions of the individuals are scheduled beginning May 5, 2026; fact discovery cutoff is May 14, 2026. Automattic asks for compliance within 48 hours of the order to avoid prejudice. ## 📚 References - Automattic’s description of Silver Lake’s control of WPE: [controlling force behind WPE strategy](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_00007_00002-00DJ&startLexposition=00000_00007&emphasizeText=becoming+the+controlling+force+behind+WPE%27s+strategy%2C+finances%2C+and+M%26A+activity) - Automattic’s claim that Wittlinger and Zhang “sit at the center” of the value story: [central individuals passage](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_00009_00004-004V&startLexposition=00000_00009&emphasizeText=The+Individuals+sit+at+the+center+of+that+story) - Description of SL’s limited and non‑substantive production: [270 documents, mostly non‑substantive](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_0000H_00002-003n&startLexposition=00000_0000H&emphasizeText=SL+has+produced+only+270+documents%2C+comprising+mainly+non-substantive+news+alerts%2C+calendar+invites) - Relief requested and timing: [expedited compliance section](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_0000T_00002-000i&startLexposition=00000_0000L&emphasizeText=Relief+Requested+.+The+Court+should+compel+the+Individuals+to+search+their+personal+devices) ## 🗣️ Paraphrase - Paragraph A paraphrase: Automattic asks the court to compel two Silver Lake executives, who effectively control WPE and its strategy, to produce documents from their personal devices and accounts using specific search terms, arguing that prior productions from WPE and SL are incomplete and that these individuals are central to the case. - Paragraph B paraphrase: Automattic claims Silver Lake tried and failed to sell WPE at an inflated valuation, then turned to litigation to recoup supposed “lost enterprise value,” while simultaneously resisting discovery into the very executives whose decisions shaped WPE’s performance, prompting Automattic’s request for expedited, targeted discovery relief. ## 📰 Newsletter Silver Lake’s control over WP Engine is emerging as a central thread in the ongoing Automattic–WPE litigation. A recent filing by Automattic argues that Silver Lake executives effectively steered WPE’s strategy and attempted exits, making their internal communications crucial to assessing “lost enterprise value” claims. For WordPress builders and hosts, this case underscores how private equity dynamics can influence product direction and pricing narratives—sometimes more than technical merit. Want to follow similar developments? - Track official Automattic statements: https://automattic.com/news - Review WordPress.org project updates: https://make.wordpress.org - Stay current with plugin and core security advisories: https://wordpress.org/news/category/security As always, keep your stacks well‑documented and your contracts precise—especially around data access and control—so discovery doesn’t become your biggest risk surface. ## ✅ Action Items #### DevRel - Map the litigation narrative into a neutral “WordPress governance & control” explainer for developers, clarifying Automattic vs WPE vs Silver Lake roles. - Prepare office‑hours or AMAs on legal‑adjacent topics: data portability, platform lock‑in, and how M&A can affect dev roadmaps. - Create sample contracts and policy templates emphasizing data ownership, logs retention, and subpoena readiness for plugin and agency teams. - Launch content series on “operating WordPress products when investors control the board,” with case‑study‑style anonymized stories. - Run surveys on developer trust in hosts, managed platforms, and PE‑backed vendors; feed results into product and comms planning. #### OSPO - Draft internal guidance on how PE or external investors interact with open‑source strategy, especially around governance and IP control. - Ensure license‑compliance scans and approval workflows account for portfolio companies and any litigation‑sensitive dependencies. - Define a vulnerability and legal hold coordination process so litigation discovery doesn’t conflict with security disclosure timelines. - Maintain a current SBOM for all critical WordPress infrastructure and hosting tools to simplify legal and security reviews. - Establish standing consultation hours with legal to review third‑party agreements that may constrain open‑source participation. - Create contribution funding frameworks (MoUs, SLAs) that survive ownership changes and protect upstream commitments. - Align KPIs and OKRs for open‑source participation with corporate risk, legal, and investor relations teams. #### Community - For maintainers: host clinics on governance hygiene, emphasizing board/investor oversight and its impact on technical direction. - For contributors: document how to protect autonomy (e.g., contributor license agreements, community charters) when corporate litigations arise. - For sponsors: standardize budget and reporting templates so funders see value without controlling governance. - For ecosystems: run cross‑project tabletop exercises simulating subpoenas, control shifts, or discovery orders, focusing on how to keep communities safe and productive. #### WordPress - Core: ensure governance documentation makes clear that WordPress.org direction is not dictated by any single company or investor. - Core Performance: insulate performance work from vendor‑specific business pressures; prioritize transparent metrics over marketing claims. - Core AI: codify guardrails ensuring training data, model integrations, and telemetry aren’t constrained by private commercial disputes. - **Core Program Team:** maintain clear rituals for conflict‑of‑interest disclosures when contributors are affiliated with litigating entities. - Mobile: review app data flows so logs and analytics can be isolated or redacted if discovery requests target specific vendors. - Playground: build “litigation‑safe” reproducible environments that can demonstrate behavior without exposing sensitive production data. - Community: strengthen WordCamp/meetup guidelines around vendor conflicts, sponsorship disclosures, and legal content framing. - Training: ship modules on “governance, funding, and legal basics for WordPress contributors.” - Marketing: avoid implying single‑vendor ownership or control of WordPress; emphasize project pluralism. - Support: develop escalation runbooks for users caught between overlapping vendor disputes (hosts vs SaaS vs agencies). - Design: propose UX patterns for clearer disclosures of data retention and jurisdiction across admin UIs. - Documentation: clarify relationships between WordPress.org, Automattic, and commercial distributors to reduce legal confusion. - Photos/TV: ensure contributor agreements cover use and takedown expectations if legal disputes arise. - Polyglots: keep translation teams independent of commercial influence; document conflict‑of‑interest norms. - Accessibility: ensure all governance and legal guidance is accessible, easy to read, and navigable. - Meta: improve .org tools to show sponsorships, affiliations, and potential conflicts clearly. - CLI: add commands or examples for exporting configs/logs safely when responding to subpoenas. - Hosting: coordinate common baseline discovery and logging practices that protect user privacy. - Tide: keep scoring transparent and insulated from commercial or legal pressure. - Openverse: document IP and takedown workflows clearly in case of legal conflicts. - Themes/Plugins: keep review and security processes independent of large commercial actors and litigation agendas. #### The WPOCC - Design fellowship or microgrant programs to support maintainers whose projects become collateral in vendor/legal battles. - Offer governance clinics focused on independence from investors and acquirers. - Pilot matched grants for projects that formalize charters limiting investor or acquirer capture. - Maintain transparent ledgers of funding, especially when sponsors have stakes in contentious litigation. ### FAIR - Prioritize technical independence: ensure governance data and logs can be verified independently (signatures, provenance). - Promote funding transparency around PE or corporate sponsors to flag potential capture. - Develop productized governance artifacts (model charters, operator agreements, scorecards) that explicitly address investor control and legal risk. ## 🧪 Hypotheses - H1: When a private equity firm holds board control over a WordPress‑centric company, its internal communications significantly shape the company’s alleged damages narrative in litigation. - H2: Courts are more likely to compel broad discovery from PE principals when they sit on portfolio company boards and are directly tied to disputed valuation decisions. - H3: PE portfolio exits that fail due to product/market constraints create incentives to pursue litigation as an alternative value‑recovery path. - H4: Non‑party status does not materially reduce discovery obligations for individuals who function as de facto decision‑makers in the core dispute. - H5: Narrowed, search‑term‑based RFPs increase judicial willingness to order expedited production from high‑level executives. ### 📊 Methodology - For H1/H3: Empirical legal study of PE‑backed tech firms involved in IP/contract disputes; code case dockets for references to failed exits, valuation disputes, and internal PE communications; correlate with damages theories. - For H2/H4: Compare federal discovery orders involving PE board members vs ordinary third parties; measure rates and scope of compelled production and timing relative to depositions. - For H5: Analyze discovery motions where requesting parties offered detailed search‑term protocols vs generic RFPs; track grant/deny rates and presence of expedited schedules. - Data sources: PACER/RECAP dockets, opinions databases, press releases, M&A filings, and case‑specific expert reports. - Analyses: logistic regression (likelihood of compulsion), survival analysis (time to order), and qualitative coding of judicial reasoning around control and burden. ### ❓ Questions - How often do PE firms controlling tech companies use litigation as a substitute for failed liquidity events? - What standards do courts apply when evaluating “burden” objections from high‑ranking non‑party executives? - How should WordPress‑adjacent companies structure governance to balance investor oversight with community and customer trust? - To what extent do internal PE valuations diverge from market realities in contested tech exits? - How might discovery into investor‑level strategy affect future PE appetite for deeply operational roles in open‑source ecosystems? ### 🔮 Future Research - Systematic mapping of investor control patterns across major WordPress ecosystem companies (hosts, SaaS platforms, agencies). - Case‑study series on how discovery fights over executives’ personal devices shape litigation outcomes in tech/IP disputes. - Comparative research on governance models that protect open‑source projects from investor capture and litigation spillover. - Surveys of maintainers and ecosystem partners about perceived risks when key actors are PE‑backed vs founder‑owned. - Design of “litigation‑resilient” data‑governance frameworks for open‑source‑centric businesses. ### 💡 Implications - Practice: WordPress companies should plan up front for subpoenas and discovery into executives’ personal devices when investor control is high. - Policy: Governance charters could limit investor influence over litigation strategy and damages framing. - Security: Logging, retention, and device‑management policies must consider both security and potential discovery obligations. - Education: Training for maintainers and tech leaders on basic litigation and discovery concepts is increasingly necessary. - Funding models: Community‑oriented funding (grants, foundations) may offer more alignment with open‑source values than tightly controlling PE structures. ### 🧠 Learning Styles Assessment - Reading level estimate: roughly Flesch–Kincaid Grade 14–16 (dense legal prose, case citations, long sentences). #### 👀 Visual learners - Present: essentially none—legal text only. - Improve: add flowcharts (timeline of SL investment, attempted exits, and litigation), org charts (SL–WPE–Automattic relationships), and simple diagrams of discovery request narrowing. #### 🔊 Aural learners - Present: none. - Improve: provide a short audio summary of the motion and a neutral “what this means” explainer. #### 🗣️ Verbal learners - Present: strong; detailed argumentation and defined legal positions. - Improve: add plain‑language callouts summarizing each section, with brief glossaries for terms like “non‑party,” “RFP,” and “undue burden.” #### 🧩 Kinesthetic learners - Present: none. - Improve: interactive exercises such as drafting a sample discovery request, role‑playing meet‑and‑confer negotiation, or mapping stakeholders in similar disputes. #### 🧠 Logical learners - Present: clear causal narrative (investment → control → failed exits → litigation → discovery fight), supported by legal citations. - Improve: add timelines, tables comparing requested vs produced documents, and decision trees for how the court might rule. #### 🧑‍🤝‍🧑 Social learners - Present: implicit—multiple parties with conflicting interests. - Improve: guided discussion prompts for meetups or study groups on ethics of investor control and litigation strategy. #### 🧘‍♀️ Solitary learners - Present: dense text suitable for solo close reading. - Improve: include reflection questions at the end (“How would this affect your company if you were WPE/Automattic?”) and self‑check quizzes on legal concepts. #### 🌿 Naturalistic learners - Present: not applicable. - Improve: analogies to ecosystem dynamics (investors as keystone species, litigation as environmental stressors) to ground abstract governance issues. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: as a PDF legal letter, likely minimal structural tagging. - Improve: add proper heading structure, document language metadata, and descriptive text for citations. #### Keyboard navigation - Present: PDF text is scrollable but lacks semantic navigation. - Improve: tag headings and sections so keyboard users can jump logically, ensure no interactive traps in any filing portals. #### Contrast and readability - Present: typical black text on white background; adequate contrast. - Improve: check line spacing and font size; offer HTML versions with adjustable themes. #### Text resizing and reflow - Present: PDF may not reflow perfectly at 200% zoom. - Improve: provide responsive HTML; ensure zoom and reflow don’t cause clipping or horizontal scrolling in narrow viewports. #### Media and captions - Present: none. - Improve: if summarised in video form, ensure captions and full transcripts; avoid auto‑playing media on hosting sites. #### Forms and interactions - Present: none inside the document. - Improve: ensure associated ECF or hosting interfaces meet target size and labeling requirements. #### Standards reference - Map gaps primarily to WCAG 2.2 AA criteria on structure (1.3.x), reflow (1.4.10), and text spacing (1.4.12). ### 🌍 DEIB Assessment #### Cultural breadth - Present: narrow US‑centric legal framing. - Improve: include comparative references to other jurisdictions’ approaches to investor control and discovery. #### Inclusive language - Present: formal, neutral legal language; minimal jargon explanation. - Improve: define specialized legal terms and avoid assuming familiarity with US federal procedure. #### Neurodiversity support - Present: long paragraphs, heavy citation density. - Improve: chunk content with consistent headings, bullet lists of key points, and summaries at section ends. #### Representation - Present: focused on institutions and executives; no explicit representation of broader community stakeholders. - Improve: consider including impacts on employees, users, and open‑source contributors, not just corporate actors. #### Psychological safety - Present: neutral legal tone; no inflammatory language. - Improve: add context sections in secondary materials explaining what this does and does not mean for everyday WordPress users. ### ✅ Logical Validity #### Strong reasoning - Automattic’s causal chain—Silver Lake controls WPE; its executives made core strategic decisions; their communications are therefore relevant—is a solid inductive argument backed by board‑control facts. - The narrowing of RFPs and offer to exclude already‑produced documents strengthens proportionality claims and rebuts undue‑burden arguments. - Citing case law on search terms and non‑party burden standards supports the move from facts to requested relief. #### Fallacies - Potential overstatement: implying that failed sale attempts “not because of anything Defendants did” were solely due to WPE shortcomings is asserted, not fully evidenced here; could be seen as a premature causal conclusion. A more precise framing would acknowledge alternative explanations while arguing why SL/WPE evidence is needed to adjudicate them. #### Tone of voice - Tone is adversarial but professional—typical of federal motion practice. - Language such as “obstruction” and highlighting trivial documents (e.g., a restaurant menu) is rhetorical, aiming to frame SL’s production as unserious without crossing into overt hostility. ### 🛡️ DARVO Analysis - Deny: Automattic implicitly denies responsibility for WPE’s alleged loss of enterprise value, shifting focus to WPE’s product/prospect weaknesses and SL’s exit strategy. - Attack: The motion characterizes SL’s and the individuals’ discovery posture as “obstruction” and their production as trivial, which challenges their credibility and cooperation. - Reverse victim/offender: There is a partial inversion: Automattic suggests SL and WPE, though plaintiffs, are leveraging litigation to recoup self‑inflicted losses and are simultaneously hindering fair discovery, positioning Automattic as the party needing court protection for access to evidence. - Emotional cues: Emphasis on a “smattering” of documents and items like a “photograph of a restaurant menu” serves to evoke judicial frustration at perceived gamesmanship rather than overt emotional appeals. ## 🎯 Conclusion Automattic’s filing argues that Silver Lake, as WPE’s controlling investor, and its executives Wittlinger and Zhang are central to the valuation and causation issues in the case. It claims SL’s prior productions are incomplete and seeks expedited, targeted discovery from the individuals’ personal devices and accounts. Practically, observers should watch how the court balances non‑party burden, investor control, and proportional discovery in this WordPress‑adjacent dispute. ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] 5–10-word present-tense claim > [!quote] [Silver Lake Controls WPE](https://readwise.io/reader/document_raw_content/449370006) by [[LaShondra Whitfield, David Zhang]] via an unnamed author. Published 2026-04-14T00:00:00+00:00. > “Silver Lake bought a majority interest in WPE and became the controlling force behind its strategy, finances, and M&A activity.” Two lines: context and use. Cite data if relevant. [view highlight](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_00007_00002-00DJ&startLexposition=00000_00007&emphasizeText=In+January+2018%2C+SL+bought+a+majority+interest+in+Plaintiff+WP+Engine) #xref #articleseed ID:rw_[MISSING] ### [H2] 5–10-word present-tense claim > [!quote] [Silver Lake Controls WPE](https://readwise.io/reader/document_raw_content/449370006) > “Automattic claims WPE’s lost enterprise value stems from WPE’s own shortcomings and Silver Lake’s failed exit strategy, not Automattic’s conduct.” Two lines: context and use. [view highlight](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_00007_00002-00DJ&startLexposition=00000_00007&emphasizeText=With+no+commercial+exit%2C+SL+and+WPE+initiated+this+litigation+to+try+to+recover+through+a+jury+verdict) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] Silver Lake exerts board-level control over WPE - Applies when SL holds majority and three of five board seats. - Pointer: investment and control description in the motion letter. - Links: [[Private-Equity-Control]] [[WordPress-Governance]] #### [Z2] Litigation replaces failed exits in some PE strategies - Applies when a PE-backed firm fails to achieve desired sale price. - Pointer: “lost enterprise value” and failed sale narrative. - Links: [[Investor-Incentives]] [[Strategic-Litigation]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Map major WordPress ecosystem companies and their investor control structures—context/https://readwise.io/reader/document_raw_content/449370006 #fleeting #inbox - [F2] Draft a “discovery basics for plugin authors” explainer—context/https://readwise.io/reader/document_raw_content/449370006 #fleeting #inbox - [F3] Design a governance template that limits investor influence over open-source litigation strategy—context/https://readwise.io/reader/document_raw_content/449370006 #fleeting #inbox --- # 🏷️ Title: Silver Lake Controls WPE ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - Automattic moves to compel Silver Lake executives Lee Wittlinger and David Zhang to produce documents related to WP Engine (WPE). - Automattic argues Silver Lake has controlled WPE’s strategy and exit attempts and is withholding key discovery. - Stakeholders: Automattic/Mullenweg, WPE, Silver Lake, Wittlinger, Zhang, the court. - Risks: discovery delays, sanctions, adverse inferences, exposure of PE internal strategy. - Bottom line: Automattic seeks expedited, broad-but-targeted production from the two Silver Lake principals before depositions. ## 📖 Main Content - Automattic files a discovery motion asking Judge Krishnan to compel non‑parties Wittlinger and Zhang to search personal devices/accounts and produce documents responsive to narrowed RFPs 1, 4, 6, 9, 14, 22. - Automattic frames Silver Lake (SL) as the controlling investor in WPE since 2018, having bought a majority stake for $250M and placing three executives (including Wittlinger and Zhang) on WPE’s five‑person board, thereby “becoming the controlling force behind WPE’s strategy, finances, and M&A activity.” ([control description](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_00007_00002-00DJ&startLexposition=00000_00007&emphasizeText=becoming+the+controlling+force+behind+WPE%27s+strategy%2C+finances%2C+and+M%26A+activity)) - According to Automattic, SL pursued a lucrative liquidity event for years but failed because WPE’s “product and prospects did not support the inflated price SL wanted,” so SL and WPE allegedly turned to litigation to recoup “lost enterprise value” that actually stems from WPE’s own shortcomings and SL’s failed exit strategy. - Automattic asserts that Wittlinger and Zhang “sit at the center of that story,” controlling WPE’s key decisions, and that WPE itself identified Wittlinger as a person with discoverable information and put his communications at issue in its complaint. Zhang is described as deeply involved in WPE finance and M&A at a granular level. ([central-role description](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_00009_00004-004V&startLexposition=00000_00009&emphasizeText=The+Individuals+sit+at+the+center+of+that+story)) - Automattic says the non‑party executives, represented by the same counsel as WPE and SL, never claim irrelevance; instead they argue Automattic can get everything from WPE/SL productions. Automattic replies that: - The individuals are not WPE custodians; their personal files/devices are not in WPE’s production, and PE firms don’t share all internal deliberations with portfolio companies. - SL’s custodial productions for the individuals are “deficient,” with only ~270 documents, mostly non‑substantive; notable gaps include no text messages between Wittlinger and WPE CEO Heather Brunner despite WPE emails referencing such communications. ([deficient-production description](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_0000H_00002-003n&startLexposition=00000_0000H&emphasizeText=SL+has+produced+only+270+documents%2C+comprising+mainly+non-substantive+news+alerts%2C+calendar+invites)) - Automattic maintains it has significantly narrowed its requests (from 27 to 6 RFPs), limited time periods, and offered tailored search terms, even excluding documents already produced by WPE/SL. The individuals allegedly refused to: - Use the proposed search terms - Provide hit counts or burden details - Propose alternatives - Disclose what terms SL used for its own searches - Automattic cites cases on search terms not being work product and on non‑movants needing to substantiate burden. It argues the individuals’ close connection to the dispute defeats any claim that non‑party status should shield them from reasonable discovery. - Relief requested: an order compelling searches of personal devices/accounts for specific RFPs using Defendants’ search terms, with compliance within 48 hours of the court’s ruling, because depositions begin May 5, 2026 and fact discovery closes May 14, 2026. ([relief section](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_0000T_00002-000i&startLexposition=00000_0000L&emphasizeText=Relief+Requested+.+The+Court+should+compel+the+Individuals+to+search+their+personal+devices)) ### 🗒️ Notes - This is a discovery motion letter filed via ECF to Judge Krishnan, on behalf of Automattic Inc. and Matthew Mullenweg, signed by counsel at Coblentz Patch Duffy & Bass LLP. - Automattic characterizes Silver Lake as an “equity giant” that acquired majority control of WPE in January 2018 for $250M and installed three executives on a five‑member board, including Wittlinger (Managing Director) and Zhang (Director). ([SL control recap](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_00007_00002-00DJ&startLexposition=00000_00007&emphasizeText=In+January+2018%2C+SL+bought+a+majority+interest+in+Plaintiff+WP+Engine)) - Automattic frames SL’s overarching narrative: SL built a liquidity timeline aimed at profit, sought a sale for years, but failed because WPE’s fundamentals allegedly didn’t justify SL’s desired price, not because of Automattic’s conduct. - The motion accuses SL and WPE of using litigation as an alternative liquidity event: they purportedly seek to recover “lost enterprise value” through damages that they couldn’t secure in the market. - Central thesis: because SL controlled WPE’s value‑driving decisions and stands to gain most from any verdict, SL’s principals Wittlinger and Zhang are core witnesses whose private communications are highly relevant to causation and damages. - Automattic notes WPE’s own initial disclosures identify Wittlinger as having relevant information and the complaint references his communications, placing them at issue; discovery shows Zhang is deeply involved in finance and M&A at WPE. - Automattic alleges obstruction: plaintiffs claim Automattic impaired WPE’s value while simultaneously blocking discovery into the two SL executives who steered WPE’s strategy and finances. - On objections, Automattic says the individuals do not claim irrelevance; instead they rely on supposed duplication with WPE/SL productions. Automattic responds that PE firms maintain separate internal deliberations, analyses, and fiduciary‑driven communications that never enter the portfolio company’s files. - Automattic characterizes SL’s prior production as token: ~270 documents, mostly news alerts, calendar invites, one menu photo; critically, no pre‑Aug 2024 substantive documents and no text messages between Wittlinger and CEO Heather Brunner despite emails referencing such texts. - The motion details a lengthy meet‑and‑confer history where Automattic claims it reduced RFPs (27→6), narrowed time frames, proposed search terms, and offered to exclude already‑produced material, but the individuals’ counsel resisted on search methodology and burden without specifics. - Automattic invokes precedent that search terms are not work product and that alleged undue burden must be supported with detail; it cites cases endorsing discovery from closely involved non‑parties. - Urgency: depositions of the individuals are scheduled beginning May 5, 2026; fact discovery cutoff is May 14, 2026. Automattic asks for compliance within 48 hours of the order to avoid prejudice. ## 📚 References - Automattic’s description of Silver Lake’s control of WPE: [controlling force behind WPE strategy](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_00007_00002-00DJ&startLexposition=00000_00007&emphasizeText=becoming+the+controlling+force+behind+WPE%27s+strategy%2C+finances%2C+and+M%26A+activity) - Automattic’s claim that Wittlinger and Zhang “sit at the center” of the value story: [central individuals passage](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_00009_00004-004V&startLexposition=00000_00009&emphasizeText=The+Individuals+sit+at+the+center+of+that+story) - Description of SL’s limited and non‑substantive production: [270 documents, mostly non‑substantive](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_0000H_00002-003n&startLexposition=00000_0000H&emphasizeText=SL+has+produced+only+270+documents%2C+comprising+mainly+non-substantive+news+alerts%2C+calendar+invites) - Relief requested and timing: [expedited compliance section](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_0000T_00002-000i&startLexposition=00000_0000L&emphasizeText=Relief+Requested+.+The+Court+should+compel+the+Individuals+to+search+their+personal+devices) ## 🗣️ Paraphrase - Paragraph A paraphrase: Automattic asks the court to compel two Silver Lake executives, who effectively control WPE and its strategy, to produce documents from their personal devices and accounts using specific search terms, arguing that prior productions from WPE and SL are incomplete and that these individuals are central to the case. - Paragraph B paraphrase: Automattic claims Silver Lake tried and failed to sell WPE at an inflated valuation, then turned to litigation to recoup supposed “lost enterprise value,” while simultaneously resisting discovery into the very executives whose decisions shaped WPE’s performance, prompting Automattic’s request for expedited, targeted discovery relief. ## 📰 Newsletter Silver Lake’s control over WP Engine is emerging as a central thread in the ongoing Automattic–WPE litigation. A recent filing by Automattic argues that Silver Lake executives effectively steered WPE’s strategy and attempted exits, making their internal communications crucial to assessing “lost enterprise value” claims. For WordPress builders and hosts, this case underscores how private equity dynamics can influence product direction and pricing narratives—sometimes more than technical merit. Want to follow similar developments? - Track official Automattic statements: https://automattic.com/news - Review WordPress.org project updates: https://make.wordpress.org - Stay current with plugin and core security advisories: https://wordpress.org/news/category/security As always, keep your stacks well‑documented and your contracts precise—especially around data access and control—so discovery doesn’t become your biggest risk surface. ## ✅ Action Items #### DevRel - Map the litigation narrative into a neutral “WordPress governance & control” explainer for developers, clarifying Automattic vs WPE vs Silver Lake roles. - Prepare office‑hours or AMAs on legal‑adjacent topics: data portability, platform lock‑in, and how M&A can affect dev roadmaps. - Create sample contracts and policy templates emphasizing data ownership, logs retention, and subpoena readiness for plugin and agency teams. - Launch content series on “operating WordPress products when investors control the board,” with case‑study‑style anonymized stories. - Run surveys on developer trust in hosts, managed platforms, and PE‑backed vendors; feed results into product and comms planning. #### OSPO - Draft internal guidance on how PE or external investors interact with open‑source strategy, especially around governance and IP control. - Ensure license‑compliance scans and approval workflows account for portfolio companies and any litigation‑sensitive dependencies. - Define a vulnerability and legal hold coordination process so litigation discovery doesn’t conflict with security disclosure timelines. - Maintain a current SBOM for all critical WordPress infrastructure and hosting tools to simplify legal and security reviews. - Establish standing consultation hours with legal to review third‑party agreements that may constrain open‑source participation. - Create contribution funding frameworks (MoUs, SLAs) that survive ownership changes and protect upstream commitments. - Align KPIs and OKRs for open‑source participation with corporate risk, legal, and investor relations teams. #### Community - For maintainers: host clinics on governance hygiene, emphasizing board/investor oversight and its impact on technical direction. - For contributors: document how to protect autonomy (e.g., contributor license agreements, community charters) when corporate litigations arise. - For sponsors: standardize budget and reporting templates so funders see value without controlling governance. - For ecosystems: run cross‑project tabletop exercises simulating subpoenas, control shifts, or discovery orders, focusing on how to keep communities safe and productive. #### WordPress - Core: ensure governance documentation makes clear that WordPress.org direction is not dictated by any single company or investor. - Core Performance: insulate performance work from vendor‑specific business pressures; prioritize transparent metrics over marketing claims. - Core AI: codify guardrails ensuring training data, model integrations, and telemetry aren’t constrained by private commercial disputes. - **Core Program Team:** maintain clear rituals for conflict‑of‑interest disclosures when contributors are affiliated with litigating entities. - Mobile: review app data flows so logs and analytics can be isolated or redacted if discovery requests target specific vendors. - Playground: build “litigation‑safe” reproducible environments that can demonstrate behavior without exposing sensitive production data. - Community: strengthen WordCamp/meetup guidelines around vendor conflicts, sponsorship disclosures, and legal content framing. - Training: ship modules on “governance, funding, and legal basics for WordPress contributors.” - Marketing: avoid implying single‑vendor ownership or control of WordPress; emphasize project pluralism. - Support: develop escalation runbooks for users caught between overlapping vendor disputes (hosts vs SaaS vs agencies). - Design: propose UX patterns for clearer disclosures of data retention and jurisdiction across admin UIs. - Documentation: clarify relationships between WordPress.org, Automattic, and commercial distributors to reduce legal confusion. - Photos/TV: ensure contributor agreements cover use and takedown expectations if legal disputes arise. - Polyglots: keep translation teams independent of commercial influence; document conflict‑of‑interest norms. - Accessibility: ensure all governance and legal guidance is accessible, easy to read, and navigable. - Meta: improve .org tools to show sponsorships, affiliations, and potential conflicts clearly. - CLI: add commands or examples for exporting configs/logs safely when responding to subpoenas. - Hosting: coordinate common baseline discovery and logging practices that protect user privacy. - Tide: keep scoring transparent and insulated from commercial or legal pressure. - Openverse: document IP and takedown workflows clearly in case of legal conflicts. - Themes/Plugins: keep review and security processes independent of large commercial actors and litigation agendas. #### The WPOCC - Design fellowship or microgrant programs to support maintainers whose projects become collateral in vendor/legal battles. - Offer governance clinics focused on independence from investors and acquirers. - Pilot matched grants for projects that formalize charters limiting investor or acquirer capture. - Maintain transparent ledgers of funding, especially when sponsors have stakes in contentious litigation. ### FAIR - Prioritize technical independence: ensure governance data and logs can be verified independently (signatures, provenance). - Promote funding transparency around PE or corporate sponsors to flag potential capture. - Develop productized governance artifacts (model charters, operator agreements, scorecards) that explicitly address investor control and legal risk. ## 🧪 Hypotheses - H1: When a private equity firm holds board control over a WordPress‑centric company, its internal communications significantly shape the company’s alleged damages narrative in litigation. - H2: Courts are more likely to compel broad discovery from PE principals when they sit on portfolio company boards and are directly tied to disputed valuation decisions. - H3: PE portfolio exits that fail due to product/market constraints create incentives to pursue litigation as an alternative value‑recovery path. - H4: Non‑party status does not materially reduce discovery obligations for individuals who function as de facto decision‑makers in the core dispute. - H5: Narrowed, search‑term‑based RFPs increase judicial willingness to order expedited production from high‑level executives. ### 📊 Methodology - For H1/H3: Empirical legal study of PE‑backed tech firms involved in IP/contract disputes; code case dockets for references to failed exits, valuation disputes, and internal PE communications; correlate with damages theories. - For H2/H4: Compare federal discovery orders involving PE board members vs ordinary third parties; measure rates and scope of compelled production and timing relative to depositions. - For H5: Analyze discovery motions where requesting parties offered detailed search‑term protocols vs generic RFPs; track grant/deny rates and presence of expedited schedules. - Data sources: PACER/RECAP dockets, opinions databases, press releases, M&A filings, and case‑specific expert reports. - Analyses: logistic regression (likelihood of compulsion), survival analysis (time to order), and qualitative coding of judicial reasoning around control and burden. ### ❓ Questions - How often do PE firms controlling tech companies use litigation as a substitute for failed liquidity events? - What standards do courts apply when evaluating “burden” objections from high‑ranking non‑party executives? - How should WordPress‑adjacent companies structure governance to balance investor oversight with community and customer trust? - To what extent do internal PE valuations diverge from market realities in contested tech exits? - How might discovery into investor‑level strategy affect future PE appetite for deeply operational roles in open‑source ecosystems? ### 🔮 Future Research - Systematic mapping of investor control patterns across major WordPress ecosystem companies (hosts, SaaS platforms, agencies). - Case‑study series on how discovery fights over executives’ personal devices shape litigation outcomes in tech/IP disputes. - Comparative research on governance models that protect open‑source projects from investor capture and litigation spillover. - Surveys of maintainers and ecosystem partners about perceived risks when key actors are PE‑backed vs founder‑owned. - Design of “litigation‑resilient” data‑governance frameworks for open‑source‑centric businesses. ### 💡 Implications - Practice: WordPress companies should plan up front for subpoenas and discovery into executives’ personal devices when investor control is high. - Policy: Governance charters could limit investor influence over litigation strategy and damages framing. - Security: Logging, retention, and device‑management policies must consider both security and potential discovery obligations. - Education: Training for maintainers and tech leaders on basic litigation and discovery concepts is increasingly necessary. - Funding models: Community‑oriented funding (grants, foundations) may offer more alignment with open‑source values than tightly controlling PE structures. ### 🧠 Learning Styles Assessment - Reading level estimate: roughly Flesch–Kincaid Grade 14–16 (dense legal prose, case citations, long sentences). #### 👀 Visual learners - Present: essentially none—legal text only. - Improve: add flowcharts (timeline of SL investment, attempted exits, and litigation), org charts (SL–WPE–Automattic relationships), and simple diagrams of discovery request narrowing. #### 🔊 Aural learners - Present: none. - Improve: provide a short audio summary of the motion and a neutral “what this means” explainer. #### 🗣️ Verbal learners - Present: strong; detailed argumentation and defined legal positions. - Improve: add plain‑language callouts summarizing each section, with brief glossaries for terms like “non‑party,” “RFP,” and “undue burden.” #### 🧩 Kinesthetic learners - Present: none. - Improve: interactive exercises such as drafting a sample discovery request, role‑playing meet‑and‑confer negotiation, or mapping stakeholders in similar disputes. #### 🧠 Logical learners - Present: clear causal narrative (investment → control → failed exits → litigation → discovery fight), supported by legal citations. - Improve: add timelines, tables comparing requested vs produced documents, and decision trees for how the court might rule. #### 🧑‍🤝‍🧑 Social learners - Present: implicit—multiple parties with conflicting interests. - Improve: guided discussion prompts for meetups or study groups on ethics of investor control and litigation strategy. #### 🧘‍♀️ Solitary learners - Present: dense text suitable for solo close reading. - Improve: include reflection questions at the end (“How would this affect your company if you were WPE/Automattic?”) and self‑check quizzes on legal concepts. #### 🌿 Naturalistic learners - Present: not applicable. - Improve: analogies to ecosystem dynamics (investors as keystone species, litigation as environmental stressors) to ground abstract governance issues. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: as a PDF legal letter, likely minimal structural tagging. - Improve: add proper heading structure, document language metadata, and descriptive text for citations. #### Keyboard navigation - Present: PDF text is scrollable but lacks semantic navigation. - Improve: tag headings and sections so keyboard users can jump logically, ensure no interactive traps in any filing portals. #### Contrast and readability - Present: typical black text on white background; adequate contrast. - Improve: check line spacing and font size; offer HTML versions with adjustable themes. #### Text resizing and reflow - Present: PDF may not reflow perfectly at 200% zoom. - Improve: provide responsive HTML; ensure zoom and reflow don’t cause clipping or horizontal scrolling in narrow viewports. #### Media and captions - Present: none. - Improve: if summarised in video form, ensure captions and full transcripts; avoid auto‑playing media on hosting sites. #### Forms and interactions - Present: none inside the document. - Improve: ensure associated ECF or hosting interfaces meet target size and labeling requirements. #### Standards reference - Map gaps primarily to WCAG 2.2 AA criteria on structure (1.3.x), reflow (1.4.10), and text spacing (1.4.12). ### 🌍 DEIB Assessment #### Cultural breadth - Present: narrow US‑centric legal framing. - Improve: include comparative references to other jurisdictions’ approaches to investor control and discovery. #### Inclusive language - Present: formal, neutral legal language; minimal jargon explanation. - Improve: define specialized legal terms and avoid assuming familiarity with US federal procedure. #### Neurodiversity support - Present: long paragraphs, heavy citation density. - Improve: chunk content with consistent headings, bullet lists of key points, and summaries at section ends. #### Representation - Present: focused on institutions and executives; no explicit representation of broader community stakeholders. - Improve: consider including impacts on employees, users, and open‑source contributors, not just corporate actors. #### Psychological safety - Present: neutral legal tone; no inflammatory language. - Improve: add context sections in secondary materials explaining what this does and does not mean for everyday WordPress users. ### ✅ Logical Validity #### Strong reasoning - Automattic’s causal chain—Silver Lake controls WPE; its executives made core strategic decisions; their communications are therefore relevant—is a solid inductive argument backed by board‑control facts. - The narrowing of RFPs and offer to exclude already‑produced documents strengthens proportionality claims and rebuts undue‑burden arguments. - Citing case law on search terms and non‑party burden standards supports the move from facts to requested relief. #### Fallacies - Potential overstatement: implying that failed sale attempts “not because of anything Defendants did” were solely due to WPE shortcomings is asserted, not fully evidenced here; could be seen as a premature causal conclusion. A more precise framing would acknowledge alternative explanations while arguing why SL/WPE evidence is needed to adjudicate them. #### Tone of voice - Tone is adversarial but professional—typical of federal motion practice. - Language such as “obstruction” and highlighting trivial documents (e.g., a restaurant menu) is rhetorical, aiming to frame SL’s production as unserious without crossing into overt hostility. ### 🛡️ DARVO Analysis - Deny: Automattic implicitly denies responsibility for WPE’s alleged loss of enterprise value, shifting focus to WPE’s product/prospect weaknesses and SL’s exit strategy. - Attack: The motion characterizes SL’s and the individuals’ discovery posture as “obstruction” and their production as trivial, which challenges their credibility and cooperation. - Reverse victim/offender: There is a partial inversion: Automattic suggests SL and WPE, though plaintiffs, are leveraging litigation to recoup self‑inflicted losses and are simultaneously hindering fair discovery, positioning Automattic as the party needing court protection for access to evidence. - Emotional cues: Emphasis on a “smattering” of documents and items like a “photograph of a restaurant menu” serves to evoke judicial frustration at perceived gamesmanship rather than overt emotional appeals. ## 🎯 Conclusion Automattic’s filing argues that Silver Lake, as WPE’s controlling investor, and its executives Wittlinger and Zhang are central to the valuation and causation issues in the case. It claims SL’s prior productions are incomplete and seeks expedited, targeted discovery from the individuals’ personal devices and accounts. Practically, observers should watch how the court balances non‑party burden, investor control, and proportional discovery in this WordPress‑adjacent dispute. ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] 5–10-word present-tense claim > [!quote] [Silver Lake Controls WPE](https://readwise.io/reader/document_raw_content/449370006) by [[LaShondra Whitfield, David Zhang]] via an unnamed author. Published 2026-04-14T00:00:00+00:00. > “Silver Lake bought a majority interest in WPE and became the controlling force behind its strategy, finances, and M&A activity.” Two lines: context and use. Cite data if relevant. [view highlight](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_00007_00002-00DJ&startLexposition=00000_00007&emphasizeText=In+January+2018%2C+SL+bought+a+majority+interest+in+Plaintiff+WP+Engine) #xref #articleseed ID:rw_[MISSING] ### [H2] 5–10-word present-tense claim > [!quote] [Silver Lake Controls WPE](https://readwise.io/reader/document_raw_content/449370006) > “Automattic claims WPE’s lost enterprise value stems from WPE’s own shortcomings and Silver Lake’s failed exit strategy, not Automattic’s conduct.” Two lines: context and use. [view highlight](https://read.readwise.io/read/01kqcv6s9tdn8s0nsq7zzj9c15?endLexposition=00000_00007_00002-00DJ&startLexposition=00000_00007&emphasizeText=With+no+commercial+exit%2C+SL+and+WPE+initiated+this+litigation+to+try+to+recover+through+a+jury+verdict) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] Silver Lake exerts board-level control over WPE - Applies when SL holds majority and three of five board seats. - Pointer: investment and control description in the motion letter. - Links: [[Private-Equity-Control]] [[WordPress-Governance]] #### [Z2] Litigation replaces failed exits in some PE strategies - Applies when a PE-backed firm fails to achieve desired sale price. - Pointer: “lost enterprise value” and failed sale narrative. - Links: [[Investor-Incentives]] [[Strategic-Litigation]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Map major WordPress ecosystem companies and their investor control structures—context/https://readwise.io/reader/document_raw_content/449370006 #fleeting #inbox - [F2] Draft a “discovery basics for plugin authors” explainer—context/https://readwise.io/reader/document_raw_content/449370006 #fleeting #inbox - [F3] Design a governance template that limits investor influence over open-source litigation strategy—context/https://readwise.io/reader/document_raw_content/449370006 #fleeting #inbox --- <!-- deep-read:sections end -->