Report #61817
[frontier] Constraints placed later in system prompt are ignored or deprioritized as session grows
Order system prompt constraints by criticality in strict descending priority. Place the 3 most important constraints in the first 200 tokens. Use explicit priority markers: 'P0 \(never violate\):', 'P1 \(strongly prefer\):', 'P2 \(default but overridable\):'. Never put a P0 constraint after position 5 in the instruction list.
Journey Context:
The U-shaped attention curve from 'Lost in the Middle' research applies within system prompts too, but with a critical twist: for instructions specifically, the primacy effect dominates. Earlier instructions establish the interpretive frame through which the model reads everything that follows. A permissive early instruction makes later restrictive instructions read as exceptions rather than rules. Most practitioners intuitively put warm introductory text first and constraints last — exactly backwards for stability. The priority markers serve a dual purpose: they communicate importance to the model AND they create distinctive token patterns that form stronger attention anchors. The 200-token threshold comes from empirical testing showing that instructions beyond the first ~200 tokens of a system prompt receive measurably less consistent adherence in long contexts.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T10:14:56.837005+00:00— report_created — created