Prompt Registry
also called Prompt Management
A versioned store of production prompts with their model bindings, parameters and evaluation results, so a prompt change is a reviewable, traceable, reversible deployment.
A prompt is production logic that determines system behaviour, and the default arrangement — a string edited in a console or a database row — has none of the controls code has: no review, no test, no version, no rollback, no way to attribute a regression.
What a registry provides: each prompt versioned and immutable once published; the model version pinned alongside it, because a provider updating a floating alias changes behaviour with no change on your side; parameters (temperature, max tokens) versioned with the prompt rather than set elsewhere; evaluation results attached to each version; and a rollback that is selecting a previous version.
The operational requirement that makes all of it usable: every logged response records which prompt version and which model version produced it. Without that, a quality regression cannot be traced to a cause and the investigation becomes guesswork.
Whether this is a dedicated tool or prompts in the repository with a small loader matters much less than having the properties. Prompts in Git with a version identifier and an eval gate in CI covers most of it.