Antidote.

Legal AI

Contract analysis, diligence, and litigation assistance. Client matters are the firm's. Post-training is back on the register; Tenet is a declared research preview, not a measured increment.

As of 26 August 2026. This memo covers contract review and diligence issue-spotting under a written playbook, and Harvey's declared return to post-training. No live-product test has been run.

Post-training is back on the register. It is not a measured increment.

Harvey spent years as a multi-model router over general-purpose models. In June 2026 the company said it was coming back to post-training open-weight models so firms could own specialized intelligence. On 20 August it published Harvey Tenet: a Kimi K3 checkpoint post-trained with Fireworks for long-horizon legal work. That is a vendor research preview. It is not an independent product test, not a public weight release, and not a renewal-winning increment.

The invasion surfaces remain three: first-party legal products from the model labs, Microsoft and DMS bundling, and in-house builds. Tenet adds a fourth question on the same register: does a post-trained open-weight legal agent beat a frontier API on a frozen playbook, at a cost the firm will actually pay? Client matters are still the firm's. Extraction is still commoditizing. Playbooks can still be valuable. Reconstructable is not free.

  1. Exposed vs scarce. Extraction is commoditizing. Matter documents are the firm's. General-purpose routing is reconstructable in kind.
  2. Still untested. Tenet versus a current frontier API on a sealed playbook and matter set. Legal correctness has not been run.
  3. The comparison that would change the call. Tenet on versus Tenet off, same harness, same matters — then Harvey versus a lab legal assistant, a DMS bundle, or the firm's own build.

Decision questions

  1. On a frozen playbook and matter set, does Harvey clear a prespecified quality and critical-miss gate relative to the current review process?
  2. What isolated increment comes from playbook templates, matter retrieval, or model identity, each changed one at a time?
  3. What is full cost per accepted memo, including escalation and partner review, not token list price?
  4. Are client materials reusable across matters, and is any quality lift from that reuse measured?
  5. Against which alternative does Harvey win the next renewal: a model lab's first-party legal product, a DMS-native bundle, or the firm's own in-house build?
  6. On the same frozen playbook and matters, what isolated increment, if any, does Tenet show against the current frontier API Harvey already routes to?

Legal work fails in specific ways: missed exceptions, unsupported recommendations, contradicted clauses tagged as silent, and fluent analysis that restates the rule without applying it. Those classes stay separate. Span overlap is not a legal-correctness verdict. A correct label with the wrong evidence span is a different error than a wrong label with a good span.

Public packs are calibration. LegalBench is a 162-task collaboration with per-task licenses; this report uses published 2023 category results and does not collapse them. LegalBench-RAG is held out until a source-by-source license chain is approved. CUAD and ContractNLI are extractive and NLI diagnostics. A Harvey run would still need sealed matters, a written playbook, and qualified review.

Workflow breakdown

Each step of the job is mapped to a published benchmark or another reputable quantitative measure only where the mapping is honest. A public figure is a floor or a labor-market context on that task type. It is never a score of this product.

TaskPublished measurePack fitWhat it does not measure
Locate a clause type in a commercial contractCUADPack fit strongSpan overlap is not legal correctness in a client fact pattern.
Test whether a hypothesis is entailed, contradicted, or not mentionedContractNLIPack fit strongContradiction is the weak slice in the paper. Not advice quality.
Avoid claiming a clause is absent when it is presentContractEvalPublic floor onlyLaziness on CUAD risk categories. Still not Harvey.
Legal reasoning by type: issue-spot, apply a rule, interpretLegalBenchPublic floor onlyCategory scores stay separate. Composite LegalBench is refused. License is composite.
Playbook application on sealed client mattersNoneNo honest public floorNeeds the firm's documents, written playbook, and qualified review.

Findings at a glance

Capability, cost, and defensibility are assessed separately. They are not averaged into a score. Where evidence is missing, the finding stays open.

StatusAreaFinding
OpenWorkflow capabilityCUAD span overlap is not legal correctness in a client matter. No authorized Harvey run is in this report.
OpenOperating economicsReviewer minutes, accepted-without-edit rate, and full cost per accepted memo are unmeasured.
JudgmentDefensibilityMatter documents are the firm's. Without a DPA grant there is no data network effect. Public legal NLP is commoditizing extraction. The invasion surfaces are first-party model-lab products, Microsoft and DMS bundling, and customer insourcing. Harvey's June–August 2026 return to post-training (Tenet on Kimi K3) is a declared strategy, not a measured increment. Playbooks can be valuable and still reconstructable.
Vendor-statedVendor claims and open questionsPublic positioning covers contract analysis, diligence, and litigation assistance. Tenet is Harvey's first named post-trained checkpoint, published 20 August 2026 as a research preview. LAB cells are vendor-declared. First-party competition and in-house-build accounts remain dated structural judgments, not measurements.

Workflow capability

One legal average would be the wrong object

Guha et al. 2023 report balanced accuracy by reasoning category, not a winner score. GPT-4, retrieved May to August 2023, is 82.9% on issue-spotting and 59.2% on rule recall. Rule conclusion is 89.9%; interpretation 75.2%; rhetorical understanding 79.4%. GPT-3.5 and Claude-1 are close to each other on several categories and far from GPT-4 on issue-spotting. That pattern is why a diligence record keeps categories apart.

Rule-application is graded twice: correctness and analysis. GPT-4 is 82.2% correct and 79.7% with analysis. GPT-3.5 is 58.5% and 44.2%. A system that emits the right outcome without the inference is a different product failure than a system that gets the outcome wrong. Hearsay slices in the same paper are small (n 12 to 29) and still useful as a map: GPT-4 lifts non-verbal hearsay from 33% to 75% and in-court statements from 57% to 93%, while both models remain weak when the statement is not offered for its truth (25% vs 45%). Those are model diagnostics from 2023, not a 2026 product ladder and not a Harvey result.

Clause location is not legal operability

CUAD asks where a clause lives across 41 commercial categories. Hendrycks et al. 2021: DeBERTa-xlarge has 47.8% AUPR and 44.0% precision at 80% recall. RoBERTa-large has a higher AUPR (48.2%) and a worse precision at 80% recall (38.1%). Those two numbers answer different questions. Averaging them would manufacture a ranking that neither metric supports. At 80% recall, even the stronger precision figure still means roughly two irrelevant hits per relevant clause.

ContractNLI adds a three-way label: entailment, contradiction, not mentioned, plus evidence spans. Span NLI BERT with DeBERTa v2 fine-tuned on CUAD reaches 89.2% NLI accuracy, 85.9% entailment F1, and 40.5% contradiction F1. The dangerous class is the weak class. A diligence memo that treats silence and contradiction as the same miss will look better than it is.

Harvey is back on post-training. That is a strategy change, not a product score.

The general-model-only thesis is the one Harvey left. In June 2026 Gabe Pereyra said Harvey was building a legal foundation-model series on open weights, inspired by Cursor's Composer, so it could serve frontier intelligence cheaper and let firms own specialized models. Winston Weinberg told Artificial Lawyer the firm was running proofs of concept that encode how a practice group — and a longstanding client — actually works. The trade press named the reversal: post-training open source is coming back after the market had treated it as pointless.

Harvey Tenet, published 20 August 2026, is the first artifact of that turn. Harvey says it is a Kimi K3 base post-trained with Fireworks by asynchronous reinforcement learning on synthetic data, public legal data, and human expert data, and that no customer data was used. The company calls it a research preview. It has not published weights, a model card, or an API. The base model is open-weight. Tenet is Harvey's checkpoint. Harvey II, two days earlier, said that until then Harvey had relied on general-purpose models and that Tenet was the first model post-trained end-to-end for legal reasoning.

The scoreboard is Harvey's Legal Agent Benchmark. Harvey reports that Tenet completes almost twice as many held-out LAB tasks as base Kimi K3 and 20 percent more on LAB: Contracts, lifting all-pass rate by 9 and 2 percentage points, with state-of-the-art on LAB: Contracts and second on LAB. It says those gains transferred, untrained, to Mercor's APEX Agents corporate-law subset and Crosby's Redline Bench. LAB is Harvey's own long-horizon legal-agent bench. Those cells are declared vendor results, often Harvey-run, and they do not stand in for legal correctness on a client matter.

The specialist stack is the rest of the research surface: an RLM diligence harness with Baseten on datarooms Harvey says can reach 80 million tokens; Review Table post-training with Applied Compute; and firm-knowledge memory with Engram on a Qwen3.8-27B. Harvey says the point is twofold — frontier legal intelligence on open weights, and a path for two firms to end up with different models because their work shaped them. The second claim is a switching-cost hypothesis. It is not an observation of exclusivity, export, or a measured quality increment when firm history is added and nothing else changes. A PE buyer still has to ask whether a Chinese open-weight base is an acceptable supply and trust fact for the firm's clients.

Published benchmarks

LegalBench, CUAD, ContractNLI, and ContractEval bound public legal NLP by reasoning type. They do not decide legal correctness in a client matter.

LegalBench

LegalBench is the public model ladder for legal reasoning types. Category scores stay separate. Interpretation includes CUAD-style clause classification, which is easier than span extraction.

Paper table · Guha et al., 2023 · not an Antidote run · not a product score

LegalBench commercial models by reasoning category

Guha et al., 2023, Table 2. Balanced accuracy within each reasoning category. GPT-4, GPT-3.5 (text-davinci-003), and Claude-1, retrieved May to August 2023. Not a single LegalBench winner score.

Reasoning categoryGPT-4GPT-3.5Claude-1
Issue-spotting82.9%60.9%58.1%
Rule recall59.2%46.3%57.7%
Rule conclusion89.9%78%79.5%
Interpretation75.2%72.6%67.4%
Rhetorical79.4%66.7%68.9%

Paper table · Guha et al., 2023 · not an Antidote run · not a product score

LegalBench rule-application correctness and analysis

Guha et al., 2023, Table 3. Correctness and analysis are graded separately. A correct outcome without analysis is a different failure than an incorrect outcome.

SystemCorrectnessAnalysis
GPT-482.2%79.7%
Claude-161.4%59%
GPT-3.558.5%44.2%

Paper table · Guha et al., 2023 · not an Antidote run · not a product score

Hearsay slices, GPT-3.5 vs GPT-4

Guha et al., 2023, Table 6. Slice n is 12 to 29. These percentages show where the models diverge, not a population estimate.

SlicenGPT-3.5GPT-4
Non-assertive conduct19100%100%
In-court statement1457%93%
Standard hearsay2997%97%
Non-verbal hearsay1233%75%
Not for truth2025%45%

CUAD

CUAD measures extractive clause location, not whether a clause is legally operative in a client fact pattern.

Paper table · Hendrycks et al., 2021 · not an Antidote run · not a product score

CUAD precision-recall, selected models

Hendrycks et al., 2021, Table 2. AUPR and precision at 80% recall are different estimands and are not averaged.

SystemAUPRPrecision @ 80% recallPrecision @ 90% recall
DeBERTa-xlarge47.8%44%17.8%
RoBERTa-large48.2%38.1%0%
RoBERTa-base42.6%31.1%0%
ALBERT-xxlarge38.4%31%0%
BERT-base32.4%8.2%0%

ContractNLI

ContractNLI distinguishes entailed, contradicted, and not-mentioned hypotheses, with evidence spans. Contradiction F1 is the weak slice in the paper.

Paper table · Koreeda and Manning, 2021 · not an Antidote run · not a product score

ContractNLI label accuracy and entailment F1

Koreeda and Manning, EMNLP 2021 findings, Table 3. Contradiction F1 stays much lower than entailment F1 and is not folded into accuracy.

SystemNLI accuracyEntailment F1Contradiction F1
DeBERTa v2 + CUAD89.2%85.9%40.5%
DeBERTa v2 xlarge88.5%85.5%36%
BERT-large87.5%83.4%35.7%
BERT-base83.8%76.5%28.7%

ContractEval

ContractEval adds a laziness metric on CUAD risk categories: claiming no related clause when one exists. It is still not a product score.

How to read the published benchmarks

Read LegalBench as a map of reasoning types, CUAD as clause location, and ContractNLI as unsupported versus contradicted claims. Do not publish a LegalBench macro. Do not treat CUAD token overlap as advice quality. Do not treat 2023 GPT-4 as a current frontier cell; current IDs and list prices are in the economics block and still need a dated LegalBench rerun before they are calibration results.

Harvey LAB, LAB: Contracts, APEX Agents, and Redline Bench in the Tenet post are vendor-declared legal-agent results. They are not the public packs on this page and they are not a Harvey product score. Contamination is high on LegalBench, CUAD, and ContractNLI. They remain useful as harness regression and as a reminder that legal NLP tasks do not share one difficulty.

Current systems, cost, and harness

Official list prices observed 8 August 2026 bound the model bill only. They are not a product subscription and not full cost per accepted output. The ladder is an illustrative bundled contrast: a small scaffold and a heavy scaffold are different systems. The bars are a design sketch, not a product score. Full cost still has to include failed attempts and reviewer minutes.

List price per million tokens

Official list prices observed 8 August 2026 from provider catalogs. USD per million input / output tokens. Cache, tools, long-context, and service-tier charges are not included.

ModelSlotInputOutput
GPT-5.6 SolFrontier$5.00$30.00
GPT-5.6 TerraBalanced$2.00$12.00
GPT-5.6 LunaEconomic$0.20$1.20
Claude Fable 5Frontier$10.00$50.00
Claude Opus 5Frontier$5.00$25.00
Claude Sonnet 5Balanced$3.00$15.00
Claude Haiku 4.5Economic$1.00$5.00
Grok 4.5Challenger$2.00$6.00
What a harness can change

Illustrative condition ladder on a frozen contract-review set. Playbook prompting is a small harness. Matter retrieval is a larger one. Tenet versus the routed frontier API is a missing isolated condition, not a bar on this ladder. Review-loop cost is in the full cost, not only the token bill.

Playbook prompting is a small harness. Matter retrieval is not.

The failure mode that matters for Harvey is publishing a LegalBench category score, or a Harvey LAB cell, as if it were legal correctness on a client matter. Playbook, retrieval, routed frontier API, and Tenet have to be changed one at a time or left unproven.

If only the product is observable, publish outcome and price. Leave model-level, post-training, and orchestration-level stories as unproven. Native PDF or long-context dumping is a different treatment from retrieval with evidence spans.

Operating economics

Reviewer minutes dominate the token bill

Current list prices bound the model component only. An economic-tier model such as GPT-5.6 Luna or Claude Haiku 4.5 can be the right cell if it clears the same quality and critical-miss gates as a frontier cell. That is an efficiency finding, and it requires the frozen ladder, not a preference for the newest name.

Full cost per accepted memo still needs failed attempts, retrieval, partner or associate correction, and any embedded legal-engineering time, with a cap treated as censored. Harvey describes Legal Engineers; intensity, margin, accepted-without-edit rate, and escalation burden are missing. A low token bill with high implementation or review load is not cheap automation.

Tenet's cost story is vendor-declared. Harvey says open-weight token prices are lower and that reward shaping cut tokens used for the same quality. Review Table research claims better citation quality at roughly one-tenth the cost per cell versus the strongest baselines they ran. Those cells are Harvey's. They are not full cost per accepted memo on a client matter.

Defensibility

Client matters are the firm's. Public legal NLP is commoditizing extraction.

Matter documents are client- or firm-owned. Harvey says customer data and content are not used to train shared models or improve shared products. Without the target's executed agreement, retained-feature settings, and customer-specific model terms, lawful reuse remains unknown and no cross-client matter-data flywheel may be claimed.

Public CUAD-style extraction and ContractNLI already show that clause location and contradiction are model tasks. Direct substitution is a generic legal stack inside the firm's DMS, not a new corpus. Microsoft, DMS vendors, and research terminals can attach generation to seats the firm already pays for. Workflow embed inside firm process can raise switching costs. That remains a structural hypothesis without retention, export friction, and services-dependence observations.

Reported dynamics sharpen the register. They do not settle it.

Harvey still describes a multi-model platform that routes across Anthropic, Google DeepMind, and OpenAI. Tenet sits beside that architecture as a declared post-trained checkpoint, not as a replacement that has been isolated. Routing, retrieval, playbook, and Tenet have to be changed one at a time or left unproven.

Public materials also describe ownership, no-training of customer data, provider-retention, provider-control, and embedded legal-engineering practices. Harvey's Tenet post says the same no-customer-data rule for the research run. Those are useful leads, not approved trust or service claims. Executed contracts, legal correctness, privilege handling, service intensity, and switching still need separate evidence.

Defensibility

Client matters are the firm's. Public legal NLP is commoditizing extraction. Harvey's remaining questions are playbook, matter retrieval, rights, first-party competition from the model labs, and Microsoft-style bundling. Reported in-house builds make customer insourcing its own exposure row.

DimensionRatingJudgmentMissing evidence
Data rightsExposedMatter documents are client- or firm-owned. Cross-matter reuse for model improvement needs a DPA and an explicit grant. Absent that grant, Harvey does not own the corpus.DPA, retention, and cross-matter reuse terms.
ExclusivityConditionalDomain playbooks can be valuable and still be reconstructable. Model identity, if opaque, cannot be credited as exclusive until a paired comparison exists. Public CUAD-style extraction is not exclusive.Rebuild time for playbooks and a generic-system paired comparison.
Rebuild difficultyConditionalA raw model plus a written playbook reconstructs the small harness. Matter retrieval over the actual corpus is harder. Both are reconstructable in kind. The increment is unmeasured.Playbook-only versus retrieval-plus-playbook on sealed matters.
FreshnessOpenHarvey's published agreement bars using customer content to train shared models while permitting non-identifying feedback and usage data to improve the service. The public loop is therefore telemetry-bounded, not matter-content compounding.Telemetry schema, retention, aggregation thresholds, opt-outs, experiments, and a measured quality curve.
Switching costConditionalPlaybooks and matter workspace embed can raise switching costs inside a firm. Unobserved.Export of playbooks, matter traces, and retention.
System of recordExposedHarvey is an assistance layer. Legal advice authority remains with the firm. Generation must not be treated as the matter record.Whether outputs are filed as work product and under whose control.
IntegrationsConditionalDMS and matter-system connectors create gravity. They also define the Microsoft bundling surface.Connector inventory and a DMS-native generation paired comparison.
Network effectsExposedCross-firm learning from client matters is usually forbidden. Without lawful reuse there is no data network effect.Any claimed cross-client improvement would need rights and a measured increment.
Trust and complianceOpenHarvey's published privacy and security controls bar customer-content training and state that model providers must meet zero-retention and no-human-review requirements. Those vendor declarations do not establish legal correctness, privilege handling in edge cases, or incident absence.Critical-miss audit, privilege handling, and incident record.
DistributionConditionalLaw-firm distribution is a channel. It does not block Copilot, Harvey competitors, or a DMS vendor from attaching legal generation to existing seats.Win/loss versus named legal-AI and platform bundles.
Services dependenceOpenHarvey embeds former lawyers with customers to build and refine agents and workflows. Legal engineering is a declared service layer; partner review remains the likely downstream exception cost.Legal Engineer hours and margin, accepted-without-edit rate, escalation, and partner minutes.
Rate of improvementOpenNo measured playbook-improvement curve is in this report.Dated quality series on frozen playbooks and matters.

How AI can compete

Replacement, a new AI product, a platform bundle, cheaper labor, and a customer building it themselves are different risks. They are not averaged into a score.

MechanismAssessment
Direct replacementA current model plus the firm's playbook and DMS retrieval is the named competitor. Harvey has to beat that cell, not beat an associate with no tools. Substitution now includes first-party legal products sold by the model labs themselves: the platform that supplies the model can also be the competing vendor.
New AI productPublic legal extraction and NLI are already model tasks. Invasion is a generic legal stack inside the firm's DMS, not a new corpus.
Platform bundleMicrosoft, DMS vendors, and research terminals can attach legal generation to systems the firm already runs.
Labor compressionIf critical-miss gates clear, associate hours on first-pass review can fall. That is a modeled value-creation case. It is not Harvey defensibility.
Customer builds itThe firm can wire a frontier model to its own playbooks and DMS instead of sharing matter data with either the vendor or a lab. Large in-house programs are reported in industry accounts as of August 2026; that is discourse, not contracts. Insourcing removes both the seat and the data-sharing objection at once.

Data flywheel

A flywheel needs every step below. On this evidence it is unproven. Having data is not the same as being allowed to reuse it, and reuse is not the same as a measured quality gain.

LinkStatusNote
Unique dataVendor-statedPlaybooks may be Harvey's. Matter exhaust is the firm's.
Permission to reuseOpenHarvey's July 2026 published default says customer data and content are not used to train models or improve shared products. Customer-specific retained features and bespoke models require separate target-term review.
Reliable feedbackOpenNo audited correction labels.
Proven quality gainOpenNo isolated playbook or retrieval increment.
Better outcomesOpenNo independent matter test.
More usage or dataOpenRetention from embed is unobserved.

What public sources resolve

Public filings and vendor documentation can settle some structural questions. They cannot replace a test on the live product.

QuestionConclusionStill open
May client data be reused to improve the shared product?Harvey's July 2026 published policy says customer data and content are not used to train models or improve products and services, and binds AI providers to the same restriction.Privacy CenterThe target's executed agreement, administrator-enabled retained features, and any customer-specific model terms.
Does a fine-tune or proprietary model drive Harvey's result?Harvey still declares a multi-model platform with provider routing. On 20 August 2026 it also published Tenet, a Kimi K3 checkpoint it says it post-trained with Fireworks. Public evidence therefore supports a bundled system plus a declared research-preview checkpoint, not attribution of client-matter outcomes to Tenet.Why Harvey is Multi-Model by Design; Inside Harvey: How a first-year legal associate built one of Silicon Valley's hottest startups; Update on Harvey's Post-Training Effort; Introducing Harvey IIPaired Tenet-on versus Tenet-off and frontier-API comparisons on the same sealed matters and playbooks.
Has Harvey returned to post-training its own legal models?Yes as a declared research strategy. June 2026 interviews and founder posts said Harvey was post-training open-weight models and running firm proofs of concept. The 20 August Tenet post is the first named checkpoint. It remains a research preview: no public weights, no independent product test, and no measured client-matter increment.Harvey Trains Open Source Models To Encode Law Firm Workflows; Update on Harvey's Post-Training Effort; Harvey Introduces Tenet, Its First Post-Trained AI Model for Legal; Introducing Harvey IIProduction status in the executed agreement, independent LAB replay, and a Tenet-on versus routed-frontier-API test on sealed matters.
Is Harvey's services dependence low?The low-services premise is not supportable from public evidence. Harvey embeds former lawyers with customers to build and refine agents and workflows, making legal engineering part of the operating model.Day in the Life: Legal Engineer; Harvey Platform AgreementLegal Engineer headcount, customer hours, utilization, implementation margin, revenue attribution, and renewal dependence.

Required comparisons

A decision-grade test would run these side by side. None has been run here.

ComparisonNote
Current workflowAssociate and partner review process must be imported, not assumed.
Generic modelSame playbook, generally available model, no legal-product harness.
Named competitorDeclared retrieval over the matter corpus with a fixed budget.
This productRequires Harvey access and matter-level authorization.
Isolated changesPlaybook, retrieval, routed frontier API, and Tenet must be separable or labeled unproven.

Open claims

Each claim stands on its own. They are not averaged into a moat score. If only the product surface is observable, outcome and price can still be reported. Model-level and Tenet stories stay unproven. Client matters are not Harvey's exclusive data.

ClaimStatusWhat is still missing
Domain harness and templates are not reconstructable.OpenRebuild time, required talent, and a generic-system paired difference.
Matter documents are typically the firm's, not Harvey's exclusive corpus.JudgmentProcessing rights versus ownership still need the DPA.
Harvey's published default bars customer data and content from shared model training or product improvement.OpenThe target's executed agreement, administrator-enabled retained features, and customer-specific model terms.
Microsoft or DMS bundling risk is low.OpenA DMS-native generation paired comparison and channel exposure.
Harvey publicly describes a multi-model routed system, so model-level contribution remains bundled.OpenA paired model-identity and isolated comparison on the same sealed matters and playbooks.
Harvey has returned to post-training its own legal models.JudgmentProduction status of Tenet, independent LAB replay, and a Tenet-on versus routed-frontier-API increment on sealed matters.
Tenet, a Kimi K3 checkpoint post-trained with Fireworks, is a measured quality or cost increment on client matters.OpenAuthorized Tenet-on versus Tenet-off on a frozen playbook. LAB cells are vendor-declared.
Firm-owned specialized models create exclusivity or switching cost.OpenExport, exclusivity, and a measured quality increment when firm history is added and nothing else changes.
Model-lab first-party legal products compete for the same seats.JudgmentWin/loss versus first-party offerings and their data terms. Reported competition as of August 2026, not a measured displacement rate.
Firms will share matter data with the vendor but not with a model lab.JudgmentDPA terms versus lab defaults, and whether reported in-house builds displace both. Reluctance is reported discourse, not a contract observation.
Embedded Legal Engineers make a material services layer part of Harvey's operating model.OpenLegal Engineer headcount, hours per customer, utilization, implementation margin, accepted-without-edit rate, escalation, and source evidence.

What this report does not conclude

  • Legal correctness of Harvey or Tenet on a client matter
  • Independent confirmation of Harvey LAB or Tenet cells
  • A measured increment of Tenet over the frontier API Harvey already routes to
  • Attribution to fine-tuning, a custom model, or a proprietary playbook
  • A data moat; client matters are the firm's
  • Cross-client learning or lawful reuse of matter data
  • That firm-owned specialized models create exclusivity or switching cost
  • Full cost per accepted memo or services dependence
  • Time-to-parity against a generic legal stack
  • Win/loss versus first-party model-lab products and in-house builds

What would settle these questions

  1. Authorized Harvey access and matter-level export of traces, with Tenet on and off.
  2. Imported associate and partner process observations.
  3. A sealed playbook and independently adjudicated issue-spotting key.
  4. Raw-model, declared generic-retrieval, routed frontier-API, and Tenet cells on the same matters.
  5. Isolated playbook, retrieval, and model isolated comparisons, or an explicit unproven label.
  6. Independent replay of LAB hold-out tasks, or a refusal to treat Harvey-run LAB as product evidence.
  7. Production versus research-preview status of Tenet in the executed agreement.
  8. Reviewer minutes, escalation rate, and all-attempt cost.
  9. The target's executed agreement, retained-feature settings, and customer-specific model terms before any flywheel or firm-owned-model claim.
  10. A DMS-native generation paired comparison versus Harvey-only review.

Sources

  1. Harvey Platform AgreementHarvey · Official contract · 9 January 2026

    Harvey's published agreement says customers own inputs, outputs, and uploaded data and bars Harvey and subprocessors from training models on them. Non-identifying feedback and usage data may improve the service.

    Order forms and feature-specific terms may modify the standard agreement. Usage-data fields, retention, opt-outs, and executed target terms remain unverified.

  2. Privacy CenterHarvey · Official policy · 13 July 2026

    Harvey states that it does not use customer data or content to train AI models or improve products and services. It says AI-provider subprocessors are contractually prohibited from training on or improving services with that content.

    Published default policy, not the target customer's executed agreement. Account-specific retained features and bespoke customer-only models must be checked separately.

  3. Introducing Harvey IIHarvey · Official product documentation · 18 August 2026

    Harvey says that until Harvey II / Tenet it relied on general-purpose models, that Tenet is its first model post-trained end-to-end for legal reasoning, that memory is never used to train models, and that two firms could end up with different models because their legal work shaped them.

    Vendor product post. It declares a strategy change and a future firm-owned-model path. It does not isolate Tenet's contribution on a frozen matter set.

  4. Day in the Life: Legal EngineerHarvey · Official product documentation · 29 April 2026

    Harvey describes former lawyers working directly with customers to design and refine agents, workflows, and legal work product. A material forward-deployed service layer is therefore part of the operating model.

    Vendor role description. Headcount, hours per customer, utilization, services revenue, capitalization, and renewal dependence are not public.

  5. Why Harvey is Multi-Model by DesignNiko Grupen, Harvey · Official product documentation · 10 March 2026

    Harvey describes a multi-model architecture spanning Anthropic, Google DeepMind, and OpenAI, with task routing informed by BigLaw Bench and expert preference tests. The same disclosure says model providers must meet zero-retention, no-human-review, and no-training requirements for customer data.

    Vendor-authored architecture and provider-policy statement. It does not expose provider contracts or isolate the contribution of routing, retrieval, playbooks, post-training, or a particular model to client-matter outcomes.

  6. Update on Harvey's Post-Training EffortHarvey · Official product documentation · 20 August 2026

    Harvey published Tenet as its first post-trained model: a Kimi K3 base post-trained with Fireworks by asynchronous RL on synthetic, public legal, and human-expert data. It says no customer data was used. It reports almost twice as many held-out LAB tasks as base K3, 20 percent more on LAB: Contracts, and all-pass lifts of 9 and 2 percentage points, with claimed transfer to APEX Agents and Redline Bench. It describes the work as a research preview to be moved into production over time, and restates a second goal that firms build and own specialized models.

    Vendor research post. LAB is Harvey's own bench and many reported cells are Harvey-run. No public weights, model card, or API. Not an independent product test and not legal correctness on a client matter.

  7. Harvey Introduces Tenet, Its First Post-Trained AI Model for LegalLaw.com Legaltech News · Third-party assessment · 20 August 2026

    Independent trade coverage corroborates the 20 August Tenet announcement, the Fireworks / Kimi K3 base, asynchronous RL, and that the introduction followed a June 2026 plan to develop custom legal-specific models.

    Secondary report of Harvey's own post. It does not independently rerun LAB or inspect weights.

  8. Inside Harvey: How a first-year legal associate built one of Silicon Valley's hottest startupsWinston Weinberg interview, TechCrunch · Named interview · 14 November 2025

    Harvey's co-founder describes workflow data and evaluation infrastructure as proposed advantages and acknowledges that the frontier model carried substantial product power in 2023 and 2024.

    Attributed founder thesis, not a measured moat or independent causal result. It is admissible only as dated structural discourse.

  9. Harvey Trains Open Source Models To Encode Law Firm WorkflowsArtificial Lawyer, quoting Winston Weinberg and Gabe Pereyra · Named interview · 18 June 2026

    In June 2026 Harvey's CEO confirmed proofs of concept that post-train open-source models to encode a practice group's — and a longstanding client's — way of working. Co-founder Gabe Pereyra described a legal foundation-model series on open weights, inspired by Cursor's Composer, with the dual goal of cheaper frontier intelligence and firms owning their own models. The piece states explicitly that post-training open source is coming back after the general-model-only thesis.

    Named interviews and founder posts, not a measured increment. Proofs of concept are not production Tenet.