Lifecycle Routes

UNOFFICIAL/EXPERIMENTAL. Generated by scripts/generate-lifecycle-routes.mjs. Do not hand-edit. Regenerate with npm run lifecycle:routes.

This is a machine-readable answer to one question a Helm user asks when a chart has a hook or hidden lifecycle behavior:

Where does it go? Who executes it? What is the default? What are my off-ramps?

Render parity proves the desired non-hook objects. This contract is the separate fact about the lifecycle behavior: its route, who runs it, and whether the product runs it automatically (today, nothing does - see below).

The full field definitions and the deterministic mapping tables are in contract.md. The two data forms are routes.csv (spreadsheet) and routes.json (stable interface for agents).

What This Covers

53 route rows across 18 chart/version lifecycle behaviors, joined from:

• data/hook-disposition/top100-hook-dispositions.csv
• data/hook-route-candidates/candidates.csv
• data/hook-lifecycle-review/top100-source-hook-route-review.csv
• data/hook-route-candidates/selected-routes/*.yaml

It starts with hooks and existing routed hook candidates, and reaches the adjacent Tier-1 lifecycle quirks those rows already touch (crd-install, target-facts, webhook-readiness). Quirk classes with no per-chart route data yet (for example generated-facts, lookup) are deliberately out of scope until that data exists - a small correct contract, not a broad guess.

The Honest Headline

0 of 53 rows are safe to show as automatic.

Nothing the catalog renders today is auto-executed by the cub installer. Every route is user-executes, target-owned (a controller or GitOps engine runs it), or not-yet-executable. That is the entire point of the contract: a routed disposition means the route and its executor are named and an off-ramp exists - not that the product silently runs it. safe_as_automatic only becomes yes when execution_mode is product-executes and evidence proves it.

Distribution

How To Read One Row

Take route_name = preflight-or-presync, disposition = routed, execution_mode = user-executes:

• quirk_class - the kind of behavior (here a pre-install/upgrade hook phase).
• disposition - routed: the route is named but not yet proven live.
• route_name / default_route - where the behavior goes by default.
• alternatives - the named off-ramps for this quirk class.
• execution_mode - user-executes: you run it; the product does not.
• human_offramp / agent_offramp - how each picks a non-default route. A human selects a different recipe base/values; an agent enumerates and selects from routes.json.
• route_requirements - what the route needs (target facts, conditions).
• live_status / safe_as_automatic - proven-ness, and the strict automatic flag (no until the product executes it with evidence).
• evidence_or_next_action - the receipt path if observed, else the next step.

Rows

Boundaries

• Static join of committed CSVs and selected-route YAML receipts. No hook is executed, no cluster is touched, no ConfigHub state is changed, no runs/ receipt is edited.
• A routed or todo row is a classification, not a proof. observed rows point at the committed receipt in evidence_or_next_action.
• The master matrix value candidate-route maps to routed here; the source_disposition column keeps the original value for traceability.