WordPress Legal Updates • October 17, 2025
🔗 **Source:** [WordPress Legal Updates • October 17, 2025](https://www.delta.blog/wordpress-legal-updates-october-17-2025/)
> [!note]+ Document Notes
> tags: [WordPress, Legal, Automattic]
> author: The Delta
> source: The Delta
> reference: [https://www.delta.blog/wordpress-legal-updates-october-17-2025/]
> date created: 2025-10-20 00:00
>
> # 🏷️ Title: WordPress legal updates • October 17, 2025
>
<!-- 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.
- Ongoing discovery fights in WP Engine v. Automattic/Matt Mullenweg; three October discovery letters (Oct 1, 6, 7) plus hearing on Oct 9. WP Engine filed a Second Amended Complaint (SAC/CSAC). New Automattic counsel joined. An intervenor renewed a contempt motion.
- Why it matters.
- Discovery scope, privilege logs, and messaging preservation could shape sanctions, admissible evidence, and public unsealing.
- Key stakeholders.
- WP Engine; Automattic; Matt Mullenweg; Judge Ryu (discovery); Judge Martínez-Olguín (contempt context); WordPress community.
- Risks and tradeoffs.
- Spoliation sanctions risk; burden vs relevance in ongoing document production; confidentiality vs public interest in unsealing.
- Bottom line.
- “Discovery disputes continue,” with rulings pending on privilege-log detail, messaging data, and the timeframe for 107 RFPs; unsealing fights hint at “endorsements on WordPress.org” negotiations.
## 📖 Main Content
- Core arguments
- Privilege logs: WP Engine argues Automattic must disclose “position” and affiliation due to a “corporate shell game”; Automattic says Standing Order/Rule 26 don’t require organizational affiliation and full role labeling for ~160 names is burdensome.
- Messaging preservation: WP Engine seeks WhatsApp/Signal/Telegram data and spoliation remedies; Mullenweg says data are preserved and “did not enable ephemeral or auto-deletion settings.”
- Timeframe scope: 107 RFPs hinge on whether production must run through fact discovery or can stop at Dec 10, 2024.
- SAC/CSAC: All claims re-asserted except attempted extortion (dismissed) and trademark misuse (may return); extensive redactions contested.
- Sourced context and terms
- “Spoliation” can trigger sanctions or adverse inference.
- “Privilege log” lists withheld materials with enough detail to assess privilege.
- Uncertainties
- Judge Ryu’s interpretation of “position” and affiliation; whether ephemeral messaging was used; how many redactions will be unsealed.
### 🗒️ Notes
- “Discovery disputes continue” with an Oct 9 hearing where “the judge admonish[ed] both parties for not working together.”
- Oct 1: WP Engine challenges privilege logs; seeks roles and affiliations due to alleged “corporate shell game.” Automattic cites Rule 26(b)(5) and Ninth Circuit practice; says extra details and manual identification are burdensome.
- Oct 6: WP Engine moves to compel Mullenweg’s WhatsApp/Signal/Telegram and sworn loss testimony; alleges minimal production (15 docs; 16 Telegram messages). Flags a Sept 2024 post inviting “Signal with disappearing messages.” Mullenweg denies enabling ephemeral settings and says responsive, non-privileged communications will be produced.
- Oct 7: 107 RFPs dispute whether production runs through end of fact discovery vs to the preliminary injunction date.
- New Automattic lawyer: Ilissa S. Samplin (Gibson Dunn).
- Intervenor Michael Willman refiled contempt motion pro se; Automattic opposed; hearing possible Nov 6.
- SAC filed Oct 3; corrected (CSAC) Oct 7 after errata. Redactions: Automattic claims “highly sensitive” business info; WP Engine urges unsealing in public interest.
- Notable line: “communications between Mullenweg and a third party concerning negotiations for the third party to be endorsed on WordPress.org… including financial terms.”
## 📚 References
- WP Engine v. Automattic case background (general legal explainer): https://en.wikipedia.org/wiki/Discovery_(law)
- Spoliation overview (U.S. civil): https://www.law.cornell.edu/wex/spoliation
- Federal Rule of Civil Procedure 26(b)(5) (privilege logs): https://www.law.cornell.edu/rules/frcp/rule_26
## 🗣️ Paraphrase
- Paragraph A: The author recaps heated discovery disputes, focusing on privilege logs, messaging preservation, and the scope of production.
- Paragraph B: They outline SAC/CSAC filing details, redactions, and public-interest arguments for unsealing.
## 📰 Newsletter
- This week in WordPress law: Discovery fireworks continue in WP Engine v. Automattic. Expect rulings on privilege-log detail, messaging preservation, and whether 107 RFPs must run through the full discovery window. The SAC is now the CSAC after a quick errata refiling, and redactions could reveal how “endorsements on WordPress.org” are negotiated. Keep an eye on Judge Ryu’s orders and a potential Nov 6 hearing.
- Learn more: Rule 26(b)(5) privilege logs, spoliation basics, and civil discovery best practices.
## ✅ Action Items
#### DevRel
- Publish neutral explainer on discovery and preservation expectations for OSS orgs.
- Create office hours for plugin/theme authors on legal readiness (records, comms hygiene).
- Draft examples for responsible communications retention policies.
#### OSPO
- Implement evidence-preservation SOPs (mobile/DM apps included); run quarterly drills.
- Update policy on ephemeral messaging in legal hold contexts; training cadence monthly.
- Establish SBOM and data-retention ownership with clear SLAs.
#### Community
- Run governance clinics on conflict-of-interest disclosures.
- Offer contributor onboarding about code-of-conduct and records hygiene.
- Publish transparent funding/reporting templates for sponsors.
#### WordPress
- Core: document decision rights across .org entities.
- Meta: publish .org endorsement criteria and audit trails.
- Accessibility: ensure policy docs are readable and discoverable.
- Documentation: add examples-first governance artifacts.
#### The WPOCC
- Fund maintainers for compliance tooling and policy templates.
- Launch microgrants for governance documentation sprints.
### FAIR
- Require signed provenance for endorsements; public covenant on anti-capture.
- Maintain local metadata and signature checks for transparency artifacts.
## 🧪 Hypotheses
- Requiring affiliation in privilege logs reduces later motion practice.
- Clear ephemeral-messaging policies lower spoliation risk and sanctions.
- Extending discovery windows beyond injunction dates yields more relevant evidence.
- Public unsealing increases community trust without material competitive harm.
### 📊 Methodology
- Pre/post policy change studies on motion frequency and sanctions.
- Case-comparison of discovery cutoff scopes vs evidentiary yield.
- Survey WordPress ecosystem trust before/after unsealing decisions.
### ❓ Questions
- Should organizational affiliation be standard in tech-ecosystem privilege logs?
- What safeguards best prevent spoliation in encrypted/ephemeral apps?
- How should .org endorsements be governed to avoid conflicts?
### 🔮 Future Research
- Model policies for OSS foundations spanning multiple affiliates.
- Standard retention playbooks for mixed personal/work messaging apps.
### 💡 Implications
- Practice: adopt comms retention + legal hold playbooks.
- Policy: publish endorsement and conflict policies for .org assets.
- Security: attestations for message export/preservation.
- Education: training on discovery-ready workflows.
### 🧠 Learning Styles Assessment
- Reading level estimate: Flesch-Kincaid ~12–14.
#### 👀 Visual learners
- Present: sectioning and quotes.
- Improve: discovery-flow diagram; privilege-log example.
#### 🔊 Aural learners
- Improve: 3-minute audio summary.
#### 🗣️ Verbal learners
- Present: definitions, contrasts.
- Improve: glossary of legal terms.
#### 🧩 Kinesthetic learners
- Improve: sandbox exercise drafting a privilege log.
#### 🧠 Logical learners
- Present: chronological sequence.
- Improve: decision tree for preservation steps.
#### 🧑🤝🧑 Social learners
- Improve: moderated Q&A and peer clinics.
#### 🧘♀️ Solitary learners
- Improve: self-check quiz on discovery basics.
#### 🌿 Naturalistic learners
- Improve: lifecycle thinking for data retention.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Improve: consistent alt text for any images; explicit landmarks.
#### Keyboard navigation
- Improve: skip links, predictable focus order.
#### Contrast and readability
- Present: likely adequate; verify 4.5:1.
#### Text resizing and reflow
- Improve: test at 200% with no clipping.
#### Media and captions
- Improve: add captions/transcripts if audio added.
#### Forms and interactions
- Improve: clear labels and inline validation on policy portals.
#### Standards reference
- Map gaps to WCAG 2.2 AA.
### 🌍 DEIB Assessment
#### Cultural breadth
- Improve: multi-region examples and translation links.
#### Inclusive language
- Present: mostly neutral; define jargon.
#### Neurodiversity support
- Improve: more consistent chunking and summaries.
#### Representation
- Improve: balanced citations and examples.
#### Psychological safety
- Present: respectful tone.
- Improve: community guidelines and escalation paths.
### ✅ Logical Validity
#### Strong reasoning
- Inductive synthesis of filings and timelines supports measured conclusions.
#### Fallacies
- Potential availability bias in weighing public statements; mitigate by citing orders.
#### Tone of voice
- Analytical, candid: “This is nonsense.” Balanced with “I am not a lawyer.”
### 🛡️ DARVO Analysis
- Deny: Mullenweg denies enabling ephemeral settings.
- Attack: Parties imply the other is deficient in discovery.
- Reverse victim/offender: Hints when burden arguments recast producers as victims of process.
## 🎯 Conclusion
- Discovery remains hotly contested across privilege detail, messaging preservation, and timeframe scope; SAC redactions could reveal sensitive endorsement negotiations. Watch for Judge Ryu’s rulings and potential Nov 6 arguments. Practical next step: implement clear retention and legal-hold policies, especially for encrypted/ephemeral apps, and publish transparent .org endorsement governance.
## 🧱 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] Court may expand discovery scope
> [!quote] WordPress legal updates • October 17, 2025 by [[The Delta]] via [[The Delta]]. Published 2025-10-17. Accessed 2025-10-20.
> “Judge Ryu was clear that WP Engine is entitled to additional fact discovery to confirm that the behaviour had stopped.”
Two lines: signals discovery beyond injunction date; guides RFP scope planning.
[view highlight](https://www.delta.blog/wordpress-legal-updates-october-17-2025/#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] Privilege logs may require affiliation clarity
> [!quote] WordPress legal updates • October 17, 2025
> “Given this corporate shell game, understanding whether an individual worked for Automattic, the Foundation, wordpress.org… is essential to evaluating privilege.”
Two lines: argues for role+affiliation to assess privilege; impacts log standards.
[view highlight](https://www.delta.blog/wordpress-legal-updates-october-17-2025/#H2) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
#### [Z1] Ephemeral-messaging policies reduce spoliation risk
- In discovery contexts with legal holds.
- Pointer: Oct 6 letter discussion.
- Links: [[Discovery]] [[Retention-Policy]]
#### [Z2] Affiliation fields increase privilege-log utility
- When multiple related entities are involved.
- Pointer: Oct 1 letter summary.
- Links: [[Privilege-Logs]] [[Corporate-Structure]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- [F1] Draft a sample privilege-log schema with affiliation fields — context/https://www.delta.blog/wordpress-legal-updates-october-17-2025/ #fleeting #inbox
- [F2] Write a 3-min audio summary on discovery disputes — context/https://www.delta.blog/wordpress-legal-updates-october-17-2025/ #fleeting #inbox
- [F3] Outline .org endorsement governance checklist — context/https://www.delta.blog/wordpress-legal-updates-october-17-2025/ #fleeting #inbox
---
<!-- deep-read:sections end -->
[[3. Resources/Readwise/Full Document Contents/Articles/WordPress Legal Updates • October 17, 2025|Full Document Contents]]
## Document Notes
---
tags: #WordPress #Legal #Automattic
author: The Delta
source: The Delta
reference: [https://www.delta.blog/wordpress-legal-updates-october-17-2025/]
date created: 2025-10-20 00:00
---
# 🏷️ Title: WordPress legal updates • October 17, 2025
## 🧭 Table of Contents
- [[#📝 Summary]]
- [[#📖 Main Content]]
- [[#🗒️ Notes]]
- [[#📚 References]]
- [[#🗣️ Paraphrase]]
- [[#📰 Newsletter]]
- [[#✅ Action Items]]
- [[#🧪 Hypotheses]]
- [[#📊 Methodology]]
- [[#❓ Questions]]
- [[#🔮 Future Research]]
- [[#💡 Implications]]
- [[#🧠 Learning Styles Assessment]]
- [[#📊 Accessibility Assessment]]
- [[#🌍 DEIB Assessment]]
- [[#✅ Logical Validity]]
- [[#🛡️ DARVO Analysis]]
- [[#🎯 Conclusion]]
### 🔗 References
- Include links cited in or relevant to the article.
## 📝 Summary
- What happened.
- Ongoing discovery fights in WP Engine v. Automattic/Matt Mullenweg; three October discovery letters (Oct 1, 6, 7) plus hearing on Oct 9. WP Engine filed a Second Amended Complaint (SAC/CSAC). New Automattic counsel joined. An intervenor renewed a contempt motion.
- Why it matters.
- Discovery scope, privilege logs, and messaging preservation could shape sanctions, admissible evidence, and public unsealing.
- Key stakeholders.
- WP Engine; Automattic; Matt Mullenweg; Judge Ryu (discovery); Judge Martínez-Olguín (contempt context); WordPress community.
- Risks and tradeoffs.
- Spoliation sanctions risk; burden vs relevance in ongoing document production; confidentiality vs public interest in unsealing.
- Bottom line.
- “Discovery disputes continue,” with rulings pending on privilege-log detail, messaging data, and the timeframe for 107 RFPs; unsealing fights hint at “endorsements on WordPress.org” negotiations.
## 📖 Main Content
- Core arguments
- Privilege logs: WP Engine argues Automattic must disclose “position” and affiliation due to a “corporate shell game”; Automattic says Standing Order/Rule 26 don’t require organizational affiliation and full role labeling for ~160 names is burdensome.
- Messaging preservation: WP Engine seeks WhatsApp/Signal/Telegram data and spoliation remedies; Mullenweg says data are preserved and “did not enable ephemeral or auto-deletion settings.”
- Timeframe scope: 107 RFPs hinge on whether production must run through fact discovery or can stop at Dec 10, 2024.
- SAC/CSAC: All claims re-asserted except attempted extortion (dismissed) and trademark misuse (may return); extensive redactions contested.
- Sourced context and terms
- “Spoliation” can trigger sanctions or adverse inference.
- “Privilege log” lists withheld materials with enough detail to assess privilege.
- Uncertainties
- Judge Ryu’s interpretation of “position” and affiliation; whether ephemeral messaging was used; how many redactions will be unsealed.
### 🗒️ Notes
- “Discovery disputes continue” with an Oct 9 hearing where “the judge admonish[ed] both parties for not working together.”
- Oct 1: WP Engine challenges privilege logs; seeks roles and affiliations due to alleged “corporate shell game.” Automattic cites Rule 26(b)(5) and Ninth Circuit practice; says extra details and manual identification are burdensome.
- Oct 6: WP Engine moves to compel Mullenweg’s WhatsApp/Signal/Telegram and sworn loss testimony; alleges minimal production (15 docs; 16 Telegram messages). Flags a Sept 2024 post inviting “Signal with disappearing messages.” Mullenweg denies enabling ephemeral settings and says responsive, non-privileged communications will be produced.
- Oct 7: 107 RFPs dispute whether production runs through end of fact discovery vs to the preliminary injunction date.
- New Automattic lawyer: Ilissa S. Samplin (Gibson Dunn).
- Intervenor Michael Willman refiled contempt motion pro se; Automattic opposed; hearing possible Nov 6.
- SAC filed Oct 3; corrected (CSAC) Oct 7 after errata. Redactions: Automattic claims “highly sensitive” business info; WP Engine urges unsealing in public interest.
- Notable line: “communications between Mullenweg and a third party concerning negotiations for the third party to be endorsed on WordPress.org… including financial terms.”
## 📚 References
- WP Engine v. Automattic case background (general legal explainer): https://en.wikipedia.org/wiki/Discovery_(law)
- Spoliation overview (U.S. civil): https://www.law.cornell.edu/wex/spoliation
- Federal Rule of Civil Procedure 26(b)(5) (privilege logs): https://www.law.cornell.edu/rules/frcp/rule_26
## 🗣️ Paraphrase
- Paragraph A: The author recaps heated discovery disputes, focusing on privilege logs, messaging preservation, and the scope of production.
- Paragraph B: They outline SAC/CSAC filing details, redactions, and public-interest arguments for unsealing.
## 📰 Newsletter
- This week in WordPress law: Discovery fireworks continue in WP Engine v. Automattic. Expect rulings on privilege-log detail, messaging preservation, and whether 107 RFPs must run through the full discovery window. The SAC is now the CSAC after a quick errata refiling, and redactions could reveal how “endorsements on WordPress.org” are negotiated. Keep an eye on Judge Ryu’s orders and a potential Nov 6 hearing.
- Learn more: Rule 26(b)(5) privilege logs, spoliation basics, and civil discovery best practices.
## ✅ Action Items
#### DevRel
- Publish neutral explainer on discovery and preservation expectations for OSS orgs.
- Create office hours for plugin/theme authors on legal readiness (records, comms hygiene).
- Draft examples for responsible communications retention policies.
#### OSPO
- Implement evidence-preservation SOPs (mobile/DM apps included); run quarterly drills.
- Update policy on ephemeral messaging in legal hold contexts; training cadence monthly.
- Establish SBOM and data-retention ownership with clear SLAs.
#### Community
- Run governance clinics on conflict-of-interest disclosures.
- Offer contributor onboarding about code-of-conduct and records hygiene.
- Publish transparent funding/reporting templates for sponsors.
#### WordPress
- Core: document decision rights across .org entities.
- Meta: publish .org endorsement criteria and audit trails.
- Accessibility: ensure policy docs are readable and discoverable.
- Documentation: add examples-first governance artifacts.
#### The WPCC
- Fund maintainers for compliance tooling and policy templates.
- Launch microgrants for governance documentation sprints.
### FAIR
- Require signed provenance for endorsements; public covenant on anti-capture.
- Maintain local metadata and signature checks for transparency artifacts.
## 🧪 Hypotheses
- Requiring affiliation in privilege logs reduces later motion practice.
- Clear ephemeral-messaging policies lower spoliation risk and sanctions.
- Extending discovery windows beyond injunction dates yields more relevant evidence.
- Public unsealing increases community trust without material competitive harm.
### 📊 Methodology
- Pre/post policy change studies on motion frequency and sanctions.
- Case-comparison of discovery cutoff scopes vs evidentiary yield.
- Survey WordPress ecosystem trust before/after unsealing decisions.
### ❓ Questions
- Should organizational affiliation be standard in tech-ecosystem privilege logs?
- What safeguards best prevent spoliation in encrypted/ephemeral apps?
- How should .org endorsements be governed to avoid conflicts?
### 🔮 Future Research
- Model policies for OSS foundations spanning multiple affiliates.
- Standard retention playbooks for mixed personal/work messaging apps.
### 💡 Implications
- Practice: adopt comms retention + legal hold playbooks.
- Policy: publish endorsement and conflict policies for .org assets.
- Security: attestations for message export/preservation.
- Education: training on discovery-ready workflows.
### 🧠 Learning Styles Assessment
- Reading level estimate: Flesch-Kincaid ~12–14.
#### 👀 Visual learners
- Present: sectioning and quotes.
- Improve: discovery-flow diagram; privilege-log example.
#### 🔊 Aural learners
- Improve: 3-minute audio summary.
#### 🗣️ Verbal learners
- Present: definitions, contrasts.
- Improve: glossary of legal terms.
#### 🧩 Kinesthetic learners
- Improve: sandbox exercise drafting a privilege log.
#### 🧠 Logical learners
- Present: chronological sequence.
- Improve: decision tree for preservation steps.
#### 🧑🤝🧑 Social learners
- Improve: moderated Q&A and peer clinics.
#### 🧘♀️ Solitary learners
- Improve: self-check quiz on discovery basics.
#### 🌿 Naturalistic learners
- Improve: lifecycle thinking for data retention.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Improve: consistent alt text for any images; explicit landmarks.
#### Keyboard navigation
- Improve: skip links, predictable focus order.
#### Contrast and readability
- Present: likely adequate; verify 4.5:1.
#### Text resizing and reflow
- Improve: test at 200% with no clipping.
#### Media and captions
- Improve: add captions/transcripts if audio added.
#### Forms and interactions
- Improve: clear labels and inline validation on policy portals.
#### Standards reference
- Map gaps to WCAG 2.2 AA.
### 🌍 DEIB Assessment
#### Cultural breadth
- Improve: multi-region examples and translation links.
#### Inclusive language
- Present: mostly neutral; define jargon.
#### Neurodiversity support
- Improve: more consistent chunking and summaries.
#### Representation
- Improve: balanced citations and examples.
#### Psychological safety
- Present: respectful tone.
- Improve: community guidelines and escalation paths.
### ✅ Logical Validity
#### Strong reasoning
- Inductive synthesis of filings and timelines supports measured conclusions.
#### Fallacies
- Potential availability bias in weighing public statements; mitigate by citing orders.
#### Tone of voice
- Analytical, candid: “This is nonsense.” Balanced with “I am not a lawyer.”
### 🛡️ DARVO Analysis
- Deny: Mullenweg denies enabling ephemeral settings.
- Attack: Parties imply the other is deficient in discovery.
- Reverse victim/offender: Hints when burden arguments recast producers as victims of process.
## 🎯 Conclusion
- Discovery remains hotly contested across privilege detail, messaging preservation, and timeframe scope; SAC redactions could reveal sensitive endorsement negotiations. Watch for Judge Ryu’s rulings and potential Nov 6 arguments. Practical next step: implement clear retention and legal-hold policies, especially for encrypted/ephemeral apps, and publish transparent .org endorsement governance.
## 🧱 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] Court may expand discovery scope
> [!quote] WordPress legal updates • October 17, 2025 by [[The Delta]] via [[The Delta]]. Published 2025-10-17. Accessed 2025-10-20.
> “Judge Ryu was clear that WP Engine is entitled to additional fact discovery to confirm that the behaviour had stopped.”
Two lines: signals discovery beyond injunction date; guides RFP scope planning.
[view highlight](https://www.delta.blog/wordpress-legal-updates-october-17-2025/#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] Privilege logs may require affiliation clarity
> [!quote] WordPress legal updates • October 17, 2025
> “Given this corporate shell game, understanding whether an individual worked for Automattic, the Foundation, wordpress.org… is essential to evaluating privilege.”
Two lines: argues for role+affiliation to assess privilege; impacts log standards.
[view highlight](https://www.delta.blog/wordpress-legal-updates-october-17-2025/#H2) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
#### [Z1] Ephemeral-messaging policies reduce spoliation risk
- In discovery contexts with legal holds.
- Pointer: Oct 6 letter discussion.
- Links: [[Discovery]] [[Retention-Policy]]
#### [Z2] Affiliation fields increase privilege-log utility
- When multiple related entities are involved.
- Pointer: Oct 1 letter summary.
- Links: [[Privilege-Logs]] [[Corporate-Structure]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- [F1] Draft a sample privilege-log schema with affiliation fields — context/https://www.delta.blog/wordpress-legal-updates-october-17-2025/ #fleeting #inbox
- [F2] Write a 3-min audio summary on discovery disputes — context/https://www.delta.blog/wordpress-legal-updates-october-17-2025/ #fleeting #inbox
- [F3] Outline .org endorsement governance checklist — context/https://www.delta.blog/wordpress-legal-updates-october-17-2025/ #fleeting #inbox
---
## 🧰 Template Library (paste into Note Refactor → Refactored Note Template)
```
### 📝 Fleeting — Refactored Note Template (Konik-ready)
---
type: fleeting
status: inbox
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
process_by: {{date:YYYY-MM-DD}}
source_title: [MISSING]
source_link:
author: [MISSING]
source_type: article|paper|video|podcast|thread
reading_stage: inspectional|analytical|syntopical
project:
tags: #fleeting #inbox
---
# 📝 Fleeting Note — {{title}}
## 🧠 One-liner (my words)
- State the single idea in one short sentence.
## 🧭 Context & cue
- Where did this arise? Page/timecode/speaker.
- Trigger: quote, data point, claim, or question.
## 🧪 Adler checks (quick)
- What is this about as a whole?
- What is said in detail, and how?
- Is it true? Evidence for or against?
- So what? Impact or next move.
## 🔎 Bias & reliability snapshot
- Possible bias or framing?
- What evidence would change my view?
## 🧩 Konik bridge
- Draft a claim header for promotion.
### [H1] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{source_link}}) by [[{{author}}]]. Accessed {{date:YYYY-MM-DD}}.
> “Short quote under ~25 words.”
One line on why this matters.
[view highlight]({{source_link}}) #xref ID:rw_[MISSING]
## 🧰 Next moves (pick 1–2)
- [ ] Promote to *Literature* with citation.
- [ ] Draft *Atomic* claim from [H1].
- [ ] Park as testable question.
## ✅ Processing checklist
- [ ] Rewrote in my words.
- [ ] Decided: trash | keep | convert.
- [ ] Linked to at least one related note.
- [ ] Tagged and moved out of inbox.
---
### 📚 Literature — Refactored Note Template (Konik-ready)
---
type: literature
status: draft
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
adler_level: inspectional|analytical|syntopical
reading_stage: inspectional|analytical|syntopical
source_title: [MISSING]
author: [MISSING]
year:
publisher_or_journal:
edition_or_volume:
doi:
url:
accessed: {{date:YYYY-MM-DD}}
citekey:
project:
tags: #literature #reading
---
# 📚 Literature Note — {{title}}
## 🧰 Action Inbox
- [H1] Short action — context/{{url}} #articleseed
- [H2] Short action — context/{{url}} #xref
- [H3] Short action — context/{{url}} #share
## 🧭 Bib Capsule
- Title, author, year, venue, and link.
- One-line scope: what the work attempts.
## 🧠 Author’s Thesis (their words)
- Core claim briefly. Include page/timecode.
## 🧩 Key Arguments
- Argument A — method/evidence — page/time.
- Argument B — method/evidence — page/time.
- Argument C — method/evidence — page/time.
## 🧪 Evaluation (Adler)
- What is this about as a whole?
- How is it argued? Fairly and clearly?
- Is it true or plausible? Why?
- So what? Practical or theoretical impact.
## 🗒️ Notes (Konik CEE units)
### [H1] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{url}}) by [[{{author}}]] via [[{{publisher_or_journal}}]]. Published {{year}}. Accessed {{accessed}}.
> “Verbatim highlight under ~25 words.”
Two lines: context and use. Link to data if relevant.
[view highlight]({{url}}#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{url}}) by [[{{author}}]] via [[{{publisher_or_journal}}]]. Published {{year}}. Accessed {{accessed}}.
> “Verbatim highlight under ~25 words.”
Two lines: context and use. Link to data if relevant.
[view highlight]({{url}}#H2) #xref ID:rw_[MISSING]
## 🔖 Zettel Candidates
#### [Z1] 5–10-word present-tense claim
- One-line context and page/time.
#### [Z2] 5–10-word present-tense claim
- One-line context and page/time.
## 🏷️ Tag Coverage
#articleseed: 0 • #xref: 0 • #share: 0 • #bmf: 0 • #addendum: 0
## ✅ Processing Checklist
- [ ] Thesis captured in my words.
- [ ] 1–3 Zettel candidates drafted.
- [ ] Action Inbox pruned to high-signal items.
- [ ] Cross-links added and filed.
---
### 🔖 Atomic (Zettel) — Refactored Note Template (Konik-ready)
---
type: atomic
id: {{date:YYYYMMDDHHmm}}-{{title}}
status: evergreen
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
origin: reading|thinking|experiment
proof_state: conjecture|working|supported|refuted
source_literature: [[Source-Literature-Note]]
citekey:
project:
tags: #zettel #idea
---
# 🔖 {{title}} <!-- 5–10 words, present tense, specific -->
## 🧠 Claim
- One idea only. Clear and testable.
## 🧾 Evidence & Pointers (Konik)
- [H#] from [[{{source_literature}}]] — page/time — brief rationale.
- ID:rw_[MISSING] — link to highlight or dataset.
> [!quote] Evidence snippet (≤25 words) if essential.
> Cite page/time. Keep it minimal.
## 🔍 Scope & Conditions
- When this holds. Boundaries and exceptions.
## 🔗 Links
- Broader: [[Parent-Concept]]
- Narrower: [[Specific-Case]]
- Related: [[Parallel-Idea]]
## 🧪 Tests / Falsifiers
- One check that could disconfirm the claim.
- Simple study or observation plan.
## 🧰 Implications
- Practice, policy, or design moves in one line each.
## 🔙 Backlinks
- From: [[{{source_literature}}]] • Context line.
## ✅ Maintenance
- [ ] Links in and out.
- [ ] Title still precise?
- [ ] Proof state updated.
```
## Highlights
- Of the approximately 70 asterisk-marked individuals who Defendants claim are attorneys, more than 50 cannot be identified through publicly available sources. Even worse, Defendants admitted—after serving their September log—that several asterisk-marked individuals are not attorneys at all but are “paralegals.” ([View Highlight](https://read.readwise.io/read/01k810sc06t67g7tz3ph69pv98))
- The [First] Amended Complaint alleges that Mr. Mullenweg orchestrated a web of conflicted relationships among Automattic, the WordPress Foundation (“the Foundation”), and wordpress.org—entities he portrayed as independent but that he actually controls behind the scenes for commercial advantage. Given this corporate shell game, understanding whether an individual worked for Automattic, the Foundation, wordpress.org (to the extent it was operating within a corporate entity, which Defendants have not disclosed), or some other undisclosed Mullenweg-controlled entity is essential to evaluating privilege. Contrary to Defendants’ assertions, knowing an individual’s position necessarily requires disclosure of their organizational affiliation where multiple different entities are involved, as is the case here. ([View Highlight](https://read.readwise.io/read/01k810sv15kadg3a5cts4bra77))
- arguing that identifying 160 names is too much of a burden? To quote WP Engine: This is nonsense. The effort would likely be under an hour for a paralegal, perhaps less for an in-house attorney at Automattic. Claiming otherwise is disingenuous at best. ([View Highlight](https://read.readwise.io/read/01k810tt8ahsngar5m2dqbt7js))
- Filed by WP Engine, [the **October 6** discovery letter](https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.177.0.pdf?ref=delta.blog) moves to compel Mullenweg to turn over documents from his WhatsApp, Signal, and Telegram accounts, as well as provide sworn testimony as to what, if any, data has been lost. ([View Highlight](https://read.readwise.io/read/01k810vfs8nfys5a3dcm5dw1xn))
- January 2025, when WP Engine discovered that Mullenweg had “knowingly deleted relevant evidence” including certain posts on X and “an entire Post Status Slack channel”, both of which contained relevant material. ([View Highlight](https://read.readwise.io/read/01k810vqdwxng8pzrjtzj88fmb))
- February 2025, when Mullenweg’s counsel acknowledged the deletion, but claimed that all evidence was preserved elsewhere, including with screenshots. WP Engine interestingly points to [a tweet from September 2024](https://x.com/photomatt/status/1837291862136365107?ref=delta.blog), months prior, where Mullenweg requests individuals contact him via “Signal with disappearing messages.” ([View Highlight](https://read.readwise.io/read/01k810w72m6vh7xkjk7j6qe1wp))
- Now, I find it *interesting* that no documents from WhatsApp or Signal have been produced, especially given the initial timeframe of September to November 2024, which is ~1 year ago at this point. But, that doesn’t inherently mean an actual issue here. We’ll have to wait for how the judge interprets the actions from each party. ([View Highlight](https://read.readwise.io/read/01k810x73cw58da4ehme2wnw6r))
- On **October 6**, Automattic and Mullenweg added a new attorney to their team, [Gibson Dunn lawyer Ilissa S. Samplin](https://www.gibsondunn.com/lawyer/samplin-ilissa/?ref=delta.blog). Like others on the team, Samplin has experience with complex commercial litigation and trials, and co-chairs Gibson Dunn’s Media, Entertainment and Technology Practice Group. ([View Highlight](https://read.readwise.io/read/01k810xvf1bd98tmgvf1zsfrk8))
- Willman [amended his motion](https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.171.0.pdf?ref=delta.blog) to solely represent himself and refiled it on **September 22**, otherwise effectively unchanged. ([View Highlight](https://read.readwise.io/read/01k810y4jtsvp93g58b8annyma))
- Now, I obviously do not know the details of the redactions—it’s entirely possible that revealing these redactions *would* harm Automattic and Mullenweg—but I really want to side with WP Engine here, because I really want to know more about the backroom deals that Automattic and Mullenweg are negotiating. ([View Highlight](https://read.readwise.io/read/01k810z6jk1yjjfxrbqpkxjxxg))