Limitation & datesAvailable
Limitation and procedural dates are computed in code, never invented by an LLM. Every candidate deadline exposes its rule, inputs, jurisdiction calendar assumptions, and warnings so counsel can audit the arithmetic.
A wrong limitation date is not a UX bug; it is professional risk. Luthor separates language understanding from calendar math: models may identify that a direction implicates a deadline family, but the result is produced by versioned rules with visible holidays, exclusions, and assumptions.
Every proposed deadline change is designed to show previous value, proposed value, rule identity, inputs, and warnings. Rejecting a proposal creates no calendar item. Approving it creates an operational action with a receipt trail, so the firm can explain later why a date moved.
District practice is dense with appearances, compliance windows, and statute-specific clocks. Luthor’s playbooks and deadline tools prioritize the families small litigation teams actually miss, starting with high-signal matter types and expanding with measured rule coverage rather than unverified calendar spam.
Luthor converts each new court event into a source-linked, deadline-aware strategy delta that a small litigation team can verify and approve, not a loose summary, a before/after change you can trust.
Always onLuthor watches active matters and re-plans when something material changes: the wedge against “never miss a hearing” alert tools that only ping, never think.
Practice depthDeep guidance for high-volume district matters (including NI Act §138, bail, MACT, matrimonial, rent/eviction, and property) with a rigorous generic fallback for everything else.