Docket Models
Docket Event Record
A docket event can be represented as exact dated data. Honesty note: simplified federal civil model; jurisdictions, local rules, and court orders vary; the pinned first step states the as-of date; not legal advice; outputs are docket and deadline traces only. Firewall doctrine: render structure, refuse interpretation, cite, abstain, and hand off.
Structured Visual
Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes a stated structural model, not the law itself. RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF.
RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF: render structure, refuse interpretation, cite provenance, abstain when unsupported, and hand off to human review.
Civil docket honesty note
Honesty note: simplified federal civil model; jurisdictions, local rules, and court orders vary; as of June 24, 2026; not legal advice; outputs are docket and deadline traces only, not filing advice.
A docket event is dated data
The stated process starts with an event record: id, type, date, label, and actor. The row is data for review, not filing advice.
Example event packet
The example event is a complaint filing dated May 1, 2026. It is one row in the toy docket.
The compiler counts authored fields
This model has 1 event and 5 authored fields.
Diagram note
The diagram shows the event row and its computed placement. The shared status vocabulary is toy trace vocabulary, not filing advice.
Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes a stated structural model, not the law itself. RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF.
RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF: render structure, refuse interpretation, cite provenance, abstain when unsupported, and hand off to human review.
Summary
Civil litigation data begins with exact dated events before deadlines, dependencies, or status labels are computed.