Production Disposition And Live/E2E Lane

The top-20 are mandatory catalog entries because their upstream Helm charts are too popular to omit. This lane records the work needed to move those supported top-20 entries from local-test support toward production support.

It does not claim production support itself. Production support is recorded in the target-scoped decision artifacts under data/production-support-decisions/.

Summary

catalog-supported local-test charts: 20
ConfigHub proof receipts passing: 20
live/e2e observed charts: 20
production-review-ready disposition rows: 19
production-blocked pending disposition: 1
target-scoped support decision artifacts: 20
target-scoped supported decisions: 17
target-scoped superseded decisions: 2
target-scoped rejected decisions: 1
target-scoped draft decisions: 0
source Helm-hook rows: 1
hook/lifecycle disposition rows: 12
related lifecycle observation rows: 2
accepted production disposition receipts: 105
charts with accepted dispositions: 20

The hook/lifecycle disposition is a production-review item. It does not always mean the retained source scan found Helm hooks. Use the evidence fields in top20.csv:

• source_hook_count shows retained source-scan hook evidence.
• lifecycle_policy_basis shows whether the row came from source hooks, recipe hook policy, generic lifecycle policy, or related lifecycle observations.
• lifecycle_observation_receipts links receipts for cert-manager and External Secrets style CRD/webhook/controller behavior.

Use data/top20-base-readiness/base-readiness.csv for base-by-base live readiness. A chart can be production-review-ready at the disposition level while a non-default base still needs target runtime review. The target-scoped production support decision chooses the supported base, target scope, accepted risk boundary, and required runtime checks.

How To Read The Production State

production-review-ready is not the same as production support. It means the chart has enough accepted disposition evidence to make or audit a target-scoped production support decision.

Use these generated files as follows:

Typical support work includes choosing the production base, naming the target scope, accepting or patching scan findings, confirming lifecycle and target-fact requirements, refreshing live/e2e evidence for that scope, and recording or updating the support decision.

Pre-Decision Workstreams

This historical queue shows the decision that was needed before the current target-scoped decisions were closed. Use the current decision artifacts for the active support state.

For the full per-chart contract, use data/production-disposition/support-decision-contract.md. For the spreadsheet form, use data/production-disposition/support-decision-queue.csv.

Top-20 Disposition Table

Doctrine

The top-20 must be in the catalog. Their local-test paths are easy to try because they have passing ConfigHub/cub installer receipts. They are not production-supported until their scan/gate warnings, lifecycle risks, target facts, and live/e2e observation requirements have explicit dispositions and a separate production support decision records the target scope.