Architecture
Registry Operations
Permanent rules for canonical app identity and registry-owned metadata
Purpose
The registry owns top-level app identity.
It is the place to manage:
- app key
- display name
- description
- icon key
- category
- primary path
- navigation labels
- sidebar and switcher visibility
- UI shortcuts
What belongs in the registry
Keep only top-level product surfaces here.
Examples:
shopgivingcrmbookings
What does not belong in the registry
Do not register internal product slices as separate apps.
Examples:
- products
- categories
- orders
- fulfillment
- tax rules
- payment methods
Those are modules, extensions, or shared services.
Edit order
- create or update canonical app identity
- define presentation metadata
- define modules and capability metadata
- apply tenant overlays
- attach plans
Rule
Entitlement decides whether an app exists for a tenant.
Registry metadata decides how that app is presented.