Generated at: 2026-07-30T12:38:02.000Z UTC · source: committed helm-expt evidence for this verification page.
Start With The Question
Use the narrowest check that proves the claim. A passing generated-file check is useful, but it is not a fresh live test. A fresh live test is stronger for one row, but it can create clusters and receipts.
| Question | Command or surface | Needs cluster? | What it proves |
|---|---|---|---|
| Generated site/docs/data | npm run site:verifynpm run docs:verifynpm run data:index:verify | No | Generated surfaces match committed source and data. |
| Rendered tutorial output | npm run redis:verify-install:render -- ... | No | A user's workdir render matches the expected chart/base/package contract. |
| Broad repo gate | npm run verify | No cluster by default | The committed corpus, generated files, receipts, and docs are self-consistent. |
| Fresh Helm-vs-cub comparison | npm run kind-parity:run -- ... | Yes, kind | Regular Helm and cub installer are compared on two vanilla kind clusters. |
| Committed kind receipts | npm run kind-parity:verify | No | Existing two-cluster receipts and summaries remain internally consistent. |
| ConfigHub/OCI live lane | npm run live-parity:run -- ... | Yes, kind plus ConfigHub and OCI path | The stricter live path for a committed recipe/base. |
| Lane semantics | npm run lane-tests:verify | No | The lane matrix and its status vocabulary are still valid. |
| cub-scout receipt | cub-scout receipt validate <receipt.json> | No | A receipt fingerprint and structure validate locally. |
Product Commands And Proof Commands
Product commands
cub, helm, kubectl, Argo, and Flux render, install, deliver, or manage configuration.
Npm proof commands
npm run ... checks repo evidence: generated files, docs, data, tutorial renders, lane receipts, and proof summaries.
Full repo gate
npm run verify is a broad consistency gate. Use it before publishing or reviewing a large change, not as the first-user experience.
Recipe, Render, Record, Route
Flat YAML shows what would run. Verification adds the trail behind it and the routes around it, so hooks, CRDs, generated Secrets, setup jobs, and target prerequisites do not disappear.
| Move | Meaning | What gets checked |
|---|---|---|
| Render | Turn a chart, version, values, release name, namespace, and capability profile into exact Kubernetes objects. | Object parity checks and rendered install checks. |
| Record | Keep inputs, source lock, objects, diffs, receipts, scans, and observations with the chart configuration. | A reviewer can see what changed and rerun the same check later. |
| Route | Name the extras Helm leaves around the edges: hooks, CRDs, webhooks, generated facts, target prerequisites, Secrets, setup jobs, and GitOps handoff. | Each extra is applied, observed, blocked, refused, or marked target-specific. |
Fresh Evidence And Committed Evidence
Committed evidence
Already in the repo. Use it to review a claim, publish generated pages, and confirm summaries still match receipts and CSVs.
Fresh evidence
Created by a new run. It may create kind clusters, use ConfigHub, publish OCI artifacts, wait for Argo or Flux, or write receipts.
Run live lanes serially
Do not overlap fresh live lanes. Keep clusters, namespaces, credentials, and receipts isolated.
Subtopics
| Topic | Use it for |
|---|---|
| Verification docs | The canonical docs landing page for proof commands and render-record-route. |
| Verify It Yourself | The practical command list for offline checks, rendered installs, parity receipts, and cub-scout receipts. |
| Verification Lanes | What each lane proves and what it does not prove. |
| Choosing Commands | When to use product commands versus repo verifiers. |
| Expected Results And Clusters | Which steps need a cluster and what output to expect. |
| Outcomes And Tests | Which repo promises map to which test commands and CSVs. |
| Live Parity | How to read live Helm-vs-ConfigHub parity status. |
| Chain Of Proof | Which boundary is proven by render, ConfigHub, delivery, and live observations. |
| What We Refuse To Claim | The refusal boundaries that keep proof language honest. |
| Two-Cluster Harness | The stricter Helm-vs-cub kind harness. |
| NPM Script Catalog | The full script catalog for maintainers. |