> For the complete documentation index, see [llms.txt](https://upliftworld.gitbook.io/upliftworld-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upliftworld.gitbook.io/upliftworld-whitepaper/the-uplift-goes-dao/core-roles.md).

# Core Roles

**The DAO will consist minimally of the following roles (not exhaustive):**

### **1) DAO token holders**

Make proposals (including all-new project proposals), vote.

### **2) Full-time roles**

**Full-time staff for key and/or legally required roles. Includes management roles that can take over committee work if there are functionality issues.**

1. Treasurer
2. Bookkeeping team
3. Other corporate-mandated roles
4. Overall project management
5. Overall product management
6. Lead back end developer
7. Lead plugin developer

### **3) Part-time roles**

**Part-time multi-role people with bursaries based on objectives or KPIs**

1. Twitter-er Tweeter
2. Instagram Poster
3. Facebook Manager
4. Event/Announcement Poster Creator
5. Autofarm hammer
6. Marketing Strategist
7. Events Coordinator
8. Project Outreach Coordinator
9. Discord wizard 
10. Mojang outreach 
11. Video editing wizard

### 4) Freelancers

**Freelancers working for bounties or on ‘in-residence’ retainers**

1. R\&D in-residence position
2. Blogger in-residence
3. Build team in-residence
4. Livestream team
5. Upliftium services execution team

### 5) DAO **Committee members**

Any one person may be in multiple roles. All roles will be voted on, although some key roles will be filled prior to DAO formation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://upliftworld.gitbook.io/upliftworld-whitepaper/the-uplift-goes-dao/core-roles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.