Report #68063
[frontier] Asymmetric Context Decay: Agent retains tool capabilities but loses negative constraints over long sessions
Implement Constraint Re-anchoring: re-inject negative constraints \(NEVER do X rules\) every 8-12 turns on a separate schedule from the main system prompt, treating prohibitions as perishable resources requiring higher refresh frequency than capabilities.
Journey Context:
Context compression algorithms asymmetrically preserve positive capabilities \(tool schemas reinforced by usage\) over negative prohibitions \(passive constraints\). Teams assume constraints are 'sticky' like capabilities, leading to late-session permission escalations where agents remember they CAN use tools but forget they MUST NOT. Standard prompt refreshing fails because it treats all instructions as equally durable; the fix requires bifurcated refresh schedules where negative constraints are re-anchored more frequently.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:43:28.114774+00:00— report_created — created