Technology
Your rules, where they cannot be skipped
Who may act, who must agree, how long to wait, where value may go — once on the account, they bind everyone.
How each rule is checkedThis account's rules
- Who may request
- Treasury · Operations
- Who must approve
- A second party
- How long it waits
- 24 hours
- Where value may go
- Permitted destinations only
What you set
The rules you get to write
Write once. Change any later without starting over.
-
Who holds which role
Owner and recovery are built in. Beyond them you create your own roles and move wallets in and out while the account runs.
-
What each role may do
Permissions per operation kind — and per part: asking, approving, cancelling, and submitting are granted separately.
-
How long an operation waits
One waiting period, set for the account. Long enough that acting alone is noticed before it lands.
-
Where value may go
Permitted destinations per kind — nowhere else.
Changing the rules follows the rules
Adding a role, shortening a wait, or widening destinations is itself an operation — second party, same record. No quiet administrator path.
See how the rules are written- A departing employee still has credentials
- Revoke their role. From the moment it lands, every operation is checked without them.
- An urgent payment needs to go out today
- It need not sit out the clock — a second party’s approval releases it now.
Write your rules once
Workspace or the product you already run.
Alpha · Testnet · Personal workspace