> 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/policies-projects-evaluation-workflow/evaluation/guidelines-for-evaluators/proposed-curating-robustness-replication.md).

# Proposed curating robustness replication

We are considering asking evaluators, with compensation, to assist and engage in the process of "robustness replication." This may lead to some interesting follow-on possibilities as we explore collaboration with the[ Institute for Replication](https://i4replication.org/) and others in this space.

We might ask evaluators discussion questions like these:

* *What is the most important, interesting, or relevant substantive claim made by the authors, (particularly considering global priorities and potential interventions and responses)?*
* *What statistical test or evidence does this claim depend on, according to the authors?*
* *How confident are* you *in the substantive claim made?*
* "Robustness checks": *What specific statistical test(s) or piece(s) of evidence would make* you *substantially more confident in the substantive claim made?*
* *If a robustness replication "passed" these checks, how confident would you be* then *in the substantive claim? (You can also express this as a continuous function of some statistic rather than as a binary; please explain your approach.)*

**Background**:

The Institute for Replication coordinates reproductions and "robustness-replications" of work published in top journals in economics and political science, increasingly focusing on specific literatures. Code- and data sharing is now being enforced in many or all of these journals and other important outlets. We want to support this work and are exploring collaboration possibilities. We are also considering how to best guide potential future robustness replication work.


---

# 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/policies-projects-evaluation-workflow/evaluation/guidelines-for-evaluators/proposed-curating-robustness-replication.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.
