Report #54692
[synthesis] Agent silently violates system constraints as conversation length increases
Instrument token distance from the last system prompt recurrence. If the agent operates >N tokens from the last system prompt reminder, inject a latent constraint-check step or re-inject the core constraints into the context window.
Journey Context:
Teams monitor total token count but miss where truncation happens. When summarization or sliding windows drop older messages, system constraints are often the first to go. The agent doesn't error; it just stops asking for confirmation or changes tone. Monitoring overall context length doesn't catch this; you must monitor the recency of constraint injection relative to the current decision.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T22:17:50.738012+00:00— report_created — created