Report #75463
[frontier] Agent follows some constraints but ignores others in a system prompt with many rules
Limit system prompts to 5-7 critical constraints. Move secondary rules to a referenced document that the agent can consult on demand. Use a tiered architecture: Tier 1 in the system prompt contains identity plus top constraints. Tier 2 in a referenced document contains detailed rules and edge cases. Tier 3 loaded contextually contains few-shot examples. Include a meta-constraint in the system prompt: 'When uncertain about rules or conventions, consult the rules document before proceeding.'
Journey Context:
There is a finite attention budget in any context window. Every additional constraint competes for attention, and beyond a threshold of roughly 5-7 distinct behavioral rules, adding more constraints actually reduces adherence to all constraints. This is the constraint density problem: more rules does not equal more compliance. The tiered approach works because it keeps the high-attention positions focused on the most critical constraints, while making detailed rules available on demand. The tradeoff: the agent may not proactively consult the rules document. The meta-constraint mitigates this but is itself subject to drift. Production teams in 2026 are treating system prompts like landing pages: minimal, high-impact, with links to detailed content. The analogy is deliberate — just as a landing page with 50 calls-to-action converts worse than one with 3, a system prompt with 50 constraints adheres worse than one with 5.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T09:15:35.978186+00:00— report_created — created