Satya brings up an important point around the compounding of systems and learning that AI and agentic workflows enable. He makes the case for how this will happen inside companies to make the firm smarter introducing the term “token capital” as somewhat of a modern update to Coase’s Theory of the Firm.
But people have always compounded too. You learn how to write the memo, spot the weak assumption, scope a feature, read the room. When you leave, you take that with you. Nobody ever proposed you should leave it behind, because the knowledge lived in your head and your head went where you went.
As we get deeper into the AI era, agents are quickly starting to change the container for that knowledge and compounding of capabilities.
My agent is a folder of markdown files: instructions, skills, memories. It's been compounding for the better part of a year. Some of those skills I built on my own. Some were sharpened at work. If I zip that folder and carry it to the next job, every abstract boundary question becomes a file question: what can live where, what transfers ownership. Whether the agent learned something confidential is not philosophical, it is a grep.
The reason this is harder than it looks: the old system worked because human memory is lossy. You left a job with patterns but not databases. Biology sufficiently redacted the specifics of process and large corpuses of confidential information, because there’s only so much detail most of us can carry in our heads. Trade secret law tolerated the transfer because it arrived pre-sanitized by forgetting. Forgetting was load-bearing, and agents broke it.
A personal agent can carry too much out. But a corporate agent that captures everything and transfers nothing at offboarding doesn't just protect secrets, it confiscates professional growth. If every company does that, the talent pool we all hire from gets shallower.
And there's a deeper question that current policy doesn't touch. If I build a skill on my own time and then use it at work because it makes me better at my job, does the company acquire a claim? If not, what stops me from developing everything personally? But if employers respond by requiring all work through corporate agents, the worker's compounding loop gets locked inside the firm. The question of who owns what is not one line. It's four separate questions: what the agent can do (authority), what it can see (data), what it remembers (memory), and what it carries forward as reusable procedure (skill). Authority and data are relatively easy to handle through existing IT tools and policies; memory and skills are where it gets messy, because what were formerly lossy, imperfect processes are increasingly being crystalized in a way that makes them formal and precise.
The more we come to rely on our agents, the more challenging and urgent these questions will become.