Attack 6 · original
Methodology reference value updates
EC-M-1.1 includes 286 reference values defining 'healthy' for each ecosystem. Some of these will change over the 99-year term as scientific understanding evolves. If reference values are baked into the property at execution, the property is stuck on outdated science; if they automatically update, landowners face involuntary methodology changes that may reduce their credit yield.
Scenario
EC-M-1.1 includes 286 reference values defining 'healthy' for each ecosystem. Some of these will change over the 99-year term as scientific understanding evolves. If reference values are baked into the property at execution, the property is stuck on outdated science; if they automatically update, landowners face involuntary methodology changes that may reduce their credit yield.
Mechanism
The architecture pins methodology version at execution and requires DAO ratification for version updates — but reference value updates within a methodology version are a separate, currently ungoverned question. A sub-version update (e.g., EC-M-1.1.1) changing reference values could alter existing credit yields without triggering the ratification requirement.
Mitigation
NRD-lite incorporates methodology by reference with version pinned at execution. Methodology version updates require DAO ratification. A flag created in open-questions (Q-methodology-1) requires methodology stewards to define how reference value updates within a major version are handled — whether they trigger version increments and what transition periods apply for properties on older sub-versions.
Residual risk
Full resolution requires methodology stewardship decisions outside this repo's scope. Must be resolved before first deployment. The transition period for properties on older sub-versions and whether sub-version updates trigger NRD-lite amendments remain open.