> 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/~/changes/531/policies-projects-evaluation-workflow/considering-projects/process-prioritizing-research.md). # Process: prioritizing research This page is a work-in-progress *15 Dec 2023: Our main current process involves* * Submitted and (internally/externally) suggested research * Prioritization ratings and discussion by *Unjournal* field specialists * Feedback from field specialist area teams * A final decision by the management team, guided by the above See [this doc](https://docs.google.com/document/d/1Bj0_tLVuEkILQWuC68dBGnEXl4466odKZm_5f1kADUs/edit?usp=sharing) (also embedded below) for more details of the proposed process. {% embed url="" fullWidth="true" %} --- # 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/~/changes/531/policies-projects-evaluation-workflow/considering-projects/process-prioritizing-research.md?ask=&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.