The hard part of measuring 'before versus after' is making both follow-ups face the same question. Design the question so it depends on one concrete earlier detail — if that detail is lost to the summary, the answer must degrade.
Method
- Plant a specific, verifiable, unremarkable detail early. For example: 'the batch number for this session is BX-7731, remember it.'
- Continue a long enough conversation to trigger compaction (or compact manually).
- After compaction ask: 'What is the batch number for this session?'
- Record: correct, wrong, or does not know. All three mean different things — not knowing is honest, wrong is fabrication.
Sample question (the answer must be machine-checkable): What batch number did I give at the start of this session? Answer with the number only, no explanation.
What the three results mean
| Result | Means | Next |
|---|---|---|
| Correct | The detail survived in the summary or the retained span | Fidelity for this kind of detail holds |
| Does not know / did not see it | The detail is gone, but the model is honest | Acceptable. Restate it if it matters |
| Wrong, with a number that looks right | The worst case: fabricated a well-formed answer | Record it. It means such details cannot be trusted post-compaction |
Why not ask 'do you still remember'
Because a model's report on its own state is not evidence. Ask 'do you remember the batch number' and it may say yes and then invent one. Ask a single-valued, mechanically checkable factual question instead.