Skip to content
StandardsReadiness and AdoptionReadiness pathways
Area · proposed

Rêya bicîhkirina serwerî

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

Rêya bicîhkirina serwerî
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
Standardên vekirî
8
named, never copied
Data and feeds
2
listed for reference
Girêdan
4
with other areas
UNI
requested · allocation in progress
Rewş
Proposednot yet in the catalogue
Last reviewed
area profile
Jêgirtina vê rûpelê

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Çarçove

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.

03Amadebûn

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

Rêya naskirinê

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

Rêya sermiyanê

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.

04Pêvajo

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.

Lêgerînerê pêvajoyê · Standards · kod bike û rast bike

Çerxa jiyanê ya standardê

17 gav6 qonax

Standards · kod bike û rast bike

Çerxa jiyanê ya standardê

Çerxa jiyanê ya standardê · Rêça NS-13 · Kanalên beşdariyê · Rêça IETF · Rêça W3C · Rêça OGC · Rêça OASIS · Qonaxên ISO û IEC · Lihevbûn · Çerxa jiyanê ya tomarê · Rêkirin · Çavdêrî.

Dîtinên çerxê dibin pêşniyarên guhertinê, Encûmena Standardên Cîhanî piştî banga dawî ya giştî dipejirîne, û her welat pejirandina xwe bi xwe diyar dike.

  1. 01 Rêkirina mîsyonan

    1. 01Route missions to standards and profilesStep · Nexus StandardsNexus Standards routes each candidate mission to the standards and profiles that apply.
  2. 02 Profîl û lihevhatin

    1. 02Profîlên mîsyonan pêk bîneGav · Nexus StandardsNexus Standards profîlên mîsyonan pêk tîne û her pejirandineke neteweyî ya ku mîsyon xwe dispêrinê tomar dike.
    2. 03Derketinên avakirinê li hember profîlan piştrast bikeGav · Nexus StandardsNexus Standards encamên avakirinê li hember profîlên pêkhatî piştrast dike û delîlan tomar dike.
    3. 04Çavdêriya lihevhatinê bike û delîlên mohrkirî tomar bikeGav · Nexus StandardsDi Hefteya Çalakiyê de Nexus Standards lihevhatinê dişopîne û cudabûnan tomar dike.
  3. 03 Pêşniyar û nirxandin

    1. 05Dûrketin û rastkirin dibin pêşniyarên guhertinêGav · Nexus StandardsDûrketin dibin pêşniyarên guhertinê, û rastkirin wekî guhertinek di delîlan de tê tomarkirin.
    2. 06Encamên çerxê dibin pêşniyarên guhertinêGav · Nexus StandardsDîtinên çerxekê dibin pêşniyarên guhertinê: dîtinên rêbaz û rastkirinê ji rêzeya Pergalên Stratejîk (F06) û babetên dosyayê ji Nexus…
    3. 07Bi eşkereyî amade bike û biguherîneGav · Komîte û komên xebatêKomîteyên teknîkî û komên xebatê standardan di pêvajoya vekirî ya NS-13 de amade dikin û nû dikin.
    4. 08Nirxandin ber bi biryara encûmenê veGav · Nexus StandardsNexus Standards pêşniyarên guhertinê bi rêya nirxandinê ber bi biryara encûmenê ve dibe.
  4. 04 Biryara encûmenê

    1. 09Banga dawî ya giştîGav · Encûmena Cîhanî ya StandardanEncûmena Cîhanî ya Standardan piştî banga dawî ya nod-rojî bi piraniya du-ji-sê dipejirîne.
    2. 10Pejirandina cîhanî ya standardekêBiryar · Encûmena Cîhanî ya StandardanEncûmena Standardên Cîhanî piştî banga dawî ya giştî li ser pejirandina her standardê biryar dide.
  5. 05 Biweşîne û nas bike

    1. 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
    2. 12UNI nas dike û qet sertîfîka nadeTomar · Nexus StandardsHer tiştekî sala bernameyê nasnavekî hildigire, UNI-yek di bin NS-1 de, da ku were jêgirtin, guhertoya wê were girtin û were çareserkirin.
    3. 13Guhertinên pejirandî yên salê biweşîneGav · Nexus StandardsDi nûkirinê de Nexus Standards guhertinên pejirandî yên salê û rewşa pejirandina neteweyî diweşîne.
  6. 06 Pejirandin û sepandina neteweyî

    1. 14Pejirandina neteweyî ji aliyê Encûmena Neteweyî ya Standardan veBiryar · Encûmena Neteweyî ya StandardanEncûmena Standardên Neteweyî ya her welatî li ser pejirandina neteweyî biryar dide: wekî xwe pejirandin, bi profîlekê pejirandin (NS-16), adaptekirin, an tenê referans.
    2. 15Standardên pejirandî digihîjin kurs û weşananGav · Nexus StandardsHer standard an profîleke pejirandî dibe modulek kursê li Risk Academy (F09), û standard di weşanên Reports de têne sepandin (R1).
    3. 16Pejirandin ji bo her herêma desthilatê dawî yeStandard · Encûmena Neteweyî ya StandardanPejirandin ji bo her herêma desthilatê dawî ye, û GSC tu vetoyê li ser biryareke neteweyî nîne. Tu dezgeheke cîhanî vetoyê nagire.
    4. 17Tomarên pejirandina neteweyîTomar · Nexus StandardsProfîlên mîsyonê yên pêkhatî û tomarên pejirandina neteweyî di amadekirina amadebûnê de diçin 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
GavQonaxXebitandinKîDecision ruleTomarImplements
01NaskirinArtefact (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
02NaskirinContext (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
03DelîlEvidence 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
04DelîlAssemble (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
05NirxandinEvaluate (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
06NirxandinReport 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
08BiryarInstitution 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.

05Standards

Standardên ku têne sepandin

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.

06System model

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.

Kontrol

  • NS-9 UNI yên çarçoveyî (belavkirin, mînak, mînakên bernameyê)
  • NS-11 Piştrastkirin û çavdêrî (delîl, erêkirin, çavdêriya lihevhatina zero-trust)
  • NS-12 Berhemên nermalav, model û AI/ML (zincîra dabînkirinê, kartên modelê, pelên koma daneyan)
  • NRS-A4 Piştrastkirina bê-bawerî ya standardan û lihevhatinê
  • NRS-A6 Kîtên bicihkirin û pejirandinê bi yek klîkê
  • NRS-T7 Xetera nasnameya dîjîtal û binesaziya baweriyê
  • NRS-H93 Hazard family: Identity, trust and cryptographic failure (NHS-1 cyber.identity)
  • NRS-H106 Malbata metirsiyê: Teknolojiya fezayê û binesaziya orbîtal (NHS-1 tech.space-systems)
  • NRS-H107 Malbata metirsiyê: Kombûn û yekrengiya binesaziya dîjîtal (NHS-1 tech.digital-concentration)

Çavdêrî

  • 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
07Girêdanên pergalî

Girêdanên pergalî

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.
10Nîşander

Nîşander

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.

Zindî
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
Radestkirin
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

12Temaşevan

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
13Koma xebatê

Working group charter

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

Çarçove

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.

Sektor 0

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

17Çavkanî

Çavkanî

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.

20Li seranserê torê

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.

21Têgehên sereke

Têgehên sereke

UNI
Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
pêşniyarkirî
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.
23Lêkolîn

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.

24Pirs

Pirs û bersiv.

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.
rêzeya Pergalên StratejîkBeşdar bibe

Ji vê rûpelê delîl bidin.

Reports weşana sê mehane ya Konsorsiyûmê ye. Tiştê ku tu li ser vê mijarê dizanî dikare di çapa pêş de bibe delîl, dosya an rastkirin, bi navê te û di bin CC BY 4.0 de weşandî li cihê ku karê te bi xwe be.

Nexus Standards
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.

Rewş û bikaranîn. Nexus Standards standardên pêşniyarkirî ne ku bi pêvajoyeke vekirî di bin NS-13 de hatine pêşxistin û ji bo bikaranîna dilxwazî hatine weşandin; ew ne belgename, ne akreditasyon û ne pejirandina rêkxistinê ne, û pejirandin biryara Encûmena Standardên Cîhanî û, li her welatî, ya Encûmena Standardên Neteweyî ya wê dimîne. UNI (Unique Nexus Identifier) berhemekê nas dike; wê belgename nake. Navên desteyên standardan û standardên wan aîdî parêzvanên wan in û tenê ji bo naskirina belgeyan têne bikaranîn; tu nivîsa standardeke derve li vir nayê dubarekirin. Nexus Standards bi tu desteya standardan a li vir hatiye binavkirin ve ne girêdayî ye, ji aliyê wê ve nayê piştgirîkirin û belgename nekiriye.

Lîsans: CC BY 4.0 ji bo nivîsa standardan, tomargeh, şema û daneyan; Apache-2.0 ji bo koda referansê. Standardên derve bi nav, hejmar û girêdanê di bin lîsansên xwe de têne jêgirtin. Dane, pirtûkxane û fontên aliyê sêyem lîsansên xwe diparêzin: binêre Agahdariyên aliyê sêyem.