The Global Centre for Risk and Innovation (GCRI)
NEXQ is the software and agent capability fabric: the catalogue of tools, models and agents a project may use, each with its declared purpose, permissions and evaluation record.
Foundry · NEXQ · Run R-6190
same inputs, versioned
| R-2421 | High-performance,… | v2.8 | 0.71 | Running |
| R-8673 | Data engineering,… | v5.1 | 0.69 | Failed test |
| R-8622 | Geospatial information… | v8.1 | 0.81 | Failed test |
| R-2368 | Artificial… | v7.4 | 0.87 | Passed |
Nexus Foundry · Build workspaceBuild workspace, in outline: domain structure with placeholder names and illustrative values, not a record.
NEXQ Ingestion and Nervous System is the Nexus Foundry system for data ingestion, lineage, schema validation and event routing. It serves 6 platforms, among them Nexus Labs as well as Artificial Intelligence and Autonomous Systems, and its stated limit is that ingested data keeps its source rights and limitations. Access is through an authorized project with an accountable owner, data terms and a review plan.
Urban demand centres and the hubs that anchor digital and data infrastructure, shown for the Strait of Malacca as an example geography for this subject.
Analytical work increasingly uses software agents that call tools and data. Without a catalogue that declares what each capability does, what it may access and how it was evaluated, an agent's reach can exceed what anyone authorized.
| Reference | Relevance |
|---|---|
| NIST AI RMF | Govern, map, measure and manage AI capabilities |
| ISO/IEC 42001 | AI management system controls |
| Model Context Protocol and similar open protocols | Declared tool interfaces for agents |
Access requires an authorized project with an accountable owner, data terms and a review plan. Enquiries go to contact@therisk.global.
Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.
| Term | Definition |
|---|---|
| Data lineage | The traceable path of data from its origin through each transformation to its current form. |
| Schema validation | Checking each incoming record against a formal definition of required fields, types and values. |
| Data pipeline | A sequence of automated steps that ingests, validates, transforms and publishes data. |
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
The current service level is R0: information and enquiries. 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.