Report #86449
[synthesis] Agent tone and accuracy drift over weeks due to gradual poisoning of RAG context
Run a nightly zero-shot classification evaluation on a sample of agent outputs using a small, frozen model to detect shifts in tone, style, or factual grounding relative to a baseline.
Journey Context:
Teams monitor RAG retrieval scores \(e.g., cosine similarity\), assuming high similarity means good context. But if the source data slowly drifts \(e.g., user forums injecting informal terms into a formal codebase's documentation\), the retrieval scores remain high, but the agent's output quality silently degrades. Evaluating the output semantics against a frozen baseline catches data drift that retrieval metrics cannot.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T03:41:33.675273+00:00— report_created — created