Who owns the code? AI code == no author == no copyright

Aug 19, 2026 05:21 AM - 4 weeks ago 4

for founders, engineering leaders, and counsel shipping AI-generated code

AI code == no author == no copyright

Under existent U.S. copyright law, purely AI-generated codification has nary quality author, truthful it cannot beryllium copyrighted and cannot beryllium defended arsenic an plus you genuinely own.

ownership.sh zsh

12345678

~/startup git:(main) $ whoami --code checking authorship of ./generated ... # purely AI output, nary quality authorship connected record author: none copyright: not eligible status: unowned, undefendable ~/startup git:(main) $ measure --my-risk

Our guidance applies to codification generated from each AI tool

the 4 things teams miss

Four ways AI codification puts ownership astatine risk

Ownership is not a formality you hole later. It is decided by who authored the expressive work, statement by line.

01own_the_output.ts

123

doYouOwnTheOutput

// verdict: noCode written wholly by an AI instrumentality has nary quality author, truthful nether U.S. copyright rule it cannot beryllium copyrighted, and you cannot ain it.

02vibe_coding.ts

123

vibeCodingRealExposure

// the AI did the expressive workWhen you fto the AI make the imaginative decisions, the codification is not human-authored, and codification that is not human-authored is not a protectable asset.

03mixed_codebase.ts

123

mixedCodebases

// you ain only what you authorIn a codebase that mixes quality and AI work, you ain the parts a personification meaningfully wrote. The AI-generated parts enactment unprotected until a quality reworks them.

04open_source.ts

123

openSourceIsNotNoCopyright

// a licence needs an proprietor to assistance itOpen root is not the aforesaid arsenic nary copyright. A licence only holds if personification owns the code, truthful an open-source licence placed connected axenic AI output has thing to enforce.

the lawsuit law, arsenic a perpetrate history

Four anchors already merged into the record

These are not predictions. Each is simply a caller determination aliases study that hardened the rule: nary quality author, nary protection.

branch: us-copyright-law

commit b7e1f04 Author: Supreme Court of the United States Date: Mar 2026

Supreme Court denied cert successful Thaler; human-authorship norm stands

The Court declined to reappraisal the D.C. Circuit's ruling, leaving the quality authorship request arsenic settled U.S. copyright rule unless Congress acts.

+ quality authorship: settled law
- purely AI-generated code: still not eligible

commit a1f0b7c Author: Thaler v. Perlmutter Date: Mar 2025

Works created wholly by AI are not eligible for copyright

The tribunal confirmed that only humans tin clasp copyright protection; a activity generated wholly by a instrumentality has nary writer the rule will recognize.

- machine-authored work: protected
+ machine-authored work: not eligible

commit 6d24e9a Author: Thomson Reuters v. Ross Date: Feb 2025

First determination to cull a fair-use defense for AI training

The first ruling to cull a fair-use defense for utilizing copyrighted worldly to train an AI, narrowing a shield galore teams assumed they had.

- training connected copyrighted data: adjacent use
+ training connected copyrighted data: defense rejected

Only meaningful quality imaginative input is eligible for protection

The Office stated that only portions of a activity carrying meaningful quality imaginative input are eligible for protection. The AI-generated remainder is not.

+ human-authored portions: protected
- AI-generated portions: unprotected

next_steps.md

run the cheque earlier your adjacent release