Who Owns It, and Who Invented It?
Ownership and inventorship are two different questions, and confusing them is how patents get lost. Ownership asks who holds title, and it turns on contracts. Inventorship asks whose contribution made the invention, and it turns on facts about who did what. An assignment fixes the first. It does nothing for the second.
Four decisions mark the boundaries. Each is read from the opinion itself, with quotations checked against the court's own text.
Most of what goes wrong here goes wrong long before anyone talks to a lawyer. A contractor helps debug a subsystem. A professor's university has a bylaw nobody read. A model suggests an approach and a person builds on it. None of those feel like legal events at the time, and all three have destroyed or nearly destroyed patents.
That is why this cluster sits on an engineering site rather than a law firm's. These mistakes happen inside engineering and business workflows, which means the people best positioned to prevent them are the people writing the code and signing the vendor agreements.
The Four Decisions
What Ties Them Together
A promise to assign is not an assignment. In Omni MedSci, a university bylaw said inventions "shall be the property of the University." The Federal Circuit held that language transferred nothing. It was a statement of intent about the future, not a present transfer, so the inventor still had title to give. The court read the bylaw as a whole rather than resting on any single phrase.
Naming the wrong inventors can end the patent. In Fortress Iron, two supplier engineers were coinventors and were not named. One could be added later. The other could not be located, and because an omitted coinventor must receive notice before a court corrects inventorship, the patents could not be fixed. A patent that names the wrong inventors and cannot be corrected is invalid. Two patents, gone.
An inventor must be a human being. In Thaler, the Federal Circuit held that the Patent Act's word "individuals" means human beings, so an AI system cannot be listed as an inventor. It decided that and nothing more, and said so explicitly.
Assigning a patent can limit what you may later argue about it. In Minerva, the Supreme Court kept assignor estoppel but tied it to contradiction, so it reaches only as far as what the inventor actually represented in assigning. This is the case that matters when a founder leaves and competes, and it sits here rather than under filing deadlines because the operative document is the assignment.
What These Pages Do Not Decide
These are descriptions of what courts held. They are not advice about any particular agreement, contributor, or application.
- Whether a specific agreement transfers a specific invention is contract interpretation, governed by state law that varies, and it belongs to a lawyer reading the actual document.
- Whether a specific contractor, vendor, or reviewer is a coinventor is a legal determination made on the facts and the claims. It is one of the determinations where being wrong costs the whole patent.
- Whether an invention made with AI assistance is patentable is an open question. Thaler expressly did not decide it.
Educational, not legal advice. Every quotation on these pages is verified against the court's own opinion, but a holding is not a rule about your facts. Consult a qualified patent attorney about your specific agreements, contributors and applications.
Related
- What recent patent decisions add up to, the cross-case synthesis and the index to every case page.
- Co-founder IP ownership: getting title clean before it matters
- IP protection checklist for engineering teams
- A completed software invention disclosure