Prompt templates need semantic versioning, not silent edits
Treat a prompt template like production code. Record the identifier, version, owner, model assumptions, expected input shape, output contract, evaluation set, and change reason.
Use a major version when the task or output contract changes, a minor version for compatible behavior improvements, and a patch version for wording changes that should not affect the contract. Even small edits should run against the existing evaluation set.
Do not overwrite the active prompt without preserving the prior version. Rollback becomes impossible when the only history is a chat message or an edited database row.
- Category
- Product
- Platform
- Web