# Procedural Records Disclose What Substantive Coverage Omits ## Claim A record that exists to justify a process, rather than to argue its merits, has to state facts about that process's real shape in order to succeed, so the least newsworthy documents in a dispute often carry information the more-covered ones never do. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Applies to scheduling motions, changelogs, meeting minutes, commit histories, expense reports, incident timelines — any document whose purpose is procedural rather than persuasive on the merits. - Strongest when the disclosed facts are checkable by the opposing party, which constrains how much the filer can exaggerate them — treat the numbers as reliable-but-self-interested, not neutral. - Distinct from an audit trail's trustworthiness, which turns on whether the record was produced by doing the work or about the work having been done. This claim is about what a procedurally-required record incidentally reveals, independent of whether that record is itself trustworthy. - Breaks down where the procedural requirement can be satisfied with boilerplate that discloses nothing case-specific — the mechanism only fires when the justification has to be concrete to succeed. ## Evidence > [!quote] ID:rw_01m1pq01zyhn8qr663wwxrv5ec > Fact discovery closed on time on 14 May 2026 after production of nearly 400,000 documents and completion of 20 fact depositions; the parties litigated 10 motions to compel; the Court ordered additional discovery on 5 June 2026; and 16 opening expert reports were exchanged on 6 August 2026. A five-week scheduling extension request (Dkt. 371, filed 2026-09-03) has to establish the movant's diligence to meet Rule 16(b)(4)'s good-cause standard, so it recites the case's discovery footprint — ~400,000 documents, 20 depositions, 10 motions to compel, 18+ testifying experts — none of which trade coverage of this litigation as a corporate rivalry story has reported. The scale numbers appear in the brief only because the rule requires them, not because either party wanted the case's cost made visible. ## Links - [[3. Resources/Permanent Notes/An Audit Trail Is Trustworthy Only When It Is a By-Product of the Work]] — adjacent, not the same claim: that note is about what makes a record trustworthy (coupling to the work), this one is about what a procedurally-forced record incidentally discloses regardless of how trustworthy it is - [[3. Resources/MOCs/Open Source Governance MOC]] — the governance-relevant fact this filing discloses (the WordPress Foundation litigating as a counterclaimant under the same counsel as Automattic and Mullenweg) is exactly what this MOC tracks, and it surfaced only because a scheduling motion had to justify itself with case facts ## Tests / falsifiers - If a comparably newsworthy fact about this case later surfaces in trade coverage before any procedural filing discloses it, the claim that procedural records lead on disclosure is weaker than stated here. - Find a scheduling motion in another case that discloses nothing beyond dates — if procedural filings in general contain no case-specific facts, this is an artifact of one unusually complex case, not a general pattern. ## Source - [[3. Resources/Readwise/Full Document Contents/Articles/Miscellaneous Relief – 371 in WPEngine, Inc. v. Automattic Inc. (N.D. Cal., 424-cv-06917) – CourtListener.com]] — primary filed brief; the scale figures are reliable-but-self-interested, offered to support the movant's own diligence argument.