Runtime/GitOps Wave · Config Workshop

Generated at: 2026-07-30T12:38:02.000Z UTC · source: committed helm-expt evidence for this rendered repository document.

This generated file selects the first runtime/GitOps live-proof wave. The top-20 already has local-kind evidence. This wave is the next step: prove that selected catalog bases can be delivered by an OCI-capable GitOps controller and observed back with a receipt.

Current Reading

top-100 runtime rows:             100
top-100 rows with local evidence: 20
first-wave chart/base pairs:      11
Argo CD OCI lanes:                7
Flux OCI lanes:                   4
first-wave receipts present:      11
first-wave pass receipts:         8
first-wave non-pass receipts:     3

Non-pass receipts are still useful evidence. watch means the controller delivered the artifact but a target condition still needs attention. blocked means the run exposed a prerequisite that must be satisfied before the selected base can be called live-ready on that target.

Files

File	Purpose
`wave1.csv`	The first chart/base/controller pairs to run live through GitOps OCI.
`receipt-index.csv`	The required receipt path and minimum checks for each first-wave run.

Rule

Local-kind evidence is not the same as GitOps/OCI evidence. A row is not GitOps-proven until the receipt under data/runtime-gitops/receipts/ exists and verifies the controller, artifact digest, sync result, runtime checks, and freshness timestamp.