AI & Intelligence · Projects + Drafting
One case, fully organized for AI — and a work product engine that turns the record into Review Tables, Discovery Matrices, chronologies and formal drafts, every cell traceable to its exact source.
Included with EdgeLex
📁 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.
The problem
AI is only as good as the context it holds — and most tools make the lawyer rebuild that context in every conversation, with no way to know whether yesterday's analysis still matches today's record.
One case, engineered for AI · the work product engine
Created. Organized. Chosen. Reviewed. Matrixed. Preflighted. Delivered.
Follow one Project from a memory policy through a Review Table and a Discovery Matrix to a deliverable in the record — every screen below is the real product, with the numbers from real runs.
01 · Created
A Project starts with a memory policy.
Bind a Project to a matter and its folders mirror the matter's own taxonomy. Then decide — with checkboxes, not defaults — what Lex may remember and must confirm: matter memory, document memory, related-matter context, personalization.
Use projects to organize files, chats, instructions, and memory policy for ongoing work.
When a matter is selected, project file folders mirror that matter’s Documents tab.
Memory policy
☑ Use global personalization
☑ Use active matter memory
☑ Use selected document memory
☐ Allow related matter context
☑ Confirm matter facts
☑ Confirm case events
02 · Organized & built
The case brain, with receipts.
Instructions, files, and saved AI work in one governed context — and living work products that prove their own state: FRESH with a recorded build receipt and every source fingerprint verified, SCOPE NEEDED when a lawyer proposition is missing, NOT BUILT when nothing pretends otherwise. Describe any work product in a sentence and it becomes a governed living artifact.
How new authority arrives →📁 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.
03 · Chosen
Describe the work product, or pick one the firm already trusts.
Review Table, Discovery Matrix, Case Status Summary, Matter Source Inventory, Matter Evidence Map, Issue Register, Case Chronology, or a custom work product in a sentence — and the formal drafts: brief or motion, a single cited section, an amendment in your precedent's conventions. Each one starts from the exact approved Project sources, never from a blank prompt.
What should Lex produce?
Practice area · General / Other ▾Custom Work Product
A custom source-grounded legal work product defined by the lawyer.
Review Table
Apply typed, evidence-grounded columns across the exact approved Project sources, review each finding, and publish an immutable snapshot.
Case Status Summary
Current operational status, issue-bound evidence, governed case events, gaps, and next actions.
Matter Source Inventory
Audits current Project DMS documents and Matter-linked emails without deciding what they prove.
Matter Evidence Map
Tests lawyer-defined propositions against one exact current Matter Source Inventory.
Issue Register
Issues, evidence, adverse facts, missing proof, risk, and next action.
Case Chronology
Dated event timeline with source support and missing-date flags.
Discovery Matrix
Every request paired to its response and objection, production checks, meet-and-confer, zero model calls.
Formal document drafts
Brief / Motion Draft · facts pinpointed to your record, law standing only on verified authority · Section Draft · one cited section supporting one proposition · Amendment Draft · exactly your stated changes, in your precedent’s conventions
04 · Reviewed
A Review Table: typed columns, every cell with its receipt.
Choose a governed template and freeze the sources. EdgeLex fills the table across all of them: this run, 31 sources and 10 columns, 310 cells analyzed, 273 evidence passages, 54 verified empty results, one source limitation disclosed in the snapshot rather than hidden. Click any cell and the cited source opens at the page. The review assistant answers only from this run. Publish, and the snapshot is immutable.
Ready to publish with source limitations
1 source limitation affects 1 result. It will be disclosed in the published snapshot; no individual approval is required.
31 documents with results · 24 relevance results · 31 party results · 30 date results · 273 evidence passages · 275 policy-cleared cells · 54 verified empty results
completed2026-05-05T23:03
completedDefendants' Request for Production…
source verified
completed2026-05-05T23:03
completedDefendants' Requests for Admissions…
source verified
completed2026-06-11T11:57
completedPLAINTIFF'S RESPONSE…
source verified
completed2026-05-05T23:08
completedDEFENDANT'S VERIFIED…
source verified
completed2026-08-19T16:30
completedProof of Service by First…
source verified
completed2026-05-05T23:02
completedDefendant Dwayne Dav…
source verified
completed2026-08-19T15:45
completedA June 15, 2026 minute…
source verified
Cited source
Exhibit H · EdgeDocs · v1.0
Review Table source · Page 1 of 7
SUPERIOR COURT OF THE STATE OF CALIFORNIA
COUNTY OF SAN DIEGO
LINDSAY ABERNATHY, Plaintiff · Case No. 24CU027820N
DEFENDANTS’ REQUESTS FOR ADMISSIONS, SET FOUR
Exact evidence · read deterministically from the frozen source · Mark for follow-up
05 · Matrixed
A Discovery Matrix, with zero model calls.
Every request paired to its response and objection across the matter's discovery: 361 items from 21 sources, 117 unmatched requests and 126 unmatched responses surfaced as exceptions instead of guesses, 90 objection-only items queued for a lawyer, 245 production checks. Each item shows its exact evidence anchor down to the line. The lawyer confirms or corrects the pairing, adds the next action or a meet-and-confer entry, and the decision joins the audit history. Freeze a draft, publish a release, export XLSX, PDF, CSV or HTML.
Deadlines the matrix feeds →Run and release
Status
completed with exceptions
Sources 21 · Items 361
Exceptions 328 · Open follow-ups 0
4 added · 293 changed · 41 removed
Draft XLSX · PDF · CSV · HTML
Discovery command center · whole-matrix counts · 361 total items
0
Missing responses
117
Unmatched requests
126
Unmatched responses
90
Objection-only review
245
Production checks
0
Open actions
0
Meet-and-confer
Item and exact source
Defendants_Request_SET_TWO_Interrogatories · EdgeDocs v1.0 · page 2 of 5
31 SPECIAL INTERROGATORIES, SET TWO
32 SPECIAL INTERROGATORY NO. 1:
33 If your response to Defendant’s Request for Admission No. 15 (First Set, served May 17, 2025)…
The extracted result stays unchanged. Your decision is added to its audit history.
06 · Preflighted
Formal drafting starts by freezing the request.
The preflight records scope, sources, model budget, and fixed tool authority — and creates nothing: no task, no run, no model call, no document. Governance happens before the first token, not after the mistake.
Saving freezes this request. It does not start Lex or create a document.
07 · Delivered
Deliverables land in the record, not in a chat window.
A finished draft arrives as a normal DMS version with AI provenance — 'Verified deliverable from legal graph' — ready for EdgeDocs or Word review before anything external happens.
The document's life from here →🗓 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
The difference
Context is engineered, not accumulated.
Most AI tools let context pile up until nobody knows what the model is looking at. A Project makes it explicit: these sources, these instructions, this memory policy — and work products that can prove they were built from the current record, not last month’s.
How Lex uses it →Build receipts
Every living work product records how and when it was built — deterministically.
Source fingerprints
419 sources verified against the current record. Stale is shown, never hidden.
Memory by policy
What Lex remembers and must confirm is a per-Project decision, not a default.
Capabilities
What it does
One governed context per case
A Project binds instructions, files, saved AI work, and memory policy to a matter. Project chats start from the whole case, not a blank box.
Review Tables
Pick a governed template (12 in English: Project Source Review, E-Discovery, Change of Control, Commercial Agreement, Lease, Credit Agreement…), freeze the exact sources, and EdgeLex fills typed, evidence-grounded columns across every document. A real run: 31 sources, 10 columns, 310 cells analyzed, 273 evidence passages, 275 policy-cleared cells, 54 verified empty results, 1 source limitation disclosed rather than hidden. Every cell opens its cited source at the page; a review assistant answers only from this run; drafts export to XLSX and PDF; publishing makes an immutable snapshot.
Discovery Matrix
Every request paired to its response and objection across the matter's discovery, with zero model calls: 361 items from 21 sources in one run, 117 unmatched requests and 126 unmatched responses surfaced as exceptions, 90 objection-only items queued for review, 245 production checks. Each item shows its exact evidence anchor (page and line), the lawyer confirms or corrects the pairing, adds a next action or a meet-and-confer entry, and the decision lands in the audit history. Freeze a working draft, publish a release, export XLSX, PDF, CSV or HTML.
Living work products
Case Status Summary, Matter Source Inventory, Matter Evidence Map, Issue Register, Case Chronology, or a custom work product defined in a sentence — built deterministically, stamped with a build receipt, and verified against current source fingerprints. FRESH means provably fresh; stale is shown, never hidden.
Immutable preflights
Formal drafting starts by freezing the request: scope, sources, model budget, and fixed tool authority — recorded before a single model call. The preflight itself creates nothing and spends nothing.
Deliverables land in the record
A draft arrives as a normal DMS version with AI provenance, ready for EdgeDocs or Word review — never a loose file in a chat window.
Memory under policy
Each Project chooses what Lex may remember and confirm: matter memory, document memory, related-matter context, personalization — checkboxes, not defaults.
In your control
The Project is a governance boundary: its instructions, sources, and memory policy are explicit and inspectable, its work products carry receipts, and nothing it produces enters the record without review.
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.
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.
Matters
Matter lifecycle, conflict checks, risk scoring, related-proceeding tracking, and a matter workspace the AI understands.
See EdgeLex on your own terms.
We'll walk through your firm's workflows, where you want it to run, and which AI you want it to use. A real person answers at sales@edgelex.com.