Start here: how this desk

01What Reports is

Reports is the quarterly publication of the Nexus Consortium. Six desks write it, and every edition shows its evidence, its method and its limits. The Global Centre for Risk and Innovation (GCRI) is the publisher of record. If you build models or publish data on coupled systems, this is where your work is read against everyone else’s.

Atlas of the GCRI Systems Evidence desk: its mandate, the series it leads, the eight chapters of its edition, what to send here and its Zenodo community. The sections below give the same facts as text. — The GCRI Systems Evidence desk atlas, with its facts written out below.

02This desk: Systems Evidence

GCRI holds the technical truth of an edition. It decides whether a finding rests on evidence that can be checked, and it leads the series that carry country, global and sector systems.

Mandate: Evidence, methods and models on coupled systems: water, energy, food, health and biodiversity, by country, region and sector, and the Labs evidence behind them.

Series this desk leads:

Country Systems Risk and Resilience
Global Systems Risk and Resilience
Global Sector Risk and Resilience
Methods and Technical
Labs Evidence
Foresight Outlook

03The six desks

Systems Evidence is one of six desks, and it deposits to its own Zenodo community under the flagship.

Diagram of the six desks and the flagship Zenodo community nexusreports. The table below lists the desks.

The six desks
Desk	Edition	Zenodo community
GCRI	Systems Evidence	nexusreports-gcri
GRF	Public Deliberation	nexusreports-grf
GRA	Capital Readiness	nexusreports-gra
NXS	Standards Progress	nexusreports-nxs
RA	Capability	nexusreports-ra
GRX	Measurement	nexusreports-grx

04The edition in eight chapters, in this desk’s terms

Chapter 6 cross-references the other five desks and never copies them.

The eight chapters of the Systems Evidence edition
Chapter	Title	What it covers
1	The coupled system	How the systems in scope depend on each other, and the couplings through which a shock travels.
2	Findings	The findings of the edition, each with its status, evidence-quality level and numbered sources.
3	Systems and sectors	Where each system and sector stood at evidence close, read in words and never scored.
4	Risks and capability	The risk objects of the edition and the capabilities that hold them, on the ladder of evidence.
5	Scenario cascade	One conditional cascade under stated assumptions; never a prediction.
6	Readings from the other desks	Readings from the other desks: cross-references to their editions for the same scope, not copies of them.
7	The 2027 agenda	The research questions the operational series takes up next, each traced to a finding.
8	Systems in depth	One section per system: its state at evidence close, its exposures and what the series will watch.

05How to contribute

Send GCRI the evidence behind a finding, the method that produced it, or a model another team can run. A correction to a value in an edition is welcome in the same way.

This desk takes:

A dataset or source that bears on a coupled-systems finding, with its release and licence
A method, model or code that an edition could use or test
A correction to a value, a finding or a reference in a Systems Evidence edition
A documented case of a cascade across systems

The gateway page of the GCRI Systems Evidence desk gives the route.

06The editorial workflow

For a research contributor the workflow is a promise about time. The window in which you can submit, revise or appeal is fixed, and an editor cannot move it by hand.

Diagram of the editorial workflow in six steps: submit, screen, review, decide, accept, publish, with a revision branch and a decline or appeal branch. The list below gives every step.

The editorial workflow
Step	What happens
1. Submit	Contributor declarations and licence terms are signed first.
2. Screen	Editors check scope, completeness and licensing.
3. Review	Peer review runs under the model declared at submission. Authors may revise, then the work returns to review.
4. Decide	Named editors decide and record their reasons. Declined work can be appealed through a separate route.
5. Accept	The decision is recorded and the work moves to production.
6. Publish	A named editor publishes. The DOI is issued.

07The sixteen-gate quarterly cycle

Your work meets the cycle at the evidence close. A dataset or method that arrives after that gate waits for the next quarter, so plan the submission deadline first.

Diagram of the sixteen gates of a quarterly cycle, from the call opening to the corrections window closing. The list below gives every gate.

The sixteen gates of a quarterly cycle
Order	Gate	Meaning
1	call_open	The call opens.
2	call_close	The call closes.
3	submission_deadline	Last moment to submit into this cycle. Later submissions roll to the next cycle.
4	triage_close	Intake triage must be finished.
5	review_open	The review window opens.
6	reviewer_reminder	First reminder to reviewers.
7	review_close	Reviews are due. Overdue reviews escalate and are reassigned.
8	decision_date	The editorial decision is due.
9	revision_close	The revision window ends.
10	copyedit_freeze	Copyedit and data-check freeze.
11	evidence_close	Evidence close.
12	production_close	Production ends.
13	release_approval	The named approver signs the release.
14	release	Release date. It is the anchor of the cycle.
15	deposit_approval	Zenodo deposit approval. The deposit stays a draft until then.
16	corrections_close	The corrections window ends.

08Release control

Before release, an edition passes the checks listed here. The data check and the citation check are the two a researcher can prepare for in advance.

Diagram of release control: seven checks must pass, the named approver signs, six artefacts are fixed with checksums, the Zenodo deposit stays a draft, then the record is published with a DOI.

09Open licensing

You keep authorship. The edition publishes your text under CC BY 4.0, your data under CC0 1.0 and your code under an OSI-approved licence.

Licence rules

Text, figures and maps: CC BY 4.0 (SPDX: CC-BY-4.0).
Data: CC0 1.0 (SPDX: CC0-1.0).
Code: an OSI-approved licence.
Media: CC BY 4.0 or CC0 1.0.
No NC, ND or SA licence on our own outputs. No paywall, no embargo on text, no fees.

Shared text. It is the same on every Reports site by design.

10Zenodo community and DOIs

Research outputs are deposited to the GCRI desk community on Zenodo. It exists and is curated; every submission is reviewed before it is accepted, and it holds no records yet.

This desk’s community: zenodo.org/communities/nexusreports-gcri

Flagship community: nexusreports. It exists and holds records today.
Every record carries a DOI and a full version history. A correction becomes a new version and keeps the concept DOI.

Shared text. It is the same on every Reports site by design.

11The open science stack, with its honest status

Most of the open science stack is built. Two items are not complete, and they are marked below so a reader does not assume otherwise.

Diagram of the open science stack with the status of each integration. The table below gives every status.

The open science stack and its status
Integration	What it does	Status
Zenodo	DOIs, deposits and versions	Built
ORCID	Contributor identity and review credit	Built
ROR	Institution identifiers	Needs the id
COAR Notify	Inbox for peer review services	Built
OAI-PMH	A harvesting endpoint	Built
JATS XML	Journal article markup	Built
RO-Crate	Research object packaging	Built
Crossref	An export, not in use	Export only

Cite

Reports, GCRI Systems Evidence, start here [Draft under review]. GCRI for the Nexus Consortium.

Review copy. The DOI is issued at deposit. Text under CC BY 4.0.

Name	Purpose	Duration	Party
`wordpress_*`cookie	Strictly necessaryThis site	Until you sign out	First party
`wordpress_logged_in_*`cookie	Strictly necessaryThis site	Until you sign out, or 14 days	First party
`wordpress_sec_*`cookie	Strictly necessaryThis site	Until you sign out, or 14 days	First party
`wordpress_test_cookie`cookie	Strictly necessaryThis site	Session	First party
`wp-settings-*`cookie	Strictly necessaryThis site	1 year	First party
`wp-postpass_*`cookie	Strictly necessaryThis site	10 days	First party
`comment_author_*`cookie	Strictly necessaryThis site	About 347 days	First party
`wpEmojiSettingsSupports`browser storage	Strictly necessaryThis site	Session	First party
`nexus_consent`cookie	Strictly necessaryPrivacy choices	180 days	First party
`nexus_consent_id`cookie	Strictly necessaryPrivacy choices	180 days	First party
`nexus_consent_reset`cookie	Strictly necessaryPrivacy choices	Session	First party
`wp_consent_*`cookie	Strictly necessaryPrivacy choices	180 days	First party
`nexus_consent`browser storage	Strictly necessaryPrivacy choices	180 days	First party
`nx_theme`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`nexus.theme.default`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`bx-color-mode`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`bx-color-mode-against`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`nexus.embed.theme`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`buddyx_dark_mode`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`buddyx_color_mode_against`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`nexus.a11y`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`nexus.dock`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`bp-activity`browser storage	Strictly necessaryCommunity directories (BuddyPress)	As the provider sets it	First party
`bp-groups`browser storage	Strictly necessaryCommunity directories (BuddyPress)	As the provider sets it	First party
`bp-members`browser storage	Strictly necessaryCommunity directories (BuddyPress)	As the provider sets it	First party
`bp-blogs`browser storage	Strictly necessaryCommunity directories (BuddyPress)	As the provider sets it	First party
`bp-messages`browser storage	Strictly necessaryCommunity directories (BuddyPress)	As the provider sets it	First party

Start here: how this desk of Reports works