Base owns shared Helm charts, Flux release packages, platform defaults, and release validation. Component repositories own application code and images; Tooling owns setup and operational commands. Add-ons own their product packages, while clients select releases, supply environment settings, and define deployment order.
- Architecture: package composition, configuration ownership, and service relationships.
- Development: local tools, validation, and release metadata.
- Operations: configuration, adoption, and recovery boundaries.
- Releases: version-specific upgrade instructions.
- AI endpoints: API and inspected-proxy client configuration.
Use the selected release's manifest for exact packages, prerequisites, images, and compatibility. A package's presence in the repository does not establish that it can be selected.