Why these exist. The Nexus Ecosystem moves work from evidence → standards → policy → capital → delivery. Each sister entity has a clear lane, tight hand-offs, and shared guardrails (neutrality, clause licensing, membership ≠ governance, no tool-ownership by GRF).
GRF — The Global Risks Forum (neutral convening & decision log)
- Core mandate: Run the monthly public discussions for all tracks (Research, Innovation, Policy, Capital, New Media), keep debate neutral, and convert discussion into short, usable outputs.
- Produces: AAR (≤3 pp), Clause Pack Delta, Policy Option Note, Investment Note, Comms Note—each labeled Public/Internal/Restricted.
- Inputs & interfaces: Intake items from members/partners; coordinates with Chairs/Leads; hands off to GCRI/TMDs, NSF, RSBs/NWGs, GRA, and New Media teams; tracks acknowledgments and T+14 follow-through.
- Out-of-scope: No tool ownership, no fundraising or deal-making, no policymaking authority.
- “Done” looks like: Decisions captured as verb + object + date, owners named, recipients acknowledge within ≤5 business days.
GCRI — The Global Centre for Risk & Innovation (systems integrator & technical engine)
- Core mandate: Turn research into working methods, data, and simulations; operate secure pipelines and compute; coordinate TMDs (Technical Management Divisions).
- Produces: Validated methods updates, test plans, simulation runs, datasets (with provenance), and reference dashboards.
- Inputs & interfaces: Methods tasks and data specs from GRF Research/Innovation; collaborates with NE Labs for advanced tooling; returns results back to GRF/recipients.
- Out-of-scope: Setting public policy, structuring capital, running public convenings.
- “Done” looks like: Task IDs opened, data access confirmed, test window scheduled, results archived with sources and uncertainty bands.
NSF — Nexus Standards Foundation (standards & registry)
- Core mandate: Convert Clause Pack deltas into registry-ready definitions, triggers, covenants, and oversight/remedy text; resolve collisions across jurisdictions/standards.
- Produces: Published clause IDs/versions, change logs, and guidance notes.
- Inputs & interfaces: Redlines from GRF; legal/technical consultation with Policy/Standards Leads; feedback to GRA (for covenant alignment) and to RSBs/NWGs (for adoption).
- Out-of-scope: Convening public sessions, financing structures, operational pilots.
- “Done” looks like: Registry ticket issued, editor of record assigned, publication ID linked back into artifacts and calendars.
GRA — The Global Risks Alliance (capital corridors & co-structuring
- Core mandate: Turn investment signals into corridor pipelines with clause-linked triggers, diligence rooms, and co-structured transactions with sovereigns, DFIs, insurers, and private capital.
- Produces: Corridor stage/next-gate, diligence requests, monitoring plans tied to NSF clauses; post-close feedback on trigger performance.
- Inputs & interfaces: Investment Notes from GRF; sanctions/PEP and ESG screens; policy preconditions from the Policy track; data hooks from GCRI/NE Labs.
- Out-of-scope: Negotiation inside GRF sessions; issuing standards; setting public policy.
- “Done” looks like: Corridor lead named, diligence opened, compliance checks started, measurable triggers accepted.
NE Labs — Research & Engineering Studio (public-benefit reference builds)
- Core mandate: Build and harden reference implementations—simulation engines, ClauseCommons tooling, digital twins, test harnesses—aligned to NSF standards.
- Produces: Open/reference software, SDKs, test datasets, and engineering notes suitable for technology transfer.
- Inputs & interfaces: Requirements from GCRI/TMDs and GRF artifacts; coordinates with NSF for standards compliance; supports RSB/NWG pilots with reference tech.
- Out-of-scope: Acting as a commercial vendor owning end-customer deployments; policy or capital decisions.
- “Done” looks like: Versioned code/docs released, reproducible tests, standard conformance proven, hand-off package ready for GCRI/recipients.
Where deployment happens — RSBs/NWGs (regional & national partners)
- Role: Localize policy routes, run pilots, and adapt standards to context across Regions and National Working Groups.
- Receives: Policy Option Notes, clause IDs, and comms/localization kits; returns pilot decisions, timelines, and feedback to GRF/NSF/GRA.
- “Done” looks like: Focal named, pilot site/agency and first milestone set, localization plan active.
How they interlock (fast flow)
- GRF tests options and issues artifacts.
- NSF publishes the standard (clause IDs).
- RSBs/NWGs localize and pilot.
- GRA structures capital with clause-verified triggers.
- GCRI (with NE Labs) runs methods, data, and reference tech to make it real.
- Results and IDs loop back to GRF for the next monthly cycle.
Guardrails (bind all entities)
- Neutrality & licensing: All outputs are clause-licensed for public benefit.
- Membership ≠ governance: Leadership is honorary, non-fiduciary, code-of-conduct bound.
- No tool ownership by GRF: Implementation and commercialization occur outside GRF via the appropriate Nexus entity.
One concrete example (end-to-end in weeks, not years)
- A coastal flood risk spike enters GRF Research; uncertainties and EVPI are logged.
- GCRI runs updated simulations; NE Labs ships a reference early-warning module.
- NSF publishes a trigger clause for river-gauge thresholds and an oversight/remedy text.
- Policy track selects a fast administrative route; RSB/NWG names a pilot city and first milestone.
- Capital track defines covenants; GRA opens diligence and sets the next gate.
- Comms are localized through New Media partners; GRF tracks T+14 progress and closes the loop.
Views: 20