On September 16, 2026, the Ninth Circuit affirmed the dismissal of a claim that copyright management information was removed from code. That information includes author names, copyright notices, and license terms.
The case is about code. The lesson is about where your name lives.
Your name on your framework is a label. It is not a record.
According to the Fractional Work Report 2026 from Fractional Jobs, 60% of fractional engagements last six months or longer.
Four mistakes keep your name on your copy and off theirs.
How many of us have handed a client our best framework and never read the contract? I invite you to consider what that contract says today.
Mistake 1: Treating the name on the file as the record
The mistake. Your name is in the footer. Your logo is on the cover. You treat that as proof of authorship.
What it costs. The footer stays on your file. The client's version is a new file. It starts without your name.
The correction. Locate the dated original you control. The first-created file, the first email that sent it, or the version history. Record the date and where it lives. Then log each time you see it in use.
You can say it, but unless it's documented, it really doesn't count.
See the difference?
Translation: a name on the file is a label. A dated original plus the written terms is a record.
Mistake 2: Never locating what the signed terms say
The mistake. You signed the agreement. You have never located what it says about ownership or reuse.
What it costs. You cannot point to a term you have never read. Neither can anyone else.
The correction. Find the signed agreement. Record its name and date. Quote the ownership, license, attribution, or reuse language, with its section number. If the agreement says nothing, write "silent."
Do not interpret it. What a clause means, and whether it holds, is a question for counsel. This post is not legal advice.
I have negotiated contracts with 41 named enterprise organizations. The signed terms are the page both sides can point to.
Mistake 3: Filing the framework as if it belongs to the engagement
The mistake. It lives in the client folder, beside the deliverables they paid for. You tell yourself it was part of the job.
What it costs. Once it carries the client's logo, work you brought in and work the client paid for look the same. The date is what separates them.
The correction. Find the earliest dated evidence that the framework existed. Set it beside the engagement start date. Write yes or no: did it exist before?
Mistake 4: Rebuilding it at renewal
The mistake. You plan to gather the proof when the renewal arrives.
What it costs. By then your access may be gone. The client's version is the one people use.
The correction. Log each sighting when it happens, in the ordinary course of the work. Record the date, the document, and whether your name was on it. This is a filing habit. It is not a decision about when to raise anything.
Do not copy client-confidential deliverables off client systems. Your register points to the evidence. It does not have to hold it.
None of these is a character flaw. Nobody teaches this. Up until now.
The example: Doe v. GitHub
The case is J. Doe 1 et al. v. GitHub, Inc., et al., No. 24-7700. The Ninth Circuit filed its published opinion on September 16, 2026. A group of programmers sued GitHub, Microsoft, and several OpenAI entities.
The programmers published copyrighted code on public GitHub repositories, subject to various licenses. The opinion notes that much public GitHub code carries open-source licenses. It says one of the most common conditions is attribution. Under that condition, any copy or derivative of the code must carry a copy of the license, with the author's name and copyright notice.
The programmers alleged that GitHub Copilot and OpenAI's Codex sometimes produce their code without that name, notice, or license text. They sued under DMCA Section 1202(b), which bars removing or altering copyright management information, and for breach of contract.
The Ninth Circuit affirmed. It held that the programmers' own allegations show the tools create new works. A new work that never contained the copyright management information has not had it removed or altered. The court also said a near-identical copy with the notice missing can support an inference of removal.
Here is what the court did not decide. It expressed no view on copyright infringement. It made no finding that any output copied any plaintiff's code. No damages have been awarded.
Two breach-of-contract claims remain pending in the district court. They are undecided. No breach has been found.
This case concerns code and a federal statute. It is not an employment, pay, or consulting-contract ruling. It says nothing about your contracts. The lesson is where attribution lives.
Translation: the name stayed on the original. It did not travel into what was built from it.
Your template
Copy this. Fill it in one sitting. One block per framework, up to three.
AUTHORED WORK REGISTER | Dated: ________ Framework name: ______________________________ Dated original I control: ____________________ (type, date, where it lives) Existed before this engagement? yes / no Earliest evidence date: ________ Engagement start date: ________ Client: ______________ Date delivered: ________ Agreement name: ______________ Date: ________ Section: ______ Ownership, license, attribution, or reuse language (quoted, or "silent"): ______________________ Seen in use since (one line each): Date: ______ Document: ______ My name on it: yes / no Date: ______ Document: ______ My name on it: yes / no Missing: ______________ Who holds it: ______________
What this does not do
This register shows what you authored, when, where the original lives, and what the signed terms say.
It does not tell you what the client's continued use is worth.
That is valuation. Documentation is not valuation. A well-documented career is just a well-organized donation.
Pick the one framework your client uses most. Find the signed agreement. Quote the clause, or write silent.
The record is step one. What it is worth is the next step. Lab Tools
Thank You; It's True™