Nexus Standards · Climate risk standards · Standards that apply

Climate risk

Climate risk: standards that apply

The 7 standards listed for climate risk in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.

Back to Climate risk All programme areas

01NS-0

Constitution and principles

Status proposed · trust, authorization and assurance · NXS-STD-ST-000004

Rule	Text
`NS0-P1`	Open · The standards, their registries, schemas, catalogs and reference tools are published in the canonical repository under the licences recorded in `LICENSING.md`. Participation in development is open to every community and stakeholder under `GOVERNANCE.md`. No standard depends on a proprietary artifact, product, account or mark to be applied.
`NS0-P2`	Machine-readable first · Every normative element exists as data (registry, schema, clause) before it exists as prose; prose explains, data governs. A standard with no machine form is not a Nexus Standard.
`NS0-P3`	Identified · Every artifact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone.
`NS0-P4`	Verified, not asserted · Conformance is a claim with evidence: receipts, digests, signed attestations and observations (NS-11). A claim without evidence is recorded as a claim, never as a fact, and the claim ceiling of the implementation bounds every statement it makes.
`NS0-P5`	Zero trust · Authenticated is not authorized; entitled is not authorized; access is denied by default. Every verification, monitoring and enforcement path assumes no implicit trust between systems, tenants, sites or agents, and records who verified what under which mandate.
`NS0-P6`	Real-time · Standards express obligations that can be evaluated continuously against live records (observations, releases, corrections, deployments), and the standards themselves are versioned so that an implementation can state exactly which version it conforms to at any instant.
`NS0-P7`	Provenance everywhere · Every artifact records what it was derived from, who produced it, under which release and policy decision, and what corrected it (NS-3b, PROV-O profile). Corrections supersede; nothing is silently rewritten.
`NS0-P8`	Honest · A UNI identifies and resolves; it never certifies. `legalState` defaults to review-required. Readiness, approval and production status are never implied by a standard, a status, a page, a score or a badge.
`NS0-P9`	Nexus-aware · Standards address cross-domain interdependence (water, energy, food, health, biodiversity, climate and the sectors they touch) explicitly: an obligation can reference artifacts in another domain, and cascades are first-class.
`NS0-P10`	Names are governed · Codes are never names. Public names follow the marks policy (`governance/OPEN_BOUNDARY_IPR_AND_LICENSING.md`, section 7). A system or component is shown by its neutral display name and its UNI; the UNI may change with context (NS-9), and no name infringes anyone's mark.
`NS0-P11`	Community-owned development · Proposals, comments, decisions and versions of every standard are themselves artifacts with UNIs. The development process is specified (NS-13) and open, and authority to adopt is recorded, never assumed.
`NS0-P12`	Fail closed · Missing evidence, a missing legal state, a missing policy decision or unavailable verification results in a refusal with a typed reason, never in a pass.

Read NS-0 in full

02Earth observation

Surface heat, rain, snow and ice in the Arctic

The map frames the Arctic as an example geography for climate risk; the frame gives context and is not a statement of where the standards apply. Shown at first: land surface temperature, day, 8-day composite (VIIRS NOAA-20 Level 3, 8-day, NASA LANCE) and precipitation rate, daily mean (GPM IMERG, NASA GES DISC). The layer drawer adds snow cover (VIIRS NOAA-20 NDSI); sea ice concentration (GHRSST MUR); sea surface temperature anomaly (GHRSST MUR25); and water storage anomaly, monthly (GRACE-FO JPL mascons). NASA products are served through NASA GIBS under NASA's open data policy, with acknowledgement; coastlines, boundaries and place names come from NASA GIBS reference layers (© OpenStreetMap contributors, ODbL) and Natural Earth (public domain). Each layer shows its own observation date; full credits are given under the map. Other sources of the profile, such as ERA5 reanalysis (Copernicus Climate Data Store) and CMIP6 climate projections (Copernicus Climate Data Store), are listed for reference.

The interactive map needs JavaScript; the layer list and sources are below.

Layers 2

Climate signals

Latest available

NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © OpenStreetMap contributors (ODbL) · Natural Earth

Loading the latest NASA imagery.

Drag to move. Ctrl or ⌘ and scroll, pinch or the buttons to zoom; hover for the values under the pointer; reset returns to the region.

Surface heat, rain, snow, sea ice, marine heat and water storage, each a dated satellite or model product, framed on the Arctic.Satellite and model products as NASA publishes them, each with its own date; indicators, not assessments of any place.

Data: NASA GIBS · ASTER GDEM · Blue Marble · © OpenStreetMap contributors · Natural Earth · NASA EONETSources and licences

We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
VIIRS near-real-time products (flood, land surface temperature, snow cover, corrected reflectance), NASA LANCE; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
GPM IMERG precipitation, NASA Precipitation Processing System; distributed by the NASA Goddard Earth Sciences Data and Information Services Center (GES DISC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
GHRSST Level 4 MUR analyses, NASA Jet Propulsion Laboratory; distributed by the NASA Physical Oceanography DAAC (PO.DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
GRACE and GRACE-FO JPL mascon solution, NASA Jet Propulsion Laboratory; distributed by the NASA Physical Oceanography DAAC (PO.DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
ASTER GDEM is a product of METI and NASA (ASTER Global Digital Elevation Model V003, NASA LP DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). Cite as: NASA/METI/AIST/Japan Spacesystems and U.S./Japan ASTER Science Team (2019). ASTER Global Digital Elevation Model V003. doi:10.5067/ASTER/ASTGTM.003. NASA open data
Made with Natural Earth. Free vector and raster map data @ naturalearthdata.com. Public domain
© OpenStreetMap contributors (ODbL), via NASA GIBS (coastlines, boundaries, roads and place names). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). ODbL
Blue Marble, NASA Earth Observatory; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
Context on the globe and flat map: coastlines, boundaries, roads and place names from NASA GIBS reference layers (OpenStreetMap data, ODbL, © OpenStreetMap contributors); Blue Marble imagery as an optional base; 3D terrain and the elevation read-out from the ASTER GDEM elevation colour index (5 m to 200 m classes, exaggerated for legibility). Boundaries are drawn as published and imply no position on any territory.
Globe: MapLibre GL JS 6.9.1, BSD-3-Clause, © MapLibre contributors.
Live: NASA EONET Events are indicative, not authority warnings.
NASA GIBS: We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS).
Past year, daily temperature and sunshine (NASA POWER): These data were obtained from the NASA Langley Research Center (LaRC) POWER Project funded through the NASA Earth Science/Applied Science Program..
Optional layers (18 sources in the layer list: live, forecast, observed and context) print their provider credit on the map and here when switched on; forecasts are model output and derived indices are estimates.

Layers and dates

Land surface temperature, day, 8-day composite: VIIRS NOAA-20 Level 3, 8-day, NASA LANCE · 14 Sep 2026
Precipitation rate, daily mean: GPM IMERG, NASA GES DISC · 12 Oct 2026
Snow cover: VIIRS NOAA-20 NDSI, NASA LANCE · 13 Oct 2026
Sea ice concentration: GHRSST MUR, NASA JPL PO.DAAC · 12 Oct 2026
Sea surface temperature anomaly: GHRSST MUR25, NASA JPL PO.DAAC · 12 Oct 2026
Water storage anomaly, monthly: GRACE-FO JPL mascons, NASA JPL PO.DAAC · July 2022

03NS-1

The UNI and the artifact catalog (grammar v0.2: domain, sector, region and environment segments)

Status proposed · trust, authorization and assurance · NXS-STD-ST-000001

Rule	Text
`NS1-R1`	One UNI shall identify one artifact concept; versions share the UNI and differ in `@VERSION`.
`NS1-R2`	UNIs shall be allocated only through a catalog (`mint`) or a record allocation authority (NS-3); they shall not be typed by hand.
`NS1-R3`	UNIs shall not be deleted or reused. A withdrawn artifact keeps its record (`WITHDRAWN`); a replaced one records `supersededBy`.
`NS1-R4`	Every record shall carry the required metadata; `legalState` defaults to review-required; `claimCeiling` stays inside the claim registry.
`NS1-R5`	The UNI shall be embedded in the artifact itself so that machines and people can find the record (section 6).
`NS1-R6`	A regional artifact shall carry REGION; public regional or national use still follows the geographic rules of the marks policy.
`NS1-R7`	Codes are classification and shall not be used as product names.
`NS1-R8`	A new scope, domain, sector or environment code shall meet the allocation rules CA-1 to CA-10 (section 1.1) and shall enter through an NS-13 proposal.
`NS1-R9`	A code shall not be reassigned or deleted; a retired code is deprecated with `supersededBy`, and identifiers that use it remain valid.
`NS1-R10`	A `PROPOSED` code may be used and shall be shown with its status until the registry change is adopted.

Read NS-1 in full

04NS-3

Risk record UNIs (grammar, legacy crosswalk, allocation authority)

Status proposed · trust, authorization and assurance; canonical risk data, records and provenance · NXS-STD-ST-000003

NS-3 states its requirements in sections rather than in a table of rules.

Read NS-3 in full

05NS-3b

Dataset and product metadata profile (STAC, DCAT, PROV-O)

Status proposed · trust, authorization and assurance; canonical risk data, records and provenance · NXS-STD-SW-000005

NS-3b states its requirements in sections rather than in a table of rules.

Read NS-3b in full

06NS-9

Contextual UNIs (deployments, instances, programme instances)

Status proposed · trust, authorization and assurance · NXS-STD-ST-000005

Rule	Text
`NS9-R1`	Each deployment or programme instance shall have one context record; the concept keeps its own UNI; `context.ofUni` is required and shall resolve.
`NS9-R2`	Context identifiers shall be allocated by the catalog for their SCOPE; they shall not be derived from names or typed by hand.
`NS9-R3`	The claim ceiling, legal state and conformance evidence of a context are its own; they shall not be inherited from the concept or from another context.
`NS9-R4`	Closing a context shall not delete it: `context.validUntil` is set and the status becomes `WITHDRAWN` or `SUPERSEDED` with `supersededBy`.
`NS9-R5`	Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere.

Read NS-9 in full

07NS-11

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

Status proposed · trust, authorization and assurance · NXS-STD-ST-000007

Rule	Text
`NS11-R1`	A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest.
`NS11-R2`	Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject's trust boundary.
`NS11-R3`	Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12).
`NS11-R4`	Attestations shall be append-only and superseded rather than changed; monitoring records shall be observations with record UNIs.
`NS11-R5`	Every displayed conformance value shall carry its evaluation instant and its evaluator; projections shall not store verdicts.
`NS11-R6`	Exports to Verifiable Credentials, in-toto or PROV-O are crosswalks; the Nexus attestation shall remain the record of truth.

Read NS-11 in full

08NS-14

Conformance and crosswalk to external standards

Status proposed · trust, authorization and assurance · NXS-STD-ST-000013

Rule	Text
`NS14-R1`	The text of an external standard shall not be reproduced; it shall be cited by identifier, clause number and URL.
`NS14-R2`	Relation claims shall come from the register and from clause sets, not from prose.
`NS14-R3`	"Compliant" and "certified" shall appear only as quotations of an authority decision cited by reference.
`NS14-R4`	Marks of standards bodies shall not form part of a Nexus name.
`NS14-R5`	Unverified register entries shall be displayed as unverified.

Read NS-14 in full

09Questions

Questions and answers.

Are these all the rules for climate risk?

They are the rules stated by the listed standards. The principles of NS-0 bind every standard; clauses specific to the area, where needed, are written under NS-10 and evaluated under NS-11.

What does a rule identifier such as NS1-R5 denote?

The number of the standard and the number of the rule within it. Rule identifiers are stable so that clauses, attestations and publications can cite them.

NRNexus Reports gateway · GW-STD

Contribute to Nexus Reports from this page.

Nexus Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.

Nexus Standards

Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.

Across the Consortium

The same subject across the Consortium.

Around Climate risk.

Nexus Standards

Shape the standards for climate risk.

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.

Propose a change Roadmap to 2030 Adopt and implement

Status and use. The Nexus Standards are proposed standards developed through an open process under NS-13 and published for voluntary use; they do not constitute certification, accreditation or regulatory approval, and adoption remains a decision of the Global Standards Council and, in each country, of its National Standards Council. A UNI (Unique Nexus Identifier) identifies an artifact; it does not certify it. 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. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.

Licences: CC BY 4.0 for standards text, registries, schemas and data; Apache-2.0 for reference code. External standards are cited by name, number and link under their own licences. Third-party data, libraries and fonts keep their own licences: see Third-party notices.