Letter Brief Re Additional Rog Responses
🔗 **Source:** [Letter Brief Re Additional Rog Responses](https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.312.0.pdf)
> [!note]+ Document Notes
> ---
> tags: [discovery-disputes, interrogatory-limits, wp-engine-litigation]
> author: [MISSING]
> source: CourtListener
> reference: [https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.312.0.pdf]
> date created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
> ---
> # 🏷️ Title: Letter Brief Re Additional Rog Responses
> ## 🧭 Table of Contents
> - [📝 Summary](#-summary)
> - [📖 Main Content](#-main-content)
> - [🗒️ Notes](#️-notes)
> - [📚 References](#-references)
> - [🗣️ Paraphrase](#️-paraphrase)
> - [📰 Newsletter](#-newsletter)
> - [✅ Action Items](#-action-items)
> - [🧪 Hypotheses](#-hypotheses)
> - [🎯 Conclusion](#-conclusion)
> - [🔄 Refactor Appendix](#-refactor-appendix)
> ## 📝 Summary
> - Gibson Dunn files opposition to WP Engine's motion to compel additional interrogatory responses in WP Engine v. Automattic litigation
> - WP Engine served compound interrogatories exceeding Rule 33's 25-question limit without court permission, totaling 45-70 questions per defendant
> - Motion filed after fact discovery closed, with inadequate meet-and-confer process (draft sent at 3:04 AM day of filing)
> - Defendants argue relief should be denied as procedurally improper, untimely, and unnecessary given extensive discovery already completed
> - Bottom line: Strategic discovery choices have consequences that Rule 33 doesn't require courts to cure retroactively
> ## 📖 Main Content
> Automattic's counsel argues WP Engine's motion to compel additional interrogatory responses violates procedural rules and comes too late. The core dispute centers on Rule 33's presumptive 25-interrogatory limit per party.
> ### Discovery Scope and Timing
> WP Engine served compound interrogatories to four defendants: 45 to Automattic, 70 to Mullenweg, 44 to WooCommerce, and 47 to WordPress Foundation. When defendants objected to exceeding Rule 33 limits, WP Engine continued serving additional questions without seeking court permission or stipulating with opposing counsel.
> After completing extensive fact discovery—including depositions and 225,000+ produced documents—WP Engine filed this motion seeking responses to 13 interrogatories, several never actually served during discovery.
> ### Procedural Deficiencies
> The brief emphasizes two procedural failures: inadequate meet-and-confer under Rule 37(a)(1) and violation of the court's joint-letter requirements. WP Engine's draft brief arrived at 3:04 AM on filing day, preventing meaningful collaboration on the joint submission.
> ### Merits Arguments
> Defendants contend WP Engine had sufficient discovery tools (100 total interrogatories across defendants) but chose to draft duplicative and compound questions. Many interrogatories were substantively identical across parties, with overlapping entity definitions making responses redundant.
> ## 🗒️ Notes
> - Strategic discovery planning matters—compound interrogatories exhaust limited question budgets
> - Courts expect parties to seek permission before exceeding Rule 33 limits, not retroactive relief
> - Extensive discovery record (225k+ documents, multiple depositions) undermines claims of insufficient information
> - Meet-and-confer requirements have teeth—inadequate process alone can doom motions
> - Timing matters in discovery disputes—waiting until after close of discovery weakens position
> ## 📚 References
> - [Fed. R. Civ. P. 33](https://www.law.cornell.edu/rules/frcp/rule_33) - Interrogatories to parties
> - [Fed. R. Civ. P. 37](https://www.law.cornell.edu/rules/frcp/rule_37) - Failure to make disclosures or cooperate in discovery
> - James v. Asian Fam. Mkt., 2026 WL 622729 (9th Cir. 2026)
> - Stearns v. Flores, 2006 WL 1980334 (E.D. Cal. 2006)
> ## 🗣️ Paraphrase
> Automattic argues WP Engine shot itself in the foot with poor discovery planning. Instead of using their 100 available interrogatories strategically, WP Engine wrote overly complex, duplicative questions that exceeded Rule 33's limits. When defendants objected, WP Engine ignored compromise offers and kept serving more questions without court permission. Now, after discovery closed and they've already gotten extensive information through depositions and document production, WP Engine wants the court to bail them out of their strategic mistakes. Automattic says the procedural violations and late timing should doom the motion regardless of substance.
> ## 📰 Newsletter
> Not applicable — legal filing
> ## ✅ Action Items
> #### DevRel
> Not applicable — legal filing
> #### OSPO
> - Monitor litigation developments affecting open source project governance models
> - Review interrogatory strategies in potential IP disputes involving foundation structures
> #### Community
> - Track legal precedents affecting multi-entity open source ecosystems (WordPress Foundation, WooCommerce relationship structures)
> #### WordPress
> Not applicable — legal filing
> #### The WPCC
> - Analyze implications for foundation/commercial entity relationship structures in open source projects
> ### FAIR
> - Document case study on discovery disputes in complex open source litigation for future reference
> ## 🧪 Hypotheses
> - Courts will increasingly scrutinize discovery abuse in complex IP litigation involving open source projects
> - Multi-entity structures (foundation + commercial arms) create discovery complexity that favors early strategic planning
> - Procedural compliance matters more than substantive need when discovery limits are exceeded
> ### 📊 Methodology
> - Case law analysis comparing discovery dispute outcomes in IP vs. general commercial litigation
> - Survey of interrogatory strategies in trademark/open source disputes
> - Analysis of meet-and-confer effectiveness in complex litigation
> ### ❓ Questions
> - How do courts balance discovery needs against Rule 33 limits in multi-defendant IP cases?
> - What constitutes adequate meet-and-confer in joint-letter jurisdictions?
> - How does extensive alternative discovery (depositions, documents) affect compel motions?
> ### 🔮 Future Research
> - Comparative analysis of discovery dispute patterns in open source litigation
> - Empirical study of compound interrogatory success rates across case types
> ### 💡 Implications
> - Discovery planning requires early assessment of interrogatory budgets across multiple defendants
> - Procedural compliance can override substantive discovery needs in motion practice
> - Open source litigation complexity doesn't automatically justify exceeding standard discovery limits
> ### 🧠 Learning Styles Assessment
> Reading level: Legal professional (Flesch-Kincaid ~16-18)
> #### 👀 Visual learners
> Present: Structured brief format, numbered arguments
> Improve: Discovery timeline diagram, interrogatory count visualization
> #### 🔊 Aural learners
> Present: Legal argument structure, oral advocacy preparation
> Improve: Audio summary of key procedural points
> #### 🗣️ Verbal learners
> Present: Technical legal definitions, rule citations
> Improve: Plain language summary of discovery concepts
> #### 🧩 Kinesthetic learners
> Present: Step-by-step procedural analysis
> Improve: Discovery planning checklist, motion drafting workshop
> #### 🧠 Logical learners
> Present: Rule-based analysis, precedent application
> Improve: Decision tree for discovery dispute strategies
> #### 🧑🤝🧑 Social learners
> Present: Adversarial brief structure
> Improve: Mock meet-and-confer exercises
> #### 🧘♀️ Solitary learners
> Present: Independent legal research and analysis
> Improve: Self-assessment questions on discovery strategy
> #### 🌿 Naturalistic learners
> Present: Litigation ecosystem relationships
> Improve: Discovery process lifecycle analysis
> ### 📊 Accessibility Assessment
> #### Screen reader semantics
> Present: Clear heading structure, logical document flow
> Improve: Alt text for any embedded exhibits
> #### Keyboard navigation
> Present: Standard PDF accessibility features
> Improve: Enhanced navigation bookmarks
> #### Contrast and readability
> Present: Standard legal document formatting
> Improve: Higher contrast version for visual impairments
> #### Text resizing and reflow
> Present: Reflowable text format
> Improve: Mobile-optimized legal document viewing
> #### Media and captions
> Present: Text-only document
> Improve: N/A for this document type
> #### Forms and interactions
> Present: Static document
> Improve: N/A for this document type
> ###
Full text of this document omitted because this document is a PDF
[Download original file →](https://readwise.io/reader/document_raw_content/460176208), Letter Brief Re Additional Rog Responses, Ajay S. Krishnan, 01ksssy7kazncr87vczq3n1y88.