Skip to content

Naming Standard

The catalog uses one primary identity for each repository and keeps alternate naming only where it helps humans understand the system.

Fields

  • Canonical Name — the default human-facing name used throughout the catalog.
  • Repository Name — the exact GitHub repository slug.
  • Technical Function — a concise description of the role the repository fulfills.
  • Product Context — the product, surface, or business area where the repository belongs.
  • Type — classification such as service, application, website, runtime, docs, or concept.
  • Lifecycle — current state such as active, on-hold, deprecated, or archived.
  • Notes — clarifying information that helps explain exceptions or edge cases.

Rules

  • Use the Canonical Name everywhere unless an exact repo slug is required.
  • Keep Repository Name exact and unchanged.
  • Write Technical Function in one sentence.
  • Use Product Context to explain where the repo belongs when the repo name alone is not enough.
  • Use Notes for exceptions, not as a replacement for clear fields.