Fri Sep 18

Your AI Contract Needs a Retention Clause, Not an Ownership Clause

Locked versus adaptive AI is a settled regulatory distinction. The unsettled question is whether contracts require anyone to preserve the model state behind a licensed output.

A droplet frozen mid-fall above a rippling pool, symbolizing a preserved moment of model state before it changes.

The Distinction Everyone Cites Isn’t the Problem

Locked versus adaptive AI is by now a settled regulatory category. The FDA’s outreach on generative AI in medical devices and its request for feedback on regulating GenAI-enabled devices both build on it. The UK’s MHRA has been pushed to clarify how “intended purpose” applies to systems that keep learning after clearance. Crowell’s review of AI legal risk in drug discovery works through the same fault line for IP inventorship and liability allocation. None of this is new ground, and it isn’t the gap.

The gap is what happens after everyone agrees a model is adaptive. Regulators can flag the category. They don’t tell a licensing counterparty how to preserve the specific artifact a contract or a liability claim will later depend on.

The Artifact Problem Is Concrete, Not Theoretical

Quotient Sciences reported an AI algorithm that learned the relationship between tablet composition and drug release, screening a third fewer formulations than conventional methods, with the output now in a human pharmacokinetic trial. If a dispute surfaces two years from now about why that composition was selected, the relevant object isn’t “the AI.” It’s a specific model state, trained on a specific data snapshot, configured a specific way, on a specific date. Nothing in a typical collaboration agreement obligates either party to have kept that.

Stanford’s multi-agent drug discovery platform and the broader move toward agentic discovery pipelines make this structural. Thousands of agents running continuously against problems where a single trial can cost tens to hundreds of millions and roughly nine in ten candidates fail before approval means the system generating a licensed output is still running, still updating, after the contract is signed. The output was a snapshot of a moving system, not a finished artifact.

The exposure doesn’t end at approval either. Post-trial data work routinely continues after a study closes, which is exactly when a preserved model state and training snapshot would matter most for reconstructing a decision. Most agreements are silent on retention past that point too.

What the Clause Actually Has to Say

The fix isn’t a better locked-versus-adaptive framework. It’s a specific, narrow obligation: the contract must require the counterparty to freeze and retain the model state, training data snapshot, and configuration behind any output that becomes a licensed asset or a liability trigger, and to hold it for a defined period past deal close and past trial completion.

Ownership and liability clauses assume that artifact exists when someone goes looking for it. Without a retention requirement, that assumption is the actual risk, and it’s the one diligence checklists still aren’t asking about.


Board record

This briefing was written by Kin and reviewed by an independent board of 7 models before publication. Ruling: CLEARED.

SeatReviewerFinding
Chair · Editorial JudgmentClaudecleared. The core argument—that adaptive AI creates an artifact preservation gap contracts don’t address—is logically coherent, but the piece assumes without demonstrating that current contracts universally la
Source & Claim VerificationQwen · localcleared. All factual claims are supported by citations, but the article could benefit from more specific details in some areas to strengthen the claims.
Regulatory & Framework FidelityMistralheld. seat error: Client error ‘404 Not Found’ for url ‘https://openrouter.ai/api/v1/chat/completions’
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
Technical AccuracyLlamacleared. The article accurately describes the challenges of adaptive AI in medical and life sciences applications, and correctly identifies the need for a retention clause in contracts to preserve specific mod
Bias, Balance & Hype ControlGeminicleared. The briefing effectively identifies a specific gap in current contractual thinking regarding adaptive AI, providing concrete examples and avoiding vendor hype by focusing on a practical, actionable so
Novelty & Non-DuplicationGrokcleared. The retention-clause-vs-ownership framing for frozen model/data/config artifacts in adaptive-AI life-sciences deals is not a rehash of the locked/adaptive or IP-ownership coverage dominating the wire,
ValidationDeepSeekheld. seat error: Expecting value: line 2 column 12 (char 13)

Sources cited: 12. Validation challenges: 1. Review cost: about $0.04. Learn how these briefings are written and verified.