> 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-app.md). # NXS-APP NXS-APP, the application catalogue, installation, health and 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-APP** is one of the twenty systems of the Nexus ecosystem: the application catalogue, installation, health and 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 `Nexus Apps`. ## Purpose and context App runtime and app operations (never generation). Application lifecycle including the deployment actuator: desired state, rollout, traffic shifting, health-driven promotion, rollback and retirement (ADR 0141). Deploys only to targets approved by an NXS-NXS-COR placement decision, using a scoped deploy identity. Its domain is application installations, instances, dependencies, upgrades and recovery. A typical setting is a tenant application rolled out across staged environments with rollback constraints. ## 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-APP: application lifecycle. | Record | What the system must keep | | ---------------------- | ----------------------------------------------------------------------- | | installation | Bind application version and effective entitlement. | | environment refs | Separate test, preview, production and sovereign profiles. | | release digest | Resolve Factory release and NXS-NXQ admission references. | | health evidence | Distinguish configured health checks from observed service performance. | | rollback compatibility | Declare irreversible migrations and forward-recovery paths. | ## 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 | | Installations | Specialist | Records: application installation, installation plan, rollout policy, rollout execution, retirement record | | Recovery | Specialist | Records: application incident, diagnosis case, remediation plan, recovery operation, recovery verification | **Kinds of work it carries:** Applications; Environment rollouts; Installed Application; App Health; Upgrade Readiness; Dependency Posture; Application portfolios; Service portfolios; Installed application programmes; Environment fleets; Upgrade programmes; Hosting and platform migrations; Service level objective programmes; Application health monitoring; Observability programmes; Incident and on-call readiness; Dependency posture programmes; Configuration and drift programmes; Integration estates; Version support and patch currency; Application retirement programmes; Access and entitlement reviews; Software licence and cost estates. **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 | Application catalogue, installation, health and 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-S17](https://nexustandards.com/standards/nrs/#nrs-s17): NXS-APP (Application catalogue and lifecycle) (status OPEN) | | Nexus Risk Standards that apply | 5 in 3 series: ai-native: [NRS-A6](https://nexustandards.com/standards/nrs/#nrs-a6); system: [NRS-S17](https://nexustandards.com/standards/nrs/#nrs-s17); technology: [NRS-T8](https://nexustandards.com/standards/nrs/#nrs-t8), [NRS-T13](https://nexustandards.com/standards/nrs/#nrs-t13), [NRS-T16](https://nexustandards.com/standards/nrs/#nrs-t16) | | Nexus Reports technology streams | SFW Software and supply-chain integrity | ## 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-STU](/organization/systems/nxs-stu.md) | application composition artifact | | [NXS-NXQ](/organization/systems/nxs-nxq.md) | admitted application/package capability | | the estate and tenancy fabric | commercial entitlement | | [NXS-GRX](/organization/systems/nxs-grx.md) | correction and supersession propagation | ## 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-POR](/organization/systems/nxs-por.md) | external application projection | | the Station shared room | installed app instance state | | [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: tenancy account root (the estate and tenancy fabric); policy authority ([NXS-NSF](/organization/systems/nxs-nsf.md)); composition runtime ([NXS-STU](/organization/systems/nxs-stu.md)); build signing authority ([NXS-FAC](/organization/systems/nxs-fac.md)); trust root and key custody ([NXS-NSF](/organization/systems/nxs-nsf.md)); capability and package registry ([NXS-NXQ](/organization/systems/nxs-nxq.md)); runtime placement capacity attestation ([NXS-COR](/organization/systems/nxs-cor.md)). ## Areas it serves | Area | Category | What the area covers | | -------------------------------------------------- | ---------- | ---------------------------------------------- | | [Shared computing](/organization/systems/areas.md) | Technology | High-performance computing for annual missions | ## 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 27001 Information security management systems | ISO/IEC | 2022 | Security controls for shared environments | | NIST SP 800-88 Revision 2, Guidelines for Media Sanitization | NIST | 2025 | Sanitisation and validation | | EuroHPC Joint Undertaking access process | European High Performance Computing Joint Undertaking | 2018 | Comparator for review-based allocation | ## 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: * infrastructure estate, clusters, capacity pools and provider credentials (NXS-NXS-COR) * attestation verdict issuance (NXS-NXS-COR) * blueprint generation (Factory) * portals (Hub) * configuration (Studio) **Method boundary.** Rollout health must compare compatible cohorts and service windows. A rollback button cannot reverse an incompatible data migration; evidence must distinguish code rollback from data restoration. Do not treat a requested installation, health check and observed healthy application as one state. [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-app.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.