How a change happens

Every change to a policy or bounded setting is announced with its reason, waits 48 hours onchain, and each setting changes at most once per 7 epochs.

How a policy or setting change happens

1. Step 1AnnouncedPosted in public with its reason, then queued.
2. 48 hours onchain+48 hTakes effectAfter the timelock, inside the hard bounds.
3. at least 7 epochs+7 epochsCan change againThe same setting, at the earliest.

For policies and bounded settings. The team operations are immediate.

1. Announced first. Every setting change is posted publicly with its reason before it is queued.
2. Waits 48 hours onchain. A timelock holds it in public view before it can take effect.
3. Once a week at most. Each setting can change at most once every 7 epochs.
4. Signed by a multisig. The governor is a team multisig, with every signer address and the threshold published.

• The timelock enforces the bounds in Policies and bounds.
• Guardian and team operations do not wait.

One-way switches

A one-way switch can only be turned on. Once on, it stays on.

Switch	Effect
Permissionless buybacks	Anyone can execute the 35% tax buyback, not only the team Safe
Permissionless defence	Anyone can execute the range-bound defence
License transfers	Licenses are soulbound at launch; a separate one-way switch, changed only through the 48-hour timelock, could make them transferable later