GCRI · Food Nexus
Yakha kwi-Foundry
The Foundry systems that serve Food Nexus, what an authorised project can do with them, and how access is requested. Foundry's public home is therisk.global/nexus-foundry.
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
Unyaka wenkquboZonke izigaba
Indlela
Around Foundry
The pillars Foundry hands work to and receives it from.
L · F · U · S · R · A
- Iintsika
- 6 kwezi-6
- Ukudluliselwa komsebenzi
- 18 kwezi-18
- Imijikelo
- 17 kuvaliwe
Ukudluliselwa komsebenzi okusebenzayo
- 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 → Iingxelo · Iziphumo zasemva kwesenzo nezeemeko-mfanekiso zezahluko 10 no-13Uphononongo emva kwesenzo
nezinye ezili-14
- IilabhoratriApho imibuzo iba yimifuniselo neeprototypes: iindlela ezintsha, idatha nezixhobo zivavanywa ekuhleni, nemida yazo irekhodiwe, phambi kokuba i-Foundry izakhe, phantsi kwe-Nexus Consortium.Iilabhoratri
- FoundryWhere methods, data and models become reproducible builds, each run with its inputs, version and limits on record.Food Nexus in FoundryFoundry
- UniverseWhere a build is tested under controlled conditions with independent evaluators, so a method's skill is measured, not assumed.Food Nexus in Universeuniverse.nexus
- Nexus StandardsWhere methods, identifiers and data schemas are codified in the open and corrected when a test finds a fault.Water and Food Systems in Standardsnexustandards.com
- ReportsWhere findings are published with their method, uncertainty and evidence class, and corrected as new versions.Food Nexus in ReportsReports
- Risk AcademyWhere methods and systems are taught on real data and real places, by working the case, on Risk Academy.Faculty of Earth and Environmental Sciences in Academyrisksacademy.com
Foundry in every area of the work
| Indawo | Foundry |
|---|---|
| Ubunkokeli | 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. |
| Inkqubo yokusebenza | 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. |
| Ulawulo | 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. |
| Ukuthatha inxaxheba | 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. |
| Kwelizwe | Each country's National Portfolio is developed and tracked. |
| Kwingingqi | 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
| Intsika | GCRI | GRF | GRA |
|---|---|---|---|
| Foundry | Amaqonga ayo enzululwazi nobugcisa azisa iindlela, idatha nobungqina i-Foundry ezakhela phezu kwazo. | Yamkela imisebenzi kwaye yamkele ukwakha ukuze kuziqheliselwe kwisango elirekhodiweyo, ukuze umsebenzi we-Foundry ungene kwinkqubo ngokurekhodiweyo. | Izisa imibuzo yokulungela kwezemali, ukuze ukwakha kuvelise ubungqina obunokufundwa ngamaziko ezemali. |
The Foundry systems that food system work draws on.
- NXS-EOP (earth observation and digital twins)NXS-EOPCrop condition, cropland and flood or drought impact on fields from satellites
- NXS-GRXNXS-GRXFood security, price and production indicators alongside other country indicators
- NXS-DSS (decision cases and deliberation)NXS-DSSReserve and trade policy options compared across shock scenarios
- NXS-AAPNXS-AAPTriggers and readiness for anticipatory action before a food crisis
The workspace for Build in Foundry.
Build workspace
Food · Build in Foundry · Run R-3535 · Example interface, not a record
Runs
same inputs, versioned
| R-9537 | Agricultural, soil | v7.7 | 0.74 | Running |
| R-7212 | Ecology and biodiversity | v6.1 | 0.51 | Ukutyibilika |
| R-9776 | Ukuqwalaselwa koMhlaba | v5.6 | 0.43 | Failed test |
| R-1874 | Spatial statistics | v5.2 | 0.61 | Passed |
Model card
- Indlela yokusebenza
- Inzululwazi yezolimo, yomhlaba neyokutya
- Inputs
- Market price survey, Rainfall estimates, satellite and gauge
- Ukuqinisekiswa
- held-out period, skill reported
- Ileyibhile
- KUMODELWE
Run log
- 00:00:30InfoIngest market price survey
- 00:02:12InfoSchema and licence checks passed
- 00:07:40WarnGap filled by interpolation, flagged
- 00:15:03DoneCalibration complete
- 00:29:55GateIndependent test queued
Food Nexus · Build workspace. Build workspace: example names and illustrative values, not a record.
Foundry systems for this field.
| Inkqubo | What it does here | Indima | Read more |
|---|---|---|---|
| NXS-EOPEarth observation and digital twins | Brings Earth observation scenes and digital twins into the field. | This field | DocumentationIntegrated, not bound |
| NXS-GRXCanonical data, provenance and risk | Holds the canonical data, provenance and risk records the field cites. Index data service: unavailable. No public endpoint is published for this site yet. | This field | DocumentationIntegrated, not bound |
| NXS-DSSDecision cases and deliberation | Turns evidence into decision cases with stated uncertainty. | This field | DocumentationIntegrated, not bound |
| NXS-AAPAnticipatory action and triggers | Anticipatory action and triggers. | This field | DocumentationIntegrated, not bound |
| NXS-EWSMulti-hazard monitoring and warning | Carries monitoring and warning layers for the hazards of the field. | This site | DocumentationIntegrated, not bound |
| NXS-LABResearch, experiments and simulations | Runs research, experiments and simulations before anything is built. | This site | DocumentationIntegrated, not bound |
| NXS-NSTCivilian common operating picture | Shows the common operating picture as a map on the page. | This site | DocumentationIntegrated, not bound |
| NXS-PORPublic, client and partner delivery | Delivers released views and maps into the page. | This site | DocumentationIntegrated, not bound |
| NXS-HUBKnowledge, records and learning | Searches the knowledge and records of the field. | This site | DocumentationIntegrated, not bound |
The release of the Nexus systems is on hold. Each code links its definition in the Nexus Risk Standards.
Indlela inkqubo eqhuba ngayo.
Process explorer · Process
Build in Foundry: Build, sign and accept
10 steps·4 stages·2 gates
Inkqubo yokusebenza
Build in Foundry: Build, sign and accept
An admitted mission becomes a cycle project; the build is pinned, verified and signed, and GRF records acceptance for exercise, not permission to deploy.
01 Request and sources
- 01Admitted mission becomes a cycle projectRecord · Universe to FoundryAn admitted mission becomes a cycle project with a decision case.
- 02Qualify data sources and resourcesStep · GCRIGCRI qualifies data sources and resource offers and builds the scenario models. An offer is not an allocation.
02 Build and verify
- 03Source snapshotRecord · NXS-FAC (blueprints, builds and signing)The snapshot pins the commit, dependencies and generator versions.
- 04Build contractRecord · NXS-FAC (blueprints, builds and signing)The build contract declares the artefact kind, environment and reproducibility envelope.
- 05Integrate and buildModel · GCRIGCRI integrates software and data, signs builds, and tests security and interoperability.
- 06Verification suiteGate · NXS-FAC (blueprints, builds and signing)Required and advisory checks stay separate. Reproducibility needs pinned inputs, declared nondeterminism and independent rebuilds.
03 Sign and admit
- 07Sign the exact artefactStep · NXS-FAC (blueprints, builds and signing)NXS-FAC builds, attests and requests a signature via a scoped signer identity. It holds no key material.
- 08Package admissionStep · NXS-NXQ (software, models and capability lifecycle)NXS-NXQ receives the signed package and keeps admission evidence that binds the task, data class, evaluation suite and expiration.
04 Accept
- 09Core Build ReportRecord · GCRIThe Core Build Report is the go or no-go record. Universe assembles the Core and holds the decision for the exercise.
- 10G3 · Build accepted for exerciseGate · The Global Risks ForumGRF records whether the build is accepted for exercise. A signed build or release candidate is not permission to deploy to production.
The programme year · NXS-FAC · UniverseDesigned 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 record order follows the Builds and Releases room lists of NXS-FAC.
How a project gets access.
- 01
Enquiry
Describe the project and its owner to contact@therisk.global.
- 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.
Apho izalathiso zeli phepha zikhokelela khona.
Amaqumrhu namaxwebhu eli phepha elifundwa ngokuthelekiswa nawo. Imeko neenguqulelo ziyatshintsha; ikhonkco ngalinye liya kwiqumrhu elikhuphayo.
Imibuzo neempendulo.
Is Foundry access free?
Bring a method, a dataset or a question.
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.
Amaxwebhu asemthethweni.
Iimephu, idatha nemizobo ekule sayithi iboniswa njengemeko nolwazi jikelele. Ayingomacebiso, uqikelelo okanye izilumkiso; imida yolwazi ichazwe kwiZilumkiso neZaziso zeDatha.