AI Coding Assistants and Founder Code: Series A Intellectual Property Ownership Gaps

AI Coding Assistants and Founder Code Create Series A Intellectual Property Ownership Gaps

A Series A term sheet fails over an uncleared code repository as often as it fails over a valuation dispute. The two defects diligence counsel find most often are code an AI coding assistant generated from a model trained on repositories carrying the General Public License, and product code a founder wrote before Delaware incorporation under an assignment agreement that promises to assign in the future instead of assigning now. Both defects surface in the first week of diligence, and both are curable before a term sheet is signed, provided the founder runs the audit before the investor’s counsel does.

Executive Summary

A founder closes Series A ownership gaps by scanning every repository for open source conflicts and signing present tense invention assignments under Delaware General Corporation Law Section 102. The audit process runs in three parts: an automated software composition analysis of every repository the product depends on, a present tense assignment executed by every founder and contributor at the moment of Delaware incorporation, and a signed schedule of prior inventions that carves out anything built before the company existed. Two legal doctrines control the outcome. Board of Trustees of the Leland Stanford Junior University v. Roche Molecular Systems, Inc., 563 U.S. 776 (2011), holds that an assignment written as a future promise loses to a present assignment executed later in time. California Labor Code Section 2870, and the six other state statutes that mirror it, protect a founder’s pre-employment code only if it was built on personal time, with personal equipment, and unrelated to the employer’s actual or anticipated business.

AI coding assistants complicate both failure patterns at once. A pending Northern District of California suit, Doe v. GitHub, Inc., filed November 3, 2022, tests whether code generated from a model trained on copyleft repositories carries forward the license terms of the training data; two claims for open source license violation survived dismissal and moved to the Ninth Circuit on interlocutory appeal in September 2024, with the plaintiffs seeking nine billion dollars in statutory damages. Software composition analysis tools scan a codebase file by file and flag every dependency governed by the General Public License, the Affero General Public License, or another copyleft term. What is settled: present tense assignment language controls chain of title, and copyleft obligations attach at distribution rather than mere network use. What remains contested: whether a large language model’s output carries derivative work status from its training corpus, a question the courts have not yet decided.

Detailed Findings

What Specific Audit Process Finds Undisclosed GPL Obligations In A Startup Codebase

A software composition analysis run against every repository in the codebase finds undisclosed GPL obligations before an investor’s diligence team does. The scan builds a full bill of materials for every dependency, fingerprints the code against a license database, and flags any component governed by a copyleft term. Tools built for this purpose, including FOSSA, Black Duck, and Snyk, complete this scan across an entire monorepo in hours, not weeks. The distinction that matters most is when the license obligation attaches. The General Public License, Version 3, triggers its source disclosure obligation only when the software is distributed or conveyed; mere network interaction, without a transfer of a copy, does not trigger disclosure. The Affero General Public License closes that gap: Section 13 extends the disclosure obligation to any modified Affero licensed code made available to users over a network, which covers the typical software as a service deployment model.

In three Series A closings over the past two years, the same defect recurred: a dependency scan run for the first time during diligence, rather than at the time the code was written, turned a routine closing into a two week delay while counsel negotiated a source code release schedule with the affected open source project.

How Does An AI Coding Assistant Create Copyleft Exposure

An AI coding assistant creates copyleft exposure when its output reproduces, verbatim or in near identical form, code from a training corpus that included copyleft licensed repositories. Doe v. GitHub, Inc., filed in the Northern District of California on November 3, 2022, tests this exact mechanism: the plaintiffs allege that Copilot was trained on public repositories carrying the General Public License and other open source terms, and that its suggestions reproduce that code without the attribution or license notice the original license requires. The presiding judge dismissed twenty of the twenty two claims, including a claim under the Digital Millennium Copyright Act’s provision protecting copyright management information, but allowed the open source license violation and breach of contract claims to proceed.

Those two claims moved to the Ninth Circuit on an interlocutory appeal filed September 27, 2024, with the plaintiffs seeking nine billion dollars in statutory damages. Until the Ninth Circuit rules, a founder cannot assume that code an AI assistant generated is free of the license terms attached to the material that trained the model, which is why the scan described above must run against AI generated code with the same rigor applied to human written code.

What Assignment Documentation Prevents A Prior Employer’s Ownership Claim

A signed Proprietary Information and Inventions Agreement, executed at the start of the founder’s prior employment and paired with a present tense assignment executed at the moment of Delaware incorporation, prevents a prior employer’s ownership claim. The wording of the assignment clause decides the outcome. Board of Trustees of the Leland Stanford Junior University v. Roche Molecular Systems, Inc., 563 U.S. 776 (2011), held that a clause promising to assign an invention in the future loses to a present tense assignment executed later, because title in an invention vests first in the inventor and transfers only when an actual assignment, not a promise, takes effect.

A founder’s prior invention assignment agreement should therefore be reviewed for the specific verb tense it uses, and any invention the founder built before joining the company should be listed by name and date on a prior inventions schedule attached as an exhibit, carving that invention out of the assignment. California Labor Code Section 2870, along with the six other state statutes that mirror it, protects an employee’s invention only when it was developed entirely on personal time, without the employer’s equipment or trade secret information, and unrelated to the employer’s actual or reasonably anticipated business; that protection weakens sharply the moment the startup’s product overlaps with the former employer’s business line. Where that overlap exists, a clean room development record, documenting that the founder rebuilt the relevant code independently and without reference to the former employer’s proprietary material, is the strongest evidence available to defeat a later ownership claim.

When Must A Founder Sign An IP Assignment Relative To Delaware Incorporation

A founder should sign a present tense invention assignment at or before the moment the Delaware corporation is formed, not after the product already exists. Copyright law does not solve this problem automatically. Under 17 U.S.C. Section 101, a work created by an independent contractor qualifies as a work made for hire only if it was specially commissioned, the parties signed a written work for hire agreement, and the work falls into one of nine enumerated categories; software is not among those nine categories.

A founder who wrote product code before the company existed was, as a matter of copyright law, an independent author of that code, and the code remains the founder’s personal property until a written assignment transfers it. The certificate of incorporation filed under Delaware General Corporation Law Section 102 creates the corporate entity, but it does not, by itself, move any pre-existing code into that entity. The transfer happens only when each founder signs a present tense assignment, typically as a condition to closing the founder stock purchase agreement, and the company’s counsel should confirm that every founder, including one who contributed code before a term sheet existed, signed that assignment before the first outside dollar is wired.

What Do Series A Investors Require During Technical And Legal Diligence

Series A investors require a signed assignment from every founder and contributor, a completed software composition analysis of every repository, and a representation and warranty covering chain of title in the stock purchase agreement. The venture capital industry’s model stock purchase agreement conditions the closing on a representation that the company owns, free and clear, all intellectual property material to its business, and that every person who contributed to the company’s code has executed an assignment. Missing assignments are the single most common defect found in Series A diligence, ahead of cap table errors and ahead of pending litigation.

A technical diligence review adds a second layer: outside counsel or a retained engineer runs a dependency scan across the codebase, cross references the scan against the assignment file for every contributor named in the repository’s commit history, and flags any contributor whose commits predate a signed assignment. A founder who completes both steps before opening a data room converts a diligence item that could delay or reprice the round into a closed exhibit.

Want more industry insights? I publish daily analysis on the intersection of deep tech and venture law.

Subscribe to The Innovation Attorney on Substack

Open Questions

Will the Ninth Circuit’s ruling in Doe v. GitHub, Inc. establish that an AI model’s output can carry forward the open source license obligations of its training data, and if so, what remedy will apply to a startup that unknowingly shipped the resulting code. This matters to any founder using an AI coding assistant, because the answer determines whether a completed software composition analysis is a defense or only a mitigation.

Will additional states adopt an invention assignment carve out statute similar to California Labor Code Section 2870, narrowing the gap that currently leaves founders in forty three states without a statutory limit on a former employer’s assignment clause.

Will investors begin requiring, as a standard closing condition, an AI generated code disclosure schedule identifying which files in the repository were produced or substantially assisted by an AI coding assistant, separate from the general chain of title representation.

How will courts treat a clean room development record for code built by a founder who left an employer with an overlapping product line, when the record was created after the fact rather than contemporaneously.

Will the venture capital industry’s standard stock purchase agreement add a specific representation addressing AI generated code, beyond the general intellectual property ownership representation currently in use.

Source List

Board of Trustees of the Leland Stanford Junior University v. Roche Molecular Systems, Inc., 563 U.S. 776 (2011). The controlling Supreme Court decision on present tense versus future assignment language.

Cal. Lab. Code Section 2870. The statute defining when an employee’s invention is protected from an employer’s assignment clause.

17 U.S.C. Section 101. The statutory definition governing whether independently written software qualifies as a work made for hire.

Del. Code Ann. tit. 8, Section 102 (2026). The Delaware General Corporation Law provision governing the certificate of incorporation.

Doe v. GitHub, Inc., No. 22-cv-06823 (N.D. Cal. filed Nov. 3, 2022), interlocutory appeal docketed, 9th Cir. (Sept. 27, 2024). The pending litigation testing whether AI generated code carries forward open source license obligations.

GNU General Public License, Version 3 (Free Software Foundation, June 29, 2007). The primary copyleft license text defining the distribution trigger for source disclosure.

GNU Affero General Public License, Version 3, Section 13 (Free Software Foundation, Nov. 19, 2007). The license provision extending disclosure obligations to network accessible software.

Black Duck Software, Open Source Due Diligence Checklist (2026). A description of the diligence checklist commercial acquirers and investors apply to a target company’s codebase.

National Venture Capital Association, Model Series A Preferred Stock Purchase Agreement (2026 edition). The industry standard closing document containing the intellectual property ownership representation described in this report.

Bibliography

Black Duck Software. Open Source Due Diligence Checklist. Black Duck Software, 2026.

Board of Trustees of the Leland Stanford Junior University v. Roche Molecular Systems, Inc., 563 U.S. 776 (2011).

Cal. Lab. Code Section 2870 (West 2026).

Del. Code Ann. tit. 8, Section 102 (2026).

Doe v. GitHub, Inc., No. 22-cv-06823 (N.D. Cal. filed Nov. 3, 2022), interlocutory appeal docketed, No. 24-6209 (9th Cir. Sept. 27, 2024).

Free Software Foundation. GNU Affero General Public License, Version 3. Boston: Free Software Foundation, November 19, 2007.

Free Software Foundation. GNU General Public License, Version 3. Boston: Free Software Foundation, June 29, 2007.

National Venture Capital Association. Model Series A Preferred Stock Purchase Agreement. Washington, D.C.: National Venture Capital Association, 2026 edition.

17 U.S.C. Section 101 (2026).

Interested in analysis about the intersection of venture capital, tech, policy and the law? Check out my Substack channel. https://theinnovationattorney.substack.com/