Register a product.

A product exists in this hub once it has an entry: a name the business uses, a team that answers for it, and a repository its documentation can be generated from. The entry is the small, hand-written half — everything on the product view after that is produced by automation.

Product name

As the business says it, not as the repository spells it.

Identifier

Lower case, digits and hyphens. It becomes the product’s address here and never changes.

Domain

The business domain it belongs to — the first thing anyone searches by.

Owning team

The team that answers questions about it. A person’s name here ages badly.

Contact address

A team mailbox rather than an individual, for the same reason.

Repository

Where the code and its living documentation are generated from.

Summary

One sentence, in the words a product manager would use. It is what the catalog card shows, and it is the only part of the entry most people will ever read.

Back to the catalog

What happens after registration

The entry is the seed, not the documentation. Once it exists, the product's pipelines publish against it: the documentation section is regenerated on every build ofdevelop, contracts are registered in api-hub, the C4 and event views come from model-hub's models, campaign results arrive from qa-hub, and incidents from observability. A product whose entry exists and whose pipelines publish nothing shows up here as an ageing product — which is the honest answer, and the reason the indicator is on the card.