Nexus StandardsHumanitarian Action and DevelopmentSectors and industries
Area · registry row planned

Humanitarian and civil society

The humanitarian and civil society section of the Humanitarian Action and Development subsite serves agencies, NGOs, community organisations and anticipatory-action programmes: how needs, response, funding and trigger records are identified, exchanged and verified under data-responsibility rules, crosswalked to Sphere, the Core Humanitarian Standard, HXL, IATI and the IPC. Every artifact of the area carries a UNI (Unique Nexus Identifier), which identifies and never certifies.

Area recordHumanitarian Action and Development
  1. TierSectors and industries
  2. Registryregistry row · planned
  3. Nexus StandardsNS-0, NS-3, NS-9, NS-10, NS-11
  4. Open standards7
  5. Feeds6 · 0 admitted
  6. Couplings4
  7. Last reviewed2026-10-17

Context entry PROPOSED for the Nexus Standards registry.

UNI
NXS-STD-DC-000003
Status
PROPOSEDregistry row · planned · scope AAP
Last reviewed
area context bank
Cite this page

Nexus Standards (2026). Humanitarian and civil society: area brief, Humanitarian Action and Development (PROPOSED). https://nexustandards.com/humanitarian/humanitarian-sector-standards/ · UNI NXS-STD-DC-000003. Last reviewed 2026-10-17.

Download the profile

Files carry the credits and the licence line; they are generated in your browser and nothing is sent. Downloads need script.

01Scope

Humanitarian and civil society: what the area covers, and what it leaves to others.

The sectors and industries section of Humanitarian Action and Development. Scope as the area context entry states it (PROPOSED).

In scope 5

  • Needs assessment and response records tagged with HXL
  • Funding flows recorded in IATI and FTS
  • Anticipatory action triggers and protocols with forecast provenance
  • Food-security classification records (IPC)
  • Data-responsibility obligations as NS-10 clauses

Out of scope 3

  • Operational decisions on assistance
  • Personal data of affected people
  • Evaluation of agency performance

Jurisdictions No jurisdiction note is recorded for this area yet; jurisdiction narrows what applies and never implies that a Nexus profile satisfies a law.

02Nexus Standards that apply

5 Nexus Standards for this area.

The Nexus Standards the area context entry lists; the registry row lists NS-0, NS-3, NS-9, NS-10, NS-11. Every one is proposed or specified; none is adopted by an authority.

  1. 01

    NS-0 · Constitution and principles

    Status proposed · 12 rules stated. Read NS-0 · The rules for this area

  2. 02

    NS-3 · GRIx record UNIs (grammar, legacy crosswalk, allocation authority)

    Status proposed · 0 rules stated. Read NS-3 · The rules for this area

  3. 03

    NS-9 · Contextual UNIs (deployments, instances, programme instances)

    Status proposed · 5 rules stated. Read NS-9 · The rules for this area

  4. 04

    NS-10 · Policies and clauses (machine-readable obligations, enforcement in commons and command rooms)

    Status proposed · 7 rules stated. Read NS-10 · The rules for this area

  5. 05

    NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)

    Status proposed · 6 rules stated. Read NS-11 · The rules for this area

04Restricted compatibility profiles

No closed standard is named for this area.

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.

05Hazards and sectors

What acts on this area, and who carries it.

Hazards and threats 4

DisastersConflict and displacementFood crisesEpidemics

Sectors 1

humanitarian
06Systemic couplings

4 couplings to other areas and subsites.

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).

Canvas · the area and its couplingsDesign, not a record
Humanitarian and civil society: systemic couplingsThe couplings the area context bank records for Humanitarian and civil society: 1 area in Humanitarian Action and Development, 3 areas in other subsites and 3 subsites reached. Each coupling carries a mechanism stated in the context bank (PROPOSED); a reading aid, not a dependency proof.

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.

  1. Agriculture and land useWater and Food SystemsAnticipatory action for drought and pests reads agricultural season monitoring and food-security classifications.
  2. Health systemsHealth and BiosecurityOutbreak response in crises combines health surveillance with humanitarian logistics.
  3. International organisations and multilateralsHumanitarian Action and DevelopmentPooled funds, appeals and cluster coordination are run by multilateral agencies whose records flow through IATI and FTS.
  4. Defence and civil protectionHazards and Disaster Risk ReductionCivil protection and civil-military coordination support humanitarian operations in large disasters.
07Data and feeds

6 sources, with provider, licence and delivery path.

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.

Every feed · pending admission

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.

Admitted
0
none yet
Register row exists
3
recorded for the GRIx path
Proposed row
3
terms to be recorded
Delivery
3 GRIx · 0 plugin · 0 browser · 3 snapshot
GRIx first, then plugin, browser-direct, snapshot
  • INFORM Risk Indexpending admission

    European Commission JRC · annual and mid-year

    CC BY 4.0 (European Commission reuse policy)

    GRIx governed readregister row exists

  • IPC food insecurity classificationspending admission

    IPC Global Partners · per analysis cycle

    IPC terms (to be recorded by Legal/IP)

    GRIx governed readregister row exists

  • Refugee Data Finderpending admission

    UNHCR · semi-annual

    CC BY 4.0 (register adapter string; not verified)

    GRIx governed readregister row exists

  • Financial Tracking Servicepending admission

    UN OCHA · daily

    OCHA FTS terms (reuse with attribution; to be recorded)

    build-time snapshotproposed register row

  • 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

08Readiness

What each pathway can read from this area.

GCRI Canada evidence pathway

GCRI Canada

Trigger, needs and funding records with provenance and data-responsibility controls become readable as evidence for GCRI Canada, which applies its own rules.

Open the GCRI Canada evidence pathway

Recognition pathway

The Global Risks Forum (GRF)

An agency programme that publishes protocol clauses and attestations gives GRF a record trail to consider; recognition is GRF's decision.

Open the Recognition pathway

Capital pathway

The Global Risks Alliance (GRA)

Pre-arranged finance for anticipatory action can present verified trigger histories to GRA, which assesses capital readiness under its own rules.

Open the Capital pathway

Each institution decides under its own rules what it reads as evidence; no pathway is an approval, a readiness statement or investment advice.

11Working group

The working-group charter, proposed.

Scope

Profile humanitarian needs, response, funding and trigger records and crosswalk them to Sphere, CHS, HXL, IATI and IPC under data-responsibility rules.

No working group is chartered yet; a community may charter this one under NS-13 through a docket.

Deliverables · 3
  1. Anticipatory trigger and protocol record profile
  2. HXL and IATI crosswalk for Nexus records
  3. Data-responsibility clause pack under NS-10 citing the IASC guidance
Liaison targets · 5
  • OCHA Centre for Humanitarian Data liaison sought
  • IATI Secretariat liaison sought
  • Sphere Association liaison sought
  • CHS Alliance liaison sought
  • IFRC liaison sought
12Audiences

Who works with this area: 4 audiences.

  1. Humanitarian agencies and NGOs
  2. Anticipatory-action and pre-arranged finance programmes
  3. Community organisations
  4. Donors
13Open problems

3 open problems an expert would start with.

  1. Trigger thresholds are set per programme without shared verification metrics, so forecast skill is not comparable.
  2. Affected-population figures differ across agencies for the same event because definitions and dates differ.
  3. Data-responsibility rules conflict with open-data defaults for sub-national needs data.
14Registry depth

The registry row: scope AAP, 3 crosswalk domains.

This area has a row in registry/subsites.yaml (status planned), so it carries five depth pages and the register crosswalk of its domains.

Crosswalk graph · humanitarian and civil societyFrom the registry
Humanitarian and civil society: the register crosswalk51 nodes on four orbits (Nexus Standards and consumers inside, then domains, external standards and issuing bodies) joined by 67 register links.
Nexus StandardsDomainsExternal standardsIssuing bodiesConsumers

5 Nexus Standards · 3 domains · 24 external standards · 18 issuing bodies · 1 consumers. Relations are register entries (adopt, profile, crosswalk, cite), never compliance claims; names belong to their stewards.

Crosswalk graph51 nodes and 67 links from registry/external-standards.yaml, registry/subsites.yaml and registry/consumers.yaml. Relations (adopt, profile, crosswalk, cite) are register entries, never compliance claims.

The registry holds no geography for the area itself: areas are not places. The one geography it implies is where the bodies that issue the area's external standards sit.

Standards globe · Humanitarian and civil society: issuing bodiesFrom the registry
Where the issuing bodies of the external standards register sitA plate carrée world map with Natural Earth coastlines, H3 resolution 2 hexagons at the public seats of 15 issuing bodies and one dot per seat. 24 register entries.
Issuing bodies' seats (15)H3 cells, resolution 2 (5); darker, more register entriesSubsites, consumers, standards: no geography in the registry
Issuing bodies and their seats (15)
BodySeatRegister entries
ISO/TC 292Geneva, Switzerland3
OASIS Emergency Management TCWoburn, Massachusetts, United States3
WMOGeneva, Switzerland2
CHS Alliance, Groupe URD and SphereGeneva, Switzerland1
FAO/WHO Codex Alimentarius CommissionRome, Italy1
HXL Working Group (UN OCHA Centre for Humanitarian Data)The Hague, Netherlands1
IFRCGeneva, Switzerland1
Inter-Agency Standing Committee (Data Responsibility Working Group)Geneva, Switzerland1
International Aid Transparency InitiativeNew York, New York, United States1
IPC Global Partners (FAO-hosted Global Support Unit)Rome, Italy1
ISO/TC 34/SC 17Geneva, Switzerland1
ITU-TGeneva, Switzerland1
Sphere AssociationGeneva, Switzerland1
WMO and UNDRRGeneva, Switzerland1
WMO, UNDRR, ITU, IFRC (co-leads)Geneva, Switzerland1

1 subsites: no geography in the registry (areas, not places) · 2 consumers: repositories, no geography · 19 Nexus Standards: documents, no geography · 3 issuing bodies without a fixed public seat, listed not drawn: United Nations General Assembly; UN Human Rights Council; International Plant Protection Convention · Programme regions of the ecosystem coverage register: named, not drawn (no coordinates in the registry)

Standards globe15 issuing bodies with a public seat, 24 register entries, H3 cells at resolutions 1 to 4. Seats are city coordinates, not registry fields; subsites, consumers and standards have no geography, so none is drawn. Plate carrée still map; globe with script.

Area on the sitesArtifact kindsGoverning standardsPages
Disaster and crisis (GCRI Canada field gateway; GRF and GRA counterparts)data, dataset, report, map, documentationNS-1, NS-3, NS-3b, NS-4, NS-5therisk.global/fields/disaster/
Disaster risk reduction, disaster risk finance, disaster risk intelligence (DRR, DRF, DRI)data, report, policyNS-1, NS-3b, NS-4, proposed NS-11globalriskforum.com/nexus-universe/

From the ecosystem coverage register: what the GCRI Canada, The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) sites publish on this area, as claimed there and not evaluated here.

15References

4 sourced references.

Peer-reviewed sources and published statistics on the publishers' own domains, as the context entry cites them.

16Learning

Risk Academy faculties for this area.

Plain links to the faculty pages of Risk Academy; no course, credential, recognition or endorsement is implied.

17Key terms

Terms used on this page.

UNI
Unique Nexus Identifier: identifies and resolves an artifact and its record; it never certifies truth, readiness or approval.
PROPOSED
Drafted content that no authority has adopted. Every area entry here is a proposal to the Nexus Standards registry.
cite
Relation: the external standard is cited by identifier and URL as a reference.
adopt
Relation: the external standard is used as published, values validated against it.
crosswalk
Relation: Nexus clauses are mapped to parts of the external standard by number, never by text.
pending admission
No legal register row admits this source for display on public pages yet, so nothing is read from it.
GRIx
The governed data layer of Nexus Foundry: external data is read through it with its licence and source release.
docket
A public change record under NS-13, decided by editors with written reasons.
attestation
An evaluator's recorded result for one clause and one subject under NS-11; never a certification.
liaison sought
A liaison the working group would ask the body for; none is held unless the body confirms it in writing.
19Learn and apply

Where Humanitarian and civil society is taught, worked on and run.

Risk Academy disciplines that teach Humanitarian and civil society, 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.

Risk Academy

Disciplines and courses

20Questions

Questions and answers.

Is the Humanitarian and civil society area adopted?
No. The area entry is PROPOSED content for the Nexus Standards registry beside its registry row. Adoption of any standard is a recorded authority decision and none is recorded today.
Are the feeds on this page live?
No. Every feed is pending admission: no legal register row admits it for public pages yet, so nothing is read from it here.
How do I change this brief?
Through a docket under NS-13: a pull request against the area context bank or the registry, decided by editors with written reasons.
Nexus Standards

Shape this brief: Humanitarian and civil society.

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.

Skip to toolbar