Architecture
Catalog Operations
Permanent rules for tenant overlays and catalog posture
Purpose
The catalog layer applies tenant-specific posture on top of the registry.
It is the place to manage:
- exposure policy
- default enabled state
- selector visibility
- tenant ordering
- tenant-specific plan packaging
Rule
The catalog does not redefine app identity.
The registry defines the app. The catalog decides how that app is exposed for a tenant.
What belongs in tenant overlays
- enabled or hidden posture
- exposure policy
- selector visibility
- sort order
- pricing posture when applicable
What does not belong in tenant overlays
Do not move canonical app metadata into overlays unless there is a clear tenant-specific need.
Avoid spreading:
- names
- primary routes
- icons
- structural app identity
across many tenant rows.
Rule for runtime
Runtime reads effective app state from:
- registry
- tenant overlay
- plan entitlement
It should not seed workspace copies of the catalog.