Report #46998
[synthesis] Context window pressure causes selective amnesia leading to schema drift in multi-step generation
Externalize schemas and contracts to a persistent scratchpad or vector store; force the agent to read the schema from the external source before every generation step, rather than relying on the conversation history.
Journey Context:
As context windows fill, LLMs suffer from 'lost in the middle' attention degradation. An agent might define a Pydantic model or API payload in Step 1, but by Step 7, the model is truncated or attention is diffused. The agent hallucinates a slightly different schema \(e.g., user\_id vs userId\). This micro-drift compiles but breaks at runtime. Relying on in-context memory for strict schemas is a common mistake; the tradeoff of an extra read-tool call per step is negligible compared to the cascading integration failures of schema drift.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T09:21:26.777327+00:00— report_created — created