> 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/programme/labs.md). # Labs The Labs pillar of the Nexus programme: where questions become experiments and prototypes, tried in the open with their limits on record before the Foundry pillar builds them. *Where this fits: applied response. Pillar: Labs. Institution: GCRI. Phases: through the year, with no recorded handoff of its own yet. Kind: pillar page.* **In brief.** The Labs pillar is where the programme explores. A question raised by a national team, a guild or a learner becomes an experiment or a prototype: a new method, a dataset or a tool, tried in the open with its limits on record. Only a reproducible prototype passes on, to the Foundry pillar, which rebuilds it before [Nexus Universe](/organization/programme/universe.md) tests it. Until then its results are exploratory and are labelled that way. The Labs pillar is published on the GCRI site on [its programme page](https://therisk.global/nexus-labs/), with its technical gateway at [Labs](https://therisk.global/ecosystem/labs/). > **Boundary.** "An experiment is exploratory: its results are labelled as such and become evidence only after the Foundry rebuilds and the Universe tests them."
Labs on the hexagon of the six pillars, with the pillars it hands work to or receives work from selected, every handoff among those pillars, and the phases of the programme year in which recorded handoffs happen. Pillars it exchanges no work with are shown unselected.

Labs in the programme. A designed programme cycle, not a record of operation. Handoff identifiers F01 to F14 and R1 to R4 as in the sites' pillar model. Source: the sectors and pillars model published on the GCRI, GRF and GRA home pages, vendored and hash-pinned in tools/figures/vendor/nexus-model. As of 2026-10-21.

Figure data (text alternative) | Element | Kind | Description | Value | | --------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | | F01 | Handoff | Universe to Foundry: Admitted mission becomes a cycle project with a decision case | Readiness preparation | | F02 | Handoff | Foundry to Universe: Core Build Report and go or no-go evidence | Controlled build | | F03 | Handoff | Foundry to Reports: Sealed observations and indicator series behind a profile | Closeout | | F04 | Handoff | Universe to Reports: After-action and scenario findings for chapters 10 and 13 | After-action review | | F05 | Handoff | Foundry to Reports: National Portfolio movement for chapter 11 | After-action review | | F06 | Handoff | Reports to Standards: Method and correction findings as change proposals | Correction | | F07 | Handoff | Universe to Standards: Docket items that need a standard or a profile | Docket review | | F08 | Handoff | Standards to Foundry: Composed mission profiles and national adoption records | Readiness preparation | | F09 | Handoff | Standards to Academy: Each adopted standard or profile becomes a course module | Renewal | | F10 | Handoff | Universe to Academy: Assessed cycle tasks become completion evidence | Closeout | | F11 | Handoff | Academy to Universe: Qualified participants for the next cycle's roles | Renewal | | F12 | Handoff | Reports to Universe: Q4 synthesis informs the next-year mandate | Renewal | | F13 | Handoff | Foundry to Standards: Validation and monitoring evidence for conformance review | Controlled build | | F14 | Handoff | Foundry to Academy: Each system's rooms become a learning-by-doing course | Planning | | R1 | Handoff | Standards to Reports: Applied in editions | Around the ring | | R2 | Handoff | Reports to Academy: Taught in the open | Around the ring | | R3 | Handoff in play | Academy to Labs: Questions become experiments | Around the ring | | R4 | Handoff in play | Labs to Foundry: Tested prototypes are built | Around the ring | | Labs | Pillar | Explore, experiment and prototype | in this route | | Foundry | Pillar | Build, simulate and prepare | in this route | | Universe | Pillar | Convene and test | – | | Standards | Pillar | Codify, correct and apply | – | | Reports | Pillar | Publish in every format | – | | Academy | Pillar | Teach in the open | in this route | | Planning | Phase (Q1, G0) | F14 Each system's rooms become a learning-by-doing course | 1 handoff(s) | | Readiness preparation | Phase (Q2, G2) | F01 Admitted mission becomes a cycle project with a decision case; F08 Composed mission profiles and national adoption records | 2 handoff(s) | | Controlled build | Phase (Q2, G3) | F02 Core Build Report and go or no-go evidence; F13 Validation and monitoring evidence for conformance review | 2 handoff(s) | | Closeout | Phase (Q3, G5) | F03 Sealed observations and indicator series behind a profile; F10 Assessed cycle tasks become completion evidence | 2 handoff(s) | | After-action review | Phase (Q3) | F04 After-action and scenario findings for chapters 10 and 13; F05 National Portfolio movement for chapter 11 | 2 handoff(s) | | Correction | Phase (Q4) | F06 Method and correction findings as change proposals | 1 handoff(s) | | Docket review | Phase (Q4) | F07 Docket items that need a standard or a profile | 1 handoff(s) | | Renewal | Phase (Q4, G7) | F09 Each adopted standard or profile becomes a course module; F11 Qualified participants for the next cycle's roles; F12 Q4 synthesis informs the next-year mandate | 3 handoff(s) |
## How the Labs pillar works **Questions first.** The Labs pillar opens each year on the questions the annual mandate names, and closes it by proposing next year's questions. Its rhythm is one of short cycles: prototypes are run quickly, the reproducible ones are handed to the Foundry, and ideas are tried alongside Action Week so that failure is cheap and recorded. "What failed and why" is a record of the pillar, kept with the same care as what worked. **Two ring handoffs.** In the sites' model, the Labs pillar has no recorded handoff in a named phase yet. It sits on the ring between [Risk Academy](/organization/institutions/risk-academy.md) and the Foundry pillar: questions arrive from teaching (R3, "questions become experiments") and tested prototypes leave for building (R4, "tested prototypes are built"). The programme has six pillars, shown as six hexagons (owner ruling, 21 October 2026); the programme spine published with the Foundry still lists five and does not yet model the Labs pillar's joins with Nexus Universe or [Nexus Standards](/organization/institutions/nexus-standards.md). Those joins are open design work and are not described here as operating. **Evidence discipline.** An experiment's output carries one of the programme's evidence labels, normally "Modelled", "Scenario" or "Expert judgement", never "Observed", until the Foundry has rebuilt it and a Universe mission has tested it. This keeps exploratory science, which must be free to fail, apart from the governed evidence on which decisions are later prepared. It follows the risk-management principle that information be the best available while its limitations and uncertainties are stated explicitly ([ISO, 2018](https://www.iso.org/standard/65694.html)). **Ownership of data.** National teams propose experiments on their own questions and keep ownership of their data. An experiment run for a country does not move that country's data into a shared pool. ## The pillar in the model The tables in this section are generated from the sites' pillar model, so they match the GCRI, GRF and GRA home pages. ### At a glance What the pillar does, the records it owns, the boundary it keeps and where it is published. | | | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Does | Turns open questions into designed experiments; Prototypes new methods, data pipelines and tools; Records failures and limits alongside results; Hands reproducible prototypes to the Foundry | | Records it owns | experiment register; prototype record; working papers | | Boundary | An experiment is exploratory: its results are labelled as such and become evidence only after the Foundry rebuilds and the Universe tests them. | | Public home | [therisk.global/nexus-labs](https://therisk.global/nexus-labs/) | | On the institutions' sites | [GCRI: the Labs pillar](https://therisk.global/nexus-labs/) | | Further pages | [the Labs pillar](https://therisk.global/nexus-labs/) | ### Handoffs The handoffs this pillar sends and receives. Recorded handoffs (F01 to F14) happen in a named phase; ring handoffs (R1 to R4) run continuously. | Id | Direction | Phase | What moves | | -- | ------------------------------------------------------- | ---------- | ---------------------------- | | R3 | From [Risk Academy](/organization/programme/academy.md) | Continuous | Questions become experiments | | R4 | To [Foundry](/organization/programme/foundry.md) | Continuous | Tested prototypes are built | ### Through the year What the pillar does in each quarter and in each phase of the programme year. | Quarter | Edition | What this pillar does | | ------- | ---------------------------- | ----------------------------------------------------------------------- | | Q1 | State and Agenda | Opens the year's experiments on the questions the mandate names | | Q2 | Evidence and Build | Runs prototypes in short cycles; hands reproducible ones to the Foundry | | Q3 | Stress Test and Readiness | Tests ideas alongside Action Week; records what failed and why | | Q4 | Annual Synthesis and Renewal | Writes up every experiment; proposes next year's questions | ### At each scale What the pillar does locally, nationally, regionally and at planetary scale. | Scale | What this pillar does at that scale | | --------- | ---------------------------------------------------------------------------------------------------- | | Local | Experiments run on real places and systems, with the location and boundary of every result recorded. | | National | National teams propose experiments for their own questions and keep ownership of their data. | | Regional | Regional experiments compare methods across countries before one is chosen for the Foundry. | | Planetary | Planetary experiments test methods against global data, labelled as exploratory until reproduced. | ### In each operating area The fourteen operating areas the programme answers for, as this pillar answers them. | Area | Question | For this pillar | | ---------------------- | --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | Leadership | Who leads, and on what record. | Each experiment has a named lead and a written question; leading an experiment confers no authority over the decision it informs. | | Strategy | How the year's priorities are set. | Experiments are chosen for the questions the annual programme cannot answer yet, and retired when they stop teaching anything new. | | Cadence | When the work happens in the year. | Experiments run in short cycles inside the annual programme, each closing with a recorded result before the next begins. | | Ownership | Which records each pillar owns. | Every prototype carries its owner, its licence and its limits, so it can be handed to the Foundry or retired on the record. | | Process | How work moves, step by step. | Question, design, run, record, review: a prototype moves to the Foundry only when its result is reproducible. | | Development | What is developed, and how capacity grows. | New methods, data and tools are developed in the open, with failures kept on the record alongside successes. | | Simulations | How scenarios and exercises are run and read. | Exploratory simulations test an idea before it is built; they are labelled as experiments, never as findings. | | Reporting | How results reach the public record. | Each experiment is written up with its method, data and limits, and the results feed Nexus Reports as working papers. | | Governance | Who decides, and what a decision is not. | Labs tries the idea in the open first, with its limits on record, before it is built. | | Data and evidence | Where the evidence comes from and how it is kept. | Labs tries the idea in the open first, with its limits on record, before it is built. | | Finance and resourcing | How work is resourced and made readable to finance. | Labs tries the idea in the open first, with its limits on record, before it is built. | | Risk and assurance | How errors are caught and limits are stated. | Labs tries the idea in the open first, with its limits on record, before it is built. | | Participation | Who takes part, and how. | Labs tries the idea in the open first, with its limits on record, before it is built. | | Communication | How each pillar speaks in public. | Labs tries the idea in the open first, with its limits on record, before it is built. | ### Applied to the eight contexts How the pillar would apply to each teaching context of the model, and the measure it would answer for. These are illustrative applications, not delivered projects. | Context | Illustrative application | Measure | Applied | | ------------------------------------------------------------------- | --------------------------------------------------------- | --------------------------------------- | ------- | | [Urban flood](/organization/model/scenarios/urban-flood.md) | Flood-depth nowcast from rain gauges and terrain | Warning lead time (higher is better) | yes | | [Hydropower reservoir](/organization/model/scenarios/hydropower.md) | Inflow forecasts and sediment models for the reservoir | Forecast skill (higher is better) | yes | | [Drought](/organization/model/scenarios/drought.md) | Drought index from rainfall, soil moisture and river flow | Lead time to trigger (higher is better) | yes | | [Heatwave](/organization/model/scenarios/heatwave.md) | Heat-health thresholds from temperature and admissions | Threshold accuracy (higher is better) | – | | [Grid blackout](/organization/model/scenarios/blackout.md) | Cascade model of what fails when the grid does | Dependencies mapped (higher is better) | – | | [Pandemic](/organization/model/scenarios/pandemic.md) | Workforce-absence scenarios for essential services | Scenarios tested (higher is better) | – | | [Pollinator decline](/organization/model/scenarios/pollinator.md) | Maps of pollinators and the yields that depend on them | Area mapped (higher is better) | yes | | [Coastal storm surge](/organization/model/scenarios/storm-surge.md) | Surge model with mangrove and dune buffers | Coast modelled (higher is better) | yes | ### The institutions in this pillar What GCRI, GRF and GRA each contribute. | Institution | Contribution | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | GCRI | Runs the experiments: its science and technology teams design prototypes, record the method and publish what failed as well as what worked. | | GRF | Brings the questions that policy and governance need answered, and admits an experiment to the programme at a recorded gate. | | GRA | Brings finance questions to test, so a prototype is tried on evidence that financial institutions can read. | ## Read further * [Programme](/organization/programme.md): the six pillars together. * [The programme year](/organization/programme/the-programme-year.md): every phase, gate and actor. * [The Nexus cycle](/organization/programme/the-nexus-cycle.md): from a question to renewal, and who decides. * [The model](/organization/model.md): coupled risk and applied response. ## Sources * GCRI, [the Labs programme page](https://therisk.global/nexus-labs/) and [Labs](https://therisk.global/ecosystem/labs/), as of 2026-10-21. * ISO (2018). [ISO 31000:2018 Risk management: Guidelines](https://www.iso.org/standard/65694.html). Geneva: International Organization for Standardization. * Pillar model and programme spine of the sites (vendored in the documentation repository, `tools/figures/vendor/nexus-model`): the source of every generated table on this page. --- # 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/programme/labs.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.