Legal OS Claude Code Matter-Isolated Context

Claude Code for Lawyers & Law Firms:
Your Legal Operating System

Q: Is Brainfile giving me legal advice?

No. Brainfile is a configuration and operating system for Claude Code — it helps legal professionals use AI more effectively. Brainfile is not a law firm, does not provide legal advice, and is not a substitute for a licensed attorney. The outputs Claude produces are drafts for attorney review, not final legal work product.

Stop rebuilding matter context every session. Brainfile gives legal professionals a persistent Claude operating system — jurisdiction-specific rules, review checklists, client intake logic, and compliance obligations — loaded automatically across every matter, every session.

Start Monthly — $99/mo Annual Plan — $999/yr (Save ~$190)

📅 Updated April 2026 ⏱ 11 min read 🎯 For Solo Practitioners, Small Firm Attorneys, In-House Counsel & Paralegals

Not legal advice. Brainfile is a software configuration product for Claude Code. It is not a law firm and does not provide legal advice. All AI-generated content is a first draft for attorney review — not final legal work product.

2 hr → 20 min

contract first-pass review with flagged clauses

90 min → 15 min

case research synthesis from memo notes

45 min → 8 min

client intake questionnaire to matter brief

Zero

cross-matter context bleed between clients

Table of Contents

The context problem legal professionals face with AI
What the Legal OS actually is
Use case 1: Contract drafting and review
Use case 2: Case research synthesis
Use case 3: Client intake automation
Use case 4: Billing narrative generation
Use case 5: Compliance monitoring
Before vs. after
A real Legal OS CLAUDE.md
Frequently asked questions

The Context Problem Legal Professionals Face

Every attorney who's tried using a general AI tool for legal work knows the frustration: you open a new session and have to re-establish the entire matter — the governing jurisdiction, the applicable statutes, the client's risk tolerance, the counterparty's known positions, the deal structure. A 30-second explanation becomes a 10-minute preamble before you can ask the actual question.

Worse, generic AI tools have no concept of your firm's preferred clause language, your jurisdiction's specific court rules, or the negotiating positions you've developed over years of practice. Every session starts from zero. Every output needs substantial reworking before it reflects how you actually practice.

The deeper problem for billable-hour practices: time spent re-explaining context to an AI is time that either doesn't get billed or eats into the efficiency gains the AI was supposed to create.

Brainfile solves this by encoding each matter's context permanently into a dedicated CLAUDE.md. Your jurisdiction-specific rules, preferred contract language, client risk profile, and matter history load automatically. You open Claude and it already knows the case.

What the Legal OS Actually Is

The key insight: CLAUDE.md is a persistent instruction file Claude reads at every session start. The Legal OS creates a separate CLAUDE.md for each matter — loaded with jurisdiction rules, client context, review checklists, and preferred clause language. Switching matters means switching directories. Each client's information is fully isolated by design, not by policy.

📋

Contract Review OS

Your firm's standard review checklist, red-flag clause library, preferred fallback language, and jurisdiction-specific enforceability rules — applied automatically to every contract Claude touches. First-pass review in 20 minutes, not 2 hours.

🔬

Research Memory OS

Case law summaries, statutory notes, prior research memos, and jurisdiction-specific procedural rules — stored in brain/research/ and surfaced automatically when Claude works on a related matter. Compound your research over time instead of starting from scratch.

💬

Client Communication OS

Client communication preferences, matter history, key dates, and prior correspondence context — encoded per client so every update letter, status email, and intake response reflects the relationship, not a generic form.

⚖️

Compliance Tracking OS

Regulatory frameworks, filing deadlines, reporting obligations, and jurisdiction-specific compliance calendars — maintained in brain/compliance/ so Claude flags upcoming obligations automatically when you're working on a client's matter.

Use Case 1: Contract Drafting & Review

First-pass contract review in 20 minutes, not 2 hours

Contract review is where legal AI provides the clearest time savings — but only if Claude knows your review standards going in. A generic AI tool reviews a contract against general legal principles. The Legal OS reviews it against your firm's specific red-flag library, your client's known risk tolerances, and the governing jurisdiction's enforceability rules.

NDA First-Pass Review

"Review this NDA against our standard checklist. Flag any deviation from our preferred mutual NDA language. Client is a Series B SaaS company — they're risk-averse on IP assignment and California jurisdiction."

Claude applies your firm's NDA checklist, flags non-standard clauses, and notes enforceability concerns under California law — without you explaining any of that context, because it's already in the matter's CLAUDE.md.

⏱ 2 hours → 20 minutes for first-pass review

Commercial Contract Redline

"Draft redline comments on sections 7, 11, and 14. Use our standard fallback positions. Flag anything that contradicts the indemnification structure we negotiated in the LOI."

Claude generates redline commentary using your firm's preferred fallback language — stored in brain/contracts/fallbacks/ — and cross-references the LOI terms already captured in brain/matters/[client]/.

⏱ Saves 60-90 minutes per contract redline cycle

Use Case 2: Case Research Synthesis

Turn raw research into a structured memo in 15 minutes

Legal research produces a pile of case citations, statutory text, and law review excerpts. Synthesizing it into a coherent argument structure is where the real time goes. The Research Memory OS stores your prior case law summaries by topic and jurisdiction — so Claude isn't just organizing today's research, it's surfacing relevant prior work from similar matters automatically.

Research Memo Draft

"Here are my notes from three days of research on implied covenant claims under Illinois law. Draft a research memo structured as: issue, brief answer, analysis, conclusion. Cross-reference any prior memos we have on similar issues."

Claude synthesizes raw notes into a structured memo and surfaces related research stored in brain/research/IL/implied-covenant/ — compounding prior work instead of treating every matter as a clean start.

⏱ 90 minutes → 15 minutes for research memo draft

Case Law Summary Library

"Add this case to our research library: [citation]. Summarize the holding, the key facts, and why it's relevant to landlord-tenant disputes in Cook County. Tag for future retrieval."

Claude generates a structured case summary and stores it in brain/research/IL/landlord-tenant/ — building a searchable case library that every attorney on the matter can use without re-reading the opinion.

⏱ Compound research value across every matter

Use Case 3: Client Intake Automation

Intake questionnaire to structured matter brief in 8 minutes

Client intake is the highest-leverage place to establish the matter context that the Legal OS will use for the entire engagement. Instead of converting handwritten intake notes into a usable matter brief manually, the Client Communication OS takes raw intake notes and generates a structured brief, conflict check input, and first-session agenda automatically.

Intake Notes to Matter Brief

"Here are my notes from the initial consultation with the new client. Generate: (1) structured matter brief, (2) conflict check list of all parties mentioned, (3) preliminary statute of limitations analysis, (4) first 30-day action items."

Claude converts unstructured intake notes into a four-part brief that immediately goes into brain/matters/[client]/ — establishing the matter context that every future session will build on automatically.

⏱ 45 minutes → 8 minutes per new matter setup

Client Status Update Letter

"Draft a status update letter to the client summarizing what happened at the deposition today and what comes next. Keep it plain English — they're not a legal professional."

Claude knows the client's communication preferences and the matter history from their CLAUDE.md — it writes in accessible language, references the right background facts, and matches the tone you've established with this client.

⏱ 30 minutes → 5 minutes per client update

Use Case 4: Billing Narrative Generation

Convert time entries into compliant billing narratives

Billing narrative is one of the most time-consuming non-billable tasks in legal practice — turning cryptic time entries into client-ready descriptions that satisfy billing guidelines, avoid block-billing objections, and reflect the value delivered. The Legal OS stores your clients' billing guidelines and preferred narrative style so Claude generates compliant entries from shorthand notes.

Time Entry Narratives

"Convert these time entries into billing narratives. Client: Meridian Corp. Their billing guidelines prohibit block billing and require task descriptions under 25 words each. Entries: 2.3h — contract review; 0.8h — client call re: indemnification."

Claude generates task-by-task narratives that comply with the client's specific billing guidelines, stored in brain/clients/meridian/billing-guidelines.md — no manual reformatting or guideline re-reading required.

⏱ 40 minutes → 6 minutes per monthly billing cycle

Pre-Bill Review Summary

"Review this month's draft bill before it goes to the client. Flag any entries that could trigger a billing objection. Summarize the work by matter phase for the cover letter."

Claude reviews the draft against the client's known objection history (stored in brain/clients/) and generates a cover letter that contextualizes the fees within the matter's progress — reducing write-off risk.

⏱ Reduces billing objections and write-off risk

Use Case 5: Compliance Monitoring

Never miss a filing deadline or regulatory obligation

For in-house counsel and practices with regulatory-heavy clients, compliance tracking is a constant background process. The Compliance Tracking OS maintains a living obligations register per client — filing deadlines, reporting windows, regulatory thresholds, and jurisdiction-specific notice requirements — and surfaces them automatically when you're working on a related matter.

Compliance Calendar Update

"We just received the new SEC guidance on beneficial ownership reporting. Update the client's compliance obligations register and flag any upcoming deadlines in the next 90 days that are affected."

Claude updates brain/compliance/[client]/obligations.md with the new requirements and cross-references the existing calendar — so the next session working on this client automatically surfaces the updated deadlines.

⏱ Eliminates manual compliance calendar maintenance

Regulatory Change Briefing

"Draft a brief memo to the client summarizing the practical impact of the new Illinois BIPA amendments on their HR data practices. Include the three specific steps they need to take before Q3."

Claude drafts the memo using the client's industry context and existing BIPA compliance posture stored in brain/clients/ — producing a client-ready briefing that's already tailored to their specific situation.

⏱ 2 hours → 20 minutes per regulatory update briefing

Before vs. After: What Changes

Task	Without Brainfile	With Legal OS
Contract first-pass review	2 hours manually flagging clauses against a checklist in your head	20 minutes — review checklist and red-flag library auto-loaded
Research memo	90 minutes organizing notes, plus re-reading prior memos for overlap	15 minutes — prior research surfaces automatically from brain/research/
Client intake to brief	45 minutes converting handwritten notes into a structured matter brief	8 minutes — Claude generates brief, conflict list, and action items
Billing narratives	40 minutes per billing cycle reformatting entries to client guidelines	6 minutes — billing guidelines auto-loaded, narratives generated from shorthand
Compliance calendar	Manual tracking spreadsheet, updated by whoever remembers	Living obligations register in brain/compliance/ — surfaced automatically
Matter knowledge retention	Context lives in one attorney's head; lost on transition or departure	Encoded in brain/matters/ — survives attorney transitions, accessible to team

A Real Legal OS CLAUDE.md

This is what a matter-specific CLAUDE.md looks like inside the Legal OS. Claude reads this at every session start and applies it to every task for that matter automatically.

# Legal OS — Matter: Meridian Corp / Series B Financing (CLAUDE.md)

## Matter Context
- Client: Meridian Corp (SaaS, Series B, Chicago IL)
- Matter type: Venture financing — Series B preferred stock
- Governing law: Delaware corporate, Illinois governing agreements
- Lead attorney: [Your name], associate: [Associate name]
- Matter opened: 2026-03-12, expected close: 2026-06-30

## Client Risk Profile
- Risk tolerance: Moderate — founder-led, first institutional round
- Priority concerns: IP assignment, anti-dilution provisions, board composition
- Known counterparty positions: Lead investor prefers broad information rights
- Prior counsel: None (first financing)

## Jurisdiction Rules
- Delaware: Apply DGCL §151 for preferred stock terms analysis
- Illinois choice of law: Governing law clause enforceability per Restatement §187
- See brain/research/DE/preferred-stock/ for relevant precedent

## Review Standards
- Contract review: Apply brain/checklists/series-b-financing.md
- Red flags: Any deviation from NVCA model documents — flag and note delta
- Billing: Meridian billing guidelines in brain/clients/meridian/billing-guidelines.md
- No block billing. Task descriptions ≤ 25 words. Monthly budget: $35K

## Matter History
- See brain/matters/meridian-series-b/ for all prior memos and correspondence
- Term sheet negotiated 2026-03-28 — see brain/matters/meridian-series-b/term-sheet-notes.md
- Open items: Board seat composition, ROFR carve-out for secondary sales
    

Legal OS Directory Structure

legal-os/
  CLAUDE.md                      # Firm-wide standards, billing rules, QA process
  brain/
    checklists/
      nda-review.md              # Standard NDA review checklist
      series-b-financing.md      # Series B deal checklist
      employment-agreement.md    # Employment contract review checklist
    contracts/
      fallbacks/                 # Firm's preferred fallback clause language by type
    research/
      DE/                        # Delaware case law and statutory notes
      IL/                        # Illinois case law by practice area
  matters/
    meridian-series-b/
      CLAUDE.md                  # Matter-specific context (overrides firm-wide)
      brain/
        intake/                  # Client intake notes and matter brief
        research/                # Matter-specific research memos
        compliance/              # Obligations register and deadline calendar
        correspondence/          # Key client and counterparty correspondence
    acme-employment/
      CLAUDE.md                  # Fully isolated — zero bleed from other matters
      brain/
        ...
    

Frequently Asked Questions

Is Brainfile giving me legal advice?

No. Brainfile is a software configuration product for Claude Code. It is not a law firm and does not provide legal advice. All AI-generated content is a first draft for attorney review — not final legal work product. The attorney remains responsible for all work product delivered to clients.

How does the Legal OS handle client confidentiality?

Brainfile runs entirely in your local Claude Code environment. Your client data, matter notes, and CLAUDE.md files never leave your machine unless you push them to a git server you control. There is no Brainfile cloud that processes your client information. You remain in complete control of where data is stored and who has access.

Can different matters have separate, isolated contexts?

Yes. Each matter gets its own directory with a dedicated CLAUDE.md and brain/ folder. Claude only reads the configuration in the directory you're currently working in — switching matters means switching directories. Client A's facts, strategy notes, and jurisdiction-specific rules never appear when you're working on Client B.

How is this different from Harvey or other legal AI tools?

Harvey and similar tools are standalone platforms with their own interfaces and pricing models, often geared toward BigLaw. Brainfile configures Claude Code — a tool you already pay for — to behave like a legal practice operating system. You define the protocols, the checklists, and the jurisdiction-specific rules. It runs in your environment, under your control, without per-seat enterprise pricing.

Can paralegals and associates use the same Legal OS configuration?

Yes. The CLAUDE.md and brain/ directory for each matter can live in a shared git repo. Every team member who works on that matter clones the repo and runs Claude locally. When you update the matter's strategy memo or add new case law, commit the change — everyone's Claude sessions reflect it immediately.

What's the pricing and does it include updates?

Brainfile costs $99/month or $999/year (saving approximately $190). Your subscription includes the Legal OS configuration and all updates. The configuration runs in your own Claude Code environment — there are no per-matter fees, no per-user charges, and no data is processed by Brainfile servers.

Give Every Matter an AI That Already Knows the Case

Stop rebuilding context. Stop re-explaining jurisdiction rules. Give your practice a persistent operating system for every matter — set up once, loaded automatically every session.

Start Monthly — $99/mo → Annual Plan — $999/yr (Save ~$190)

$99/mo · No per-matter fees · No per-user charges · Runs in your environment · Cancel anytime

Claude Code for Lawyers & Law Firms:Your Legal Operating System