Catalog Distribution
Catalog Distribution is the provider-owned operation that publishes reviewed, signed governance package releases for cloud cells and licensed on-prem installations to consume.
It is separate from:
- Commercial catalog, which owns plans, add-ons, billing, and package entitlement policy.
- Catalog Adoption, which is the workspace-local import and review flow.
- Source-owner modules, which own runtime records after adoption.
Operator Journey
- Prepare or receive a reviewed package manifest and release metadata.
- Confirm that rights, AI-use posture, trust profile, signature, bundle hash, and compatibility metadata are suitable for distribution.
- Open Admin > System > Catalog Distribution.
- Materialize the reviewed package and release metadata with a governed reason.
- Verify the release appears in the distribution release table.
- Let cloud cells or on-prem installations consume the release through the existing service/install distribution channel.
What The Admin Surface Accepts
The admin surface accepts structured package metadata and release metadata. It does not accept raw package body text, protected standards text, secrets, credentials, storage keys, prompts, embeddings, vector payloads, or raw provider payloads.
Package and component kinds remain descriptor-driven. Do not encode a country, framework, authority, tender, or customer name as a product schema concept.
Cloud And On-Prem
Cloud cells use a managed service identity. Licensed on-prem installations use install identity and license evidence. Both consume the same signed release shape and import it into their local catalog cache before workspace adoption.
Normal workspace use reads local cache/adoption records. It does not read provider admin routes or provider databases.
Not A Public Developer API
Catalog Distribution is a provider operation, not the customer developer API
surface. The public developer API is served under /api/v1.