Matter record
One record per matter. Every value says where it came from.
The complaint, the parties, the judge, the entries and the documents, resolved from the public docket into one canonical record. Nothing is typed in by hand or overwritten; each field carries the fetch that produced it.
Halvorsen v. Meridian
N.D. Tex. · 4:26-cv-00812 · Judge Alvarado
Discovery · day 22No vendor named
ECF 31Sep 22Motion to compel ESI from 11 custodiansmotion.compel
ECF 28Sep 8Scheduling order; production due Feb 1, 2027order.scheduling
ECF 24Aug 26Joint 26(f) report; 9 custodians per sidediscovery.request
ECF 19Aug 13Answer to complaintpleading.answer
Next deadlineProduction, Feb 1, 2027ECF 28 · court-set
Expected volume60–140 GB87 comparables
Stage exit~140 daysconfidence 0.91
Judge94 d to scheduling order212 matters
Example matter. Parties, counsel and figures are invented for illustration.
4
layers, from raw fetch to intelligence
3
layers: raw, normalized, canonical
1
assertion behind each 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. Each 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; not edited by hand.
Raw record
Each 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
Numbered entries with their text as written and an event type with a confidence; under 0.8 goes to human review.
Documents
Metadata for each filing; text when fetched; sealed documents listed, not 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, quoted and labelled as the court’s.
Responses name the fields that hold court-supplied prose under untrusted_text, so your systems can show them, search them and cite them by entry without acting on them.
ECF 28, scheduling order
Halvorsen v. Meridian · N.D. Tex. · 4:26-cv-00812 · Sep 8, 2026
The court’s textQuoted as filed
“SCHEDULING ORDER. Pursuant to Fed. R. Civ. P. 16(b), the Court enters the following schedule. All fact discovery, including the production of documents, shall be completed by February 1, 2027. Dispositive motions shall be filed by April 15, 2027.”
What Grey Matter read from it
Event typeScheduling orderorder.scheduling · confidence 0.97
Deadlines createdProduction, Feb 1, 2027; dispositive motions, Apr 15, 2027court-set · read from this entry
SourcePACER docket reportfetched Sep 8, 2026, 4:12 pm
Shown, searched and cited by entry. Not acted on.
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