Crate helm_schema_ir

Expand description

Symbolic Helm interpretation and normalized contract IR.

Modules§

fragment_eval: Fragment evaluation: the Guarded<AbstractFragment> domain and its interpreter over the helm-schema-syntax templated-YAML CST.

ConditionalPathOverlay: Conditionally-scoped values path whose schema can be lowered under a values-decidable guard set.
ContractDocument: Versioned serialized contract document for stable inspection and tooling.
ContractIr: Opaque guarded contract graph for one template interpretation.
ContractPathSchemaEvidence: All schema-lowering evidence for one values path.
ContractProvenance: Source provenance for one emitted contract fact.
ContractSchemaSignals: Contract-derived facts consumed by core values-schema generation.
ContractUse: A contract claim for one observed values path.
ContractValuePathFacts: Schema-generation facts for one input values path.
FinalizedContract: Finalized contract artifact derived from one canonical normalized contract.
HelperBranch: One branch of an if/elif/else chain in a helper or manifest header.
ProviderSchemaUse: Contract fact that needs a Kubernetes resource schema lookup.
ResourceRef: Detected Kubernetes resource type (apiVersion + kind).
SourceSpan: Byte span within a template source file.
SymbolicIrContext: Reusable state for generating symbolic IR across many templates that share one DefineIndex.
ValuesDefaultSource: A chart-wide default subtree merged into an effective .Values subtree.
YamlPath: YAML path in the rendered manifest, e.g. ["metadata", "name"].

CapabilityGuard: Structurally-decoded capability guard for an if action.
ConditionalGuard: Values-decidable guard expression that can be lowered into JSON Schema conditionals.
Guard: A guard condition from an if, with, or range block.
GuardValue: Scalar literal used by values-decidable guard comparisons.
HelperBranchBody: What a HelperBranch produces when its guard is live.
MetadataFieldKind: Kubernetes metadata.* field shape referenced by a values path.
ValueKind: How a value contributes to rendered YAML.

define_bodies_in_source: The (name, body) pairs a template source defines, for include-graph walks that need to follow helper calls through helper bodies and for chart-ownership queries over the define index’s files.