GCRI · Nexus Ecosystem
Foundry technical gateway
Foundry is the persistent work environment of the Nexus Consortium. Projects, data, models, maps, analysis and evidence live there all year, across twenty technical systems of ten rooms each. The Global Centre for Risk and Innovation (GCRI) documents Foundry in public and, through GCRI Canada, contracts in support of the national and regional consortiums. Systems, project entry and authorisation boundaries are below. Part of Nexus ecosystem.
01Contents
Foundry technical gateway in four parts.
02Twenty systems
What each system contributes, and the line it does not cross.
- NXS-CMD (integrated posture and executive synthesis)NXS-CMDPortfolio and institutional project coordinationNXS-CMDNo substitute for external decision authority
- NXS-NSTNXS-NSTCommon operating picture and field coordinationNXS-NSTCivilian scope; maps and operating-picture authority only
- NXS-DSS (decision cases and deliberation)NXS-DSSScenarios, options, uncertainty and decision analysisNXS-DSSAnalysis is not the decision
- NXS-COR (compute, nodes and runtimes)NXS-CORInfrastructure enrolment, lifecycle, placement and recoveryNXS-CORApproved assets and workload authority only
- NXS-NXQ (software, models and capability lifecycle)NXS-NXQVersioned capabilities, admission and qualificationNXS-NXQDoes not own the agent population fabric
- NXS-GRX (canonical data, provenance and risk)NXS-GRXData, ontology, evidence, fusion, lineage and risk productsNXS-GRXSource rights and limitations persist
- NXS-EOP (earth observation and digital twins)NXS-EOPEarth-observation search, processing and change evidenceNXS-EOPNo implied authority to order paid acquisition
- NXS-EWS (multi-hazard monitoring and warning)NXS-EWSForecast verification and warning supportNXS-EWSIssuing warnings stays with authorised parties
- NXS-AAP (anticipatory action and triggers)NXS-AAPTrigger evaluation and preparednessNXS-AAPNo automatic fund release or dispatch
- NXS-NETNXS-NETConnectivity, network intent, telemetry and continuityNXS-NETNo control of unconsenting third-party networks
- NXS-OPSNXS-OPSInstruments, measurement and calibration evidenceNXS-OPSPhysical operation needs authorised scope
- NXS-SIG (signal, spectrum, timing and PNT)NXS-SIGAuthorised signal and positioning integrity observationNXS-SIGNo unauthorised collection
- NXS-NSF (trust, authorisation and assurance)NXS-NSFPolicy, purpose, rights, mandate and assurance decisionsNXS-NSFInterface intent cannot create authority
- NXS-HUBNXS-HUBKnowledge, learning, service and continuityNXS-HUBNo fabricated credentials or employment
- NXS-STU (composition, dashboards and workflows)NXS-STUAgent populations and composed experiencesNXS-STUOwns the shared agentic fabric
- NXS-FAC (blueprints, builds and signing)NXS-FACGoverned build, verification, signing and releaseNXS-FACRelease is not deployment authorisation
- NXS-APPNXS-APPApplication installation and runtime lifecycleNXS-APPNo new infrastructure authority
- NXS-RLS (participants, agreements and handoffs)NXS-RLSProtocols, obligations, handoffs and receiptsNXS-RLSA receipt is not settlement or external acceptance
- NXS-POR (public, client and partner delivery)NXS-PORPublic and audience-specific deliveryNXS-PORPublication never overrides source permission
- NXS-LAB (research, experiments and simulations)NXS-LABReproducible research, testbeds and benchmarksNXS-LABExperiment results are not certification
Full system pages are on Foundry technical systems and the overview on The twenty Foundry systems.
03Project entry
How work enters Foundry.
- 01
Enquiry
A national programme, institution or mission team describes its question and receives a reference.
- 02
Scope and rights
The counterpart, the information scope, the data rights and the authority for the next step are agreed in writing.
- 03
Workspace
A project workspace is opened for authorised users only, when access opens at the relevant service level.
- 04
Build and review
Models and analysis are built in governed systems, and findings are reviewed before any publication.
04Boundaries
Authorisation stays with the people who hold it.
- Participation gives Nexus no control of operational technology, and exercises carry no live actuation or warning authority.
- A blueprint is not an installed environment, and requested capacity is not allocated capacity.
- National programmes keep their agenda, data and decision rights under a rights schedule.
- Foundry is hosted on cloud infrastructure in the United States, run by an external provider at arm’s length. Personal information may be processed there under the privacy notice.
05Status
What is open today.
Information and enquiries are open today. Workspace access and computing allocations open only when their team, terms and review capacity are in place. Technical documentation is on Foundry. The Global Risks Forum (GRF) describes the annual programme work Foundry supports on Universe at GRF.
06Questions
Questions and answers.
Who operates Foundry?
National and regional Nexus Consortiums operate it through their host and lead organisations, within the programme led by the three pillar institutions. GCRI Canada supports them as global contracting party and runs the global-to-local deployment.
Who owns the Foundry code?
The technology developer and infrastructure operator is the intended licensor of the code and intellectual property to GCRI Canada for public-good, not-for-profit operation. It does not operate the service or direct programme decisions.
Can I get a workspace now?
Not yet. The current service level is information and enquiries; an enquiry receives a reference and the acknowledgement names the next step.
The Global Centre for Risk and Innovation
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.
Legal
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.