What problem does it solve? Adding a new tunable or switchable knob to the ELM-FATES model requires coordinated edits across Fortran source (EDParamsMod declare/register/retrieve) and every parameter file the run reads; missing either half causes runtime aborts or silently ignored values. ## Core Features & Use Cases - EDParamsMod wiring recipe: Step-by-step scalar parameter pattern (declaration, name string, nan sentinel default, RegisterParameter, RetrieveParameter) following the ED_val_understorey_death template. - Parameter file updates: JSON insertion for api-43 checkouts and NetCDF createVariable for api-31 legacy files, applied to every parameter file the experiment reads. - Reproducibility gating: Default-off switch-gating so a switch-off build reproduces the frozen baseline bit-for-bit (V0-at-equality), with runtime-tunable activation. - Use Case: Promote a hardcoded density cap in EDPhysiologyMod to a registered fates_max_plant_density parameter, add it to the JSON parameter file with a no-op default, then sweep values at runtime without rebuilding. ## Quick Start Add a new scalar FATES parameter named fates_<name> by wiring it through EDParamsMod and inserting it into the JSON parameter file with a default-off value.