> 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/programme/identifiers-and-records.md). # Identifiers and records Identifiers and records of the Nexus programme: one UNI under NS-1 for every object of the programme year, and the records each pillar owns. *Where this fits: applied response, as records. Pillars: all six. Institutions: GRF (cycle and mission records), GCRI Canada (publisher and issuer of record). Standard:* [*NS-1*](https://nexustandards.com/standards/ns-1/) *(PROPOSED). Kind: reference page.* **In brief.** Every object of the programme year (a cycle, a mission, a country profile, an edition, a course, a credential issuance, a participation) carries one identifier, a UNI under the Nexus Standard NS-1, so that it can be cited, versioned and resolved ([The UNI](https://nexustandards.com/uni/)). The programme spine names the template for each object but never mints identifiers itself: a UNI is allocated through a catalog, never typed by hand. NS-1 is at the PROPOSED stage, and a UNI never certifies anything; it identifies. Each pillar owns its records, listed below, and hands them on only through the recorded handoffs. ## Identifier templates | Object | Identifier template | Note | | ------------------------------- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | Annual cycle | `NXS-GRF-PR-` | One programme instance per cycle year, under the steward's scope; the year is a field, not part of the identifier. | | Cycle status | `NXS-GRF-RS-` | Phase and gate state of a cycle, append-only. | | Mission | `NXS-GRF-PR--` | A mission is a programme instance in a country (ISO 3166-1 alpha-3) or a region (UN M49). | | Country profile scope agreement | `NXS-NXO-PA--` | The country programme's agreement on profile scope, recorded before Q1. | | Country profile edition | `NXS-NXO-RP--@` | Published by GCRI Canada; a correction is a new version with a recorded reason. | | Regional profile edition | `NXS-NXO-RP--@` | Preserves the national sources it draws on. | | Technology stream brief | `NXS-NXO-RP--@` | Carries the stream's NS domain code (NS-1 section 1.1). | | Edition dataset | `NXS-GRX-DS--` | The permitted machine-readable bundle behind an edition. | | Course | `NXS-HUB-LS-@` | Every course names the systems, standards or roles it teaches. | | Credential issuance | `NXS-GCR-AT-` | An attestation by GCRI Canada as issuer of record; status is checked, never assumed. | | Participation | `NXS-GRF-PA-` | A participant's standing in a cycle, separate from any credential. | `` is the ISO 3166-1 alpha-3 country code and `` the UN M49 area code. A `@` suffix cites one state of a versioned record; citing without it cites the record as a whole. How a UNI is minted, embedded, cited and resolved is shown in [Nexus Standards](/organization/standards.md), with the text of [NS-1 and its companions on nexustandards.com](https://nexustandards.com/standards/), which govern. ## Records each pillar owns | Pillar | Records it owns | | --------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | Labs | experiment register; prototype record; working papers | | Foundry | Projects and builds; Observations and canonical data; Simulation and benchmark runs; The National Portfolio record; Evidence seals | | Nexus Universe | Cycle mandate; Mission admission decisions; Gate decisions G0 to G7; After-action records; Renewal decision | | Nexus Standards | UNI identifiers; Standards, clauses and profiles; Change proposals; National adoption records; Conformance evidence | | Nexus Reports | Editions and their evidence cutoff; Country and regional profiles; Technology stream briefs; Correction history | | Risk Academy | Learning pathways and courses; Cohorts and enrolments; Assessment evidence; Completion records; Credential issuance records | A record moves between pillars only through a recorded handoff, F01 to F14, written in a named room of a Foundry system, or around the ring, R1 to R4 ([Programme](/organization/programme.md)). Nothing crosses unrecorded. ## Read further * [The programme year](/organization/programme/the-programme-year.md): when each record is produced. * [Nexus Standards](/organization/standards.md): from minting to resolving a UNI. ## Sources * [Nexus Standards](/organization/institutions/nexus-standards.md), [The UNI](https://nexustandards.com/uni/) and [The standards](https://nexustandards.com/standards/), as of 2026-10-21. * Pillar model and programme spine of the sites (vendored in the documentation repository, `tools/figures/vendor/nexus-model`): the source of every generated table on this page. --- # 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/programme/identifiers-and-records.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.