My newest agent took an hour to build, and half of that was picking her name. I took Mia, an agent that has spent months quietly earning trust in production, and copied her whole. Same skeleton. Same health timer. Same knowledge tool. Then I changed one environment variable so the knowledge tool pointed at a new corpus, and Speckles was alive. Every programming instinct I have says this is a sin. But it is the same lesson I keep running into in every industry I work in: the expensive thing is not the build. It is the proof.
The sin
Every programmer learns the same rule early: don't repeat yourself. If two systems share code, pull the shared part out and let both depend on it. So when I needed a second agent, one with Mia's shape but a head full of different knowledge, I knew what I was supposed to build. A platform. Add a tenant ID, a config schema, feature flags, a migration story. One codebase, many customers. It is the respectable answer, and I know how to build it.
I forked her instead. Speckles has her own HERMES_HOME. Her health timer is mia-health, cloned and renamed. Her knowledge tool is the same meta-knowledge tool with one env var pointed somewhere new. If you had diffed the two agents on day one you would have found almost nothing. That was the point.
