Your rules, enforced on the account.
Who may act, who must agree, how long to wait and where value may go — set once on the account, they apply to every request it receives.

From team habits to enforced rules.
In most teams, who may do what lives in an interface, a backend or people’s habits. Programmable governance turns it into rules the account enforces on every request — whichever app, script or agent sends it.
Teams change, so the rules can change too — through the account’s own controlled path, like any other operation.
Four things you decide.
Set them when you create the account. Change any of them later, without starting over.
Changing the rules is an operation too.
Adding a role, shortening a wait or widening destinations goes through the account’s own configured path — and leaves the same on-chain record as any other operation.
- Someone leaves the team
- Remove their wallet from the role. From then on, every request is checked without them.
- An urgent payment can’t wait
- An authorized signer can approve off-chain; a broadcaster executes — no wait for the delay.
Rules are only as good as their setup.
Governance enforces what the account is configured to enforce. Separation of duty depends on which wallets hold which roles — so review the combined permissions each wallet holds.
Start with one team’s rules.
Related: Pre-execution security · Smart-account architecture