Report #51117
[frontier] Flat prompt structure causes all instructions to decay equally with no priority differentiation
Implement a three-tier prompt hierarchy using structural markers: \(1\) Immutable Core—identity and hard constraints, never modified, always at context start; \(2\) Operational Layer—current task instructions and active context, updated as task evolves; \(3\) Ephemeral Layer—turn-specific details, freely compressible. Use XML tags to enforce boundaries between tiers.
Journey Context:
Most system prompts are flat lists of instructions with no internal structure. All instructions compete equally for attention, and as context grows, they all decay together. The hierarchical approach creates a priority system that mirrors how attention actually works: the model gives different weight to information in different structural positions. XML tags work particularly well because models trained on structured data treat tagged sections as semantically distinct compartments—you can put something in and the model treats it differently than something in . The three tiers map to three levels of mutability: immutable core \(who the agent is\), operational \(what the agent is doing right now\), ephemeral \(what just happened\). When context pressure requires compression, the system can safely truncate the ephemeral layer, selectively compress the operational layer, and never touch the core. The tradeoff is upfront design discipline—you can't just append new instructions to a growing prompt. But the benefit is that critical instructions maintain salience regardless of session length, and the agent has a clear model of which of its instructions are negotiable and which aren't.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T16:17:11.786882+00:00— report_created — created