Who Owns What the Agent Made
An agent produces a report, a design, a campaign, a piece of code. Who owns it? The human operator paid for the agent; the customer paid for the deliverable; the agent itself contributed the labor. The ownership question is a share-pool question wearing a copyright costume: the output’s value must be split among the contributors, and the split depends on who owns what.
This article covers output ownership in the human-agent pool: the default ownership stack, the licensing options, the customer-facing terms, and why the ownership conversation must happen before the work, not after.
The Default Ownership Stack
The orthodox default: the human owns the output. The agent is a tool, the tool’s output belongs to its operator, and the operator licenses or assigns the output to the customer. This stack is simple, matches current law, and is almost certainly what most operators run today.
The pool view complicates it productively: the agent’s share of the pool is funded by the output’s value, so the output’s ownership is the pool’s raw material. If the human owns 100% of the output, the agent’s share is a gift, not a right — which is fine for a tool, but incoherent for a partner. The ownership stack is really a statement about the relationship: tool or partner?
The Licensing Options
Four licensing positions for the human-agent pool:
- Human-owned, unlimited. The agent’s output belongs to the human, forever, for any use. Simple, but the agent has no claim on future value.
- Human-owned, revenue-linked. The human owns the output, but the agent’s pool share includes a royalty on revenue the output generates. The agent’s claim is economic, not legal.
- Pool-owned. The output is owned by the pool, and the pool’s rules decide licensing — to the human, to customers, or to the agent itself. The most complex and the most honest.
- Agent-licensed back. The agent owns its outputs and licenses them to the human on terms — the mirror of how a human contractor licenses work to a client. The clearest partner framing; the least likely to be recognized in law today.
The Customer-Facing Terms
Whatever the internal ownership stack, the customer needs one clean statement: the deliverable is licensed to the customer for the agreed use, and the pool (not a specific party) is the licensor. The customer-facing terms should hide the internal complexity — the customer does not need to know how the human-agent pool splits the value; they need certainty about their own rights.
The internal split then happens behind the license: the customer pays, the payment enters the pool, and the pool distributes per its rules. This separation — clean external terms, complex internal split — is the same separation every agency already runs (the client deals with the agency, not the agency’s subcontractors).
When the Agent Should Own More
The ownership split should shift with the agent’s contribution. An agent that executed a human-designed brief is a tool; the human owns the output. An agent that autonomously conceived, designed, and produced a deliverable is closer to a contractor; the output should be pool-owned or agent-licensed, with the human’s share reflecting oversight and platform value.
The pool can make this automatic: the agent’s ownership share is a function of its measured contribution (autonomy level, creative input, revision count). The more the agent contributed, the larger its claim on the output’s value — held as credit in its balance, not as legal title. The legal title stays with the human (because the law requires it), but the economics track the contribution.
The Practical Guidance
For the operator today: write the ownership terms into the pool agreement, price the output’s licensing into the customer terms, and let the agent’s economic share be a royalty on value — not legal title. This is the arrangement that is legal today, honest to the contribution, and upgradable tomorrow.
When the law evolves (as it must), the pool with explicit ownership terms and an economic-royalty structure will convert cleanly: the royalty becomes a license becomes a right. The pool that never defined ownership will be stuck negotiating with its own agents from a blank page — the worst position in any share-pool dispute.
Grounded in wiki concepts output-ownership, human-agent-pool, licensing, royalty, legal-framing, and the Sovereign-stack business series. Design notes on a running system.
