Inside the handbook
A framework for
delegated discretion.
What authority moves when a DAO delegates—and how can it retain control?
The handbook examines delegation as an authority relationship: who grants power, what it covers, how much judgment the recipient can exercise, how decisions are executed, and how that power can be withdrawn.
It follows those questions across token delegation, DReps, validators, expert councils, stewards, institutional custody workflows and AI-assisted systems. Cases illustrate mechanisms, trade-offs and redesigns rather than a universal model to copy.
From diagnosis to control
Start with why delegation is needed, what is being transferred and who should receive it.
Connect mandates and incentives to accountability, revocation and the delegate lifecycle.
Use the Delegation Architecture Canvas and worked example to bring the choices together.
Explore the contents
Open a chapter in the original PDF. Page navigation depends on your browser’s PDF reader.
- Executive summary06 ↗
- Why delegate at all?09 ↗
- What exactly is being delegated?13 ↗
- Who gets the power?16 ↗
- What does a delegate owe?21 ↗
- Who pays for governance?24 ↗
- Can power actually be taken back?29 ↗
- Does delegation decentralize power?33 ↗
- The delegate lifecycle37 ↗
- When delegates stop being the answer41 ↗
- The governance intermediary45 ↗
- Institutional delegation48 ↗
- Delegation after AI52 ↗
- When not to delegate55 ↗
- The Delegation Architecture Canvas57 ↗
- Worked example — applying the canvas59 ↗
- Appendices — system map, failures & sources63 ↗
