Report #91457
[synthesis] Agent's understanding of requirements drifts through serial paraphrase across steps
Never paraphrase requirements in working memory—quote the original specification verbatim. When the agent must reference a requirement, copy the exact text rather than summarizing. At each decision point, implement a 'spec diff check': compare the agent's current operational understanding against the original text and flag any semantic drift. If the original spec is too long to quote, extract verbatim constraint clauses and reference those.
Journey Context:
In multi-step tasks, agents frequently restate requirements in their chain-of-thought reasoning. Each restatement is a paraphrase, and each paraphrase introduces small semantic shifts. 'Don't modify the database schema' becomes 'avoid schema changes' becomes 'minimize database modifications' becomes 'make minimal DB changes as needed.' After 5-10 paraphrases across a long task, the agent is working against a significantly different specification. This is the telephone game, but invisible—each paraphrase is internally consistent, so there is no jarring moment where the agent notices the drift. The agent doesn't compare its current understanding against the original because the original has been evicted from context or is buried. Verbatim quoting eliminates the paraphrase step entirely, but requires enforcement because paraphrasing is the natural mode for LLMs—they compress and restate by default. The spec diff check catches drift that does occur by making the comparison explicit.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T12:06:11.630415+00:00— report_created — created