Portability is what makes everything else honest. The agents we build are instruction files, documentation, and code, and none of it depends on our being there. They run on a harness that can be replaced. They call a model that can be replaced. They can be hosted by us or by you.
This is why every engagement ends in a hand-off on day 90, why nothing after it is required, and why running on our rails is not a trap. There is nothing to hold hostage.
It is also why the system gets better over time. Because the files persist and the machinery underneath is swappable, every improvement in models or harnesses is an improvement to your system, for free.
Example
What it looks like.
portability.mdplain text
What leaving looks like: a folder with the instruction files, the docs, and the code; the accounts transferred; our access removed. The agents run the next morning without us.Related
Read next.
- source filesWhat 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.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
- harnessThe software that runs an agent: loads the instructions, connects the tools, keeps the schedule, delivers messages. Replaceable. The instructions are not.Read the definition
- railsOur hosting, email, backend, and models, run for you. One bill, nothing to babysit, always on current software. Your files stay portable.Read the definition