policyengine-parameter-patterns

YAML parameter standardization enforces consistent structure across parameter files by requiring specific metadata fields (unit, period, label, reference), precise naming conventions (amount.yaml, rate.yaml, threshold.yaml), and strict formatting. This ensures parameter files remain valid, documented, and deployable across multi-state social assistance programs like TANF.

Required metadata includes unit (measurement type), period (time span), label (human-readable name), and reference (source documentation). Each field must follow strict formatting rules, including date validation and source verification, to maintain compliance with social assistance parameterization standards.

Yes, parameter patterns support both dollar-amount values and rate-based patterns through dedicated file naming conventions. Amount.yaml handles dollar thresholds, rate.yaml manages percentage or per-unit calculations, and threshold.yaml defines cutoff values, enabling flexible parameterization for different calculation types.

Validation checks that parameter files match required YAML structure, naming conventions, and complete metadata fields with correct date formatting and source validation. Enforcing these rules at creation prevents deployment failures and ensures consistent parameter application across state programs.

Parameter files follow precise naming: amount.yaml for dollar-amount values, rate.yaml for rate-based patterns, and threshold.yaml for threshold values. This convention standardizes file discovery, deployment routing, and parameter interpretation across multi-state workflows.

Apply parameter pattern standards when creating or updating social assistance program parameters, particularly in TANF workflows. Standards ensure parameters are discoverable, validated, properly documented with metadata, and ready for deployment without manual correction or revalidation.