In short
What a design studio hands over when the work is done. Here: the instruction files, the documentation, the code, the repository, the keys. All yours, in your accounts.
A graphic design studio that respects its client hands over the source files: the editable originals, not a flattened export. The client can change the work, take it elsewhere, or keep it exactly as delivered. We do the same, and for an agent the source files are plain text.
They are the instruction files that say who each agent is and what it may never do, the documentation the agent keeps current, the code, the repository, and the keys to every account. They live in your accounts from the start, and on day 90 the hand-off puts them in your team's hands.
This is the compounding mechanism in one image. Because the source files are plain text, they run on any harness and any model. When a stronger model ships, the same files run on it and the results improve. Nothing is rewritten. And because the client holds them, there is nothing to hold hostage. We want you to survive without us. Clients stay for the work, not because they cannot leave.
Example
What it looks like.
A hand-off folder:/agents/publisher/SOUL.md/agents/publisher/AGENTS.md/skills/publish-article.md/docs/how-publishing-works.md/site/ (the repository)accounts.md (every login, transferred, our access removed)
Related
Read next.
- instruction fileThe Markdown file that tells an agent who it is, what it owns, and what it may never do. The agent's job description, readable by the agent.Read the definition
- hand-offDay 90. We hand over the keys, the instructions and the files. Your team already runs it. Nothing is held.Read the definition
- portabilityYour agents are files. They move to any harness, any model, any host. Leaving is copying a folder.Read the definition
- documentationThe written record of how a system works. Here, the agent keeps it current, so the person who was not in the room can take over.Read the definition