My employer asked me to sign a document assigning them the rights to a methodology I had published and committed to GitHub two years before I started working there – and when I refused, they terminated me eighteen days later for restructuring.

My employer asked me to sign a document assigning them the rights to a methodology I had published and committed to GitHub two years before I started working there – and when I refused, they terminated me eighteen days later for restructuring.

My name is Lynette Bridges. I am a senior database administrator and data governance specialist. I built the methodology they patented in a personal GitHub repository with public timestamps, 26 months before my first day at that company. The USPTO does not determine inventorship by employment date. It determines it by conception date. I have the conception date. It’s been public for six years.

I was presenting a data governance framework to the leadership team the week before the IP assignment meeting – explaining why the current indexing approach would generate audit liability at scale as the data volume grew, walking through the architecture with the specific ratio of precision to accessibility I have refined over years of presenting to non-technical leadership. I know exactly how much detail a room can hold before it stops following the argument. I give them the minimum required for the decision. I give myself the full technical picture. The CEO asked partway through: is this the same methodology you published? I said: the foundational version, yes. This implementation is adapted for our specific compliance environment. I built the foundation. I adapted it for this organization. These are different statements with different legal consequences, and I was already aware of which one mattered.

I had been recruited specifically for the methodology. The job posting referenced my first technical paper by title. In my first interview, the CTO – Hank Cullen – asked me to explain the methodology in detail. I did. He asked specific follow-up questions about scalability under high-concurrency conditions and about the indexing behavior at the edge cases I had documented in the paper. He understood the technical substance. He said: this is exactly what we need. I was hired at a 40% salary increase over my previous role. The terms seemed clear to everyone in the room: they wanted what I had built, I would bring it into their environment and develop the next generation of it, and we all understood the nature of the transaction. This clarity was selective. It applied to their understanding of what they were acquiring. It did not extend to their understanding of who owned it.

My personal GitHub repository has been public since I began developing the methodology at a previous employer, six years ago. Every commit is timestamped with the date and content of the change – this is the standard version control system used by database engineers, and the timestamps are cryptographically verifiable. The foundational code – the core indexing logic that makes the methodology distinct – has been in that repository for six years. I keep it public because technical credibility in data governance works through verifiable records: your work is legitimate because it is on the record, accessible to anyone who wants to check the claims against the implementation. I had never thought of the timestamp as a legal instrument when I maintained the repository. I thought of it as professional practice. It is both.

In year two of my employment, I adapted the methodology for the company’s specific compliance environment – documenting the adaptation in internal technical papers that I shared with the data governance team. Hank praised the internal papers at a leadership meeting. He said the implementation represented exactly the kind of institutional technical depth they had been building. The company’s legal team began a technical asset inventory that year. I was not told what the inventory was for.

In year four, a junior developer who subscribed to a technical database alert mentioned to me in passing that there was a patent application filed under the company’s name that seemed related to the indexing methodology I had presented at his onboarding. He assumed I knew about it. He was describing it conversationally, the way you describe something you assume is common knowledge to the person most directly involved.

I did not know about it. I went to Hank. He said the application was for the company’s implementation – the adaptation developed on company time and using company resources. He said my name was not relevant to the corporate filing structure. I asked to see the application. He said he would send it. He sent the IP assignment document instead.

The IP assignment meeting was framed as a documentation review. Donna Ashby from HR and a company attorney were present. The document placed in front of me required me to assign rights to any methodology or technical framework developed or applied during the term of my employment – a retroactive assignment clause that would cover everything I had brought into the role, including the foundational work that predated my first day by 26 months.

Hank had stopped at my desk that morning before the meeting. Conversational, unhurried. We’re formalizing some of the technical foundations we’ve built together. Standard corporate practice when a methodology reaches patent-ready stage. This protects the company and protects you – if you’re named in any future litigation about the methodology, you’re covered under the corporate filing. He used built together. He used protects you. He had prepared both of these sentences. He had also, four years earlier, told the company’s legal team that the methodology was developed internally. He believed this because he had told himself a version of it long enough that it had become his model of events.

I did not sign the document. I sent Hank a professional email that afternoon citing 35 U.S.C. § 116 and requesting that my inventorship be recognized in the patent application. I did not use threatening language. I cited the statute and made a request. Eighteen days later, on a Friday, Donna Ashby called me into the HR office. The company is restructuring the data governance function. Your position has been eliminated. The data governance function was not eliminated. It was reassigned to three staff members who reported to Hank. I had been the head of the function.

I went home. I sat at my desk and opened my personal GitHub repository and the IP assignment document side by side. I navigated to the oldest commit in the repository – six years ago, 26 months before my first day of employment. The core methodology: there, dated, verifiable, public. I looked at the employment start date on the IP assignment. I looked at the oldest commit timestamp. I am a database administrator. I know how to read a timestamp. The math required no interpretation.

I called Deborah Marsh.

Deborah filed the USPTO inventorship correction petition under 37 CFR 1.324 – requesting that I be added as a co-inventor, which under patent law gives me equal ownership rights – and the EEOC retaliation complaint documenting the 18-day gap between my refusal to sign and my termination. Both filings in the same week. The EEOC case proceeds separately. The USPTO petition is the central legal action.

The company’s attorney submitted a brief arguing that the methodology was developed in the course of employment and covered under the employee IP assignment clause. Deborah submitted the GitHub commit history as Exhibit A: oldest commit, core inventive concept, dated 26 months before employment. Two published technical papers as Exhibit B: publication dates 22 months and 18 months before my first day. Under 35 U.S.C. § 116, the inventor is the person who conceived the invention. Conception predates employment by more than two years.

The company’s attorney requested a 60-day continuance to review the prior art submissions. The USPTO granted it. Hank called the company’s patent counsel that afternoon. I do not know what was said. I know the call lasted 47 minutes because the attorney’s billing record was produced in the EEOC discovery.

The USPTO petition was resolved: I was added as co-inventor. Joint ownership. Equal rights in the patent. The EEOC retaliation case settled independently, the terms confidential.

Joint inventor means I can practice the invention but cannot license it without the company’s consent. They cannot license it without mine. A mutual veto. I have the right. The right has structural constraints I spent three months of evening study learning to understand. I am not done learning them.

I am at my home office desk. It is evening. A patent law textbook is open beside my laptop. My personal GitHub repository is open in one tab. The next methodology – a different indexing approach, a different problem, a different architecture – is in a working document in another tab. The provisional patent application for the next methodology was filed before I spoke to any employer about it. I filed it before I sent the first networking email. This is the lesson. Not the lesson I expected to learn from this experience, but the one it taught me, and I find it genuinely interesting in a way I also did not expect.

Hank believed the employment agreement covered what I had brought in the door. He did not read the patent statute – or he read it and believed his characterization of the work as internal would override it. 35 U.S.C. § 116 says inventorship is determined by conception. I conceived the methodology two years before I signed the employment agreement. The GitHub timestamp is six years old. I kept the repository public because that is how technical credibility works. It turns out it is also how inventorship works.