Skip to content
StandardsAgriculture and land useStandards that apply
Agriculture and land use

Agriculture and land use: standards that apply

The 5 standards listed for agriculture and land use in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.

Agriculture and land use
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-3, NS-9, NS-10, NS-14.
  • Open standards: IPC Technical Manual 3.1; Codex Alimentarius standards, guidelines and codes of practice; International Standards for Phytosanitary Measures (ISPMs); Terrestrial Animal Health Code; Voluntary Guidelines on the Responsible Governance of Tenure; Recommendations of the Taskforce on Nature-related Financial Disclosures.
  • Data and feeds: FAOSTAT; FEWS NET food security outlooks and data; IPC food insecurity classifications; World Development Indicators.
  • Couples with: Food and agriculture; Water utilities and basins; Finance, insurance and capital markets; Humanitarian and civil society.
Nexus Standards
5
NS-0, NS-3, NS-9
Open standards
6
named, never copied
Data and feeds
4
listed for reference
Couplings
4
with other areas
01NS-0

Umgaqo-siseko nemigaqo

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

UmthethoText
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-3

Ii-UNI zerekhodi yomngcipheko (igrama, uthelekiso lwakudala, igunya lokwabiwa)

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

03NS-9

Ii-UNI zemeko (ukusasazwa, iimeko, iimeko zenkqubo)

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

UmthethoText
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 or SUPERSEDED ene 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

04NS-10

Imigaqo-nkqubo namagatya (izibophelelo ezifundeka ngoomatshini: inkcazo, ukubopha, uvavanyo nokunyanzeliswa)

Status proposed · trust, authorisation and assurance; integrated posture and executive synthesis · NXS-STD-ST-000006.

UmthethoText
NS10-R1Every obligation that an implementation enforces shall be a clause with a UNI; code may implement a rule, but no rule shall be enforced without a clause record that names it.
NS10-R2Subjects shall be contextual UNIs; names, labels or free text shall not bind.
NS10-R3The predicate shall be data in a declared language; evaluators shall record the engine and its version; two conformant evaluators shall reach the same result for the same clause and the same inputs.
NS10-R4External obligations shall be cited, not copied.
NS10-R5Failure effects shall be typed; refuse is the default for blocking clauses in production contexts.
NS10-R6A clause or policy whose legalState is other than APPROVED may be evaluated, but its results shall be displayed as claims under review.
NS10-R7Policies and clauses shall be append-only artefacts: withdrawal and supersession keep the record.

Read NS-10 in full

05NS-14

Ukuhambelana nokuthelekiswa nemigangatho yangaphandle

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

UmthethoText
NS14-R1The text of an external standard shall not be reproduced; it shall be cited by identifier, clause number and URL.
NS14-R2Relation 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-R4Marks of standards bodies shall not form part of a Nexus name.
NS14-R5Unverified register entries shall be displayed as unverified.

Read NS-14 in full

06Imibuzo

Imibuzo neempendulo.

Are these all the rules for agriculture and land use?
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.
Imigangatho

Shape the standards for agriculture and land use.

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.

Imeko nokusetyenziswa. I-Nexus Standards yimigangatho ecetywayo ephuhliswe ngenkqubo evulekileyo phantsi kwe-NS-13 kwaye ipapashelwe ukusetyenziswa ngokuzithandela; ayisiso isatifikethi, ugunyaziso okanye imvume yolawulo, kwaye ukwamkelwa kuhlala kusisigqibo seBhunga leMigangatho yeHlabathi kwaye, kwilizwe ngalinye, seBhunga lalo leMigangatho leSizwe. I-UNI (Unique Nexus Identifier) ichonga into; ayiyiqinisekisi. Amagama amaqumrhu emigangatho nemigangatho yawo ngawabagcini bawo kwaye asetyenziswa kuphela ukuchonga amaxwebhu; akukho mbhalo womgangatho wangaphandle uphindwe apha. I-Nexus Standards ayidibananga, ayixhaswanga okanye ayiqinisekiswanga nguwuphi na umbutho wemigangatho okhankanywe apha.

Iilayisenisi: CC BY 4.0 yombhalo wemigangatho, iirejista, iischema nedatha; Apache-2.0 yekhowudi yereferensi. Imigangatho yangaphandle icatshulwa ngegama, inombolo nekhonkco phantsi kweelayisenisi zayo. Idatha yamaqela esithathu, iilayibrari neefonti zigcina iilayisenisi zazo: bona iZaziso zamaqela esithathu.