# Team Roles

**Project liaison**\
This person tracks the projects that were investing in and reports news back to the pool operator i.e. launch has moved, sketchy activity, etc.

**Pool Operator**\
The person in charge of making the physical buys/sells for the investment pool “pulls the levers”.

**Community Manager**\
Manages socials, interacts with the community, launches and tallies votes.

**White List Coordinator**\
Collects WL spots for projects on CrowdX from project devs and from our community members.

**Treasurer**\
Oversees the distribution of trading proceeds to the club members, manages the dev and treasury wallets “Master of Coin”.

**Club President**\
Manages the daily business operation, reporting and responsibilities of the DAO LLC.

**Club VP**\
Backs up all other positions in the event of vacation, incapacitation, transition.

**Members at-large**\
As a group decide what votes go before the community. Act as a general strategist for the club and make day to day decisions. Everyone on the core team will have this job, most will have multiple roles.

**In house tech lead**\
Responsible for all backend business tech development and management including graphics, website, software, dApps and email. Reports status and progress to the core team.

**Outside Tech liaison**\
Coordinates and manages the development and implementation of all smart contracts, proprietary software packages and dapps. Reports status and progress to the core team for community updates.


---

# Agent Instructions: 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:

```
GET https://defi-trading-club.gitbook.io/whitepaper/team-roles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.