WPEngine, Inc. v. Automatic Inc. et al. 🔗 **Source:** [WPEngine, Inc. v. Automatic Inc. et al.](https://readwise.io/reader/document_raw_content/449369972) > [!note]+ Document Notes > tags: [legal, wordpress, discovery] > author: [MISSING] > source: [MISSING] > reference: [https://readwise.io/reader/document_raw_content/449369972] > date created: 2026-04-29 00:00 > > # 🏷️ Title: WPEngine, Inc. v. Automatic Inc. et al. > <!-- 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 - What happened: WP Engine accuses Matt Mullenweg/Automattic of failing to preserve and produce WhatsApp, Signal, and Telegram messages; defendants deny spoliation and say they performed a diligent search. - Why it matters: Centered on e-discovery preservation duties and potential Rule 37(e) sanctions in a high-profile WordPress-related dispute. - Key stakeholders: WP Engine, Automattic, Matt Mullenweg, federal court (N.D. Cal.), WordPress ecosystem. - Risks and tradeoffs: Sanctions, adverse inferences, reputational damage, plus cost and delay if further discovery ordered. - Bottom line: WP Engine seeks declarations and sanctions leverage; defendants frame it as a late, meritless tactic after WP Engine’s substantive claims allegedly weakened. ## 📖 Main Content - WP Engine outlines a timeline from 2024–2026 of preservation demands, alleged deletions (X posts, plugin reviews, Slack channel), and repeated unfulfilled promises to produce ephemeral-app messages, arguing spoliation is “inescapable.” - They highlight “Signal with disappearing messages” invitations and the near-absence of produced WhatsApp/Signal/Telegram content, requesting a detailed sworn declaration and reserving Rule 37(e) sanctions. - Defendants respond that they searched all work sources plus Signal/WhatsApp, produced thousands of communications (including personal emails, iMessages, Telegram, Slack screenshots, X DMs), and found no relevant WhatsApp messages. - They emphasize that ephemeral functions were never enabled, that message histories go back many years, and that WP Engine identified no contact who used the public Signal invitation. - Defendants characterize WP Engine’s motion as a “manufactured controversy” filed late to salvage a case that “has now collapsed on the merits,” asserting WP Engine has no damages and is litigating as a substitute for failed M&A efforts. - Uncertainties: whether any messages were actually lost; whether alternative sources (screenshots, other custodians) fully substitute; how the judge will weigh credibility and timelines. ### 🗒️ Notes - Joint discovery letter to Judge Krishnan (N.D. Cal.) dated April 10, 2026 regarding Mullenweg’s WhatsApp, Signal, and Telegram communications. - WP Engine position: - Sent early preservation demands covering WhatsApp, Signal, Telegram and other platforms, tying duty to preserve to at least September 2024. - Points to public statements about a “nuclear war” on WPE and directing people to contact Mullenweg via “Signal with disappearing messages,” plus deletions of X posts, plugin reviews, and a Post Status Slack channel. - Chronology: preservation demand (Sept 2024), document requests including messaging apps (Nov 2024), discovery of deletions (late 2024–Jan 2025), counsel’s acknowledgments and assurances (Feb–Apr 2025), repeated follow-ups (Oct 2025–Feb 2026), and minimal production (one Signal message, ~40 Telegram, no WhatsApp) by April 9, 2026. - Argues defendants’ earlier representation that messages “have been or will be produced” was false, inferring that responsive messages “indisputably existed” and were destroyed. - Requests court-ordered sworn declaration detailing use, preservation steps, auto-delete settings, and date ranges for preserved vs. deleted communications; also confirmation and completion of production for X DMs and Slack screenshots; reserves right to seek sanctions under Rule 37(e). - Defendants’ position: - Characterize motion as “manufactured controversy” and “litigation tactic” at the “eleventh hour” in a case that “has now collapsed on the merits.” - Claim diligent search of all work sources plus Signal and WhatsApp (which they say Mullenweg does not use for work), producing thousands of communications, including personal emails, Telegram messages, Signal message, X DMs, iMessages, and Slack screenshots. - State that no relevant or responsive WhatsApp messages were identified and that ephemeral messaging functions on WhatsApp/Signal/Telegram were never activated. - Note WPE has never identified a person who took up the public Signal invitation and that message histories on those apps extend back years. - Argue WPE is seeking declarations and production of materials that have already been provided; assert the motion is moot and based on “baseless conjecture.” - Reframe merits: allege WPE lost no customer due to defendants, suffered from internal mismanagement and market forces, and used litigation after failing to sell at desired valuation. - Suggest remaining issues can be addressed in Mullenweg’s upcoming deposition. - Core legal hook: Federal Rule of Civil Procedure 37(e) and case law on when preservation duties arise and what constitutes spoliation for ephemeral or app-based messages. ## 📚 References - WP Engine, Inc. v. Automattic Inc. et al., No. 3:24-cv-06917 (N.D. Cal.) — joint discovery letter re: messaging apps (April 10, 2026). - Fed. R. Civ. P. 37(e) (failure to preserve electronically stored information). - HUB Bellevue Props., LLC, 2020 WL 2512872 (W.D. Wash. May 15, 2020) (cited in the letter regarding when duty to preserve is triggered). - Public X.com post referenced: `https://x.com/photomatt/status/1837291862136365107` (Signal with disappearing messages). ## 🗣️ Paraphrase - Paragraph A paraphrase: WP Engine contends that despite clear preservation demands and obvious relevance, Mullenweg/Automattic either deleted or failed to preserve key WhatsApp, Signal, and Telegram messages, and now seeks a sworn declaration plus potential sanctions. - Paragraph B paraphrase: Automattic responds that it conducted a reasonable search, produced all responsive messages from work and related accounts, never enabled auto-deletion on the apps, and that WP Engine’s motion is a late-stage attempt to create a discovery scandal after its substantive case weakened. ## 📰 Newsletter The WP ecosystem is watching a major U.S. lawsuit unfold: WP Engine alleges Automattic CEO Matt Mullenweg failed to preserve key WhatsApp, Signal, and Telegram messages, while Automattic calls the dispute a manufactured discovery sideshow. Whatever the outcome, this is a reminder for hosts, agencies, and product teams: document your incident-response and data-retention policies, especially around chat tools and “disappearing” messages. Consider regular legal/ops reviews of Slack, Telegram, and ticketing practices to avoid surprise discovery headaches. ## ✅ Action Items #### DevRel - Developer advocacy: Prepare neutral, factual talking points explaining that the litigation is separate from core WordPress contribution and plugin development; avoid legal commentary. - Education: Draft a short guide for developers on logging, auditability, and support-channel recordkeeping. - Developer experience: Ensure API and webhook docs highlight recommended logging strategies for production sites. - Developer marketing: Emphasize reliability, audit trails, and observability features in any relevant campaigns. - Community management: Moderate discussions about the case in official spaces to keep them factual and non-defamatory. - Internal/external/cross-project: Create a feedback loop with legal and trust/safety teams for handling subpoenas and data requests. #### OSPO - Policy & Governance: Define open-source communication and record-retention policies for project leads using chat platforms. - License Compliance: Ensure dependency and contribution review processes include basic audit trails. - Security Management: Add guidance on secure-yet-preservable channels for coordinating vulnerability disclosures. - Software Inventory: Maintain clear ownership and retention expectations for CI logs, issue trackers, and incident reports. - Developer Support: Offer office hours with legal/compliance to answer high-level questions around logs and data retention. - Community Engagement: Clarify expectations for project leadership communications that could become part of legal discovery. - Strategic Alignment: Track KPIs on compliance training coverage for leads and maintainers. #### Community - Maintainers: Run “governance/ops” clinics on how to handle sensitive discussions without relying solely on self-deleting chats. - Contributors: Provide onboarding material on using issue trackers and PR threads for substantive decisions. - Sponsors: Share transparent documentation of governance, escalation, and incident-handling processes. - Ecosystem: Coordinate cross-project tabletop exercises on how to respond if communications are subpoenaed. #### WordPress - Core: Encourage use of public tickets for technical decisions; minimize key architectural debates in private chats. - Core Performance: Keep performance experiments documented in trac/PRs rather than ephemeral channels. - Core AI: Document AI-related decisions, datasets, and evaluation methods in durable locations. - **Core Program Team:** Establish expectations for which discussions can be private vs. must be logged in public tools. - Mobile: Ensure incident and release retrospectives are written up in durable docs. - Playground: Document experiment matrices and test harness decisions in repos. - Community: Update WordCamp/meetup organizer handbooks with light-touch guidance on records and sensitive conversations. - Training: Add modules on compliance-aware communication for sponsors and organizers. - Marketing: Keep campaign planning docs in systems with retention rather than only in private chats. - Support: Ensure support escalations and resolutions are logged in ticketing systems. - Design: Capture design decisions and rationale in tickets, not just Figma or chat. - Documentation: Track doc decisions and review processes in an auditable manner. - Photos: Clarify retention policy for submissions and moderation notes. - TV: Ensure caption and moderation workflows have sufficient logs. - Polyglots: Record key glossary and policy decisions in permanent threads. - Accessibility: Document accessibility decisions and audits in trac or GitHub. - Meta: Review .org infrastructure logs and retention policies. - CLI: Capture roadmap discussions and design choices in issues/notes. - Hosting: Work with hosts on minimum observability and logging guidance. - Tide: Maintain transparent documentation on scoring changes and review processes. - Openverse: Keep ingestion and moderation decisions well logged. - Themes: Document review outcomes and rationale in the review system. - Plugins: Ensure security and policy decisions in plugin reviews have durable records. #### The WPOCC - Programs: Consider governance and ops training for maintainers on legal and discovery basics. - Projects: Run “governance clinic” sessions on communication channels and retention. - Funding experiments: Encourage grant proposals that improve transparency and documentation for key community infrastructure. ### FAIR - Technical independence: Promote tooling that allows local export/backup of moderation and incident records. - Policies and covenants: Encourage clear funding and governance covenants that include transparency and record-keeping. - Productized governance artifacts: Offer reusable charters and operator agreements that specify communication and logging expectations. ## 🧪 Hypotheses - H1: Clear, enforced preservation policies for messaging platforms significantly reduce discovery disputes in tech companies. - H2: Public statements about “disappearing messages” meaningfully increase courts’ willingness to infer spoliation. - H3: Organizations relying heavily on ephemeral messaging for business decisions face higher litigation risk and legal spend. - H4: Transparent, documented decision-making in public trackers decreases suspicion around missing chat messages. ### 📊 Methodology - Study designs: - Retrospective case-study analysis of federal e-discovery sanctions orders involving chat apps. - Survey of in-house counsel on preservation practices for Slack, Signal, WhatsApp, Telegram. - Comparative analysis of organizations before/after implementing strict communication-retention policies. - Data sources: PACER rulings, law firm client surveys, internal policy documents (anonymized), incident reports. - Analyses: Logistic regression of sanctions likelihood vs. policy strength; thematic coding of judicial reasoning; cost comparison of discovery disputes. ### ❓ Questions - Under what circumstances will courts infer intent to deprive from use of apps with disappearing messages? - How should open-source leaders balance privacy/security with legal preservation duties? - What minimum retention baseline is reasonable for small companies and non-profits? - How can the WordPress project model good documentation and communication practices without excessive bureaucracy? ### 🔮 Future Research - Empirical mapping of e-discovery disputes involving encrypted/ephemeral apps. - Best-practice frameworks for OSS communities on governance communications. - Tooling to export and sanitize chat histories for legal preservation without over-collection. - Economic modeling of the cost of over-retention vs. under-retention in small tech orgs. ### 💡 Implications - Practice: Companies should formalize policies on which channels are appropriate for substantive decisions and ensure logs exist where needed. - Policy: Courts may increasingly reference explicit guidance on ephemeral messaging when setting sanctions and expectations. - Security: Need to align secure communications with accountability; not all sensitive talk should be unlogged. - Education: Legal, security, and engineering teams benefit from joint training on chat, logging, and discovery. - Funding models: Foundations and community orgs may need resources for better ops and compliance infrastructure. ### 🧠 Learning Styles Assessment - Reading level estimate: Approx. U.S. Grade 13–14 (college-level), based on dense legal syntax and citations (Flesch-Kincaid style approximation). #### 👀 Visual learners - Present: Structured headings, date-based timelines. - Improve: Add flowcharts of discovery timelines, diagrams of communication channels, and simple timeline graphics. #### 🔊 Aural learners - Present: None specified. - Improve: Provide an audio summary of the dispute and a short explainer podcast episode. #### 🗣️ Verbal learners - Present: Detailed legal narrative, citations, quotes. - Improve: Add plain-language callouts and short glossary of discovery terminology. #### 🧩 Kinesthetic learners - Present: None. - Improve: Interactive exercises (e.g., mock discovery response, designing a preservation plan). #### 🧠 Logical learners - Present: Chronological argument, references to rules and case law. - Improve: Tables comparing claims vs. evidence, decision trees for when preservation duties start. #### 🧑‍🤝‍🧑 Social learners - Present: Adversarial positions illustrating negotiation dynamics. - Improve: Discussion prompts for teams on how they’d handle similar preservation issues. #### 🧘‍♀️ Solitary learners - Present: Text suitable for careful solo study. - Improve: Reflection questions about one’s own team’s communication and retention practices. #### 🌿 Naturalistic learners - Present: None. - Improve: Analogies to ecosystem balance (e.g., logs as environmental records over time) and sustainability of governance. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear headings and section labels in the letter. - Improve: Ensure any web rendering has proper heading hierarchy and language attributes. #### Keyboard navigation - Present: Not applicable to PDF text itself. - Improve: When published on the web, confirm full keyboard navigation and meaningful focus indicators. #### Contrast and readability - Present: Standard black-on-white legal formatting is usually high contrast. - Improve: Increase line spacing and paragraph breaks for better legibility online. #### Text resizing and reflow - Present: PDF may not reflow gracefully. - Improve: Offer HTML or EPUB versions that reflow at 200% zoom without horizontal scrolling. #### Media and captions - Present: Text only. - Improve: Provide audio recordings with transcripts and proper labeling if turned into multimedia. #### Forms and interactions - Present: None. - Improve: N/A. #### Standards reference - Map potential web presentation to WCAG 2.2 AA, especially 1.4.x (contrast), 1.3.1 (structure), 2.1.x (keyboard). ### 🌍 DEIB Assessment #### Cultural breadth - Present: U.S.-centric legal framing. - Improve: Add context on how other jurisdictions handle e-discovery and privacy. #### Inclusive language - Present: Formal legal language, mostly neutral. - Improve: Provide plain-language summaries to broaden accessibility beyond legal professionals. #### Neurodiversity support - Present: Consistent headings and structure. - Improve: More subheadings, summaries, and bulleting to reduce cognitive load. #### Representation - Present: Corporate parties and law firms only. - Improve: Acknowledge broader community impact (developers, users) where relevant. #### Psychological safety - Present: Formal tone, no direct harassment language. - Improve: In community discussions about the case, ground guidelines to avoid personal attacks. ### ✅ Logical Validity #### Strong reasoning - WP Engine: Uses a chronological chain of demands, assurances, and minimal production to infer likely spoliation; strength is in specific dates and repeated unmet promises. - Defendants: Appeal to concrete facts (no ephemeral settings, long message histories, volume of produced data) to argue against deletion and to question WPE’s inference. #### Fallacies - Possible overstatement: - WPE’s “inescapable conclusion” that destruction occurred rests on indirect evidence; courts might see this as overconfident inference rather than proven fact. - Defendants’ assertion that WPE’s case “collapsed” and therefore the motion is purely tactical risks ad hominem/circumstantial reasoning; they could instead focus on factual mootness. #### Tone of voice - WP Engine: Accusatory and insistent, using phrases like “make no mistake” and “inescapable conclusion.” - Defendants: Combative and dismissive, calling the motion a “manufactured controversy” and “rank speculation.” ### 🛡️ DARVO Analysis - Deny: Defendants deny any spoliation, stressing that ephemeral functions were never activated and that all responsive materials have been produced. - Attack: They portray WP Engine’s motion as “manufactured,” “distortion,” and “rank speculation,” questioning WP Engine’s motives and credibility. - Reverse victim/offender: They recast WP Engine as the aggressor using litigation to compensate for failed business strategies, suggesting Automattic is the party being unfairly targeted rather than a potential wrongdoer. ## 🎯 Conclusion - Bottom line: This joint letter crystallizes a discovery fight over alleged message spoliation versus claimed full compliance, set against a larger business and competition dispute between two major WordPress players. - Practical next steps: For readers in similar ecosystems, review your own communication, logging, and preservation practices—especially around chat apps—to ensure you can meet legal duties without sacrificing security or practicality. ## 🧱 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] [{Title or entity}](https://readwise.io/reader/document_raw_content/449369972) by [[{Author or [MISSING]}]] via [[{Site or [MISSING]}]]. Published {DATE_OR_[MISSING]}. Accessed . > “Short quote, verbatim, ≤25 words.” Two lines: context and use. Cite data if relevant. [view highlight](https://readwise.io/reader/document_raw_content/449369972#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] 5–10-word present-tense claim > [!quote] [{Title or entity}](https://readwise.io/reader/document_raw_content/449369972) > “Short quote, verbatim, ≤25 words.” Two lines: context and use. [view highlight](https://readwise.io/reader/document_raw_content/449369972#H2) #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] 5–10-word present-tense claim - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[Parent-Concept]] [[Related-Idea]] #### [Z2] 5–10-word present-tense claim - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[Parent-Concept]] [[Related-Idea]] --- ### ✏️ 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] Short action — context/https://readwise.io/reader/document_raw_content/449369972 #fleeting #inbox - [F2] Short action — context/https://readwise.io/reader/document_raw_content/449369972 #fleeting #inbox - [F3] Short action — context/https://readwise.io/reader/document_raw_content/449369972 #fleeting #inbox --- <!-- deep-read:sections end -->