> 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/systems/nxs-nxq.md). # NXS-NXQ NXS-NXQ, the software, packages, models, agents and capability lifecycle system of the Nexus ecosystem: purpose, rooms, inputs and outputs, areas, standards and boundaries. {% hint style="info" %} This page is generated from the twenty-system charters, the system profiles, the interface and authority registers, the room register, the areas of work, the systems article of the constitution set and the programme spine. Do not edit it in GitBook: change the source and export again. {% endhint %} **NXS-NXQ** is one of the twenty systems of the Nexus ecosystem: the software, packages, models, agents and capability lifecycle system. It is described here as a system of the ecosystem, with its purpose, its rooms, what it receives and provides, the areas it serves, the standards that apply and its boundaries. Earlier pages may use the retired name `NEXQ`. ## Purpose and context Capability, package, agent, tool, model and connector-package registry: admission, entitlement, capability versions, dependency and compatibility, revocation and recall, and the model gateway registry (ADR 0139). Its domain is software, models, tools, skills, packages and capability admission. A typical setting is an organization's model and agent capability estate with pinned versions and controlled tool access. ## What it is the authority for It is the single owner of these fact families; any other system that needs them reads them from NXS-NXQ: capability and package registry. | Record | What the system must keep | | ------------------- | ---------------------------------------------------------------------------------- | | capability | Preserve digest, provider identity and manifest version. | | consumer refs | Track who resolves or uses each capability without inventing Account entitlements. | | admission evidence | Bind task, data class, evaluation suite and expiration. | | license constraints | Keep software, weights, data and service terms separate. | | dependency graph | Detect incompatible, withdrawn or unpinned dependencies before preparing a bundle. | ## Rooms and areas of work Every system has ten rooms: eight shared rooms, which work the same way across systems with this system's domain, and two specialist rooms. | Room | Kind | Purpose | | ------------ | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | Station | Shared | The system's home: posture of the system's own records, freshness, refusals and next actions; never a summary of another system's truth | | Mission | Shared | Mission and task work for the system's domain, linked to Universe missions and Project OS plans | | Builder | Shared | Composition of the system's artifacts and configurations from admitted packages (NXS-STU, NXS-FAC and NXS-NXQ boundaries apply) | | Maps | Shared | Spatial views of the system's records and NXS-GRX products, under the boundary licence gate | | Data | Shared | The system's datasets, sources and lineage as NXS-GRX products or system-owned records | | Commons | Shared | Shared methods, standards, templates and reusable artifacts, including Nexus Standards (NXS, a programme of the Nexus Consortium) participation | | Reports | Shared | Reports and editions built from the system's evidence, with cutoffs and correction history | | Knowledge | Shared | Institutional knowledge, records, runbooks and learning linked to NXS-HUB | | Capabilities | Specialist | Records: capability, capability version, admission case, distribution projection | | Competence | Specialist | Records: competence profile, evaluation campaign, evaluation result, qualification | **Kinds of work it carries:** Capability packages; Capability evaluations; Capability Catalog; Admitted Package; Tool Manifest; Model Manifest; Agent Manifest; Entitlement Projection; In-house ML models; Foundation model admissions; RAG knowledge assistants; Edge model deployments; Agent fleets; Agentic workflow estates; Prompt & skill libraries; SaaS connector estates; OT & industrial connector estates; Tool & MCP catalogues; Capability bundles; Open-source intakes; Internal capability catalogues; Recall & revocation responses; Model risk inventories; Evaluation & red-team campaigns; Model drift watches; Model documentation backlogs; Training-data provenance reviews; Licence & entitlement estates; Vendor AI procurement reviews; Marketplace distributions. **This system in the Nexus model.** Generated from the Nexus Standards index and the programme spine; statuses are registry statuses, never adoption or certification. | | | | -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Descriptor | Software, packages, models, agents and capability lifecycle | | In the programme | Built, simulated and prepared in the [Foundry pillar](/organization/programme/foundry.md); its records serve the other pillars through the handoffs of [the programme year](/organization/programme/the-programme-year.md), and the competent authority decides outside the programme. | | System profile | [NRS-S5](https://nexustandards.com/standards/nrs/#nrs-s5): NXS-NXQ (Software, models and capability lifecycle) (status OPEN) | | Nexus Risk Standards that apply | 14 in 7 series: ai-native: [NRS-A3](https://nexustandards.com/standards/nrs/#nrs-a3), [NRS-A8](https://nexustandards.com/standards/nrs/#nrs-a8), [NRS-A9](https://nexustandards.com/standards/nrs/#nrs-a9); core: [NRS-C9](https://nexustandards.com/standards/nrs/#nrs-c9), [NRS-C14](https://nexustandards.com/standards/nrs/#nrs-c14); development: [NRS-D4](https://nexustandards.com/standards/nrs/#nrs-d4); programme: [NRS-E3](https://nexustandards.com/standards/nrs/#nrs-e3); intelligence: [NRS-I3](https://nexustandards.com/standards/nrs/#nrs-i3), [NRS-I7](https://nexustandards.com/standards/nrs/#nrs-i7); system: [NRS-S5](https://nexustandards.com/standards/nrs/#nrs-s5); technology: [NRS-T0](https://nexustandards.com/standards/nrs/#nrs-t0), [NRS-T1](https://nexustandards.com/standards/nrs/#nrs-t1), [NRS-T16](https://nexustandards.com/standards/nrs/#nrs-t16), [NRS-T17](https://nexustandards.com/standards/nrs/#nrs-t17) | | Nexus Reports technology streams | AIS AI and foundation models | ## Inputs What it receives, and from whom. Each interface carries its context (estate, tenant, workspace, purpose, jurisdiction, time and place) and is checked under the policy authority. | From | What it receives | | ------------------------------------------- | -------------------------------- | | [NXS-FAC](/organization/systems/nxs-fac.md) | signed package release/admission | | the shared intelligence runtime fabric | model/tool route decision | ## Outputs What it provides, and to whom. Consumers read projections; the system stays the authority for its own records and their corrections. | To | What it provides | | ------------------------------------------- | ----------------------------------------- | | [NXS-COR](/organization/systems/nxs-cor.md) | signed workload/package placement request | | [NXS-APP](/organization/systems/nxs-app.md) | admitted application/package capability | | [NXS-NSF](/organization/systems/nxs-nsf.md) | authorization/policy evaluation request | | the evidence fabric | append consequential receipt/evidence | ## Interfaces with other systems Beyond its interfaces, it relies on fact families owned elsewhere: application lifecycle ([NXS-APP](/organization/systems/nxs-app.md)); build signing authority ([NXS-FAC](/organization/systems/nxs-fac.md)); runtime authority spine (the runtime authority spine); trust root and key custody ([NXS-NSF](/organization/systems/nxs-nsf.md)). ## Areas it serves | Area | Category | What the area covers | | ---------------------------------------------------- | ---------- | ------------------------------------------------- | | [Sovereign AI](/organization/systems/areas.md) | Technology | National data environments and responsible AI | | [Digital governance](/organization/systems/areas.md) | Policy | AI, data and digital public infrastructure policy | ## Standards that apply Every record of the system is identified through the UNI identifier fabric of Nexus Standards (NS-1), and its public name follows the Nexus Standards naming rules. The areas it serves reference these external standards; naming a standard records where it is referenced and is not a claim of certification, accreditation, conformance or endorsement. | Standard | Issuer | Year | Use | | ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | ---- | ----------------------------------------- | | ISO/IEC 42001 Artificial intelligence management system | ISO/IEC | 2023 | Management system for responsible AI | | AI Risk Management Framework 1.0 | NIST | 2023 | Govern, map, measure and manage | | Artificial Intelligence Act, Regulation (EU) 2024/1689 | European Union | 2024 | Risk-based obligations where it applies | | Recommendation on the Ethics of Artificial Intelligence | United Nations Educational, Scientific and Cultural Organization (UNESCO) | 2021 | Human rights and ethics baseline | | Global Digital Compact | United Nations General Assembly | 2024 | Shared principles for digital cooperation | | Framework Convention on Artificial Intelligence and Human Rights, Democracy and the Rule of Law | Council of Europe | 2024 | Binding AI treaty framework | | OECD AI Principles, updated | OECD | 2024 | Trustworthy AI principles | | General Data Protection Regulation, Regulation (EU) 2016/679 | European Union | 2016 | Data protection benchmark | ## In the programme | Pillar | Room | What happens there | | -------------------------------------------------- | ---------- | -------------------------------------------- | | [Risk Academy](/organization/programme/academy.md) | Competence | Competence frameworks and role qualification | ## Governance boundaries Policy authority for the system sits with [NXS-NSF](/organization/systems/nxs-nsf.md); identifiers come from the UNI identifier fabric. The system exports read projections and commands through typed contracts, and no other system writes its records. It does not own, and never stands in for: * data ingestion, pipelines, lineage, canonical records and data products (NXS-NXS-GRX) * connector runs, credentials and schedules (NXS-NXS-GRX) * blueprints (Factory) * app runtime (Apps) * compute (NXS-NXS-COR) **Method boundary.** Qualification is task-, population- and version-specific. Keep evaluation uncertainty, coverage gaps and data leakage controls; admission cannot follow a generic success percentage alone. Do not reassign generic data-pipeline authority to NXS-NXQ merely because an older profile uses that wording. [All twenty systems](/organization/systems.md) ยท [Areas](/organization/systems/areas.md) *** *Generated page. It records names, roles and design for reading, not readiness: release is on hold, and nothing here is presented as ready, certified or official.* --- # 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/systems/nxs-nxq.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.