Step 5 of 6

Treat every policy edit as a new reviewed operating boundary. Preserve the previous version so the change remains understandable and reversible.

Before editing

Start from a concrete operational reason: a rejected action that should be allowed, a capability that is no longer needed, a changed wallet or market, or a safer limit. Record the agent, active version, relevant verdict, and exact control that needs to change.

Create the next version

1. Open the agent and select Edit policy.
2. Copy the active version when you want to preserve its reviewed settings.
3. Change only the controls required by the stated operational reason.
4. Review assets, recipients, contracts, trade sides, numeric limits, and sanctions controls.
5. Save the new version and confirm which version becomes active.
6. Exercise the change with a controlled test action.

Never remove or weaken sanctions controls to make a request pass. Do not broaden several unrelated capabilities in one version; smaller changes make the resulting verdicts easier to understand.

Verify the change

Open the next activity record and confirm that it cites the new policy version. Check that the intended action is handled correctly and that unrelated restrictions remain in place. The version-history view should retain the superseded configuration for comparison.