pub const OCI_SCHEME_PREFIX: &str = "oci://";Expand description
Canonical OCI URL scheme prefix — the "oci://" byte-string every
substrate-side renderer that composes an OCI artifact reference for a
Helm chart prepends. The Helm 3 OCI storage protocol (Helm 3.8+) and
the FluxCD HelmRepository type: oci source both key off this
literal — helm pull / helm install / helm registry login /
FluxCD’s source-controller all reject any other scheme on the OCI
path — so a byte-shape drift on this prefix silently splits the
substrate’s published chart references from the cluster-side
resolvers that consume them at helm registry / FluxCD reconcile
time far from the source renderer.
The single source of truth every downstream renderer that composes
an oci://<registry>/<chart> reference reaches for —
caixa-tatara’s derive_chart_ref OCI ref
(caixa-tatara/src/lib.rs:202), and every future OCI-ref emitter
(the future M4 mesh.pleme.io/v1alpha1/Aplicacao CR materializer’s
chart_ref slot on the tatara Process intent, the future
per-cluster snapshot bundle’s OCI chart references, the future
caixa-otel collector chart’s OCI publish shape) inherits the prefix
through this const by construction. Same “one canonical scheme /
prefix / separator lives in one place” discipline the peer
LAREIRA_CHART_NAME_PREFIX (f7320d7), CONTRATO_EDGE_LABEL_SEPARATOR
(6d9b04e), PLEME_LABEL_PREFIX (b473c00 / 9d9813f) lifts apply
on the sibling canonical-load-bearing-substrate-string axes.