Discovery: capabilities and limits

What is owed, and when

• Twenty-five interrogatories, and the last day a request can go out

  Propounded items count against the Rule 33(a)(1) default of 25 as an advisory, never a block; discrete subparts are not counted. State matters get no federal counter. The last day to serve a request is counted backwards through the forum's rule, holidays and mail days.

• The one pretrial clock whose expiry forfeits a right

  Receiving the other side's Rule 26(a)(3) list starts a 14-day objection period, and an objection not made inside it is waived. Recording the list raises the clock as a task to confirm and writes nothing to the calendar. An unrecorded service date yields no date.

• Objections from the request's own words, and a promise watched until it moves

  Seven grounds fire deterministically on the request text; one dismissed on item four never returns there. Order is adjusted by the firm's recorded outcomes in this forum, where a motion to compel granted reads as that objection overruled. A supplement promise raises one self-closing task.

A production arrives

• Load files in both directions, and a receipt nothing edits

  Shipped

  Concordance DAT, Opticon OPT and EDRM XML are read and written, so a production arrives and leaves in the form the other side uses. An inbound set persists as an immutable receipt bounded at 50,000 members. Only a validated SHA-256 may claim a document's content.

• Seven kinds of gap, hunted with no model in it

  Shipped

  Findings land as a closed set of seven kinds, from Bates holes and broken families to privileged material that reached a production. A deterministic key means a re-scan refreshes the open row and a dismissed finding is never reopened. Every finding quotes a 240-character span.

• A gap phrased as a question when it must be

  Shipped

  Where the load file discloses document-level numbers only, the gap is reported as a question rather than an accusation of withholding. A sequence missing more than 200,000 page numbers returns no list at all rather than a partial one presented as the whole.

• Nine deficiencies, a letter, and a chronology that certifies

  Shipped

  A received set is graded against the terms recorded at the Rule 26(f) conference, only against fields the load file can show. Nine deficiency kinds each carry a governing-standard paragraph. The cure-by date stays a placeholder, and the trail compiles into a Rule 37(a)(1) chronology.

Review

• A ranker trained on the calls already made

  Shipped

  Order is learned from the attorney's own responsiveness decisions by a deterministic pass over embeddings already held; a model's guess never becomes training truth. The refit runs on 25 new labels behind a ten-minute debounce, and richness stays unknown until a control set is coded.

• A reviewer's rate and two element ledgers, both derived at read time

  Throughput and overturn are computed from the decision ledger at every read, and a rate exists only past ten recorded calls and thirty active minutes, each gap capped at ten. The element reconciliation reports both ledgers, resolves nothing, and fails closed on a partial read.

Privilege and redaction

• Classification takes the more protective of two

  Shipped

  Where a model and a rule-based scan disagree, the more protective reading wins and the basis stays visible; a model saying not privileged is a signal, not an answer. Redactions burn at 200 DPI and are read back by OCR, and no derivative is auto-cleared.

• A standing diff, and six named ways a log entry discharges nothing

  Shipped

  Two alarms never merge: privileged material that reached a production, the clawback call under Rule 26(b)(5)(B), and material withheld with no adequate entry under Rule 26(b)(5)(A). Adequacy is a named defect list, because every column is nullable and a blank row satisfies a presence check.

What leaves the building

• Three reasons a document does not leave, and no service without a rule

  Shipped

  The producible gate blocks a document because it is privileged, unreviewed, or because the lookup that would have cleared it did not return it. The bundle then fails closed against the negotiated protocol. Direct-email service needs a recorded authorization naming the rule that permits it.

Proof of coverage

• Where a custodian's name came from, and a plan the model may not populate

  A custodian's name carries its source on a five-rank lattice: attested above connector above load file above inferred from sender above a model's guess. A proposed row naming anybody outside the matter's recorded people is refused, and an ungrounded row is retained rather than promoted.

• Wilson intervals, a thirty-sample floor, and a run a closure may not cite

  Recall, precision and elusion come from a seeded, digest-fingerprinted draw with two-sided Wilson score intervals at the 0.95 confidence level, and a denominator under thirty is labelled limited evidence. A Rule 26(g) closure may cite a run only where a number exists.

The pages opened from outside

• An emailed link, a code sent another way, and a frozen package behind it

  Opposing counsel signs in with the address the link was sent to plus a 128-bit code on another channel, so a wrong address, a revoked portal and a token never issued answer alike. What renders is an allow-list built field by field, and no caption.

• A no-login door with a slot count, and a hold link that authors nothing

  A minted link drops a file into a named matter with no account, and the last slot is claimed by compare-and-swap, so two racers produce one winner. A hold link answers every token's bare fetch identically and writes nothing; acknowledging is a separate, version-stamped gesture.

Limits

• A gap is what the received set does not contain between its own first and last number. It is not proof of withholding.
• A rate with no denominator is reported as unmeasurable, never as zero.
• An objection ground this firm has no recorded outcome for carries no history at all, rather than a zero that reads like a loss.
• A cross-matter match is on recorded extracted text. That the bytes on screen are the bytes that were coded is reported as unproved.
• Coverage is what the record shows was searched, collected and reviewed. It is not a representation about material nobody recorded.

What BRON refuses

• Hunt a production it cannot read in full.

  Past its 200,000-document ceiling the hunt is declined outright. A partial production cannot be hunted honestly, and a short hunt would report a clean set rather than an unread one.

• Accuse the other side of your own privilege hygiene.

  The two outbound privilege kinds are excluded from the deficiency catalog by name. They are ours, not theirs.

• Advise you to log your own filed brief.

  That advice was shipped and then removed. The candidate set includes the firm's own filed motions, served responses and hold notice, so following it would put a public filing onto the log served on opposing counsel.

• Call a page unread and a page unreadable the same thing.

  An unread page is deferred with a continuation row naming where to resume. A page that will not be read is truncated. One is a queue, the other is a limit.

• Count a waiver clock from the day the file was uploaded.

  The trigger is the day their Rule 26(a)(3) disclosures were served on you, and today is not it. An undated ask is honest; a date counted from an upload is invented, and on the one clock that forfeits a right an invented date is worse than none.

• Let a model's guess overwrite a person.

  Custodian attribution is ranked, and a weaker source cannot overwrite a stronger one. The database raises SQLSTATE 55000 and the write that tried keeps the rest of its update and says what was declined.

• Rest a Rule 26(g) closure on a run that measured nothing.

  A completed run whose recall and elusion both came back unmeasurable measured nothing about what the search missed. No bar is invented for those rates either: the intervals are reported and the proportionality judgment stays with counsel.

• Ship a production the negotiated protocol refuses.

  Outbound validation fails closed at the export route. The attorney's conscious override is demoting the protocol to negotiating, which is a recorded status change with an author, not a checkbox that clears a warning. What ships is byte work: every page stamped with its true number, the confidentiality legend, and a manifest.

• Quote a reviewer's pace off a five-call sprint.

  Ten recorded calls and thirty active minutes are both required before a rate exists. Five calls in four minutes extrapolates to a number that is arithmetic rather than a measurement.

• Copy another matter's coding onto this one.

  The cross-matter screen shows that this firm has coded the same recorded text before, and stops there. It copies no call, links no documents, never crosses a firm, and withholds the advisory entirely when the set of matters this reader may see cannot be read.

• Tell a link scanner whether a hold token is real.

  The acknowledgment page's plain fetch never parses or looks up its token, so a live one, an expired one, a revoked one, one already used and one that was never issued all return the same bytes. A preview that answered would let a prefetcher both probe the register and author evidence in a custodian's name. Under Rule 37(e) the thing being built is who acknowledged what, and when.

• Show the responding side the matter caption.

  The counterparty payload is built field by field and nothing is spread into it, so a column added upstream tomorrow cannot arrive through it, and the caption is left out by name. A matter title here is routinely an internal nickname carrying the firm's own read of the case, and the side responding already knows which case it is in.

• Release a package it could not record.

  The download row is written before a byte of the frozen ZIP moves, and a failed write returns that no package was released rather than quietly sending an unrecorded one. The stored object is re-hashed against the build's receipt first, so bytes that do not match their own record are refused instead of delivered. Only a finished transfer spends one of the three download slots.

They produced 4,200 documents, and ours goes out next week. What is missing on their side, and what must not leave on ours?

Inspect incoming productions, find gaps and see what the review has covered. Prepare outgoing material with its disclosure checks in view. Each finding keeps the load-file row, page or ledger entry behind it.

Inputs

• The matter brain
• Every production and its load file
• Custodians, holds and collection receipts
• The privilege log
• The terms recorded at the Rule 26(f) conference

Outputs

• The meet and confer, and a motion to compel
• Drafting and the citation gate
• Deadlines
• Trial exhibits and designations
• Valuation