For the complete documentation index, see llms.txt. This page is also available as Markdown.

Glossary

Appendix A. Glossary of Terms, Acronyms & NX Components

This glossary provides concise, normative definitions of key concepts used throughout the Nexus Ecosystem and Nexus Risk Management (NRM) technical architecture. It is intended as a reference for architects, engineers, regulators, academics, and practitioners. Where relevant, entries indicate relationships to other components in the stack.


A.1 Core Concepts & Methods

AEP — Assurance & Evidence Pack A structured, versioned bundle of evidence (data, models, assumptions, diagnostics, uncertainty analysis, provenance, and co-authorship) produced under NRM. Each AEP is assigned an Evidence Quality Level (EQL1–EQL5) and is explicitly tied to one or more decision contexts (e.g., early warning, capital triggers, supervisory review).

ERM — Enterprise Risk Management The prevailing, firm-centric risk management paradigm focused on identifying, measuring, and managing risks to an individual organisation’s objectives and balance sheet. In the Nexus design, ERM is treated as the “inside-the-firm” layer that interfaces with NRM for systemic and planetary risk.

NRM — Nexus Risk Management A next-generation, systemic and multi-level risk management discipline that aggregates and integrates existing regimes (ERM, DRR, DRF, prudential supervision, climate and adaptation frameworks) on top of the Nexus Rail. NRM explicitly treats human–machine–nature intelligence as a first-class design constraint and is designed for systemic, cascading, and planetary risks.

NRM Profile A structured specification of how NRM is applied to a specific risk domain and decision context (e.g., NRM–Climate–Sovereign–Drought–Food Security). Profiles bind together ontologies, data sources, models, AEP requirements, CL/EQL targets, governance rules, and capital/decision linkages.

NXSECO — Nexus Ecosystem The overall socio-technical system comprising institutions (GCRI, GRF, GRA, RNCs, NCCs, communities), standards (NXSS), runtime (NXSOS), technical components (NXSTUDIO, NXOBS, etc.), and practices (NRM), operating as a global digital public good for risk.

Nexus Rail (colloquial) Shorthand for the combination of:

  • the Nexus technical stack (NXSS, NXSOS, NXSTUDIO, NXOBS, etc.) and

  • the institutional and governance arrangements (GCRI, GRF, GRA, RNCs, NCCs, communities) that together turn signals → evidence → decisions → money-in-motion & action in a consistent, auditable way.

UNOSINT — Universal Nexus Open Source Intelligence The Nexus-specific, open, and extensible OSINT architecture that fuses multimodal data (EO, sensor streams, cyber telemetry, financial indicators, social signals, etc.) into the Nexus Observatory (NXOBS) and AEPs, under SDZ, lawful-basis, and safety constraints.


A.2 Institutional Actors & Governance

GCRI — Global Centre for Risk & Innovation The technical and scientific authority for NRM and the Nexus Ecosystem. GCRI stewards the core risk ontologies (GRIx), UNOSINT and observatory methods, scoring engines, simulations, and NRM curricula (NXAcademy). It coordinates R&D and methods across Nexus Competence Cells (NCCs).

GRF — Global Risks Forum The standards, assurance, and consortia governance authority for Nexus. GRF maintains the Nexus Standards Stack (NXSS), defines Conformance Levels (CL) and Evidence Quality Levels (EQL), oversees GRF-IP profiles, and governs semantic, ethical, and consortia processes (including rail-level DAOs and cross-rail NXHIVE rules).

GRA — Global Risks Alliance The capital, industry, and facility orchestration authority. GRA designs and coordinates NRM-linked products and facilities (contingency windows, parametric covers, resilience bonds, credit enhancements) ensuring they are anchored in NRM evidence (AEPs, Profiles) and GRF standards.

RNC — Regional Nexus Consortium A regional multi-actor consortium responsible for operating Nexus Rails within a geographic region (e.g., APAC, East Africa, MENA). RNCs host regional observatories, coordinate local NCCs, manage rail governance (Rail DAO/NVM), and liaise with governments, regulators, and industry.

NCC — Nexus Competence Cell A university- or institution-hosted node that acts as a distributed technical/scientific cell of GCRI. NCCs co-develop ontologies, models, AEPs, scenarios, and curricula, and often operate local observatory functions or specialised domain packs.

Rail DAO A rail-level decentralised governance entity, implemented via the nxproto.dao-nvm-engine, comprising representatives from government, regulators, financial institutions, infrastructure operators, academia/NCCs, and communities. It approves high-impact changes to rail configuration, Profiles, and facilities under NVM quorum rules.

NVM — Nexus Validation Machine The formal quorum and validation mechanism for high-stakes governance decisions (e.g., adoption of Profiles for capital facilities, changes to CL/EQL minima). Encodes who must sign and in what combinations (e.g., “3-of-6” including government, finance, infrastructure, and community/Indigenous keys).


A.3 Platform & Architectural Components (NX* Stack)

NXSS — Nexus Standards Stack The normative and semantic core of the Nexus Ecosystem: ontologies (GRIx), SDZ classes, CL/EQL definitions, DSLs (Policy, Playbook, Agent, rail.yaml, pack.yaml), safety and crypto baselines (AI safety tiers, BioSafe, PQGuard), lawful-basis matrices, test suites, and contribution/licensing models.

NXSOS — Nexus Operating System The governance, trust, connectivity, and abstraction runtime that runs on top of ledgers, clouds, and heterogeneous infrastructure. It includes the Governance & Trust Plane, Connectivity & Real-Time Plane, and Platform & Hardware Abstraction Plane (NXHAL, NXPAL, NXMirror).

NXSR — Nexus Rails Long-lived, governed deployments of the Nexus architecture defined by rail.yaml, for a specific mission × geography × institutional perimeter (e.g., “East Africa climate & food security rail”). Rails combine NXSOS, NXSTUDIO, NXOBS, NXCOMMS, NXN, and NXNODE under explicit governance (Rail DAO, NVM).

NXPCK — Nexus Packs Composable, domain-specific bundles defined by pack.yaml that package: GRIx ontology extensions, data pipelines, models, AAP/IRP playbooks, dashboards, connectors, CL/EQL targets, safety overlays, and NVM templates for coherent NRM use-cases (e.g., coastal flood & infrastructure, pandemic & health system stress).

NXSTUDIO — Nexus Studio The core data/ML/runtime platform comprising:

  • NEXCORE (orchestration runtime)

  • OP (UNOSINT ingestion pipelines)

  • GRIx runtime (ontology & lineage via Fabric IQ)

  • EWS (Early Warning Services)

  • AAP (Anticipatory & Action Playbooks module)

  • DSS (Decision Support Services)

  • NEXQ (workflow & queueing)

  • NSF SDK runtime, Data Fabric, ML Fabric, Policy Hub, Config & Secrets Service

It runs on the Fabric / OneLake reference implementation.

NXOBS — Nexus Observatory The intelligence and fusion layer. Hosts UNOSINT pipelines and INT modules, fusion engines, index engines (risk, resilience, systemic stress, equity), and the AEP Generator. Observatories are certified under GRF and assigned CL/EQL capabilities.

NXCOMMS — Nexus Comms The messaging and routing fabric: transport abstraction (HTTP/2/3, gRPC, MQTT, Matrix/XMPP, DTN), security envelopes and policy tags (SDZ, GeoGuard, HIL, safety), and topic/queue routing for indices, alerts, episodes, and coordination messages.

NXN — Nexus Network Integration of 5G/6G telco slices and DePIN overlays (decentralised physical infrastructure) for sensing, connectivity, and compute. Supports QoS, NTN (non-terrestrial networks), multi-rail traffic isolation, and degraded/contested-environment operation.

NXNODE — Nodes & Devices Layer Taxonomy, identity, and lifecycle management for all computational and physical endpoints: sovereign nodes, edge/MEC nodes, IoT/OT gateways, specialised compute (GPU/HPC/NPU/FPGA/quantum), and critical field devices. Includes node competence profiles, onboarding, attestation, SBOM management, and revocation.

NXAPP — Apps, Agents & Swarms The application and agent layer: UIs, dashboards, portals, mobile clients; data agents (virtual analysts); operations agents (virtual operations team members); policy agents (virtual strategists); and multi-agent swarms. Enforced by the Agent Safety Layer and Agent Capability DSL.

NXUNIV — Nexus Universe Marketplace and developer portal for listing and discovering rails, packs, apps, observatories, agents, connectors, and swarms. Includes catalog schemas, rating and reputation systems, certification/badging surfaces (CL/EQL, safety, BioSafe, PQ, privacy), and SDK/CLI tooling.

NXFOUNDRY — Nexus Foundry Design and assembly environment for packs, rails, ontologies, policies, and agents. Includes: Pack Design Studio, Rail Design Studio, Ontology & Schema tools, Policy & Playbook editors, Twin & Assurance Lab, Rail Twin & CSECOP (Cyber-Physical Systems & Ecosystems Operations environment), and GitOps/CI/CD integration, including testing and red-teaming pipelines.

NXPROG — Nexus Programs Programmatic layer covering NXAcademy (Nexus Risk Academy), assessment & simulation (scenario exams via twins and CSECOP), Nexus accelerators (country/sector/city rail deployments), partner & venture registry, maturity & governance analytics, and social/equity programmes (community advisory, grievance mechanisms, equity indicators).

NXHIVE — Nexus Hive The multi-rail orchestrator and systemic governance layer. Maintains cross-rail catalogs and topology, systemic observability (indices, AEP summaries, equity/ecology/energy/capital views), cross-rail corridors (food, energy, cyber, humanitarian), global policy pushes (minimum CL/EQL, PQ, BioSafe, AI safety baselines), systemic stress testing, and hive-level DAOs/NVM rules.

NXHAL — Hardware Abstraction Layer NXSOS component that abstracts heterogeneous hardware (CPU/GPU/NPU/FPGA/neuromorphic/quantum). Models compute capabilities, TEEs, HSMs, and supports placement/scheduling policies (e.g., TEEs-only, low-carbon nodes).

NXPAL — Platform Abstraction Layer NXSOS component abstracting container/orchestration platforms (K8s/K3s/OpenShift/Nomad/serverless), messaging systems (Kafka/Redpanda/NATS, MQTT), and storage backends (S3, Iceberg/Delta/Hudi, Postgres, ClickHouse, graph/TSDB).

NXMirror — Local Mirror & Offline Core Localised mirror of NXSS, registries, and critical evidence stores with minimal observatory and decision support views, enabling disconnected or contested environments. Synchronises conflict-aware with regional/sovereign hubs when connectivity permits.

NXIdentity Identity and credential infrastructure based on DID/VC (decentralised identifiers / verifiable credentials). Manages keys, roles, and credentials for users, nodes, agents, and institutions. Integrated with nxsos.iam-broker.


A.4 Semantic, Standards & DSL Constructs

GRIx — Global Risk & Resilience Index / Ontology Engine The core semantic and indexing engine of NXSS. Provides entity and relationship types, logic constraints, and index definitions across domains (climate, bio, cyber, finance, infrastructure, social), extended by packs. Implemented atop Fabric IQ in reference deployments.

SDZ — Sovereign Data Zones Classes and tiers specifying data residency, jurisdiction, and processing rules. Govern where data can reside, how it can be linked or aggregated, and which compute-to-data patterns are permissible, especially for sensitive and Indigenous data.

CL — Conformance Levels (CL1–CL4) Graduated levels indicating institutional and system conformance to Nexus standards and governance practices, from basic awareness and partial alignment (CL1) to fully embedded, audited, and high-stakes-capable implementations (CL4).

EQL — Evidence Quality Levels (EQL1–EQL5) Graduated levels indicating robustness, transparency, and reproducibility of evidence in AEPs, from exploratory/indicative (EQL1) to fully audited and methodologically mature use in high-stakes decisions (EQL5).

Chronotope Schemas Time–space–context models that encode the spatio-temporal framing of events, indices, AEPs, and decisions, enabling consistent aggregation, comparison, and narrative reconstruction of risk episodes.

Episode Schemas Standardised representations of episodes (signals → decisions → actions → outcomes) enabling evaluation, learning, and meta-governance. Episodes are first-class objects in the Chronotope & Episodic Memory Fabric.

Nexus Protocol The logical specification of how evidence, governance, and capital flows are orchestrated on the Nexus Rail: who can invoke which processes, under which constraints, with what logging and audit requirements. Implemented as part of NXSOS runtime.

Policy DSL A domain-specific language for expressing access, residency, safety, lawful-basis, GeoGuard, and human-in-the-loop (HIL) constraints in machine-readable form.

Playbook DSL A DSL for encoding Anticipatory Action Plans (AAPs) and Incident Response Playbooks (IRPs) as executable workflows tied to indices, triggers, and governance constraints.

Agent Capability DSL Language for specifying what agents can and cannot do (actions, scopes, conditions, safety tiers) and under what supervision patterns, enforced by the Agent Safety Layer.

Rail Configuration DSL (rail.yaml) Canonical YAML-based specification for a Nexus Rail’s identity, scope, governance profiles, SDZ configuration, topology, activated packs, SLOs, safety envelopes, DR/BC policies, and NVM rules.

Pack Configuration DSL (pack.yaml) Canonical YAML-based specification for a Nexus Pack’s identity, scope, dependencies, GRIx extensions, playbooks, dashboards, connectors, CL/EQL targets, and safety overlays.

Lawful-Basis Matrices Structured mappings of legal bases for data processing and sharing (e.g., consent, public interest, contractual necessity) across jurisdictions and data categories, integrated with the Policy DSL and SDZ configuration.


A.5 Data, Intelligence & AI Components

INT Modules Families of domain-specific “intelligence” within UNOSINT / NXOBS, including:

  • OSINT — Open-Source Intelligence.

  • GEOINT — Geospatial Intelligence.

  • IMINT — Imagery Intelligence.

  • SIGINT — Signals Intelligence.

  • MASINT — Measurement & Signature Intelligence.

  • CYBINT — Cyber Intelligence.

  • HUMINT — Human Intelligence.

  • SOCINT — Social Intelligence.

  • COMMINT — Communications Intelligence.

  • BIOINT — Biological Intelligence.

  • VETINT — Veterinary Intelligence.

  • AGROINT — Agricultural Intelligence.

  • FININT — Financial Intelligence.

  • MACROINT — Macroeconomic Intelligence.

  • CREDITINT — Credit & Solvency Intelligence.

  • GOVINT — Government & Public-Sector Intelligence.

  • POLINT — Political Intelligence.

  • LEGALINT — Legal & Regulatory Intelligence.

  • LOGINT — Logistics Intelligence.

  • SUPPLYINT — Supply-Chain Intelligence.

  • INFRAINT — Infrastructure Intelligence.

  • AI-INT — AI Systems Intelligence.

  • SYNINT — Synthetic/AI-Generated Intelligence.

  • MODELINT — Model Behaviour & Performance Intelligence.

  • TRUSTINT — Trust, Governance & Legitimacy Intelligence.

  • CLIMATEINT — Climate Intelligence.

  • RESILINT — Resilience Intelligence.

Each INT family contributes features, indices, and narratives into GRIx and AEPs.

Fabric / OneLake The reference unified data lakehouse platform used in Nexus implementations. OneLake provides a single logical data lake for all organisational data (SQL, NoSQL, streams, on-prem, cloud, SaaS), while Fabric provides multi-workload engines (ETL, analytics, real-time, operational DBs, BI). Nexus uses Fabric as the foundational unified data & platform layer.

Fabric IQ The semantic intelligence workload in Fabric, used as the implementation of GRIx ontologies and digital twins in Nexus. Supports entity-centric and relationship-centric modelling, binding to tables, streams, time-series, and geospatial data, and provides graph and twin navigation.

Foundry IQ The knowledge and agent orchestration layer integrated with Fabric IQ. Enables custom data agents, operations agents, and policy agents that operate over Nexus ontologies and actions, with full traceability and policy enforcement.

Data Agents Virtual analyst agents operating over the ontology and unified data, capable of answering analytic questions, exploring patterns, and generating candidate AEP components within safety and governance constraints.

Operations Agents Virtual operations team members configured via low-code experiences, connected to the ontology and action APIs, monitoring conditions (e.g., risk thresholds) and recommending or executing operational responses under HIL and Agent DSL constraints.

Policy & Strategy Agents Higher-level agents that assist with scenario design, policy option generation, and strategy evaluation, using NRM Profiles, AEPs, and simulation outputs, subject to strict safety, explainability, and governance regimes.


A.6 Security, Safety, Compliance & Operations

AI Safety Tiers A classification scheme for agents and AI models based on risk and capability, specifying allowed actions, required safeguards, and oversight levels for each tier (e.g., read-only analytic agents vs agents with actuation privileges on critical infrastructure).

BioSafe Rules Domain-specific rules and safeguards to prevent misuse of biological data, models, or simulations (e.g., dual-use concerns), including restrictions on detail, combinations of datasets, or automated design capabilities.

PQGuard The Nexus framework for post-quantum cryptography and crypto agility: baselines for acceptable algorithms, migration pathways, hybrid modes, and deprecation timelines for legacy schemes across NXSOS, NXIdentity, and related components.

Zero-Trust Security Fabric Cross-cutting security pattern enforcing continuous verification, least privilege, micro-segmentation, and no implicit trust, integrated with SDZ, NXIdentity, and Policy DSL.

HIL — Human-in-the-Loop Operational requirement that certain classes of decisions, actions, or agent suggestions must be reviewed and explicitly approved by a human with appropriate competence and authority before execution.

RailOps The ensemble of SRE, on-call, operations, and incident management practices applied to Nexus Rails and NXSOS services. Responsible for SLO attainment, incident handling, DR/BC, and coordination with governance bodies.

SLO — Service Level Objective A formal target for a given service or workflow (e.g., latency, availability, evidence quality timeliness) encoded in rail.yaml and enforced/monitored via NXSOS and RailOps.


A.7 External Frameworks & Acronyms (Referenced)

Basel (Basel III/IV, BCBS) Global banking supervision standards used as reference for NRM alignment in prudential risk, climate risk, and systemic stress testing domains.

COSO Committee of Sponsoring Organizations of the Treadway Commission; provider of widely adopted ERM frameworks. NRM integrates and extends COSO-style ERM into systemic contexts.

DRR — Disaster Risk Reduction Policy and practice frameworks focused on reducing disaster risk and impacts (e.g., UN Sendai Framework). NRM seeks semantic and operational compatibility with DRR.

DRF — Disaster Risk Finance Instruments and programmes for financing disaster response, recovery, and resilience (e.g., contingent credit, parametric insurance). NRM provides the evidence rail for DRF design, triggers, and learning.

DFI — Development Finance Institution Multilateral or national institutions providing development finance and risk finance; expected key users of NRM-linked facilities and NRM Profiles.

ESG — Environmental, Social, Governance Corporate and financial reporting categories; NRM provides systemic risk intelligence and evidence that can ground more meaningful ESG and impact metrics.

NIST, ISO, WMO, Sendai, IPCC Selected external standards and frameworks (cybersecurity, risk management, meteorology, DRR, climate science) to which NXSS and NRM artefacts are mapped via GRF-IP profiles and interoperability guidance.


Last updated

Was this helpful?