Companion brief · Current through May 1, 2026

Legal AI's observability gap.

The profession is not ignoring AI risk. It is absorbing AI through old governance systems faster than those systems can make AI use visible, auditable, priced correctly, and disciplined.

Executive signal

The problem is not AI use. It is hidden AI use.

The central finding is that generative AI has moved into legal production while the profession still relies mainly on traditional duties of competence, confidentiality, supervision, candor, communication, and reasonable fees. Those duties matter, but they do not automatically create proof of what happened. [1]

Visible failures

Fake citations are the public symbol.

Hallucinated authorities, fabricated quotes, and corrected filings are visible because courts, opposing counsel, and citators can detect them. They are important, but they are only the surface layer. [14] [15]

Invisible routine

Correct AI use is usually private.

Clients often cannot see tool choice, prompt logs, retained data, verification steps, model routing, or whether AI materially compressed billed work.

Governance gap

Responsibility without auditability is fragile.

The next phase of legal AI governance will turn on evidence: data path, authority, retention, billing model, verification, and preserved records.

Current record

A recent signal is supervision.

Recent public matters sharpen the page's original thesis. Courts and opposing counsel are no longer looking only for the person who typed a prompt. They are looking for supervision, disclosure, vendor attribution, and proof that verification actually occurred.

Supervision

A false citation can become a management failure.

On April 28, 2026, U.S. Magistrate Judge Peter Kang (N.D. Cal.) sanctioned managing partner Lenden Webb $1,001 in Hill v. Workday over a junior attorney's AI-assisted brief with a false citation. The order treated citation checking and review as supervisory obligations, not merely individual-user obligations. Reuters reported that the record was less than clear as to the source of the false citation. [17]

Disclosure

When AI contributes to an error, candor matters.

The Oregon Court of Appeals sanctioned a lawyer, struck a filing, and ordered roughly $8,000 in fee shifting after fabricated quotations and other AI-related errors appeared in a brief. [18]

Vendor attribution

The tool name is becoming part of the dispute.

In Hill v. Workday, the junior attorney attributed the false citation in part to Thomson Reuters' Westlaw AI / CoCounsel. Thomson Reuters stated that an internal review found no evidence its tools generated the citation. With no shared audit trail, neither account could be conclusively verified. Tool identity, model path, prompt, output, and reviewer records become central to observability. [17] [19]

Scope

The visible record now spans practice settings.

Recent examples include appellate sanctions, a public reprimand of a former federal prosecutor, and an elite-firm correction. The safer wording is broad failure record, not a claim that every example was sanctioned. [14]

Market pressure

The numbers explain the incentive problem.

These public anchors are not neutral social science. Several are vendor or industry reports. They are still useful because they show market pressure, workflow adoption, and client-firm misalignment that make the coordination problem plausible. [8] [9] [10]

90%Percent of legal dollars still flowing through hourly arrangements in the Thomson Reuters and Georgetown 2026 market report. [8]
80%Percent of Fortune 1000 executives in a LexisNexis survey expecting outside counsel bills to drop from GenAI efficiencies. [9]
9%Percent of large law firm executives reporting that clients had expressed that billing-reduction expectation. [9]
5,700Freshfields employees given access to Claude via the firm's AI platform after a multi-year Anthropic partnership. [11]
>60%More than 60 percent of federal judges responding to a Northwestern survey reported using at least one AI tool, with use intensity varying by judge. [16]
1,394Entries tracked in Damien Charlotin's AI Hallucination Cases database, which describes itself as a work in progress tracking legal decisions and documents addressing AI hallucination issues, with limited unconfirmed-AI exceptions noted. Last updated May 1, 2026. [15]
Coordination failure

Four forces pull the market away from the cooperative optimum.

Each actor has a defensible local incentive. Firms must adopt. Clients want savings. Courts want candor without noise. Vendors want scale. Bar guidance preserves traditional duties. The system result can still be under-disclosure.

Adoption pressureNon-adoption becomes competitively costly.
Legacy billingHourly economics collide with time compression.
Observability failureCritical workflow facts remain private by default.
Architecture asymmetryPublic, enterprise, private, and air-gapped systems differ materially.
AI governance gap
Adoption is rational.AI can summarize, draft, extract facts, build chronologies, assist discovery, compare contracts, and accelerate research.
Disclosure is costly.Transparent time compression can threaten hourly revenue, bargaining leverage, staffing assumptions, and perceived value.
Non-disclosure is tempting.A generic invoice or polished memo often hides the production chain unless an error or dispute exposes it.
Architecture only solves part of it.Secure local AI can reduce data exposure. It does not decide who captures the productivity surplus.
Self-regulatory loop

The profession regulates a tool it is also adopting.

This is not inherently corrupt. It is the traditional structure of lawyer self-regulation. AI changes the stakes because delegation, data routing, and billing compression can be hidden at scale.

A lawyer can produce work faster while the client may not see tool choice, data routing, output verification, log retention, or billing impact.

Most acute pressure point

AI turns the billable hour into a surplus-allocation fight.

Under honest hourly billing, reduced human time should reduce billed time. Under fixed or value pricing, the firm may capture more upside if the bargain is explicit. The danger zone is opaque hybrid behavior: AI-compressed work presented as ordinary hourly production.

Compression simulator

Adjust a stylized task to see why the incentive problem is structural. This is not an accusation of overbilling. It is a mechanism map.

If actual time is lower, hourly integrity requires the time entry to follow the human work actually performed. Value pricing can be legitimate, but the engagement terms need to state the bargain.

Traditional hourly invoice$6,500
Before AI
Actual hourly invoice after compression$650
If time follows work
Potential hidden surplus$5,850
If old hours are preserved

Compression ratio: 10.0x

Thomson Reuters describes a structural mismatch where AI can perform some tasks in minutes while most legal dollars still move through hourly-rate arrangements. [8]

Architecture as evidence

AI risk is not generic. It is architectural.

The question is not merely whether a lawyer used AI. The better question is what architecture touched the client's data, under what controls, and with what proof.

Public chatbot

Highest concern for confidential facts, discovery materials, privilege workflows, and client strategy unless terms and data controls are clearly adequate.

Enterprise AI

Better contractual controls may exist, but retention, training, logs, subprocessors, and deletion still need diligence.

Legal AI platform

Domain-specific workflows help, but legal content branding is not a substitute for matter-specific data-path proof.

On-premise

Lower third-party exposure when deployed with matter isolation, access controls, logs, and disciplined operation.

Air-gapped

Strongest data-path proof for high-stakes corpora, but still needs verification, logging, governance, and billing transparency.

Architecture can reduce data-exposure risk and make routing auditable. It does not eliminate the risk. A controlled system can help prove approved data routing only when logs, access controls, retention rules, deletion terms, training restrictions, and review records are actually preserved. It also does not answer whether the client, the firm, or both capture the productivity surplus.
A serious battleground

Discovery is where AI risk becomes concrete.

Discovery combines volume, privilege, third-party information, confidential business records, privacy obligations, clawback regimes, and high AI productivity upside. Courts are beginning to distinguish public tools from closed or secure tools. [12] [13]

Weak protocol

Confidentiality label decides everything.

Non-confidential discovery can be uploaded to public tools
Clawback does not necessarily remove data from a model ecosystem
Prompt logs and deletion mechanics remain uncertain
Mature protocol

Data path decides risk.

Public tools restricted for discovery materials
Closed tools permitted only with safeguards
Logs, deletion, training bans, and certification are specified
Protective-order signal: recent commentary tracking 2025-2026 federal decisions identifies AI-specific protective-order language as an emerging battleground for confidential discovery, including bans or contract-based safeguards for model training, onward disclosure, deletion, and auditability. [20]
Visible tail

Hallucinations matter, but they are not the whole risk universe.

The visible failure record is growing and now reaches small firms, pro se parties, government lawyers, appellate practice, supervisory review, and elite-firm corrections. The larger governance problem is what remains invisible when the output is plausible.

Visible failure Fake citations

Easy to spot. Easy to sanction. Easy to talk about.

Harder-to-see risks What clients, courts, and firms often cannot see
Data routing
Missed evidence
Hidden billing compression
Unlogged prompts
Vendor retention
Chambers use

Surface failure: false legal authorities.

Sullivan & Cromwell apologized in April 2026 for AI-generated inaccuracies in a court filing. Reuters also reported an Alabama Supreme Court sanction, a former federal prosecutor's public reprimand, an Oregon fee-shifting ruling, and May 1 coverage of an April 28 supervisory sanction tied to an AI-assisted brief. [14] [17] [18]

Attribution failure: lawyer, workflow, or vendor?

Recent reporting describes disputes over whether a named legal AI product was responsible for fabricated filing content or whether the failure came from lawyer use, review, or copying. The answer depends on logs. [19]

Subsurface failure: plausible but wrong work.

A model can distort a chronology, omit adverse facts, summarize discovery incorrectly, or import framing bias without producing a fake citation.

Control failure: policy without workflow proof.

The relevant question becomes whether the lawyer or firm can show approved tools, supervisory review, data restrictions, verification steps, controlled logs, and consequences for noncompliance.

Institutional exposure

Judges, vendors, and insurers sit inside the same opacity problem.

The profession's legitimacy depends on accountable human judgment. AI does not eliminate that requirement. It makes proof of supervision more important.

Judiciary

AI must not become an invisible adjudicator.

The federal judiciary created an advisory AI Task Force in 2025, and a 2026 survey reported broad but uneven AI use among federal judges. Public norms for chambers use remain immature. [7] [16]

Vendors

Legal AI is becoming infrastructure.

Major partnerships, embedded research tools, practice platforms, and agentic workflows mean vendor terms can affect privilege, auditability, work product, and client trust. When a tool is named after a filing failure, vendor attribution becomes an evidentiary issue, not just a procurement issue. [11] [19]

Insurance

Some potentially useful risk data is private.

Malpractice and cyber carriers may see claim patterns, near misses, and control failures that never become public discipline records. Anonymized claim typologies would improve the feedback loop.

Risk findings

Ten places where visibility determines trust.

Filter the findings by primary exposure. Several risks overlap because the same hidden workflow can affect confidentiality, billing, discovery, and candor at once.

01 Data

Confidentiality and privilege

Prompts, documents, strategy, work product, and privileged communications need controlled routing.

02 Court

Discovery integrity

Public AI upload can undermine clawback, privacy, trade secret controls, and production trust.

03 Court

Candor and accuracy

False citations are sanctionable, but plausible factual distortions may be harder to detect.

04 Economic

Fee transparency

AI compresses time while clients often cannot see whether invoices reflect actual human work.

05 Client

Communication duties

Material AI use may affect consent, confidentiality, pricing, strategy, and client decision-making.

06 Court

Judicial legitimacy

Chambers AI needs boundaries for reasoning-sensitive use, sealed records, verification, and disclosure triggers.

07 Market

Vendor dependence

Contracts, subprocessors, model routing, prompt logs, versioning, and incident response become legal facts.

08 Operations

Supervision and policy gaps

A policy memo is weak unless paired with approved tools, controlled logs, training, supervisory review, and enforcement.

09 Access

Access-to-justice tension

AI can help self-represented litigants, while secure tools may be costly or unavailable to them.

10 Trust

Appearance of conflict

Self-regulation, vendor sponsorship, procurement, and internal adoption need stronger transparency.

Mechanism design

The fix is tiered observability, not a blanket ban.

The mature regime matches architecture, disclosure, logging, and pricing rules to legal risk. Low-risk administrative uses do not need the same treatment as privileged discovery analysis or dispositive court filings.

Client-facing AI protocolsDefine permitted tools, prohibited tools, data restrictions, consent, verification, log preservation, and fee treatment.
Data-routing certificationIdentify tool, vendor, model family, data category, retention, training restrictions, logs, deletion, subprocessors, and storage jurisdiction.
Matter-level AI logsPreserve material prompts, outputs, tool identity, model identity or version, user identity, timestamps, retrieved materials, reviewer identity, and verification status, subject to privilege, retention, access-control, and minimization rules.
Invoice integrity rulesHourly matters should reflect actual attorney time. Fixed or value pricing should disclose how technology efficiencies are allocated.
AI clauses in protective ordersDefine public and closed tools, training bans, deletion, audit logs, notice procedures, and AI-assisted review limits.
Chambers AI policiesSeparate administrative uses from reasoning-sensitive uses, and set disclosure triggers for material AI assistance.
Public discipline taxonomyCode incidents by false citation, data upload, billing, disclosure, discovery misuse, judicial use, or vendor issue.
Vendor diligence standardizationMove from adjectives like secure to evidence about retention, training, routing, access, deletion, audit, incident reconstruction, and matter isolation.
Insurance feedback loopPublish anonymized claim typologies so the profession can learn from failures without exposing confidential claims.
Architecture-based safe harborsReward audited, matter-isolated, no-training, access-controlled, log-preserving, local or air-gapped systems.
Approved architectureData is routed through approved environments under documented controls.
AuditabilityLogs prove tool, prompt, output, user, time, and verification.
Pricing integrityThe client sees how AI affects billing or value pricing.
Public confidenceRules, court policies, discipline, and vendor diligence become legible.
Operational questions

Ask for proof, not vibes.

The practical takeaway is a shift from AI slogans to evidence. These are the questions that distinguish declared governance from actual control.

What tools are approved, prohibited, or restricted by matter type?
What client or matter data may enter each approved tool?
What evidence proves vendor promises were followed?
How are AI outputs verified before client delivery or court filing, and who signs off on that review?
How does AI affect hourly billing, fixed fees, budgets, and client disclosure?
Where are material prompts, outputs, retrieved documents, supervisory approvals, and verification records preserved?
Which AI tools may touch our matter, and which are forbidden?
Will confidential or privileged information enter any third-party system?
Will any tool retain, log, train on, or route our data through subprocessors?
Can the firm certify that public AI tools will not receive our documents without written consent?
Will AI reduce bills, change pricing, or affect staffing assumptions?
Will material AI logs be preserved for discovery, privilege, advice, and filings?
Do filing rules target material AI use without requiring noisy disclosure of trivial uses?
Do protective orders define open tools, closed tools, training bans, deletion, and auditability?
Do court policies address sealed records, confidential materials, and chambers data routing?
Are judges, clerks, and staff required to verify outputs independently?
Are AI-related sanctions coded in searchable categories?
Are disclosure triggers clear when AI materially assists reasoning or dispositive drafting?
Can the product provide matter-specific audit evidence, including tool, model, run, prompt, output, and reviewer path?
Are retention, deletion, training exclusions, model routing, and subprocessors documented?
Can customers place prompts and outputs under litigation hold?
Does the tool support matter isolation and role-based access controls?
Are incident response and breach notification terms tuned to legal confidentiality obligations?
Can the vendor prove its claims without relying on marketing labels?
2022 to 2026

From experiment to operating infrastructure.

The transition has been fast. Rules, sanctions, partnerships, and survey evidence now point in the same direction: AI is embedded, while observability is still catching up.

2022Generative AI enters mainstream legal awareness as large language models become widely available.
2023California approves practical guidance for lawyers using generative AI, putting early state-lawyer guidance into the developing ethics record. [4]
2024Florida Opinion 24-1 and ABA Formal Opinion 512 apply core professional duties to generative AI, including competence, confidentiality, communication, billing, verification, and advertising issues. [1] [2]
2025The federal judiciary establishes an advisory AI Task Force. Illinois adopts a court-system AI policy effective January 1, and Texas Opinion 705 addresses lawyer use of generative AI. [7] [5] [3]
Early 2026New York adds Part 161, effective June 1, and March protective-order rulings in Morgan and Jeffries push AI discovery disputes into concrete order language. [6] [12] [13] [20]
Apr to May 2026Freshfields and Anthropic announce enterprise co-development. Recent sanctions, disclosure rulings, vendor-attribution disputes, and May 1 Reuters coverage of an April 28 supervisory sanction make auditability the operative issue. [11] [14] [17] [18] [19]
Falsification

What would weaken the thesis?

A strong structural thesis should say what evidence would count against it. These are the public signals that would make the coordination-failure diagnosis less compelling.

Visible client disclosure becomes normal.

Reliable public data shows firms routinely disclose material AI use, preserve matter-level logs, and pass hourly savings through to clients.

Outside-counsel rules become specific.

Guidelines broadly require AI-use disclosure, data-routing certification, and invoice-level AI treatment, with documented compliance.

Claims and discipline become measurable.

Disciplinary bodies and insurers publish reliable AI-coded typologies showing rare, well-controlled harm.

Billing model pressure declines.

Alternative fees or value pricing displace hourly billing enough that time compression no longer creates the same surplus-allocation conflict.

Source trail

Public source trail.

This page synthesizes public-source checks through May 1, 2026. It is not legal advice.

  1. American Bar Association, Formal Opinion 512 coverage. The ABA describes duties of competence, confidentiality, communication, supervision, candor, and reasonable fees for lawyers using generative AI.
  2. The Florida Bar, Opinion 24-1. Guidance on confidentiality, competence, billing, and advertising when lawyers use generative AI.
  3. Texas Professional Ethics Committee, Opinion 705. Texas ethics issues raised by lawyer use of generative AI.
  4. State Bar of California ethics and technology resources, plus 2026 proposed amendments related to artificial intelligence.
  5. Illinois Supreme Court Policy on Artificial Intelligence direct PDF. Court-system policy, effective January 1, 2025, on AI use by litigants, attorneys, judges, judicial clerks, research attorneys, and court staff.
  6. New York State Unified Court System, Part 161. Added March 25, 2026, effective June 1, 2026, on AI technology in court papers.
  7. Administrative Office of the U.S. Courts, 2025 annual report. Establishment of an advisory AI Task Force for the federal judiciary.
  8. Thomson Reuters, 2026 State of the U.S. Legal Market. Includes the 90 percent hourly-billing data point and AI billing-model tension.
  9. LexisNexis, 2024 Investing in Legal Innovation Survey coverage. Client and firm expectation gap around GenAI and outside-counsel billing.
  10. Thomson Reuters, 2026 AI in Professional Services Report. Survey-based account of AI adoption and professional services workflow shifts.
  11. Freshfields and Anthropic, April 23, 2026 partnership announcement, plus Reuters coverage.
  12. Jeffries et al. v. Harcros Chemicals Inc. et al., D. Kan., March 25, 2026. Protective-order ruling extending AI restrictions to all discovery materials.
  13. Sidley, analysis of Morgan v. V2X and Jeffries, and CaseMine, Morgan v. V2X, Inc..
  14. Reuters on Sullivan & Cromwell's AI filing apology, Reuters on former federal prosecutor reprimand, and Reuters on Alabama Supreme Court sanctions.
  15. Damien Charlotin, AI Hallucination Cases Database. Database tracking legal decisions involving AI hallucination issues.
  16. Northwestern Engineering, federal judges AI adoption survey coverage, plus Reuters coverage.
  17. Reuters, May 1, 2026 report on supervisory sanction, Bloomberg Law (Sam Skolnik, April 29, 2026) coverage , plus the April 28, 2026 court order. Federal judge sanctions managing partner Lenden Webb in Hill v. Workday, N.D. Cal., over a junior attorney's AI-assisted filing with a false citation. Reuters reports uncertainty about the source of the false citation, and Thomson Reuters disputed responsibility for the faulty material.
  18. Reuters, Oregon Court of Appeals AI error disclosure and fee-shifting coverage. State appellate ruling on candor when generative AI contributes to fabricated legal content.
  19. Business Insider, April 30, 2026 vendor-attribution coverage. Reporting on a Louisiana filing error dispute involving a named legal AI tool and related audit claims.
  20. Kilpatrick Townsend, May 1, 2026, on protective orders in the age of generative AI. Practice alert summarizing emerging AI-specific protective-order approaches for confidential information.