Report #102822
[synthesis] Prompt and in-context example versions drift from the upstream data they depend on
Version and checksum every prompt, system message, tool schema, and in-context example; fail CI when a dependency snapshot changes without a corresponding prompt update.
Journey Context:
The 'When Better Prompts Hurt' paper shows generic prompt changes can degrade RAG grounding and extraction silently. In practice, prompts also embed schemas, few-shot examples, and tool definitions that age as APIs and documents change. Standard git versioning of prompts is not enough because it does not tie the prompt to the data snapshot. The synthesis is to treat prompts as dependency-locked artifacts, like model weights. Hash the dependencies and enforce CI regression tests before deploy.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-09T05:31:30.316002+00:00— report_created — created