WPE v. Automattic Dkt. 362 — Transcript Order  🔗 **Source:** [WPE v. Automattic Dkt. 362 — Transcript Order](https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.362.0.pdf#deepread) > [!note]+ Document Notes > tags: [court-transcripts, court-procedure, wordpress-litigation, docket-records] > author: "[MISSING] — the text layer of the CAND 435 form does not capture the filled-in contact or attorney fields" > source: U.S. District Court, N.D. Cal. (Dkt. 362, via CourtListener RECAP) > reference: https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.362.0.pdf > date created: 2026-08-13 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > # 🏷️ Title: Transcript Order (Form CAND 435), Dkt. 362, WPEngine, Inc. v. Automattic, 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 - Docket 362, *WPEngine, Inc. v. Automattic, Inc. et al.*, No. 4:24-cv-06917-AMO (N.D. Cal. filed July 30, 2026) - Form CAND 435 (Transcript Order, N.D. Cal., rev. 08/2018) ## 📝 Summary - What happened: On July 30, 2026, a party filed a one-page Transcript Order (Form CAND 435) on the WPE v. Automattic docket, requesting a court-reporter transcript of a proceeding in the case. - Why it matters: A transcript order right after the late-July flurry (sanctions motion Dkt. 357, sealing motion Dkt. 358, magistrate referral Dkt. 359, re-notice Dkt. 360) suggests a party wants the verbatim record of a recent hearing — commonly a prelude to briefing, objections to a ruling, or appellate positioning. - Key stakeholders: The ordering party (not identifiable from the extracted text), the court reporter, and both litigation camps that will eventually cite the transcript. - Risks and tradeoffs: Minimal — the filer certifies payment of transcription charges; delivery speed depends on the tier selected (ordinary 30-day through hourly/realtime). - Bottom line: Routine records mechanics; the only analytic signal is that someone considered a recent proceeding worth paying to transcribe. The captured text layer preserves only the blank form fields, so the specific hearing, format, and requester are not recoverable from this file. ## 📖 Main Content - Form CAND 435 is the Northern District of California's standard transcript request. One form is used per court reporter, and it captures: contact and attorney information, case name and number, the proceedings to transcribe (judge, hearing type, portion), formats (PDF, text/ASCII, paper, condensed, ECF access), and delivery tier (ordinary 30-day, 14-day, expedited 7-day, 3-day, daily, hourly, realtime). - The form distinguishes appeal from non-appeal orders and criminal from civil, and it excludes CJA requests (those use Form CJA24). In forma pauperis orders require an attached court order. - Critically for this capture: the text extraction preserves the form's printed labels but none of the handwritten or typed field values. Who ordered the transcript, which proceeding, which judge's initials, and which delivery tier were selected cannot be determined from this txt file — the PDF image would need visual inspection. - Signing the form is a payment certification: the requester commits to pay the deposit plus any additional charges before the reporter begins work. - Context from the surrounding docket: filings 357-360 (July 28-29, 2026) concern WPE's spoliation sanctions motion and its referral to Magistrate Judge Krishnan; a July 30 transcript order plausibly targets a proceeding connected to that sequence, but the form itself does not say so. ### 🗒️ Notes - Form identity: "CAND 435 (CAND Rev. 08/2018)," headed "UNITED STATES DISTRICT COURT / NORTHERN DISTRICT OF CALIFORNIA — TRANSCRIPT ORDER." - Field inventory visible in the text layer: contact person/phone/email (1a-3), attorney name/phone/email (1b-3), mailing address (4), case name (5), case number (6), court reporter name or FTR (7), order type checkboxes (8), transcript(s) requested with format and delivery grids (9a-c), additional comments (10), signature and date certification (11-12). - All value fields are empty in the extraction — this is a text-layer limitation, not necessarily a blank filing. - Delivery tiers on the form range from ordinary (30-day) to realtime; ECF access is included with purchase of PDF, text, paper, or condensed formats. - "COURT USE ONLY / DUE DATE" box appears top right, unfilled in the text layer. ## 📚 References - [Dkt. 362 PDF (CourtListener RECAP)](https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.362.0.pdf) - [N.D. Cal. court reporter and transcript information](https://www.cand.uscourts.gov/about/court-reporters/) - [CourtListener docket, WPEngine v. Automattic, 4:24-cv-06917](https://www.courtlistener.com/docket/69221176/wpengine-inc-v-automattic-inc/) ## 🗣️ Paraphrase - A party in WPE v. Automattic submitted the district's standard one-page transcript request form, which asks the court reporter to produce a transcript of a specified proceeding in a chosen format and delivery speed, with the requester certifying they will pay all charges. - The captured text shows only the form's printed structure; the filled-in specifics (requester, hearing, format, speed) did not survive text extraction and would require viewing the PDF image. ## 📰 Newsletter - Small but telling docket entry in WPE v. Automattic: a transcript order landed July 30, right on the heels of the spoliation sanctions motion and its referral to Magistrate Judge Krishnan. Someone wants the official record of a recent proceeding in writing — usually a sign a party intends to quote it in briefing. The form's text layer doesn't reveal who or which hearing, so this one goes in the "watch the PDF" pile. ## ✅ Action Items #### DevRel - Not applicable to this source — a transcript order form generates no developer-advocacy work. #### OSPO - Not applicable to this source — no policy, license, or security action follows from a records request. #### Community - Not applicable to this source — no community program action arises from this filing. #### WordPress - Not applicable to this source — no core, meta, or contributor-team action follows from this filing. #### The WPOCC - Not applicable to this source — the organization is not referenced in this filing. ### FAIR - Not applicable to this source — no technical-independence artifact is implicated by a transcript order. ## 🧪 Hypotheses - The transcript order targets a proceeding tied to the late-July sanctions/referral sequence (Dkts. 357-360), given the July 30 filing date. - The ordering party selected an expedited delivery tier, since a September 30 hearing date creates briefing pressure. - The transcript, once produced, will surface in the sanctions briefing or in objections to a magistrate ruling. ### 📊 Methodology - Inspect the Dkt. 362 PDF image for the filled fields; cross-reference the docket's minute entries around late July 2026 to identify which proceeding was transcribed; watch for a reporter's transcript entry and later citations to it. ### ❓ Questions - Which proceeding is being transcribed, and by which party? - Was a hearing held in late July 2026 that the minute entries would reveal? - What delivery tier was chosen, and does the due date precede the sanctions briefing deadlines? ### 🔮 Future Research - Once the transcript docket entry appears, check whether it is restricted (transcripts have a 90-day redaction window under Fed. R. Civ. P. 5.2 procedures) and when it becomes publicly available. ### 💡 Implications - For docket followers, transcript orders are an early-warning signal: they mark the proceedings a party considers consequential enough to pay for, ahead of any visible briefing use. ### 🧠 Learning Styles Assessment Not applicable to this source — a blank administrative form is not instructional content and has no pedagogy to assess. ### 📊 Accessibility Assessment Not applicable to this source — this is a court-issued PDF form; its accessibility is the court's design choice, not the filer's, though the empty text layer illustrates why scanned/flattened form values are a records-access problem. ### 🌍 DEIB Assessment Not applicable to this source — an administrative form contains no audience-facing content to evaluate for inclusion. ### ✅ Logical Validity #### Strong reasoning - Not applicable in the argumentative sense — the form makes no arguments. Its one logical structure is the payment certification: signature entails liability for deposit plus additional charges. #### Fallacies - None — there are no claims to test. #### Tone of voice - Bureaucratic-instructional: imperative field labels and instructions such as "Please use one form per court reporter." ### 🛡️ DARVO Analysis Not applicable to this source — an administrative form contains no accusations, denials, or victim-offender framing. ## 🎯 Conclusion - Dkt. 362 is the least substantive of the late-July filings: a standard CAND 435 transcript request whose filled-in values did not survive text extraction. Its significance is entirely contextual — filed one day after the sanctions motion was re-noticed to Magistrate Judge Krishnan, it likely marks a party locking down the record of a related proceeding. - Next step for readers: view the PDF image to recover the requester and target hearing, and watch the docket for the transcript's completion entry. ## 🔄 Refactor Appendix — Transcript Order, Dkt. 362 (Form CAND 435) ### 📚 Literature Atoms (H3) #### [H1] Transcript orders bind the requester to pay all charges > [!quote] Source: gov.uscourts.cand.437474.362.0.txt > By signing below, I certify that I will pay all charges (deposit plus additional). **Context & use**: - Order & Certification block (items 11-12) at the bottom of the form. - The signature is a financial commitment, which is why transcript orders signal genuine intent to use the record. **Tags**: #xref **Highlight**: n/a — source is a local docket text capture, not a Readwise highlight <!-- atomicity: 1 idea ✓ --> #### [H2] CAND 435 requires one form per court reporter > [!quote] Source: gov.uscourts.cand.437474.362.0.txt > Please use one form per court reporter. **Context & use**: - Form header instruction, top of page 1. - Explains why multi-hearing transcript requests can generate several near-identical docket entries. **Tags**: #xref **Highlight**: n/a — source is a local docket text capture, not a Readwise highlight <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] Flattened form PDFs lose their answers in text extraction **Claim** (one sentence, Courtney's voice): Text-layer extraction of court form PDFs preserves the printed questions but drops the filled-in answers, so form-type docket entries always need visual inspection of the PDF image. **Evidence pointer**: [[#H1]] — the captured file contains every field label of CAND 435 and none of the values **Scope & conditions**: Holds for scanned or flattened form filings; breaks when forms are filed as fillable PDFs with live text fields. **Links** (≥1 with annotation): - [[RECAP docket capture workflow]] — because applies-in evidence-gathering pipelines - [[OCR limitations in records research]] — because extends <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Open the Dkt. 362 PDF image to identify the requester and target proceeding — https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.362.0.pdf #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Check Dkt. 362 PDF image for the transcribed hearing details — WPE v. Automattic case file #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/WPE v. Automattic Dkt. 362 — Transcript Order.md|WPE v. Automattic Dkt. 362 — Transcript Order by US District Court, N.D. Cal.]] ## Highlights - UNITED STATES DISTRICT COURT TRANSCRIPT ORDER COURT USE ONLY NORTHERN DISTRICT OF CALIFORNIA Please use one form per court reporter. DUE DATE: CAND 435 (CAND Rev. 08/2018) Please read instructions on next page. 1a. CONTACT PERSON FOR THIS ORDER 2a. CONTACT PHONE NUMBER 3. CONTACT EMAIL ADDRESS ([View Highlight](https://read.readwise.io/read/01kzxrjvgvxvxwrksbw5pxt5p7)) - Note: CAND 435 transcript order form — filled values didn't survive text extraction; see PDF for specifics. - Tags: atom/fleeting/f1