Backstage-Style Service Catalogue
also called Software Catalogue, Service Registry
A queryable inventory of every service, its owner, its dependencies, its documentation and its operational state.
The catalogue answers questions that become unanswerable somewhere between fifty and a hundred services, and that get asked in the worst circumstances: who owns this, what depends on it, where are its runbook and dashboards, which version is deployed, is it in scope for this vulnerability.
Its value is a direct function of whether the data is derived rather than declared. A catalogue populated by hand is accurate on the day it is filled in and misleading within a quarter, which is worse than nothing because people trust it. A catalogue that ingests ownership from repository metadata, dependencies from build manifests and traces, versions from the deployment system and health from monitoring stays true without anyone maintaining it.
Ownership is the field that decays fastest and matters most, because reorganisations happen more often than services are retired. Tie it to a group identity that survives people leaving, and run an automated check that every service has an owner who still exists.
The second-order benefit is that once the catalogue is trustworthy, it becomes the substrate for everything else: scorecards, migration tracking, dependency risk analysis and the platform's own adoption telemetry.