---
# System prepended metadata

title: 'Wordsmiths of RaidGuild<>MolochDAO<>UberHaus: Proposal Sketch - September 2021'
tags: [uberhaus, Wordsmiths, molochdao, documentation, proposal]

---

---
###### tags: `Wordsmiths` `molochdao` `uberhaus` `proposal` `documentation`
---

# Wordsmiths of RaidGuild<>MolochDAO<>UberHaus: Proposal Sketch - September 2021

## Overview of Documentation Deliverables for MolochDAO
- **Manifesto:** An ideological document rendered at high-fidelity (avoiding jargon/lingo) that allows members to align around the central purpose. This requires reimagining what the central purpose is! ie: what MolochDAO funds after Eth2.0, how we define *public goods*, "a non-profit grant awarding DAO with a regenerative treasury focused on retroactive public goods funding,"" etc.
    - Pitched to the members and requires their approval

- **Membership Policies:** Details the minutae of DAO operations, in two categories:
    - **Soft Governance:** 
        - How does the DAO interacts socially - Discord, Twitter, code of conduct, who to contact for support
        - Outline responsibilities of grant recipients in reciprocity with the DAO: expectations, reports, how and where they are filed
        - An articulation of the filing system (typeform connected to airtable) for existing members, to know how to access the data, serving as a users manual of internal ops that can educate new ops members (Really Boring Guild contributors)
    - **Hard Governance:** On-chain interactions
        - How to operate/navigate DAO contributions on DAOhaus: voting, sponsoring, ragequitting, etc.
        - Overview of policies: voting, grace period; amount of ETH for tribute, proposal submissions; step-by-step tutorials for how to connect different wallets (metamask, gnosis multisigs, etc.)

- **Articulation of Grant Pipeline Procedures:**
    - What kinds of grants MolochDAO distributes, what kinds of projects we are interested in funding
    - How to apply for a grant, what information to provide, how the app will be evaluated and pushed through the pipeline, what to expect, how to proceed

- **Articulation of ReallyBoringGuild RFP PRocedures:**
    - How RFPs are different from DAO grants, what are RBG's funding priorities, how RFPs relate to the overall vision of the DAO and why we even have the system set up this way

- **ReallyBoringGuild Operational/Administrative Procedures:** An RBG handbook??
    - How RBG operates: detailing the multisig, onboarding new contributors, contributor roles, status updates, payment requests, etc.
    - Will RBG continue to operate? If so, as an autonomous DAO or as a member working group? How will funding be allocated moving forward? How will RBG roles/contributors be evaluated, and by whom? Should RBG be absorbed back into the DAO?
    - Articulation of RBG Oversight: 
        - outline assets, tools, databases, and other resources that are managed by RBG
        - outline RBG spending priorities for personnel, marketing, ad hoc contributions, how multisig oversight works
        - how RBG interfaces with DAO members: rights and responsibilities

- **Programming Bots:** to facilitate smooth onboarding of remedial tasks, onboarding in Discord, member notifications, etc. Copy needs to be written and programmed - with a dev?

- **Public-facing / Marketing Copy:**
    - Blogposts to track the journey/changes of the DAO to the community, recent v2 upgrade, current documentation reboot, roadmap into the future, etc.
    - Define the "personality" style for social channels: Discord, Twitter
    - Crafting of the public narrative/mythology
    - Outline parameters for individuals interested in contributing, outline current needs and potential for membership via sweat equity
    - Website copy updates: FAQs, all tutorials, all information pages, basically ALL copy

## Budget Considerations

- **ReallyBoringGuild has a budget.** Received as a MolochDAO grant for internal ops/admin. RBG is tasked with updating the docs, so it would be appropriate to distribute funds from this treasury for "ad hoc contributions." The amount would be limited, tight, and short-term, but it could get things started.
    - Would Wordsmith contributors be considered RBG members? Could compensation be distributed via sweat equity, ie: shares in the DAO? Pros/cons of this strategy...

- **We could propose an autonomous MolochDAO grant for documentation research/writing:** outlined and discussed in Discord, submitted on-chain. Problem is that MolochDAO members are not particularly active and this project might be difficult to justify!
    - Need to articulate the total cost, based on firm deliverables: will require some research.

- **Grant matching from other DAOS:** 
    - UberHaus<>DAOhaus: Audit of their handbook and help articulating the *federated roundtable of DAOs* idea for UH/DH, but more importantly to influence other DAOs in the community to align philosophically and join in UH governance. All of this will certainly prove useful for MolochDAO. MolochDAO docs will represent indebtedness/relation to DH/UH.
    - MetaGammaDelta: An internal ops grant to support Zayi & Ann as contributors (since neither are RG or Moloch members) and secure the inclusive design of the docs. MolochDAO docs will represent indebtedness/relation to MGD.
    - RaidGuild: Handbook audit (currently a season2 cohort task that was not picked up by apprentices), solidification of Wordsmiths as a sub-guild or child DAO of RG - setting a precident for attracting new kinds of clients to RG and also serving up a solid RIP. MolochDAO docs will represent indebtedness/relation to RG.
    - LexDAO? Perhaps no funding necessary, but this might be framed as a collaboration or reciprocal consultation to align their legal expertise with the cultural/narrative articulations that would be crafted by this group. MolochDAO docs will represent indebtedness/relation to LexDAO in articulating our legal entity (501c3 nonprofit org?)
    
## Scope 

:::info
Idea here is to create components that are generally present in most Wordsmiths tasks, creating a framework for resource planning, client qualifications, quotations and effort sizing.
:::

> i. For now.  there are 2 kinds of non-mutually exclusive wordsmith tasks (i.e. **Marketing/Narrative work vs Docs/Process work**)


> ii. Within both task types, there are typically 4 steps (dependent on client and also non-mutually exclusive).They are
> - **Market Research & Audit**: Identify gaps & create suggestions based on best practices & case studies
> - **Process Setup**: Create process, guides, workflows for creation of copy / docs both internally and externally 
> - **Copywriting**: Actual creation of whatever copy's needed for client
> - **Tech  / Platform Setup**: Set up tools or platforms that clients may need (e.g. Docusaurus / Gitbook / Medium / Substack, etc. )


> iii. Also, all the components are done in view of the client's **objective** (**what they want to achieve, not what they want us to do**). This should help us have the the right priorities in mind when looking for resources, spec-ing and quoting the project, as well as delivering the right value to them. 


### Client: MolochDAO



|     | Objective                                                                                                          | Deliverable                                                                                 | Market Research & Audit? | Process Setup? | Copywriting? | Tech / Platform Setup? |
| --- | ------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------- | ------------------------ | ------------------------- | ------------ | ---------------------- |
| 1   | Re-define narrative & explain the WHY behind MolochDAO                                                             | Manifesto                                                                                   | Yes                      | No                        | Yes (Marketing)         | Yes (Docusaurus/Gitbook)                   |
| 2   | Increase mindshare and spread message to the people that should care about MolochDAO (now that WHY is established) | <li>Blogposts, narrative</li> <li>Personality, style guide</li><li>Website copy</li>        | Existing (1)                    | Yes                       | Yes (Marketing)         | Existing  (1)                   |
| 3   | Automate and optimise community management (i.e. the people that care about the WHY)                               | <li>Discord bots, etc.</li>                                                                 | Existing (1)                     | No                       | Yes          | Yes                    |
| 4   | Explain the processes & policy (i.e. the HOW & the work) that fuels MolochDAO                                      | <li>Membership </li> <li>Governance</li><li>Grant Pipeline Procedures</li>            | No                       | No                        | Yes (Docs)         | Existing (1)                   |
| 5   | Explain the WHY & HOW of ReallyBoringGuild                                                                         | <li>Mini-manifesto - What is RBG?</li> <li>Memberships, Operations, Scope</li><li>RFPs</li> | No                       | No                        | Yes (Docs)        | Existing   (1)                    |


### Client: UberHaus <> DAOhaus
|     | Objective                                                                          | Deliverable                                     | Market Research & Audit? | Process Setup? | Copywriting? | Tech / Platform Setup? |
| --- | ---------------------------------------------------------------------------------- | ----------------------------------------------- | ------------------------ | -------------- | ------------ | ---------------------- |
| 1   | Articulate narrative of *federated roundtable of DAOs*  (the WHY DAOs should care) | Potentially a page like a Manifesto in the docs | No                       | No             | Yes          | No                     |
| 2   | Improve UberHaus handbook (the HOW) to encourage greater DAO participation         | Docs audit & improvement                        | Yes                      | Might be       | Yes (Docs)   | No                     |

### Client: RaidGuild 
|     | Objective                                                                  | Deliverable              | Market Research & Audit? | Process Setup? | Copywriting? | Tech / Platform Setup? |
| --- | -------------------------------------------------------------------------- | ------------------------ | ------------------------ | -------------- | ------------ | ---------------------- |
| 1   | Improve RaidGuild handbook (the HOW) for greater understanding of RG ops  | Docs audit & improvement | Yes                      | Might be       | Yes (Docs)   | No                     |

### Client: LexDAO



## Methodology

- Need to articulate the parameters of the **handbook audit,** loosely at first, then more specifically before we begin. Should be crafted in a manner than generates and distributes more value for all, not just for the benefit of MolochDAO!
- Need to outline the key research points required for the MolochDAO docs, how they interface with other DAO docs, and the procedure for how information will be extracted from the audits to fill in these holes. This will serve to formalize the research process as PoW for future clients.
- Compile a shortlist of DAO handbooks, organized by what they are particularly well-suited in explicating.