Your VP of Growth left the company eight months ago for a direct competitor. The competitor offered her a 30 percent raise, a signing bonus, and a title bump. She accepted. Her employment agreement at your company included a 12-month non-compete, enforceable in your state, signed and witnessed in 2021 when she was hired. The non-compete prohibits employment at any “Competing Business” during the 12-month period, defined to include your top six competitors by name.
She joined the competitor anyway.
Your CEO called outside counsel. Outside counsel sent a cease-and-desist. The competitor’s counsel responded that the VP was working on different products, in a different market segment, in a non-overlapping geography. The dispute went into a 90-day standstill while both sides mapped scope. [S: 90 days of standstill is an admission.]
Eight months later, your CRO forwards you a screenshot. The competitor’s growth team is running a Claude project that looks suspiciously like the one your VP built at your company. Same system prompt structure. Same objection-handling playbook. Same scoring rubric for inbound leads. Even the same Easter eggs your VP wrote into her custom instructions.
You forward the screenshot to outside counsel. Outside counsel calls you back at 4:30 p.m. and tells you the screenshot is interesting and probably evidence of nothing actionable. The non-compete prohibits employment. Not skill replication.
This is the story of every senior employee transition in 2026 with an AI-built skill. It is happening right now at yours.
What the non-compete actually covers
A non-compete is a contractual restriction on the employee’s ability to work for a competitor for a defined period after employment ends. The remedy for breach is injunctive relief (the employee is barred from the new role) and damages. The doctrine has been on the books for a century. The mechanics are stable.
The contract was drafted to prevent two things. The employee bringing customer relationships to the new employer. The employee bringing institutional knowledge to the new employer. Both were assumed to require the employee’s physical presence at the new employer’s office. The contract reaches the presence.
It does not reach the artifact.
The artifact left when the employee did. The artifact may have been built at home, on a personal Claude account, with a library the employee assembled from her work product. The artifact does not require the employee to be employed anywhere to function. It runs in the new employer’s Claude tenant on day one of her start. The new employer benefits from the artifact whether or not the employee is at her desk.
The non-compete bars the employment. The employment was the trigger for the artifact’s deployment, not its source. The contract is a closed door on a building that does not contain what the contract was meant to protect.
What changed
Three things, all in the last 24 months.
State-by-state fragmentation accelerated. California has long banned employee non-competes. In 2024, Minnesota joined. New York’s bill stalled but the AG’s enforcement guidance treats most non-competes as presumptively unenforceable. Texas tightened its standard. Florida loosened its. The map is now a patchwork of seven different rules. [M: state by state. Plan for the worst.]
The FTC’s 2024 ban tried to set a federal floor. The rule prohibited most non-competes nationwide. The Northern District of Texas struck it down in August 2024. The Fifth Circuit affirmed. The Supreme Court declined to take it up. The federal floor is enforcement uncertainty.
The skill emerged as a distinct asset. A senior employee leaving for a competitor in 2018 brought their head and their relationships. A senior employee leaving in 2026 brings their head, their relationships, and the artifact. The artifact is a third thing. The contract that was drafted to address the first two does not address the third.
Why this is harder than it looks
A non-compete dispute used to turn on whether the new role was “competing.” That question has a fact-driven answer: same customers, same products, same geography. Discovery is bounded. Evidence is documentary. The contract reaches the answer.
A skill dispute turns on whether the artifact deployed at the new employer is derived from material taken from the old employer. The question is technical, latent, and contested at every step.
Who built it? The employee at home. The employee on a company laptop. The employee on a personal Claude account. The new employer’s engineering team that re-implemented the prompt the employee remembered. The new employer’s contractor who reverse-engineered a public-facing version. Each version of the answer carries different doctrinal consequences.
What does it contain? The system prompt that “looks like” the old prompt. The library that “feels like” the old library. Embeddings that “behave like” the old embeddings. Pattern matching is not the same as proof.
Where does it run? A personal Claude account the employee retains. The new employer’s enterprise Claude tenant. A self-hosted fine-tuned open-weight model on the new employer’s infrastructure. Each location requires a different theory of access for discovery.
Who has standing? The old employer for breach of non-compete and trade secret misappropriation. The old employer’s customers if their data is in the library. The vendor (Anthropic, OpenAI) if its terms of service are implicated. The new employer’s investors if the dispute affects the value of the company.
The doctrine has not adjusted. The remedies were designed for the bounded fact pattern. The skill dispute is unbounded.
How to control for it before the departure
Five things. Do them at hire, not at departure.
- The non-compete is not enough. Pair it with a robust PIIA that names AI artifacts as company property. System prompts. Custom instructions. Project configurations. Fine-tuned weights. Embeddings indexes. Retrieval libraries. Each one assigned to the company on creation, by name, with no carve-out for personal-time work.
- Add a separate AI artifact return covenant. On separation, the employee certifies under penalty of perjury that all AI artifacts created during employment have been returned to the company and that no copies, derivatives, or refinements exist on personal accounts. The covenant does not stop the conduct. It creates the record. [S: the PIIA and the return covenant do the work. The non-compete doesn’t.]
- Lock down the personal Claude account. Acceptable-use policies that block personal accounts on company networks. Enterprise SSO enforcement. Admin logging. Audit trails that survive the employee’s departure. None of this prevents the employee from working at home on a personal account. All of it shifts the burden of proof onto the employee at the litigation stage.
- Bonus structure that vests over the artifact. A retention bonus tied to the employee’s contribution to the company’s AI tooling, vesting over time, forfeitable on departure. The bonus is an economic check on the artifact-replication play. Most companies have not added one. The ones that have are getting fewer disputes.
- Have the employee sign a non-derivative covenant. A separate agreement that prohibits creating, anywhere, at any time, AI artifacts derived from the company’s confidential information or tooling. The covenant is broader than the non-compete. It survives the non-compete window. It is the contract that actually reaches what you are trying to protect.1
If you’re mid-raise and have not modeled the stack against your priced round, that conversation is worth having before the next check clears.
Talk to a Talairis attorney →How to litigate it after the departure
Four moves. Make them quickly, in order.
- Send a preservation letter the day you suspect. To the employee, the new employer, and the AI vendor. Cite the non-compete, the PIIA, the DTSA, and the vendor’s terms of service. Specify the artifacts you believe were taken. The letter starts the clock on willfulness and creates the discovery record.
- Move for expedited discovery into the new employer’s Claude tenant. The threshold question is access. If the new employer used the same vendor as the old employer, the vendor can produce logs of project creation, system prompt content, library uploads, and queries. Most companies do not move fast enough on this. The vendor’s retention windows are short.
- Engage forensic experts on the artifact. A system prompt is text. Two system prompts can be compared for substantial similarity, just as two pieces of source code can. The doctrine for software clean-room comparison maps onto AI artifacts almost cleanly. Get an expert who has run both kinds of analysis.
- Plead inevitable disclosure where the state recognizes it. Inevitable disclosure is the doctrine that a senior employee with knowledge of trade secrets cannot help but use that knowledge in a sufficiently similar role at a competitor. The doctrine is contested in many states and rejected outright in California. Where it survives, it is the cleanest theory for a skill case. The artifact is the proof that disclosure was inevitable. [M: inevitable disclosure is the workaround where the non-compete fails.]2
Get counsel before the next senior departure
The non-compete was a contract for a world where the employee was the asset. The skill changes that.
The artifact is the asset.
The artifact crosses the line the contract was drafted to hold.
The new employer has the artifact. The old employer has the contract. The contract reaches the employment. The artifact reaches the next quarter.
This is not a question for the corporate counsel who drafted your non-compete in 2019. Not for the IP partner whose AI experience is a CLE webinar. Not for the labor lawyer who has handled non-compete disputes but never seen a system prompt.
Find counsel who has read a system prompt. Counsel who has run forensic comparison of AI artifacts. Counsel who has moved for expedited discovery into a vendor tenant. Counsel who has plead inevitable disclosure in a state that still recognizes it.
Find them now.
- The state-by-state map of non-compete enforceability is a moving target. California, North Dakota, and Oklahoma have long banned employee non-competes. Minnesota joined in 2024. New York is pending. Texas, Florida, Massachusetts, and Illinois have varying enforceability standards. The FTC’s 2024 nationwide ban was struck down by the Northern District of Texas. The map is a patchwork. Plan for the worst-case state. ↩
- The cleanest skill-dispute case starts with two screenshots. The employee’s old project at the prior employer. The competitor’s new project at the new employer. Both system prompts. The pattern match is forensically obvious. The contractual hook is whatever your team drafted in 2019. The gap between them is the entire suit. ↩
