Creating and Configuring a DAO¶

This guide will walk you through creating and configuring your own DAO using playbooks.

Choose a Playbook¶

Sage provides versioned playbooks that set sensible governance defaults:

Playbook	Use Case	Governance	Members
Creator	Solo publisher	Operator (direct control)	1
Squad	Small team	Safe multisig	3-10
Community	Token holders	Governor + Timelock	50+

Create with Playbook (Recommended)¶

1. Generate a Plan¶

First, preview what will be deployed:

sage dao create-playbook \
  --playbook community \
  --name "My Community DAO" \
  --dry-run

This generates a plan file (dao-plan-*.json) showing: - Contracts to deploy - Roles to grant - Parameters to set - External actions required (e.g., Safe transactions)

2. Review the Plan¶

Open the generated dao-plan-*.json file and review: - Governance parameters (voting period, quorum, threshold) - Role assignments (PROPOSER, EXECUTOR, LIBRARY_ADMIN) - Timelock delays

3. Apply the Plan¶

Execute the deployment:

sage dao create-playbook --apply dao-plan-*.json

The CLI will: 1. Deploy all contracts 2. Grant necessary roles 3. Configure governance parameters 4. Return your DAO address

4. Verify Configuration¶

Check that everything is set up correctly:

sage project status --dao 0xYourNewDAO

This shows: - Current library CID - Role permissions - Governance configuration

Playbook Details¶

Creator Playbook¶

Best for: Solo operators who want direct control

sage dao create-playbook \
  --playbook creator \
  --name "Personal Skills Library"

Features: - No voting required - Instant updates - Direct control over library

Squad Playbook¶

Best for: Small trusted teams (3-10 members)

sage dao create-playbook \
  --playbook squad \
  --name "Team Skills"

Features: - Safe multisig for proposals - Fast execution (1-2 day timelock) - Requires threshold approval

Community Playbook¶

Best for: Decentralized communities (50+ members)

sage dao create-playbook \
  --playbook community \
  --name "Community Intelligence DAO"

Features: - Token-weighted voting - Longer voting periods (3-7 days) - Quorum requirements (typically 4%) - Proposal threshold (e.g., 10,000 tokens to propose)

Adding a DAO Profile¶

You can set up a DAO profile with avatar, description, and social links at creation time or later.

Option 1: At Creation Time¶

First, create and upload your profile:

# Create a profile JSON and upload to IPFS
sage profile upload --name "My DAO" --bio "A community for..." --type dao
# Returns: CID: QmYourProfileCID

# Then create DAO with profile
sage dao create \
  --name "My DAO" \
  --symbol "MYDAO" \
  --profile-cid QmYourProfileCID

Or use the wizard which prompts for profile CID:

sage dao wizard

Option 2: After DAO Creation¶

# Upload profile and get CID
sage dao profile upload 0xYourDAO --name "My DAO" --description "Description" --avatar ipfs://...

# Set the profile CID (creates governance proposal)
sage dao profile set 0xYourDAO --cid QmNewProfileCID

Advanced: Custom Parameters¶

For full control, use sage dao create directly:

sage dao create \
  --name "Custom DAO" \
  --symbol "CUSTOM" \
  --token-type fork \
  --initial-supply 1000000 \
  --voting-delay 1 \
  --voting-period 5 \
  --proposal-threshold 10000 \
  --quorum 4 \
  --profile-cid QmYourProfileCID

Note: Playbooks are recommended for most use cases to avoid configuration drift.

Next Steps¶

After creating your DAO:

Publish your first skill

sage prompts publish my-skill --dest <dao-address>

Invite members (for Squad/Community)
Share DAO address
Distribute governance tokens
Guide members through voting setup

Monitor proposals

sage proposals inbox --dao <dao-address>