One source of truth, so an update reaches everyone using an agent

Agents drift into copies. Someone tweaks the instructions for their team, someone else exports a version to a document. The fix is boring – one place where each agent lives, a version number, an owner who publishes, and nobody running a private copy.

By Matthew Steele4 min read28 October 2026

A whiteboard listing six tools with version numbers and owner names, photographed at an angle in a quiet office
Illustrative scene, not a customer's premises.

How the copies happen

Nobody sets out to make 5 versions of the quoting assistant. It goes like this. Sales find the instructions too formal and soften them for their own use. Someone exports the prompt to a document "so it's not lost", and a new starter gets given the document. A second office builds its own because it can't see the first one. About 6 months later nobody can say which version is current, and a fix to one of them reaches roughly a fifth of the people who need it.

We don't think that's a people problem. It's just what happens when an agent has no home.

The four parts

One home against copiesOn the left, one agent at version 1.4 in one home, with four teams using it in place and a change note going to all of them. On the right, in grey, four copies of the same agent at different versions in different places, with updates that never arrive.One homeQuoting assistantversion 1.4, one ownerSalesServiceSecond officeNew startersUsed in place. One change note reaches everyone.Copiesv1.1 in a documentv1.3, softenedv1.0, exported"my version"Which one is current? Nobody knows.A fix reaches a fifth of the people who need it.
One home, and everyone uses it there. An update never finds its way to a copy.
Part What it means in practice
One home Each agent lives in one place everyone who uses it can reach. They open it there and never paste it anywhere else.
A version A number that goes up when the owner publishes, shown where people use it, so "which version are you on?" has an answer.
Saved test cases 10 to 20 real examples with the answer the owner expects. Every change gets run against them before it's published.
A change note One or two sentences per version. What changed, why, and what to do differently, if anything.

This isn't a technical standard so much as a habit, and keeping it is the owner's job.

The publishing routine

A change request comes in, from a user or from the owner's own sample check. The owner makes the change in a working copy, runs the saved test cases, reads the ones that came out differently, and decides. If it's right, the version number goes up, the change note gets written, and the old version is kept for a week in case something was missed. Then one message to everyone who uses it: "Quoting assistant is now version 1.4. It asks for the delivery postcode before it drafts. Nothing else changed."

That's the whole routine and it takes about an hour. The part people skip is the message – which is the only part the users ever see.

The person who wants their own version

They'll turn up, and usually they've got a point. Turn the private copy into a request: what would you change, and why? Three ways it goes:

  • The change is good for everyone. The owner publishes it.
  • The change is only for their team. The owner adds a setting, a choice the agent asks at the start, instead of a copy. One agent, two behaviours, one home.
  • The change isn't a good idea. The owner says so, and why.

What doesn't happen is a second copy. Once there are two copies there's no source of truth, and the next request produces a third.

If your platform can't do this

Some tools make the habit easy: shared agents, versions, a changelog, a way to tell users. Some make it nearly impossible, and the drift is built in. If you're keeping the current version in a document and asking people to paste it in, you're running on hope. How to pick one platform and stay on it is in keeping agents on one platform.