> 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/parallel-partner-initiatives-and-resources/sciety.md).

# Sciety

Sciety is essentially a hub for *curating* the sort of evaluations that *Unjournal* aims to do. Users can access research works that have been publicly evaluated.

There are several initiatives of public—and sometimes journal-independent—peer evaluation, including around two dozen [groups listed on Sciety](https://sciety.org/groups), such as the [Biophysics Collab](https://sciety.org/groups/biophysics-colab/lists), [Rapid Reviews COVID-19](https://sciety.org/groups/rapid-reviews-covid-19/lists), and [E-Life](https://sciety.org/groups/elife/lists). However, these are nearly exclusively in biology and related areas.

[Sciety's mission:](https://sciety.org/about)

> Sciety’s mission is to grow a network of researchers who evaluate, curate and consume scientific content in the open. In doing so, we will support several long-term changes to scientific communication:
>
> * Change peer review to better recognize its scholarly contribution
> * Shift the publishing decision from editors to authors
> * Move evaluation and curation activity from before to after publication
>
> Our community-driven technology effort is producing an application that can support the changes in behaviour required to secure this future.


---

# 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 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/parallel-partner-initiatives-and-resources/sciety.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 `automate deployments from our CI pipeline` 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.