Nexus StandardsHydrometeorological hazard standardsStandards that apply
Hydrometeorological hazard

Hydrometeorological hazard: standards that apply

The 4 standards listed for hydrometeorological hazard in the subsite registry, each with its status, UNI (Unique Nexus Identifier) and the rules its text states. Every standard here is proposed: drafted and applied by consumers, not adopted by an authority. A UNI identifies and resolves; it never certifies truth, readiness or approval. 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.

01NS-0

Constitution and principles.

Status proposed · owner trust · NXS-STD-ST-000004

RuleText
NS0-P1Open · The standards, their registries, schemas, catalogs and reference tools are published in the canonical repository under a licence recorded by counsel; participation in development is open to every community and stakeholder under GOVERNANCE.md; no standard depends on a proprietary artifact to be applied.
NS0-P2Machine-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-P3Identified · Every artifact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone.
NS0-P4Verified, 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; the claim ceiling of the consumer bounds every statement.
NS0-P5Zero trust · Authenticated is not authorized; entitled is not authorized; deny 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-P6Real-time · Standards express obligations that can be evaluated continuously against live records (observations, releases, corrections, deployments), and the standards themselves are versioned so a consumer can state exactly which version it conforms to at any instant.
NS0-P7Provenance 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-P8Honest · 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 or a badge.
NS0-P9Nexus-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-P10Names are governed · Codes are never names. Public names follow the name architecture standard; a system or component is shown by its neutral display name and its UNI, which may change with context (NS-9) while the name does not infringe anyone's mark.
NS0-P11Community-owned development · Proposals, comments, decisions and versions of every standard are themselves artifacts with UNIs; the development process is specified (NS-13) and open; authority to adopt is recorded, never assumed.
NS0-P12Fail closed · Missing evidence, missing legal state, missing policy decision or unavailable verification is a refusal with a typed reason, never a pass.

Read NS-0 in full

02NS-3

GRIx record UNIs (grammar, legacy crosswalk, allocation authority).

Status proposed · owner trust; canonical data · NXS-STD-ST-000003

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

Read NS-3 in full

03NS-3b

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

Status proposed · owner trust; canonical data · NXS-STD-SW-000005

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

Read NS-3b in full

04NS-11

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

Status proposed · owner trust · NXS-STD-ST-000007

RuleText
NS11-R1No conformance statement without an attestation; no attestation without an evaluator, a mandate, evidence references and a digest.
NS11-R2Zero trust: subject and evaluator are distinct; production evaluations run outside the subject's trust boundary.
NS11-R3Missing or unresolvable evidence is INDETERMINATE or REFUSED, never PASS (NS0-P12).
NS11-R4Attestations are append-only and supersede; monitoring records are observations with record UNIs.
NS11-R5Every displayed conformance value carries its evaluation instant and evaluator; projections never store verdicts.
NS11-R6Exports to Verifiable Credentials, in-toto or PROV-O are crosswalks; the Nexus attestation is the record of truth.

Read NS-11 in full

05Learn and apply

Where Hydrometeorological hazard is taught, worked on and run.

Risk Academy disciplines that teach Hydrometeorological hazard, 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

06Questions

Questions and answers.

Are these all the rules for hydrometeorological hazard?
They are the rules the listed standards state. NS-0's principles bind every standard; area-specific clauses, where needed, are written under NS-10 and evaluated under NS-11.
What does a rule id like NS1-R5 mean?
The standard number and the rule number inside it. Rule ids are stable so clauses, attestations and pages can cite them.
Nexus Standards

Shape the standards for hydrometeorological hazard.

Every standard here is proposed. Changes enter as proposals under NS-13; conformance is shown by attestations under NS-11; 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