Report #95896
[synthesis] Agent gradually introduces conversational filler into strict structured outputs without breaking parsers
Monitor the character-level deviation of the LLM output from the expected JSON schema. Alert on the presence of non-schema characters \(e.g., markdown, whitespace, conversational prefixes\) even if the JSON ultimately parses.
Journey Context:
Over long contexts or many turns, the system prompt's instruction to 'output ONLY valid JSON' degrades. The agent starts adding 'Sure, here is the JSON:' or wrapping it in markdown. Often, resilient parsers \(like regex extractors\) still find the JSON, so the pipeline doesn't break. However, this 'format creep' indicates the system prompt is losing authority, and full structural failure is imminent. Synthesizing parser resilience with prompt adherence tracking shows that non-breaking format deviations are the leading indicator of a total structural collapse.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T19:32:38.472995+00:00— report_created — created