> For the complete documentation index, see [llms.txt](https://globalimpact.gitbook.io/the-unjournal-project-and-communication-space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://globalimpact.gitbook.io/the-unjournal-project-and-communication-space/readme-1/call-for-participants-research/interested-in-working-for-the-unjournal/advisory-team-roles-research-management.md).

# Advisory/team roles (research, management)

{% hint style="info" %}
**Dec 2024**: We are still looking to bring in more [field specialists](/the-unjournal-project-and-communication-space/readme-1/organizational-roles-and-responsibilities.md#field-specialists-fs) to build our teams in a all areas, but particularly in the quantitative social science and economics/behavior modeling of catastrophic risks, AI governance and safety.
{% endhint %}

In addition to the "work roles," we are looking to engage researchers, research users, meta-scientists, and people with experience in open science, open access, and management of initiatives similar to *The Unjournal.*

We are continually looking to enrich our general team and board, including our [Organizational roles and responsibilities](/the-unjournal-project-and-communication-space/readme-1/organizational-roles-and-responsibilities.md#management-committee-members), [Organizational roles and responsibilities](/the-unjournal-project-and-communication-space/readme-1/organizational-roles-and-responsibilities.md#advisory-board-members-abm-and-field-specialists-fs) These roles come with some compensation and incentives.

\
(Please see links and consider submitting an expression of interest).


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://globalimpact.gitbook.io/the-unjournal-project-and-communication-space/readme-1/call-for-participants-research/interested-in-working-for-the-unjournal/advisory-team-roles-research-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.