Thanks, Morb. The user signs and accepts how veDelegate will vote, including how the allocation can change automatically.
We then follow that choice. It is baked into the contracts and verifyable on-chain. We do not change their saved vote preference. There is no background update or transaction that rewrites it.
This follows the same basic idea as the [VeBetterDAO Navigator concept]([VeBetterDAO Proposal] Activating Governance - From Lazy Votes to Curated Stewardship "VeBetterDAO Navigator concept
([VeBetterDAO Proposal] Activating Governance - From Lazy Votes to Curated Stewardship)"): users choose to let another party make voting decisions for them, and those decisions can change each week.
If we need to explain that choice more clearly before signing, I’m happy to improve the interface. Could you clarify whether the concern is how users confirm this choice, or whether the RuleBook treats delegation through veDelegate differently from Navigator delegation?