Skip to content

NXS · Foundations

Inside NS-10: policies and clauses in water and food systems

What the proposed NS-10 would mean for drinking-water, food safety and food security obligations: machine-readable clauses that cite their source, bound to named deployments and evaluated, never prose assurances.

As of
3 November 2026
Bacaan
10 minutes
Bukti
14 sources, cited in order
Status
Proposed standard
Kode
NS-10 · Policies and clauses
NEXUS TWIN · WF-1 · COLUMNSSEED 85b53914NXS-M03.APPLIES.NS-10xyzSCHEMATIC · COLUMNSST-01 · 0.343 0.661ST-02 · 0.319 0.656ST-03 · 0.360 0.656
WF-1 · columns Schematic wireframe twin (columns, crop water and yield). An illustration, not data.

Status and scope

A proposed standard. It is not adopted, approved or certified by any authority.

Kode
NS-10 · Policies and clauses
Lingkup
Machine-readable obligations, here those of water and food systems, bound to deployments and evaluated.
Berlaku untuk
Drinking-water, food safety and food security obligations of water and food deployments.
  1. 2 The clause
  2. 3 The policy
  3. 4 Milik bersama dan ruang komando
  4. 5 Aturan

01What NS-10 policies and clauses mean for water and food systems

What NS-10 policies and clauses mean for water and food systems

NS-10 policies and clauses is the proposed Nexus Standard NS-10 that makes obligations machine-readable 1. A clause is one obligation. A policy is an ordered, versioned set of weighted clauses with an owner, an adoption decision and conformance levels 1.

The Water and Food Systems programme lists NS-10 in all six of its areas, from water risk standards to FAO and food security 2. This explainer shows how NS-10 would apply to the obligations those areas deal with. It builds on the programme's standards landscape.

NS-10 is a preparatory working draft, version 0.1.0, circulated for comment on 17 October 2026 and not for implementation 1.

02Why water and food obligations should be checkable

Why water and food obligations should be checkable

Water and food systems run on obligations: water suppliers must meet national quality standards, food businesses must follow food safety rules, and programmes commit to monitor and report. Most of these live in prose. Checking them means reading documents and comparing them with data by hand, often long after the fact.

NS-10 starts from a different premise. Every obligation enforced anywhere in the ecosystem is a clause with an identifier, and no rule is hidden in code without a clause record (rule NS10-R1) 1. For a water utility or a food security programme, that would mean every check it runs has a name, a source and an owner, and each result can be traced to the obligation it serves.

03Anatomy of a water or food clause

Anatomy of a water or food clause

Clause 2 of NS-10 sets the fields of a clause 1. The modality uses the RFC 2119 key words, such as MUST, SHOULD and MAY 1. RFC 2119 defines these words to signify requirement levels in a specification 4. The subjects are selectors that resolve to contextual identifiers, such as one deployment of a monitoring system in one country; a name is never a selector 1.

The condition is a predicate written as data in a declared language, over named inputs with a time window 1. The evaluation mode may be continuous, on each record, scheduled or on demand, and the evaluator is never the subject itself 1. The evidence field says which kinds of evidence satisfy the clause. The onFailure field names the effect, from recording or warning to refusing an action or escalating to a role 1. The derivedFrom field cites the external standard and clause the obligation implements 1.

Fig. 01A water or food clause, field by field

A water or food clause, field by field Six stacked layers: modality, subjects as deployments, condition over records, evaluation by an independent evaluator, evidence such as monitoring results, and a failure effect. 01ModalityMUST, SHOULD or MAY02SubjectsA named deployment03ConditionTest over records04EvaluasiNever by the subject05BuktiMonitoring results06Failure effectTyped in advance
Fields as published in NS-10 clause 2 1; the example is an illustration.1Sources: Nexus Standards, NS-10 clause 2. Figure CC BY 4.0. As of 3 November 2026.
Figure 1 in words

Six layers. Modality: MUST, SHOULD or MAY. Subjects: the contextual UNI of a supply system or monitoring deployment. Condition, highlighted: a test over named records within a time window. Evaluation: scheduled or continuous, never by the subject. Evidence: the monitoring results that count. Failure effect: record, warn, lower the claim level, refuse or escalate to a role.

04Drinking-water obligations as clauses

Drinking-water obligations as clauses

WHO's Guidelines for drinking-water quality, fourth edition with the first and second addenda, published on 21 March 2022, organise safety around health-based targets, catchment-to-consumer water safety plans and independent surveillance 5. They form the basis on which countries set national regulations and standards 5.

Under NS-10 a national requirement derived from those guidelines would become a clause whose derivedFrom field cites both the national rule and the WHO guidelines by identifier and URL, without reproducing their text 1. The subject would be the contextual UNI of a supply system or a monitoring deployment 1,3. The condition would test the relevant records, and the evidence field would name the monitoring results that count 1.

Access targets work the same way. The JMP defines a safely managed drinking water service as one from an improved source that is accessible on premises, available when needed and free from contamination 6. SDG indicator 6.1.1 tracks the proportion of population using safely managed drinking water services 7. In each of these examples the draft standard adds no new water or food rule, and it is not for implementation. A reader should treat the examples as a way to understand the draft, not as guidance on any regulatory duty. Where a regulator, a utility or a food authority already publishes a requirement, that publication remains the place to read it. The draft would only describe how such a requirement could be recorded, with its source named, so that a later reader can see where it came from and how it was meant to be evaluated. It would only record, in a testable form, an obligation that an issuer has already published, and name the source it comes from.

05Food safety and food security obligations

Food safety and food security obligations

The Codex Alimentarius website names the Joint FAO/WHO Food Standards Programme in its footer contact for the Secretariat 8.

Food security commitments are often about monitoring and response rather than limits. A programme might commit to report the prevalence of undernourishment and moderate or severe food insecurity, the SDG 2.1 indicators 9. It might also commit to act when a crisis classification crosses a threshold. The Famine Early Warning Systems Network defines severity by the degree to which households can meet basic survival needs and maintain normal livelihoods 10. Under NS-10, the threshold and the response would be a clause with its evaluation mode and its failure effect stated in advance 1.

Fig. 02Obligations by domain

Obligations by domain Three columns: drinking water (WHO guideline values, JMP definitions, SDG 6.1.1); food safety (Codex Alimentarius); food security (SDG 2.1 indicators). Drinking waterWHO guideline valuesJMP service definitionsSDG 6.1.1 indicatorFood safetyCodex AlimentariusKetahanan panganSDG 2.1 indicators
Sources as published by each issuer 5,6,7,8,9.5,6,7,8,9Sources: WHO; JMP; Codex; UNSD. Figure CC BY 4.0. As of 3 November 2026.
Figure 2 in words

Column 1, drinking water: WHO guideline values; JMP service definitions; the SDG 6.1.1 indicator. Column 2, food safety: Codex Alimentarius. Column 3, food security: the SDG 2.1 indicators.

06Clauses read records, not documents

Clauses read records, not documents

A clause's condition is evaluated over named inputs, each a record kind or artefact category with a selector and a time window 1. In water and food systems those inputs would be the records named under NS-3: observation facts such as monitoring results, source releases such as a national data release, and indicator definitions 11.

The evidence that satisfies a clause includes record references in the form of a record UNI at its record version, receipts, digests, signed attestations, observations, external reports and human decisions 1. A drinking-water clause would therefore point to the exact monitoring results it was evaluated on, at their versions, rather than to a summary table that might later change.

This is what turns a clause from a statement of intent into something checkable. When a result is later revised, the attestation that relied on the earlier version still names it, and a new evaluation can be run against the revision. Under NS-11, evidence that no longer resolves makes an attestation indeterminate, never a pass 12.

07Weights and failure effects

Weights and failure effects

A policy gives each clause a weight: blocking, required, recommended or informative 1. Rule NS10-R5 says failure effects are typed, and that refuse is the default for blocking clauses in production contexts 1.

In water and food terms, a blocking clause might stop a dataset from being published as complete when a required quality check has not run. A required clause might lower the claim level of a monitoring deployment until missing reports arrive. A recommended clause might only warn. Escalation always goes to a role or mandate, never to a person's name 1. These examples illustrate the mechanism; NS-10 does not itself set any water or food thresholds.

08Conformance levels for a water or food deployment

Conformance levels for a water or food deployment

NS-10 fixes four conformance levels 1. At the self-declared level, the subject states conformance and no evaluation has run. At the verified level, every blocking and required clause has a current pass attestation from a mandated evaluator under NS-11 1,12. The attested level adds signed attestations and published evidence digests. The recognised level adds a recorded authority decision, and the authority, not the policy, confers recognition 1.

For a utility or a national monitoring programme, these levels would make plain how much of its stated conformance has actually been checked. They are not legal findings, and NS-10 says no level amounts to legal compliance unless the issuing authority's own decision says so 1.

09Binding policies to basins and countries

Binding policies to basins and countries

Clause 4 of NS-10 sets a cycle of define, bind, evaluate, enforce and report 1. Binding attaches a policy to a context, such as a system deployment, a programme, a tenant or a jurisdiction, and the binding is itself a record with an authority decision 1.

Under NS-9, each such context has its own identifier, and its claim level and evidence are never inherited from the concept or another context 3. The programme's example geography, the Ganges and Brahmaputra basin, spans more than one country 2. A policy bound to one national deployment there would be evaluated on that deployment's records alone.

Fig. 03Four conformance levels for a deployment

Four conformance levels for a deployment A ladder of four levels: self-declared, verified with current pass attestations, attested with signed evidence, and recognised by a recorded authority decision. 01Self-declaredA claim only02TerverifikasiCurrent pass attestations03AttestedSigned evidence04RecognisedKeputusan otoritas
Levels as published in NS-10 clause 3 1.1Sources: Nexus Standards, NS-10 clause 3. Figure CC BY 4.0. As of 3 November 2026.
Figure 3 in words

Four rising steps. Self-declared: the deployment states conformance; nothing has been evaluated. Verified, highlighted: every blocking and required clause has a current pass attestation. Attested: signed attestations and published evidence digests. Recognised: a recorded authority decision.

10Crisis reporting as an example of obligations at scale

Crisis reporting as an example of obligations at scale

The Famine Early Warning Systems Network describes itself as an early-warning provider on food insecurity 10. A programme that contributes to a monitoring system carries implicit obligations: to submit data on time, in a known format, with a known method. NS-10 would make such obligations explicit as clauses bound to the contributing deployment 1. Reporting under clause 4 is a projection of attestations, never a stored verdict, and it carries the evaluation time and evaluator 1. This is an illustration of the mechanism, not a description of how any monitoring system works.

11Differences and open questions

Differences and open questions

Three points are worth noting for water and food implementers. First, many water and food obligations are national, and NS-10 cites external obligations but does not yet say how a clause should record which national version of an international guideline applies 1. Second, NS-10 allows five predicate languages, and water and food data often need spatial and seasonal conditions that the text does not address 1. Third, the programme lists NS-10 in every area but its area profiles do not yet publish any clauses 2.

Relations to external instruments would be stated under NS-14 13. Changes to NS-10 itself go through an NS-13 proposal 14.

12Who this serves and how to take part

Who this serves and how to take part

NS-10 in water and food systems would serve utility operators, food safety authorities, programme managers, auditors and funders. It would give each obligation an address, so a question about whether it is met has a record to point to 1.

Comments go through the contact form, and changes follow Develop a standard. The standards are published by The Global Centre for Risk and Innovation (GCRI) as Secretariat. The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) take part as stakeholders like any other.

13Instruments related to this explainer

The table lists external instruments whose obligations NS-10 clauses would cite, as published on 3 November 2026. Each is maintained by its own issuer.

InstrumenKind of obligationEdisi
WHO drinking-water guidelinesBasis for national water quality standards4th ed. with addenda, 21 March 2022 5
JMP drinking waterService level definitionsOnline estimates 6
SDG 6.1 metadataReporting on safely managed waterMetadata repository 7
Codex AlimentariusFood safety standards programmeProgramme website 8
SDG 2.1 metadataReporting on undernourishment and food insecurityMetadata repository 9
RFC 2119 (IETF)Modality key words in clausesBCP 14, March 1997 4
Water and food instruments that NS-10 clauses would cite, as of 3 November 2026.

What this page does not claim: NS-10 and the Water and Food Systems programme are proposed, and NS-10 is a preparatory working draft not for implementation; no Nexus Standard has been adopted by the Global Standards Council or any National Standards Council. The clauses described are illustrations of how NS-10 would apply; none has been published, and NS-10 sets no water or food thresholds. WHO, UNICEF, FAO, the Codex Alimentarius Commission, the UN Statistics Division, FSIN, the Famine Early Warning Systems Network and the IETF maintain their own instruments; Nexus Standards has no affiliation with any of them.

Pertanyaan

Pertanyaan dan jawaban

Would NS-10 set drinking-water or food safety limits?

No. Limits stay with WHO, Codex and national authorities. NS-10 would only express an obligation as a clause that cites its source and can be evaluated.

What does a water or food clause contain?

Its modality, the deployments it binds, a condition written as data, how and by whom it is evaluated, the evidence that counts and the effect of failure.

Can a deployment rely on another country's evidence?

No. Policies bind to a named deployment, and its evidence and claim level are its own, never inherited from another context.

Are NS-10 conformance levels legal findings?

No. They show how much of a stated conformance has been checked. Only an issuing authority's own decision can make a legal statement.

What is the status of NS-10 for water and food systems?

Proposed. NS-10 is a preparatory working draft not for implementation, and the programme is in preparation.

Ketentuan

Glosarium

Klausul
One machine-readable obligation with subjects, a condition, an evaluation mode, evidence and a failure effect.
Kebijakan
A versioned set of weighted clauses with an owner and an adoption decision.
Water safety plan
A catchment-to-consumer plan for identifying and managing risks to a drinking-water supply.
Binding
The recorded attachment of a policy to a deployment, programme or jurisdiction.
Tingkat kesesuaian
One of four fixed levels, from self-declared to recognised, showing how far conformance has been checked.

Comment on this draft

Comments are taken clause by clause, with the exact text you propose and your evidence, through the comment form on this site.

Sumber

References

14 sources, numbered in the order they are first cited
  1. Nexus Standards (2026-10-16). NS-10: Policies and clauses (proposed). nexustandards.com. Accessed 2026-11-03.
  2. Nexus Standards (2026-10-17). Water and Food Systems: a programme of the Nexus Standards. nexustandards.com. Accessed 2026-11-03.
  3. Nexus Standards (2026-10-16). NS-9: Contextual UNIs (proposed). nexustandards.com. Accessed 2026-11-03.
  4. Internet Engineering Task Force (IETF) (1997-03). RFC 2119: Key words for use in RFCs to Indicate Requirement Levels. www.rfc-editor.org. Accessed 2026-11-03.
  5. World Health Organization (WHO) (2022-03-21). Guidelines for drinking-water quality: fourth edition incorporating the first and second addenda. www.who.int. Accessed 2026-11-03.
  6. WHO/UNICEF Joint Monitoring Programme for Water Supply, Sanitation and Hygiene (JMP) (2026-11-03). Drinking water: JMP monitoring. washdata.org. Accessed 2026-11-03.
  7. United Nations Statistics Division (2026-11-03). SDG indicator metadata, target 6.1. unstats.un.org. Accessed 2026-11-03.
  8. FAO/WHO Codex Alimentarius Commission (2026-11-03). Codex Alimentarius: international food standards. www.fao.org. Accessed 2026-11-03.
  9. United Nations Statistics Division (2026-11-03). SDG indicator metadata, target 2.1. unstats.un.org. Accessed 2026-11-03.
  10. FEWS NET (2026-11-03). Famine Early Warning Systems Network. fews.net. Accessed 2026-11-03.
  11. Nexus Standards (2026-10-16). NS-3: Risk record UNIs (proposed). nexustandards.com. Accessed 2026-11-03.
  12. Nexus Standards (2026-10-16). NS-11: Verification and monitoring (proposed). nexustandards.com. Accessed 2026-11-03.
  13. Nexus Standards (2026-10-16). NS-14: Conformance and crosswalk to external standards (proposed). nexustandards.com. Accessed 2026-11-03.
  14. Nexus Standards (2026-10-16). NS-13: Standards development process (proposed). nexustandards.com. Accessed 2026-11-03.

Catatan

Editorial record

Facts as of 3 November 2026. The NS-10 text, the programme page and every external instrument were checked at the issuer that day. This page is reviewed at least every 180 days and whenever NS-10 or the programme changes version or status. Text, visuals and data on this page are licensed CC BY 4.0.

Published by the Standards desk, Nexus Standards. Drafted with AI assistance under the Nexus editorial constitution. To report an error, use the corrections page; corrections are dated and listed here.

Cite this article

Standards desk, Nexus Standards (2026, November 3). NS-10 policies and clauses in water and food systems. Water and Food Systems. https://nexustandards.com/water-food/ns-10-water-and-food-systems/

Republish

Republish or translate this article free of charge, in print or online, under CC BY 4.0: keep the byline and Water and Food Systems, link to the original and note any change. Figures, maps and twins made by the institutions carry the same licence; third-party data keeps its own credit line.

Attribution to paste
<p>Inside NS-10: policies and clauses in water and food systems — Standards desk, Nexus Standards, Water and Food Systems. First published 3 November 2026 at <a href="https://nexustandards.com/water-food/ns-10-water-and-food-systems/">https://nexustandards.com/water-food/ns-10-water-and-food-systems/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>

Related across the Consortium

Proporsi

EmailLinkedInBlueskyMastodon