Report #39153
[frontier] All constraints treated equally so minor preference drift cascades into major constraint violations
Structure your system prompt with an explicit constraint hierarchy: 'INVOLIABLE: \[constraints that must never be dropped, e.g., security rules\]. IMPORTANT: \[constraints that should be followed but can be explicitly overridden by user request\]. PREFERRED: \[style preferences and conventions\].' Only re-inject INVOLIABLE constraints at checkpoints. When context pressure forces tradeoffs, the agent now knows what to hold at all costs.
Journey Context:
When all constraints are equal, the agent can't prioritize under context pressure—and context pressure is inevitable in long sessions. The result: a minor style preference and a critical security constraint get the same weight, and both erode together. The hierarchy lets the agent know what to hold at all costs versus what can flex. This mirrors how human organizations handle policy: constitutional principles are non-negotiable, guidelines are strong defaults, and preferences are optional. The key insight is that this hierarchy must be EXPLICIT in the prompt—agents don't infer relative importance well from implicit signals like ordering or emphasis.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T20:11:32.107810+00:00— report_created — created