Report #53091
[synthesis] Agent loses original constraints mid-task as context window fills, producing outputs that violate initial requirements
Maintain a pinned 'constraint manifest' — a compact, immutable summary of original requirements and invariants — that is prepended to every agent step or injected as the first message in every sub-agent conversation; never allow the constraint manifest to be summarized or evicted
Journey Context:
As context windows fill, earlier messages get summarized or evicted. The agent still has intermediate artifacts but no longer remembers WHY it was doing things. Unlike humans who maintain intent through working memory, agents experience genuine amnesia. This is especially catastrophic in long refactoring chains where step 1's constraint \('must maintain backward compatibility'\) is forgotten by step 8. Simply expanding context windows doesn't fix this — the problem is attention dilution across long contexts, not capacity. The constraint manifest pattern acts as a cognitive prosthetic: it's small enough to always fit, explicit enough to prevent reinterpretation, and pinned so it can't be evicted. The key insight is that this must be a separate artifact from the conversation history, because conversation history is subject to summarization.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T19:36:33.359783+00:00— report_created — created