Mar 29, 2026 AI

The Identic Agent: Who Owns Your AI Twin When You Leave?

All posts

Imagine you spend six months building an AI agent trained on how you work. You feed it your decision frameworks, your communication patterns, the way you triage incidents, and the structure you use for board reports. Over time it becomes genuinely useful, and your team starts relying on it to handle tasks that previously required your direct involvement. Then you hand in your notice.

What happens to the agent?

What Is an Identic Agent?

An identic agent is an AI agent that has been trained, fine-tuned, or prompted using an individual's professional knowledge, judgement, and working patterns. Unlike a general-purpose assistant, it reflects a specific person's way of thinking and operating. It knows how you would respond to a particular situation because it has learned from the way you have responded to similar situations in the past.

Companies are already building these, sometimes deliberately and sometimes by accident. Every time someone creates a custom GPT with detailed instructions about how they want things done, builds a knowledge base from their own documents and decision logs, or fine-tunes a model on their communication history, they are creating something that sits closer to a digital twin of their professional self than a generic tool.

As AI agents become more capable and more embedded in daily workflows, the line between "a tool I configured" and "a digital copy of how I work" is going to blur considerably.

The Ownership Question Nobody Has Answered

Employment contracts have covered intellectual property, inventions, and work product for decades. If you write code on company time using company resources, the company owns it. If you develop a process or a methodology as part of your role, the company has a claim to it. This is well-established territory.

An agent trained on how you think sits in a much greyer area. The training data came from your work, and the company has a reasonable claim to that data since it was produced during employment using company resources. But the patterns and judgement the agent encodes are your professional experience, built over an entire career and not just at this particular company. You would carry those skills, instincts, and decision-making frameworks with you regardless of whether an agent existed to capture them.

Current employment law was not written with this scenario in mind. Most contracts say the company owns what you create during employment, but it is genuinely unclear whether that extends to a digital representation of your professional capabilities. Is the agent a work product, like a document or a piece of software? Or is it more like a recording of your expertise, which raises entirely different questions about consent and ownership?

The Employer's Perspective

From the company's point of view, the argument for ownership is straightforward. They invested in building the agent. It runs on company infrastructure and was trained on company data, processes, and internal knowledge. The prompts, the knowledge bases, and the workflows it was trained on were all created during paid employment. In that framing, the agent is no different from any other work product and the company owns it.

There is also a practical argument. I have written before about the risk of knowledge fragility — what happens when one resignation takes twenty years of undocumented knowledge out the door. An identic agent is, in some ways, the solution to that exact problem: the knowledge has been captured. But now the question flips. If a departing CTO's identic agent knows the entire platform architecture, the vendor relationships, the incident response playbook, and the way critical decisions have historically been made, letting that agent walk out the door with them would be equivalent to handing over the documentation and the tribal knowledge simultaneously. For many companies, especially in the period immediately after a senior departure, that agent might be one of the most valuable knowledge assets they have.

The Employee's Perspective

From the individual's point of view, the picture looks quite different. The agent encodes professional judgement that was built over an entire career, across multiple employers and roles. Your communication style, your decision frameworks, your way of assessing risk, your approach to stakeholder management — these are transferable skills you developed over decades, and they existed long before this particular employer decided to capture them in an AI agent.

If the company owns the agent outright, they effectively own a copy of your professional identity that continues working after you leave. It keeps advising, keeps making decisions in your style, keeps answering questions the way you would have answered them. You are gone, but your digital twin is still at the desk. That raises some uncomfortable questions about digital labour rights and whether your professional expertise can be cloned and used indefinitely without your ongoing consent or compensation.

There is also a chilling effect to consider. If employees know that the expertise they pour into building an agent will be retained by the company after they leave, used to train their replacement, or deployed as a permanent knowledge asset, they may be far less willing to contribute to agent-building in the first place. The most capable people, the ones whose knowledge is most valuable to encode, are also the ones most likely to recognise what they are giving away.

The Practical Problems Already Emerging

Beyond the philosophical ownership debate, there are immediate practical questions that most companies have not considered.

Liability after departure. If your identic agent gives advice six months after you leave and that advice turns out to be wrong, who is responsible? The agent was trained on your judgement, but you are no longer there to update it, correct it, or account for changes in context. The company is relying on a frozen version of your thinking that becomes less accurate over time.

Modification without consent. Can the company modify the agent after your departure? If they retrain it, update its knowledge base, or change its instructions, it is still associated with your professional patterns but now reflects decisions you did not make. In effect, they would be putting words in your mouth.

Replacement and compensation. If the company uses your identic agent to fully replace your role, eliminating the need to hire a replacement, there is a reasonable argument that your professional expertise is generating ongoing value without any ongoing compensation. Employment law has no framework for this yet, but it is only a matter of time before someone raises it.

Data protection and the right to be forgotten. Under GDPR and similar regulations, individuals have the right to request deletion of their personal data. If an identic agent was trained on data that includes your communication patterns, decision history, and professional judgement, there is a legitimate question about whether you can demand the agent be deleted when you leave. The data protection implications have not been tested in court, but they are significant.

What Companies Should Do Now

This will become a legal and HR battleground within the next few years, and the companies that have thought about it in advance will be in a far stronger position than those that are scrambling to respond after a dispute.

A Question for Every Board

If you are a CEO or board member thinking about AI agent strategy, this ownership question needs to be part of the conversation from day one. The technology to build identic agents exists now. Your employees may already be creating them, intentionally or otherwise. The legal and ethical framework has not caught up.

The question to ask your leadership team is straightforward: if our most valuable person handed in their notice tomorrow and they had spent the last year building an AI agent trained on everything they know, what would happen? If the answer involves uncomfortable silence or a shrug, you have work to do.

Read next The Death of the MSP Dashboard