How does the Clief Notes COmmunity keep context lean?

A priming bundle grows without anyone ever deciding to grow it. Mine reached a 106 KB markdown

file going into every fresh chat before I noticed I was spending most of an opening context

window on orientation the job did not need.

- The files grow, the bundle never gets re-scoped - each markdown earns a few lines a week and

nobody re-reads the total.

- Orientation is paid per spawn - every new chat pays the full size again, whether that job

touches any of it or not.

- Size is checkable, relevance is not - a byte count is trivial to gate on, whether a file

earns its place in this specific job is not.

What I run now is a size gate rather than a curation step. The priming script assembles the

bundle, checks the total, and if it is under threshold it goes. If it is over, the loop running

in the background trims on its next pass rather than blocking the spawn. Crude, but it fails in

the right direction, because I never get stopped from starting work and the trim happens on the

loop's clock instead of mine.

It is still a blunt instrument. Size is a proxy for the thing I actually care about, which is

whether a given file is load-bearing for this particular job, and a byte count cannot tell me

that.

So this one is a question rather than a share. How are you handling it - retrieval instead of

pasting, per-job bundles assembled by task type, a summarisation pass, or third-party tooling I

have not looked at properly? I am more interested in what has actually held up in practice than