> 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/governance-in-operation/a-national-mission.md). # A national mission, from mandate to renewal One national mission through the programme year, from the annual mandate (G0) to renewal (G7): which pillar, institution and national body acts at each step, and which record each step leaves. Illustr **Where this fits.** Governance in operation › national level · all six pillars · national structures, GCRI, GRF, GRA, Nexus Standards bodies, competent authorities · every phase, G0 to G7 · worked example (illustrative). {% hint style="warning" %} **Illustrative.** This page follows one hypothetical mission through a hypothetical year. It describes the design of the sequence. It records no mission, country, exercise or result. No national programme is recorded as constituted or active, and the current service level is R0, information and enquiries. {% endhint %} ## In brief A mission starts as a material question that a country raises and ends, a year later, as reviewed evidence handed to the institutions that can act on it, with corrections and a renewed mandate. Between those points it crosses every pillar. The Nexus Consortium model, as published on [How Nexus Consortium works](https://therisk.global/consortium/), names the chain: **Material question → Accountable agenda → Institutional and expert capacity → Persistent Foundry project → Qualified computation or inquiry → Controlled exercise → Reviewed evidence → National Portfolio movement → Publication → Competent next action → Correction and renewal** **Boundary.** Every gate in this page is a programme decision recorded by GRF as steward of [Nexus Universe](/organization/programme/universe.md). None is a public-authority approval, a certification or a deployment authorisation. Real-world decisions stay with the competent authority throughout. The country owns the agenda, the data and the decisions at every step.
An illustrative national mission, read across eight lanes. The national structures (National Desk, NNC, NLC and NWG) raise the material question and own the agenda, data and decisions throughout. GRF, as steward of Nexus Universe, authorises the annual mandate (G0), admits the mission (G1), accepts the build for exercise (G3), authorises controlled live operation in Action Week (G4), authorises publication (G6) and reviews renewal (G7). GCRI, through its technical office and the Foundry pillar, opens the cycle project and the National Portfolio baseline, qualifies data and resources (G2), delivers the Core Build Report, seals the evidence (G5) and records portfolio movement. Nexus Standards composes mission profiles and records national adoption, receives conformance evidence and change proposals. Nexus Reports agrees the country profile scope before Q1 and publishes the quarterly editions and the Q4 synthesis. Risk Academy runs qualification courses and records completion. GRA runs the finance-readiness track and releases a readiness dossier only on the programme owner's written direction. The competent authority, outside the programme, takes every real-world decision.

One national mission through the programme year. Illustrative: a design of the sequence, not a record of any mission. Gates are programme decisions, never public-authority approvals; no national programme is recorded as constituted or active. Source: Programme model behind the GCRI, GRF and GRA homes (phases, gates G0 to G7, handoffs F01 to F14); therisk.global/consortium/national/; globalriskforum.com/nexus-universe/grf-role/; globalriskalliance.com/finance-readiness/handoff/. As of 2026-10-21.

Figure data (text alternative) | Element | Description | Connected to | | -------------------- | ------------------------------------- | ----------------------------------------------------------------------- | | Material question | Via the National Desk | G0 Mandate | | G0 Mandate | Planning, Q1 | Material question; Cycle project; G1 Admission | | Cycle project | National Portfolio baseline | G0 Mandate | | Profile scope | Agreed before Q1 | | | NWG assignments | Sources and model inputs | | | G1 Admission | Readiness preparation, Q2 | G0 Mandate; G2 Qualified | | G2 Qualified | Data and resources (F01) | G1 Admission; Core Build Report | | Mission profiles | With national adoption (F08) | Core Build Report | | Qualification | Courses for admitted roles | | | G3 Build accepted | After the one-month build | Core Build Report; G4 Action Week | | Core Build Report | Go or no-go evidence (F02) | Mission profiles; G2 Qualified; G3 Build accepted; Conformance evidence | | Conformance evidence | For review (F13) | Core Build Report | | Exercise roles | National participants | | | G4 Action Week | Controlled live operation | G3 Build accepted; G5 Evidence sealed | | G5 Evidence sealed | Stand-down and closeout (F03) | G4 Action Week; Portfolio movement | | Completion records | Assessed tasks (F10) | Qualified people | | Finance track | Simulated loss is not observed impact | | | Real-world action | The authority alone decides | | | Portfolio reviewed | The country decides entries | Quarterly alignment | | After-action report | To Reports (F04) | Portfolio movement; G7 Renewal | | Portfolio movement | Recorded (F05) | G5 Evidence sealed; After-action report | | Change proposals | Corrections (F06) | | | G6 Publication | Q4 synthesis authorised | | | Readiness dossier | On written direction only | Recipient decides | | Recipient decides | Ministry, lender or insurer | Readiness dossier | | Quarterly alignment | NNC and NLC priorities | Portfolio reviewed | | G7 Renewal | Next mandate (F12) | After-action report | | Qualified people | Next cycle roles (F11) | Completion records |
## Step 0: forming the agenda The mission enters the year through agenda formation. The model sets nine steps: 1. National Desks collect material questions, capability gaps and candidate missions. 2. Regional coordination identifies shared dependencies: basins, grids, health systems, ports, corridors, digital infrastructure and financial exposure. 3. GCRI's evidence process classifies what is observed, unknown, modelled and worth testing. 4. GRF's participation process tests inclusion, institutional fit, leadership demand and public-purpose legitimacy. 5. GRA's readiness process identifies financial transmission, protection gaps and diligence requirements without selecting investments. 6. Scientific and affected-stakeholder challenge informs mission selection and methods. 7. The authorised annual mandate sets scope, budget, participating structures, evaluation questions and publication intentions. 8. National structures keep their own agenda authority and may decline participation or data sharing. 9. Quarterly evidence and annual results revise the mandate through a recorded change process. In the illustrative mission, a National Desk records a material question: how far a flood in the capital region would interrupt water, power and clinic access together. This is the urban-flood context of [The Model](/organization/model.md). The question has a competent recipient, the national water and power regulators, so it can enter the mandate. ## The year, step by step The programme year runs at five time scales: a year to prepare, a month to build, a week to act and test, a day to stand down, and a following period to review and renew. | Time scale | Work | Entry | Exit | | ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | | One year: Prepare | National demand, research, institutional participation, monthly working-group delivery, quarterly evidence, technology and resource qualification. | Annual mandate, programme owners and provisional resources. | An approved mission portfolio, qualified inputs and an achievable build plan. | | One month: Build | Assemble the Core, bind authorised resources, integrate software and data, test security and interoperability, train teams and rehearse. | Rights, budget, site safety, technical capacity and mission scope. | Core Build Report, measured readiness, known defects and go or no-go decisions. | | One week: Act and test | Controlled exercises, scenario work, benchmarks, independent observation, leadership deliberation and public-safe engagement. | Qualified environments, controllers, evaluators, a scenario plan and stop-work authority. | Run, decision and observation records, limitations, an evidence seal and improvement items. | | One day: Stand down (proposed) | Stop new work, checkpoint authorised jobs, revoke temporary access, isolate or release temporary capacity, reconcile equipment and seal transferable evidence. | An approved closeout plan, retention decisions and accountable operators. | A stand-down receipt, a preserved evidence manifest and named unresolved exceptions. | | Following period: Review and renew | Validate archives, complete scientific and editorial review, publish approved results, reconcile support and close corrective actions. | Persistent owners and retained evidence. | Reviewed publications, closed corrections and the next-cycle mandate. | Within that frame, the mission moves through the eight gates: | Gate | What happens to the mission | Who acts | Record left | | -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | | **G0** Annual programme authorised (Planning, Q1) | The mission's question is in the authorised annual mandate | GRF authorises; the National Desk and NNC [Helix councils](/organization/governance-in-operation/councils.md) raised the question; GCRI opens the cycle project and the National Portfolio baseline | Cycle mandate; portfolio baseline; country profile scope agreed before Q1 | | **G1** Missions admitted (Readiness preparation, Q2) | The mission is admitted with a decision case; F01 turns it into a cycle project | GRF admits; the NLC has proposed it as a national priority | Admission decision | | **G2** Data and resources qualified (Q2) | Sources, people and resources are qualified. Standards composes the mission profile and records national adoption (F08). [Risk Academy](/organization/programme/academy.md) runs the qualification courses | GCRI technical office; NWG assignments; the NSC for adoption; [Risk Academy](/organization/institutions/risk-academy.md) | Qualified resource list; mission profiles; qualified participants | | **G3** Build accepted for exercise (Controlled build, one month, Q2) | The [Foundry pillar](/organization/programme/foundry.md) builds the city twin of substations, pumps and clinics on the Nexus systems; the Core Build Report goes to Universe (F02); validation evidence goes to Standards (F13) | GCRI builds in the Foundry pillar; GRF accepts | Core Build Report; signed builds; validation evidence | | **G4** Controlled live operation authorised (Action Week, Q3) | A controlled exercise keeps water and power running through a 1-in-100 flood, with independent evaluators. GRA runs the finance-readiness track | GRF authorises; operators and NWG [CERTs](/organization/governance-in-operation/nwg.md) take exercise roles; GRA | Run, decision and observation records; exercise assessments | | **G5** Evidence sealed and stand-down recorded (Closeout, Q3) | New work stops, temporary access is revoked and transferable evidence is sealed; sealed observations go to Reports (F03); assessed tasks become completion evidence (F10) | GCRI; Risk Academy | Stand-down receipt; evidence seal; completion records | | (After-action review, Q3) | Findings go to Reports (F04); National Portfolio movement is recorded (F05) | GRF; GCRI; the country decides what enters its portfolio | After-action report; portfolio update; change proposals | | **G6** Publication authorised (Reporting, Q4) | The Q4 annual synthesis and the country profile are published after review. Method findings become change proposals for the standards (F06). On the programme owner's written direction, GRA releases a readiness dossier to a competent party the owner names | GRF authorises publication; [Nexus Reports](/organization/programme/reports.md) publishes; GRA releases | Q4 synthesis; country profile; release record | | **G7** Renewal reviewed (Renewal, Q4) | The Q4 synthesis informs the next mandate (F12); qualified participants are available for next year's roles (F11); adopted profiles become course modules (F09) | GRF reviews; the NNC and NLC set next priorities at their quarterly alignment | Renewal decision; next-cycle mandate | ## Who decides, at every step The mission never moves a decision out of the hands that hold it: * **The country** decides what enters its portfolio, what it shares and whether to continue. It may decline at any point. * **The water and power regulators and the operators** decide any real-world change to their systems. The exercise gives the programme no control of operational technology, and "exercises carry no live actuation, incident command or warning authority" (offering O02). * **The receiving institution** decides on the readiness dossier: a ministry of finance, a development lender or an insurer, under its own authority and criteria. * **Reviewers and the publisher** decide what is accepted as evidence. "Institutional influence cannot decide a scientific conclusion." ## What the mission leaves behind At the end of the year, the illustrative mission has left: * a cycle project, sealed evidence and a National Portfolio entry, all owned by the country; * an after-action report and a country profile in the Q4 edition; * change proposals for the standards and new course modules; * a readiness dossier released to one named institution, with a release record; * completion records for the people who took part; * a renewed question for the next mandate. Each of these is a record with an identifier, as the [programme year](/organization/programme/the-programme-year.md) sets out. None is an approval, a rating or a commitment. ## Sources * GCRI: the Nexus Consortium model, as published on [How Nexus Consortium works](https://therisk.global/consortium/); [Annual programme cycle](https://therisk.global/programmes/annual-cycle/); [National Nexus](https://therisk.global/consortium/national/). * GRF: [Nexus Universe at GRF](https://globalriskforum.com/nexus-universe/); [Programme governance](https://globalriskforum.com/nexus-universe/grf-role/). * GRA: [Universe finance-readiness programme](https://globalriskalliance.com/engagement/nexus-universe/); [Lawful handoffs](https://globalriskalliance.com/finance-readiness/handoff/). * The programme model behind the GCRI, GRF and GRA homes: phases, gates G0 to G7 and handoffs F01 to F14 ([How Nexus works](https://therisk.global/nexus-cycle/)). * [Sources library](/organization/reference/sources.md). --- # 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/governance-in-operation/a-national-mission.md?ask=&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.