Skip to content
ستانداردئامادەیی و پەسەندکردنڕێڕەوەکانی ئامادەیی
Area · proposed

ڕێڕەوی جێبەجێکردنی سەروەرانە

The sovereign deployment pathway area of the Readiness and Adoption programme explains how a government or institution operates the Nexus reference implementation on its own infrastructure: data residency, air-gapped operation, zero-trust identity, signed builds with SBOMs and provenance attestations, and how locally held records stay verifiable and interoperable with the global registry and resolver without surrendering control. Each artefact of the area carries a UNI (Unique Nexus Identifier).

ڕێڕەوی جێبەجێکردنی سەروەرانە
What this area is built from: the Nexus Standards it applies, the open standards it names and the data and feeds it reads, then the areas its record couples it with (marked).Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-9, NS-11, NS-12.
  • Open standards: NIST SP 800-207 Zero Trust Architecture; Supply-chain Levels for Software Artifacts (SLSA) 1.1; Sigstore signing and transparency log; SPDX; CycloneDX; OpenID Connect Core 1.0 on OAuth 2.0; Decentralized Identifiers (DIDs) v1.0; Digital Public Goods Standard.
  • Data and feeds: ROR data dump; World Development Indicators.
  • Couples with: Sovereign stack; National adoption pathway; Zero-trust fabric; Software and supply chain.
Nexus Standards
3
NS-9, NS-11, NS-12
ستانداردە کراوەکان
8
named, never copied
Data and feeds
2
listed for reference
پەیوەستبوونەکان
4
with other areas
UNI
requested · allocation in progress
دۆخ
Proposednot yet in the catalogue
Last reviewed
area profile
ئاماژە بەم پەڕەیە بدە

Nexus Standards (2026). Sovereign deployment pathway: area brief, Readiness and Adoption programme. Proposed. https://nexustandards.com/readiness/sovereign-deployment-pathway/. Last reviewed 17 October 2026.

Download the profile

Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.

02سنوور

Scope and boundaries

An area of the Readiness and Adoption programme (readiness pathways). The area profile sets out 5 matters in scope and 3 matters addressed by other areas.

In scope 5

  • Data-residency and air-gapped deployment records (contextual UNIs)
  • Build provenance, signing and SBOMs for deployed components
  • Zero-trust identity federation with the global resolver
  • Synchronisation and verification of registry and catalogue data
  • Local licence status and licence conditions

Out of scope 3

  • Hosting services or procurement
  • National security accreditation, which this pathway does not address
  • Data-sharing agreements

Jurisdictions Application in each jurisdiction is a national decision, taken by the National Standards Council (NSC) with the competent national authorities.

03ئامادەباشی

Evidence, recognition and capital pathways

What each institution of the ecosystem draws from this area: The Global Centre for Risk and Innovation (GCRI Canada), as Secretariat, for evidence; The Global Risks Forum (GRF) for recognition; and The Global Risks Alliance (GRA) for capital.

Evidence pathway

GCRI Canada

Records produced in a sovereign deployment remain readable by the GCRI Canada evidence pathway when their provenance and signatures verify; GCRI Canada decides admissibility.

Read the evidence pathway

ڕێڕەوی ناسینەوە

Global Risks Forum (GRF)

A sovereign deployment’s contextual UNI and attestation trail can be cited in a GRF recognition record under GRF’s rules.

Read the recognition pathway

ڕێڕەوی سەرمایە

Global Risks Alliance (GRA)

Projects operated on a sovereign deployment can present verifiable records to GRA, which decides capital readiness.

Read the capital pathway

Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.

04پرۆسە

From evidence to a decision

An artefact is identified and described; its evidence is assembled against the profile of this pathway; clauses are evaluated by an independent evaluator and attested; the evidence file is submitted by reference, and the deciding institution decides under its own rules. 8 operations in 5 phases, built from the area profile: the rows carry its own data sources, indicators, open standards, couplings and, where listed, hazards, and each operation names the rules it implements (14). Records and artefacts are cited by UNI (Unique Nexus Identifier) and version.

گەڕۆکی پرۆسە · Standards · کۆدکردن و ڕاستکردنەوە

خولی ژیانی ستاندارد

17 هەنگاو6 قۆناغ

Standards · کۆدکردن و ڕاستکردنەوە

خولی ژیانی ستاندارد

خولی ژیانی ستاندارد · ڕێڕەوی NS-13 · کەناڵەکانی بەشداری · ڕێڕەوی IETF · ڕێڕەوی W3C · ڕێڕەوی OGC · ڕێڕەوی OASIS · قۆناغەکانی ISO و IEC · گونجاندن · خولی ژیانی تۆمار · ئاڕاستەکردن · چاودێری.

دۆزینەوەکانی خول دەبنە پێشنیاری گۆڕانکاری، ئەنجومەنی جیهانیی ستانداردەکان دوای دوایین بانگەوازی گشتی پەسەندیان دەکات، و هەر وڵاتێک بڕیار لەسەر پەسەندکردنی خۆی دەدات.

  1. 01 ئاڕاستەکردنی ئەرکەکان

    1. 01Route missions to standards and profilesStep · Nexus StandardsNexus Standards routes each candidate mission to the standards and profiles that apply.
  2. 02 پرۆفایلەکان و گونجان

    1. 02پرۆفایلی ئەرکەکان پێکبهێنەهەنگاو · Nexus StandardsNexus Standards پرۆفایلی ئەرکەکان پێکدەهێنێت و هەر پەسەندکردنێکی نیشتمانی تۆمار دەکات کە ئەرکەکان پشتی پێدەبەستن.
    2. 03دەرچووەکانی دروستکردن بەراورد بە پڕۆفایلەکان پشتڕاست بکەرەوەهەنگاو · Nexus StandardsNexus Standards دەرچووەکانی دروستکردن بەراورد بە پڕۆفایلە پێکهێنراوەکان پشتڕاست دەکاتەوە و بەڵگەکان تۆمار دەکات.
    3. 04چاودێریی گونجان بکە و بەڵگەی مۆرکراو تۆمار بکەهەنگاو · Nexus Standardsلە ماوەی Action Week دا، Nexus Standards چاودێریی گونجان دەکات و لادانەکان تۆمار دەکات.
  3. 03 پێشنیار و پێداچوونەوە

    1. 05لادان و ڕاستکردنەوەکان دەبنە پێشنیاری گۆڕانکاریهەنگاو · Nexus Standardsلادانەکان دەبنە پێشنیاری گۆڕانکاری، و ڕاستکردنەوەکە وەک گۆڕانێک لە بەڵگەکەدا تۆمار دەکرێت.
    2. 06دۆزینەوەکانی خول دەبنە پێشنیاری گۆڕانکاریهەنگاو · Nexus Standardsدۆزینەوەکانی خولێک دەبنە پێشنیاری گۆڕانکاری: دۆزینەوەکانی میتۆد و ڕاستکردنەوە لە ڕاپۆرتەکان (F06) و بابەتەکانی خشتەی کار لە Nexus…
    3. 07بە ئاشکرا ڕەشنووس بکە و پێیدا بچۆرەوەهەنگاو · لیژنەکان و گرووپەکانی کارلیژنە تەکنیکییەکان و گرووپەکانی کار ستانداردەکان لە پرۆسەی کراوەی NS-13 دا ڕەشنووس دەکەن و پێیاندا دەچنەوە.
    4. 08پێداچوونەوە بەرەو بڕیاری ئەنجومەنهەنگاو · Nexus StandardsNexus Standards پێشنیارەکانی گۆڕانکاری لە ڕێگەی پێداچوونەوەوە بەرەو بڕیاری ئەنجومەن دەبات.
  4. 04 بڕیاری ئەنجومەن

    1. 09بانگەوازی کۆتایی گشتیهەنگاو · ئەنجومەنی جیهانیی ستانداردەکانئەنجومەنی جیهانیی ستانداردەکان دوای بانگەوازێکی کۆتایی نەوەد ڕۆژە بە زۆرینەی دوو لەسەر سێ پەسەند دەکات.
    2. 10پەسەندکردنی جیهانیی ستانداردێکبڕیار · ئەنجومەنی جیهانیی ستانداردەکانئەنجومەنی جیهانیی ستانداردەکان دوای دوایین بانگەوازی گشتی بڕیار لەسەر پەسەندکردنی هەر ستانداردێک دەدات.
  5. 05 بڵاوکردنەوە و ناساندن

    1. 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
    2. 12UNI دەناسێنێت و هەرگیز بڕوانامە ناداتتۆمار · Nexus Standardsهەر بابەتێکی ساڵی بەرنامە یەک ناسێنەر هەڵدەگرێت، UNI یەک لەژێر NS-1، بۆ ئەوەی ئاماژەی پێ بکرێت، وەشانبەندی بکرێت و چارەسەر بکرێت.
    3. 13گۆڕانکارییە پەسەندکراوەکانی ساڵەکە بڵاو بکەرەوەهەنگاو · Nexus Standardsلە کاتی نوێکردنەوەدا Nexus Standards گۆڕانکارییە پەسەندکراوەکانی ساڵەکە و دۆخی پەسەندکردنی نیشتمانی بڵاو دەکاتەوە.
  6. 06 پەسەندکردن و جێبەجێکردنی نیشتمانی

    1. 14پەسەندکردنی نیشتمانی لەلایەن ئەنجومەنی نیشتمانیی ستانداردەکانەوەبڕیار · ئەنجومەنی نیشتمانیی ستانداردەکانئەنجومەنی نیشتمانیی ستانداردەکانی هەر وڵاتێک بڕیار لەسەر پەسەندکردنی نیشتمانی دەدات: وەک خۆی پەسەند بکرێت، بە پڕۆفایلێک پەسەند بکرێت (NS-16)، بگونجێنرێت، یان تەنها ئاماژەی پێ بکرێت.
    2. 15ستانداردە پەسەندکراوەکان دەگەنە خول و وەشانەکانهەنگاو · Nexus Standardsهەر ستاندارد یان پرۆفایلێکی پەسەندکراو دەبێتە مۆدیولی خولێک لە Risk Academy (F09)، و ستانداردەکان لە وەشانەکانی Reports دا جێبەجێ دەکرێن (R1).
    3. 16پەسەندکردن بۆ هەر ناوچەیەکی دەسەڵات کۆتاییەستاندارد · ئەنجومەنی نیشتمانیی ستانداردەکانپەسەندکردن بۆ هەر ناوچەیەکی دەسەڵات کۆتاییە، و GSC هیچ ڤیتۆیەکی بەسەر بڕیارێکی نیشتمانیدا نییە. هیچ دەزگایەکی جیهانی ڤیتۆی نییە.
    4. 17تۆمارەکانی پەسەندکردنی نیشتمانیتۆمار · Nexus Standardsپڕۆفایلە پێکهێنراوەکانی ئەرک و تۆمارەکانی پەسەندکردنی نیشتمانی لە قۆناغی ئامادەکردنی ئامادەییدا دەنێردرێن بۆ Foundry (F08).

Nexus Standards · Nexus Standards (institution) · National Standards CouncilAn outline of the designed programme cycle, not a record of operation: no cycle has run and every programme is at service level R0. Every Nexus Standard is at the PROPOSED stage and nexustandards.com governs the text and status of each one. A UNI identifies and never certifies; a validator report is evidence for review, not a conformance claim.

The operations, as a table
Process · from evidence to an institutional decision8 operations · 5 phases
هەنگاوقۆناغکارکردنکێDecision ruleتۆمارImplements
01ناسینەوەArtefact (start). What this pathway reads: Data-residency and air-gapped deployment records (contextual UNIs), Build provenance, signing and SBOMs for deployed components and Zero-trust identity federation with the global resolver.the applicant institutionevery artefact carries a UNI and its recordData-residency and air-gapped deployment records (contextual UNIs)NS1-R1, NS1-R4
02ناسینەوەContext (step). Each programme or deployment is its own context.the applicant institutionevidence belongs to its context; nothing is inheritedthe contextual UNI of the programme or deployment (NS-9)NS9-R1, NS9-R3
03بەڵگەEvidence profile (model). Open references of this pathway: NIST SP 800-207 Zero Trust Architecture, Supply-chain Levels for Software Artifacts (SLSA) 1.1, Sigstore signing and transparency log and SPDX.the pathway working groupthe profile states what an artefact must carry to be readable as evidencerequired fields, licence status and provenance depth; references such as NIST SP 800-207 Zero Trust ArchitectureNS14-R2
04بەڵگەAssemble (record). Data sources listed for reference: ROR data dump and World Development Indicators.the applicant institutionevidence is cited by UNI and version; missing evidence is recorded as missingrecord references, including ROR data dumpNS2-R2, NS11-R3
05هەڵسەنگاندنEvaluate (exercise). The evaluator runs outside the applicant’s trust boundary.an independent evaluator with a mandatesubject and evaluator are distinct; missing evidence is INDETERMINATEattestations per clauseNS11-R1, NS11-R2, NS11-R3
06هەڵسەنگاندنReport 17.6.1 (record). A report never states certification; it lists results and evidence.the reporting servicethe report is generated from attestations, with evaluator and instanta generated report, with SDG 17.6.1 where relevantNS11-R5, NS14-R3
07SubmissionFile by reference (step). The institution reads the records at the resolver, so it checks the current state independently.the applicant institutionsubmitted by reference, never copiedthe evidence file cited by UNI and versionNS2-R1, NS2-R5
08بڕیارInstitution decides (end). Records produced in a sovereign deployment remain readable by the GCRI Canada evidence pathway when their provenance and signatures verify; GCRI Canada decides admissibility.the deciding institutionthe institution decides under its own rules; a standard makes no one readythe institution’s decision, recorded by referenceNS13-R4, NS14-R3

Table.Operations in walking order; each row names the phase, the operation, its actor, its decision rule, the record it leaves and the rule identifiers it implements. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: NIST SP 800-207 Zero Trust Architecture · Supply-chain Levels for Software Artifacts (SLSA) 1.1 · NS-9: Contextual UNIs · NS-11: Verification and monitoring.

05ستاندارد

ستانداردە جێبەجێبووەکان

The area profile lists 3 Nexus Standards. Each is a proposed standard under development.

  1. 01

    NS-9 · Contextual UNIs (deployments, instances, programme instances)

    Status: proposed · 5 requirements stated. Read NS-9.

  2. 02

    NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)

    Status: proposed · 6 requirements stated. Read NS-11.

  3. 03

    NS-12 · Software, model and AI/ML artefacts (supply chain, model cards, dataset sheets)

    Status: proposed · 4 requirements stated. Read NS-12.

06مۆدێلی سیستەم

How a shock travels through this system

A system model of this area built from the registry: 5 systems, 4 sectors, 9 controls, 2 feeds, 2 indicators. Select the components to include, choose an initiating hazard and run the scenario. Stress propagates through the hazard relations of the Nexus Hazard Standard (NHS-1), the exposure of each system, the recorded couplings and the sectors that carry the loss; adopted standards dampen transmission and live data sources support detection. All parameters are stated assumptions that the reader can adjust; results are illustrative scenario outputs for exercises and training, not forecasts or risk assessments.

کۆنترۆڵەکان

  • NS-9 UNIی ناوەڕۆکی (دامەزراندنەکان، نموونەکان، نموونەکانی پڕۆگرام)
  • NS-11 سەلماندن و چاودێری (بەڵگە، گواهییەکان، چاودێریی گونجان لەگەڵ zero-trust)
  • NS-12 بەرهەمەکانی نەرمەکاڵا، مۆدێل و AI/ML (زنجیرەی دابینکردن، کارتی مۆدێل، پەڕەی کۆمەڵە داتا)
  • NRS-A4 پشتڕاستکردنەوەی بێمتمانەی بنەڕەتی بۆ ستانداردەکان و گونجان
  • NRS-A6 کیتەکانی دامەزراندن و پەسەندکردن بە یەک کرتە
  • NRS-T7 مەترسیی ناسنامەی دیجیتاڵ و ژێرخانی متمانە
  • NRS-H93 Hazard family: Identity, trust and cryptographic failure (NHS-1 cyber.identity)
  • NRS-H106 خێزانی مەترسیدەر: تەکنەلۆجیای ئاسمانی و ژێرخانی خولگەیی (NHS-1 tech.space-systems)
  • NRS-H107 خێزانی مەترسیدەر: چڕبوونەوە و یەکڕەنگیی ژێرخانی دیجیتاڵ (NHS-1 tech.digital-concentration)

چاودێری

  • ROR data dump (listed for reference)
  • World Development Indicators (listed for reference)
  • Fixed broadband subscriptions per 100 inhabitants, by speed
  • Proportion of individuals using the Internet
07پەیوەستبوونە سیستەمییەکان

پەیوەستبوونە سیستەمییەکان

4 couplings link this area to other areas and programmes, each with the mechanism of the link.

  1. Sovereign stackOpen Infrastructure and DevelopersThe self-hostable reference deployment is specified in the infrastructure area.
  2. National adoption pathwayReadiness and AdoptionNational adoption commonly requires in-country hosting.
  3. Zero-trust fabricTrust, Verification and AssuranceIdentity, mandates and mutual authentication make a sovereign deployment trustworthy to others.
  4. Software and supply chainTrust, Verification and AssuranceSigned builds, SBOMs and provenance attestations let a sovereign operator verify what it runs.
10نیشاندەرەکان

نیشاندەرەکان

The area profile names 2 indicators, each with its framework and code.

11Data sources

Data sources

2 data sources named in the area profile, each with provider, licence, update frequency and delivery path.

Data sources

Data sources are listed for reference; live data is displayed once licence review is complete.

زیندوو
0
on completion of licence review
Listed in the data register
1
licence terms recorded
Proposed for the register
1
licence terms to be recorded
جێبەجێکردن
1 governed service · 0 plugin · 0 browser · 1 snapshot · 0 listed for reference
proposed paths in order of preference: governed data service, plugin, direct browser read, build-time snapshot; sources whose terms do not permit reuse are listed for reference only
  • World Development Indicatorsfor reference

    World Bank · annual with quarterly updates

    CC BY 4.0

    governed data servicelisted in the data register.

  • ROR data dumpfor reference

    Research Organization Registry · monthly

    CC0 1.0

    build-time snapshotproposed for the data register

12بینەران

Intended users

The area profile identifies 4 user communities.

  1. Government digital agencies
  2. National data centres
  3. Institutions with residency obligations
  4. Developers and operators
13گرووپی کار

Working group charter

A proposed charter for this area, open to institutions and experts.

سنوور

Describe the sovereign deployment profile and how sovereign instances stay verifiable and interoperable.

Institutions and experts are invited to charter this working group under NS-13 by filing a public change record. National Working Groups (NWGs) contribute national inputs and field exercises through their National Nexus Consortium (NNC).

Deliverables · 3
  1. Sovereign deployment profile (residency, air-gap, identity federation)
  2. Build provenance requirements on SLSA and Sigstore
  3. Synchronisation protocol for registry data
Liaison targets · 4
  • OpenSSF liaison sought
  • Digital Public Goods Alliance liaison sought
  • OpenID Foundation liaison sought
  • W3C DID Working Group liaison sought
14Research questions

Open research questions

3 questions identified as priorities for the working group.

  1. Air-gapped operation conflicts with transparency logs that assume online verification.
  2. Identity federation across sovereign instances lacks an agreed trust framework.
  3. Data-residency law varies and can restrict even metadata synchronisation.
15Restricted standards

Restricted compatibility profiles

Standards whose text is not openly available are named and linked only. Any compatibility profile is kept on protected pages until an arrangement with the issuing body is in place.

The working group may identify restricted standards relevant to this area; they are listed here by name and link.

16Hazards and sectors

Hazards, threats and sectors concerned

Hazards and threats 0

This area draws on the hazards of the areas it is coupled with.

کەرتەکان 0

This area serves all sectors through the areas it is coupled with.

17سەرچاوەکان

سەرچاوەکان

4 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.

18Research hub

Recent research on this area

Recent peer-reviewed articles, preprints, datasets and reports on the subject of this area, 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 termsdigital sovereignty; data sovereignty; digital public infrastructure; Sigstore signing and transparency log; SPDXDerived from the title and scope of the area, the NHS-1 hazards it names and the open standards it lists.

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

20لە سەرانسەری تۆڕەکەدا

Programmes, tracks and courses for this area

GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA) and Risk Academy work on the subject of this area in distinct roles (research and evidence; governance, policy and convening; capital, finance and markets; education and training). Each entry states why it corresponds and the step it offers; each institution sets its own terms of participation.

Governance, policy and convening

Global Risks Forum (GRF)

Tracks that convene public authorities, researchers and institutions on the governance of shared risks.

AI and Digital GovernanceExamines digital dependence.Join this track globalriskforum.comAll tracks of The Global Risks Forum
21زاراوە سەرەکییەکان

زاراوە سەرەکییەکان

UNI
Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
پێشنیازکراو
A draft in the open development process that the Global Standards Council has not yet adopted. Each area profile is a proposal to the Nexus Standards registry.
adopt
Relation in which the external standard is used as published and values are validated against it.
crosswalk
Relation in which clauses of these standards are mapped to parts of the external standard by clause number, without reproducing its text.
profile
Relation in which a Nexus profile narrows or extends the external standard for a defined use, validated with the issuing body’s own tools where these exist.
change record
A public record of a proposed change under NS-13, decided by the editors with written reasons.
attestation
An evaluator’s recorded result for one clause and one subject under NS-11.
liaison sought
A liaison the working group intends to request from the issuing body; a liaison is established only when the body confirms it in writing.
23توێژینەوە

Recent research and sources

Peer-reviewed articles, preprints, reports and datasets on the subject of this area, retrieved at the time of reading from open scholarly metadata services (OpenAlex and Crossref) and listed with authors, venue, year, type and access status, with a link to each work. Curated references and related standards are listed first; recent works matched by subject follow and are listed for orientation.

Curated references

Related standards and frameworks

Search terms, derived from the title and scope of the area: digital sovereignty; data sovereignty; digital public infrastructure. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

24پرسیارەکان

پرسیار و وەڵام.

What is the status of the Sovereign deployment pathway area?
The area profile is a proposal to the Nexus Standards registry; the area is not yet in the catalogue. Standards are adopted by the Global Standards Council after last call; in each country, adoption is a decision of its National Standards Council (NSC).
How are data sources presented?
Each data source is listed with its provider, licence, update frequency and delivery path, and links to the provider’s own publication.
How can this brief be amended?
Through a public change record under NS-13: a proposed amendment to the area profile or the registry, decided by the editors with written reasons.
ڕاپۆرتەکانبەشداری بکە

لەم لاپەڕەیەوە بەڵگە پێشکەش بکە.

Reports بڵاوکراوەی وەرزیی کۆنسۆرتیۆم ـە. ئەوەی تۆ لەسەر ئەم بابەتە دەیزانیت دەتوانێت لە وەشانی داهاتوودا ببێتە بەڵگە، کەیس یان ڕاستکردنەوە، بە ناوی خۆتەوە و لەژێر CC BY 4.0 بڵاو دەکرێتەوە کاتێک کاری خۆتە.

Nexus Standards
ستاندارد

Contribute to Sovereign deployment pathway

Institutions and experts are invited to propose amendments, join the working group or propose data sources. National participation is organised through each country’s National Nexus Consortium (NNC) and its National Working Groups (NWGs); competent national authorities are engaged through official channels.

دۆخ و بەکارهێنان. Nexus Standards ستانداردی پێشنیارکراون کە لە ڕێگەی پرۆسەیەکی کراوەوە لەژێر NS-13 پەرەیان پێدراوە و بۆ بەکارهێنانی خۆبەخشانە بڵاو کراونەتەوە؛ بڕوانامە، متمانەپێدان یان ڕەزامەندیی ڕێکخەر نین، و پەسەندکردن بڕیاری ئەنجومەنی جیهانیی ستانداردەکان و، لە هەر وڵاتێکدا، ئەنجومەنی نیشتمانیی ستانداردەکانی ئەو وڵاتەیە. UNI (Unique Nexus Identifier) بەرهەمێک دەناسێنێت؛ بڕوانامەی پێ نادات. ناوی دەستەکانی ستاندارد و ستانداردەکانیان هی پارێزەرەکانیانن و تەنها بۆ ناساندنی بەڵگەنامەکان بەکاردێن؛ هیچ دەقێکی ستانداردێکی دەرەکی لێرەدا دووبارە نەکراوەتەوە. Nexus Standards پەیوەست نییە بە هیچ دەستەیەکی ستانداردی ناوهێنراو لێرەدا، و لەلایەن هیچیانەوە پشتگیری یان بڕوانامەی پێ نەدراوە.

مۆڵەتەکان: CC BY 4.0 بۆ دەقی ستانداردەکان، تۆمارگەکان، سکێماکان و داتا؛ Apache-2.0 بۆ کۆدی سەرچاوە. ستانداردە دەرەکییەکان بە ناو، ژمارە و بەستەر لە ژێر مۆڵەتەکانی خۆیاندا ئاماژەیان پێدەدرێت. داتا، کتێبخانە و فۆنتەکانی لایەنی سێیەم مۆڵەتەکانی خۆیان دەپارێزن: بڕوانە ئاگادارییەکانی لایەنی سێیەم.