Particle CS Launch app (opens in a new tab)

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.

Why it matters

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.

What you set

Four things you decide.

Set them when you create the account. Change any of them later, without starting over.

Who holds which roleOwner and recovery come with the account. Beyond them, you create your own roles and move wallets in and out while it runs.
What each role may doPermissions are set per kind of operation — and per step. Requesting, approving, cancelling and submitting are granted separately.
How long an operation waitsA waiting period for direct approvals, set for the account — long enough that acting alone is noticed before it lands.
Where value may goPermitted destinations for each kind of operation. Where a list is set, a destination that isn’t on it is refused.
Changing the rules

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.
Limits

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.

Go further