Treasury and Execution Policy
This note narrows permissions-and-policy to treasury, fund, signer, and constrained-execution systems where the real mechanism is a policy stack rather than a raw wallet or vault.
Questions worth asking:
- Does authority live in signer thresholds, workflow approvals, vault constraints, or allocator mandates?
- Which parts of treasury control are visible onchain versus hidden in operating software?
- Is the system a wallet, a workflow layer, or a policy constitution for capital deployment?
Canonical comparison set
- Visible account and signer substrate: safe
- Business-operations and treasury-workflow layer: stackup
- Constrained allocator and guardian-policy layer: aera
- Institutional approval-graph operators: fireblocks and bitgo
- Governance-allocation variants where pool rules and role design are the mechanism: allo-protocol and aragon
- Regulated treasury / fund wrappers where investor admission and redemption policy become decisive: hashnote and openeden
Useful traversal questions
- Is this product allocating capital, governing spend, or just packaging custody?
- Which policy layer can still move faster than the public decentralization story suggests?
- When the treasury acts, what is the smallest set of humans or operators that actually had to say yes?