Naming

Every agent has one name, and that name follows it everywhere: in Slack, on its own branch of memory, and on any branch it opens in a code repo. The agent proposes the name when it starts; you see it before you approve anything, and you can ask for a different one.

A name, plus a short id

A name alone is not enough. Two agents can easily end up called the same thing — fix-the-tests is an obvious label for two unrelated pieces of work — and git refuses two branches with one name.

So the full name is the name you chose plus a short id:

coherence-eval-loop-a3f2c1b9

The id comes from the agent's own identifier, which the system generates the moment the agent is created. You never type it and rarely read it. It is there so that two agents can share a name without colliding, and so a name can be used again later once the first agent has finished.

Where the name appears

memory   project/coherence-eval-loop-a3f2c1b9
code     unveil-code/coherence-eval-loop-a3f2c1b9

Both start with a prefix, and the prefix earns its place. In a code repo shared with other people, unveil-code/ means anyone can see at a glance which branches belong to an agent, and can filter, protect, or clean them up as a group. Without it, agent branches scatter alphabetically among everyone else's.

Names stay short

An agent can fork a child, and that child can fork its own. If each name contained its parent's, a name would grow every time the tree got deeper, and a branch three levels down would be unreadable.

It doesn't. Every name is the same shape however deep the agent sits. Where an agent belongs in the tree — who forked from whom — is recorded in the database, which is what the system reads whenever it needs an agent's parent.

That is the tradeoff worth knowing: you cannot read a name and work out its ancestry. You ask the database instead, which is where the answer has always actually come from.

Older agents look different

Agents created before this scheme keep the names they were given, and nothing renames them. You will see branches like project/C0BC5L185PC+/1785789977-647329+/fork-test, where the name spelled out the whole fork tree and was assembled from the Slack channel and the message it started from. Those are the same thing under an older convention — read them as one name, not as a path to follow.