> For the complete documentation index, see [llms.txt](https://docs.therisk.global/organization/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.therisk.global/organization/introduction/acceleration.md). # ACCELERATION How the Nexus programme intends to turn shared methods and evidence into working capability, and the limits on every claim of build, compute and scale. **Where this fits:** all six sectors · the [Foundry pillar](/organization/programme/foundry.md), with [Labs](/organization/programme/labs.md), [Nexus Universe](/organization/programme/universe.md) and [Risk Academy](/organization/programme/academy.md) · the [Nexus Consortium](/organization/institutions/nexus-consortium.md) and [National Nexus](/organization/governance-in-operation/national-nexus.md) · the Planning, Readiness preparation and Controlled build phases of [the programme year](/organization/programme/the-programme-year.md) · introduction to the deep doctrine. Canonical homes: [The Model](/organization/model.md) · [Systems](/organization/systems.md) · [Finance readiness](/organization/finance-readiness.md).
Document record · Draft · Legal review required · Updated 21 October 2026 | | | | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Status** | Draft. Explanatory page; it creates no rights or obligations. | | **Legal review** | Required before final publication. | | **Version** | 2026.10.21-r3 | | **Updated** | 21 October 2026 · reviewed every 180 days | | **Owner** | Documentation desk (named reviewer pending) | | **Based on** | Nexus constitutional directives D-V3-0003 (*Twenty-system constitution*), D-V3-0004 (*One Rail-Two Stacks and non-execution*) and D-V3-0005 (*Product truth, claims and evidence*); the owner decision of 11 October 2026 on Nexus institutional architecture and participation, with GCRI Canada as lead contracting organization, and the consortium programme offerings and service levels, in the Nexus institutional register; the Nexus model and the Nexus Consortium model as published on the GCRI, GRF and GRA sites; [Nexus Standards](/organization/institutions/nexus-standards.md) as published at nexustandards.com | | **Corrections** | Public corrections route to be announced; corrections are published as new dated versions. |
{% hint style="info" %} **Status.** System capabilities described on this page are target architecture under development. Nothing here states that a capability is in production use, certified or offered as a service. {% endhint %} ## In brief Acceleration, in this documentation, is the governed path by which shared methods, evidence and standards are meant to become working capability: computing estates, observation at the edge, tested builds, learning programmes, a catalogue of reusable components, national and regional consortiums, and a time-bound activation plan. Every page here describes a target design. None of it is a record that a system is deployed, a programme is running or a country has joined, and decisions stay with competent authorities \[1]\[2]\[3]. ## Current position (21 October 2026) This section brings the page up to date with the published sites, the Nexus Standards and the owner's rulings of October 2026. Where the older text below differs, this section and the canonical pages it links govern. **Systems, not products.** The technology this page refers to is the [twenty Nexus systems](/organization/systems.md), each named by its display code (for example [NXS-COR](/organization/systems/nxs-cor.md) for compute and runtimes, [NXS-NET](/organization/systems/nxs-net.md) for networks, [NXS-FAC](/organization/systems/nxs-fac.md) for builds and verification, [NXS-NXQ](/organization/systems/nxs-nxq.md) for packages and capability lifecycle, [NXS-APP](/organization/systems/nxs-app.md) for the application catalogue and [NXS-RLS](/organization/systems/nxs-rls.md) for agreements and lawful handoffs). The build work is the [Foundry pillar](/organization/programme/foundry.md): "a configured or simulated capability is not a validated result, and a National Portfolio entry is not an investment decision" \[7]. Technology, infrastructure and service providers work with the Nexus Consortium at arm's length under written agreements. Programmes and campaigns are now described as mission families of [Nexus Universe](/organization/programme/universe.md), the annual programme governed by GRF: missions are admitted at gate G1, built in a one-month controlled build, tested in Action Week and stood down, with findings published after review \[8]. The ten programme offerings O01 to O10 of the Nexus Consortium are the public entry routes ([Use by](/organization/use-by.md)). **Finance boundary.** National Consortium Companies and Project SPVs are structures that competent, lawful actors may form outside the programme, under their own law and licences. The programme prepares evidence, standards and readiness; it never forms, arranges, owns or advises on a vehicle or a transaction, and readiness evidence is not a financing decision \[9]\[10]. Where this page describes such vehicles, read it with [Lawful handoffs](/organization/finance-readiness/lawful-handoffs.md) and [National portfolios](/organization/finance-readiness/national-portfolios.md). **Status.** Every programme is in formation and the current service level is R0, information and enquiries; no edition of [Nexus Reports](/organization/programme/reports.md) has been released and no [Risk Academy](/organization/institutions/risk-academy.md) credential has been issued \[11]\[12]. ## What this section covers The eight pages below keep their existing addresses. Each explains one part of the acceleration design and links to the pages that hold shared definitions.
PageWhat it answersLink
I. OrderWhat acceleration means here, the rules that bound it, and how its layers map to the twenty canonical systems.I. Order
II. ComputeHow compute estates, placement, networks and deployment are divided between NXS-COR, NXS-NET and NXS-APP, and what "sovereign" may and may not mean.II. Compute
III. EdgeHow signals from instruments, imagery and communities are meant to become governed observations and evidence, and why none of it is an official warning.III. Edge
IV. The Foundry pillar and the systemsHow capabilities are composed, built, verified, signed and installed, and why verification is not certification.IV. The Foundry pillar and the systems
V. ProgramsThe programme offerings that build institutional capability, their entry routes, outputs and boundaries.V. Programs
VI. MarketplaceHow reusable components are meant to be registered, admitted and found, and why a listing is not recognition.VI. Marketplace
VII. ConsortiumsThe global, regional and national consortium geometry, who stewards it, and which actors execute outside it.VII. Consortiums
VIII. CampaignThe activation horizon to 2030, stated as targets with no implementation record.VIII. Campaign
## How to read this section * **Authority.** Every page here is explanatory (authority level L5). It creates no obligation and adopts no instrument. Where a page and a binding record disagree, the record prevails \[5]. * **Deployment profiles.** While the release hold is active, only internal development, pull-request preview, isolated test and non-certified research profiles are permitted. Enterprise SaaS, on-premises, private cloud, sovereign, OEM-embedded, marketplace and certified public-good profiles are blocked \[4]. * **Programme state.** The consortium programme records state the current service level as R0, "Information and enquiries": applications, contribution payments, computing allocations and event registration open only when their service team, terms and review capacity are in place \[6]. * **Names.** Systems are named by their Nexus Standards display codes: the first mention on a page carries a short description, and later mentions use the code alone. This section draws mainly on NXS-COR, the distributed compute system for compute, providers and regions; NXS-NET, the network intelligence and communications resilience system; [NXS-OPS](/organization/systems/nxs-ops.md), the observatory protocol system; [NXS-SIG](/organization/systems/nxs-sig.md), the authorized signal, spectrum and communications integrity system; [NXS-EOP](/organization/systems/nxs-eop.md), the Earth observation, geospatial and digital-twin fabric; [NXS-EWS](/organization/systems/nxs-ews.md), the early warning support system for watches and warning readiness, which never issues official alerts; [NXS-STU](/organization/systems/nxs-stu.md), the builder and configuration workspace, which composes but never deploys; NXS-FAC, the mission application factory, which produces app blueprints but never runs them; NXS-NXQ, the software, capability and agent fabric for registries, licensing, APIs and connectors; and NXS-APP, the mission app runtime, for app instances, routes and versions. The twenty systems together make up the technical architecture; no single design environment is the whole of it \[1]. * **Drafting.** This section was drafted with AI assistance and has not yet been reviewed by a named human approver. ## Key relationships
Reading map of the eight acceleration pages. I. Order sets the rules and leads to two branches: II. Compute and III. Edge, which feed evidence and records; and IV. The Foundry pillar and the systems, VI. Marketplace, V. Programs, VII. Consortiums and VIII. Campaign. Foundry also produces evidence and records. Evidence reaches competent authorities as evidence only and campaign targets as targets only; authorities decide.

Figure 1. How the eight acceleration pages relate. A reading map of a target design, not a record of any deployed system, running programme or constituted consortium. Source: V3 constitutional set and consortium programme source in the institutional records [1][2][6], as of 2026-10-16.

Text description of Figure 1 I. Order sets the rules and maps acceleration to the twenty canonical systems. It leads to II. Compute (NXS-COR, NXS-NET and NXS-APP) and IV. The Foundry pillar and the systems (NXS-STU, NXS-FAC and NXS-APP). Compute supports III. Edge (NXS-OPS, NXS-SIG, NXS-EOP and NXS-EWS), which feeds evidence and records. Foundry feeds VI. Marketplace (NXS-NXQ and NXS-APP) and also produces evidence and records. The marketplace supports V. Programs (offerings O01 to O10), which lead into VII. Consortiums at global, regional and national level, which lead into VIII. Campaign, the targets to 2030. Evidence and records, and campaign targets, reach competent authorities only as evidence and as targets; the authorities decide.
## Canonical definitions used in this section * Institutional roles are stated once, in [I. Order of the Organization introduction](/organization/introduction/organization/i.-order.md). Acceleration pages summarize them and link back. * Status words, the five public states and the boundary formulas are explained in [III. Reading rules](/organization/introduction/knowledge/iii.-reading-rules.md). * The twenty canonical systems are listed with their remits in [I. Order](/organization/introduction/acceleration/i.-order.md) of this section. * The national, regional and global levels are explained in [VI. Federation](/organization/introduction/organization/vi.-federation.md). ## Related pages * Up: [Organization space home](/organization/introduction.md) * Across: [Knowledge](/organization/introduction/knowledge.md) · [Organization](/organization/introduction/organization.md) · [Operations](/organization/introduction/operations.md) · [Cooperation](/organization/introduction/cooperation.md) · [Standardization](/organization/introduction/standardization.md) * Counterparts: [Acceleration part](/organization/acceleration.md) · [Systems](/organization/systems.md) · [Nexus Compute](/organization/acceleration/nexus-compute.md) · [Nexus Programs](/organization/acceleration/nexus-programs.md) · [GCRI Campaigns](/organization/acceleration/nexus-campaigns.md) · [Technology acceleration thesis](/organization/organization/architecture/i.-thesis/iv.-technology-acceleration.md) ## Sources 1. Nexus constitutional directive D-V3-0003, *Canonical Twenty-System Constitution and Authority Matrix*. Internal record, cited by identifier. 2. Nexus constitutional directive D-V3-0004, *One Rail-Two Stacks, Non-Execution and Lawful Handoff Constitution*: public-good rail, enterprise and sovereign execution stack, boundary formulas. Internal record, cited by identifier. 3. Nexus institutional register, *Nexus institutional architecture and participation*: owner decision of 11 October 2026 on GCRI Canada as lead contracting organization (owner-confirmed; counsel review pending), roles and "not conferred" table. Internal record. 4. Nexus institutional register: release hold policy (in force since 21 July 2026; blocked and permitted profiles) and claim register. Internal record. 5. Nexus Documentation Standard, draft of 16 October 2026 (authority and status, naming, external frameworks and sources), the owner decisions of 16 October 2026 and the introduction audit of 16 October 2026. Internal editorial records; not published. 6. Nexus institutional register, consortium programme: operating functions, programme offerings O01 to O10, service levels R0 to R5, current service level R0; drawing on the consortium directives D-NEXUS-CONSORTIUM-PUBLIC-ARCHITECTURE-2 and D-NEXUS-CONSORTIUM-STAKEHOLDER-READINESS-3. Internal record. 7. GCRI (2026). *How Nexus works*: the six pillars, their eighteen handoffs and the eight-step cycle (Question, Evidence, Build, Organize, Test, Publish, Decide, Renew). [therisk.global/nexus-cycle](https://therisk.global/nexus-cycle/). Read 2026-10-21. 8. [The Global Risks Forum](/organization/institutions/grf.md) (2026). *Nexus Universe at GRF*: the annual programme, gates G0 to G7 and the ten Action Week tracks. [globalriskforum.com/nexus-universe](https://globalriskforum.com/nexus-universe/). Read 2026-10-21. 9. [The Global Risks Alliance](/organization/institutions/gra.md) (2026). *Finance and insurance readiness*: readiness evidence is not a financing decision. [globalriskalliance.com/finance-readiness](https://globalriskalliance.com/finance-readiness/). Read 2026-10-21. 10. The Global Risks Alliance (2026). *Lawful handoffs*: readiness evidence is released one to one on the owner's written direction, with no introduction and no pay tied to any transaction. [globalriskalliance.com/finance-readiness/handoff](https://globalriskalliance.com/finance-readiness/handoff/). Read 2026-10-21. 11. GCRI (2026). *Programme status*: Exploration, In formation, Constituted, Active programme, Paused, Closed, Historical record; current service level R0. [therisk.global/consortium/programme-status](https://therisk.global/consortium/programme-status/). Read 2026-10-21. 12. GCRI (2026). *Nexus Reports programme*: quarterly country editions, an annual flagship and specialist series; current approved releases: none. [therisk.global/publications/nexus-reports](https://therisk.global/publications/nexus-reports/). Read 2026-10-21. ## Editorial record * As of: 2026-10-16. Refresh: every 180 days, or sooner when a governing source changes. * Drafting: AI-assisted. Human review: pending; no named reviewer or approver yet. * Corrections: a public corrections route has not yet been published. Corrections will be recorded as new dated versions, not silent edits. * Change: 2026-10-16, upgraded to the documentation standard draft. "Sovereign-ready environments" removed; Record block, In brief, release-hold status, cards to every child page, acceleration map, sources and editorial record added. * Change: 2026-10-16 r2, readable document record and status note; Nexus Standards display codes for systems; system naming; Nexus Observatory Protocol note; ownership and licensing statements rewritten without naming any company; internal paths, commit references and status codes replaced with plain words. * Change: 2026-10-21 r3, brought up to date with the published sites, Nexus Standards and the owner's rulings of October 2026: Where this fits line; a Current position section; Nexus Standards described as published ([NS-0](https://nexustandards.com/standards/ns-0/) to [NS-16](https://nexustandards.com/standards/ns-16/) and [NS-3b](https://nexustandards.com/standards/ns-3b/), NIS-1, 348 NRS in 15 series, all PROPOSED; GCRI Canada publisher of record; governance bodies and adoption modes); the national vocabulary of National Nexus, the NNC with its six [Helix councils](/organization/governance-in-operation/councils.md), the NLC and the NWG; the finance boundary on every vehicle passage; the systems named as systems; all original sections kept. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.therisk.global/organization/introduction/acceleration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.