Humanitarian and civil society: conformance
How an implementer in humanitarian and civil society 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-3, NS-9, NS-10, NS-11.
- Open standards: Sphere Handbook (2018); Core Humanitarian Standard on Quality and Accountability (2024); Humanitarian Exchange Language (HXL) 1.1; IATI Standard 2.03; IASC Operational Guidance on Data Responsibility in Humanitarian Action; IPC Technical Manual 3.1; Common Alerting Protocol 1.2.
- Data and feeds: Humanitarian Data Exchange; Financial Tracking Service; IATI Datastore; IPC food insecurity classifications; Refugee Data Finder; INFORM Risk Index.
- Couples with: Agriculture and land use; Health systems; International organisations and multilaterals; Defence and civil protection.
Summary
- 01Self-assessmentagainst the rules
- 02Clause setNS-10
- 03Evidencereferenced, not embedded
- 04AttestationNS-11, named evaluator
- 05Reportgenerated from results
- Nexus Standards
- 5
- NS-0, NS-3, NS-9
- Open standards
- 7
- named, never copied
- Data and feeds
- 6
- listed for reference
- Couplings
- 4
- with other areas
Standards listed in the sectors and industries 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 humanitarian and civil society
The first rules of each applicable standard. A self-assessment is a statement by the implementer, verifiable under NS-11.
| விதி | Requirement | தரநிலை |
|---|---|---|
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 |
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.
கண்காணிப்பு
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.
கேள்விகளும் பதில்களும்.
How does a conformance report in humanitarian and civil society relate to the decisions of other bodies?
What happens when evidence is missing?
Around humanitarian and civil society.
Shape the standards for humanitarian and civil society.
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.
நிலையும் பயன்பாடும். Nexus Standards என்பவை NS-13-இன் கீழ் திறந்த செயல்முறையின் மூலம் உருவாக்கப்பட்டு, தன்னார்வப் பயன்பாட்டுக்காக வெளியிடப்பட்ட முன்மொழியப்பட்ட தரநிலைகள்; அவை சான்றளிப்போ, அங்கீகாரமோ, ஒழுங்குமுறை ஒப்புதலோ அல்ல; ஏற்பு உலகளாவிய தரநிலை மன்றத்தின் முடிவாகவும், ஒவ்வொரு நாட்டிலும் அதன் தேசியத் தரநிலை மன்றத்தின் முடிவாகவும் இருக்கிறது. ஒரு UNI (Unique Nexus Identifier) ஒரு கலைப்பொருளை அடையாளம் காண்கிறது; அதைச் சான்றளிப்பதில்லை. தரநிலை அமைப்புகளின் பெயர்களும் அவற்றின் தரநிலைகளும் அவற்றின் பொறுப்பாளர்களுக்கு உரியவை, ஆவணங்களை அடையாளம் காண மட்டுமே பயன்படுத்தப்படுகின்றன; எந்த வெளிப்புறத் தரநிலையின் உரையும் இங்கே மீண்டும் வழங்கப்படவில்லை. Nexus Standards இங்கே பெயரிடப்பட்ட எந்தத் தரநிலை அமைப்புடனும் இணைக்கப்படவில்லை, அவற்றால் ஆதரிக்கப்படவோ சான்றளிக்கப்படவோ இல்லை.
உரிமங்கள்: தரநிலை உரை, பதிவேடுகள், திட்டவரைவுகள் மற்றும் தரவுக்கு CC BY 4.0; குறிப்புக் குறியீட்டுக்கு Apache-2.0. வெளிப்புறத் தரநிலைகள் அவற்றின் சொந்த உரிமங்களின் கீழ் பெயர், எண் மற்றும் இணைப்பால் மேற்கோள் காட்டப்படுகின்றன. மூன்றாம் தரப்புத் தரவு, நூலகங்கள் மற்றும் எழுத்துருக்கள் அவற்றின் சொந்த உரிமங்களைத் தக்க வைக்கின்றன: மூன்றாம் தரப்பு அறிவிப்புகளைப் பாருங்கள்.