Catalog and scorecards
Where your services live, who owns them, and how you read their health at a glance.
The catalog is the map of everything your teams run: services, APIs, data, and the systems they belong to. Every service you scaffold lands here with an owner, and the catalog is where you go to find, understand, and act on what you have.
What the catalog holds
- Services, each with an owner, links to its repository and pipelines, and a scorecard.
- APIs, browsable and shareable, with an API marketplace for the ones meant to be consumed across teams.
- TechDocs, the documentation for each service, kept next to the service rather than in a separate wiki.
- A tech radar, so the choices your organization endorses are visible in one place.
Ownership is not optional
Every entry has an owner. That single fact is what makes the rest work: when a scorecard slips or a finding lands, there is someone to route it to. Ownership is part of scaffolding, so a new service is never orphaned from day one.
Scorecards: health at a glance
A scorecard is a running read on a service across the things that matter: security findings, delivery, reliability, and ownership. It is how you tell, without opening five tools, whether a service is in good shape.
Scorecards are also load-bearing. The same signal that tells a human “this service needs attention” is what the platform uses to nudge services toward the current golden-path standard, and what feeds posture and governance views. You raise the bar once, and every service is measured against it.
Next
A service in the catalog is wired to a pipeline. See how changes move through it in Deliver.