REPOSITORY ANALYSIS

fast-compaction-dsh

Verdict-based context compaction for DeepSeek Harness — replaces lossy LLM summaries with fast keep/truncate/drop decisions from jev-latest; everything kept stays verbatim. Port of tamaratran/fast-jev-compaction.

E2 · source reviewedPublic material or source evidence was reviewed. A fixed-version source review requires checking a pinned revision; this is not a reproduction, performance endorsement, or safety guarantee.
Stars
3
Forks
0
License
—
Last commit
2026-09-20

What Jev does here

Two Nouls per eligible tool pair control keep, truncate-result or drop-pair. DSH code rebuilds the retained text inside a transcript checkpoint and falls back to compaction-basic on failure.

Keeps selected tool evidence verbatim at DSH’s compaction seam, with an inspectable verdict report and explicit fallback.

Fixed-version documentation and implementation material were inspected on 2026-10-24. The DSH plugin was not installed or exercised. Author-reported round-trip timing was not independently reproduced.

What task does this project fit?

Replace DSH’s compaction summary with per-call retention verdicts at its supported engine seam.

Material analysed:

From input to action

  1. Pair tool calls and results; pin the first conversation and recent messages.
  2. Ask separate call/result Nouls in budgeted batches.
  3. Rebuild the compacted region as a verbatim transcript checkpoint inside one durable user message.

Implementation details that matter

Byte-preserving text can still have different framing

The README explains that DSH replaces a surface span with one user message containing role labels. Retained text is unchanged, but its original message structure is not preserved.

Inspect the supporting source ↗

This is not the same intervention as pre-compaction

It subclasses the compaction engine’s summarize hook when compaction triggers. The wjw66 advisor instead runs before that boundary and replaces selected result nodes.

Inspect the supporting source ↗

When to choose it

Choose it when DSH’s compaction seam is the desired control point. Compare checkpoint framing with your agent’s expectations; exact text alone does not guarantee equivalent interpretation.

How to inspect it yourself

Read README’s numbered flow and questionsFor in src/jev.ts. Trace keepResult, keepCall-only and drop cases, then inspect how their role labels are represented inside the single checkpoint message.

Limits of this review

  • The DSH plugin was not installed or exercised.
  • Author-reported round-trip timing was not independently reproduced.
Primary material used in this analysis