Start here: how this desk

01What Reports is

Reports is the Consortium’s quarterly publication, and the Global Risks Forum writes the desk that records public deliberation. If you sat in a convening, a council or a dialogue, this is where what you concluded, and where you disagreed, becomes part of the record.

Atlas of the GRF Public Deliberation 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 GRF Public Deliberation desk atlas, with its facts written out below.

02This desk: Public Deliberation

The Forum holds the public meaning of an edition. It reports what a convening was asked, what it concluded, where participants dissented and which questions stayed open.

Mandate: The record of deliberation: what a convening, council, dialogue or working group was asked, what it concluded, where participants disagreed and which questions stayed open.

Series this desk leads:

Observatory Signal
Strategic Systems
Evidence Brief

03The six desks

Public Deliberation 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

The frame is shared with the other desks, so a reader can compare a Forum edition with a systems edition chapter by chapter.

The eight chapters of the Public Deliberation edition
Chapter	Title	What it covers
1	What was asked, and by whom	The questions put to the convenings of the cycle, and the bodies and roles that put them.
2	Conclusions and dissent	What the convenings concluded, with the dissent recorded beside each conclusion.
3	Positions by sector	The positions stated by sector and by type of body, attributed to those who hold them.
4	Public concerns	The concerns raised by the public and by civil society, as they were raised.
5	Deliberated scenarios	The scenarios the convenings discussed, and what participants said would change their view.
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	Commitments asked for	The commitments participants asked of institutions, recorded as requests, not as agreements.
8	Session records	The record of each session: agenda, participation by role, materials and outcome.

05How to contribute

Send the Forum the outcome of a convening, a stakeholder position or a recorded dissent. A dissent is not a defect here. It is part of what the desk publishes.

This desk takes:

The outcome of a convening, with its agenda and who took part, by role
A stakeholder position, stated by the body that holds it
A recorded dissent or minority view
A question a convening left open for the next edition

The gateway page of the GRF Public Deliberation desk gives the route.

06The editorial workflow

A position sent to the Forum follows the same steps as any other work. Reasons for every decision are recorded, so a participant can see why a position was or was not taken up.

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

Convenings run on their own calendar. The cycle tells you the last date a session record can reach the next edition, and the date after which it waits a quarter.

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

The checks matter to a participant for one reason. A session record is cited only after the data and legal checks pass, and the approver cannot be one of its authors.

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

Reusing a deliberation record needs no permission beyond the licence. Text is CC BY 4.0. Say so to participants before they speak on the record.

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

Session records are deposited to the Forum’s own community on Zenodo. It exists and is curated; the Forum reviews every submission, and no record is in it yet.

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

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

Participants with an ORCID can be credited for their contribution. The status of every other integration is shown below.

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, GRF Public Deliberation, start here [Draft under review]. The Global Centre for Risk and Innovation (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