# Base variant records

Generated by `scripts/generate-config-catalog-program.mjs`. Do not edit the generated records by hand.

There are **203 records**: 2 aicr, 199 helm, 1 kubara, 1 sveltos. Their current statuses are 199 available, 4 partial.

A base-variant record connects the literal configuration to the source that produced it, the choices fixed before install, the remaining target inputs, hooks and CRDs, proof results, policy, and OCI handoffs. It does not imply that every record is present in a live ConfigHub org.

3 canonical records also name who owns the configuration, where it should run, which checks apply, and how it should roll out. The [operational class examples](../operational-class-examples/summary.md) explain those choices. The other records remain `not-yet-classified`; the generator does not guess from a chart name.

## What to read

| Question | Field |
| --- | --- |
| Where did this configuration come from? | `spec.source` |
| Which exact configuration is managed? | `spec.configuration` |
| What was fixed and what remains to set? | `spec.inputs` |
| What must happen around ordinary apply? | `spec.routing` |
| Which OCI artifact is this? | `spec.delivery` |
| Which checks run before apply? | `spec.policy` |
| Who owns it, where does it run, and how should it roll out? | `spec.operations` when classified |
| What has actually been proved? | `spec.evidence` and `status` |

## Examples

- [Redis default](records/bitnami-redis-25-5-3-default.yaml) connects a Helm render intent, 14 literal objects, and its revision digest without claiming a current three-consumer delivery receipt.
- [NGINX http-clusterip](records/bitnami-nginx-24-0-2-http-clusterip.yaml) records the first exact catalog base published as one ConfigHub release OCI and consumed at the same digest by Argo CD, Flux, and direct apply.
- [Argo CD no-crds](records/argo-cd-argo-cd-9-5-15-no-crds.yaml) shows a base with external CRD requirements.
- [AICR EKS H100 training for Flux](records/aicr-eks-h100-training-kubeflow-v0-14-0-base.yaml) records the generated Flux objects, their controller requirements, and a locally tested OCI bundle without claiming a live upload.
- [AICR EKS H100 training for Argo CD](records/aicr-eks-h100-training-kubeflow-v0-14-0-argocd.yaml) connects AICR's generated Helm source package to the 17 rendered Application objects that ConfigHub can upload.
- [Kubara local platform](records/kubara-local-platform-v0-12-0-base.yaml) connects Kubara's generated platform source, 77 rendered bootstrap objects, and the recorded CRD, hook, Secret, and External Secrets work.
- [Sveltos Kyverno fleet](records/sveltos-kyverno-fleet-3-8-1-staging.yaml) records a two-wave result: ConfigHub approved a pilot and one selector expansion at different OCI digests, then Sveltos installed Kyverno and repaired drift on both staging clusters.

## Files

- [records.csv](./records.csv) is the compact index.
- [records.json](./records.json) contains every generated record.
- [schemas/base-variant-record.schema.json](../../schemas/base-variant-record.schema.json) defines the record shape.
- [Config catalog doctrine](../../docs/reference/config-catalog-doctrine.md) explains how the sources, variants, policy, delivery, and Apps fit together.