Skip to content
StandaardeNS-3Voorgestel
NS-3

NS-3: Risikorekord-UNI's (grammatika, ooreenkomstabel vir ouer kodes, toekenningsgesag)

NS-3 is a proposed Nexus Standard; the artefacts it governs are identified by UNIs (Unique Nexus Identifier). NS-1 gives artefacts (software, reports, datasets, figures) a UNI allocated by the catalogue. NS-3 gives The Global Risks Index (NXS-GRX) records (observation facts, source releases, indicators, boundaries, chronotopes, corrections, analytical products, subjects) a UNI allocated by the UNI fabric in PostgreSQL, on the same grammar, so a record can be cited, resolved and crosswalked like any other Nexus artefact. A UNI identifies and resolves a record; it never certifies the record's truth (V3 directive, section 12).

NS-3 in the catalogue
The standards NS-3 depends on and those that cite it, then its sections with one mark for each numbered requirement.Source: NS-3-grix-record-uni.md; the Nexus Standards registry.
  • NS-3 depends on: NS-1, NS-3b.
  • NS-3 is cited by: NS-0, NS-1, NS-3b, NS-9, NS-10, NS-11, NS-15, NS-16.
  • Section 1, Grammar: no numbered requirement.
  • Section 2, Legacy ids stay valid: no numbered requirement.
  • Section 3, Allocation: no numbered requirement.
  • Section 4, What changes for ingest paths: no numbered requirement.
  • Section 5, Adopted paths: no numbered requirement.
  • Section 6, Follow-on: no numbered requirement.
01Oorsig

Summary

NS-3record
  1. Statusproposed
  2. Responsible scopetrust; canonical data
  3. Rules stated0
  4. Programme areas47
  5. Source filesrepository

Nexus Standards · proposed

Requirements
Not recorded
numbered rules
Sections
6
in the text
Depends on
2
NS-1, NS-3b
Cited by
8
Nexus Standards
02The standard

NS-3: the standard

The text of NS-3 as it stands in the canonical repository (commit 2cbe0d41b5f8): 6 clauses, 0 sub-clauses and 0 identified requirements, each with its anchor and citation.

Code
NS-3
Title
Risikorekord-UNI's (grammatika, oorerflike kruisverwysing, toewysingsgesag)
Version
0.1.0
Status
VOORGESTEL
Date
catalogue 2026-10-16 · circulated 17 October 2026
Unique Nexus Identifier
NXS-STD-ST-000003
Responsible scope
trust; canonical data
Bron
standards/NS-3-grix-record-uni.md at 2cbe0d41b5f8

Preparatory working draft, circulated for review and comment. Not for implementation. Prepared and circulated by Saeed Valadbaygi, Chief Steward, Nexus Standards (saeed@therisk.global), 17 October 2026. Technical review area: TR-02. This document is not a Nexus Standard; it may change without notice and is not to be implemented, relied upon or cited as a Nexus Standard. Its stage is designated only by the Global Standards Council and its technical committees under NS-13. Recipients are invited to submit comments with supporting reasons, and to notify any patent rights of which they are aware. See the notice of circulation.

Status
VOORGESTEL
Owner
the trust and assurance system (standard) and NXS-GRX (records)
Reference implementation (nexus-foundry): library the network's own records, store server/grix/uni/recordUniStore.ts, migration the network's own records, proof the network's own records

NS-1 gives artefacts (software, reports, datasets, figures) a UNI allocated by the catalogue. NS-3 gives NXS-GRX records (observation facts, source releases, indicators, boundaries, chronotopes, corrections, analytical products, subjects) a UNI allocated by the UNI fabric in PostgreSQL, on the same grammar, so a record can be cited, resolved and crosswalked like any other Nexus artefact. A UNI identifies and resolves a record; it never certifies the record's truth (V3 directive, section 12).

CiteNS-3, clause 1. NXS-STD-ST-000003@0.1.0. https://nexustandards.com/standards/ns-3/#nx-c-1

1. Grammar

NXS-GRX-<KIND>[-<REGION>]-<SERIAL>              the record concept   (ObservationFact.recordUni) NXS-GRX-<KIND>[-<REGION>]-<SERIAL>@<version>    one record version   (recordUni@recordVersion) NXS-GRX-OB-KEN-000042@3     observation fact 42 for Kenya, version 3 NXS-GRX-SR-000001           source release 1 (global)

The version segment is the NXS-GRX integer recordVersion. NS-1 v1.1 therefore accepts @3 as well as @1.2.0; an artefact carries a semantic version, a record an integer. A ref with a semantic version is not a record ref.

KindCodeKindCode
Observation factOBChronotope versionCT
Source releaseSRCorrection recordCR
Indicator definitionINAnalytical product recordAP
Measure definitionMESubject (place, asset, organisation)SU
Boundary versionBD

Record kinds and artefact categories never share a code (registry/nexus-standards.yaml#recordCategories; tools/validate.mjs and the consumer unit test enforce it).

CiteNS-3, clause 2. NXS-STD-ST-000003@0.1.0. https://nexustandards.com/standards/ns-3/#nx-c-2

2. Legacy ids stay valid

NXS-GRX already carries record ids such as obs:unrisk:<key>, uni:source:worldbank.wdi, uni:indicator:<code> and dotted ids such as grix.eo.stac.catalogue. They parse as LEGACY, keep working in <ref>@<version> refs (parseRecordRef, now used by the governed risk data-cut binder), and are crosswalked to an NS-1 UNI when allocated. Nothing is renamed in place; a record either carries an NS-1 recordUni (new records) or a legacy recordUni plus the allocated uni (ObservationFact.uni, optional during the transition).

CiteNS-3, clause 3. NXS-STD-ST-000003@0.1.0. https://nexustandards.com/standards/ns-3/#nx-c-3

3. Allocation

Serials are never derived or typed by hand (NS1-R2). They come from nexus_uni.allocate_record_serial(scope, category, region), an atomic counter per (GRX, kind, region) in nexus_uni.record_serial_sequence, advanced only inside a scoped tenant transaction (or the platform bypass). Every allocation is one append-only row in nexus_uni.record_uni_allocation (tenant, workspace, account, UNI, kind, region, serial, legacy_uni, verified principal). The legacy id is the idempotency key within an account: allocating the same legacy id twice returns the same UNI with reused: true. UNIs are never reused or reassigned: UPDATE, DELETE and TRUNCATE raise UNI_RECORD_ALLOCATION_IMMUTABLE, and a CHECK keeps the UNI string equal to its segment columns.

Isolation follows the repository's FORCE RLS pattern (v956 account-scope pair, systemic scope guard, v959 membership guard). The counters hold no tenant data; they are readable by any scope. The integration test proves on a real PostgreSQL, as a NOSUPERUSER NOBYPASSRLS role: serials shared across accounts, crosswalk private to the account, a forged scope writes nothing, mutation refused, the counter refused outside a scoped transaction, and the migration re-applies as a no-op.

const store = resolveRecordUniStore(); const { uni, reused } = await store.allocate(scope, { kind: "OB", region: "KEN", legacyUni: "obs:unrisk:wdi.KEN.SP.POP.TOTL.2020" }); // uni = "NXS-GRX-OB-KEN-000042"; ref for version 3: formatRecordRef(uni, 3)

Offline is a typed 503 (AuthoritativeStoreUnavailableError); there is no memory fallback.

CiteNS-3, clause 4. NXS-STD-ST-000003@0.1.0. https://nexustandards.com/standards/ns-3/#nx-c-4

4. What changes for ingest paths

  • New records: allocate through the store at write time and store the NS-1 form in recordUni.
  • Existing paths (obs:unrisk:… in server/unrisk/realDataObservationIngest.ts and the others): unchanged until each path is migrated; they can allocate and set uni on the fact without changing their recordUni key.
  • Refs: build with formatRecordRef(recordUni, recordVersion) and read with parseRecordRef(ref); both forms are accepted so correction dependencies keep resolving across the transition.
CiteNS-3, clause 4a. NXS-STD-ST-000003@0.1.0. https://nexustandards.com/standards/ns-3/#nx-c-4a

4a. Adopted paths

  • WDI bootstrap (CGRIC-03): allocates SR and OB UNIs with a verified uniScope; WdiBootstrapResult.uniAllocation.
  • Real-data hydration (server/unrisk/realDataHydration.ts, NS-3c): hydrateUnriskRealData(context, { uniScope: { accountId }, recordUniStore? }) crosswalks every obs:unrisk:<key>@<version> ref of the hydration to an OB UNI (region = ISO3 for country-scoped hydrations) through server/unrisk/realDataRecordUni.ts and records the outcome in data.uniAllocation (ALLOCATED with crosswalks, NOT_REQUESTED, or UNAVAILABLE with partial progress). The synchronous ingest (realDataObservationIngest.ts) keeps its legacy keys; the data cut and consumers keep matching them, and a product's PROV-O bundle maps both forms (NS-3b). The envelope's requester carries no account id, so callers supply it (NS-3d below); without it hydration reports NOT_REQUESTED.
  • Verified account forwarding (NS-3d): server/standards/verifiedUniScope.ts reads { accountId, principalId } from the request's verified claims only; a header, body or query account is never authority, and the acct:<tenant> the authority context synthesises is never used. POST /source-bootstrap/run passes it as uniScope to the WDI bootstraps; UnriskFabricScope.accountId is forwarded by runUnriskFabricQuery through hydrateUnriskRealDataComplete and hydrateUnriskRealDataExtended to hydrateUnriskRealData. The fabric query, NEIF mission-agent, data-agent and Commons agent-team routes and the hex-intel UNRISK contributor forward it; the Builder v2 UNRISK tool does not (its scope accepts a header account, NS3D-G1). Without a claim every path stays NOT_REQUESTED.
  • Open-data ingests (NS-3e): server/grix/fusion/openData/openDataRecordUni.ts allocates an OB UNI for every observation the public-data plane writes (native indicators from World Bank, UNSD, WHO, IMF and the statistical adapters; public hazard events; Open-Meteo current, forecast and ensemble records) under the system-owned scope the plane already uses for SQL (account ACC-GRIX-PUBLIC-DATA, identity system:grix-public-data). REGION is the ISO3 dimension or country place ref; points and globals are unregioned. The legacy recordUni stays the fabric key; the UNI rides on the stored fact (durable file and the PostgreSQL record payload), is kept across corrections, and a current version written before NS-3e receives its UNI on its next correction through the legacy crosswalk. Unchanged rows cost no fabric round-trip. A fabric outage never blocks an observation write: the first typed outage trips a per-pass circuit and the receipt's uniAllocation verslae UNAVAILABLE with the partial counts; any other scope is NOT_REQUESTED.
CiteNS-3, clause 5. NXS-STD-ST-000003@0.1.0. https://nexustandards.com/standards/ns-3/#nx-c-5

5. Follow-on

NS-3b delivered (NS-3b-dataset-and-product-metadata-profile.md). NS-3d (verified account forwarding) and NS-3e (open-data ingests) delivered. Remaining: a dedicated uni column on grix_chrono.observation_facts so the UNI is queryable without reading the record payload; the Builder v2 scope becomes claims-only so its tool can forward too.

Change history

Versions from the catalogue; entries from the changelog that name this document.

VersionDateNote
0.1.016 October 2026current version in the catalogue
  • 0.1.0 – 2026-10-16 Canonical repository bootstrapped from the standards first drafted inside nexus-foundry (work items LEGAL-NAME-ARCHITECTURE-001, NS-3-7-RECORD-UNI-RESOLVER-001, NS-3B-DATA-PROFILE-001).
  • 0.1.0 – 2026-10-16 NS-1 (the UNI and the artefact catalogue), NS-3 (NXS-GRX record UNIs) and NS-3b (STAC, DCAT, PROV-O profile) as PROPOSED documents under standards/.
03System model

How a shock travels through this system

A system model of the context of NS-3 built from the registry: 26 hazards, 25 systems, 10 sectors, 13 controls, 18 feeds, 17 indicators. The systems are 35 of the 87 areas that list NS-3 (cascading and systemic risk, finance and insurance, health, water, food and energy, infrastructure, hazards); the model shows where the records, data and controls that NS-3 governs sit in a cascade, and is not a reading of the standard's text. Select the components to include, choose an initiating hazard and run the scenario. Stress propagates through the hazard relations of the Nexus Hazard Standard (NHS-1), the exposure of each system, the recorded couplings and the sectors that carry the loss; adopted standards dampen transmission and live data sources support detection. All parameters are stated assumptions that the reader can adjust; results are illustrative scenario outputs for exercises and training, not forecasts or risk assessments. The Map view places the same run on an example geography, The Philippines, a region suited to the hazards named, with open data: country boundaries, a grid of hexagonal cells and NASA satellite layers for the initiating hazard. The geography serves exercises and training and is not an assessment of that place.

Gevare

  • HIV epidemic
  • Tropical cyclone
  • Earthquake
  • Ice-jam flood
  • Toxic gas release
  • Persistent organic pollutants
  • Natech event
  • Dam failure
  • Storm surge (set off downstream)
  • Intense rainfall (set off downstream)
  • River flood (set off downstream)
  • Flash flood (set off downstream)
  • Dangerous surf (set off downstream)
  • Widespread power outage (set off downstream)
  • Mass displacement (set off downstream)
  • Coastal flood (set off downstream)
  • Aftershock sequence (set off downstream)
  • Fault surface rupture (set off downstream)
  • Soil liquefaction (set off downstream)
  • Slope slide (set off downstream)
  • Rockfall (set off downstream)
  • Tsunami (set off downstream)
  • Building collapse (set off downstream)
  • Water supply failure (set off downstream)
  • Disaster and conflict debris (set off downstream)
  • Food and feed contamination (set off downstream)

Systems and couplings

Controls

  • NS-0 Grondwet en beginsels
  • NS-3 Risikorekord-UNI's (grammatika, oorerflike kruisverwysing, toewysingsgesag)
  • NS-11 Verifikasie en monitering (getuienis, attestasies, zero-trust-ooreenstemmingwaarneming)
  • NS-9 Kontekstuele UNI's (ontplooiings, instansies, programinstansies)
  • NS-10 Beleide en klousules (masjienleesbare verpligtinge, afdwinging in gemeenskaplike ruimtes en bevelkamers)
  • NS-14 Konformiteit en ooreenkomstabel met eksterne standaarde
  • NS-5 Standaard vir figure, kaarte en visualisering (met die UI/UX-stel)
  • NRS-H61 Gevarefamilie: Kaskaderende faling (NHS-1 sys.cascade)
  • NRS-H60 Gevarefamilie: Ontwrigting van voorsieningskettings en vloei (NHS-1 sys.supply-chain)
  • NRS-H62 Gevarefamilie: Saamgestelde en veelvuldige-gevaar-gebeure (NHS-1 sys.compound)
  • NRS-H41 Gevarefamilie: Oordrag van dier na mens (NHS-1 health.zoonotic)
  • NRS-H65 Gevarefamilie: Oorskryding van planetêre grense (NHS-1 planet.boundary)
  • NRS-H43 Gevarefamilie: Epizoötieë by vee en akwakultuur (NHS-1 health.animal-health)

Observation

  • WHO Disease Outbreak News (listed for reference)
  • WAHIS animal health events (listed for reference)
  • GBIF occurrence API and downloads (listed for reference)
  • ERA5 reanalysis (Copernicus Climate Data Store) (listed for reference)
  • CHIRPS quasi-global gridded precipitation (listed for reference)
  • USGS earthquake GeoJSON summary feeds (listed for reference)
  • PubChem compound, hazard and GHS classification records (listed for reference)
  • eMARS Major Accident Reporting System (listed for reference)
  • Copernicus EMS rapid mapping activations (listed for reference)
  • OpenStreetMap planet and replication (listed for reference)
  • FAOSTAT (listed for reference)
  • FEWS NET food security outlooks and data (listed for reference)
  • IPC food insecurity classifications (listed for reference)
  • World Development Indicators (listed for reference)
  • Global Human Settlement Layer (listed for reference)
  • WorldPop gridded population (listed for reference)
  • Overture Maps buildings theme (listed for reference)
  • OpenStreetMap (listed for reference)
  • International Health Regulations capacity and health emergency preparedness
  • Proportion of countries adopting relevant national legislation and adequately resourcing the prevention or control of invasive alien species
  • Total public international support for national disaster risk reduction actions (Sendai indicator F-1)
  • Direct economic loss attributed to disasters in relation to global GDP
  • Number of parties to international multilateral environmental agreements on hazardous waste and other chemicals
  • Hazardous waste generated per capita and proportion treated
  • Mortality rate attributed to unintentional poisoning
  • Number of disruptions to basic services attributed to disasters
  • Proportion of agricultural area under productive and sustainable agriculture
  • Indicator of food price anomalies
  • Prevalence of moderate or severe food insecurity in the population, based on the Food Insecurity Experience Scale
  • Direct agricultural loss attributed to disasters
  • Agricultural land (% of land area)
  • Direct economic loss in relation to global GDP, damage to critical infrastructure and number of disruptions to basic services, attributed to disasters
  • Proportion of local governments that adopt and implement local disaster risk reduction strategies in line with national strategies
  • Proportion of urban population living in slums, informal settlements or inadequate housing
  • Percentage of local governments that adopt and implement local disaster risk reduction strategies in line with national strategies

Example geography

  • The Philippines: 184 hexagonal cells
  • Night lights tonight, outages (VIIRS Day/Night Band), NASA GIBS
  • Rain rate, last half hour (IMERG), NASA GIBS
  • Surface water through cloud, 30 m (OPERA DSWx-S1 radar), NASA GIBS
  • Surface soil moisture (SMAP), NASA GIBS
04Navorsing

Research, sources and files

Recent research on NS-3

Recent peer-reviewed articles, preprints, datasets and reports on the subject of this standard, retrieved at the time of reading from open scholarly metadata services (OpenAlex, Crossref, DataCite, Zenodo, arXiv, Europe PMC, OpenAIRE Graph) with search terms composed from the registry. Each work is listed with its authors, venue, year, type, open-access status and licence, and links to its DOI or landing page. Sources not yet enabled for live display on this site are listed for reference and are not queried.

Search termsdisaster loss data; disaster loss database; hazard event identifier; disaster event database; loss and damage data; DataCite Metadata Schema; ORCID iDcombined with: disaster; hazard; riskDerived from the subject of the standard and its rules, and the external standards of its crosswalk domains.

  • OpenAlexlisted for reference; not queried
  • Crossreflisted for reference; not queried
  • DataCitelisted for reference; not queried
  • Zenodolisted for reference; not queried
  • arXivlisted for reference; not queried
  • Europe PMClisted for reference; not queried
  • OpenAIRE Graphlisted for reference; not queried

No source is enabled for live display on this site yet: the sources are listed for reference and none is queried. Once the publisher of record enables a source after its terms are reviewed, recent works are listed here. Metadata and links only: title, authors, venue, year, type, open-access status and licence as each source records them; works are listed for orientation, not reviewed or endorsed.

05In practice

Where it applies and how it is developed

How it is developed and how to take part, the standard as a process, and the programme areas that list it.

How NS-3 is developed, and how to take part

NS-3 is developed in the open under NS-13 (the stages and gates of NS-13). Working groups draft, councils decide the reserved matters, and anyone may propose a change, comment, submit an implementation report, object or appeal, without membership or fee.

06Eksterne standaarde

Relation to external standards

NS-3 relates to external standards by identifier, clause number and URL (NS14-R1), and directs the reader to the issuing body.

07Oor die netwerk

Learning, the network and questions

Risk Academy courses and disciplines

1 course and 2 disciplines of Risk Academy (risksacademy.com) that teach the knowledge and methods of NS-3. Each course lists its level, stream and learning hours.

Kursusse

Dissiplines

The correspondence between courses, disciplines and the Nexus Standards is maintained with Risk Academy and is subject to its academic review.

VerslaeDra by

Dra bewyse vanaf hierdie bladsy by.

Reports is die Konsortium se kwartaallikse publikasie. Wat jy oor hierdie onderwerp weet, kan in die volgende uitgawe bewyse, 'n gevallestudie of 'n regstelling word, aan jou toegeskryf en gepubliseer onder CC BY 4.0 waar dit jou eie werk is.

Nexus Standards
Standaarde

Neem deel aan die standaarde.

Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.

Status en gebruik. Die Nexus Standards is voorgestelde standaarde wat deur 'n oop proses onder NS-13 ontwikkel en vir vrywillige gebruik gepubliseer word; hulle maak nie sertifisering, akkreditasie of regulatoriese goedkeuring uit nie, en aanvaarding bly 'n besluit van die Wêreldwye Standaarderaad en, in elke land, van sy Nasionale Standaarderaad. 'n UNI (Unique Nexus Identifier) identifiseer 'n artefak; dit sertifiseer dit nie. Name van standaardliggame en hul standaarde behoort aan hul rentmeesters en word slegs gebruik om die dokumente te identifiseer; geen teks van 'n eksterne standaard word hier gereproduseer nie. Nexus Standards is nie geaffilieer met, onderskryf deur of gesertifiseer deur enige standaardliggaam wat hier genoem word nie.

Lisensies: CC BY 4.0 vir standaardteks, registers, skemas en data; Apache-2.0 vir verwysingskode. Eksterne standaarde word volgens naam, nommer en skakel onder hul eie lisensies aangehaal. Derdeparty-data, -biblioteke en -lettertipes behou hul eie lisensies: sien Kennisgewings van derde partye.