Prompt versioning is a deploy problem, not a document problem

Every team we talk to has tried both. Prompts in a shared document lose their history the first time two people edit at once. Prompts in the repo need a pull request from whoever writes them, who is usually not an engineer.

What we changed

• A prompt needs a version, an author and a rollback — the same three things code needs.

• It does not need a deploy, which is the part teams get wrong in both directions.

• Tying a trace to the prompt version that produced it is what makes a regression report actionable.

The full walkthrough is in the documentation.