Service catalog and ownership

The catalog is now the default landing page. It lists every service Beltic can see, who owns it, and which environments it is deployed to.

• Ownership is inherited from your identity provider groups
• Environments are detected automatically on first sync
• Filter by team, environment or health with a shareable URL

How ownership is resolved

Beltic resolves an owner for every service it discovers, in order, stopping at the first match:

1. An explicit owner in the service's beltic.yaml
2. The identity provider group that owns the repository
3. The team with the most commits over the last 90 days

Where none of those resolve, the service is listed as unowned and surfaced on the catalog's review queue rather than being silently assigned.

Detecting environments

Environments are read from deployment metadata on first sync and refreshed every fifteen minutes. A service deployed to an environment Beltic has not seen before appears within one sync rather than needing to be declared.

What changes for existing workspaces

Nothing is migrated. The catalog builds itself from what Beltic can already see, so existing workspaces have a populated catalog the first time they open it.