GCRI · Foundations
Non-execution: why shared resilience work informs, never decides
The non-execution boundary keeps every public, regulatory, financial and operational decision with the competent authority. This page explains what the Nexus Consortium programme may do, what it never does, and why that boundary is what makes participation safe.
- As of
- 21 October 2026
- Reading
- 11 minutes
- Evidence
- 16 sources, cited in order
Methods and evidence
- Evidence
- 16 sources, cited in order and listed under References
- Figures
- 4 figures
- Data availability
- Every chart's data is published as a table on this page.
01What the non-execution boundary is
What the non-execution boundary is
Non-execution is the boundary between preparing evidence and acting on it. The programme may frame questions, assemble and label evidence, build models, run controlled exercises, publish reviewed findings and prepare readiness dossiers. It never takes the public, regulatory, fiduciary or operational decision those outputs inform. "Decisions and execution remain with the relevant government, operator or licensed institution", and the competent authority stands outside the programme 1.
The rule is stated by each institution for its own role 2. GCRI, as Consortium Secretariat and steward of evidence and methods, "does not regulate, certify, license or approve". GRF, which leads leadership, dialogue and the governance of Nexus Universe, "does not regulate, finance, procure or certify". GRA, which leads finance, insurance and development readiness, "does not lend, underwrite, rate, invest, advise on or arrange transactions. Readiness is not approval." GRA sets out the same boundary in four short rules on its regulated-activity boundaries page: participation is not authority; readiness is not approval; visibility is not endorsement; stewardship is not execution 9.
The earlier version of this page called the boundary a "doctrine" of the whole ecosystem and attached it to rooms, rails and holds under retired names. The boundary is kept; those structures are not on the programme's record and are withdrawn.
02Why the boundary makes shared work usable
Why the boundary makes shared work usable
Shared resilience work sits next to authority everywhere. A hazard map sits next to a warning; an exercise next to a security assessment; a scenario next to a forecast; a readiness dossier next to a credit decision. Without a clear boundary, each participant's contribution can be read as something it is not, and the institutions with real mandates have every reason to stay away. With a clear boundary, they can take part. GRF names the risk exactly: the separation of evidence, deliberation and allocation means that "a modelled estimate cannot appear as consensus, and a dialogue outcome cannot appear as investment readiness" 10.
Warnings are the clearest case. The Sendai Framework commits countries to substantially increase the availability of and access to multi-hazard early warning systems by 2030 (target g) 11. Progress is measurable: in the 2025 global status report, 119 countries, 60 per cent of all countries, reported a multi-hazard early warning system, a 113 per cent increase in ten years, but only 43 per cent of small island developing states did 3. The 2024 edition found that countries with less comprehensive systems have a disaster mortality ratio nearly six times higher than countries with substantial to comprehensive coverage 12. And the Global Commission on Adaptation estimated that just 24 hours of warning of a storm or heat wave can cut the ensuing damage by 30 per cent 8.
Those gains depend on a warning chain that people trust, with one authoritative voice at its end. A research programme that issued its own alerts, however good its models, would compete with the authority and weaken the chain. That is why, in the programme's systems, a warning-support candidate is "never an alert", and any warning is issued "by the authority, not by Nexus" 4.
Fig. 01Warnings save lives when the chain is complete
Figure 1 in words, and its data
Left panel, per cent of countries reporting a multi-hazard early warning system, 2025: all countries 60 (119 countries, up 113 per cent in ten years); small island developing states 43. Right panel, value of warning: 24 hours of warning of a storm or heat wave can cut the ensuing damage by up to 30 per cent (Global Commission on Adaptation, 2019); countries with less comprehensive systems have a disaster mortality ratio nearly six times higher than those with substantial or comprehensive coverage (WMO and UNDRR, 2024).
| Measure | Value | Source and scope |
|---|---|---|
| Countries reporting a multi-hazard early warning system | 119 (60 per cent of all countries) | WMO and UNDRR, 2025 3 |
| Small island developing states reporting a system | 43 per cent | WMO and UNDRR, 2025 3 |
| Change in the number of reporting countries over ten years | +113 per cent | WMO and UNDRR, 2025 3 |
| Disaster mortality ratio, less comprehensive against substantial or comprehensive coverage | Nearly six times higher | WMO and UNDRR, 2024 12 |
| Damage avoided by 24 hours of warning of a storm or heat wave | Up to 30 per cent | Global Commission on Adaptation, 2019 8 |
03From observation to decision
From observation to decision
The programme's systems are designed so that the boundary is visible in the flow of evidence itself 4. A signal is captured by remote sensing, an in-situ instrument or an edge deployment and becomes an observation under the Nexus Observatory Protocol. Observations become governed evidence with quality and provenance in NXS-GRX (canonical data, provenance and risk), and are reviewed before use. NXS-EWS (multi-hazard monitoring and warning) may produce a warning-support candidate, which is never an alert. NXS-DSS (decision cases and deliberation) assembles a decision-support package with a trigger check. NXS-NSF (trust, authorization and assurance) applies the policy gate, and NXS-RLS (participants, agreements and handoffs) carries the lawful handoff under written agreements. Then the authority alone decides, and any warning is issued by the authority 4.
Every one of these systems is a design described for reading; nothing here records that any of them is deployed or in production use 4. The point of the design is that the last two steps, the decision and the warning, are drawn outside the programme from the start.
Fig. 02From observation to decision
Figure 2 in words
Two rows of boxes joined by arrows. Inside the programme: signal captured (remote, in-situ or edge); observation under the Nexus Observatory Protocol; governed evidence in NXS-GRX with quality and provenance; evidence review; warning-support candidate in NXS-EWS, never an alert; decision-support package in NXS-DSS with a trigger check; policy gate in NXS-NSF; lawful handoff in NXS-RLS under written agreements. Outside the programme: the authority alone decides; any warning is issued by the authority, not by the programme.
04The boundary in each domain
The boundary in each domain
The boundary is written into every programme offering and entry route, so that a participant knows before taking part what a result will and will not mean 5. The table summarizes the domains where it is most often tested.
| Domain | The programme may | It never | Who decides |
|---|---|---|---|
| Public authority | Scope a mandate-specific technical programme with a regulator or ministry | Confer regulatory approval or privileged access through participation 5 | The authority, under its own law |
| Procurement and technology | Run testbeds with versioned candidates and measured evaluation | Present testbed participation as a regulatory sandbox, a certification or a procurement status 5 | The procuring body |
| Warnings and response | Run preparedness exercises with simulation marking and stop-work controls | Exercise live actuation, incident command or warning authority, or act as an emergency-dispatch service 5 | The civil-protection or warning authority |
| Finance and insurance | Prepare exposure notes, scenario evidence and readiness dossiers | Promise funding, underwriting, a bankability rating, capital or a transaction 5 | The lender, insurer or finance ministry |
| Standards and conformance | Propose standards and record test results against them | Present test completion as accredited certification 5 | Standards councils and accreditation bodies |
| Learning and workforce | Record contribution and supervised work | Treat a learning record as a professional licence or a promise of employment 5 | The licensing body or employer |
Fig. 03The boundary in six domains
Figure 3 in words
Six rows. Public authority: may scope a technical programme; never confers regulatory approval or privileged access; the authority decides. Procurement and technology: may run testbeds; never a sandbox, certification or procurement status; the procuring body decides. Warnings and response: may run marked exercises with stop-work controls; never live actuation, incident command, warning authority or dispatch; the warning authority decides. Finance and insurance: may prepare dossiers; never promises funding, underwriting, a rating, capital or a transaction; the lender, insurer or ministry decides. Standards: may propose standards and record tests; never presents test completion as accredited certification; councils and accreditation bodies decide. Learning: may record contribution; never a licence or a promise of employment; the licensing body or employer decides.
05Gates are programme decisions, not approvals
Gates are programme decisions, not approvals
The programme does take decisions of its own, and they are recorded. The eight gates of the programme year, G0 to G7, from authorising the annual programme to reviewing renewal, are held by GRF as steward of Nexus Universe 13. Their meaning is fixed in a sentence: "A cycle gate is a programme decision. It is not a public-authority approval, a certification or a deployment authorisation" 13. A build accepted for exercise at G3 is accepted for an exercise and nothing else; publication authorised at G6 is the release of a reviewed edition, not an endorsement of its findings by any authority.
The same applies to the proposed Nexus Standards. Global councils decide global adoption, each National Standards Council decides national adoption, and neither decides for the other; adoption of a Nexus Standard is a standards decision, never a regulatory one 1. The governance of the Nexus Standards sets out the full matrix.
06How the boundary is checked
How the boundary is checked
A boundary is only as good as its record. Every programme carries one explicit state taken from a record, and the service level for the whole programme is R0, information and enquiries 5. Each institution keeps a public register of claims and states, GCRI's claims and readiness register, GRF's claims and programme state and GRA's claims and programme status, and anyone may ask for a correction without membership 14. GRA checks every output against a fixed set of questions before release, and releases a dossier only at the programme owner's written direction, with a release record 7.
Evidence labels carry the boundary into every finding: observed, published statistics, institution-reported, estimated, modelled, forecast, scenario, expert judgement or unknown. Simulated results are never reported as observed impact, and simulation messages are never delivered as official warnings 5.
07Where the decisions already sit
Where the decisions already sit
Non-execution is not a gap in governance; it reflects where the law already places each decision. Warning authority sits with national authorities under frameworks such as Sendai 11. Supervision of climate-related financial risk sits with supervisors, guided by the Basel Committee principles of 15 June 2022 15. ICT continuity in EU finance became a supervised obligation when DORA entered into application on 17 January 2025 16. The programme prepares evidence these authorities can read; supervisors may use published scenario evidence as any other source, and no participant gains privileged access 5.
08What the boundary does not prevent
What the boundary does not prevent
The boundary limits authority, not ambition. Within it the programme can run national baselines, sector dependency studies, sovereign capability assessments, responsible-innovation testbeds, preparedness exercises, cross-border missions, finance-readiness work, workforce formation, annual missions and reviewed publication: the ten offerings of the model, each with its own stated boundary 5. Negative findings and independent scrutiny always remain possible, a readiness effort may conclude that evidence is insufficient, and a rejected recommendation receives a reasoned disposition rather than disappearing 5.
For participants the practical meaning is simple. A ministry or regulator can bring a question through the route for governments and public institutions; a lender or supervisor can read evidence on GRA's finance and insurance readiness pages; a provider can respond to a testbed call through the route for technology providers. In each case the decision that follows is theirs.
Fig. 04Four boundaries, in the institutions’ own words
Figure 4 in words
Four columns. GCRI, evidence and methods: does not regulate, certify, license or approve. GRF, leadership, dialogue and Nexus Universe: does not regulate, finance, procure or certify. GRA, finance readiness: does not lend, underwrite, rate, invest, advise on or arrange transactions; readiness is not approval. Competent authority, outside: decides and executes. Beneath, GRA’s four rules: participation is not authority; readiness is not approval; visibility is not endorsement; stewardship is not execution.
09What is changing
What is changing
- Warning coverage is expanding. The number of countries reporting a multi-hazard early warning system rose 113 per cent in ten years, raising the stakes of keeping one authoritative voice 3.
- Small states lag. Only 43 per cent of small island developing states report a system, where evidence support matters most and authority must stay national 3.
- Supervisors are reading physical risk. The Basel principles and DORA bring climate and ICT risk inside supervision, which increases demand for evidence that is clearly not a supervisory finding 15,16.
- AI raises the risk of borrowed authority. Model outputs that sound institutional make the evidence label, not the fluency of the text, the test of what a finding is 5.
10Three institutions, one boundary
Three institutions, one boundary
The boundary is the same from three directions. For GCRI it means evidence and methods without approval, on its board and governance page. For GRF it means convening and gates without regulation, finance or procurement, set out in GRF in the Consortium. For GRA it means readiness without any regulated activity, on its non-execution boundary page. The GitBook page on decision rights and the GitBook guide for disaster and civil-protection agencies show how the boundary looks to an authority.
What this page does not claim: no programme is constituted or active and the service level is R0. The systems named are designs described for reading, not deployed services. The programme issues no warning, approval, certification, rating, financing or procurement decision and holds no regulated status. GCRI does not regulate or certify, GRF does not regulate, finance or procure, and GRA does not lend, underwrite, rate or invest. Naming a framework or an agency is not a claim of partnership or endorsement.
Questions
Questions and answers
Can the programme issue an early warning?
No. A warning-support candidate in the programme is never an alert. The competent authority alone decides and issues any warning, and simulation messages are never delivered as official warnings.
If a regulator takes part, has it approved the work?
No. Regulator participation confers no regulatory approval or privileged access. Participation is not authority, and visibility is not endorsement.
Is a testbed result a certification?
No. Testbed participation is not a regulatory sandbox, a certification or a procurement status, and test completion is never presented as accredited certification.
Does a readiness dossier mean a lender will finance a project?
No. Readiness evidence is not a financing or underwriting decision. The lender reviews independently and decides under its own authority.
Then what is the programme for?
Better evidence before decisions: baselines, dependency studies, exercises, reviewed reports and readiness dossiers, each labelled with its evidence type and its limits, for the institutions that decide.
What if a page or partner overstates a result?
Report it through the corrections route of any of the three institutions. No membership is needed, and an accepted correction creates a new recorded version.
Terms
Glossary
- Non-execution
- The boundary by which the programme prepares and publishes evidence but never takes a decision that belongs to an authority, operator or licensed institution.
- Competent authority
- The government body, operator or licensed institution with the legal mandate to decide and act.
- Warning-support candidate
- A programme output that may inform a warning authority; it is never an alert.
- Gate
- A recorded programme decision about the annual cycle, G0 to G7; never an approval or certification.
- Evidence label
- One of nine labels on every finding, from observed to unknown, stating what kind of evidence it is.
Reuse and cite
Text CC BY 4.0. Cite the page with its date; data tables are linked under each figure.
Sources
References
16 sources, numbered in the order they are first cited
- The Global Centre for Risk and Innovation (GitBook) (2026-10). Decision rights. docs.therisk.global. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). GCRI, GRF and GRA. therisk.global. Accessed 2026-10-21.
- World Meteorological Organization and UNDRR (2025-11). Global Status of Multi-Hazard Early Warning Systems 2025. wmo.int. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (GitBook) (2026-10). Systems: from observation to decision. docs.therisk.global. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (GitBook) (2026-10). Status and service levels: offerings and entry routes. docs.therisk.global. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). How Nexus Consortium works. therisk.global. Accessed 2026-10-21.
- The Global Risks Alliance (2026-10). Non-execution boundary. globalriskalliance.com. Accessed 2026-10-21.
- Global Commission on Adaptation (2019-09). Adapt Now: A Global Call for Leadership on Climate Resilience. gca.org. Accessed 2026-10-21.
- The Global Risks Alliance (2026-10). Regulated-activity boundaries. globalriskalliance.com. Accessed 2026-10-21.
- The Global Risks Forum (2026-10). Nexus Consortium relationship. globalriskforum.com. Accessed 2026-10-21.
- United Nations General Assembly (2015-06). Sendai Framework for Disaster Risk Reduction 2015–2030, A/RES/69/283. documents.un.org. Accessed 2026-10-21.
- World Meteorological Organization and UNDRR (2024-11). Global Status of Multi-Hazard Early Warning Systems 2024. wmo.int. Accessed 2026-10-21.
- The Global Risks Forum (2026-10). Programme governance of Nexus Universe. globalriskforum.com. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Claims and readiness register. therisk.global. Accessed 2026-10-21.
- Basel Committee on Banking Supervision (2022-06). Principles for the effective management and supervision of climate-related financial risks. www.bis.org. Accessed 2026-10-21.
- European Insurance and Occupational Pensions Authority (2025). Digital Operational Resilience Act (DORA). www.eiopa.europa.eu. Accessed 2026-10-21.
Record
Editorial record
Facts and programme states are given as of 21 October 2026. This page is reviewed at least every 180 days and whenever a cited figure or a programme state changes. It replaces an earlier version of the same page, which presented non-execution as an ecosystem doctrine tied to "Safety Holds", "Stack Passports", capital-reader rooms and rails under retired names; the boundary itself is kept, and those structures, which are not on the programme's record, are withdrawn.
Published by the GCRI editorial desk under the scientific and editorial integrity policy. To report an error or request a correction, use the corrections route; corrections are dated and listed with the page.
Cite this article
GCRI editorial desk (2026, June 8). Non-execution: why shared resilience work informs, never decides. The Global Centre for Risk and Innovation. https://therisk.global/non-execution-doctrine-the-boundary-that-makes-shared-resilience-infrastructure-usable/
@online{gcri2026nonexecutiondoctrinet,
author = {{GCRI editorial desk}},
title = {{Non-execution: why shared resilience work informs, never decides}},
publisher = {The Global Centre for Risk and Innovation},
year = {2026},
month = {6},
url = {https://therisk.global/non-execution-doctrine-the-boundary-that-makes-shared-resilience-infrastructure-usable/},
language = {en}
} TY - ELEC AU - GCRI editorial desk TI - Non-execution: why shared resilience work informs, never decides PB - The Global Centre for Risk and Innovation PY - 2026 DA - 2026/06/08 UR - https://therisk.global/non-execution-doctrine-the-boundary-that-makes-shared-resilience-infrastructure-usable/ LA - en ER -
Republish
Republish or translate this article free of charge, in print or online, under CC BY 4.0: keep the byline and The Global Centre for Risk and Innovation, link to the original and note any change. Figures, maps and twins made by the institutions carry the same licence; third-party data keeps its own credit line.
Attribution to paste
<p>Non-execution: why shared resilience work informs, never decides — GCRI editorial desk, The Global Centre for Risk and Innovation. First published 8 June 2026 at <a href="https://therisk.global/non-execution-doctrine-the-boundary-that-makes-shared-resilience-infrastructure-usable/">https://therisk.global/non-execution-doctrine-the-boundary-that-makes-shared-resilience-infrastructure-usable/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>