Report #88486
[frontier] Agent forgets safety and style constraints but retains all capabilities after 30\+ turns
Recognize the Capability-Constraint Asymmetry: capabilities are baked into weights \(permanent\), constraints live only in context \(transient\). Implement periodic constraint re-injection at conversation midpoints — do not assume a constraint stated at turn 1 is active at turn 40.
Journey Context:
This is the fundamental asymmetry driving instruction drift. A model will never forget how to write a regex or call an API because that knowledge is in its weights. But 'always use TypeScript strict mode' or 'never modify the config file' lives in the context window and is subject to attention dilution. Teams that simply make system prompts longer actually make drift worse — more constraint text means more text competing for attention. The fix is concise, repeated constraint anchors, not exhaustive one-shot instruction dumps.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T07:06:18.619363+00:00— report_created — created