GRA · Fintech Nexus
Spatial financeWhere capital meets hazard, exposure and transition
Build in Foundry
Fintech Nexus analysis would use Foundry systems for trust and policy (NSF), application lifecycle (Apps) and software and model capability (NXS-NXQ), because the questions concern dependencies, controls and models. Every workspace needs an authorised project with an accountable owner, data terms and a review plan, and no customer data.
Foundry among the six pillars.
Where things are built, simulated and prepared: every output of the Global Centre for Risk and Innovation (GCRI), the Global Risks Forum (GRF) and the Global Risks Alliance (GRA), under the Nexus Consortium. It is led by the Nexus Consortium; its home is therisk.global/nexus-foundry.
handoff in playrecorded handoffno direct handoff
Programme yearAll phases
Route
Around Foundry
The pillars Foundry hands work to and receives it from.
L · F · U · S · R · A
- Pillars
- 6 of 6
- Handoffs
- 18 of 18
- Loops
- 17 closed
Handoffs in play
- F01Universe → Foundry · Admitted mission becomes a cycle project with a decision caseReadiness preparation
- F02Foundry → Universe · Core Build Report and go or no-go evidenceControlled build
- F03Foundry → Reports · Sealed observations and indicator series behind a profileCloseout
- F04Universe → Reports · After-action and scenario findings for chapters 10 and 13After-action review
and 14 more
- LabsWhere questions become experiments and prototypes: new methods, data and tools are tried in the open, with their limits on record, before the Foundry builds them, under the Nexus Consortium.Labs
- FoundryWhere exposure and scenario evidence is built so supervisors, insurers and investors can read it.Fintech Nexus in FoundryFoundry
- UniverseWhere scenarios are tested in controlled exercises, and finance-readiness dialogues read what they mean for capital and cover.Fintech Nexus in Universeuniverse.nexus
- Nexus StandardsWhere disclosure and data rules are codified so risk evidence is comparable for finance and insurance.Finance, Insurance and the Economy in Standardsnexustandards.com
- ReportsWhere sector analysis and the finance and insurance readiness series are published, with exposure and limits stated.Fintech Nexus in ReportsReports
- Risk AcademyWhere finance, insurance and public-finance professionals learn to read risk evidence, on Risk Academy.Faculty of Finance and Economics in Academyrisksacademy.com
Foundry in every area of the work
| Area | Foundry |
|---|---|
| Leadership | Each build is led by an authorised project with an accountable owner; leadership is technical and never extends to the decision the build informs. |
| Strategy | The build plan follows the National Portfolio and the missions admitted for the year. |
| Cadence | Works all year; the controlled build runs for one month in Q2, and measured capacity results are reviewed in Q4. |
| Ownership | Owns projects and builds, observations and canonical data, simulation and benchmark runs, the National Portfolio record and evidence seals. |
| Process | Work moves through governed rooms on twenty systems, and every run leaves a record with its limits. |
| Development | Develops the cycle's software, data and environments, and develops each country's National Portfolio. |
| Simulations | Runs scenarios, experiments and benchmarks with published method and conditions; a simulated capability is not a validated result. |
| Reporting | Supplies the permitted data bundles and sealed observations behind every edition. |
| Governance | Shared infrastructure made available to the Consortium for public-good purposes; it holds no vote in the governance of the standards. |
| Data and evidence | Canonical observations and provenance are held in The Global Risks Index (NXS-GRX), and every value carries its source and licence. |
| Finance and resourcing | Compute and data allocations open per project when their terms and review capacity exist; temporary capacity is released at stand-down. |
| Risk and assurance | Builds are signed and tested for security and interoperability, and accepted for exercise only at gate G3. |
| Participation | Stakeholders and service providers may establish their presence for non-profit and consortium objectives under the Terms. |
| Communication | Public pages describe each system's purpose and design, and state what it does only as far as its record shows. |
| Local | Observations and models keep their place: every value carries the location and boundary it was drawn on. |
| National | Each country's National Portfolio is developed and tracked. |
| Regional | Shared systems and cross-border dependencies are modelled across the countries of a region. |
| Planetary | Global data and Earth observation are held with provenance, so planetary pressures can be read alongside national ones. |
What each institution brings
| Pillar | GCRI | GRF | GRA |
|---|---|---|---|
| Foundry | Its science and technical platforms bring the methods, data and evidence that the Foundry builds on. | Admits missions and accepts the build for exercise at a recorded gate, so Foundry work enters the programme on the record. | Brings finance-readiness questions, so builds produce evidence that financial institutions can read. |
Foundry systems in fintech work.
The workspace for Build in Foundry.
Build workspace
Fintech · Build in Foundry · Run R-9046 · Example interface, not a record
Runs
same inputs, versioned
| R-7388 | Payment and financial | v5.7 | 0.68 | Running |
| R-4672 | Distributed ledgers | v8.7 | 0.57 | Failed test |
| R-9355 | Artificial intelligence | v8.4 | 0.58 | Drift |
| R-0221 | Cybersecurity | v3.5 | 0.83 | Drift |
Model card
- Method
- Payment and financial market technology
- Inputs
- Transaction logs, API telemetry
- Validation
- held-out period, skill reported
- Label
- MODELLED
Run log
- 00:00:46InfoIngest transaction logs
- 00:02:12InfoSchema and licence checks passed
- 00:06:40WarnGap filled by interpolation, flagged
- 00:13:03DoneCalibration complete
- 00:28:55GateIndependent test queued
Fintech Nexus · Build workspace. Build workspace: example names and illustrative values, not a record.
How the process runs.
Process explorer · Process
Build in Foundry: Layers to published map
7 steps·4 stages·1 gate
Process
Build in Foundry: Layers to published map
Layers enter with their rights, are aligned, analysed and checked for uncertainty, then released after public-safe review; a map is a governed spatial claim.
01 Data
- 01Source layers with their rightsDataset · NXS-GRX (canonical data, provenance and risk)Spatial views of NXS-GRX products sit under the boundary licence gate. Rights classification sets how a layer may be used.
02 Harmonise
- 02Coordinate reference and boundary versionRecord · NXS-EOP (earth observation and digital twins)The area of interest preserves its coordinate reference system, polygon validity and observation support. Boundary versions are kept.
- 03Harmonise units, variables and timeStepUnit metadata, conversion records and transformation logs are required. Alignment is an evidence event, not hidden preprocessing.
03 Analyse and check
- 04Analyse with a recorded processing recipeModel · GIS teamA processing recipe records parameters, calibration, inputs and output lineage. The analysis methods are named in each product's own record.
- 05Spatial uncertainty checkGateSpatial uncertainty is recorded and affects downstream use. A high-uncertainty polygon may suit internal review, not public-safe release.
04 Publish
- 06Spatial metadata bundleRecordThe bundle records boundary type, jurisdiction, geometry version, projection, resolution, source, time window, uncertainty and access class.
- 07Public-safe release of the mapDecisionThe output record names the redactions, uncertainty and public-safe reviewer. A map is a governed spatial claim, never merely a picture.
Spatio-temporal intelligence · Data protocols: semantic, jurisdictional and temporal intelligence · NXS-EOPDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The pages cited are design doctrine.
Foundry systems for this field.
| System | What it does here | Role | Read more |
|---|---|---|---|
| NXS-NSFTrust, authorisation and assurance | Keeps the authorisation and assurance trail of a readiness file. | This field | DocumentationIntegrated, not bound |
| NXS-APPApplication catalogue and lifecycle | Application catalogue and lifecycle. | This field | DocumentationNot bound |
| NXS-NXQSoftware, models and capability lifecycle | Software, models and capability lifecycle. | This field | DocumentationIntegrated, not bound |
| NXS-GRXCanonical data, provenance and risk | Supplies risk products by place for an exposure reading. Index data service: unavailable. No public endpoint is published for this site yet. | This site | DocumentationIntegrated, not bound |
| NXS-AAPAnticipatory action and triggers | Links triggers to pre-arranged finance and its records. | This site | DocumentationIntegrated, not bound |
| NXS-DSSDecision cases and deliberation | Sets out options and their trade-offs for a financial decision. | This site | DocumentationIntegrated, not bound |
| NXS-RLSParticipants, agreements and handoffs | Records the agreements and handoffs behind a readiness file. | This site | DocumentationIntegrated, not bound |
| NXS-EOPEarth observation and digital twins | Reads exposure from observation for spatial finance. | This site | DocumentationIntegrated, not bound |
The release of the Nexus systems is on hold. Each code links its definition in the Nexus Risk Standards.
How a project gets access.
- 01
Enquiry
Describe the project and its owner to Contact.
- 02
Authorisation
Access requires an authorised project with an accountable owner, data terms and a review plan.
- 03
Allocation
Compute and data allocations open when their terms and review capacity exist.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Where this page's references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
Questions and answers.
Is Foundry access free?
Bring an exposure or capital question to the Alliance.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.