# Talk to Your DAO Proposal ## Scope/Feature Dump **Launch** - launch dao agent ui - web ui or chat ui only? - payment rails (subscription or one time?) **Channels** - channel scope: discord + farcaster - how much can we automate here? - twitter oauth to give agent access to an account - farcaster? single account? - can you progromatically create an account owned by the agent? - discord - single bot you give access? **Context/Data** - dao/community data sources - how does the bot get initial context? - moloch dao - discord channels/farcaster channels - hats tree? - some level of community led customization/personalization would go a long way - make it feel custom to community (as simple as the custom ui theme in dh v2 app) - lite level of community involvement in training/flavoring? - lead to governance to train/flavor? **Functions** - general chat about dao based on content it was fed - q&a - explain proposals - onboarding workflow - annoucements - sources - onchain activity - new proposals/voting ending - treasury snapshots/accounting help - calendar - what other data sources? - other/future? or maybe different agents you add? - could it generate agendas for town halls - generate newletters / activity recaps - cohort, sponsor, or client intake - dao event/calendar notification - the bot can play games - roll dice and give out axes - it's a casino dealer - make/vote on proposals - give out hats - be a shaman/give out shares **example app** - chat interfaces - loading different characters for different communities - adding context to a character by a community admin https://market-demo-five.vercel.app/ **some potential tech** fleek has an agent api that allows you to create and edit eliza agents eliza has good interfaces for discord, twitter, farcaster $20/mo per agent no custom plugin support but seems on the roadmap https://fleek.xyz/docs/ai-agents/agents-apis/ venice api as potential alternative to openai https://docs.venice.ai/api-reference/endpoint/characters/list openai, https://platform.openai.com/docs/guides/agents https://openai.github.io/openai-agents-python/ mpc connectors? https://github.com/modelcontextprotocol **other** how do we distribute? - RaidGuild as first paying customer? - Farcastle daos usage for examples? - Warpcast mini app? e2t on team? - not sure we need a pm, but comms/farcastle implementation? help with agent/eliza connection/amplification/partnership? Validation Questions What problem does this platform solve for DAOs and their members? Engaging current members, handles community anouncements and news/updarts, onboarding new members, support How will this platform improve engagement and interaction within DAOs? conversation interface, interesting and egageing personalities Are there existing solutions that offer similar functionality? ## 💡 Shadow Org — Product Ideation Summary ### 🔧 Core Concept A Discord-native AI bot platform where communities **hire customizable AI personas** to manage different functions within their server. Each persona has a name, a role, a personality, and access to community-specific context uploaded by the admin. > Think: “Lisa the Support Tech” helping newcomers, “Frank the Announcer” broadcasting proposal updates, “Townhall Warden” generating agendas, etc. Admins manage their **Shadow Workforce** via a web dashboard that acts like a control center for team building, training, and deployment. --- ### 🧠 Features & Architecture #### ✨ MVP Feature Set - ✅ One Discord bot per server, running multiple **channel-bound personas** - ✅ Admin dashboard: - Hire/fire personas - Upload context (docs, PDFs, URLs) - Customize name/image/personality quirks - Set channel assignments - ✅ Basic text chat interaction in Discord - ✅ Culture handbook as a shared global personality layer across all personas - ✅ Base set of personas: Announcer, Onboarder, Support Tech, Warden #### 🔁 Architecture Thoughts - One centralized bot for simplicity - Dynamic loading of persona context/personality on message receive based on: - Server ID - Channel ID → active persona - Context stored and versioned per server and persona - Bot response generated via OpenAI or similar with server-specific prompt augmentation - Cron jobs / server-side jobs handle notifications (i.e. proposal updates, DAO events) #### 📦 Future Add-Ons - More channels (Farcaster, Twitter) - More personas (Treasurer, Proposal Explainer, Meme Lord) - Persona stores or marketplaces - Community-generated personas - Email alerts - Games (dice, trivia, casino persona) --- ### 💰 Monetization Strategy #### Tiered SaaS Model - **Base Subscription** (e.g. $10–20/mo/server) - Includes access to dashboard + 1–2 base personas - **Refillable Credit Packs** - Use credits to unlock more personas, extra features, or advanced integrations - **Premium Personas** - Access to persona templates like “Onchain Treasurer” or “Meta-Governance Wonk” - **Pro Plan** - Increased message volume, analytics, API access #### Add-on Ideas - Persona “skins” or flair for extra customization - Paid integrations (Notion, Snapshot, Hats Protocol, etc.) - Revenue share with persona authors (in a future marketplace) --- ### 🛠 Next Steps 1. **Figma Dashboard Prototype** - Hiring interface - Persona editor - Channel mapping system 2. **Tech Exploration** - Fleek or OpenAI for agent infra? - Discord bot framework (e.g. `discord.js`, `discord-py`) - Persona routing logic per server/channel - Minimal DB schema (server, personas, context) 3. **Persona Design Doc** - Define traits/personality options - Draft base prompt templates for 3 starter personas 4. **Pilot Server Setup** - Build internal test server - Add single bot - Simulate onboarding experience via a channel + “Lisa the Onboarder” 5. **Market Validation** - Interviews with 5–10 DAO operators/community managers - Would they pay $20/mo for this tool? - Which persona would they need first? --- ### ❓Open Questions - Should personas be allowed to overlap across channels? - How rich do you want the personality customization to be (traits, tone, emojis, response frequency)? - Will personas need memory/history across multiple messages? - Would a self-serve marketplace of personas be useful early, or should all persona templates come from your team first? - What’s the best onboarding flow for a new server? (Add bot → open dashboard → hire personas) Absolutely! Here's a solid DAO proposal draft you can submit to DAOhaus to kick off Phase 1 of *Shadow Org*. I’ve aimed to balance clarity, vision, and concrete outcomes so it’s easy to support: --- --- --- ## 🧾 Proposal: Fund Phase 1 of *Shadow Org* MVP **Title:** Shadow Org – MVP Development Phase 1 **Submitted by:** [Your wallet or ENS] **Developers:** Sam & Dekan **Requested Funding:** 7.5 ETH **Duration:** 1.5 months (6 weeks) --- ### 🎯 Purpose This proposal requests funding to begin development of the *Shadow Org* MVP, a Discord-native AI bot framework that allows DAOs to “hire” custom personas—like onboarding guides, announcement agents, or support staff—to interact with community members in meaningful, on-brand ways. Shadow Org is an experiment in community-scale automation and playful governance tooling. We believe it fits squarely into the DAOhaus mission of empowering communities through modular, composable infrastructure. --- ### 🛠 Scope of Phase 1 (6 Weeks) **Goal:** Ship a functional MVP that can be piloted by DAOhaus and partner DAOs. #### ✅ Core Deliverables - 🔧 A single Discord bot that runs **multiple personas** within a server (1 bot per server) - 🧑‍💼 Web-based **admin dashboard** to: - Hire/fire AI personas - Upload context docs (markdown, PDFs) - Customize name, avatar, personality traits - Assign persona to specific channels - 💬 Discord message handling - Server-specific memory and prompt injection - Persona-based responses triggered by channel ID - 🧪 3 Starter Personas: - Larry the Onboarder - Frank the Announcer - Lisa the Support Tech - 🔁 Onchain/offchain context support: - Import DAOhaus proposals (via Subgraph or API) - Calendar or announcement triggers (stubbed or static) --- ### 💰 Budget **Total Ask:** 7.5 ETH for 1.5 months of full-time work by Sam and Dekan - 2 developers (Sam + Dekan) - Planning, architecture, bot framework, UI dashboard, persona system - Milestone-based delivery - Hosting/infra costs covered by the team during Phase 1 --- ### 📅 Timeline | Week | Milestone | |------|-----------| | 1–2 | Bot infra setup, Discord integration, basic persona routing | | 3–4 | Admin dashboard (hire/fire, persona editor), data model | | 5 | Starter persona prompt tuning + community context ingestion | | 6 | DAOhaus test server + feedback round | --- ### 🧪 Why DAOhaus? Shadow Org is inspired by years of DAO coordination pain. DAOhaus is the ideal launch partner: - **Culturally aligned:** playful, autonomous, modular - **Technically relevant:** integrates well with DAOhaus's proposal lifecycle - **Public goods orientation:** potential long-term open source or DAO-owned licensing --- ### 🧵 Future Phases (Not Included in this Proposal) - Farcaster & Twitter integrations - Persona Marketplace - Plugin/API ecosystem - Proposal generation & submission tooling - AI governance experiments --- ### 🙏 Request We respectfully request **7.5 ETH** from the DAOhaus treasury to fund Phase 1 development of *Shadow Org*. This work will be done transparently, in public, and with DAOhaus as the first testbed. Let’s build the weird workforce of the future—one goblin accountant, and onboarding fairy at a time.