Docket Models
Hearing, Order, Judgment
Court events are docket records with dependencies. 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.
Court events are docket rows
The process records hearing, order, and judgment as dated events with dependencies. The model does not predict what the court will do.
Example event chain
The model records 3 court events from August 1, 2026 through August 8, 2026.
Elapsed days follow the dated chain
The compiler orders the events and recomputes 7 elapsed days across them.
Diagram note
The diagram is a dependency trace among docket events. The shared status vocabulary is toy trace vocabulary, not a merits or enforcement outcome.
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
Court events can be modeled as dated records linked by dependencies, with legal review outside the model.