Nothing floats
Every durable chat, document, and run carries its organization and project. There is no 'no project' state — orphan work cannot exist.
Domain-specific AI for legal work
Legal AI, on the record.
Lia is the matter-first workspace where lawyers and agents work the same corpus — research, drafting, redline, review, and automation — with every output traced to a source you can open and verify.
Project Meridian
Acquisition of Meridian Biotech by Northstar Health
Add filesInvite
Ask anything in Project Meridian
SourcesCreateModel
Your history
Summarize consent requirements across the data room1 hour ago
Change-of-control provisions — buyer analysis1 day ago
Indemnification caps: market benchmarks1 day ago
Exclusivity extension letter drafting2 days ago
HSR filing readiness checklist3 days ago
Instructions
Advise Northstar Health on the Meridian acquisition. Flag consent requirements, assignment restrictions, and conditions to closing.
Recent files View all
Meridian SPA — v4.docxJul 6, 2026
Disclosure Schedules.pdfJul 6, 2026
VDR Index.xlsxJul 6, 2026
Q2 Board Minutes.pdfJul 5, 2026
Diligence Memo — IP.docxJul 5, 2026
Integration Plan.pptxJul 3, 2026
The architecture
Legal work is matter-shaped. So is Lia.
Chats, documents, research runs, drafts, and agent work don't float in a global feed — they live inside the matter they belong to. Projects are the clean boundary for each engagement: its people, its corpus, its knowledge, its automations. Sessions capture each work episode so you can resume it, share it, or put it in front of a reviewer — and every activity inside stays on the record.
- Organization
- Your firm — tenancy, membership, billing, and the top-level boundary nothing crosses.
- Project
- The matter — a clean home for the people, documents, knowledge, and work of one engagement.
- Session
- The work episode — what you were doing Tuesday afternoon, resumable, shareable, and deep-linkable.
- Activity
- Every action and artifact — each query, draft, redline, and run, recorded where it happened.
Organization org_northstar
Project Meridianthe matter boundary
MembersInstructionsCorpusTemplatesKnowledgeAutomations
Session — Change-of-control research1h ago
Corpus query 12 citations Memo draft
Session — Exclusivity letter drafting1d ago
Template copy Redline Approval sent
Every activity lands in a session. Every session belongs to a matter. Every matter lives inside your organization — permissions, knowledge, and context follow the same boundary.
Containment
You always know where you are.
General-purpose AI blurs accounts, teams, projects, chats, and memories — you're left guessing which container is answering you, and what happens to a thread when its project moves. Casual use tolerates that. Legal work can't: client boundaries, matter scoping, privilege, and retention depend on knowing exactly what belongs where. Lia commits to one hierarchy with hard edges — and the product, the URLs, and the API all speak it.
lia-ai.comhost/o/org_northstarOrganization/p/proj_meridianProject/s/sess_0142Session“Where am I?” is answered by the address bar — never inferred from sidebar placement. Path segments are stable ids, so renaming a matter never breaks a link.
No fake defaults
My Project is a real project row, not a UI fiction. Rename it, archive it, outgrow it — it behaves like any other matter.
Settings stack cleanly
User preferences → organization config → project context. A new matter inherits the organization — never a sibling matter's scope.
Sharing follows the boundary
Access flows organization → project → object. 'Who can see this?' has exactly one answer, at every layer.
Everything a matter needs, in one system of record
Research, drafting, redline, vault, workflows, and agents share one foundation — the matter's corpus, the matter's knowledge, and citations on every output.
01 · Research
Authority you can open
Ask in plain language or precise terms. Lia answers from the corpus you trust — case law, statutes, filings, and your own precedent — with treatment signals on every authority and pinpoint citations on every proposition. If it can't cite it, it doesn't say it.
- Cite-checked by default — every claim resolves to an authority you can open at the pinpoint.
- Treatment signals — followed, distinguished, or overruled — know where an authority stands.
- Matter-scoped — research runs land in the session, next to the work they support.
Assignment & change-of-control — authoritiesIllustrative product preview
Controlling contract languageIllustrative preview
MatchedJurisdiction-specific authorityIllustrative preview
In scopeMatter precedent noteIllustrative preview
ReviewLia can keep contract language, authority signals, and matter precedent in one review trail so lawyers can open the supporting source before relying on the answer.
[1] Source excerpt[2] Matter note
Meridian SPA — §8.2 AssignmentTurn 4 · vs. playbook
Neither party may assign this Agreement without the prior written consent of the other party, which consent may be withheld in its sole discretion such consent not to be unreasonably withheld, conditioned, or delayed.
Notwithstanding the foregoing, Buyer may assign this Agreement to any Affiliate upon written notice to Seller.
Any purported assignment in violation of this Section shall be null and void.
FallbackPlaybook · Assignment
Preferred: mutual consent, reasonableness standard. Fallback: affiliate carve-out with notice. Escalate: sole-discretion consent.
Why this edit
Sole-discretion consent conflicts with your playbook position and the deal's pre-closing reorganization plan.
Approval requested — Partner review
02 · Contracts & Redline
From intake to signature, one thread
Run intake, review, and approvals through the matter. Draft from your templates and playbooks, redline against your positions with reasons attached, and keep every turn — who changed what, and why — on the record.
- Intake to signature — requests, review queues, and approval gates in one thread.
- Playbook-aware redlines — edits argue from your standard positions, not generic guesses.
- Templates that live in the matter — copy a template into the project and draft inside its corpus.
03 · Vault & Records
The corpus is the matter
Every document lands in the matter's vault with provenance intact — versions, sources, and the session that produced it. Then put the whole corpus to work: query thousands of documents at once and extract the terms that matter into structured tables.
- Provenance on every row — who added it, which session touched it, what it produced.
- Review at scale — one query across the data room, answers in a structured table.
- A record, not a bucket — versions and sources persist — work product stays defensible.
Project Meridian — Vault341 files
Material Contractsuploaded · VDR sync264 files
Meridian SPA — v4.docxsess_draft-loop · redlineContract
Q2 Board Minutes.pdfuploaded · E. KatzGovernance
Diligence Memo — IP.docxsess_ip-review · outputWork product
Extraction · change-of-control terms
Consent required31 of 264
Sole discretion6 flagged
Notice only48 found
NDA first-pass reviewRun #212 · Project Meridian
Intakecounterparty NDA received
DoneScreen against playbookterm · confidentiality · residuals
DoneApproval gate2 deviations → partner review
WaitingReturn redlinemarkup + rationale to requester
Queued04 · Workflows & Automations
Encode the routine passes
Turn the passes your team repeats into standing workflows — first-pass review, clause extraction, filing checklists, intake triage. Runs attach to the matter, wait at the approval gates you define, and never act past the authority you give them.
- Encode the routine — the passes you repeat become workflows the whole team shares.
- Approval gates built in — deviations stop and wait for a human — that is the design.
- Runs on the record — every run logs its steps in the matter, like any other session.
05 · Agents
Delegate episodes, not judgment
Hand an agent a whole work episode — research a question, assemble a diligence memo, prepare a closing checklist. It plans, works the matter's corpus and tools, and returns with sources attached and every step logged. You review, revise, and decide.
- Grounded in the matter — agents see the project corpus and knowledge — nothing outside it.
- Every step logged — plans, tool calls, and sources land in the session as activities.
- Judgment stays with you — agents deliver for review — they do not sign, send, or file.
Agent — Diligence memo: consent requirementsSession · live
Plan the episodescope: 264 material contracts · consent + assignment provisions
Work the corpusvault.query · extract.table · 31 consent triggers found
Draft the memodraft.compose · citing 12 sources from Project Meridian
Return for reviewmemo + extraction table + full activity log
Nothing leaves the matter without your reviewReview
Security
Engineered for privileged work
Confidentiality isn't a feature tier — it's the architecture. Lia is built for privileged, high-stakes matters from the first line of code, and the same boundary that organizes your work enforces who can see it.
Talk to us about securityEncryption controls
Encryption and transport controls are deployment requirements for documents, messages, and indexes.
Data-use controls
Workspace data-use commitments are governed by the provider and deployment controls selected for the customer lane.
Tenant-aware boundaries
Organization, project, and object boundaries drive access checks across the workspace.
Access follows the matter
Organization, project, and object permissions — matter walls are native, not bolted on.
Audit-ready activity
Key queries, access, and actions are being shaped for reviewable event trails.
Enterprise identity controls
SAML SSO, SCIM provisioning, and role-based permissions are part of the enterprise security roadmap.
Deployment controls are evaluated per customer lane. SOC 2 and ISO 27001 readiness remain enterprise roadmap workstreams as Lia scales out of private beta.
What we believe legal AI should be
Cited by default
Every answer traces back to a source you can open, read, and check. No claim stands without one.
Matter-scoped by design
Context, permissions, and knowledge follow the matter — nothing leaks across engagements, and nothing floats without a home.
Private by architecture
Your data stays inside firm-scoped controls, with deployment-specific data-use commitments documented for each customer lane.
Legal AI should earn trust the way a good lawyer does — by citing its sources, showing its work, and keeping every matter's confidence. We're building Lia to do exactly that, in the open, with the firms using it.
— The Lia teamSee Lia on your matters.
We're onboarding a small group of design partners. Book a demo, bring one live matter, and watch it become a workspace — people, corpus, sessions, and record included.