AI & Intelligence · Cascade
A source-backed deadline engine that calculates, connects, and recalculates your court obligations.
Included with EdgeLex
Clock rows · 5 — every row needs a citation to publish
Response due — 10 COURT days after service (AB 2347, eff. 2025); counted against the verified court closure calendar
10 court days after service dateDEFENDANTCCP § 1167 (as amended by AB 2347)Edit
Motion to quash service window — runs inside the response period
10 court days after service dateDEFENDANTCCP § 1167.4Edit
🔗 Request entry of default immediately if no response was filed
1 court day after 'Response due — 10 COURT days after service'PLAINTIFFCCP § 1169Edit
Request trial setting after answer — the court must set trial within 20 days of the request
1 court day after answer filed datePLAINTIFFCCP § 1170.5(a)Edit
Discovery cutoff — 5 days before trial (expedited UD track)
5 calendar days before trial dateBOTH SIDESCCP § 2024.040Edit
The problem
A missed or miscalculated deadline is among the most common malpractice claims — and most calendaring tools store dates without the rule, the trigger, or any way to react when a hearing moves.
One deadline’s whole life
Governed. Composed. Clocked. Applied. Protected.
Follow a court rule from an authoritative source to a locked date on the matter — every screen below is the real product.
01 · Governed
Court rules are infrastructure, not folklore.
The Court Rules Control Plane manages jurisdictions, registered source artifacts, executable rule sets, fact-trust policies, holidays, and an audit log. AI-extracted dates queue for human review; court days count against a verified closure calendar.
Court Rules Control Plane
Set up jurisdictions, register authoritative source artifacts, govern executable rule sets, and monitor court-rule runtime readiness.
Every rule set traces to registered source artifacts — statutes, local rules, standing orders — chunked and reviewable.
AI-extracted dates never flow silently into the runtime; they queue for human review first.
Court days are counted against a verified holiday and closure calendar — per court, not per assumption.
02 · Composed
A case type is authored like law, not configured like software.
The Case Type Composer walks a proceeding from forum and canonical identity through its official forms — each tagged by which side files it. The description carries its statutes, amendments included, with a verified-live date.
Canonical key
unlawful_detainer
Platform spine identity — normalized to snake_case
Court-local label
Unlawful Detainer (Eviction)
Attached forms · 5 — tag whose side files each
03 · Clocked
Each row is a sentence a lawyer can read and the compiler can execute.
The compliance clock is written in deadline sentences: 10 COURT days after service under the amended statute, a default request chained one court day onto the response row, a discovery cutoff counted back from trial. Every row needs a citation to publish.
Clock rows · 5 — every row needs a citation to publish
Response due — 10 COURT days after service (AB 2347, eff. 2025); counted against the verified court closure calendar
10 court days after service dateDEFENDANTCCP § 1167 (as amended by AB 2347)Edit
Motion to quash service window — runs inside the response period
10 court days after service dateDEFENDANTCCP § 1167.4Edit
🔗 Request entry of default immediately if no response was filed
1 court day after 'Response due — 10 COURT days after service'PLAINTIFFCCP § 1169Edit
Request trial setting after answer — the court must set trial within 20 days of the request
1 court day after answer filed datePLAINTIFFCCP § 1170.5(a)Edit
Discovery cutoff — 5 days before trial (expedited UD track)
5 calendar days before trial dateBOTH SIDESCCP § 2024.040Edit
04 · Skeletoned
Clocks become locked tasks; work wraps around them.
Every clock row lands as a governed task — 'Cascade owns these clocks,' and the due date is not editable here. Around them, the operational skeleton: verify the pre-filing notice, file the complaint and summons, evaluate the answer inside the window.
Phases
1. Notice & Pleadings ✕2. Response & Default ✕3. Trial ✕
Governed deadlines — Cascade owns these clocks
Operational tasks · 4 — the work around the clocks
05 · Applied
Five steps from rule set to living deadlines.
In the matter, the wizard picks the rule set, asks what starts the clock — service date or hearing date — and applies: events, tasks, calendar items, and reminders land on the matter. When reality moves, Recalculate moves the whole chain.
Pick a rule set, choose the triggering event, and the wizard calculates statutory deadlines and creates tasks, calendar entries, and reminders for this matter.
1. Pick Rule Set2. What Starts the Clock?3. Review Deadlines4. Reminders & Assignee5. Confirm & Apply
Selected source: GA-13121-CONTEMPT-COMPOSED · Motion for Contempt
GA-13121-CONTEMPT-COMPOSED · Motion for Contemptactive
Superior Court of Fulton County (GA-13121) · Trigger: hearing date on 8/25/2026
Events: 2 · Tasks: 2 · Calendar items: 2
06 · Protected
Mandated dates are a protected class.
On the timeline, court-mandated tasks carry a lock. They can't be dragged, hand-edited, or quietly deleted — the Cascade owns those dates, and every change flows through the rules with lineage.
Gantt · week view
🔒 Mandated bars are locked — the Cascade owns those dates; hand-editing is structurally impossible.
The difference
Dates that move together — and can’t be pulled apart.
A calendar full of individually plausible, collectively stale dates looks exactly like a correct calendar. Cascade makes that failure impossible: dates derive from cited rules, recalculate as a chain when reality moves, and the mandated ones are locked against the quiet hand-edit that starts a malpractice file.
How tasks enforce it →Citation to publish
No clock row exists without its statute — down to the amending bill and effective date.
Verified court days
Counted against each court's verified closure calendar, not a generic weekday assumption.
Locked when mandated
Court-mandated dates are a protected class — recalculated by rule, never dragged by hand.
Capabilities
What it does
Rule-aware deadline math
Calendar days, business days, or court days — computed against court holidays and closures, with a per-step calculation trace: base days, extensions, and exactly which dates were counted or skipped.
Source-to-deadline lineage
Every deadline keeps its triggering fact, its source document, the reviewed rule that produced it, and its audit lineage. “Why is this on my calendar?” always has a real answer.
Deadlines that know their dependents
A noticed motion isn't one date — it's a chain: motion filed → opposition due → reply due → hearing. Cascade models the chain, so a change at the top flows to everything downstream.
Recalculation when the case moves
A continued hearing, an extension agreement, a court closure, late service, a rejected filing, opposing counsel missing a response — Cascade identifies the affected obligations and recalculates, supersedes, preserves, or flags each one for review.
Human judgment is preserved
A lawyer's override is never silently overwritten — if recalculation would move an overridden date materially, it queues for review instead. And AI-extracted dates can't self-approve: deadline-impacting facts from OCR or inference go to a review queue first.
Fails closed, never guesses
If court-calendar coverage isn't complete and approved, Cascade blocks rather than inventing a date. It never fabricates a deadline no reviewed rule supports.
Deadlines become work
Generated deadlines carry their tasks, calendar entries, and reminders with legal context and statutory references attached — one legal clock feeding the whole platform.
Court rules, calendar & forms
A reviewed court-rules database (federal, state, county, municipal), a full legal calendar with matter-linked events and reminders, and a court-forms catalog auto-populated from matter data.
In your control
Every deadline is explainable and traceable to a rule authority — defensible, not opaque. The engine computes; your team stays the authority on what stands.
Related
Works with
Matters
Matter lifecycle, conflict checks, risk scoring, related-proceeding tracking, and a matter workspace the AI understands.
Tasks
Court deadlines as a protected class, a triage gate that turns captures into commitments, and Lex as a first-class assignee.
Lex AI & Agents
Lex isn't one application among many. It's the horizontal layer connecting matters, documents, email, messages, meetings, deadlines, and billing — grounded in your data, gated by your approvals.
See EdgeLex on your own terms.
We'll walk through self-hosting, model control, and your firm's workflows.