Open Check my config and choose one of two starts:
- Select See the complete example. The page loads a small AI-written NGINX candidate and a safer comparison, runs the browser checks, and shows the finished result.
- Add your own rendered Kubernetes YAML. You may also add a comparison and a Catalog source and intent record. If you ran
cub check, add its JSON result too.
What the browser does
The page:
- parses the Kubernetes YAML;
- lists the exact object identities;
- compares object contents without treating formatting changes as real changes;
- checks a short list of manifest risks;
- adds known hooks, CRDs, and prerequisites when you supplied a Catalog record;
- accepts
cub-check.jsononly when its object count and canonical object-set hash match the candidate; - records every check that did not run; and
- creates
workshop-result.json.
The complete result contains the candidate YAML, optional comparison, optional source and intent record, browser review, matching local check result, and SHA-256 hash for every file. It also contains one canonical object-set hash for the accepted Kubernetes objects. The file hash changes when file layout or document order changes; the object-set hash does not. You can keep the result locally or give it to Claude, Codex, another AI assistant, or CI. The separate YAML and review downloads remain available when a tool expects ordinary files.
Four answers in every result
The downloaded review keeps four questions separate:
| Question | What the browser can record | What it needs next |
|---|---|---|
| What do I have? | The source identity and exact files or objects you supplied. | Nothing else. A Catalog match is optional. |
| What will it produce? | Literal YAML is already the object set. For Helm, AICR, Timoni, Kubara, Sveltos, or another generator, the page can inspect supplied output but does not run the source tool. | Recorded source inputs and the source-native command when you need reproduction. |
| Can this destination accept it? | Not answered by browser files alone. | The exact candidate and current facts from the named destination. Deployment is not required. |
| Did it work? | Not answered before deployment. | The exact delivered revision and the live evidence required by the claim. |
Each stage has an evidence state and a result state. Missing destination access, credentials, hardware, components, or a deployment makes the relevant stage blocked or not-run. It does not make the source, candidate, workload, or conformance result fail.
What stays on your machine
The static website does not:
- render an arbitrary Helm chart or AICR recipe;
- pull an arbitrary OCI package;
- contact Git, ConfigHub, or Kubernetes;
- run schema or admission checks;
- execute hooks or establish CRDs; or
- test workload health, migrations, or external services.
Use Helm, AICR, cub installer, oras, or your existing build on your machine to produce the YAML. The page can then inspect it. Use local or CI tools for the checks that need source access, a registry, or a cluster.
Three valid endings
The browser result is useful without ConfigHub.
- Keep
workshop-result.jsonwith your change. - Publish the reviewed Kubernetes objects as OCI for Argo CD, Flux, or another consumer.
- Retain the candidate and review in ConfigHub when a team needs shared history, variants, approval, promotion, release OCI, or live comparison.
The page generates the ConfigHub commands and a prompt for the AI assistant you already use. Signing in is an optional operating choice, not a requirement for the browser check.
The generated commands keep a matching cub check result as a non-deployable evidence Unit beside the reviewed objects. That local result remains advisory. ConfigHub validation and apply gates are separate checks against the retained revision.
The website and command-line contract shows the same flow for Helm and literal Kubernetes YAML. Both carry the canonical object-set hash into the ConfigHub upload annotation.
The result format is defined by the WorkshopResult schema. The individual review inside it follows the ConfigurationReview schema.