EdgeLex
The Legal Operating System.
Everything your firm runs on — matters, documents, email, meetings, research, citations, playbooks, deadlines, money — with AI that answers for its work.
Notice of Entry of Order — with Exhibit
👤 Client: Harborview HOA🗂 Hale v. Northstar Logistics📁 Orders, Judgments, and Appeals
Entered · Aug 14 · + Add deadline
Aug 15, 3:41 AMCreated Aug 14
👁⬇✦⚖🗑Whitfield Deposition — Session Recording, Vol. 1
📁 Depositions
Aug 14, 9:04 AMCreated Aug 14
👁⬇✦⚖🗑Order Denying Motion to Compel (3) ✎
👤 Client: Harborview HOA🗂 Hale v. Northstar Logistics⚖ Cite-check: verified with warnings · 5 to review
Filed · Aug 14 · + Add deadline
Aug 13, 9:31 PMCreated Aug 13
👁⬇✦⚖🗑Meet-and-Confer Letter — Supplemental Discovery
👤 Client: Harborview HOA🗂 Hale v. Northstar Logistics📁 Correspondence and Evidence
Aug 13, 8:02 PMCreated Aug 13
👁⬇✦⚖🗑POS-030 — Proof of Service, Motion to Compel
👤 Client: Harborview HOA🗂 Hale v. Northstar Logistics📁 Service and Notice
Aug 13, 8:00 AMCreated Aug 13
👁⬇✦⚖🗑✦ Second chair · live · attorneys only
Follow-up: confront the custody denial with RFP No. 12He just said he “can’t recall” who kept the logs — the verified discovery response in your deposition plan admits his department’s custody. [00:02:04–00:02:12]
TRANSCRIPTCHATEXHIBITS
Maya Chen [00:01:47]
And the December 9 delivery — whose department received it?
R. Whitfield [00:01:55]
I'm not absolutely sure.
Maya Chen [00:02:00]
Who was responsible for keeping the delivery logs?
R. Whitfield [00:02:04]
I really can't remember who was responsible for keeping those logs.
14 segments · updates every 15s · highlight lines with your mouse to cut a video clip
August 14, 2026
Via Email · Counsel of record, Northstar Logistics, Inc.
Re: Meet and Confer — Plaintiff’s Supplemental Written Discovery Responses
Hale v. Northstar Logistics · Case No. 26CV004182 · Superior Court of California, County of Alameda
Dear Counsel:
This letter is intended to meet and confer regarding Plaintiff’s supplemental written discovery responses and related production obligations.
On July 21, 2026, the Court granted Plaintiff’s request for a partial extension and ordered that responses be served by the close of business on August 14, 2026. The order followed the parties’ June 15, 2026 Informal Discovery Conference.
1. Incomplete or evasive responses. Plaintiff’s prior responses contain broad objections — including vagueness, burden, and privilege — without identifying the documents that will be produced or the factual basis for withholding.
📁 Civil — Hale v. Northstar
Project chats use the instructions, files, and saved AI work attached here.
Living project work products
📇 Matter Source Inventory CURRENT
Built Aug 14 · 419 sources
✓ deterministic build · build receipt recorded
✓ 419 source fingerprints verified
🧮 Discovery Matrix FRESH
Built Aug 14 · 19 sources
✓ deterministic build · build receipt recorded
✓ 19 current source fingerprints verified
🗺 Matter Evidence Map SCOPE NEEDED
Tests lawyer-defined propositions against the exact current Source Inventory.
Current inventory ready · lawyer proposition required
🕰 Case Chronology NOT BUILT
What happened at each stage: filings, responses, hearing outcomes, next expected hearings.
⚠ Issue Register NOT BUILT
Issues, evidence, adverse facts, missing proof, risk, and next action.
＋ Describe any work product GOVERNED
Create a governed living Project artifact from a sentence.
🤖 Agent Control Center
Standing Delegations, committed work, runtime health, and governed delivery.
Matter Watch — Hale v. Northstar ✎
💬 Discuss with Lex📄 Process a document…⏸ Disable✎ New version🗑 RetireHealthyEnabled
Summarize each newly linked Matter document in exactly 5 bullets.
Definition v3 · 24 linked Tasks · Updated 8/13/2026, 10:24 PM
ACTIVE TASKS
4
IN REVIEW
20
COMPLETED
0
DELIVERY FAILURES
0
Asks before anything goes out · Shows its sources · Runs in our cloud or on your own servers.
Every part of the practice. One AI moving through it.
One instruction can cross all of it — a new court order becomes a summary, a calculated deadline, a calendar entry, a task, and a message to the team. Nothing re-keyed, nothing sent without your OK. Want to see? Ask Lex — live in the corner of every page.
One matter, every workstream
The matter is the center of gravity.
Documents, messages, meetings, deadlines, billing, email, tasks, and the Data Room — one workspace your team and your AI both understand.
The matter
Hale v. Northstar Logistics
Civil litigation · active · every workstream in one workspace
Documents
23 documents · Motion to Compel v4
Messages
3 threads · 2 unread
Meetings
Whitfield deposition · transcript aligned
Deadlines
Opposition due Sep 4 · traced to rule
Billing
41.5 unbilled hours · trust reconciled
Data Room
Mediation room · 3 released versions
Matter-linked · privilege-marked
Tasks
6 open · 2 rule-generated
The category
Everything they do. One operating system.
AI legal work, a collaborative AI workspace, and practice management have been three separate purchases. EdgeLex is the operating system that is all three — deployed in our cloud, your private cloud, or on your own servers.
| Capability | AI legal tools | AI workspaces | Practice mgmt | EdgeLex |
|---|---|---|---|---|
| AI legal work — research, drafting, review | Yes | Yes | — | Yes |
| Collaborative AI workspace across the firm | — | Yes | — | Yes |
| Matters, billing, calendar, intake | — | — | Yes | Yes |
| Email, meetings, e-signature, data rooms | — | — | — | Yes |
| Standing AI delegations with approval gates | — | — | — | Yes |
| One system — your cloud or ours | — | — | — | The category |
$ edgelex deploy --self-hosted
✓ 14 services healthy · postgres · vector store · document engine
✓ models: local llama-70b + frontier via your keys — governed per matter
# your metal, your data, your models. our OS.
Real for engineers, not just brochures.
Self-host the entire platform, run local models on your own hardware, bring frontier models under your own keys — with per-matter governance, typed evidence behind every claim, and an audit trail your IT counsel can actually read.
Where the work happens
Lex speaks first — from the record.
Open EdgeLex in the morning and the practice answers back: what’s overdue, what needs you, what the courts filed overnight. Every turn routes with a slash; every answer carries its receipts.
Good morning, Maya — you have 8 overdue tasks.
/task/deadline/emailType / in the message box to route a turn — filing, deadline, draft, email, billing, and more.
Ask Lex to research, review, draft, or explain… (type / for commands)
Lex Projects
The case brain.
One governed context per case — documents, email, notes, billing, and saved AI work — with living work products that carry build receipts and verified source fingerprints. Context engineering as a feature.
The record, at hand
Highlight anything. It becomes work.
Any DMS document renders beside the conversation and becomes governed context for the selected matter — exact version pinned. Select a passage and a menu appears: ask about it, save it to the matter, turn it into a fact note, chronology entry, depo question, or draft — or check it against rule authority and dates.
See it in the Lex story →SUPERIOR COURT OF CALIFORNIA
COUNTY OF ALAMEDA
TENTATIVE RULING
HEARING DATE: 8/14/2026 · JUDICIAL OFFICER: HON. A. OYELARAN
CASE NO.: 26CV004182 · CASE TITLE: Hale v. Northstar Logistics
Defendants’ motion to dismiss is DENIED.
A. The complaint pleads each element of breach with the specificity Code Civ. Proc. § 430.10(e) requires; the agreement, the performance rendered, and the July 7 cessation of work are alleged with dates and amounts.
B. The first amended complaint was filed without leave of court. See Code Civ. Proc. § 472(a). The court declines to strike the FAC to avoid further delay, and directs plaintiff to follow all applicable rules going forward.
C. Like attorneys, self-represented litigants must check every citation to ensure that the cited authority exists and supports the proposition for which it is cited.
Tentative Ruling — Hale v. Northstar… Esc
⚡ Ask & use
📌 Save to the Matter
🗂 Turn into work product
⚖ Check against authority
Lex moves with the work
One court order. Six systems. Zero re-keying.
Lex isn't a chatbot in a separate tab — it's the intelligence layer that follows the work across the firm. Here's one real workflow, end to end.
A court order arrives
“Order Granting Continuance — Hale v. Northstar” lands in the matter's inbox.
Lex reads it as evidence
The new hearing date is identified from the order's own words — a source-backed event, not a guess.
Deadlines recalculate
The dependent chain — opposition, reply, hearing — recalculates from the rules, with full lineage.
You approve
The proposed calendar entries and tasks wait for a human. One tap says yes.
The team knows
The matter team is alerted in Messages, with the order and new dates linked.
The record keeps everything
Evidence, computation trace, approval, and actions — attached to the matter, auditable forever.
Every step is source-backed, approval-gated where it acts, and written to the matter's audit trail.
The platform
Everything a firm runs on, in five layers.
AI & Intelligence
Lex and the governed engines that reason over your firm's work.
Legal Work
Matters, tasks, intake, and billing — the practice's system of record.
Documents & Collaboration
Draft, message, meet, share, and sign — together, in matter context.
Work Everywhere
Browser, mobile, desktop, and Microsoft Word — one platform.
Firm Control
Deployment, security, and a platform shaped around your firm.
Agentic AI · Lex Delegations
Chatbots answer questions. Delegations do the work — and answer for it.
Tell Lex once, in plain language — “whenever a document is linked to this matter, summarize it and message me” — and it becomes a standing delegation: versioned, bounded, and awake long after you close the tab.
- Wakes on the firm's own events — a document lands, an email arrives, a deadline approaches
- Every run is a real task assigned to Lex — trackable and reportable like an associate's work
- Immutable versioned instructions, approval gates on consequential steps, budgets, and a kill switch
🤖 Agent Control Center
Standing Delegations, committed work, runtime health, and governed delivery.
Matter Watch — Hale v. Northstar ✎
💬 Discuss with Lex📄 Process a document…⏸ Disable✎ New version🗑 RetireHealthyEnabled
Summarize each newly linked Matter document in exactly 5 bullets.
Definition v3 · 24 linked Tasks · Updated 8/13/2026, 10:24 PM
ACTIVE TASKS
4
IN REVIEW
20
COMPLETED
0
DELIVERY FAILURES
0
One run, end to end: the event fires, a task lands on the matter ledger, the work happens inside the allowlist, the run pauses for approval, and the deliverable arrives in EdgeMessage.
EdgeMessage · Included with EdgeLex
Messaging that knows what a matter is.
Secure legal messaging organized around matters, people, and documents — not generic workplace chat. One universal inbox across every EdgeLex surface, with Lex as an @mentionable teammate.
- Direct messages, team threads, and conversations attached to specific document versions
- Ask Lex and Message people are structurally separate — a DM can never route to the AI
- On mobile with push — content-free lock-screen previews, deep link into the thread
Messages🔍 ＋
EdgeLex Connect · internal firm conversations
✦Lex
🎥 Meeting started — Join: https://…
TOTunde Okafor
Filed the opposition — see the doc thread
DRDana Reyes
Thanks — see you Tuesday
⚖ Hale v. Northstar — Alameda
MATTER CHANNEL · PRIVILEGED
📄 Northstar Opposition to Ex Parte…
Document conversation
📄 Draft Modification Request
Document conversation
📄 Platform Services Agreement
Document conversation
📄 Verified Matter Assessment — 2026-08…
Document conversation
LexMaya Chen, Lex✦ Catch up🎥 Meet now
Lex Aug 13, 9:45 PM
Matter Watch — standing delegation– Tentative ruling issued August 14, 2026, in Hale v. Northstar Logistics, Alameda County Superior Court, Case No. 26CV004182.
– The court denied Northstar’s motion to strike.
Hale v. Northstar — 26-JH-Civil Law-002Tentative Ruling (3)Review TaskRun detail
Completed Aug 13, 9:45 PM
Lex Aug 14, 1:47 PM
Notice of Ruling with Exhibit was just filed into Hale v. Northstar. Based on what it is, I can produce:
– Exhibit Compliance Report — your exhibit list checked against the pretrial order and the court rules. Checked against the real court-rules corpus, not a prompt.
Say the word and I will start — nothing runs until you ask.
Live now · recorded with transcript
JoinNotify: @Maya Chen @Lex
Write a message…➤ Send
Internal EdgeLex message. Try “@Lex help” to see what Lex can do here.
EdgeMeet · Included with EdgeLex
Meetings and depositions, on your infrastructure.
Self-hosted video with a legal brain: live transcripts, an AI second chair that cites its insights, off-the-record control that actually drops the record, and exhibits shared in the room.
- The second chair surfaces contradictions, admissions, and follow-ups — attorneys only, every insight cited
- Certified transcript alignment upgrades citations to page:line; designations become hash-verified clips
- Guests join by consent-gated link, structurally walled off from insights and case context
✦ Second chair · live · attorneys only
Follow-up: confront the custody denial with RFP No. 12He just said he “can’t recall” who kept the logs — the verified discovery response in your deposition plan admits his department’s custody. [00:02:04–00:02:12]
TRANSCRIPTCHATEXHIBITS
Maya Chen [00:01:47]
And the December 9 delivery — whose department received it?
R. Whitfield [00:01:55]
I'm not absolutely sure.
Maya Chen [00:02:00]
Who was responsible for keeping the delivery logs?
R. Whitfield [00:02:04]
I really can't remember who was responsible for keeping those logs.
14 segments · updates every 15s · highlight lines with your mouse to cut a video clip
Cascade · Included with EdgeLex
Deadlines that survive contact with reality.
A source-backed deadline engine that calculates, connects, and recalculates court obligations. When the hearing moves, the chain moves — with lineage, not guesswork.
- Court-day math with a per-step trace and the rule authority behind every date
- Continuances, extensions, closures, and non-compliance recalculate the dependent chain
- Overrides are preserved, AI-extracted dates go to review, and missing data blocks instead of guessing
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
Data Rooms · Available in every matter
Share the file. Keep the control.
A secure Data Room inside every matter: version-locked documents, verified external participants, per-room policy, and an activity ledger you can produce.
- Documents are shared as explicit locked versions — never a live 'latest' pointer
- Watermarking, download denial, IP restriction, link expiry, revoke-on-demand
- Every view and download lands in an immutable, exportable room ledger
Room name
Hale v. Northstar — Discove…Template
Discovery ▾+ Createclosed
Created 7/13/2026, 8:22 AM
Closed0 of 0 versions are searchable. No OCR release blockers.
Ready
0Failed
0Pending
0Sensitive review
0Score 75/100. Resolve blockers before external release.
Docs
0Open Q&A
0Review
0OCR blockers
0Policy warnings
1⚠ Room documents — No documents are assigned to this room.
✓ Search and OCR readiness — All assigned versions satisfy the room OCR policy.
✓ Release review — No open review blockers.
Real-Time Collaboration · Built into EdgeLex
Two lawyers, one document, zero collisions.
Live coauthoring in EdgeDocs with presence, cursors, and comments — while Microsoft Word stays a first-class surface over the same version chain, and the document's conversation travels with it in EdgeMessage.
- EdgeDocs in the browser and native Word are co-equal surfaces on one DMS record
- Margin comments bridge into the document's message thread with provenance
- The Lex Document Expert works inside the session — and only edits with your approval
Chat✕
Maya Chen
Tunde Okafor
MCMaya Chen
Tightening the intro — watch ¶1.
TOTunde Okafor
Good — I'll take the timeline section.
MCMaya Chen
Use the June 15 order language from the minute order, not our letter.
TOTunde Okafor
Pulled it in. Also flagged their three proposed end dates — they don't even agree with themselves.
MCMaya Chen
That's the closer. Put it last.
Enter your message here
Send
SUPERIOR COURT OF THE STATE OF CALIFORNIA
COUNTY OF ALAMEDA
DEPARTMENT 24
JORDAN HALE,
Plaintiff and Cross-Defendant,
v.
NORTHSTAR LOGISTICS, INC., et al.,
Defendants.
Case No. 26CV004182
Hon. A. Oyelaran, Judge
Hearing: October 6, 2026, 8:30 a.m.
Department 24
PLAINTIFF’S OPPOSITION TO DEFENDANT’S EX PARTE APPLICATION FOR EXTENSION OF TIME TO SERVE SUPPLEMENTAL WRITTEN DISCOVERY RESPONSES
Plaintiff Jordan Hale opposes Northstar’s Ex Parte Application for an extension of time to serve supplemental written discovery responses. The application should be denied because the requested extension rests principally on counsel’s admitted failure to account for his own July travel when the existing deadline was set — after the Court had already granted the additional time counsel requested at the June 15 conference. The resulting delay should not be shifted to Plaintiff.
I. RELEVANT BACKGROUND AND TIMELINE
1. On June 15, 2026, the parties appeared for an Informal Discovery Conference concerning Northstar’s supplemental written discovery responses. The resulting direction established a compliance deadline; the dispute had already been pending for months.
2. The Court initially discussed approximately 30 days for compliance. Counsel requested 45 days, citing commitments then said to be on calendar. The Court granted the additional time — the present September 23 deadline therefore already reflects an accommodation.
3. Counsel now relies on his failure to account for July travel when that period was discussed. The application’s related papers do not identify a single consistent proposed end date — they refer variously to October 28, 29, and 31.
TOTunde Okafor 8/15, 5:42 PM
Lead with the June 15 order instead — stronger opener?
AddCancel
Clause Benchmark · Included with EdgeLex
“Is this market?” Answer from your own deals.
Benchmark every clause against what your firm has actually negotiated and signed — source-grounded observations, lawyer-approved standards, and cohorts limited to comparable agreements. Not a vendor's market data.
- Every position cites a verified span of the actual document text — unverifiable extractions are flagged, not trusted
- Standards and outliers vs. your negotiation history, filtered by contract type, governing law, and your side of the paper
- Machine extractions never silently become firm standards — approval is one audited click, and benchmarking fails closed until review completes
“Project facts of record: the Riverbend Commerce Center site improvements dis…”418 chars · Esc
City Stormwater Permit — Narrative Requirements Excerpt
The application narrative must address: A. a description of the site and proposed improvements, including total disturbed area; B. the measures preventing sediment discharge during construction; C. the permanent stormwater controls proposed; D. the party responsible for maintenance after completion.
Project facts of record: the Riverbend Commerce Center site improvements disturb approximately 18,500 square feet for parking-field regrading and a new bioretention area; silt fencing and inlet protection are specified during construction; Riverbend Commerce Center LLC holds fee title and will maintain permanent controls under its property-management program.
Lex Training Center · Included with EdgeLex
Frontier, local — or your firm's own model.
Model choice shouldn't stop at picking a cloud. EdgeLex runs frontier models with your keys, local open-source models on your hardware — and lets your firm fine-tune its own model on its own curated work product, in its own infrastructure.
- Feedback from real work is signal-only — nothing auto-trains; datasets grow from lawyer-approved examples with full lineage
- Legal-safety and privacy review gate every record; eval holdouts keep the measurement honest
- The dataset and the weights never leave your deployment — and the firm model serves under the same default-deny governance
🎓 Lex Training Center
Manage feedback, training examples, and track Lex quality.
Total Feedback
8
Thumbs Up
3
Thumbs Down
5
With Corrections
5
Legacy feedback remains review evidence. Dataset growth must use selected manual examples or selected traces.
draftLineage
firm_model_v2Records
0Created
6/30/2026
✅ All clear — no examples need review.
Lex Research · Included with EdgeLex
Research with the receipts.
Lex researches like an associate — plans the question, works your matters and documents, verifies caselaw against a national citation ledger inside your own deployment, and returns a cited memo where every claim carries its evidence or gets blocked.
- Essentially every published US caselaw citation verifies locally, with live CourtListener verification and opinion text on demand
- Claim-level evidence is enforced, not decorative — an ungrounded claim is blocked and shown as blocked
- Findings become work product: the memo files to the matter, tasks land in Triage, and delegations keep the research standing
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 AI Governance layer
Your firm is the authority. The AI works under policy.
Governance isn't a disclaimer here — it's architecture. The task is classified before the model runs, tools are bound per turn, claims are verified against typed evidence, and actions wait for approval.
AI Model Governance
Control which AI models the Lex Runtime can use, set defaults, and monitor usage.
🛡 Runtime Governance Active authority
The Lex Runtime checks firm policy in the database before any model call. Browser clients cannot override this policy.
Work everywhere
Browser, phone, desktop, and Word — one platform.
The same matters, the same governance, the same audit trail — on every surface the work happens.
☰✦ Firm default · pinned ▾
Good morning, Maya.
Scoped to your matters · every answer cited
Ask Lex anything…
Lex · just now
The opposition draft is ready for review — filed to Hale v. Northstar, version 4.
Voice-first Lex — under firm policy.
Messages🔍 ＋
✦Lex
Matter Watch: tentative ruling — motion to strike denied
TOTunde Okafor
Exhibit set locked — see the doc thread
⚖ Hale v. Northstar — Alameda
MATTER CHANNEL · PRIVILEGED
📄 Opposition to Ex Parte — v4
Document conversation
Lex💬
Messages🗂
Matters🔔
Activity2⋯
More
The matter channel in your pocket.
Lex
Matters
Documents
Messages
EdgeMail
Calendar
Meet
Tasks
Billing
↻ Relaunch with update
Motion to Compel Further Responses.docxInstalled app
Version history
Sign-in runs in the system browser; tokens live in OS-encrypted storage. One binary, governed Word round-trip, signed updates.
The installed workspace — governed Word round-trip, signed updates.
EdgeLex Private Edition
Buy the foundation. Shape the last mile.
Dedicated or on-premises deployment, firm-specific workflows and applications, and governed source-level customization — your firm's operating model, built on a legal platform that already exists.
Why we built EdgeLex
"I'm a practicing attorney and a developer. I wanted the leverage modern AI offers without handing a vendor my clients' privileged data or trusting a model I couldn't see. EdgeLex is the platform I wanted to exist: as capable as the cloud tools, but the firm keeps control."
David · Founder, EdgeLex
Resources
For firms that research before they buy.
Standing delegations: how to hand work to an AI the way you hand work to an associate
One plain-language sentence becomes a standing instruction that wakes on your firm's events, does the work, and answers for it — on the same task list as everyone else.
8 min readGuidesThe law firm buyer's guide to legal AI
Eight questions a managing partner can put to any legal AI vendor — on data, models, grounding, action, work product, cost, and audit — and how EdgeLex answers each one.
9 min readAgents & accountabilityAgents vs. chatbots: what lawyers should know
"Agent" now means everything and nothing. A working taxonomy — chatbot, assistant with tools, standing agent — and the accountability questions that matter at each level.
8 min readSee EdgeLex on your own terms.
We'll walk through self-hosting, model control, and your firm's workflows.