Clearon AI

AI law and governance intelligence

Author: Clearon AI

  • AI Court Rules Are Becoming Verification Rules

    AI Court Rules Are Becoming Verification Rules

    The next phase of legal AI regulation looks less like a blanket ban and more like a verification record.

    Florida now requires filers to stand behind the existence and accuracy of cited legal authorities. New York now allows AI-assisted court papers without a statewide disclosure requirement, but requires independent verification. The Ninth Circuit just sanctioned lawyers for AI hallucinations and lack of candor. A Mississippi federal judge just removed all four lawyers from a case after both sides filed AI-tainted briefs.

    Different courts. Same message: the tool is not the issue. The filing is.

    The New Rule: Verify First

    Florida's amended Rule 2.515(d)(2), effective June 15, 2026, says that by filing a document, the signer represents that "the legal authorities identified exist and are accurately cited." If that representation is false, sanctions can include reprimand, contempt, striking the filing, dismissal, costs, attorneys' fees, or other relief.

    That is deliberately broader than AI. A lawyer cannot escape the rule by saying a fake case came from a chatbot, a legal research product, an associate, local counsel, a vendor, or a recycled brief.

    New York's Part 161, effective June 1, takes a different route but lands in the same place. It permits AI use in court submissions and does not impose a statewide disclosure mandate. But users must understand the technology's limits and independently ensure that filings do not contain fabricated or fictitious cases, statutes, or other material.

    So the emerging split is not "AI allowed" versus "AI banned." It is disclosure versus no disclosure, with verification underneath both.

    The Sanctions Cases Are Getting Less Patient

    In Lnu v. Blanche, the Ninth Circuit sanctioned two lawyers after filings contained nonexistent cases, misattributed quotations, and serious misreadings of real cases. The court stressed that it was not punishing AI use by itself. It was punishing false filings and the lawyers' later lack of candor.

    That distinction matters. A bad citation is a serious problem. A bad explanation can become the larger one.

    The Mississippi sanctions order in Withers v. City of Aberdeen is even more vivid. The case started as a fee dispute brought by Louisiana lawyer Tom Withers III against Aberdeen, Mississippi. After transfer to the Northern District of Mississippi, the court found hallucinated authorities in filings from both sides.

    The plaintiff side included Louisiana pro hac vice counsel Kathleen M. Wilson and Mississippi local counsel Shauncey Hunter Ridgeway. The defense side included Texas pro hac vice counsel Kathryn Y. Williams and Mississippi local counsel Mark C. McClinton. The court removed all four lawyers from the case, revoked both pro hac vice admissions, barred the two out-of-state lawyers from appearing in the district for two years, imposed monetary sanctions, and referred the order to disciplinary authorities.

    The local-counsel lesson is hard to miss: signing is not clerical. Sponsoring is not ceremonial. If your name is on the filing, the verification problem is yours too.

    California May Be Next

    California is also moving from guidance toward rules. The State Bar has opened public comment on proposed amendments to the Rules of Professional Conduct related to AI, after the California Supreme Court asked it to consider incorporating generative-AI guidance and addressing agentic AI tools.

    That is not a court-filing rule like Florida's or New York's. But it shows the same maturation curve. Soft guidance is starting to harden.

    What To Do Before The Next Filing

    Litigation teams should assume courts will ask a simple question: who checked this?

    • Check the courtwide rule, local rule, judge's standing order, and part rules before filing.
    • Identify whether AI touched research, drafting, editing, factual summaries, record citations, or proposed orders.
    • Verify every cited authority in an authoritative source.
    • Read the authority, not just the citation.
    • Confirm quotations, parentheticals, holdings, procedural posture, and subsequent history.
    • Trace facts and record cites back to the record.
    • Make signing, local, and sponsoring counsel confirm the verification process.
    • If an error is found, correct it quickly and candidly.

    The hardest AI errors are not always fake case names. Sometimes they are real cases used for propositions they do not support. A citation check is not enough; the proposition has to survive too.

    Bottom Line

    Courts are not focused on whether AI helped with the first draft. They want to know whether a lawyer verified the final filing.

    The practical rule is now simple: use the tool if the forum, client, confidentiality obligations, and governing orders allow it. But before anything is filed, someone qualified must verify the authorities, quotations, facts, and record references. And someone with a signature block must be ready to say so.

    For a broader inventory of court rules, sanctions orders, privilege decisions, protective-order restrictions, and tribunal guidance, see Clearon's AI Litigation Practice Tracker.

    Sources

    Sources

  • AI-Assisted Legal Filing Verification Checklist

    AI-Assisted Legal Filing Verification Checklist

    Generative AI can accelerate legal work, but it does not change who is responsible for a court filing. Use this checklist before filing any paper that may contain AI-assisted research, drafting, revision, or analysis.

    It is a practical starting point, not a substitute for the requirements applicable to a particular matter.

    Quick Rule

    Do not file an AI-assisted document until a qualified human has independently verified every legal authority, quotation, factual assertion, record citation, and representation about the proceeding against an authoritative source.

    If any item cannot be checked, stop and resolve it before filing.

    1. Confirm Permitted Use

    • [ ] Identify the AI tools used and the portions of the filing they may have affected.
    • [ ] Confirm the use complies with client instructions, protective orders, confidentiality duties, firm policy, and applicable law.
    • [ ] Check local rules, standing orders, judge-specific practices, and filing instructions for AI restrictions or disclosure requirements.
    • [ ] Confirm no protected information was entered into an unapproved system.

    2. Verify Authorities and Quotations

    • [ ] Open and read every cited authority in an authoritative source.
    • [ ] Confirm each citation identifies the correct authority and current version.
    • [ ] Confirm that each authority supports the precise proposition for which it is cited.
    • [ ] Check precedential status, subsequent history, negative treatment, and applicable citation limits.
    • [ ] Compare every quotation and pinpoint citation against the original source and surrounding context.
    • [ ] Confirm parentheticals, paraphrases, and descriptions accurately characterize the source.

    3. Verify Facts and the Record

    • [ ] Trace every material factual assertion to the record or another permissible source.
    • [ ] Open and verify every record citation, exhibit reference, transcript page, docket entry, and date.
    • [ ] Check names, entities, amounts, calculations, timelines, tables, and summaries.
    • [ ] Distinguish allegations, evidence, findings, holdings, inferences, and argument.

    4. Review and Approve the Final Filing

    • [ ] Have a qualified human independently review the final version.
    • [ ] Check the requested relief, legal standard, jurisdiction, deadlines, service representations, and procedural history.
    • [ ] Check for placeholders, invented citations, inconsistent names, unsupported cross-references, and omitted controlling authority.
    • [ ] Verify appendices, exhibits, certificates, signature blocks, and proposed orders.
    • [ ] Complete any required AI-use disclosures or certifications.
    • [ ] Obtain informed approval from the signing lawyer and responsible supervising, local, or sponsoring counsel.

    Ready to File

    • [ ] Every authority, quotation, fact, and record citation has been independently verified.
    • [ ] The final version has not changed since verification.
    • [ ] Applicable AI rules, client restrictions, and disclosure duties have been satisfied.
    • [ ] The signing lawyer can accurately explain how the filing was prepared and checked.
    • [ ] The team preserved a concise record of who reviewed what and when.

    If an Error Is Discovered After Filing

    • [ ] Stop using the affected material and notify responsible lawyers immediately.
    • [ ] Independently determine the error's full scope and preserve relevant records.
    • [ ] Assess duties to the client, court, opposing counsel, insurer, firm, and disciplinary authorities.
    • [ ] Correct material errors promptly and candidly using the required procedure.
    • [ ] Review other filings or matters that may have used the same workflow.

    Candor after discovery can materially affect the court's response. Recent sanctions orders show that concealment, blame shifting, and repeated inaccuracies can be more damaging than the original mistake.

    Bottom Line

    AI assistance does not reduce the duty of inquiry attached to a court filing. Independent verification, meaningful supervision, signer approval, and prompt candor are still the core requirements.

    For examples of how courts are applying those principles, see Oregon Supreme Court's First AI Hallucination Sanctions Show What Courts Punish Most and Clearon's AI Litigation Practice Tracker.

    Sources

    Sources

  • Oregon Supreme Court’s First AI Hallucination Sanctions Show What Courts Punish Most

    Oregon Supreme Court’s First AI Hallucination Sanctions Show What Courts Punish Most

    The Oregon Supreme Court has issued its first sanctions orders involving court filings attributed to generative artificial intelligence. The significance is not a new AI-specific rule. It is that the court applied familiar duties of accuracy, reasonable inquiry, supervision, and candor to filings containing AI-generated errors.

    They also show that the response after an error is discovered can matter almost as much as the original filing.

    In one case, a self-represented litigant accepted responsibility, fully responded to the court, and received a $500 sanction with permission to submit a corrected filing. In the other, self-represented litigants acknowledged fabricated authorities but submitted more nonexistent cases less than 12 hours after the court's show-cause order. The court struck their filings and dismissed the proceeding.

    The lesson extends well beyond Oregon and beyond self-represented litigants. Courts across the country have imposed monetary sanctions, fee awards, dismissal, disqualification, practice suspensions, bar referrals, mandatory disclosures, and other remedies for filings containing fabricated or materially inaccurate authorities.

    Key Takeaways

    • *The Oregon Supreme Court sanctioned self-represented litigants, not lawyers.* The orders make clear that the obligation not to inject false authority into a proceeding applies to everyone who files.
    • *Courts are punishing the filing, not the mere use of AI.* The recurring issue is whether the signer verified that authorities exist, quotations are accurate, and cases support the propositions asserted.
    • *Candor changes the sanction analysis.* Prompt disclosure, correction, and acceptance of responsibility can mitigate sanctions. Repetition, concealment, blame shifting, and misleading explanations can sharply increase them.
    • *The signature and supervision duties are nondelegable.* Lawyers cannot avoid responsibility by pointing to an associate, contract lawyer, local counsel, vendor, internal AI tool, or firm policy.
    • *Financial penalties are only part of the risk.* Dismissal, disqualification, suspension, bar referral, and mandatory notice to clients and other courts can be more consequential than a fine.

    Oregon's Two New Orders

    The Oregon Supreme Court issued both orders on June 4, 2026, and announced them publicly the next day.

    Aldridge v. Tussing: Repeating the Error Led to Dismissal

    In Aldridge v. Tussing, the relators filed a petition for a writ of mandamus supported by nonexistent cases and fabricated quotations. The court ordered them to verify every citation under penalty of perjury, explain the errors, and show cause why sanctions should not be imposed.

    The relators acknowledged that fabricated authorities had been included and attributed the errors to a service called LegalAI. But less than 12 hours after receiving the show-cause order, they submitted another declaration containing at least four nonexistent cases.

    The court struck the petition and the show-cause response and dismissed the proceeding. Its explanation was direct: injecting false precedent undermines the integrity of a proceeding, and repeating the conduct in response to a show-cause order warrants a meaningful sanction.

    Witkin v. McGreevy: Acceptance of Responsibility Mitigated the Result

    In Witkin v. McGreevy, a self-represented respondent filed a response containing fictitious authorities and inaccurate legal arguments generated with AI. After receiving a show-cause order, the respondent addressed each fabricated authority, explained the AI use, and accepted responsibility.

    The court still struck the filing and imposed a stipulated $500 sanction. But it allowed the respondent to file a corrected response, provided that any revised filing certified that every cited, quoted, or paraphrased source of law had been verified to exist.

    The contrast is the point. Both filings contained false authority. The litigant who responded candidly and corrected course received a limited financial sanction and another opportunity to file. The litigants who repeated the misconduct after a direct warning lost the proceeding.

    Oregon Already Had a Six-Figure Warning for Lawyers

    The state-court orders arrived only months after a separate federal case from Oregon demonstrated how large the financial exposure can become.

    In Couvrette v. Wisnovsky, the U.S. District Court for the District of Oregon addressed summary-judgment briefing containing nonexistent cases and fabricated quotations. The court struck the briefing, dismissed the plaintiffs' claims with prejudice, imposed monetary sanctions, and awarded the opposing parties $94,704.38 in fees and costs directly resulting from the briefing.

    The March 2026 fee order allocated the award between lead counsel and local counsel. The local lawyer was ordered to pay 15% after the court found that he had failed to meaningfully participate despite serving as required local counsel for a lawyer admitted pro hac vice. The lead lawyer was ordered to pay the remaining 85%. The court also required local counsel to attach the sanctions order to future motions in which he sought to sponsor pro hac vice counsel in the district.

    Together with the court's earlier monetary sanctions, the financial consequences exceeded $110,000. More important, the case shows that local counsel and supervising lawyers cannot treat their role as providing a name, bar number, or signature while leaving the substance unchecked.

    The Sanctions Menu Is Expanding

    The early headline case was Mata v. Avianca. In 2023, the Southern District of New York imposed a $5,000 penalty after lawyers submitted fabricated cases and fake opinions generated by ChatGPT and continued to defend the material after its authenticity was questioned. The court also required notice to the client and to judges falsely identified as authors of the fabricated opinions.

    Since then, courts have used a much broader range of remedies:

    • *Sanctions for every signer:* In Wadsworth v. Walmart, the District of Wyoming imposed $5,000 in combined sanctions and revoked one lawyer's pro hac vice admission after a filing cited eight nonexistent cases. The court treated the duty to ensure a filing is supported by existing law as nondelegable.
    • *A $10,000 appellate sanction:* In Noland v. Land of the Free, L.P., the California Court of Appeal imposed $10,000 in sanctions after an appellate brief contained fabricated quotations and other inaccurate authority. The published opinion warned that lawyers must personally read and verify the authorities they cite.
    • *Disqualification and bar referrals instead of a fine:* In Johnson v. Dunn, the Northern District of Alabama publicly reprimanded and disqualified three lawyers, required broad distribution of the sanctions order, and referred the matter to licensing authorities. The court concluded that a fine and public embarrassment were insufficient deterrents.
    • *Suspension from appellate practice:* In Lnu v. Blanche, the Ninth Circuit imposed $2,500 sanctions on each of two lawyers, suspended both from practice before the circuit for six months, required notice to clients, opposing counsel, judges, and the lawyers' firm, and imposed a two-year AI-use disclosure and verification requirement. The court emphasized that the more serious discipline resulted from repeated failures of candor after the errors came to light.
    • *Both sides sanctioned:* In Withers v. City of Aberdeen, the Northern District of Mississippi sanctioned and removed all four lawyers after filings from both sides contained hallucinated authorities. The two out-of-state lawyers were also barred from appearing in the district for two years.

    These cases do not establish a uniform sanctions schedule. They show that courts are calibrating remedies to the conduct, the harm, the lawyer's role, prior warnings, remediation, and candor.

    What Courts Appear to Punish Most

    The orders point to several aggravating factors.

    Filing Without Reading the Authorities

    Checking whether a case name exists is not enough. Courts expect lawyers to read the authority and confirm that quotations are accurate, procedural posture is correctly described, and the case actually supports the proposition asserted.

    The Ninth Circuit drew a useful distinction between fabricated authorities and subtler inaccuracies. A fake case may be easy to detect. A real case mischaracterized by an AI tool may be more dangerous because it can survive a superficial citation check.

    Treating Signatures as Administrative

    Courts repeatedly reject the idea that a lawyer can lend a signature without assuming responsibility for the filing. That principle reaches supervising lawyers, local counsel, partners, and lawyers whose names appear in signature blocks even when they did not personally use AI.

    Repeating or Concealing the Problem

    An inaccurate filing creates a serious problem. Misleading the court about how it happened, replacing fake citations without disclosing the original problem, or submitting additional fabrications after a warning creates a larger one.

    The Oregon Supreme Court's two orders make the distinction unusually clear. So does the Ninth Circuit's order in Lnu, where the court said lesser sanctions might have been warranted if the lawyers had promptly disclosed the AI use and accepted responsibility.

    Relying on a Policy Without Enforcing It

    Having a written AI policy is not a defense when actual workflows allow unverified material to reach the court. Policies must identify who checks citations, quotations, propositions, facts, and record references before filing. They also need a clear escalation process when an error is discovered.

    What Litigation Teams Should Do Now

    For a practical pre-filing workflow, use Clearon's AI-Assisted Legal Filing Verification Checklist.

    • Require verification of every citation, quotation, factual assertion, and record reference against the original source before filing.
    • Make the signing lawyer responsible for confirming that verification occurred.
    • Apply the same controls to work prepared by associates, contract lawyers, local counsel, clients, vendors, and AI tools.
    • Preserve enough information about the drafting and verification process to explain it accurately if questioned.
    • When an error is discovered, notify the court and opposing counsel promptly, identify the nature and source of the error, and propose a concrete correction.
    • Do not describe a fabricated authority as a typographical error or silently swap in a different citation.
    • Train lawyers to detect mischaracterizations of real cases, not only nonexistent citations.
    • Treat show-cause orders as urgent risk events requiring independent review and senior oversight.

    Bottom Line

    The Oregon Supreme Court's first AI-related sanctions orders do not ban AI. They show how courts protect the integrity of filings when AI-assisted work reaches the docket without real verification.

    The technology may explain how a false citation appeared, but it does not change who is responsible for filing it. Courts are increasingly focused on three questions: Was the filing verified? Who accepted responsibility for it? What happened after the error was discovered?

    The emerging sanctions record suggests that the last question can determine whether the result is a correctable mistake, a monetary penalty, a lost case, or a career-level disciplinary problem.

    For the broader court-rule landscape, see Federal Court AI Orders Are Splitting Into Clear Patterns and Clearon's AI Litigation Practice Tracker.

    Sources

    Sources

  • Legal AI Workflows: A Governance Checklist for Legal Teams

    Legal AI Workflows: A Governance Checklist for Legal Teams

    Legal AI succeeds or fails at the workflow level.

    A model may look impressive in a demonstration and still create unacceptable risk once it touches client files, institutional knowledge, contract data, legal research, or work product.

    The practical question is not simply whether an AI tool is accurate. It is whether the full workflow around the tool is governable, reviewable, and defensible.

    Start with the workflow, not the model

    This checklist gives law firms and legal departments a structured way to evaluate and manage AI-assisted workflows before and after deployment.

    A usable workflow definition should identify:

    • the task and intended outcome;
    • the people permitted to use the workflow;
    • the data the tool may receive or retrieve;
    • the decisions or documents the output may influence;
    • the required level of human review; and
    • the person accountable for the final result.

    This step prevents a narrow tool approval from quietly becoming permission for much broader uses.

    1. Assign an owner and risk tier

    Every production workflow needs a named business owner and a defined risk level. The owner should be responsible for approving changes, monitoring performance, and escalating incidents.

    Risk tiers should reflect the consequences of error and the sensitivity of the information involved. A tool that summarizes public regulations presents a different risk profile from one that reviews privileged investigation materials or drafts a filing.

    Higher-risk workflows should receive more testing, tighter access controls, stronger documentation, and more frequent review.

    2. Control confidential and privileged information

    Legal teams should determine exactly what happens to prompts, uploaded documents, retrieved materials, outputs, and usage logs. The answer may differ across consumer, enterprise, API, and privately hosted versions of the same product.

    Key diligence questions include:

    • Is submitted data used to train or improve models?
    • How long is data retained, and can retention be configured?
    • Which vendor personnel and subprocessors can access the data?
    • Where is the data stored and processed?
    • Can the organization enforce matter-level permissions and ethical walls?
    • What happens to data after termination?

    ABA Formal Opinion 512 emphasizes that lawyers using generative AI must consider duties including competence and confidentiality. A workflow should not accept sensitive legal information merely because the interface makes uploading it easy.

    3. Govern context, permissions, and retrieval

    For many legal workflows, the most valuable capability is not the model itself. It is access to the organization’s own documents, precedents, policies, and prior work.

    That creates a permissions problem. An AI system should not reveal information a user could not otherwise access. Legal teams should test whether the retrieval layer respects document permissions, matter boundaries, client restrictions, retention rules, and information barriers.

    This is why institutional knowledge and governed context are becoming central to legal AI infrastructure.

    4. Define required human review

    “Human in the loop” is not a complete control unless the organization defines what the human must actually do.

    For each workflow, specify:

    • who reviews the output;
    • what sources or underlying documents must be checked;
    • which factual, legal, citation, numerical, or contractual elements require verification;
    • what level of confidence or error requires escalation; and
    • whether the output may be sent externally before review.

    Review should match the use. A lawyer approving a court filing needs a different process from a team using AI to create a first-pass internal summary.

    5. Test the complete workflow

    Testing should use realistic examples and measure the complete workflow, not just isolated model answers. That includes the source documents, retrieval system, prompt or interface, output, reviewer actions, and final downstream use.

    A practical evaluation set should include routine matters, difficult edge cases, incomplete information, conflicting documents, and attempts to cross permission boundaries. Teams should record both quality failures and process failures.

    NIST’s AI Risk Management Framework organizes risk work around the functions Govern, Map, Measure, and Manage. That structure is useful for legal workflows because it treats evaluation and monitoring as continuing responsibilities, not a one-time procurement exercise.

    6. Review vendor terms and operational dependencies

    Legal and procurement teams should evaluate the contract around the workflow, including:

    • data-use and confidentiality commitments;
    • security obligations and incident notification;
    • subprocessors and model providers;
    • indemnities, liability limits, and warranty disclaimers;
    • audit rights and documentation;
    • service changes and model substitutions;
    • data export, portability, and termination assistance; and
    • the organization’s ability to preserve records or satisfy legal holds.

    Workflow dependence matters too. As frontier-model providers move into government legal workflows through specialized partners, buyers need to understand which party controls each layer and what happens if one layer changes.

    7. Create records that make review possible

    A defensible workflow should produce enough documentation to reconstruct important decisions. Depending on the use case, that may include the tool and version used, source materials, prompts or configured instructions, output, reviewer, corrections, approval, and date.

    Not every low-risk use requires a permanent prompt archive. The organization should make a deliberate retention decision based on legal obligations, business need, risk, and discoverability rather than allowing the product’s default settings to decide.

    8. Monitor changes after launch

    AI workflows can change even when the organization does not intentionally redesign them. Vendors update models, retrieval systems, interfaces, terms, and safety controls. Internal data sources and permissions also change.

    Monitoring should include:

    • periodic quality and permission testing;
    • review of incidents, overrides, and user feedback;
    • tracking vendor and model changes;
    • reviewing whether the workflow is being used beyond its approved purpose; and
    • reassessing the risk tier when the workflow expands.

    A practical approval record

    Before launch, the approving team should be able to answer these questions in writing:

    1. What exact workflow are we approving?
    2. Who owns it?
    3. What information may it access?
    4. What can go wrong, and who could be affected?
    5. What testing supports the decision?
    6. What human review is required?
    7. What records will we keep?
    8. How will we detect changes and failures?
    9. When will we review the approval again?

    The Clearon AI takeaway

    Legal AI governance should be concrete enough to operate. Policies matter, but the durable control point is the individual workflow: its owner, data, permissions, testing, human review, contract, records, and monitoring.

    The legal AI market is increasingly competing at this workflow layer. The teams that benefit most will be the ones that make those workflows useful without making them unaccountable.

    Related Clearon AI analysis

    Primary sources

  • The OpenAI Copyright MDL Has Become a Data-Governance Case

    The OpenAI Copyright MDL Has Become a Data-Governance Case

    Current through June 9, 2026.

    The OpenAI copyright multidistrict litigation matters because it has already produced claim-specific rulings and unusually consequential discovery disputes involving model-development records, privilege, and large sets of ChatGPT conversation logs.

    No court has entered a final judgment on whether OpenAI's model training is fair use. The litigation still gives companies a practical warning: ordinary decisions about retention, deletion, vendor terms, and internal records can become central evidence in a major lawsuit.

    Where the MDL stands

    The Judicial Panel on Multidistrict Litigation created MDL No. 3143 on April 3, 2025, transferring four actions to the Southern District of New York for coordinated or consolidated pretrial proceedings. Additional actions have since been transferred.

    The consolidated cases are not identical. They include claims by authors, newspapers, publishers, and other rights holders involving model training, allegedly infringing outputs, contributory infringement, and provisions of the Digital Millennium Copyright Act concerning copyright-management information.

    An MDL coordinates overlapping pretrial work, but it does not turn every plaintiff’s theory into one claim or decide that any claim will succeed.

    The case has moved beyond consolidation

    In a December 15, 2025 ruling involving Ziff Davis, the court allowed several claims to proceed past a motion to dismiss, including contributory-infringement and certain DMCA copyright-management-information claims. It dismissed other theories, including the claim that disregarding robots.txt instructions constituted circumvention of an effective technological measure. The ruling did not decide liability, but it showed that the litigation will turn on specific claims, facts, and model behavior rather than one sweeping answer about AI and copyright.

    Discovery has become just as important as the pleading rulings:

    • In January 2026, Judge Stein upheld orders requiring production of a sample of 20 million de-identified ChatGPT conversation logs.
    • In March 2026, Magistrate Judge Wang granted in part a request involving additional reservoirs of 78 million and 10 million logs, subject to a protocol addressing de-identification and user privacy.
    • In May 2026, the court ordered OpenAI to produce deposition testimony from separate litigation involving Sam Altman, Greg Brockman, Satya Nadella, and an OpenAI corporate designee after finding the narrowed request relevant and proportional.
    • In February 2026, Judge Stein set aside a magistrate judge’s ruling that OpenAI had waived attorney-client privilege over certain 2022 communications concerning the Books1 and Books2 datasets and Library Genesis.

    Those developments do not establish infringement. They do show what an AI copyright case can demand once it reaches coordinated discovery.

    The clearest governance lesson is about data

    The MDL has made retention and discovery policy part of the copyright-risk discussion.

    For enterprise users, the immediate lesson is not that their prompts will necessarily become evidence in this case. It is that vendor data practices, contractual promises, litigation holds, and court-ordered discovery can interact in ways that are easy to overlook during procurement.

    Legal, privacy, security, and procurement teams should ask:

    • What prompts, outputs, metadata, and logs does the vendor retain?
    • Which retention settings are defaults, and which require an enterprise plan or approval?
    • Can ordinary deletion schedules be suspended by a legal hold, court order, or regulatory obligation?
    • What data may be used to improve models, and what requires an affirmative opt-in?
    • Which internal repositories or systems can the tool access?
    • Can the company preserve its own audit trail without collecting more sensitive content than it needs?

    OpenAI states that business-product and API data are not used to train its models by default. It also states that API inputs and outputs are generally removed after 30 days unless legal requirements require retention, and that eligible customers may request zero-data-retention controls for qualifying endpoints. Those are meaningful controls, but buyers still need to understand exceptions, product-specific settings, and what happens when litigation or another legal obligation changes the ordinary retention rules.

    Procurement terms need operational follow-through

    Contract review remains important, but contract language alone is not a governance program.

    Buyers should evaluate vendor representations about training data, output restrictions, indemnity, retention, confidentiality, security, and cooperation during disputes. They should also make sure internal settings and workflows match the negotiated terms.

    A contract may promise strong business-data protections while employees continue using consumer accounts. A zero-retention option does little if it was never enabled for the relevant endpoint. A restriction on confidential data will not help if the organization has no practical rule for deciding which repositories or matters an AI coding or research tool may access.

    Code-generation controls remain useful, but they are a separate issue

    AI-generated code presents a related but distinct set of copyright and open-source-license risks. Companies should not treat the OpenAI MDL as proof that generated code infringes or that any particular compliance control is legally required.

    Still, software companies have practical reasons to treat AI-generated code like third-party code until it is reviewed:

    • use approved enterprise coding tools and accounts;
    • enable public-code matching or reference features where available;
    • require human review for long or unusually specific generated snippets;
    • scan generated code for open-source and snippet-level risks before release;
    • document remediation of flagged code; and
    • restrict sensitive repository and file access.

    GitHub documents a policy that can block Copilot suggestions matching publicly available code or allow them with code references. Cursor states that Privacy Mode enables zero data retention for model providers, while also explaining that some code data may still be stored to provide additional features and that codebase indexing involves uploads for embedding. These controls address different risks. Public-code matching is not a confidentiality control, and privacy settings are not license-clearance tools.

    What legal teams should do now

    1. Map which AI products are in use, including consumer accounts and tools embedded in other software.
    2. Record the actual retention, training, access, and deletion settings for each approved product.
    3. Reconcile vendor contracts with technical configuration and employee practice.
    4. Decide what AI-use records are genuinely needed for audit, compliance, or litigation readiness.
    5. Apply separate controls for confidential data, generated code, external-facing content, and high-risk decisions.
    6. Revisit the program when vendor terms, product settings, or major court rulings change.

    What to watch next

    The most consequential developments will be rulings that clarify training-copy theories, output-based claims, fair use, DMCA liability, and the permissible scope of discovery. Additional transfer orders also matter because they determine which disputes enter the coordinated proceeding.

    For enterprise users, the discovery fights may be as instructive as the eventual merits rulings. They show that AI governance is not limited to deciding whether employees may use a tool. It includes knowing what the tool retains, what the company can control, and what may have to be preserved or produced when litigation begins.

    Sources

  • Federal Court AI Orders Are Splitting Into Clear Patterns

    Federal Court AI Orders Are Splitting Into Clear Patterns

    Current snapshot: June 4, 2026.

    Federal courts are not moving toward one uniform AI rule. They are moving toward a patchwork. Some judges prohibit AI use in filings. Some require disclosure or certification. Others simply remind lawyers that Rule 11, candor, confidentiality, and sanctions rules still apply.

    That makes the practical rule simple: check the forum before filing, check the judge before drafting, and verify every AI-assisted citation, quotation, factual assertion, and legal proposition before it goes to court.

    1. No-use or near no-use orders

    The strictest orders do not merely require disclosure. They prohibit AI use for filings or memoranda.

    Judge Christopher A. Boyko of the Northern District of Ohio has a standing order stating that no attorney or pro se party may use AI in preparing any filing submitted to the court. Judge Sharon Johnson Coleman of the Northern District of Illinois similarly states in her standing requirements that parties may not use AI to draft memoranda or as authority to support motions.

    These orders are still the minority approach, but they matter because they show that some courts view AI-assisted drafting itself as the risk, not just unverified AI output.

    2. Disclose if AI was used

    The more common approach is disclosure. These rules do not necessarily forbid AI. They require the filer to say when AI was used and sometimes to identify the tool or the AI-generated portions.

    The Northern District of Texas now requires a brief prepared using generative AI to disclose that fact on the first page under the heading “Use of Generative Artificial Intelligence.” If the required disclosure is absent, the filing operates as a certification that no part of the brief was prepared using generative AI.

    Judge Michael M. Baylson of the Eastern District of Pennsylvania requires a clear factual statement disclosing AI use in papers filed in cases assigned to him and a certification that all citations to law or the record have been verified. The Southern District of California Bankruptcy Court uses a disclosure and certification form for generative AI use in pleadings, motions, and papers.

    3. Certify or verify the work

    Some courts focus less on whether AI was used and more on whether a human verified the final filing.

    The District of Nebraska’s local rule requires a certificate stating either that no generative AI was used or that a human verified all generated text, including citations and legal authority. The District of Kansas reminds lawyers and pro se litigants that AI-assisted filings remain subject to existing duties of candor and accuracy and warns that the court may strike filings, impose sanctions, or require sworn AI-use statements.

    This bucket is likely to grow because it fits comfortably with the existing professional-responsibility framework: AI can assist, but it cannot be the final authority.

    4. Treat AI output as an unverified source

    Some orders frame the problem as source reliability. The District of Hawaii’s General Order 23-1 treats AI-generated material as an unverified source and requires a declaration when counsel or a pro se party submits material generated by an unverified source.

    That framing is useful. It avoids treating AI as uniquely mysterious and instead places it beside other unverified material: useful as a lead, not good enough as filed authority unless checked.

    But Hawaii’s approach also creates a line-drawing problem. The order defines unverified sources to include AI-generated briefs and memoranda, along with online briefs or memoranda drafted by paid writers that are not tailored to a specific case. The risk is that lawyers may now have to decide not only whether they used AI, but whether a particular research output, template, summary, or purchased work product counts as an “unverified source.”

    The last paragraph of the order matters because it carves out ordinary legal research. The court says the order does not affect basic research tools such as Westlaw, Lexis, or Bloomberg, and that no declaration is required when the sources can be found on those tools. That is a sensible safe harbor for conventional citation checking, but it also raises practical questions as legal research platforms add generative AI features. If a lawyer uses a research platform’s AI summary, answer, or drafting aid, is the source the underlying case law, the research database, or the AI-generated synthesis?

    For lawyers, the safest reading is narrow: a source is not verified merely because it appeared inside a trusted platform. The underlying authority still has to be located, read, and checked. Hawaii’s final paragraph reduces friction for traditional legal research, but it should not be read as a blanket blessing for every AI-assisted feature embedded inside a legal research product.

    5. Protect confidential and proprietary information

    Other orders focus on confidentiality. Judge Stephen Vaden of the Court of International Trade requires disclosure when a filing contains text drafted with generative AI and a certification that the AI use did not disclose confidential or business proprietary information to an unauthorized party.

    This is the piece many lawyers miss. AI orders are not just about fake cases. They are also about what happens when privileged, confidential, sealed, trade secret, business proprietary, health, financial, or export-controlled information is entered into a tool that may store, train on, or transmit user input.

    6. Proposed Federal Rule of Evidence 707

    The most important federal rulemaking item is not a filing-disclosure rule. It is proposed Federal Rule of Evidence 707, which would address machine-generated evidence. The pending rules materials place proposed new Evidence Rule 707 on the December 1, 2027 track.

    That issue is different from AI-assisted drafting. Filing orders ask whether lawyers verified what they submitted. Evidence rules ask whether machine-generated evidence is reliable enough to be admitted.

    What lawyers should do now

    • Check district-wide local rules and judge-specific standing orders before drafting or filing.
    • Do not assume a general Rule 11 review is enough if the judge requires a separate disclosure or certificate.
    • Keep enough internal record of AI use to answer a court question without waiving privilege or exposing mental impressions unnecessarily.
    • Do not enter confidential, privileged, sealed, business proprietary, trade secret, protected health, financial, or export-controlled information into public AI tools.
    • Verify every citation, quotation, factual assertion, record reference, and legal proposition outside the AI tool.

    Help us keep the tracker current

    Clearon AI is tracking federal and state court AI orders, standing orders, local rules, protective-order language, and sanctions decisions. If you have found a court order on AI that is not reflected here, please send it through the Contact page.

    The most helpful submissions include the court, judge, date, docket number or rule number, a link to the order or PDF, and a short note on what the order requires. We will verify submissions against primary court sources before adding them to the tracker.

    Primary sources checked

  • Trump’s New AI Executive Order Turns Frontier Models Into a Cybersecurity Priority

    Trump’s New AI Executive Order Turns Frontier Models Into a Cybersecurity Priority

    President Donald Trump signed a new artificial intelligence executive order on June 2, 2026, and the center of gravity is clear: cybersecurity, critical infrastructure, and the most capable frontier models.

    The order, titled "Promoting Advanced Artificial Intelligence Innovation and Security," does not create a broad AI licensing regime. It expressly says it should not be read to authorize mandatory preclearance, licensing, or permitting for the release of new AI models. But it still gives the federal government a more formal role near the front end of model release: identifying high-capability frontier models and arranging early, secure access before those models are shared more widely with trusted partners.

    This is not a general-purpose AI rulebook. It is a national-security and cybersecurity order. Advanced AI is treated as both a defensive asset and a possible accelerant for cyber risk.

    What the Order Does

    Four pieces do most of the work.

    First, it directs federal cybersecurity leaders to prioritize AI-enabled cyber defense across national security systems, Department of War systems, and civilian federal government systems. Within 30 days, CISA, in consultation with OMB and other White House cyber and national-security officials, is directed to issue binding operational directives and other guidance where appropriate.

    Second, it creates an AI cybersecurity clearinghouse. Treasury, the Department of War through NSA, DHS through CISA, and the National Cyber Director are directed to form a voluntary clearinghouse with AI companies and critical-infrastructure operators. The goal is to coordinate vulnerability scanning, validation, remediation, and patch distribution.

    Third, it directs federal officials to develop a classified benchmarking process for advanced cyber capabilities in AI models. That process will help determine when an AI model should be treated as a "covered frontier model" under the order.

    Fourth, it calls for a voluntary framework under which AI developers can work with the federal government to determine whether models under development meet the covered-frontier-model threshold. Developers may then give the government secure access to covered models, with confidentiality, cybersecurity, insider-risk, intellectual-property, and nondisclosure protections, for up to 30 days before release to other trusted partners.

    That is the legal story for AI companies. The order does not say, "submit your model for approval." It says the federal government wants a structured way to spot advanced cyber capability, review certain models before broader trusted-partner release, and coordinate deployment where national cybersecurity interests are implicated.

    Why It Matters

    The order keeps the administration's pro-innovation posture, but it also shows where federal oversight is likely to harden first. Not around generalized consumer AI rules, at least not here. Around cybersecurity, national security, critical infrastructure, and model capability thresholds.

    That should get the attention of several groups.

    AI developers will need to assess whether their model-development processes can support secure government engagement without compromising trade secrets, release timelines, or customer commitments. Even a voluntary framework can become practically significant when major labs, cloud platforms, federal contractors, or critical-infrastructure vendors are involved.

    Federal contractors and regulated entities should watch the CISA and OMB guidance that follows. The order directs action on federal systems, but it also points to access for state and local authorities and operators of critical infrastructure, including rural hospitals, community banks, and local utilities. That suggests downstream cybersecurity expectations may reach beyond Washington.

    Legal and compliance teams should also pay attention to the documentation burden. If a model could plausibly fall within a classified benchmarking process, companies will want a defensible internal record of model capabilities, cyber-risk testing, access controls, deployment plans, and third-party release decisions.

    The Frontier-Model Piece

    "Covered frontier model" may be the most consequential phrase in the order.

    The order directs federal officials to build a classified benchmarking process to assess advanced cyber capabilities and identify the threshold for that designation. The designation decision is assigned to NSA leadership in consultation with the National Cyber Director, the Assistant to the President for Science and Technology, CISA, and Department of War representatives.

    That approach keeps the most sensitive capability assessment out of public view. It also means companies may never get a clean public checklist for what makes a model covered. They may instead be dealing with a government-facing process built around classified benchmarks, agency judgment, and secure communications with federal officials.

    From a legal-risk perspective, this creates several practical questions:

    • How will a company determine whether to initiate voluntary engagement?
    • What internal evidence should support the company's view that a model is or is not likely to meet the threshold?
    • How will pre-release access be governed contractually?
    • How will intellectual property, model weights, system prompts, evaluations, logs, and vulnerability findings be protected?
    • What happens if a company disagrees with the government's assessment?

    The order does not answer those questions. It starts the process that will create them.

    Not a Licensing Regime, But Not Nothing

    The anti-licensing language is not throwaway. It appears designed to reassure industry that the administration is not recreating a mandatory pre-release approval system for frontier AI.

    But legal teams should not mistake that reassurance for irrelevance. Voluntary frameworks can still shape market expectations, procurement preferences, liability arguments, insurance underwriting, and board-level risk controls. If the federal government creates a recognized process for secure early access and frontier-model cyber benchmarking, companies that ignore it may eventually have to explain why.

    That is especially true in sectors where AI models are deployed into cybersecurity products, vulnerability detection, incident response, financial services, health systems, utilities, or other sensitive environments.

    The Altman-Musk Divide

    The industry's early reaction shows why that anti-licensing language was probably necessary.

    OpenAI has publicly embraced the final order's basic structure. Sam Altman reportedly said the order "gets the balance right," and OpenAI's chief global affairs officer, Chris Lehane, framed the issue as one for democratic institutions, technical experts, and public stakeholders. That fits OpenAI's broader posture: accept government-informed safety testing and standards for high-capability systems, while resisting a regime that turns every major model release into a permission slip.

    Elon Musk and xAI appear to be in a different, more skeptical lane. Axios reported that Musk, along with Meta's Mark Zuckerberg and White House AI adviser David Sacks, spoke with President Trump before an earlier version of the order was delayed. The final version that emerged was narrower: voluntary rather than mandatory, built around a 30-day pre-release access window, and explicit that it does not authorize preclearance, licensing, or permitting for new AI models.

    That does not mean xAI is rejecting federal testing. In May, xAI, Google, and Microsoft agreed to give the federal AI Safety Institute, now CAISI, access to models for security testing before release. The better reading is narrower: xAI appears willing to participate in government model testing, while the Axios reporting suggests Musk was part of the industry pushback against a heavier pre-release review regime.

    For legal teams, that distinction is useful. The frontier labs are not simply dividing into "regulated" and "unregulated" camps. They are drawing boundaries around the legal character of the process: voluntary cooperation, safety benchmarking, and secure government access on one side; mandatory licensing, public approval gates, and open-ended release delays on the other.

    Enforcement Against AI-Enabled Cybercrime

    The order also directs the Attorney General to prioritize enforcement against people who use AI to unlawfully access or damage computer systems, steal data, or facilitate other crimes. It specifically references federal computer crime and fraud statutes, including 18 U.S.C. 1028, 1030, and 1343.

    That section is short, but it does some work. It frames AI-enabled cyber misuse as an enforcement priority rather than a wholly new legal category. The administration appears to be saying that existing criminal laws already reach many AI-assisted cyber offenses, and DOJ should treat AI use as a reason to prioritize those cases.

    Companies should read that as a controls issue. AI agents, autonomous scanning tools, security research workflows, and employee use of AI in technical environments all need clear authorization boundaries. A tool that accelerates defensive work can also create evidence problems if it is used the wrong way.

    What To Watch Next

    The next 30 to 60 days will tell us more than the headline did.

    CISA guidance and any binding operational directives will show how federal agencies are expected to use AI-enabled cyber tools and whether contractors will see new expectations in security programs. Treasury, NSA, DHS, and the National Cyber Director's clearinghouse work will show how much private-sector coordination the government can realistically achieve. The classified benchmarking process will determine whether "covered frontier model" becomes a narrow national-security category or a broader marker for advanced AI cyber capability.

    The order is not a comprehensive AI law. It is not a privacy law, a copyright law, or a civil-liability framework. It does show where federal AI governance may harden first: cybersecurity.

    For AI companies and the organizations that rely on them, the practical takeaway is direct: model capability, cybersecurity readiness, release governance, and critical-infrastructure impact now belong in the same review process.

    Editorial Notes

    Suggested dek: The June 2 order does not create a mandatory AI licensing system, but it does create a federal path for frontier-model cyber benchmarking, secure early access, and AI-enabled cyber defense.

    Suggested social: The new AI executive order is not a broad licensing regime. It is something more targeted: a cybersecurity and national-security framework for frontier-model capability, pre-release access, and critical infrastructure defense.

    Related follow-ons:

    • What AI companies should document before engaging with the voluntary frontier-model framework.
    • Why CISA's next AI guidance may matter more than the executive order itself.
    • How AI-enabled cybercrime enforcement could affect companies using autonomous agents.

    Sources

  • Weekend Legal AI Roundup: What lawyers should catch up on Monday

    Weekend Legal AI Roundup: What lawyers should catch up on Monday

    The weekend did not produce a flood of legal AI news, but it did leave a few developments worth carrying into Monday.

    The biggest late-Friday carryovers were a new statewide Florida court rule on AI-assisted filings and a clear Big Law signal that Kirkland & Ellis wants to build more of its own AI infrastructure instead of renting all of it.

    There was also a narrower but still relevant enforcement development: the FTC has begun rolling out its TAKE IT DOWN Act enforcement channel. That is not the lead enterprise-AI story of the week, but it belongs on the synthetic-media and platform-obligations watchlist.

    Here are the items worth catching up on before the week gets moving.

    Florida put a statewide rule around AI-assisted court filings

    The Florida Supreme Court issued a May 28 administrative order and companion rule amendments replacing circuit-by-circuit AI disclosure requirements with a single statewide standard.

    The new framework puts the emphasis on something much more practical than generic AI panic: lawyers remain responsible for the existence and accuracy of cited legal authorities, and courts have express sanctions language to back that up. The change takes effect June 15, 2026.

    This is one of the cleaner signs yet that courts are moving from scattered warnings to operational AI-use rules. Florida is not banning AI. It is doing something more durable: turning verification, supervision, and filing discipline into a statewide workflow expectation.

    That matters to litigators, supervising partners, and in-house teams that review outside-counsel AI policies.

    The practical Monday-morning takeaway is simple: if your team uses AI in drafting or cite-checking, this is a good week to confirm who verifies authorities, how that verification gets documented, and whether your written AI-use guidance still sounds abstract when the court rule now sounds concrete.

    Kirkland is spending like AI infrastructure is now a strategic asset

    Reuters reported on May 28 that Kirkland & Ellis plans to spend $500 million over the next three to four years building a proprietary AI platform, with $100 million expected in 2026 alone.

    The report says the firm will still license some outside tools, but the headline point is hard to miss: one of the world’s largest firms appears to think the long game is not just buying AI products, but owning more of the workflow layer itself.

    This is a stronger market signal than yet another vendor demo or partnership announcement. If elite firms are willing to treat AI as internal infrastructure, that sharpens the build-versus-buy question for everyone else.

    It also reinforces a trend Clearon has been tracking for weeks: competitive advantage may sit less in raw model access and more in governed context, firm-specific knowledge, integration, and control.

    The practical Monday-morning takeaway is that law firms and legal departments evaluating AI tools should ask a more serious architecture question than whether a feature looks useful. The better question is which capabilities belong in a vendor stack, which should sit behind internal controls, and what gets harder to unwind once workflow, precedent, and usage data start concentrating in one place.

    The FTC’s TAKE IT DOWN rollout is not a core enterprise-AI story yet, but it is worth watching

    The FTC announced that it has begun enforcing the TAKE IT DOWN Act and launched a complaint channel for failures to honor valid removal requests involving nonconsensual intimate imagery, including AI-generated abuse scenarios described in the agency’s rollout.

    This is not the lead item for most law firms or in-house AI governance teams, but it is a real compliance signal for platform operators, trust-and-safety counsel, and anyone tracking synthetic-media obligations.

    It also shows how fast AI-specific legal questions can get folded into ordinary enforcement machinery once a law is in place.

    The practical Monday-morning takeaway is that if your organization operates a platform, moderation workflow, or user-generated-content channel, this is a useful prompt to review takedown intake, escalation paths, and whether synthetic-media response procedures are documented well enough to survive regulator scrutiny.

    What to watch this week

    Watch whether Florida’s court-rule move gets copied elsewhere, and whether more legal organizations start talking openly about AI as infrastructure rather than software.

    The recurring question is getting clearer: who controls the workflow, who verifies the work, and where responsibility actually sits once AI is inside legal operations.

  • Legal AI Roundup: This Week’s Pressure Points

    Legal AI Roundup: This Week’s Pressure Points

    This week's legal AI story was not the volume of headlines. It was the sharper pressure points underneath them.

    Copyright plaintiffs kept pushing AI disputes deeper into court. The FTC reminded the market that fake AI capability claims can become an enforcement problem quickly. And on the legal-workflow side, vendors kept leaning into a more practical message: the value is not only model output, but whether AI can operate inside governed institutional context.

    Here are the developments lawyers should know before the weekend.

    CNN sues Perplexity over alleged copying and distribution of news content

    CNN sued Perplexity in the Southern District of New York, alleging that the company unlawfully crawled, scraped, copied, and distributed more than 17,000 CNN stories, videos, images, and other works to power its products. The complaint also includes trademark allegations tied to supposed affiliation and premium-access claims.

    This pushes the publisher-AI conflict further into answer-engine behavior, output substitution, and source-rights questions tied to real-time content use. It also appears to be the first AI copyright case brought by a television network, which broadens the plaintiff set beyond newspapers, authors, and music-rights holders.

    The practical takeaway is that legal teams evaluating answer-engine or retrieval-heavy AI products should stop treating content provenance as a background issue. If the product experience depends on scraping, summarizing, re-serving, or commercially repackaging third-party content, rights questions are part of the product risk, procurement risk, and litigation-risk analysis from day one.

    Disney’s AI copyright case against MiniMax survived its first major dismissal push

    Judge Stanley Blumenfeld Jr. denied MiniMax’s motions to dismiss for lack of personal jurisdiction and failure to state a claim in the Disney-led copyright case over the Hailuo AI system. The ruling keeps the case alive and requires MiniMax to answer the complaint.

    Procedural rulings like this are easy to underrate, but they matter. They show that some courts are willing to keep AI copyright disputes moving rather than resolving them at the threshold. That means litigants, vendors, and enterprise users should expect more record development around training inputs, model behavior, distribution theories, and rights defenses before the law settles.

    The bigger signal is not that plaintiffs have already won. They have not. It is that courts may be prepared to let these cases mature long enough to produce more meaningful guidance. For legal and business teams, that means dataset governance and vendor diligence still belong on the live risk list, not in the category of speculative future problems.

    The FTC’s latest AI case is really about fake capability claims and bad consent stories

    The FTC announced settlements with Cox Media Group, MindSift, and 1010 Digital Works over claims that they marketed an AI-powered “Active Listening” advertising product that supposedly captured consumer conversations from smart devices and relied on consumer opt-in. According to the FTC, the product did not actually work that way, did not use voice data at all, and was instead built around resold email lists.

    This is a strong enforcement reminder that AI risk is not limited to model outputs or hallucinations. Marketing claims, technical representations, and consent narratives can create liability on their own. For in-house legal teams, that reaches product marketing, vendor diligence, privacy review, procurement, and internal signoff processes.

    This is exactly the kind of case that should make lawyers ask harder basic questions before any AI product or vendor pitch goes out the door: what does the system actually do, what evidence supports that claim, what data does it really use, and is the consent story real or just sales gloss? A lot of AI governance work still comes down to old-fashioned substantiation discipline.

    Harvey and DeepJudge pushed the legal AI market further toward institutional knowledge grounding

    Harvey and DeepJudge announced a partnership aimed at bringing prior work, negotiated positions, internal expertise, permissions, and ethical-wall-aware institutional knowledge directly into AI workflows. The pitch is not just better outputs in the abstract. It is AI that reflects how a specific firm or legal department actually works.

    This is one of the clearest workflow signals of the week. Legal AI value is increasingly being framed around governed context, access controls, precedent reuse, and organization-specific judgment rather than generic model performance alone. That matters for firms and law departments trying to separate impressive demos from systems they can actually supervise and trust.

    The strongest legal AI vendors are converging on the same message: the hard part is no longer just generating text. It is controlling what institutional knowledge the system can reach, how permissions carry through, whether outputs reflect the team’s own standards, and how that whole process stays auditable. That is a much more serious buyer conversation than a feature checklist.

    Why this week mattered

    The pattern this week was not just more legal AI news. It was more evidence that the important legal AI fights are getting more concrete.

    On one side, courts and plaintiffs are pushing harder on content rights, copying, and distribution theories. On another, regulators are reminding companies that exaggerated AI claims and sloppy consent narratives can still trigger ordinary enforcement tools. And inside legal workflow itself, vendors keep moving toward governed context and institutional knowledge as the place where durable advantage may actually sit.

    For lawyers, the through-line is straightforward: the important question is not whether AI remains exciting. It is whether the systems being bought, deployed, or defended can survive scrutiny around rights, representations, governance, and operational control.

    Related Clearon reading

  • Institutional Knowledge May Be Legal AI’s Main Competitive Layer

    Institutional Knowledge May Be Legal AI’s Main Competitive Layer

    The Harvey-DeepJudge partnership offers a clear picture of where legal AI is heading next: toward institutional knowledge.

    Harvey brings the workflow layer. DeepJudge brings prior work, negotiated positions, internal expertise, and permissions-aware access to what a firm or legal department already knows. Put together, the pitch is simple: AI should do more than produce a plausible answer. It should reflect how the organization actually practices.

    What is actually at stake

    A lot of legal AI value will be won or lost here.

    If a system cannot reflect prior positions, accepted language, internal judgment, and ethical-wall-aware access rules, the output may be fast but still generic. Useful, maybe. Institutional, no.

    The deeper buyer question is shifting from model quality alone to whether the model can operate inside the knowledge, permissions, and standards that make a legal team distinctive.

    What the partnership signals

    Harvey and DeepJudge are betting that the next wave of legal AI will be less about raw model performance and more about context control.

    That means legal teams should pay closer attention to:

    • how AI reaches internal knowledge
    • whether permissions and ethical walls stay intact
    • how prior work informs drafting and analysis
    • whether outputs reflect firm-specific or department-specific standards

    The bigger shift

    This fits the same broader pattern visible across iManage, Harvey, Anthropic, and other legal AI players. The market is moving away from model quality alone and toward workflow ownership, governed context, and knowledge grounding.

    That may sound less flashy than another reasoning benchmark. It is also much closer to where real legal advantage lives.

    Practical guide: Legal AI Workflows: A Governance Checklist for Legal Teams