Product · Matter record
One record per matter. Every value says where it came from.
The complaint, the parties, the judge, every entry and every document, resolved from the public docket into one canonical record. Nothing is typed in by hand; nothing is overwritten; every field carries the fetch that produced it.
Discovery · day 12No vendor named
Halvorsen Logistics v. Meridian Foods
N.D. Tex. · 4:26-cv-00812 · Judge Alvarado · example matter
ECF 31Dec 7Motion to compel ESI from 11 custodiansmotion.compel
ECF 28Nov 24Scheduling order · production due Apr 15, 2027order.scheduling
ECF 24Nov 12Joint 26(f) report · 9 custodians per sidediscovery.request
ECF 19Oct 30Answer to complaintpleading.answer
Next deadline
Production · Apr 15, 2027 ECF 28
Expected volume
60–140 GB 87 comparables
Stage exit
~140 days 0.91
Judge
94 d to scheduling order 212 matters
94
federal districts, hourly
3
layers: raw, normalized, canonical
1
assertion behind every value
Intelligence
Stage, expected exit, computed deadlines, judge and counsel profiles, expected review volume. Each figure with its confidence and comparable count.
Canonical record
Source-agnostic matter, parties, counsel, judge, entries, deadlines. Every value backed by the record it came from. Confirmations in teal.
Source-normalized
One table per court system, raw strings kept, parser version recorded. Reprocessed when a parser improves; never edited by hand.
Raw record
Every fetch from the court, stored as received, immutable. The layer nothing is allowed to change.
What a record holds
Parties and counsel
As the court lists them, resolved to one entity each; appearances are public record, not a statement about who is anyone's client.
Judge
Assigned and reassigned, with the entry that did it.
Docket entries
Every numbered entry with its text as written and an event type with a confidence; under 0.8 goes to human review.
Documents
Metadata for every filing; text when fetched; sealed documents are listed and never opened.
Deadlines
Computed from the trigger entry with its rule id, or read from the order as court-set.
Provenance
Which fetch, which method, what confidence — kept even when a later source wins.
The court's words are quoted, labelled, and never obeyed.
Every response names the fields that hold court-supplied prose under untrusted_text; the product shows them, searches them, cites them by entry, and never treats them as instructions.
sequence_no: 28 entry_date: 2026-11-24 event_type_canonical: order.scheduling event_type_confidence: 0.97 text_raw: "SCHEDULING ORDER …" // untrusted_text source_record_id: 01J8XA5C0B7M2P9Q1R3S5T7V9X
The record is the product. Everything else reads from it.
Ask, deadlines, profiles, alerts and the API all read the same canonical record, so a correction in one place is a correction everywhere.
Related