Reviewing Economic Policy Changes¶
Required Review Steps¶
- identify every changed constant, enum branch, and claim-mode mapping.
- map change to principal-protection and claimability consequences.
- run conformance suite and policy-specific scenario traces.
- require security review signoff before queueing upgrade.
Must-Answer Questions¶
- does this broaden reward-enabling states?
- does this alter reserve exposure caps or recoup semantics?
- does this weaken quarantine/fail-closed behavior?
- does this modify settlement ordering around principal protection?
Review Outputs¶
Economic policy review must produce an implementation-diff summary, updated scenario traces, affected state-machine notes, claimability impact, and governance payload review. If the change affects ECONOMIC_POLICY_HASH, the release package must show how the new metadata is registered and monitored.
Abort Conditions¶
Abort the release if old traces still pass only because assertions are weak, if negative scenarios are missing, if source-ledger uniqueness is not tested, or if reserve/settlement consequences are not reviewed by risk owners.
Evidence Model¶
| Field | Requirement |
|---|---|
| Purpose | cross-layer review before changing accounting or claim policy. |
| Expected location | source diff, tests, specs, and scenario table. |
| Current local evidence status | Evidence required unless the named artifact is present in this repository or the Solidity source snapshot and has been inspected in the current run. |
| What it proves | that a policy change has evidence across model, source, and docs. |
| What it does not prove | that governance should approve the change without human review. |
| How to regenerate | Run the documented tool from a clean environment, archive command, commit/source hash, config, stdout/stderr, and result files. |
| Production requirement | Results must be tied to the exact source manifest lock, compiler version, dependency lock, and deployment artifact under review. |
| Owner responsible | Protocol engineering owns source/test correctness; security review owns independent challenge; governance owns accepting residual risk. |
| Failure meaning | A failure blocks release, launch, upgrade, or operation until root cause is fixed or explicitly accepted with documented risk. |
Review Notes¶
Do not write “pass” for Economic policy change review without current evidence. If evidence is missing, stale, or tied to a different source snapshot, write Evidence required and keep the gap visible in the release or operations checklist.