The humanitarian and public-sector entry section of the Humanitarian Action and Development subsite is written for emergency managers, humanitarian information officers and public-service practitioners: it walks through the CAP and WIS 2.0 packages, the alert console in the sandbox, and the HXL and IATI packages, and shows how operational records stay interoperable and responsible under data-protection rules. Every artifact of the area carries a UNI (Unique Nexus Identifier), which identifies and never certifies.
Context entry PROPOSED for the Nexus Standards registry.
Nexus Standards (2026). For humanitarian and public-sector practitioners: area brief, Humanitarian Action and Development (PROPOSED). https://nexustandards.com/humanitarian/for-humanitarian-and-public-sector/. Last reviewed 2026-10-17.
Files carry the credits and the licence line; they are generated in your browser and nothing is sent. Downloads need script.
The audiences section of Humanitarian Action and Development. Scope as the area context entry states it (PROPOSED).
In scope 5
Out of scope 3
Jurisdictions No jurisdiction note is recorded for this area yet; jurisdiction narrows what applies and never implies that a Nexus profile satisfies a law.
Standards
| Standard | Title | Status | UNI |
|---|---|---|---|
| NS-1 | The UNI and the artifact catalog (grammar v0.2: domain, sector, region and environment segments) | proposed | NXS-STD-ST-000001 |
| NS-9 | Contextual UNIs (deployments, instances, programme instances) | proposed | NXS-STD-ST-000005 |
| NS-10 | Policies and clauses (machine-readable obligations, enforcement in commons and command rooms) | proposed | NXS-STD-ST-000006 |
| NS-11 | Verification and monitoring (evidence, attestations, zero-trust conformance observation) | proposed | NXS-STD-ST-000007 |
Areas
NS-0, NS-1, NS-3, NS-3b, NS-9, NS-10, NS-11 · planned
Nexus domainsNS-0, NS-1, NS-3, NS-9, NS-10, NS-11 · planned
Nexus domainsNS-0, NS-1, NS-3, NS-3b, NS-9, NS-10, NS-11 · planned
Nexus domainsNS-0, NS-1, NS-3, NS-9, NS-10, NS-11 · planned
Nexus domainsNS-0, NS-1, NS-3, NS-3b, NS-9, NS-11, NS-14 · planned
Hazard and threat familiesNS-0, NS-3, NS-3b, NS-11 · planned
Hazard and threat familiesNS-0, NS-3, NS-3b, NS-11 · planned
Hazard and threat familiesNS-0, NS-3, NS-3b, NS-11 · planned
Hazard and threat familiesNS-0, NS-3, NS-9, NS-11 · planned
Hazard and threat familiesNS-0, NS-3, NS-11 · planned
Hazard and threat familiesNS-0, NS-3, NS-9, NS-11 · planned
Hazard and threat familiesNS-0, NS-9, NS-10, NS-11, NS-12 · planned
External standards
Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here.
12 more in the crosswalk pages of the areas above.
Tools
Implementation status per consumer, not readiness or certification.
| Consumer | Role | This audience's standards |
|---|---|---|
| nexus-foundry | runtime (Foundry server, rooms, passports, GRIx fabric) and catalog for the system, organisation, LEG, GOV and PRG scopes | NS-1 planned (wired on a branch not yet merged, #3043) · NS-9 planned (wired on a branch not yet merged, #3043) · NS-10 planned (wired on a branch not yet merged, #3043) · NS-11 planned (wired on a branch not yet merged, #3043) |
| nexus-foundry-wordpress-plugin | editorial and institutional sites (GCRI Canada, GRF, GRA subsites; therisk.global Nexus Registry) | NS-1 planned (wired on a branch not yet merged, #3043) |
| Record | Title | Status |
|---|---|---|
NXS-STD-ST-000001 | Nexus Standards NS-1 - the UNI and artifact catalog | draft |
NXS-STD-SW-000001 | UNI runtime library (TypeScript, nexus-foundry consumer implementation) | draft |
NXS-STD-SW-000002 | UNI command-line tool (validate, parse, next, mint, catalog, export) - reference implementation | draft |
NXS-STD-SC-000001 | UNI artifact record schema v1 | draft |
NXS-STD-SW-000003 | UNI crosswalk exports (Zenodo, DataCite, Schema.org, CodeMeta, CITATION.cff) - nexus-foundry consumer implementation | draft |
NXS-STD-SW-000004 | Zenodo deposit client (sandbox default, dry-run default, legal gate) - nexus-foundry consumer implementation | draft |
NXS-STD-ST-000002 | Open-standards and open-source stack under the UNI | draft |
NXS-STD-SW-000005 | UNI data profile (STAC, DCAT, PROV-O crosswalks) - standard text here, nexus-foundry consumer implementation | draft |
NXS-STD-ST-000003 | Nexus Standards NS-3 - GRIx record UNIs (grammar, legacy crosswalk, allocation authority) | draft |
NXS-STD-ST-000005 | Nexus Standards NS-9 - contextual UNIs (deployments, instances, programme instances) | draft |
Pathways
Each institution decides under its own rules; no pathway is an approval.
What an institution, programme or deployment must evidence for GRF recognition records; records, not reputation. Open the pathway
What a project, dataset or model must carry to be admissible evidence in the GCRI Canada research and intelligence pipelines. Open the pathway
Version and feed state per standard; every row reads source feed pending admission until a register row admits a feed.
Today · from the registryTest suites, conformance statements and attestations per standard; no attestation is recorded yet, and none would certify.
Today · in your browserPick a sector, hazard family, capability and artifact type; the registry routes the standards and says why.
A console computes from the registry and shows its reasons; it never decides, approves or certifies.
The Nexus Standards the area context entry lists. Every one is proposed or specified; none is adopted by an authority.
Status proposed · 12 rules stated. Read NS-0
Status proposed · 0 rules stated. Read NS-3
Status proposed · 7 rules stated. Read NS-10
Status proposed · 6 rules stated. Read NS-11
Relations are register entries (NS-14), never conformance or equivalence statements; hover or focus a relation for its meaning. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here.
Each coupling names the mechanism that links this area to another; select a card on the canvas to trace it. Mechanisms are stated in the context bank (PROPOSED).
Fig.RUNNING marks the area you are reading; DONE an area in the same subsite, QUEUED an area elsewhere and GATE a subsite reached. Tags give reading order only, never a status. Design, not a record.
Practitioners learn which operational and warning records GCRI Canada can read as evidence, with GCRI Canada deciding admissibility.
Practitioners see how a programme's protocols and attestations form a trail GRF may consider under its own rules.
Practitioners see how anticipatory finance can present verified trigger histories to GRA, which decides capital readiness; no approval is implied.
Each institution decides under its own rules what it reads as evidence; no pathway is an approval, a readiness statement or investment advice.
Sources the area reads or proposes. Delivery follows GRIx first; a source is shown live only after an owner decision admits it for public pages.
No legal register row admits any of these sources for live display on public pages yet, so nothing is read from them here. A register row that exists records the source for the governed GRIx path; admission for public pages is a separate owner decision.
GDACS disaster alerts (API, RSS, CAP)pending admission
European Commission JRC and UN OCHA · near real time
European Commission reuse policy (CC BY 4.0) via GDACS terms
GRIx governed readregister row exists
WMO Alert Hub and Register of Alerting Authoritiespending admission
World Meteorological Organization · real time
WMO Unified Data Policy plus each alerting authority's terms
GRIx governed readregister row exists
Humanitarian Data Exchangepending admission
UN OCHA Centre for Humanitarian Data · continuous
Per-dataset licences (CC BY, CC BY-IGO, ODbL and others)
build-time snapshotproposed register row
IATI Datastorepending admission
International Aid Transparency Initiative · daily
Publishers' open licences as declared in the IATI Registry
build-time snapshotproposed register row
Indicator names and codes as their stewards publish them; values appear only from a governed GRIx source, never typed into a page.
Curate the practitioner learning path and the sandbox alert scenarios.
No working group is chartered yet; a community may charter this one under NS-13 through a docket.
Closed or paywalled standards appear by name and link only; any compatibility profile of one is built on simulated data and kept on protected pages until an institutional arrangement with the issuing body is recorded. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.
The working group may name closed standards later; they would be listed here by name and link only.
Hazards and threats 0
No hazard or threat is listed for this area; it reads the hazards of the areas it couples with.
Sectors 0
No sector is listed for this area; it serves every sector through the areas it couples with.
Peer-reviewed sources and published statistics on the publishers' own domains, as the context entry cites them.
Plain links to the faculty pages of Risk Academy; no course, credential, recognition or endorsement is implied.
Risk Academy disciplines that teach For humanitarian and public-sector practitioners, with their courses; the GCRI Canada, The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) subsites that carry those disciplines; and the Nexus Foundry systems the standards name. Mappings are proposed for review (Risk Academy standards map, 2026-10-17); a link says a page on the same subject exists, never an endorsement or a conformance statement; framework names in course titles are named and linked, never reproduced.
Propose a change, join the working group or name a source. Area entries are PROPOSED content for the Nexus Standards registry; a UNI identifies and never certifies, and nothing on this site is a certification, an approval or a readiness statement.
Nexus Standards documents CC BY 4.0 · tooling Apache-2.0 · counsel review pending (DEC-2026-10-16-NEXUS-STANDARDS-OPEN-LICENCE). External standards are named and linked under their own licences; a UNI (Unique Nexus Identifier) identifies, it never certifies. · Generated from the Nexus Standards corpus at commit 437ae044c5cb (2026-10-17); proposed and open.