<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=593366) </details> <!--IssueSummary end--> ## Context [ADR-022](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/18808) (namespace decoupling) introduces an internal entity with an immutable slug that customers choose when setting up their Artifact Registry instance. The internal table is currently called `namespaces`, but "namespace" is an overloaded term at GitLab. We need a user-facing name that is clear and distinct. For v1, each organization has a single instance of this entity. In the future (for example, after organization merges), an organization could have multiple instances. The UX and naming should account for this from the start. ## Where the slug appears The slug is omnipresent. It is the first path segment in every Artifact Registry URL: **GitLab UI:** - `/-/organizations/acme-corp/artifact_registry/acme-slug/repositories` - Breadcrumb: `Acme Corp > Artifact Registry > acme-slug > maven > my-repo` **Client configuration files:** - npm (`.npmrc`): `@scope:registry=https://ar.gitlab.com/acme-slug/npm/my-repo` - Maven (`settings.xml`): `<url>https://ar.gitlab.com/acme-slug/maven/my-repo</url>` **CI/CD pipelines (`.gitlab-ci.yml`):** ```yaml publish: script: - docker push ar.gitlab.com/acme-slug/docker/my-repo/my-image:latest ``` **Dockerfiles:** ```dockerfile FROM ar.gitlab.com/acme-slug/docker/my-repo/my-image:latest ``` **Team documentation / READMEs:** ```markdown Our internal packages are hosted at ar.gitlab.com/acme-slug/npm/shared-libs ``` ## Options discussed so far - **Namespace**: technically accurate but overloaded in GitLab (groups are already called namespaces internally) - **Registry**: aligns with product name but could confuse with the product itself - **Registry handle**: distinguishes from the product - **Anchor**: internal concept, not user-facing Other options are welcome. ## References - [ADR-022 MR discussion](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/18808#note_3143572857)