Docket Models

Discovery Response Clock

A stated discovery response clock can be recomputed from service. 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.

TOY MODELNOT LEGAL ADVICESTRUCTURE ONLYHUMAN REVIEW REQUIRED
Discovery response clockDiscovery response clockscope: US-FED | Discovery response clock | as of 2026-06-24points are events; intervals are deadline deltas; arrows are dependenciesSimplified federal civil model; rules and orders vary; not legal advice; docket traces only, not filing advice; on_time and late aretoy delta labels only, not timely or untimely filing conclusions.2026-07-012026-07-31scope=US-FED model=Discovery response clock as_of=2026-06-24note=Simplified federal civil model; rules and orders vary; not legal advice; docket traces only, not filing advice; on_time and late are toy deltalabels only, not timely or untimely filing conclusions.status vocabulary=early,event,late,on_timeorder=1 id=interrogatories date=2026-07-01 elapsed=0 status=event due=none delta=none reach=1 label=Interrogatories servedorder=2 id=responses date=2026-07-31 elapsed=30 status=on_time due=2026-07-31 delta=0 reach=0 label=Responses servedevent=interrogatories date=2026-07-01 label=1 interrogatories 2026-07-01event=responses date=2026-07-31 label=2 responses 2026-07-31event=due_responses date=2026-07-31 label=due responses 2026-07-31interval=2026-07-01->2026-07-31 label=due 30 daysdependency=interrogatories->responses label=response
highlighted = computed this step

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.

federal civil model as of June24,2026\text{federal civil model as of }June 24, 2026

Discovery response clock is stated

Fed. R. Civ. P. 33(b)(2) is modeled as a simplified response clock from a service event.

service event+response days\text{service event}+\text{response days}

Example discovery service

Interrogatories are served on July 1, 2026. The model uses 30 days after service.

days=30\text{days}=30

The service date governs the due date

The stated response clock is 30 days after service. The recomputed due date is July 31, 2026 with delta 0.

days=30,delta=0\text{days}=30,\quad \text{delta}=0

Diagram note

The diagram shows the discovery response clock as a docket trace. Any on_time or late row text is a toy delta label only, not a timely or untimely filing conclusion.

delta labels are not timeliness conclusions\text{delta labels are not timeliness conclusions}

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.

TOY MODELNOT LEGAL ADVICESTRUCTURE ONLYHUMAN REVIEW REQUIRED
Discovery response clockDiscovery response clockscope: US-FED | Discovery response clock | as of 2026-06-24points are events; intervals are deadline deltas; arrows are dependenciesSimplified federal civil model; rules and orders vary; not legal advice; docket traces only, not filing advice; on_time and late aretoy delta labels only, not timely or untimely filing conclusions.2026-07-012026-07-31scope=US-FED model=Discovery response clock as_of=2026-06-24note=Simplified federal civil model; rules and orders vary; not legal advice; docket traces only, not filing advice; on_time and late are toy deltalabels only, not timely or untimely filing conclusions.status vocabulary=early,event,late,on_timeorder=1 id=interrogatories date=2026-07-01 elapsed=0 status=event due=none delta=none reach=1 label=Interrogatories servedorder=2 id=responses date=2026-07-31 elapsed=30 status=on_time due=2026-07-31 delta=0 reach=0 label=Responses servedevent=interrogatories date=2026-07-01 label=1 interrogatories 2026-07-01event=responses date=2026-07-31 label=2 responses 2026-07-31event=due_responses date=2026-07-31 label=due responses 2026-07-31interval=2026-07-01->2026-07-31 label=due 30 daysdependency=interrogatories->responses label=response

Summary

A discovery clock row should expose the source label, service event, day count, computed due date, and delta.

source plus service plus due date\text{source plus service plus due date}