Start here: how this desk

01What Reports is

Reports is the Consortium’s quarterly publication, and the Global Risks Alliance writes the desk that asks whether finance and insurance can read a finding. If you price risk or allocate capital, this desk tells you what the evidence supports and what it does not.

Atlas of the GRA Capital Readiness 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 GRA Capital Readiness desk atlas, with its facts written out below.

02This desk: Capital Readiness

The Alliance holds the capital meaning of an edition: protection gaps, portfolio readiness and disclosure. It states what a finding can and cannot be used for in a balance sheet.

Mandate: How far finance and insurance are ready for the risks in scope: protection gaps, disclosure practice, portfolio readiness and the capacity of balance sheets, read on a ladder of evidence and never as advice or a rating.

Series this desk leads:

Finance and Insurance Readiness
Portfolio and Readiness

03The six desks

Capital Readiness 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

Each chapter is framed in the language of capital, from exposure to market actions.

The eight chapters of the Capital Readiness edition
Chapter	Title	What it covers
1	Exposure and capital	The exposures in scope and the capital that stands behind them, as public sources state them.
2	Readiness findings	The readiness findings of the edition, each placed on the ladder of evidence with its source.
3	Protection gaps by sector	Where insured and uninsured losses diverge, by sector, from published loss and cover data.
4	Balance-sheet and insurance capacity	The capacity of public and private balance sheets and of insurance to absorb the risks in scope.
5	Stress test	A conditional stress test under stated assumptions; never a forecast, a rating or advice.
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	Market actions	Actions markets and public finance could examine, stated as questions for evidence, never as recommendations.
8	Instruments and products	The instruments and products in use or under discussion, described from their public documentation.

05How to contribute

Send the Alliance a protection gap with its source, an insurance or finance case, or a disclosure practice that other firms could adopt. Name the instrument and the data behind it.

This desk takes:

Evidence of a protection gap, with its source and the period it covers
An insurance or finance case, documented with where its record is kept
Disclosure practice, with the framework it reports against
A correction to a readiness statement in a Capital Readiness edition

The gateway page of the GRA Capital Readiness desk gives the route.

06The editorial workflow

A case from a regulated firm passes the same gates as every other contribution. The legal check is part of the release, so state early what you can disclose.

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

Reporting calendars differ across firms. The evidence close is the date that matters: a figure supplied after it is read in the next cycle.

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

Capital users should note the legal and licence checks. A figure leaves the edition only when its source and its licence allow reuse.

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

Your figures stay yours. Where the data is yours to share, an edition may publish it under CC0 1.0. Where it is not, the edition cites it and does not republish it.

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

Alliance records go to the Alliance community on Zenodo. It exists and is curated by the Alliance desk; it holds no records yet.

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

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

Institution identifiers matter to this audience. ROR is not complete until GCRI’s id is supplied, and the Crossref route is an export only.

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, GRA Capital Readiness, 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