0PricingLogin
Claude Architect · Lesson

Progressive Summarization Risks

Numbers, percentages and dates go vague when summarized.

Why Summaries Drift

Long-running agents can't keep every turn in the context window. A common fix is progressive summarization: periodically compress earlier messages into a shorter recap so the conversation keeps fitting.

It works for narrative flow. But it has a sharp failure mode for the Context Management & Reliability domain: when prose gets compressed, numbers, percentages and dates go vague. "$1,284.50 refunded on 2026-03-14" quietly becomes "a refund was issued recently."

What Actually Gets Lost

Summarization optimizes for gist, not precision. The model keeps the storyline and drops the exact tokens that carry transactional meaning.

  • Amounts: "$4,999.00" → "a large charge"
  • Percentages: "a 17.5% discount" → "a discount"
  • Dates: "order placed 2026-01-09" → "earlier this year"
  • IDs: "order #A-88231" → "the order"

These are exactly the facts downstream tools and policy checks depend on.

All lessons in this course

  1. Full History Is Required
  2. Progressive Summarization Risks
  3. Lost-in-the-Middle Effect
  4. Case-Facts Blocks & Trimming Output
← Back to Claude Architect