GCRI · Foundations
The Foundry pillar: preparing capabilities before the annual cycle
Before a programme year tests anything, its software, data, models and environments have to be built and qualified. This page explains how the Foundry pillar of the Nexus programme prepares capabilities under recorded gates, and why a simulated capability is never a validated result.
- As of
- 21 October 2026
- Reading
- 13 minutes
- Evidence
- 11 sources, cited in order
Methods and evidence
- Evidence
- 11 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 Foundry pillar is
What the Foundry pillar is
The Foundry pillar is the build pillar of the programme, one of six with Labs, Nexus Universe, Nexus Standards, Reports and Risk Academy 1. It builds the software, data and environments a programme year needs, simulates scenarios and runs benchmarks, monitors hazards, systems and evidence, and develops and tracks each country's National Portfolio. GCRI runs it as part of the programme's technical office, which handles scoping, qualification, the build, exercise support, evidence capture and closeout 4,1. The pillar works on the twenty Nexus systems, each a governed environment with named rooms, so that every handoff of the year is written in a place where what crossed, when and under which gate can be traced.
The question this page answers is a practical one: what has to be true of a capability before the annual test, and who decides that it is? The answer is the sequence of phases and gates in the programme year, and the boundaries that keep preparation from being mistaken for proof.
An earlier version of this page described a separate preparation and acceleration layer, with sponsors and providers maturing their own tools toward a stage of the annual cycle. That framing is not on the programme's record and is withdrawn. Preparation is a pillar of the programme, run under its gates; providers of technology work at arm's length, and no offer of infrastructure is an allocation.
02Why capabilities must be prepared before they are tested
Why capabilities must be prepared before they are tested
A test of readiness is only as good as what is brought to it. If a model arrives with unqualified data, a software build with unknown defects or an environment without a stop-work authority, the exercise measures the preparation, not the readiness of the institutions taking part. Public practice in high-stakes fields has learned this the hard way. NASA's standard for models and simulations was developed in response to a 2004 NASA report on the Columbia Accident Investigation Board's findings, with the Board's own report also considered; it asks that the credibility of simulation results be assessed and clearly conveyed, especially for critical decisions (NASA-STD-7009B, Standard for Models and Simulations) 5.
Three other bodies of practice make the same point from different directions. NASA's technology readiness levels grade maturity on nine levels, from research just beginning at the first to a technology proven in a mission at the ninth, with a fully functional prototype at the sixth (Technology readiness levels) 6. The Secure Software Development Framework of the National Institute of Standards and Technology sets out a core set of high-level practices that reduce vulnerabilities in released software and address their root causes 7. And the Homeland Security Exercise and Evaluation Program gives a common approach to exercise program management, design and development, conduct, evaluation and improvement planning 8. Each says, in its own terms, that trust is earned before the decisive moment, not during it.
For a programme whose purpose is to help governments, operators and financial institutions test decisions before a crisis does, the stakes are the same. A capability that looks ready but is not can mislead the very institutions it is meant to help. The Foundry pillar exists to make preparation visible, gated and correctable.
03One year, one month, one week, one day
One year, one month, one week, one day
The programme runs on one annual cycle, with a short rule: prepared for a year, built in a month, tested in a week and stood down in a day, then reviewed and renewed 2. The year is the preparation. It holds national demand, research, institutional participation, monthly working-group delivery, quarterly evidence, and the qualification of technology and resources; it ends when an approved mission portfolio, qualified inputs and an achievable build plan are in place 2,1.
The month is the build. The Core is assembled, authorised resources are bound, software and data are integrated, security and interoperability are tested, teams are trained and the exercise is rehearsed; it ends with a Core Build Report, measured readiness, known defects and a go or no-go decision. The week is the test, in controlled exercises with controllers, evaluators, a scenario plan and stop-work authority. The day is the stand-down: new work stops, temporary access is revoked, temporary capacity is released and transferable evidence is sealed, a step the programme still records as proposed 1.
Fig. 01What the Foundry pillar does in each quarter
Figure 1 in words
Q1, State and Agenda: planning, gate G0, opens the cycle projects and takes a baseline of every National Portfolio. Q2, Evidence and Build: readiness preparation, gate G2, qualifies data sources and resource offers and builds the scenario models; controlled build, gate G3, highlighted, integrates software and data, signs builds and tests security and interoperability. Q3, Stress Test and Readiness: Action Week, gate G4, runs simulations and benchmarks and monitors the exercise picture; stand-down revokes temporary access and releases temporary capacity; closeout, gate G5, reconciles equipment and costs and verifies persistent services; after-action review updates the National Portfolio with measured movement. Q4, Annual Synthesis and Renewal: reporting, gate G6, supplies the permitted data bundles; correction re-runs affected analysis; docket and network review register capability gaps and publish measured capacity; renewal, gate G7, carries the Portfolio and open projects into the next cycle. A note gives the rule of the year and states that gate G1, missions admitted, precedes readiness preparation.
04Where preparation happens, quarter by quarter
Where preparation happens, quarter by quarter
In the first quarter the Foundry pillar opens the cycle projects and takes a baseline of every National Portfolio, under the annual mandate at gate G0. In the second it qualifies data sources and resource offers and builds the scenario models during readiness preparation (gate G2), then runs the one-month controlled build, which ends at gate G3 when the build is accepted for exercise. In the third quarter it runs simulations and benchmarks during Action Week (G4), releases temporary capacity at stand-down, reconciles equipment and verifies persistent services at closeout (G5), and updates the National Portfolio with measured movement after the action review. In the fourth it supplies the permitted data bundles behind each edition of Reports (G6), re-runs analysis when inputs are corrected, registers capability gaps for the next build and carries the Portfolio into renewal (G7) 1.
The gates are not the Foundry pillar's to grant. GRF stewards Nexus Universe and holds the mandate, the admission of missions and the authorisation of publication, in the manner of exercise direction and apart from controllers and evaluators 9,1. GCRI runs the technical office and the build. GRA runs the finance-readiness dialogues and reads the findings for finance, through the Universe finance-readiness track 1. Each actor holds a part of the year and hands it on.
05What the Foundry pillar sends and receives
What the Foundry pillar sends and receives
The Foundry pillar sends more recorded handoffs than any other pillar. From Nexus Universe it receives an admitted mission, which becomes a cycle project with a decision case (F01), and it returns the Core Build Report with go or no-go evidence (F02). From Nexus Standards it receives composed mission profiles and national adoption records (F08), and it returns validation and monitoring evidence for conformance review (F13). To Reports it sends sealed observations and indicator series (F03) and the movement of each National Portfolio (F05). To Risk Academy it sends each system's rooms as a learning-by-doing course (F14). And from Labs it receives tested prototypes to build (R4) 1.
The systems carry that work. Builds and verification run in NXS-FAC (blueprints, builds and signing), composition in NXS-STU (composition, dashboards and workflows), simulation and frontier evaluation in NXS-LAB (research, experiments and simulations), canonical data in NXS-GRX (canonical data, provenance and risk), compute in NXS-COR (compute, nodes and runtimes) and access in NXS-NSF (trust, authorization and assurance).
Fig. 02The Foundry pillar sends more work than any other
Figure 2 in words
The Foundry pillar sits at the centre with the label build, simulate and prepare. Universe, convene and test: F01 in, an admitted mission becomes a cycle project; F02 out, the Core Build Report and go or no-go evidence. Standards, codify and correct: F08 in, composed mission profiles and national adoption records; F13 out, validation and monitoring evidence for conformance review. Labs, explore and prototype: R4 in, tested prototypes are built. Reports, publish: F03 out, sealed observations and indicator series; F05 out, National Portfolio movement. Academy, teach in the open: F14 out, each system's rooms become a learning-by-doing course.
06From a configured capability to sealed evidence
From a configured capability to sealed evidence
A capability passes through states, and each state permits a different claim. The second-quarter edition labels new evidence and capability configured, not validated 1. The first gate a capability meets is the qualification of its data and resources at G2. The build is accepted for exercise at G3 only on the Core Build Report. It operates under control in Action Week only after G4 authorises it. And its run, decision and observation records are sealed at G5, with the stand-down recorded 1.
The public literature on simulation points the same way. Sargent discusses conceptual model validity, model verification, operational validity and data validity, and gives a way to document the results 10; NASA's standard asks that the credibility of simulation results be assessed and clearly conveyed, especially for critical decisions 5. The programme does not adopt either as its rule.
Fig. 03A capability earns its claims one gate at a time
Figure 3 in words
Six rising steps. 1, configured: a capability labelled configured, not validated. 2, gate G2, data and resources qualified: sources, rights and resource offers checked before use. 3, gate G3, build accepted for exercise, highlighted: the Core Build Report gives go or no-go evidence, known defects and measured readiness. 4, gate G4, controlled live operation: exercised in Action Week with controllers, evaluators and stop-work authority. 5, gate G5, evidence sealed, highlighted: run, decision and observation records sealed and stand-down recorded. 6, gate G6, publication authorised: reviewed results released, corrections stay open.
07The National Portfolio is a record of readiness
The National Portfolio is a record of readiness
Each country's National Portfolio is developed and tracked in the Foundry pillar. It has four views: risk, capability, projects and research, and readiness and handoffs. In the programme's words, readiness is fitness for a stated next step, not approval, bankability or certification 11. A Portfolio entry describes a country's own pipeline in its own terms. The recipient decides under its own authority 11.
Where a project's evidence matters to finance, GRA reads it for the questions lenders, insurers and public finance ask, and hands it to them through lawful handoffs. The decision stays with the competent authority, operator or financial institution, outside the programme.
08How preparation is evidenced
How preparation is evidenced
The table below sets the records the pillar works on against the gate where each matters most. Each is kept so that it can be read later without the people who made it. Every record carries an evidence label, observed, modelled, scenario or estimated, so that a measured value is never presented as a model output; and the programme's participation records hold the state of each participant separately from any record of performance.
| Record | Gate where it matters | What it is not |
|---|---|---|
| Projects and builds | G3, build accepted for exercise 1 | Not a validated result until exercised and sealed |
| Observations and canonical data | G2, data and resources qualified 1 | Not cleared for use until sources and rights are qualified |
| Simulation and benchmark runs | G4, controlled live operation 1 | Not a forecast or a performance claim |
| National Portfolio record | G7, renewal 1 | Not approval, bankability or certification 11 |
| Evidence seals | G5, evidence sealed and stand-down recorded 1 | Not a publication until G6 authorises one |
Fig. 04What public practice asks before a capability is trusted
Figure 4 in words
Four rows. NASA technology readiness levels: maturity on nine levels, from research beginning at TRL 1 through a fully functional prototype at TRL 6 to flight proven in a mission at TRL 9; related phase, readiness preparation at G2, where data sources and resource offers are qualified. NIST SP 800-218, Secure Software Development Framework 1.1 of 2022: a core set of high-level secure development practices that reduce vulnerabilities and address root causes; related phase, controlled build at G3, where builds are signed and tested for security and interoperability. Homeland Security Exercise and Evaluation Program: programme management, design and development, conduct, evaluation and improvement planning; related phase, Action Week at G4, with controllers, evaluators and stop-work authority. Sargent 2013: conceptual model validity, model verification, operational validity and data validity, and a way to document results; related phase, simulation, where a configured or simulated capability is not a validated result.
09Standards and public practice the pillar reads
Standards and public practice the pillar reads
The programme's own standards are proposed, not adopted, and each country decides whether and how to use them through its National Standards Council. For the Foundry pillar the relevant families are the standards for software and supply chains, for verification and monitoring and for scenarios, models and foresight, all listed with the Nexus Standards. The public references in Figure 4 are read against the phases they relate to: NASA's readiness levels 6, the NIST framework 7, the exercise programme guidance 8 and the literature on simulation validity 10; NASA's standard for models and simulations is read the same way 5. Naming them is not a claim of conformance.
10What institutions can do now
What institutions can do now
The programme is in formation, and its current service level is R0: information and enquiries 3. No build, compute allocation, exercise registration or payment is open; each opens only when its service team, terms and review capacity are in place. What is open is the question. A ministry, an operator, a university or a National Working Group candidate can write through the enquiry form and receive a reference and the next step. The programme status page explains each state, and claims and status explains what the programme may and may not say about any capability.
- Research teams: bring a method or a prototype to Labs and its testbeds; tested prototypes are what the Foundry pillar builds.
- Modellers: read the programme's approach to uncertainty and validation and digital twins, and the methods and technical series of the Reports platform.
- Learners: follow the Risk Academy programme and its course on model risk and validation.
11What is changing
What is changing
- Credibility stated with the result. NASA's 2024 revision of its models and simulations standard requires that the credibility of results be assessed and conveyed with them, especially for critical decisions 5.
- Secure builds as a precondition. Secure development practice is now framed as a shared vocabulary between buyers and suppliers of software 7.
- Exercises as evidence. HSEEP describes exercise evaluation as the functional link between an exercise and improvement planning 8.
- Stand-down as a recorded step. The programme's one-day stand-down, still proposed, would seal transferable evidence and release temporary capacity on the record 1.
12Three faces of the Foundry pillar
Three faces of the Foundry pillar
The Foundry pillar looks different from each institution. For GCRI it is where its science and technical platforms bring the methods, data and evidence the programme builds on. For GRF it is the work that enters the programme on the record when GRF admits missions and accepts the build for exercise at a gate; its programme governance, exercises and learning and results and records pages explain how. For GRA it is the work whose findings it reads for the finance and insurance chapter of the flagship report 1. All three follow the Nexus cycle from question to renewal, with the build and test stages described on each site, including the build stage at GRF and the build stage at GRA; the annual test is held in Nexus Universe, whose application is at universe.nexus. The programme and the Nexus cycle in the documentation are set out in full.
What this page does not claim: no build, compute allocation, exercise or evidence seal is open or recorded today; the programme is in formation at service level R0. A capability labelled configured is not a validated result, an infrastructure offer is not an allocation, and a National Portfolio entry is not approval, bankability or certification. Technology providers work at arm's length and do not direct programme decisions. Naming NASA, NIST, FEMA or any other body is not a claim of conformance, partnership or endorsement. GCRI does not regulate or certify, GRF does not regulate, finance or procure, and GRA does not lend, underwrite, rate or invest.
Questions
Questions and answers
Is the Foundry pillar a separate organization or company?
No. It is one of the six pillars of the Nexus programme, run by GCRI as part of the technical office. Technology providers work with the programme at arm's length and do not operate it or direct its decisions.
Can a provider bring its own tool to be tested in Nexus Universe?
Not as of right. An infrastructure or technology offer is not an allocation. Resources are qualified at gate G2 and a build is accepted for exercise only at G3, on a Core Build Report; today no build is open.
When is a capability sealed as evidence?
Its run, decision and observation records are sealed at gate G5, after exercise under control in Action Week, with the stand-down recorded. Publication is authorised separately, at gate G6.
Does a National Portfolio entry mean approval?
No. The National Portfolio describes a country's risks, capabilities, projects and readiness in its own terms. Readiness means fitness for a stated next step, not approval, bankability or certification, and the recipient decides under its own authority.
Who decides that a build is ready?
The gate decisions are held by GRF as steward of Nexus Universe, apart from controllers and evaluators. GCRI prepares the Core Build Report; the decision to act on any result belongs to the competent authority, outside the programme.
How can I take part today?
The programme offers information and enquiries only. Write through the enquiry form at therisk.global; you receive a reference and the next step. Builds, allocations and exercises open only when their team, terms and review capacity exist.
Terms
Glossary
- Foundry pillar
- The build pillar of the Nexus programme, where cycle software, data and environments are built, scenarios simulated, evidence sealed and National Portfolios developed.
- Core Build Report
- The report that closes the one-month controlled build, with measured readiness, known defects and the go or no-go evidence for gate G3.
- Gate
- A recorded programme decision about the cycle, G0 to G7, such as admitting missions or authorising publication; never an approval of a capability or an institution.
- Evidence seal
- The closing of run, decision and observation records at gate G5, so that they can be cited and corrected later without being altered.
- Design state
- A capability labelled configured, not validated, that has not yet been exercised and sealed.
- Technology readiness level
- NASA's nine-level scale of technology maturity, from research beginning to a technology proven in a mission.
Reuse and cite
Text CC BY 4.0. Cite the page with its date; data tables are linked under each figure.
Sources
References
11 sources, numbered in the order they are first cited
- Nexus Consortium documentation (docs.therisk.global) (2026-10-21). The programme year. docs.therisk.global. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Annual programme cycle. therisk.global. Accessed 2026-10-21.
- Nexus Consortium documentation (governance in operation) (2026-10-21). Status and service levels. docs.therisk.global. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (programmes) (2026-10). Nexus Universe: the technical office. therisk.global. Accessed 2026-10-21.
- National Aeronautics and Space Administration (Office of the Chief Engineer) (2024-03-05). NASA-STD-7009B, Standard for Models and Simulations. standards.nasa.gov. Accessed 2026-10-21.
- National Aeronautics and Space Administration (2026). Technology readiness levels. www.nasa.gov. Accessed 2026-10-21.
- National Institute of Standards and Technology (2022-02). Secure Software Development Framework (SSDF) version 1.1: recommendations for mitigating the risk of software vulnerabilities, SP 800-218. csrc.nist.gov. Accessed 2026-10-21.
- U.S. Federal Emergency Management Agency (2026-10). HSEEP resources: about HSEEP. preptoolkit.fema.gov. Accessed 2026-10-21.
- The Global Risks Forum (2026-10). Programme governance: GRF's role in Nexus Universe. globalriskforum.com. Accessed 2026-10-21.
- Sargent, Journal of Simulation 7(1), 12–24 (2013-02). Verification and validation of simulation models. link.springer.com. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (National Nexus) (2026-10). National Portfolio. therisk.global. 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 gate, a phase or a programme state changes. It replaces an earlier version of the same page, which described a separate preparation and acceleration layer outside the programme's pillars, sponsor and provider pathways into a stage of the annual cycle, and readiness gates not on the programme's record; those descriptions are withdrawn, and the pillar is now described from the programme's recorded model.
Published by the GCRI editorial desk under the 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). Foundry pillar: preparing capabilities before the cycle. The Global Centre for Risk and Innovation. https://therisk.global/nexus-foundry-preparing-capabilities-before-the-annual-technical-cycle/
@online{gcri2026nexusfoundrypreparing,
author = {{GCRI editorial desk}},
title = {{Foundry pillar: preparing capabilities before the cycle}},
publisher = {The Global Centre for Risk and Innovation},
year = {2026},
month = {6},
url = {https://therisk.global/nexus-foundry-preparing-capabilities-before-the-annual-technical-cycle/},
language = {en}
} TY - ELEC AU - GCRI editorial desk TI - Foundry pillar: preparing capabilities before the cycle PB - The Global Centre for Risk and Innovation PY - 2026 DA - 2026/06/08 UR - https://therisk.global/nexus-foundry-preparing-capabilities-before-the-annual-technical-cycle/ 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>The Foundry pillar: preparing capabilities before the annual cycle — GCRI editorial desk, The Global Centre for Risk and Innovation. First published 8 June 2026 at <a href="https://therisk.global/nexus-foundry-preparing-capabilities-before-the-annual-technical-cycle/">https://therisk.global/nexus-foundry-preparing-capabilities-before-the-annual-technical-cycle/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>