Food and agriculture risk: conformance
How an implementer in food and agriculture risk demonstrates conformance: a self-assessment against the rules, clauses evaluated from evidence, attestations and a generated report. Each result names its evaluator and the time of evaluation, and each artefact is identified by a UNI (Unique Nexus Identifier).
- Nexus Standards: NS-0, NS-1, NS-3, NS-3b, NS-9, NS-10, NS-11.
- Open standards: Integrated Food Security Phase Classification Technical Manual 3.1; Codex Alimentarius standards; International Standards for Phytosanitary Measures (ISPMs); Humanitarian Exchange Language (HXL); SpatioTemporal Asset Catalog (STAC).
- Data and feeds: IPC acute food insecurity analyses; FEWS NET outlooks and data; CHIRPS quasi-global gridded precipitation; FAO GIEWS Food Price Monitoring and Analysis tool; ESA WorldCover 10 m land cover.
- Couples with: Water; Supply chain and trade risk; Conflict and security; Biological hazard.
Summary
- 01Self-assessmentagainst the rules
- 02Clause setNS-10
- 03Evidencereferenced, not embedded
- 04AttestationNS-11, named evaluator
- 05Reportgenerated from results
- Nexus Standards
- 7
- NS-0, NS-1, NS-3
- Open standards
- 5
- named, never copied
- Data and feeds
- 5
- listed for reference
- Couplings
- 4
- with other areas
Standards listed in the domains tier
The programme areas of this tier against the standards they list in the registry; the row for this area sets the initial scope of a self-assessment.
Coverage matrixA filled cell indicates that the area lists the standard in the registry. Status terms are those of the registry.
Conformance to NS-0
An implementation conforms to NS-0 when it:
- names the canonical repository and the versions of the standards it applies;
- does not fork a registry;
- runs the repository validator, or an equivalent, on the copies of the registries it uses;
- records its implementation status per standard in
registry/consumers.yamltruthfully;and - carries the honesty fields (
legalState,claimCeiling,status) on every record it publishes.
Conformance to NS-0 is a statement by the implementation, verifiable under NS-11. It is not a certification by the Secretariat or by the Global Standards Council.
Initial self-assessment for food and agriculture risk
The first rules of each applicable standard. A self-assessment is a statement by the implementer, verifiable under NS-11.
| Umthetho | Requirement | Umgangatho |
|---|---|---|
NS0-P1 | Open · 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. | NS-0 |
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. | NS-0 |
NS0-P3 | Identified · Every artefact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone. | NS-0 |
NS1-R1 | One UNI shall identify one artefact concept; versions share the UNI and differ in @VERSION. | NS-1 |
NS1-R2 | UNIs shall be allocated only through a catalogue (mint) or a record allocation authority (NS-3); they shall not be typed by hand. | NS-1 |
NS1-R3 | UNIs shall not be deleted or reused. A withdrawn artefact keeps its record (WITHDRAWN); a replaced one records supersededBy. | NS-1 |
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. | NS-9 |
NS9-R2 | Context identifiers shall be allocated by the catalogue for their SCOPE; they shall not be derived from names or typed by hand. | NS-9 |
NS9-R3 | The 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. | NS-9 |
NS10-R1 | Every 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. | NS-10 |
NS10-R2 | Subjects shall be contextual UNIs; names, labels or free text shall not bind. | NS-10 |
NS10-R3 | The 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. | NS-10 |
NS11-R1 | A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest. | NS-11 |
NS11-R2 | Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject’s trust boundary. | NS-11 |
NS11-R3 | Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12). | NS-11 |
Attestations
One attestation is recorded per clause, per subject, per evaluation (AT category, append-only). Results: PASS; FAIL; INDETERMINATE (evidence missing or unresolvable); NOT_APPLICABLE (the subject was outside the clause’s selectors at that instant); REFUSED (the evaluator lacked a mandate or the evidence was not accessible; the refusal is itself recorded). An attestation carries a canonical digest and, optionally, a signature; certifiesTruth is always false. A later attestation supersedes an earlier one for the same clause and subject, and the history is kept.
Crosswalks: an attestation can be exported as a W3C Verifiable Credential under the Verifiable Credentials Data Model 2.0 (subject: the contextual UNI; issuer: the evaluator; evidence: the refs), as an in-toto attestation (for software subjects) or as a PROV-O activity (NS-3b). The Nexus attestation remains the key and the record of truth.
Ukubeka iliso
Monitoring is continuous evaluation together with observation records. For each bound policy and context, the monitoring service records (a) the latest attestation per clause, (b) coverage (which clauses have no current attestation, and why), (c) drift (a change in a subject’s records that invalidates an attestation) and (d) the availability of evaluators and evidence sources. Monitoring records are observations with record UNIs. Dashboards and panels are projections of them and show the timestamp and the evaluator for every value; no verdict is stored.
Reporting
A conformance report for a context is generated, not written: policy by policy and clause by clause, with attestation UNIs, evidence refs, conformance levels (NS-10 section 3) and the honesty fields. Reports are catalogued artefacts (RP) and may be published (NS-8) only when their legalState allows. A report does not say "certified" or "compliant" except when it quotes an authority decision by reference.
Display of conformance statements
A context (NS-9) or artefact claims a relation to an external standard only through a clause set (NS-10) that cites that standard and is evaluated (NS-11). The claim is displayed as "implements clauses derived from <standard> (n of m with a current PASS)", with attestation UNIs. It is never displayed as "compliant with" or "certified to" unless a decision of the body entitled to say so is referenced. Where a body operates its own certification, conformance under the Nexus Standards is explicitly not that certification.
Imibuzo neempendulo.
How does a conformance report in food and agriculture risk relate to the decisions of other bodies?
What happens when evidence is missing?
Around food and agriculture risk.
Shape the standards for food and agriculture 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.
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.