> For the complete documentation index, see [llms.txt](https://docs.therisk.global/organization/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.therisk.global/organization/operations/platforms/7.-nexus-journals.md).

# 7. Nexus Journals

Where Nexus journals are published now.

{% hint style="info" %}
**Updated guide.** Earlier versions of these guides described community features of a previous GCRI website: accounts, profiles, questions and answers, journals, quests, bounties and similar. Those features have been retired. This guide describes how to take part through the current public sites; the earlier text is kept in the repository history.
{% endhint %}

Nexus journals are now published by [Nexus Reports](https://therisk.global/nexus-reports/); the earlier journals address leads there. [Nexus Reports](/organization/programme/reports.md) publishes by area, and the same area appears on each institutional site that hosts Nexus Reports.

To propose a contribution, use the [Nexus Reports contact page](https://therisk.global/nexus-reports/contact/). To challenge or correct something published, use [Corrections and concerns](https://therisk.global/trust/corrections/).


---

# 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://docs.therisk.global/organization/operations/platforms/7.-nexus-journals.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.