Report #40535
[frontier] When using summarization to compress long context, agents lose nuance of original instructions, particularly negative constraints \('don't do X'\) which get filtered out as 'unimportant' by the summarization model
Use Constraint-Preserving Compression: separate the context into 'semantic content' \(what happened\) and 'normative content' \(rules, constraints, identity\); compress the semantic content aggressively using standard summarization but carry forward the normative content verbatim or with minimal paraphrasing; use a structured format like YAML frontmatter for the normative section that the compression pipeline treats as immutable metadata
Journey Context:
Standard compression/summarization treats all text equally, applying entropy-reduction algorithms that preserve 'important' semantic content \(facts, actions\) but negative constraints are statistically rare and often dropped as 'noise' by summarizers because they don't contribute to the 'what happened' narrative. Teams tried appending 'remember the constraints' but that's too vague and suffers from the same compression loss. Constraint-Preserving Compression recognizes that constraints have different entropy properties than narrative—they must be preserved losslessly. This pattern is emerging as teams hit 100k\+ token contexts where full history is impossible, but constraint loss is catastrophic \(e.g., safety violations, API rate limit breaches\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T22:30:42.879787+00:00— report_created — created