Report #40338
[frontier] Front-loading all constraints in system prompt causes attention dilution—each constraint gets 1/N of the attention budget
Implement a constraint registry mapping each constraint to the action types where it applies. Include only identity-level constraints in the system prompt. Inject domain-specific constraints as just-in-time reminders immediately before the actions where they're relevant. Use XML tags or structured blocks to make JIT constraints visually and attentionally distinct from conversational context.
Journey Context:
The system prompt is a blunt instrument for constraint management. When 20 constraints compete for attention in the system prompt, each receives approximately 1/20th of the constraint-attention budget. But most constraints are conditional: format constraints apply during output generation, safety constraints apply during tool use, style constraints apply during explanation, domain rules apply during specific task types. The Constraint Lattice delivers constraints just-in-time, when they're most relevant and most likely to be attended to. This is analogous to just-in-time compilation: you apply optimizations at the specific points where they matter, not everywhere at once. Anthropic's recommendation to use XML tags for structuring prompts provides the delivery mechanism: JIT constraints wrapped in distinct XML tags are visually and attentionally separated from the conversational flow, increasing their salience at the decision point. Teams implementing this pattern find that constraint adherence improves proportionally to the specificity of the constraint-to-action mapping.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T22:10:46.258617+00:00— report_created — created