- کۆد
NS-0- ناونیشان
- دەستوور و بنەماکان
- وەشان
- 0.1.0
- دۆخ
- پێشنیارکراو
- بەروار
- catalogue 2026-10-16 · circulated 17 October 2026
- Unique Nexus Identifier
NXS-STD-ST-000004- Responsible scope
- متمانە
- سەرچاوە
standards/NS-0-constitution-and-principles.mdat2cbe0d41b5f8
Preparatory working draft, circulated for review and comment. Not for implementation. Prepared and circulated by Saeed Valadbaygi, Chief Steward, Nexus Standards (saeed@therisk.global), 17 October 2026. Technical review area: TR-01. This document is not a Nexus Standard; it may change without notice and is not to be implemented, relied upon or cited as a Nexus Standard. Its stage is designated only by the Global Standards Council and its technical committees under NS-13. Recipients are invited to submit comments with supporting reasons, and to notify any patent rights of which they are aware. See the notice of circulation.
- دۆخ
- پێشنیارکراو
- خاوەن
- the trust and assurance system
- Applies to
- every Nexus Standard (NS-1 and later), every consumer, every site and every agent that produces or applies an artefact of the Nexus ecosystem.
NS-0 says what a Nexus Standard is, what it is for, how it is made and what it must never claim. Every other standard specialises NS-0 and may not weaken it.
Cite
NS-0, clause 1. NXS-STD-ST-000004@0.1.0. https://nexustandards.com/standards/ns-0/#nx-c-11. Purpose
The Nexus Standards are the shared, machine-readable rules by which the Nexus ecosystem (its systems, data, software, documents, visualisations, maps, models, policies, clauses, services and sites) identifies, describes, verifies, monitors and cites what it produces, across every sector, hazard, domain, region and institution it covers. They exist so that one artefact means the same thing to a person, a machine, a regulator, a researcher and a community anywhere in the ecosystem, and so that conformance can be observed rather than asserted.
Cite
NS-0, clause 2. NXS-STD-ST-000004@0.1.0. https://nexustandards.com/standards/ns-0/#nx-c-22. The nexus of standards
The world already has standards for most of what the ecosystem does: enterprise risk, continuity, security, zero trust, supply chain, climate and nature disclosure, disaster risk and early warning, financial prudence, geospatial data, provenance, identifiers and software supply chains (the landscape is recorded in research/STANDARDS_LANDSCAPE.md و registry/external-standards.yaml). Most are closed to participate in, slow to change, published as static documents and conformant only by audit.
A Nexus Standard does not replace them. It is the nexus: the layer that (a) crosswalks an artefact to every external standard it satisfies or relates to, (b) makes the obligations of those standards machine-readable as clauses, (c) verifies conformance continuously from evidence instead of periodically from attestation, and (d) lets every stakeholder take part in developing the standard itself. Where no external standard exists for a nexus concern (cross-domain cascades, real-time verification, open participation, provenance across the whole lifecycle), a Nexus Standard specifies it.
Nothing in a Nexus Standard reproduces the copyrighted text of another body's standard; it cites by identifier and URL. The names of standards bodies and their standards are their marks and are used only to refer to them.
Cite
NS-0, clause 3. NXS-STD-ST-000004@0.1.0. https://nexustandards.com/standards/ns-0/#nx-c-33. Principles (binding)
| ناسنامە | Principle | What it requires |
|---|---|---|
NS0-P1 | کراوە | The standards, their registries, schemas, catalogues and reference tools are published in the canonical repository under a licence recorded by counsel; participation in development is open to every community and stakeholder under GOVERNANCE.md; no standard depends on a proprietary artefact to be applied. |
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. |
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. |
NS0-P4 | Verified, 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; the supported claim level of the consumer bounds every statement. |
NS0-P5 | متمانەی سفر | Authenticated is not authorised; entitled is not authorised; deny 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-P6 | Real-time | Standards express obligations that can be evaluated continuously against live records (observations, releases, corrections, deployments), and the standards themselves are versioned so a consumer can state exactly which version it conforms to at any instant. |
NS0-P7 | Provenance 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-P8 | Honest | 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 or a badge. |
NS0-P9 | Nexus-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-P10 | Names are governed | Codes are never names. Public names follow the name architecture standard; a system or component is shown by its neutral display name and its UNI, which may change with context (NS-9) while the name does not infringe anyone's mark. |
NS0-P11 | Community-owned development | Proposals, comments, decisions and versions of every standard are themselves artefacts with UNIs; the development process is specified (NS-13) and open; authority to adopt is recorded, never assumed. |
NS0-P12 | Fail closed | Missing evidence, missing legal state, missing policy decision or unavailable verification is a refusal with a typed reason, never a pass. |
Cite
NS-0, clause 4. NXS-STD-ST-000004@0.1.0. https://nexustandards.com/standards/ns-0/#nx-c-44. The standard set
| ناسنامە | ستاندارد | Governs |
|---|---|---|
| NS-0 | دەستوور و بنەماکان | This document |
| NS-1 | The UNI and the artefact catalogue | Identification and cataloguing of artefacts |
| NS-2 | Citation and attribution | How a UNI is cited by people and machines |
| NS-3 | The Global Risks Index (NXS-GRX) record UNIs | Identification of records (observations, releases, indicators, boundaries, chronotopes, corrections, products, subjects) |
| NS-3b | Dataset and product metadata profile | STAC, DCAT, PROV-O crosswalks |
| NS-4 | Document template | Front matter and structure of documents and reports |
| NS-5 | Figure, map and visualisation | Visual artefacts, maps, GIS products and their captions, provenance and accessibility |
| NS-6 | Surface wiring | How APIs, rooms, passports and pages carry UNIs |
| NS-7 | Resolver | Landing pages, meta tags, sitemaps |
| NS-8 | Publication workflow | Zenodo and DOI publication with the legal gate |
| NS-9 | Contextual UNIs | Deployments and instances: a system in a region, domain, sector or jurisdiction |
| NS-10 | Policies and clauses | Machine-readable policy and clause artefacts, their obligations and enforcement in commons and command rooms |
| NS-11 | Verification and monitoring | Evidence, attestations, conformance observation and reporting, zero-trust verification services |
| NS-12 | Software, model and AI/ML artefacts | Software supply-chain, model cards, dataset sheets and AI governance crosswalks |
| NS-13 | Standards development process | How standards are proposed, debated, versioned and adopted openly |
| NS-14 | پابەندبوون و هاوتاکردن لەگەڵ ستانداردی دەرەکی | How an artefact claims and evidences relation to external standards |
Ids above NS-3b are allocated here and are OPEN until drafted; standards/INDEX.md carries the live status.
Cite
NS-0, clause 5. NXS-STD-ST-000004@0.1.0. https://nexustandards.com/standards/ns-0/#nx-c-55. Precedence
Applicable law and executed contracts → the consumer's legal and IP constitution → NS-0 → the other Nexus Standards → the consumer's own directives and policies. A conflict is a blocking record (DIRECTIVE_CONFLICT) in the consumer, never code written through.
Cite
NS-0, clause 6. NXS-STD-ST-000004@0.1.0. https://nexustandards.com/standards/ns-0/#nx-c-66. Conformance to NS-0
A consumer conforms to NS-0 when it (1) names the canonical repository and the versions of the standards it applies, (2) never forks a registry, (3) runs the repository validator or an equivalent on its vendored copies, (4) records its implementation status per standard in registry/consumers.yaml honestly, and (5) carries the honesty fields on every record it publishes. Conformance to NS-0 is a statement by the consumer, verifiable under NS-11; it is not a certification by the trust and assurance system.
Change history
Versions from the catalogue; entries from the changelog that name this document.
| وەشان | بەروار | تێبینی |
|---|---|---|
0.1.0 | 16 October 2026 | current version in the catalogue |
- 0.2.0 – 2026-10-16 NS-0 constitution; NS-2, NS-4, NS-5, NS-9, NS-10, NS-11, NS-12, NS-13, NS-14 drafted (PROPOSED). Categories DP, PR, CL, AT; record schema v1.1 with the NS-9 context; clause, policy, attestation and proposal schemas.