Legal Work · Lex Research
Agentic legal research with the proof attached — from your record, the caselaw, and the open web.
Included with EdgeLex
Maya, California law permits further responses when an RFP response contains an incomplete compliance statement, an inadequate inability-to-comply representation, or an objection that is meritless or too general. The moving party must show request-specific good cause, meet and confer, and ordinarily give notice within 45 days. (Code Civ. Proc., § 2031.310(a)–(c).) citation:CCP § 2031.310
⚖ Governing standard
A compliant response must address each RFP separately — compliance, inability to comply, or objection. (§ 2031.210.) citation:CCP § 2031.210 An objection must identify with particularity the documents covered and state its specific ground. (§ 2031.240(a)–(c).) citation:CCP § 2031.240
The motion must make a fact-specific showing of relevance and good cause. (Kirkland v. Superior Court (2002) 95 Cal.App.4th 92, 98.) citation:Official court discussion of Kirkland standard
📌 Application to Northstar’s Set Two objections
Northstar’s January 12 responses were objections-only, asserted globally rather than request by request… The court’s June 15 minute order confirms the analysis: code-compliant supplemental verified responses ordered for RFP Nos. 1–9, 12, 15, and 16, with a legally compliant privilege log.
Ask Lex to research, review, draft, or explain… (type / for commands)
The problem
Legal research AI splits into two camps: chatbots that guess from the open web — which is exactly how fabricated citations end up in filings — and research platforms that know the law but not your cases. Neither produces an answer you can trace, claim by claim, from your record to the authority to the filing.
One question’s journey
Asked. Worked. Hunted. Gated. Delivered. Standing.
Every other surface holds the case. Research answers the question — and every answer below is the real product, from live runs on a real matter, recast to the showcase case.
01 · Asked
Statute, caselaw, and your own docket — one answer.
Ask for the standard on compelling further RFP responses and Lex returns the governing sections with a citation link on every claim, Kirkland for good cause — then applies it to the served Set Two and confirms against the minute order already on the matter. Research platforms know the law; chatbots guess; this answer does what neither can.
Maya, California law permits further responses when an RFP response contains an incomplete compliance statement, an inadequate inability-to-comply representation, or an objection that is meritless or too general. The moving party must show request-specific good cause, meet and confer, and ordinarily give notice within 45 days. (Code Civ. Proc., § 2031.310(a)–(c).) citation:CCP § 2031.310
⚖ Governing standard
A compliant response must address each RFP separately — compliance, inability to comply, or objection. (§ 2031.210.) citation:CCP § 2031.210 An objection must identify with particularity the documents covered and state its specific ground. (§ 2031.240(a)–(c).) citation:CCP § 2031.240
The motion must make a fact-specific showing of relevance and good cause. (Kirkland v. Superior Court (2002) 95 Cal.App.4th 92, 98.) citation:Official court discussion of Kirkland standard
📌 Application to Northstar’s Set Two objections
Northstar’s January 12 responses were objections-only, asserted globally rather than request by request… The court’s June 15 minute order confirms the analysis: code-compliant supplemental verified responses ordered for RFP Nos. 1–9, 12, 15, and 16, with a legally compliant privilege log.
Ask Lex to research, review, draft, or explain… (type / for commands)
02 · Worked
It shows its work, and works your record first.
A request-by-request assessment with verdicts per definition, closed by the evidence basis: what it reviewed, what it searched — 100 matter documents for the exact phrase — and which citations it verified against the approved corpus. Then the forensic register: a service date answered from an email span with the message ID, sources expanded to the underlying documents.
🔍 Application to the served Set Two definitions
| Definition | Assessment | Likely result |
|---|---|---|
| DOCUMENT | Tracks the statutory concepts of writings and ESI. | Generally defensible. Breadth alone doesn't make the RFPs overbroad. |
| COMMUNICATION | Includes oral exchanges, though an RFP compels only existing documents. | Partially vulnerable. Construe as recorded communications; production still owed. |
| YOU/YOUR | Includes the party and agents acting on its behalf. | Partially vulnerable. Bounded by possession, custody, control, and privilege. |
Evidence basis: reviewed the served Set Two RFPs and the separate draft, searched 100 current matter documents for the exact phrase “overbroad definitions” (90 had searchable text; no exact match), and verified the five California case citations against the approved legal corpus; DMS review current August 15, 2026.
The case citations were confirmed against the approved legal corpus; exact quotations and pin cites should be checked against the published opinions before filing.
Maya, opposing counsel received RFP Set Two on December 9, 2025. The service email — “SERVICE OF PLAINTIFF’S RFP, SET TWO” — was addressed to d.ostrander@ostranderllp.com and transmitted at 8:15 p.m. Pacific. Email message ID: 7c2e41ab-90d5-4f1c-b8e2-1a6f30c47d19
Opposing counsel later corroborated receipt in his own January 12 service email, reproduced in the IDC statement.
DMS Project Evidence Packet
“…22 7. OBJECTIONS: This request seeks to improperly invade the attorney-client communication and attorney work product…”
DMS Project Evidence Packet
“ELECTRONIC SERVICE OF PLAINTIFF’S WRITTEN DISCOVERY REQUESTS — From Daniel Ostrander · Mon 1/12/2026 8:24 PM · 1 attachment (4 MB)…”
03 · Hunted
The open web, on a leash — and honest about the leash.
Lex resolves the department and judge from the matter's own metadata, then reads that department's current posted policy from the court's official site. When an internal resolver is unavailable, the answer says so and states exactly what the conclusion rests on. Tools can fail; the evidence trail doesn't.
Maya, for Department 24, the current court-posted procedure requires party agreement and a reservation before any IDC brief is submitted.
⚖ Required sequence
- All parties must agree to participate. Dept. 24 conducts an IDC only with every party’s agreement.
- Reserve through the Calendar Clerk: (510) 555-0147. IDCs are heard Mondays and Wednesdays at 8:30 a.m.
- Two court days before the IDC, each party submits a brief — five pages maximum — to the department and opposing counsel. citation:Department 24 Policies and Procedures
Nothing is identified as an upfront court filing before reserving the IDC. The optional post-IDC stipulation form is not the entry ticket. citation:Superior Court local form
Evidence basis: checked August 15, 2026 against the court’s current Department Policies page and its linked Dept. 24 policy; the internal Court Rules resolver was unavailable for this turn, so this conclusion rests on the court’s official website. The matter’s DMS returned no readable documents relevant to this procedural question.
Sources
- Department 24 Policies and Procedures — current court-linked policy for Hon. A. Oyelaran’s department.
- Superior Court Department Policies page — official page presently linking the Dept. 24 policy.
04 · Gated
The claim it refuses to make.
Ask for a final deadline with no verified hearing date on the record and Lex gives the governed calculation, states the conditional boundary — and blocks the final claim, visibly. A claim with no supporting evidence is blocked and shown as blocked, never padded over. Citation checking beyond this gate is EdgeCite's job.
How citations get verified →Maya, I can give you the governed calculation — but not a final date, because no hearing date for this motion is verified on the record yet.
What I can state
Opposition papers are due nine court days before the hearing (Code Civ. Proc., § 1005(b)). citation:CCP § 1005(b) If the hearing is set for October 6, the opposition deadline computes to September 23 — conditional on that setting.
Final opposition deadline — no verified hearing date exists in the matter record or the Register of Actions. I won’t state a final date I can’t ground. Confirm the hearing setting and I’ll finalize the calculation with full lineage.
05 · Delivered
Findings become work product, not a transcript.
The memo lands in the DMS as a normal version with AI provenance, proposed tasks and deadlines land in Triage, and every write waits at an approval gate. Found law becomes evidence on the record — and the record lives in the Project. Research ends where the case is organized.
Where the record lives →🗓 This Month (2 versions) · Group by Date
Verified deliverable from legal graph msa_obligation_register.v1 — every obligation traced to its clause span.
👤 Maya Chen (Attorney) · 301 words · 10 KB
Initial version.
👤 Maya Chen (Attorney) · 294 words · 10 KB
06 · Standing
Research that runs when the event fires.
Pair it with a delegation: whenever opposing counsel files anything, verify every authority they cite and brief me on the ones that matter. A locked work contract, budgets, and a kill switch — research on the docket's schedule, not your memory's.
The full Delegations story →The locked agreement it works under. Nothing here can drift — every change creates a new version you can review.
Its job
Summarize each newly linked Matter document in exactly 5 bullets.
Your instruction
“Change the summary to five bullets”
WHEN IT RUNS
Runs automatically whenever a new document is added to this Matter.
WHERE IT WORKS
Works inside one Matter only. It cannot see or touch anything outside it. Its Matter: Hale v. Northstar Logistics — breach of contract.
WHAT IT MAY DO
Read-only. It can read and summarize, but can never change documents, Tasks, deadlines, calendar entries, or billing records. If it ever proposed a change, your approval would be required first.
TOOLS IT MAY USE
Allowed to use 2 tools, nothing else: Look up document details · Read document text.
HOW RESULTS REACH YOU
Results arrive in your Messages. Each result links back to its source documents. You are alerted if a delivery ever fails.
ITS LIMITS
Up to 50 runs a day and 1,000 a month. Each run stops itself after 10 minutes or 8 working steps. Spending is capped at $5 per run, $50 a day, $1,000 a month.
The AI running it
Firm model · governed
This exact model is locked into the current version and re-checked against firm policy before every run.
Who pays for its AI time
Billed to the Matter each run works on
Spent so far: $0.00 across 33 runs.
The difference
Research that ends on the record.
Research tools stop at an answer. Lex Research stops when the answer is evidence: every claim typed to a document span, an email span, a verified citation, or a rule authority; every found source saved to the matter; every deliverable a governed artifact in the record. Projects holds the case — Research is how new authority earns its way in.
The case brain it feeds →Claim-typed
Document spans, email spans, verified citations, rule authorities — per claim, or blocked.
Ledger-verified
A 15-million-citation authority ledger inside your deployment; live verification for the fresh and contested.
On the record
Memos to the DMS, tasks to Triage, sources to the matter — approval-gated, every time.
Capabilities
What it does
Agentic research, not one-shot retrieval
Lex plans the research like an associate would: it breaks the question down, decides which sources it needs, queries across your matters, documents, email, transcripts, deadlines, and billing, evaluates whether it has enough, and digs deeper where it doesn't — then synthesizes one answer with claim-level citations.
Caselaw with the receipts
A national citation authority ledger — built from the Free Law Project's CourtListener corpus, essentially every published US caselaw citation — lives inside your deployment, so citations verify locally with zero data egress. Fresh or contested cites verify live against CourtListener, and Lex pulls the actual opinion text on demand.
Statutes, regulations, and court rules from primary sources
Statute lookup, regulatory research, and court-rule questions answer from governmental and primary legal sources — and deadline math comes from Cascade with the rule authority attached to every date, not from a model's recollection.
The open web, on a leash
Lex's research agent can search the open web — but its searches are biased to authoritative legal sources, and everything it retrieves is saved to the matter as a sourced artifact. Found law becomes evidence on the record, not a browser tab that vanishes.
Evidence-gated, not just cited
Every claim in the answer carries typed evidence — a document span, an email span, a verified citation, a rule authority, a ledger entry. A claim that can't be grounded is blocked and shown as blocked, never padded over. Other tools cite; EdgeLex enforces.
Cite-checked before it reaches a filing
EdgeCite validates every citation deterministically against the authority ledger before any AI judgment runs, escalates unknowns to live verification, routes judgment calls to human review, and maintains a citation graph of how your documents rely on which cases — holding, dicta, or criticism.
Research becomes work product
Findings don't die in a chat transcript. The memo saves to the matter in the DMS, proposed tasks and deadlines land in Triage, and the result delivers to EdgeMessage — every write approval-gated.
Standing research
Pair it with Lex Delegations: "whenever opposing counsel files anything, verify every authority they cite and brief me on the ones that matter." Research that runs when the event fires — not when you remember to ask.
Your model does the reasoning
Research runs on the models your firm chooses — frontier, local open-source, or your own model tuned in the Lex Training Center — and the router keeps underpowered models away from work they can't carry.
In your control
Research runs under the same governance as everything else: evidence requirements set before the model runs, deterministic citation validation before AI resolution, sources stored as auditable artifacts, and a complete trail from question to claim to authority.
Related
Works with
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.
EdgeCite
Citation governance: extract, validate, and verify citations against your case library before they ever reach a filing.
Cascade
Deadlines computed from the actual rules, chained to the facts that triggered them, and recalculated with full lineage when the case moves.
Lex Delegations
Standing delegations you create in plain language. Lex watches the matter, wakes when your firm's events fire, does the work inside your approval gates — and every run lands on the task ledger like any other member of the team.
See EdgeLex on your own terms.
We'll walk through self-hosting, model control, and your firm's workflows.