Skip to content
StandardsBiodiversity and nature risk standardsStandards that apply
Biodiversity and nature risk

Biodiversity and nature risk: standards that apply

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

Standardên xetera cûrbecûrbûna jîndaran û xwezayê
What this area is built from: the Nexus Standards it applies (marked), the open standards it names and the data and feeds it reads, then the areas it couples with.Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-0, NS-1, NS-3, NS-3b, NS-5, NS-9, NS-11.
  • Open standards: Darwin Core; IUCN Global Ecosystem Typology; System of Environmental-Economic Accounting – Ecosystem Accounting; Recommendations of the Taskforce on Nature-related Financial Disclosures; Kunming-Montreal Global Biodiversity Framework; SpatioTemporal Asset Catalog (STAC).
  • Data and feeds: GBIF occurrence API and downloads; World Database on Protected and Conserved Areas; Global Forest Watch tree cover loss (Hansen/UMD) and alerts; ESA WorldCover 10 m land cover; Copernicus Land Monitoring Service products.
  • Couples with: Climate; Health; Food and agriculture; Environmental degradation hazard.
Nexus Standards
7
NS-0, NS-1, NS-3
Standardên vekirî
6
named, never copied
Data and feeds
5
listed for reference
Girêdan
4
with other areas
01NS-0

Destûr û prensîb

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

RêgezNivîs
NS0-P1Open · The standards, their registries, schemas, catalogues 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 artefact, product, account or mark 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 artefact, 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, and the supported claim level of the implementation bounds every statement it makes.
NS0-P5Zero trust · Authenticated is not authorised; entitled is not authorised; 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-P6Real-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-P7Provenance everywhere · Every artefact 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, a score 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 artefacts in another domain, and cascades are first-class.
NS0-P10Names 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-P11Community-owned development · Proposals, comments, decisions and versions of every standard are themselves artefacts with UNIs. The development process is specified (NS-13) and open, and authority to adopt is recorded, never assumed.
NS0-P12Fail 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

02NS-1

UNI û kataloga berheman (rêziman v0.2: beşên qad, sektor, herêm û jîngehê)

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

RêgezNivîs
NS1-R1One UNI shall identify one artefact concept; versions share the UNI and differ in @VERSION.
NS1-R2UNIs shall be allocated only through a catalogue (mint) or a record allocation authority (NS-3); they shall not be typed by hand.
NS1-R3UNIs shall not be deleted or reused. A withdrawn artefact keeps its record (WITHDRAWN); a replaced one records supersededBy.
NS1-R4Every record shall carry the required metadata; legalState defaults to review-required; claimCeiling stays inside the claim registry.
NS1-R5The UNI shall be embedded in the artefact itself so that machines and people can find the record (section 6).
NS1-R6A regional artefact shall carry REGION; public regional or national use still follows the geographic rules of the marks policy.
NS1-R7Codes are classification and shall not be used as product names.
NS1-R8A 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-R9A code shall not be reassigned or deleted; a retired code is deprecated with supersededBy, and identifiers that use it remain valid.
NS1-R10A PROPOSED identifier may be used and shall be shown with its status until the registry change is adopted.

Read NS-1 in full

03NS-3

UNIyên tomara xetereyê (rêzimanî, nexşeya veguhastina ji pergala kevin, desthilata veqetandinê)

Status proposed · trust, authorisation 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

04NS-3b

Profîla metadata ya daneset û berheman (STAC, DCAT, PROV-O)

Status proposed · trust, authorisation 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

05NS-5

Standarda wêne, nexşe û dîtbarkirinê (bi kîta UI/UX)

Status proposed · earth observation and digital twins; visual composition and workflows · NXS-STD-ST-000011.

RêgezNivîs
NS5-R1Every visual artefact shall carry a UNI in its metadata and in its caption.
NS5-R2Every rendered value shall trace to record UNIs and to a time of evaluation.
NS5-R3Missing, degraded and insufficient-evidence states shall be rendered explicitly; no such state shall be coerced to a value.
NS5-R4Licence-restricted or withheld features shall be counted and declared on the figure or map.
NS5-R5Every visual artefact shall carry the accessibility and cartographic declarations of section 4 that apply to it.

Read NS-5 in full

06NS-9

UNI yên çarçoveyî (belavkirin, mînak, mînakên bernameyê)

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

RêgezNivîs
NS9-R1Each deployment or programme instance shall have one context record; the concept keeps its own UNI; context.ofUni is required and shall resolve.
NS9-R2Context identifiers shall be allocated by the catalogue for their SCOPE; they shall not be derived from names or typed by hand.
NS9-R3The supported claim level, legal state and conformance evidence of a context are its own; they shall not be inherited from the concept or from another context.
NS9-R4Closing a context shall not delete it: context.validUntil is set and the status becomes WITHDRAWN an SUPERSEDED bi supersededBy.
NS9-R5Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere.

Read NS-9 in full

07NS-11

Piştrastkirin û çavdêrî (delîl, erêkirin, çavdêriya lihevhatina zero-trust)

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

RêgezNivîs
NS11-R1A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest.
NS11-R2Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject’s trust boundary.
NS11-R3Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12).
NS11-R4Attestations shall be append-only and superseded rather than changed; monitoring records shall be observations with record UNIs.
NS11-R5Every displayed conformance value shall carry its evaluation instant and its evaluator; projections shall not store verdicts.
NS11-R6Exports to Verifiable Credentials, in-toto or PROV-O are crosswalks; the Nexus attestation shall remain the record of truth.

Read NS-11 in full

08Pirs

Pirs û bersiv.

Are these all the rules for biodiversity and nature 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.
Standards

Shape the standards for biodiversity and nature 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.

Rewş û bikaranîn. Nexus Standards standardên pêşniyarkirî ne ku bi pêvajoyeke vekirî di bin NS-13 de hatine pêşxistin û ji bo bikaranîna dilxwazî hatine weşandin; ew ne belgename, ne akreditasyon û ne pejirandina rêkxistinê ne, û pejirandin biryara Encûmena Standardên Cîhanî û, li her welatî, ya Encûmena Standardên Neteweyî ya wê dimîne. UNI (Unique Nexus Identifier) berhemekê nas dike; wê belgename nake. Navên desteyên standardan û standardên wan aîdî parêzvanên wan in û tenê ji bo naskirina belgeyan têne bikaranîn; tu nivîsa standardeke derve li vir nayê dubarekirin. Nexus Standards bi tu desteya standardan a li vir hatiye binavkirin ve ne girêdayî ye, ji aliyê wê ve nayê piştgirîkirin û belgename nekiriye.

Lîsans: CC BY 4.0 ji bo nivîsa standardan, tomargeh, şema û daneyan; Apache-2.0 ji bo koda referansê. Standardên derve bi nav, hejmar û girêdanê di bin lîsansên xwe de têne jêgirtin. Dane, pirtûkxane û fontên aliyê sêyem lîsansên xwe diparêzin: binêre Agahdariyên aliyê sêyem.