Skip to content
ViwangoNS-9Inapendekezwa
NS-9

NS-9: UNI za muktadha (utekelezaji, nakala, nakala za programu)

NS-9 is a proposed Nexus Standard; the artefacts it governs are identified by UNIs (Unique Nexus Identifier). A system, component, product or service exists once as a concept and many times in context: the early-warning system deployed for Kenya's water sector, the same system for a Sahel food-security programme, a data product published for an African region, a command room instance for one host city. NS-9 gives each context its own UNI, so that a page, a passport, a report, a policy, a clause or a monitoring record can name exactly which deployment it is about, while the concept keeps one UNI and the public name never changes with context and never infringes a mark.

NS-9 in the catalogue
The standards NS-9 depends on and those that cite it, then its sections with one mark for each numbered requirement.Source: NS-9-contextual-uni.md; the Nexus Standards registry.
  • NS-9 depends on: NS-1, NS-3, NS-10, NS-11, NS-14, NS-16.
  • NS-9 is cited by: NS-0, NS-1, NS-10, NS-11, NS-12, NS-14, NS-15, NS-16.
  • Section 1, Grammar (unchanged): no numbered requirement.
  • Section 2, The context record: no numbered requirement.
  • Section 3, Resolution and display: no numbered requirement.
  • Section 4, Policies, clauses and monitoring: no numbered requirement.
  • Section 5, Rules: R1, R2, R3, R4, R5.
  • Section 6, Adoption: no numbered requirement.
01Muhtasari

Summary

NS-9record
  1. Haliinapendekezwa
  2. Responsible scopetrust
  3. Rules stated5
  4. Programme areas40
  5. Source filesrepository

Nexus Standards · proposed

Requirements
5
numbered rules
Sections
6
in the text
Depends on
6
NS-1, NS-3, NS-10
Cited by
8
Nexus Standards
02The standard

NS-9: the standard

The text of NS-9 as it stands in the canonical repository (commit 2cbe0d41b5f8): 6 clauses, 0 sub-clauses and 5 identified requirements, each with its anchor and citation.

Code
NS-9
Title
UNI za kimuktadha (utekelezaji, matukio, matukio ya programu)
Version
0.1.0
Hali
INAYOPENDEKEZWA
Date
catalogue 2026-10-16 · circulated 17 October 2026
Unique Nexus Identifier
NXS-STD-ST-000005
Responsible scope
trust
Chanzo
standards/NS-9-contextual-uni.md at 2cbe0d41b5f8

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

Hali
INAYOPENDEKEZWA
Owner
the trust and assurance system

A system, component, product or service exists once as a concept and many times in context: the early-warning system deployed for Kenya's water sector, the same system for a Sahel food-security programme, a data product published for an African region, a command room instance for one host city. NS-9 gives each context its own UNI, so that a page, a passport, a report, a policy, a clause or a monitoring record can name exactly which deployment it is about, while the concept keeps one UNI and the public name never changes with context and never infringes a mark.

CiteNS-9, clause 1. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-1

1. Grammar (unchanged)

NS-9 adds no segment to the NS-1 grammar. A contextual UNI is an ordinary NS-1 identifier whose category is a context category and whose REGION segment carries the geography:

NXS-<SCOPE>-DP[-<REGION>]-<SERIAL>        a deployment or instance of a system or component NXS-<SCOPE>-PR[-<REGION>]-<SERIAL>        a programme or engagement instance (a pathway run in a context) NXS-EWS-DP-KEN-000001        deployment 1 of the early-warning system in Kenya NXS-EWS-DP-M011-000003       deployment 3 of the early-warning system in Western Africa (UN M49 011) NXS-GRX-DP-000002            a global deployment of the data system (no region) NXS-GCR-PR-COL-000001        GCRI programme instance 1 in Colombia

With NS-1 grammar v0.2 a contextual UNI also carries the domain, sector and environment of the context as segments, so the identifier alone names the context: NXS-GRX-DP-WAT-WUT-CAN-PRD-000001 is production deployment 1 of the data system for Canadian water utilities, and its context name NXS-GRX-WAT-WUT-CAN-PRD (the identifier without CAT and SERIAL) is the name every page, article, dataset and dashboard about that deployment carries (NS-16). The context object below stays the record of truth: finer jurisdictions, several domains or sectors, the host and the validity window live there, and the segments in the identifier are the primary ones.

DP (deployment or instance) and PR (programme instance) are new artefact categories in registry/nexus-standards.yaml#categories (append-only, NS1-R3). Zenodo and DataCite mappings are other/Other: a deployment is catalogued, not deposited, unless its evidence is published separately.

CiteNS-9, clause 2. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-2

2. The context record

A contextual record is an NS-1 record (schema v1.1) with a context object:

NyanjaMeaning
context.ofUniThe concept the context instantiates: the system, component, product or programme UNI (required). The record also carries relatedIdentifiers[IsPartOf, <ofUni>].
context.domainsNexus domains from registry/domains.yaml (water, energy, food, health, biodiversity, climate and the others the ecosystem covers), one or more.
context.sectorsSectors from registry/sectors.yaml (one or more).
context.jurisdictionsISO 3166-1 alpha-2 country codes and, where relevant, subdivision codes (ISO 3166-2) or INTL for international.
context.hostRefThe institution, host city, tenant or programme that operates the context (entity reference from the consumer's legal registers).
context.environmentproduction, staging, lab or fixture; the environment never raises a supported claim level.
context.validFrom / context.validUntilWhen the context is live; a closed context keeps its record.
context.conformsToThe Nexus Standards and external standards (registry/external-standards.yaml ids) this context claims and evidences (NS-11, NS-14).

REGION in the identifier is the primary geography (one country or one M49 region); finer or multiple jurisdictions go in context.jurisdictions. The identifier is allocated by the consumer's catalogue for the SCOPE (NS1-R2); the catalogue is append-only.

CiteNS-9, clause 3. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-3

3. Resolution and display

  • /uni/NXS-EWS-DP-KEN-000001 resolves to the deployment's landing page: the concept it instantiates, its domains, sectors, jurisdictions, host, environment, conformance claims with evidence state, and the records (NS-3) it produces.
  • The display name is the concept's neutral public name plus a context phrase from the name architecture standard, for example "Early Warning · Kenya · Water". The context phrase is derived from the record, never hand-typed, and never composes a geographic term with a protected mark in a way the name architecture forbids (NS0-P10).
  • Every page, passport, report and monitoring record about the deployment carries the contextual UNI (NS1-R5), and a X-Nexus-UNI header or nexus-uni meta tag names it.
CiteNS-9, clause 4. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-4

4. Policies, clauses and monitoring

A policy or clause (NS-10) binds to a contextual UNI, not to a name: "clause C applies to NXS-EWS-DP-KEN-000001". Verification and monitoring services (NS-11) observe a contextual UNI and record conformance per context. A command room or commons instance is itself a context (DP under the STU or CMD scope) so that what it enforces is identifiable.

CiteNS-9, clause 5. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-5

5. Rules

RuleText
NS9-R1One context record per deployment or programme instance; the concept keeps its own UNI; context.ofUni is required and must resolve.
NS9-R2Context identifiers are allocated by the catalogue for their SCOPE, never derived from names or typed by hand.
NS9-R3A context's supported claim level, legal state and conformance evidence are its own; they are never inherited from the concept or from another context.
NS9-R4Closing a context never deletes it; context.validUntil is set and the status becomes WITHDRAWN or SUPERSEDED chenye supersededBy.
NS9-R5Display names in context follow the name architecture standard; the UNI, not the name, is the key everywhere.
CiteNS-9, clause 6. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-6

6. Adoption

Domains and sectors registers (registry/domains.yaml, registry/sectors.yaml) are populated from the ecosystem coverage study (research/ECOSYSTEM_COVERAGE.md). First contexts to catalogue: the foundry's tenant deployments and command rooms, the Global Risks Forum (GRF) host cities and national hubs, the Global Centre for Risk and Innovation (GCRI Canada) programmes per country, the Global Risks Alliance (GRA) capital-readiness engagements. Each consumer records its contexts in its own catalogue under its scopes.

Change history

Versions from the catalogue; entries from the changelog that name this document.

VersionDateNote
0.1.016 October 2026current 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.
03Utafiti

Research, sources and files

Recent research on NS-9

Recent peer-reviewed articles, preprints, datasets and reports on the subject of this standard, retrieved at the time of reading from open scholarly metadata services (OpenAlex, Crossref, DataCite, Zenodo, arXiv, Europe PMC, OpenAIRE Graph) with search terms composed from the registry. Each work is listed with its authors, venue, year, type, open-access status and licence, and links to its DOI or landing page. Sources not yet enabled for live display on this site are listed for reference and are not queried.

Search termspersistent identifier; digital twin; provenance of deployments; contextual metadata; DataCite Metadata Schema; ORCID iDcombined with: identifier; provenance; context; deployment; instanceDerived from the subject of the standard and its rules, and the external standards of its crosswalk domains.

  • OpenAlexlisted for reference; not queried
  • Crossreflisted for reference; not queried
  • DataCitelisted for reference; not queried
  • Zenodolisted for reference; not queried
  • arXivlisted for reference; not queried
  • Europe PMClisted for reference; not queried
  • OpenAIRE Graphlisted for reference; not queried

No source is enabled for live display on this site yet: the sources are listed for reference and none is queried. Once the publisher of record enables a source after its terms are reviewed, recent works are listed here. Metadata and links only: title, authors, venue, year, type, open-access status and licence as each source records them; works are listed for orientation, not reviewed or endorsed.

04In practice

Where it applies and how it is developed

How it is developed and how to take part, the standard as a process, and the programme areas that list it.

How NS-9 is developed, and how to take part

NS-9 is developed in the open under NS-13 (the stages and gates of NS-13). Working groups draft, councils decide the reserved matters, and anyone may propose a change, comment, submit an implementation report, object or appeal, without membership or fee.

05Viwango vya nje

Relation to external standards

NS-9 relates to external standards by identifier, clause number and URL (NS14-R1), and directs the reader to the issuing body.

06Katika mtandao mzima

Learning, the network and questions

Risk Academy courses and disciplines

1 course and 1 discipline of Risk Academy (risksacademy.com) that teach the knowledge and methods of NS-9. Each course lists its level, stream and learning hours.

Kozi

Taaluma

The correspondence between courses, disciplines and the Nexus Standards is maintained with Risk Academy and is subject to its academic review.

RipotiChangia

Changia ushahidi kutoka ukurasa huu.

Reports ni chapisho la robo mwaka la Muungano. Unachojua kuhusu mada hii kinaweza kuwa ushahidi, mfano au marekebisho katika toleo lijalo, kikitajwa kwa jina lako na kuchapishwa chini ya CC BY 4.0 pale kinapokuwa kazi yako mwenyewe.

Nexus Standards
Viwango

Shiriki katika viwango.

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.

Hali na matumizi. Nexus Standards ni viwango vinavyopendekezwa vilivyoandaliwa kupitia mchakato wazi chini ya NS-13 na kuchapishwa kwa matumizi ya hiari; si uthibitisho, uidhinishaji wala idhini ya kidhibiti, na upitishaji unabaki kuwa uamuzi wa Baraza la Viwango la Dunia na, katika kila nchi, wa Baraza lake la Viwango la Kitaifa. UNI (Unique Nexus Identifier) hutambua kitu; haikithibitishi. Majina ya vyombo vya viwango na viwango vyao ni mali ya wasimamizi wake na yanatumika tu kutambua nyaraka; hakuna maandishi ya kiwango cha nje yanayonakiliwa hapa. Nexus Standards haihusiani na, haiidhinishwi wala haithibitishwi na chombo chochote cha viwango kilichotajwa hapa.

Leseni: CC BY 4.0 kwa matini ya viwango, rejista, miundo na data; Apache-2.0 kwa msimbo wa marejeo. Viwango vya nje hunukuliwa kwa jina, namba na kiungo chini ya leseni zake vyenyewe. Data, maktaba na fonti za wahusika wengine huhifadhi leseni zake: tazama Notisi za wahusika wengine.