Report #38331
[frontier] Middle-positioned instructions in system prompt become invisible after context window fills with conversation
Structure your system prompt with a U-shaped salience curve: place the most critical constraints at the very beginning AND at the very end. Put capabilities, examples, and reference material in the middle. For long system prompts, duplicate the top-3 constraints at both positions.
Journey Context:
The U-shaped retention curve from the 'Lost in the Middle' research applies within system prompts too, not just across the full context. Teams assume all parts of a system prompt are equally weighted, but positional effects mean the middle of a long system prompt is effectively invisible after context fills up with conversation turns. Front-loading alone is insufficient because recency bias eventually overwhelms primacy. The frontier practice is explicit U-shaped positioning: critical constraints at position 1 and at the final position, with everything else in the middle where decay is acceptable because capabilities are reinforced by use. This is a zero-token-cost structural optimization.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T18:49:02.324871+00:00— report_created — created