WPGEngine, Inc., a Delaware Corporation 🔗 **Source:** [WPGEngine, Inc., a Delaware Corporation](https://readwise.io/reader/document_raw_content/421377813) > [!note]+ Document Notes > ```markdown > > --- > tags: [litigation, law, wordpress] > author: [Rachel Herrick Kassabian, Yury Kagan, Margret M. Caruso, Brian Mack, Michael E. Williams, Kevin Y. Teruya] > source: an unnamed author > reference: [https://readwise.io/reader/document_raw_content/421377813] > date created: 2026-02-16 10:00 > > --- > > # 🏷️ Title: WPGEngine, Inc., a Delaware Corporation > <!-- 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: WPEngine’s counsel, Brantley I. Pepperman, files a short declaration supporting an administrative motion about sealing material in WPEngine’s Third Amended Complaint (TAC) in a federal case involving WooCommerce. - Why it matters: It documents compliance with a protective order and local rules on sealing, and shows which party is asserting confidentiality over certain materials. - Key stakeholders: WPEngine (plaintiff), WooCommerce/other defendants, Northern District of California, and counsel. - Risks and tradeoffs: Balancing public access to court filings against protection of confidential business information designated under a stipulated protective order; risk of over‑sealing versus disclosure of sensitive materials. - Bottom line: WPEngine is provisionally filing its unredacted TAC and redline under seal because defendants have designated certain referenced documents as “Confidential” or “Highly Confidential – Attorneys’ Eyes Only,” while also filing redacted public versions. ## 📖 Main Content - Core arguments: - Pepperman declares his qualifications and role: he is a California attorney, admitted in N.D. Cal., and associate at Quinn Emanuel for WPEngine. He has “personal knowledge of the facts set forth herein.” ([opening declaration](https://read.readwise.io/read/01khh9zxd3ekm0nbah9r9rt4c6?endLexposition=00000_00009_00000-004W&startLexposition=00000_00003&emphasizeText=I+am+a+member+of+the+bar+of+the+State+of+California)) - Procedural history: - On December 2, 2025, WPEngine moved for leave to amend its Corrected Second Amended Complaint to name WooCommerce, Inc. as a defendant in a Third Amended Complaint for several counts, submitting a proposed TAC at that time. ([Dec. 2 motion description](https://read.readwise.io/read/01khh9zxd3ekm0nbah9r9rt4c6?endLexposition=00000_00009_00000-004W&startLexposition=00000_00003&emphasizeText=On+December+2%2C+2025%2C+WPE+filed+a+motion+for+leave)) - On January 27, 2026, the court granted leave and ordered WPEngine to file the TAC as a stand‑alone docket entry, with a redline against the first amended complaint by February 10, 2026, and instructed the parties to meet and confer on a tailored, supported sealing motion. ([court’s order summary](https://read.readwise.io/read/01khh9zxd3ekm0nbah9r9rt4c6?endLexposition=00000_0000F_00000-0069&startLexposition=00000_0000B&emphasizeText=the+Court+granted+WPE%27s+motion+for+leave%2C+ordering+WPE+to+file+the+Third+Amended+Complaint)) - Meet‑and‑confer outcome: - After conferring, defendants agreed to down‑designate most previously redacted portions of the proposed TAC, leaving only selected paragraphs still redacted (named paragraphs 213, 215, 219, 220, 225, 238, 297, 324, 336). ([remaining redactions](https://read.readwise.io/read/01khh9zxd3ekm0nbah9r9rt4c6?endLexposition=00000_0000F_00000-0069&startLexposition=00000_0000B&emphasizeText=except+the+portions+that+remain+redacted+in+Paragraphs+213%2C+215)) - Confidentiality basis: - The TAC and the redline include references and quotations from documents that defendants—not WPEngine—have designated as “Highly Confidential – Attorneys’ Eyes Only” or “Confidential” under a stipulated protective order. ([confidential designations](https://read.readwise.io/read/01khh9zxd3ekm0nbah9r9rt4c6?endLexposition=00000_0000F_00000-0069&startLexposition=00000_0000B&emphasizeText=have+designated+as+either+%22Highly+Confidential+%E2%80%93+Attorneys%27+Eyes+Only%22)) - Compliance with protective order and local rules: - To comply with the protective order and give defendants an opportunity to submit a statement under N.D. Cal. Civil Local Rule 79‑5(f), WPEngine is provisionally filing under seal the unredacted TAC and the unredacted redline, concurrent with its administrative motion and this declaration. ([provisional sealing step](https://read.readwise.io/read/01khh9zxd3ekm0nbah9r9rt4c6?endLexposition=00000_0000N_00000-003P&startLexposition=00000_0000H&emphasizeText=provisionally+filing+under+seal+the+following+documents)) - The “yellow highlighted” references in those unredacted documents correspond to materials that defendants have maintained as confidential even after meet‑and‑confer; WPEngine identifies them by Bates numbers and designations in its motion and proposed order. ([highlighted references description](https://read.readwise.io/read/01khh9zxd3ekm0nbah9r9rt4c6?endLexposition=00000_0000N_00000-003P&startLexposition=00000_0000H&emphasizeText=The+yellow+highlighted+references+in+the+unredacted+version+of+WPE%27s+Third+Amended+Complaint)) - WPEngine has also filed public, redacted versions of both the TAC and the redline. ([public redacted versions](https://read.readwise.io/read/01khh9zxd3ekm0nbah9r9rt4c6?endLexposition=00000_0000N_00000-003P&startLexposition=00000_0000H&emphasizeText=WPE+has+also+filed+public+versions+of+its+Third+Amended+Complaint)) - The declaration concludes with Pepperman’s penalty‑of‑perjury statement and execution date and location (February 10, 2026, Los Angeles, California). ([execution clause](https://read.readwise.io/read/01khh9zxd3ekm0nbah9r9rt4c6?endLexposition=00000_0000v_00002-000S&startLexposition=00000_0000P&emphasizeText=I+declare+under+penalty+of+perjury+under+the+laws+of+the+United+States+of+America)) - Context & terms: - “Administrative Motion to Consider Whether Another Party’s Material Should Be Sealed”: A mechanism in N.D. Cal. for a filing party to trigger court review of sealing requests where another party claims confidentiality over materials. - “Stipulated Protective Order”: Agreement, approved by the court, governing handling of confidential discovery materials. - “Highly Confidential – Attorneys’ Eyes Only”: Strongest confidentiality tier, typically limiting access to outside counsel and certain experts. - N.D. Cal. Civil Local Rule 79‑5(f): Provides process and deadlines for designating party to justify sealing after another party provisionally files material under seal. - Uncertainties/contested claims: - The declaration does not argue whether the materials actually meet the legal standard for sealing; it only records that defendants have designated them as confidential and that WPEngine is following procedure. - It remains for defendants (and ultimately the court) to justify and decide what, if anything, stays sealed. ### 🗒️ Notes - Declarant: - Brantley I. Pepperman, California attorney, admitted in N.D. Cal., associate at Quinn Emanuel, represents WPEngine. - States he has personal knowledge of the declaration’s facts and could testify competently if called. - Procedural posture: - Dec. 2, 2025: WPEngine moves for leave to amend, seeking to name WooCommerce, Inc. as a defendant in a Third Amended Complaint, attaching a proposed TAC. - Jan. 27, 2026: Court grants leave; orders: - File TAC as a stand‑alone docket entry. - Include redline vs. first amended complaint. - Deadline: no later than Feb. 10, 2026. - Parties must meet and confer on a narrowly tailored, properly supported motion to seal. - Meet‑and‑confer outcome on sealing: - Defendants agree to down‑designate previously redacted portions of the proposed TAC. - Remaining redactions limited to certain paragraphs (213, 215, 219, 220, 225, 238, 297, 324, 336). - Indicates narrowing of secrecy claims but continued dispute over specific content. - Basis for sealing: - TAC and redline quote/reference documents designated “Highly Confidential – Attorneys’ Eyes Only” or “Confidential” under the parties’ protective order. - These designations were made by defendants, not WPEngine; WPEngine is not independently asserting confidentiality over that material. - Compliance steps: - To comply with the protective order and N.D. Cal. Local Rule 79‑5(f): - WPEngine provisionally files under seal: - Unredacted TAC. - Unredacted redline showing changes from the first amended complaint to the TAC. - Yellow highlighting in unredacted versions: - Marks references to documents that defendants still treat as confidential. - WPEngine lists those documents by Bates number and confidentiality designation in its separate administrative motion and proposed order. - Public access: - WPEngine simultaneously files public, redacted versions of: - TAC. - Redline. - This allows some transparency while the court decides on final sealing. - Formalities: - Declaration made under penalty of perjury under U.S. law. - Executed Feb. 10, 2026, Los Angeles, California. - Signed “/s/ Brantley I. Pepperman.” ## 📚 References - Northern District of California Civil Local Rule 79‑5 (on sealing): https://www.cand.uscourts.gov/local-rules/local-rules-of-court/ - Example discussion of “Highly Confidential – Attorneys’ Eyes Only” designations in protective orders: https://www.fjc.gov/content/discovery-and-protective-orders ## 🗣️ Paraphrase - Paragraph A paraphrase: - An attorney for WPEngine explains his role, recounts the procedural history of how WPEngine obtained leave to file a Third Amended Complaint adding WooCommerce, and describes the court’s instructions to file a redline and coordinate on a narrowly tailored sealing request. - Paragraph B paraphrase: - He states that after negotiations, defendants agreed to reduce some confidentiality designations but continue to claim secrecy over certain material; therefore, WPEngine is provisionally filing the unredacted complaint and redline under seal in accordance with the protective order and local rules while also providing redacted public versions. ## 📰 Newsletter Here’s your quick WordPress‑world legal update: WPEngine has filed a Third Amended Complaint in its ongoing litigation involving WooCommerce, along with a declaration explaining why parts of the filing are currently under seal. Because the complaint cites materials that defendants labeled “Highly Confidential” under a court‑approved protective order, WPEngine is provisionally filing unredacted versions under seal while offering redacted public copies. For WordPress builders and hosts, these cases are a reminder that: - Contracts, APIs, and data‑sharing arrangements can land in discovery. - Protective orders and “Attorneys’ Eyes Only” designations are standard tools to avoid exposing sensitive technical or business details on public dockets. Keep an eye on future orders to see what, if anything, the court ultimately allows to remain sealed—and consider whether your own documentation and agreements are litigation‑ready. ## ✅ Action Items #### DevRel - Developer advocacy: - Prepare neutral explainer content on how litigation and protective orders can affect public documentation of WordPress‑related products. - Education: - Offer an internal workshop on “What happens to your code and docs in discovery?” for engineers and PMs. - Developer experience: - Review SDK and API documentation for clarity around licensing, data usage, and integration boundaries that might be scrutinized in disputes. - Developer marketing: - Avoid legal speculation in external marketing; stick to facts from public filings. - Community management: - Moderate forum discussions about the case to ensure accuracy and avoid personal attacks on individuals or companies. - Internal/external/cross‑project: - Coordinate with legal and product teams to ensure any public technical commentary doesn’t conflict with litigation positions. #### OSPO - Policy & Governance: - Clarify contribution and IP policies around code used in commercial WordPress hosting or plugins. - License Compliance: - Audit licensing for components that might be involved in enterprise WordPress offerings. - Security Management: - Ensure vulnerability handling processes are documented and ready for discovery if needed. - Software Inventory: - Maintain accurate SBOMs for WordPress‑related stacks used or distributed. - Developer Support: - Provide guidance for engineers on what they can share publicly while litigation is ongoing. - Community Engagement: - Map upstream dependencies (e.g., WordPress core, WooCommerce) and their governance structures for better alignment. - Strategic Alignment: - Incorporate legal‑risk awareness into OSPO OKRs where relevant to commercial WordPress services. #### Community - Maintainers: - Review governance documents and codes of conduct; ensure they are clear and up‑to‑date. - Contributors: - Communicate clearly how contributions are licensed and may be used in commercial contexts. - Sponsors: - Request transparency reporting from funded projects where legal exposure may arise. - Ecosystem: - Coordinate with other projects on incident response and legal‑risk playbooks. #### WordPress - Core: - Continue to maintain clear licensing and contribution guidelines. - Core Performance: - No direct actions from this declaration; maintain existing perf workstreams. - Core AI: - Ensure any AI‑related features have clear terms and data boundaries documented. - **Core Program Team:** - Track major legal developments that might affect contributor agreements or governance. - Mobile: - Ensure app terms of service and data handling docs are current. - Playground: - Provide clear licensing and acceptable‑use information for in‑browser environments. - Community: - Offer sessions at meetups/WordCamps on open source, IP, and litigation basics. - Training: - Add a short module on legal context for plugin/theme developers. - Marketing: - Keep case‑related messaging factual and non‑inflammatory. - Support: - Prepare a brief internal FAQ so support can respond neutrally to user questions. - Design: - N/A from this filing; maintain existing UX work. - Documentation: - Ensure legal‑relevant docs (licenses, trademarks, brand use) are easily discoverable. - Photos: - Ensure all media usage respects licenses; good general hygiene under legal scrutiny. - TV: - If covering legal topics, coordinate content with legal counsel. - Polyglots: - Provide consistent legal notices across locales where relevant. - Accessibility: - No special action from this filing. - Meta: - Keep .org policy docs (e.g., plugin guidelines) clear and current. - CLI: - Confirm license notices and usage guidelines are documented. - Hosting: - Review customer contracts regarding IP, uptime, and indemnity. - Tide: - Ensure any scoring explanations don’t inadvertently misrepresent legal risk. - Openverse: - Maintain clear provenance and licensing data for cataloged media. - Themes: - Ensure theme guidelines and reviews emphasize license clarity. - Plugins: - Encourage plugin authors to maintain clear, consistent licensing and branding. #### The WPOCC - Programs: - Consider fellowship or microgrant tracks focused on governance and legal literacy in the WordPress ecosystem. - Projects: - Host documentation sprints on contributor agreements, codes of conduct, and governance templates. - Funding experiments: - Pilot funding for legal‑education resources (guides, workshops) for open‑source maintainers. ### FAIR - Technical independence: - Encourage signed releases and verifiable artifacts for WordPress distributions to reduce ambiguity in disputes. - Policies and covenants: - Draft model charters or covenants for funders and maintainers that clarify expectations and limit capture. - Productized governance artifacts: - Turn successful governance/agreements into templates (charters, MOUs) that others can reuse. ## 🧪 Hypotheses - H1: Courts in N.D. Cal. increasingly enforce stricter, more “narrowly tailored” sealing practices in tech‑related IP and commercial disputes. - H2: Parties filing materials referencing an opponent’s confidential documents are more likely to use administrative motions like this to shift justification duty to the designating party. - H3: Over time, defendants down‑designate more material as public when pressed to justify sealing under Local Rule 79‑5. - H4: Public‑facing tech companies in the WordPress ecosystem will adjust documentation and contracts in response to high‑profile litigation, aiming to minimize exposure. ### 📊 Methodology - For H1: - Study: Collect N.D. Cal. orders on sealing in tech/IP cases over the past 10 years; code outcomes for breadth of sealing and justifications. - Analysis: Time‑series of grant/deny rates and qualitative coding of “narrowly tailored” language. - For H2: - Study: Sample dockets where administrative motions to consider sealing of another party’s material were filed. - Analysis: Track who designates what as confidential and how courts allocate burdens. - For H3: - Study: Compare initial designations vs. post‑meet‑and‑confer vs. final court‑approved sealing in a cohort of cases. - Analysis: Quantify “down‑designation” rates and correlate with judicial comments. - For H4: - Study: Interviews and surveys of WordPress‑ecosystem companies plus document analysis of updated terms, privacy policies, and plugin agreements pre/post major cases. - Analysis: Thematic coding for patterns in risk‑mitigation language. ### ❓ Questions - How often do courts in N.D. Cal. refuse to seal material that a party has designated “Highly Confidential – Attorneys’ Eyes Only”? - Does the existence of a detailed protective order encourage broader initial confidentiality designations? - What kinds of technical information (APIs, schemas, performance metrics) are most frequently litigated in WordPress‑related disputes? - How should open‑source communities plan for discovery and subpoenas without chilling participation? ### 🔮 Future Research - Empirical mapping of how often WordPress and WooCommerce feature in federal litigation and in what contexts (IP, contracts, consumer protection). - Comparative analysis of local sealing rules across major tech venues (N.D. Cal., W.D. Wash., S.D.N.Y.). - Best‑practice guides for open‑source‑centric companies on discovery preparedness and protective orders. ### 💡 Implications - Practice: - Companies should assume internal docs and technical materials may be referenced in public pleadings; design documentation accordingly. - Policy: - Courts could offer clearer, consistent guidelines for tech‑case sealing to reduce over‑designation and motion practice. - Security: - Sensitive infrastructure details must be carefully handled in litigation to avoid inadvertently exposing attack surfaces. - Education: - Developers and maintainers need baseline legal literacy on discovery, confidentiality, and public dockets. - Funding models: - Funders may value projects that come with strong governance and legal‑risk practices as part of due diligence. ### 🧠 Learning Styles Assessment - Reading level estimate: - Likely around U.S. grade 13–15 (college level) based on legal jargon, sentence length, and structure (e.g., Flesch‑Kincaid College level style). #### 👀 Visual learners - Present: - None; this is plain text legal prose. - Improve: - Flow chart of sealing process under N.D. Cal. rules. - Timeline of procedural events (motion for leave, order, filing, sealing). #### 🔊 Aural learners - Present: - No audio version. - Improve: - 2–3 minute spoken summary of the declaration and sealing process. - TTS version of the filing. #### 🗣️ Verbal learners - Present: - Formal, precise legal language; clear structure in numbered paragraphs. - Improve: - Glossary of terms: “protective order,” “Attorneys’ Eyes Only,” “administrative motion,” etc. - Plain‑language sidebar explaining each procedural step. #### 🧩 Kinesthetic learners - Present: - None. - Improve: - Step‑by‑step “mock filing” exercise walking through drafting an administrative sealing motion and declaration. #### 🧠 Logical learners - Present: - Chronological ordering; clear if‑then reasoning (“because defendants designated materials as confidential, WPE provisionally files under seal”). - Improve: - Decision tree showing when to file under seal vs. publicly. - Table mapping designating vs. filing parties’ responsibilities. #### 🧑‍🤝‍🧑 Social learners - Present: - Implied collaboration in meet‑and‑confer process. - Improve: - Group discussion prompts for law/tech meetups on balancing transparency vs. confidentiality. #### 🧘‍♀️ Solitary learners - Present: - Self‑contained text suitable for individual close reading. - Improve: - Reflection questions (e.g., “What would you want sealed if your product were in litigation?”). #### 🌿 Naturalistic learners - Present: - No environmental or sustainability framing. - Improve: - Analogies to ecosystems (e.g., information‑flow and boundaries) if used in teaching, though not necessary to the legal content. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: - As a PDF court filing, may have minimal tagging; real‑world accessibility depends on how it was generated. - Improve: - Ensure tagged PDF structure with headings, language declaration, and proper reading order. #### Keyboard navigation - Present: - Not directly applicable to static text, but PDF viewers vary. - Improve: - Provide HTML versions with clear headings, skip links, and logical tab order. #### Contrast and readability - Present: - Standard black text on white background; usually high contrast. - Improve: - Check font size and line spacing; avoid watermarks that reduce contrast. #### Text resizing and reflow - Present: - Depends on PDF; may not reflow well on mobile. - Improve: - Offer responsive HTML or EPUB versions that reflow and respect user zoom settings. #### Media and captions - Present: - No media. - Improve: - N/A, though any future multimedia explanations should include captions/transcripts. #### Forms and interactions - Present: - None. - Improve: - N/A. #### Standards reference - Map gaps mainly to: - WCAG 2.2 AA: 1.3.1 (Info and Relationships), 1.4.4 (Resize text), 1.4.10 (Reflow) for typical PDFs. ### 🌍 DEIB Assessment #### Cultural breadth - Present: - Narrow, U.S. federal‑court, tech‑litigation context. - Improve: - If used educationally, add comparative notes on other jurisdictions or community norms. #### Inclusive language - Present: - Formal, neutral legal language; no obvious exclusionary terms. - Improve: - Provide lay summaries to reduce jargon barriers. #### Neurodiversity support - Present: - Structured into numbered paragraphs; predictable layout. - Improve: - Add headings, bullet summaries, and consistent sectioning in derivative materials. #### Representation - Present: - Focuses on institutions (court, parties, counsel), not individuals’ identities. - Improve: - Not applicable for the filing itself; educational companions can spotlight diverse legal/tech voices. #### Psychological safety - Present: - Neutral tone; no graphic or sensitive content beyond litigation context. - Improve: - Community discussions of the case should have clear moderation and guidelines. ### ✅ Logical Validity #### Strong reasoning - Type: - Mainly factual, chronological exposition; light causal reasoning. - Strengths: - Clear linkage between defendants’ confidentiality designations and WPEngine’s need to file under seal. - References to specific rules (protective order, Local Rule 79‑5(f)) anchor the actions in procedural requirements. #### Fallacies - None apparent: - The declaration does not make argumentative leaps; it reports steps taken and reasons tied to court orders and rules. #### Tone of voice - Tone: - Formal, neutral, procedural. - Examples: - “I have personal knowledge of the facts set forth herein…” - “To comply with the terms of the parties’ Stipulated Protective Order…” ### 🛡️ DARVO Analysis - Deny: - No denial or minimization of wrongdoing; the declaration does not address liability or merits. - Attack: - No attacks on opposing parties or their credibility. - Reverse victim/offender: - No attempt to recast parties as victims; it is purely procedural. - Overall: - DARVO framework is not really applicable; this is a neutral procedural filing, not a narrative about allegations. ## 🎯 Conclusion - Bottom line: - WPEngine’s counsel files a concise declaration explaining why the unredacted Third Amended Complaint and redline are being provisionally filed under seal: because defendants have labeled certain referenced documents as confidential under a protective order, and local rules require this process. - Practical next steps for readers: - If you’re involved in similar litigation, ensure your team understands: - Who designated what as confidential. - How to use administrative motions to handle another party’s sealing requests. - The need to prepare both unredacted (under seal) and redacted (public) versions of key filings. ## 🧱 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] WPEngine files declaration on sealing > [!quote] [WPGEngine, Inc., a Delaware Corporation](https://readwise.io/reader/document_raw_content/421377813) by [[Rachel Herrick Kassabian, Yury Kagan, Margret M. Caruso, Brian Mack, Michael E. Williams, Kevin Y. Teruya]] via an unnamed author. Published 2026-02-10. Accessed 2026-02-16. > “WPE is…provisionally filing under seal the following documents: (1) Unredacted Version of WPE's Third Amended Complaint; and (2) an Unredacted Redline…” Two lines: context and use. Cite data if relevant. [view highlight](https://read.readwise.io/read/01khh9zxd3ekm0nbah9r9rt4c6?endLexposition=00000_0000N_00000-003P&startLexposition=00000_0000H&emphasizeText=WPE+is%E2%80%94concurrent+and+consistent+with+its+Administrative+Motion) #xref #articleseed ID:rw_[MISSING] ### [H2] Defendants maintain select confidentiality designations > [!quote] [WPGEngine, Inc., a Delaware Corporation](https://readwise.io/reader/document_raw_content/421377813) > “Defendants agreed to down-designate all of the previously-redacted portions…except the portions that remain redacted in Paragraphs 213, 215, 219, 220, 225, 238, 297, 324, and 336…” Two lines: context and use. [view highlight](https://read.readwise.io/read/01khh9zxd3ekm0nbah9r9rt4c6?endLexposition=00000_0000F_00000-0069&startLexposition=00000_0000B&emphasizeText=Defendants+agreed+to+down-designate+all+of+the+previously-redacted+portions) #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] Filing party shifts sealing burden to designator - When a complaint references documents designated confidential by an opponent, the filing party can use an administrative motion to let the designator justify sealing. - Pointer to page/time or dataset: Pepperman declaration, paras. 5–7. - Links: [[Civil-Procedure]] [[Protective-Orders]] #### [Z2] Courts require narrowly tailored sealing motions - In N.D. Cal., courts order parties to meet, confer, and file narrowly tailored, supported sealing motions for amended complaints. - Pointer to page/time or dataset: Pepperman declaration, para. 3. - Links: [[Civil-Procedure]] [[Open-Courts]] --- ### ✏️ 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] Draft a one‑page explainer on N.D. Cal. Local Rule 79‑5 using this declaration as an example—https://readwise.io/reader/document_raw_content/421377813 #fleeting #inbox - [F2] Create a visual flowchart of the “other party’s material” sealing process for internal legal training—https://readwise.io/reader/document_raw_content/421377813 #fleeting #inbox - [F3] Compare sealing outcomes in 5 recent N.D. Cal. tech cases involving “Attorneys’ Eyes Only” designations—https://readwise.io/reader/document_raw_content/421377813 #fleeting #inbox --- <!-- deep-read:sections end -->