To stay within context limits, your system summarizes older turns once a conversation gets long. In long multi-issue sessions, the agent sometimes refers to "the refund we discussed" with the wrong amount or date. Earlier turns had established a $84.17 overcharge on order #A-5521 and a promised callback by Friday. What change best preserves these details?

Answer: A — Keep transactional facts (amounts, order numbers, dates, statuses, promises) in a persistent case-facts block included in every prompt, outside the summarized history.

Progressive summarization tends to blur exact numbers, dates, and customer expectations into vague phrasing, so transactional facts belong in a persistent structured block outside the summarized history (task 5.1). Asking the summarizer to try harder (b) is still lossy compression with no guarantee. Dropping summarization (c) eventually exhausts context and exposes facts to the lost-in-the-middle effect. Asking customers to repeat themselves (d) hurts the experience and replaces facts the agent already verified with values the customer recalls.