JevMade hello@JevMade.com
← Back to guides

JevMade field notes / Architecture and workflow guide

jev-pruner

A host-by-host workflow for deciding which context survives compaction, with retention rules, troubleshooting, and a manual evaluation harness.

Original by tamaratranRetrievalRepository README and documentationSource reviewed

Before you dive in

What you’ll find in the original

  1. Classify information into explicit retention categories rather than asking for a free-form summary.
  2. Keep host installation and wrapper behavior separate because Codex, Claude Code, and other hosts expose different compaction hooks.
  3. Evaluate retention against labeled source units and inspect failures before changing the policy.
Worth knowing

Behavior and measurements are reported by the repository authors; source and critical implementation were inspected but not executed.