Skip to content
StandarStandar risiko pangan dan pertanianKesesuaian
Risiko pangan dan pertanian

Risiko pangan dan pertanian: kesesuaian

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).

Standar risiko pangan dan pertanian
Unsur pembentuk bidang ini: Nexus Standards yang diterapkannya (ditandai), standar terbuka yang disebutkannya, serta data dan umpan yang dibacanya, kemudian bidang-bidang yang terhubung dengannya.Sumber: registri Nexus Standards: catatan area.
  • Nexus Standards: NS-0, NS-1, NS-3, NS-3b, NS-9, NS-10, NS-11.
  • Standar terbuka: Integrated Food Security Phase Classification Technical Manual 3.1; standar Codex Alimentarius; Standar Internasional untuk Tindakan Fitosanitasi (ISPM); Humanitarian Exchange Language (HXL); SpatioTemporal Asset Catalog (STAC).
  • Data dan umpan: analisis kerawanan pangan akut IPC; prospek dan data FEWS NET; presipitasi grid kuasi-global CHIRPS; alat FAO GIEWS Food Price Monitoring and Analysis; tutupan lahan ESA WorldCover 10 m.
  • Berkaitan dengan: Air; Risiko rantai pasok dan perdagangan; Konflik dan keamanan; Bahaya biologis.
01Ikhtisar

Ringkasan

  1. 01Penilaian mandiriterhadap aturan
  2. 02Set klausulNS-10
  3. 03Buktidirujuk, tidak disematkan
  4. 04AtestasiNS-11, evaluator yang disebutkan namanya
  5. 05Laporandihasilkan dari hasil
Nexus Standards
7
NS-0, NS-1, NS-3
Standar terbuka
5
disebutkan, tidak pernah disalin
Data dan umpan
5
dicantumkan sebagai rujukan
Keterkaitan
4
dengan area lain
02Cakupan

Standar yang tercantum pada tingkat domain

Bidang-bidang program pada tingkat ini terhadap standar yang dicantumkannya dalam registri; baris untuk bidang ini menetapkan cakupan awal penilaian mandiri.

Matriks cakupan · standar di sisi horizontal, area program di sisi vertikalRegistri Nexus Standards
40 dari 54 pasangan program dan standar tercantum, mencakup 6 program dan 9 standar. Sumber: register program Nexus Standards dan indeks standar.

Matriks cakupanSel yang terisi menunjukkan bahwa area mencantumkan standar tersebut dalam registri. Istilah status mengikuti registri.

03Garis dasar

Kesesuaian dengan 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.yaml truthfully; 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.

04Penilaian mandiri

Initial self-assessment for food and agriculture risk

Aturan awal dari setiap standar yang berlaku. Penilaian mandiri adalah pernyataan pelaksana, yang dapat diverifikasi berdasarkan NS-11.

AturanPersyaratanStandar
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.NS-0
NS0-P2Utamakan keterbacaan mesin · Setiap unsur normatif ada sebagai data (registri, skema, klausul) sebelum ada sebagai prosa; prosa menjelaskan, data yang mengatur. Standar tanpa bentuk mesin bukanlah Nexus Standard.NS-0
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.NS-0
NS1-R1One UNI shall identify one artefact concept; versions share the UNI and differ in @VERSION.NS-1
NS1-R2UNIs 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-R3UNIs shall not be deleted or reused. A withdrawn artefact keeps its record (WITHDRAWN); a replaced one records supersededBy.NS-1
NS9-R1Each 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-R2Context identifiers shall be allocated by the catalogue for their SCOPE; they shall not be derived from names or typed by hand.NS-9
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.NS-9
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.NS-10
NS10-R2Subjects shall be contextual UNIs; names, labels or free text shall not bind.NS-10
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.NS-10
NS11-R1A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest.NS-11
NS11-R2Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject’s trust boundary.NS-11
NS11-R3Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12).NS-11
05NS-11 · Atestasi

Atestasi

One attestation is recorded per clause, per subject, per evaluation (AT kategori, hanya-tambah). Hasil: 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 selalu 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.

06NS-11 · Pemantauan

Pemantauan

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.

07NS-11 · Pelaporan

Pelaporan

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) dan dapat diterbitkan (NS-8) hanya jika legalState allows. A report does not say "certified" or "compliant" except when it quotes an authority decision by reference.

08NS-14 · klaim

Tampilan pernyataan kesesuaian

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.

09Pertanyaan

Tanya jawab.

Bagaimana laporan kesesuaian di bidang risiko pangan dan pertanian berkaitan dengan keputusan lembaga lain?
Laporan kesesuaian menyatakan hasil klausul dan buktinya. Apabila keputusan suatu otoritas atau badan lain relevan, laporan tersebut mengutipnya melalui rujukan.
Apa yang terjadi jika bukti tidak tersedia?
Atestasi dicatat sebagai tidak dapat ditentukan, bukan sebagai lulus. Bukti, status hak, atau verifikasi yang tidak ada menghasilkan penolakan beralasan (NS0-P12).
Standar

Bentuk standar untuk risiko pangan dan pertanian.

Pemerintah, regulator, badan standar, industri, akademisi, dan komunitas diundang untuk membentuk katalog sebelum rilis resmi pertamanya yang ditargetkan pada 2030: berikan komentar pada draf, usulkan perubahan, bergabunglah dengan kelompok kerja, atau selenggarakan latihan lapangan.

Status dan penggunaan. Nexus Standards adalah standar usulan yang dikembangkan melalui proses terbuka berdasarkan NS-13 dan diterbitkan untuk penggunaan sukarela; standar ini bukan sertifikasi, akreditasi, atau persetujuan regulasi, dan adopsi tetap menjadi keputusan Global Standards Council serta, di setiap negara, Dewan Standar Nasionalnya. UNI (Unique Nexus Identifier) mengidentifikasi artefak; UNI tidak menyertifikasinya. Nama badan standar dan standarnya adalah milik pengelolanya dan hanya digunakan untuk mengidentifikasi dokumen; tidak ada teks standar eksternal yang direproduksi di sini. Nexus Standards tidak berafiliasi dengan, didukung oleh, atau disertifikasi oleh badan standar mana pun yang disebut di sini.

Lisensi: CC BY 4.0 untuk teks standar, registri, skema, dan data. Apache-2.0 untuk kode acuan. Standar eksternal dikutip dengan nama, nomor, dan tautan di bawah lisensinya sendiri. Data, pustaka, dan fon pihak ketiga mempertahankan lisensinya sendiri: lihat Pemberitahuan pihak ketiga.