Skip to main content

amagi-litigation-deadlines

Compute litigation response deadlines from a trigger event and a date, with a markdown table and an .ics calendar file, and a citation for every rule applied.

Demo

demo

$ amagi-litigation-deadlines calc --rules frcp --event answer-complaint --date 2026-10-19
NOT LEGAL ADVICE: This is not legal advice. amagi-litigation-deadlines computes dates from a
code-maintained summary of court rules. Every computed deadline must be verified by an attorney
against the court's current rules, local rules, standing orders, and any case-specific order
before you rely on it.

| Event | Trigger date | Deadline | Rolled forward? | Rule cite | Counting rule |
|---|---|---|---|---|---|
| Answer to complaint (served, not waived) | 2026-10-19 | 2026-11-09 | no | Fed. R. Civ. P. 12(a)(1)(A)(i) | Fed. R. Civ. P. 6(a) |

Source rule set note: Current as of the 2026-10-20 build of this tool. Verify against the
official text at https://www.law.cornell.edu/rules/frcp or
https://www.uscourts.gov/rules-policies/current-rules-practice-procedure before relying on any
computed date.

amagi-litigation-deadlines is a calculator, not a lawyer. It applies a code-maintained summary of a rule's day-counting method and holiday list. It does not know about local rules, standing orders, judge-specific procedures, electronic-service variations, prior extensions, or any court-specific closure that isn't on its bundled holiday list. Every deadline this tool computes must be independently verified by an attorney against the court's current rules before anyone relies on it. Missing a deadline is a malpractice risk — do not skip that verification step.

Install

pipx install amagi-litigation-deadlines

Usage

List the bundled rule sets:

$ amagi-litigation-deadlines list-rule-sets
frcp       Federal Rules of Civil Procedure (civil, district court) (counting rule: Fed. R. Civ. P. 6(a))
florida    Florida state courts (civil) (counting rule: Fla. R. Jud. Admin. 2.514(a))

List the events available in a rule set:

$ amagi-litigation-deadlines list-events --rules frcp
answer-after-waiver             60 day(s)  Fed. R. Civ. P. 12(a)(1)(A)(ii)  -- Answer after waiver of service (domestic defendant)
answer-after-waiver-foreign     90 day(s)  Fed. R. Civ. P. 12(a)(1)(A)(ii)  -- Answer after waiver of service (defendant outside any US judicial district)
answer-complaint                21 day(s)  Fed. R. Civ. P. 12(a)(1)(A)(i)  -- Answer to complaint (served, not waived)
answer-to-amended-pleading      14 day(s)  Fed. R. Civ. P. 15(a)(3)  -- Response to an amended pleading (minimum period; may be later if original response not yet due)
discovery-response              30 day(s)  Fed. R. Civ. P. 33(b)(2) / 34(b)(2) / 36(a)(3)  -- Response to interrogatories, document requests, or requests for admission
removal-notice                  30 day(s)  28 U.S.C. S 1446(b)(1); counting method per Fed. R. Civ. P. 6(a) (applies to statutory periods not otherwise specifying a method)  -- Notice of removal from state court
reply-to-counterclaim           21 day(s)  Fed. R. Civ. P. 12(a)(1)(B)  -- Reply to a counterclaim
reply-to-crossclaim             21 day(s)  Fed. R. Civ. P. 12(a)(1)(B)  -- Answer to a crossclaim

Compute a deadline and also write an .ics file you can import into your calendar:

$ amagi-litigation-deadlines calc --rules florida --event answer-complaint --date 2026-10-19 \
    --jurisdiction "Example Circuit Court, Example County" --ics deadline.ics

NOT LEGAL ADVICE: ...
Jurisdiction (informational only, not used in the calculation): Example Circuit Court, Example County

| Event | Trigger date | Deadline | Rolled forward? | Rule cite | Counting rule |
|---|---|---|---|---|---|
| Answer to complaint | 2026-10-19 | 2026-11-09 | yes | Fla. R. Civ. P. 1.140(a)(1) | Fla. R. Jud. Admin. 2.514(a) |

Source rule set note: Current as of the 2026-10-20 build of this tool. Verify against the
official text at https://www.flcourts.gov/Resources-Services/Office-of-General-Counsel/Rules or
the Florida Bar's rules of procedure page before relying on any computed date.

Wrote deadline.ics

(The raw 20-day count from 2026-10-19 lands on Sunday 2026-11-08, so it rolls forward to the next non-weekend, non-holiday day, Monday 2026-11-09 — this is exactly the kind of roll-forward step you must re-verify against the court's calendar, since local closures aren't modeled here.)

--jurisdiction is a free-text label printed back for your own records; it is not used in the calculation (the rule set you pick with --rules drives the counting method and holiday list).

Rule sets and sources

Each bundled rule set is a YAML file under src/amagi_litigation_deadlines/data/, and every event in it carries its own rule citation. The two counting-method citations:

Rule set Counting-method citation Legal-holiday citation
frcp Fed. R. Civ. P. 6(a) 5 U.S.C. S 6103 (via Fed. R. Civ. P. 6(a)(6)(A))
florida Fla. R. Jud. Admin. 2.514(a) Fla. Stat. S 683.01 (via Fla. R. Jud. Admin. 2.514(a)(6))

See src/amagi_litigation_deadlines/data/frcp.yaml and src/amagi_litigation_deadlines/data/florida.yaml for the per-event citations (e.g. Fed. R. Civ. P. 12(a)(1)(A)(i) for the standard answer-to-complaint deadline). Rules change — contributions that update a citation, add a jurisdiction, or fix a holiday list are welcome as PRs against the YAML files.

Adding a jurisdiction

Copy an existing file in src/amagi_litigation_deadlines/data/, change the id, name, counting_rule_cite, and holiday_set (add a new holiday function in holidays.py if the jurisdiction's legal-holiday list differs), then add events: entries with a label, days, and cite for each deadline. Add it to _BUNDLED in rules.py.

Star this if it saved you time

If amagi-litigation-deadlines saved you from counting days by hand, a star helps other solo/small-firm litigators and paralegals find it.

Other AmagiLabs projects

  • amagilabs on GitHub — the full catalog of small, open-source developer and productivity tools from AmagiLabs (Amagisolutionsgroup, Inc.).
  • amagi-watch — turns a video URL into something Claude can read (transcript + key frames + timestamped index).

License

MIT — see LICENSE. Copyright (c) 2026 AmagiLabs (Amagisolutionsgroup, Inc.).

Metadata

Release files for amagi-litigation-deadlines 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for amagi-litigation-deadlines 0.1.0
File Size Uploaded Provenance
amagi_litigation_deadlines-0.1.0.tar.gz 15.6 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for amagi-litigation-deadlines 0.1.0
File Interpreter ABI Platform
amagi_litigation_deadlines-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 30.7 kB

Release files / amagi_litigation_deadlines-0.1.0.tar.gz

Download URL amagi_litigation_deadlines-0.1.0.tar.gz
Size 15.6 kB
Tags Source
SHA-256 checksum
How to use checksums
7444df75a765cd0a490bda44b3e90050d35ca44b336a9375c8bfa6f68ecbe1b0
BLAKE2b-256 checksum
How to use checksums
1b9f1cf1ffe8a45dc1ac650c8ed8614904b0d4fb8a210f80fdd56f1c999cc84a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.

Transparency log

Release files / amagi_litigation_deadlines-0.1.0-py3-none-any.whl

Download URL amagi_litigation_deadlines-0.1.0-py3-none-any.whl
Size 15.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
84d39cff5512bdce8d8e0de20ca035ff7693e19c713f8a63d005f372e430831b
BLAKE2b-256 checksum
How to use checksums
ba61d4bedfa367be37eb23e5e14bb0f53a2cbea84045c598b1506f104fb9b921
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.

Transparency log

Security for amagi-litigation-deadlines 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for amagi_litigation_deadlines-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page