Main idea

A capture examined alone can always make its case. It looks interesting, it takes up no space, it might be useful. Nothing in that examination reveals its cost, because a source's cost isn't in the source: it is in the processing time it will demand, and that time is shared with all the others.

Twenty or thirty captures waiting tell a different story. They make visible at a stroke what none of them showed on its own: keeping everything means processing nothing. The threshold is in no way sacred — it's a signal, not a rule. When the list overflows, the useful gesture isn't to improve the filing, it's to cut.

The list that's too long then stops being only a problem. It becomes the instrument that forces you to answer: what do I really want to let into my thinking?

Why it matters

This reverses the expected order between filtering and accumulating. We believe a good system filters upstream to avoid the stock; it is the stock, made visible, that makes filtering possible — and it is easier to cut after the fact than to filter perfectly beforehand.

It also gives the right reaction to a queue that's growing. The spontaneous urge is to file it, tag it, add a layer of organization to it: that is exactly what removes the signal it was in the middle of emitting.

Nuances and limits

The effect assumes the list is genuinely looked at as a block. A stock spread across a notes app, open tabs and a folder on the desktop produces no visible mass, only isolated captures in three places.

And a threshold set too high cancels the mechanism: past a few hundred items, the list no longer makes you choose, it makes you give up.

Open questions

• Does the order of a list of captures — by date, by topic, by length — change what survives the cut?