# Top-100 Catalog Analysis

This is the generated proof-surface view for the 100 maintained public Helm
chart recipes in this repo.

It is different from the top-500 matrix:

```text
top-100 = maintained recipe/package proof artifacts in this repo
top-500 = source-feature reconnaissance plus any matching recipe proof
```

## Summary

```text
rows: 100
top-20 catalog-supported entries: 20
next-80 proof-grade entries: 80
retained newer candidate versions: 10
catalog-supported: 20
proof-grade: 80
multi-variant entries: 67
default-only entries: 33
top-20 current with latest upstream: 13
top-20 update candidates: 7
production-disposition-needed entries: 0
production-review-ready entries: 20
entries matched to top-500 source rows: 65
no hard gap in chart-facts: 75
hard gap for at least one recommended capability: 25
```

## Interpretation

- The top-20 entries are the public catalog-supported lane for the declared
  `local-test` scope.
- The next-80 entries are proof-grade. They have deterministic recipe/package
  proof artifacts, but they still need user-shaped variants and promotion review
  before support is claimed.
- Latest-version currentness is tracked only for the top-20 catalog-supported
  lane at the moment. The broader top-100 currentness lane should wait until
  the current top-20 update candidates are promoted or explicitly deferred.
- Retained newer candidate versions are visible elsewhere in the catalog, but
  they are not counted as additional top-100 chart identities.

## Readiness Tiers

The top-100 should be read as four overlapping readiness views, not one blanket
claim.

| Tier | Count | Meaning |
| --- | ---: | --- |
| Recipe/package proof exists | 100 | The chart has a maintained recipe and executable `cub installer` package with proof artifacts. |
| Catalog-supported for local-test | 20 | The chart is in the public top-20 lane with local kind live/e2e and ConfigHub proof receipts. |
| Proof-grade, not catalog-supported | 80 | The chart has deterministic proof artifacts but still needs user-shaped variants and promotion review. |
| Variant-rich | 67 | The chart has more than one base variant. |
| Default-only | 33 | The chart has a proof path, but not enough variants for common user choices. |
| No hard gap in chart-facts | 75 | Recommended capabilities are built, not applicable, or have a known path. |
| Hard gap for a recommended capability | 25 | The core recipe may still work, but at least one useful capability is not yet enabled. See `data/chart-facts/summary.md`. |

In plain English:

```text
works now under declared proof scope
  100 charts have recipe/package proof artifacts.

works for the public local-test catalog
  20 charts have top-20 catalog support and live/e2e receipts.

works, but still needs user-shaped product review
  80 charts are proof-grade but not catalog-supported.

works only with a named limitation or user/operator help
  25 charts have at least one hard gap for a recommended extra capability.
```

The hard-gap column is about missing recommended capabilities, not total chart
failure. For example, a chart may have a working default recipe while still
lacking an `existing-secret`, `no-crds`, or HA path for a specific variant.

## Current User Answer

| Question | Count | Answer |
| --- | ---: | --- |
| Can the repo prove a maintained recipe/package path exists? | 100 | Yes. Every top-100 entry has recipe/package proof artifacts. |
| Can a user try it through the public local-test catalog lane today? | 20 | Yes, for the top-20 declared local-test scope. |
| Does it still need catalog promotion review before support is claimed? | 80 | Yes. These entries are proof-grade, not catalog-supported. |
| Does it already have more than one base variant? | 67 | Yes. These entries cover more than the default shape. |
| Is it still default-only? | 33 | Yes. These entries need user-shaped variants before a strong catalog recommendation. |
| Does it have a named hard gap for at least one recommended capability? | 25 | Yes. The core recipe may work, but one useful variant or capability is missing or blocked. |
| Is a supported top-20 chart behind the latest upstream version? | 7 | Yes. These need promotion proof before the catalog points at the newer chart. |

## Top-20 Update Candidates

| Chart | Supported version | Latest version | Variants | Required action |
| --- | --- | --- | --- | --- |
| `argo-cd/argo-cd` | `9.5.15` | `9.5.17` | default;no-crds | Run full promotion lanes before replacing the supported version. |
| `bitnami/mongodb` | `19.0.7` | `19.1.0` | static-passwords;existing-secret-replicaset | Run full promotion lanes before replacing the supported version. |
| `bitnami/nginx` | `24.0.2` | `25.0.0` | http-clusterip;existing-tls-ingress | Run full promotion lanes before replacing the supported version. |
| `bitnami/postgresql` | `18.6.7` | `18.7.0` | static-passwords;existing-secret | Run full promotion lanes before replacing the supported version. |
| `bitnami/redis` | `25.5.3` | `27.0.0` | default;reuse-existing-secret | Run full promotion lanes before replacing the supported version. |
| `prometheus-community/kube-prometheus-stack` | `85.3.3` | `86.1.0` | default;no-crds | Run full promotion lanes before replacing the supported version. |
| `prometheus-community/prometheus` | `29.8.0` | `29.9.0` | default;server-only-ephemeral | Run full promotion lanes before replacing the supported version. |

## High-Rank Next-80 Promotion Candidates

These rows already have proof-grade artifacts and appear high in the source
catalog reconnaissance. They need real variants before catalog support.

| Proof rank | Top-500 rank | Chart | Version | Source features |
| ---: | ---: | --- | --- | --- |
| 21 | 8 | `traefik/traefik` | `40.2.0` | lookup;generated-facts;tpl;capabilities;crds;cluster-rbac;webhooks;stateful-storage |
| 22 | 18 | `external-dns/external-dns` | `1.21.1` | tpl;crds;cluster-rbac |
| 23 | 21 | `gitlab/gitlab-runner` | `0.89.0` | generated-facts;tpl;capabilities |
| 24 | 38 | `kyverno/kyverno` | `3.8.1` | lookup;generated-facts;tpl;capabilities;hooks;crds;cluster-rbac;stateful-storage |
| 25 | 41 | `cloudnative-pg/cloudnative-pg` | `0.28.2` | generated-facts;tpl;crds;cluster-rbac;webhooks |
| 26 | 42 | `fluent/fluent-bit` | `0.57.6` | tpl;capabilities;hooks;cluster-rbac |
| 27 | 45 | `runix/pgadmin4` | `1.62.0` | tpl;capabilities;stateful-storage |

## Outputs

```text
data/top100-catalog-analysis/raw.json
data/top100-catalog-analysis/review.csv
data/top100-catalog-analysis/summary.md
```