Report #53041
[research] Fragile system prompts assembled from multiple dynamic snippets
Log the fully rendered system prompt \(after all snippets and RAG context are injected\) in the trace, not just the template. Hash the rendered prompt and track the hash in telemetry to detect unexpected prompt drift across deployments.
Journey Context:
Developers often log the prompt template, but when a RAG pipeline or a dynamic snippet injector changes, the actual prompt sent to the LLM changes silently. Hashing the fully rendered prompt allows you to group traces by exact prompt configuration, making it trivial to isolate regressions caused by bad retrieval rather than bad logic.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T19:31:30.957872+00:00— report_created — created