Skip to content
MyDSHMy DSH Field Notes
中文
Independently maintained; not affiliated with DeepSeek. No association with mydsh.dev or other MyDSH sites.

Home/Modes & context/Context & compaction

The same follow-up before and after compaction: how to measure it meaningfully

Suspecting later answers degrade in long sessions without knowing whether compaction is the cause.

To be testedVersion and environmentChecked 2026-11-14
Source
the compaction event model; no paired run here yet
Checked
2026-11-14
Honest note: no measurements here yet. When compaction fires and where depends on session content and thresholds, so exact reproduction is hard. Below is a method that produces comparable results.

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

  1. Plant a specific, verifiable, unremarkable detail early. For example: 'the batch number for this session is BX-7731, remember it.'
  2. Continue a long enough conversation to trigger compaction (or compact manually).
  3. After compaction ask: 'What is the batch number for this session?'
  4. 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

ResultMeansNext
CorrectThe detail survived in the summary or the retained spanFidelity for this kind of detail holds
Does not know / did not see itThe detail is gone, but the model is honestAcceptable. Restate it if it matters
Wrong, with a number that looks rightThe worst case: fabricated a well-formed answerRecord it. It means such details cannot be trusted post-compaction
The third case is far worse than the second. Apply the same standard when judging any claim: prefer 'I do not know' over a plausible fabrication.

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.

What counts as working

Check every line. All of them pass or the job is not done.

  • The planted detail is unique and machine-checkable
  • Compaction actually fired (a compaction event exists in the log)
  • Three outcomes are recorded separately; fabrication is not conflated with not knowing

Where it fails

Symptom, cause, what to do — written in the order it actually happens.

SymptomCauseWhat to do
Compaction never firesThe session is too short, or the capability is not installedConfirm availability, or trigger a manual compaction before asking
The two follow-ups are worded differentlyDifferent questions, incomparable answersFix the exact wording and reuse it verbatim

Sources

Verified means measured here. Compiled means every line carries a source.