> 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-stu.md). # NXS-STU NXS-STU, the visual composition, dashboards, forms and workflow experiences 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-STU** is one of the twenty systems of the Nexus ecosystem: the visual composition, dashboards, forms and workflow experiences 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 Studio`. ## Purpose and context Configuration and composition (never deployment). Agent population and workflow orchestration product code, including project-scoped agent configuration; the project owner owns what each agent does (ADR 0140, amends ADR 0120). Its domain is visual composition, reusable experiences and Studio-owned agentic populations. A typical setting is a domain dashboard and bounded multi-agent workbench composed from admitted capabilities. ## 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-STU: composition runtime; agentic intelligence fabric. | Record | What the system must keep | | ------------------- | ---------------------------------------------------------------------- | | composition | Bind component tree, source references and view-specific state. | | component bindings | Validate data types, units, permissions and lifecycle compatibility. | | population template | Record roles, delegation boundaries, memory scopes and approved tools. | | preview profile | Isolate previews from live effects and production credentials. | | accessibility spec | Support keyboard alternatives, focus order and nonvisual outputs. | ## 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 | | Composer | Specialist | Records: experience composition, data binding, interaction binding, composition version, experience bundle | | Populations | Specialist | Records: population template, population version, population instance, agent task record, intervention record | **Kinds of work it carries:** Compositions; Reusable templates; Application Composition; Dashboard; Map Experience; Form/Workflow UI; Reusable Artifact; System compositions; Client applications; Partner embeds; Operations dashboards; Control-room displays; Map experiences; Data stories; Digital twin experiences; Workflow automations; Field data collection forms; Public service forms; Component libraries; Template libraries; Design system adoptions; Accessibility remediations; Interface modernisations; Localisation programmes. **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 | Visual composition, dashboards, forms and workflow experiences | | 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-S15](https://nexustandards.com/standards/nrs/#nrs-s15): NXS-STU (Composition, dashboards and workflows) (status OPEN) | | Nexus Risk Standards that apply | 4 in 4 series: intelligence: [NRS-I2](https://nexustandards.com/standards/nrs/#nrs-i2); system: [NRS-S15](https://nexustandards.com/standards/nrs/#nrs-s15); technology: [NRS-T3](https://nexustandards.com/standards/nrs/#nrs-t3); cross-cutting: [NRS-X5](https://nexustandards.com/standards/nrs/#nrs-x5) | | Nexus Reports technology streams | DTW Digital twins and simulation | ## 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-GRX](/organization/systems/nxs-grx.md) | data/product catalog projection; 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-APP](/organization/systems/nxs-app.md) | application composition artifact | | the Station shared room | workspace composition | | [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: consent authority ([NXS-NSF](/organization/systems/nxs-nsf.md)); delegation authority ([NXS-NSF](/organization/systems/nxs-nsf.md)); capability and package registry ([NXS-NXQ](/organization/systems/nxs-nxq.md)). ## Areas it serves | Area | Category | What the area covers | | ---------------------------------------------------- | ----------- | -------------------------------------------------------- | | [Exercises](/organization/systems/areas.md) | Management | Scenario exercises that test decisions before a crisis | | [Foresight](/organization/systems/areas.md) | Research | Emerging risks, horizon scanning and long-term scenarios | | [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 | | [Capacity building](/organization/systems/areas.md) | Development | Technical assistance and institutional skills | | [Leadership](/organization/systems/areas.md) | Development | Leaders, specialists and workforce capability | ## 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 | | ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | ---- | ------------------------------------------- | | Homeland Security Exercise and Evaluation Program (HSEEP) | FEMA | 2020 | Design, conduct, evaluation and improvement | | WHO Simulation Exercise Manual | World Health Organization (WHO) | 2017 | Health-emergency exercise types | | ISO 22301, clause 8.5 (exercising and testing) | ISO | 2019 | Exercising continuity arrangements | | ISO 31050 Guidance for managing emerging risks to enhance resilience | ISO | 2023 | Emerging-risk management | | Declaration on Future Generations | United Nations General Assembly | 2024 | Long-term thinking in policy | | Strategic Foresight for Better Policies | OECD | 2019 | Foresight in government practice | | 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 | | Capacity Development: A UNDP Primer | United Nations Development Programme (UNDP) | 2009 | Assessing and developing capacity | | The Challenge of Capacity Development: Working Towards Good Practice | OECD Development Assistance Committee | 2006 | Principles for capacity development | | ISO 30414 Human capital reporting | ISO | 2018 | Workforce capability reporting | | ISO 22301, clause 7.2 (competence) | ISO | 2019 | Competence for continuity roles | | Recommendation on Open Science | UNESCO | 2021 | Inclusive skills and participation | ## 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: * deployment (Apps) * artifact builds (Factory) * model provider credentials and routing (NXS-NXS-NXQ gateway) * tool brokers and tool/agent registries (NXS-NXS-NXQ) * sandbox compute (NXS-NXS-COR) * authorization decisions (NXS-NSF) * agent-owned domain facts (agents propose, domain systems commit) **Method boundary.** Agent evaluations must measure task success, policy violations, cost and uncertainty under bounded tools. Component validation must check data and interaction contracts, not just screenshot similarity. Do not treat a saved agent population definition as evidence that a qualified population is running. [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-stu.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.