GCRI · Registry
Public recordWhat the Nexus ecosystem publishes and runs, as data
Data and evidence record model
The record model of the Registry: the NS-1 identifier grammar, the 32 fields of an artefact record in the catalogue schema, and the flat record the snapshot publishes for all 12 types, each shown with a real example drawn from the snapshot.
01Identifier
The UNI is the key; every other identifier is a crosswalk from it.
Grammar version 0.2. One identifier per artefact concept; versions share it and differ after the at sign.
| Property | Value |
|---|---|
| Grammar | NXS-<SCOPE>-<CAT>[-<DOMAIN>][-<SECTOR>][-<REGION>][-<ENV>]-<SERIAL>[@<VERSION>] |
| Pattern | ^NXS-([A-Z]{3})-([A-Z]{2})((?:-(?:[A-Z]{3}|M[0-9]{3})){0,4})-([0-9]{6})(?:@([0-9]+(?:\.[0-9]+\.[0-9]+)?))?$ |
| URN form | urn:nexus:uni:{uni} |
| Record field | uni |
| Segment | Rule |
|---|---|
| SCOPE | three uppercase letters from scopes (a canonical system, an organisation or a cross-cutting scope) |
| CAT | two uppercase letters from categories (artefact type, mapped to Zenodo and DataCite resource types) or from recordCategories (NXS-GRX (canonical data, provenance and risk) record kinds, NS-3); the two lists never share a code |
| DOMAIN | optional; three-letter domain code from domains.yaml (WAT water, ENE energy, CLI climate, …) |
| SECTOR | optional; three-letter sector code from sectors.yaml (AGR agriculture, WUT water utilities, FNI finance and insurance, …) |
| REGION | optional; ISO 3166-1 alpha-3 country code (KEN, CAN) or UN M49 region as M + three digits (M002 = Africa), registry regions.yaml |
| ENV | optional; PRD, STG, LBX or FIX (deployment environment of a contextual record) |
| SERIAL | six digits, allocated per full prefix (SCOPE+CAT+context segments) by the catalogue (artefacts) or the UNI fabric (records), zero-padded, never reused |
| VERSION | optional; semantic version of an artefact (1.2.0) or the integer recordVersion of an NXS-GRX record (3); the identifier without version names the concept |
02Catalogue schema
The artefact record has 12 required fields.
From the published artefact record schema: Nexus artefact record (NS-1). A starred part of a structured field is required inside it.
| Field | Type | Use | Meaning and parts |
|---|---|---|---|
| uni | string | required | The UNI (Unique Nexus Identifier), NS-1 grammar, without @version. |
| displayAlias | string | optional | Public Registry short form (NX-R-47092) shown next to the UNI during the transition. |
| registryState | string | optional | Public registry state; corrections keep the UNI and add a version. Values: REGISTERED, Correction open, Rights hold, WITHDRAWN. |
| legacyUni | string | optional | Dotted UNI v0 this record replaces, for crosswalk (for example grix.eo.stac.catalogue). |
| title | string | required | |
| description | string | optional | |
| scope | string | required | |
| category | string | required | |
| region | string | optional | |
| domain | string | optional | DOMAIN segment code from the domain register (NS-1 v0.2); present when the identifier carries it. |
| sector | string | optional | SECTOR segment code from the sector register (NS-1 v0.2). |
| environment | string | optional | ENV segment code (NS-1 v0.2). Values: PRD, STG, LBX, FIX. |
| contextName | string | optional | NS-16 context name: the identifier without CAT and SERIAL; derived, never allocated. |
| systemId | string | optional | Canonical systemId from the public identity register when scope is a SYSTEM. |
| status | string | required | Values: DRAFT, PUBLISHED, SUPERSEDED, WITHDRAWN. |
| currentVersion | string | optional | |
| versions | array | optional | Parts: version*; date*; gitSha; digest; note. |
| creators | array | required | Parts: name*; type [Personal, Organisational, Agent]; affiliation; orcid; ROR. |
| publisherRef | string | required | Entity reference from the legal entity register; the institution stays publisher of record for institutional artefacts. |
| publicationDate | string | required | |
| language | string | optional | |
| keywords | array | optional | |
| rights | object | required | Parts: license*; rightsHolderRef; accessRight [open, embargoed, restricted, closed]; embargoDate. |
| legalState | string | required | Values: Legal review required, APPROVED, RESTRICTED, PROHIBITED. |
| supported claim level | string | required | Values: Fixture verified, Implementation complete, INTEGRATED, Lab observed. |
| locations | array | required | Parts: kind* [repoPath, URL, doi, storage]; value*; digest. |
| relatedIdentifiers | array | optional | Parts: relation* [IsPartOf, HasPart, IsDerivedFrom, IsSourceOf, IsSupplementTo, IsSupplementedBy, IsDocumentedBy, Documents, IsNewVersionOf, IsPreviousVersionOf, Cites, IsCitedBy, References, IsReferencedBy, Compiles, IsCompiledBy, Requires, IsRequiredBy, Obsoletes, IsObsoletedBy, IsVariantFormOf, IsIdenticalTo]; identifier*; identifierType [NXS, DOI, URL, ORCID, ROR, ISBN, arXiv, Handle, URN, Other]. |
| supersededBy | string | optional | |
| workPackageId | string | optional | |
| directiveRefs | array | optional | |
| notes | string | optional | |
| context | object | optional | NS-9: this record is a deployment, instance or programme instance of the concept ofUni, in a context. Parts: ofUni*; domains; sectors; jurisdictions; hostRef; environment [production, staging, lab, fixture]; validFrom; validUntil; conformsTo. |
03Snapshot record
One flat record for every type.
The snapshot keeps the same few fields on every record so that one table, one search and one export serve all twelve types.
| Field | Meaning |
|---|---|
| id | Stable registry id: the type, a colon and the type’s own key. Never reused. |
| kind | One of the twelve record types. |
| sub | A finer kind inside a type (the catalogue category code, work item, lesson). |
| uni | The NS-1 identifier where one is allocated. |
| title | The name as the source gives it. |
| status | The status word of the source register, lower case; see the status table on the records page. |
| scope | The organisational or structural scope: tier, scope code, legal class, faculty. |
| domain | The domain or discipline, where the source has one. |
| version | The version the source gives; a short digest for runtimes. |
| licence | The licence of the thing described, as its register states it; legal review required where none is recorded. |
| steward | The entity or system that stewards it, as the source names it. |
| URL | A public page for the record, only where one is built. |
| summary | One or two sentences from the source, never rewritten into a claim. |
| date | A date the source carries; the snapshot adds none. |
| evidence | Pairs of label and link: the issuing body, the licence, the site. |
| rel | Pairs of relation and the registry id of another record. |
| x | Fields particular to the type, such as bytes, integrity, page count or mix of implementation rows. |
04Examples
Two real records.
Both are read from the snapshot at build time.
A catalogue artefact, art:NXS-STD-ST-000001:
| Field | Value |
|---|---|
| id | art:NXS-STD-ST-000001 |
| kind | artefact |
| sub | ST |
| uni | NXS-STD-ST-000001 |
| title | Nexus Standards NS-1 – the UNI and artefact catalogue |
| status | draft |
| scope | STD |
| version | 0.1.0 |
| licence | LicenseRef-Nexus-Proprietary |
| steward | Legal review required |
| summary | Standard in the Nexus Standards themselves scope. |
| date | 2026-10-15 |
| type fields (x) | {"access":"restricted","supported claim level":"INTEGRATED","creators":"Legal review required","legalState":"Legal review required","workPackage":"LEGAL-NAME-ARCHITECTURE-001"} |
A consumer, Foundry, with its implementation status:
| Field | Value |
|---|---|
| id | Foundry |
| kind | consumer |
| title | Foundry |
| status | partly wired |
| scope | Implementation |
| summary | runtime (Foundry server, rooms, passports, The Global Risks Index (NXS-GRX) fabric) and catalogue for the system, organisation, LEG, GOV and PRG scopes |
| rel | [["implements (wired)","std:NS-1"],["implements (wired)","std:NS-3"],["implements (wired)","std:NS-3b"],["…","9 more relations"]] |
| type fields (x) | {"mergeState":"pending merge","note":"Implementation status, not readiness or certification.","planned":1,"wired":11} |
05Other record types
The standards define five further record schemas.
They apply to proposals, clauses, policies, attestations and subject passports, and are carried in the catalogue as UNI records of their own.
| Schema | Title | Required fields |
|---|---|---|
| nexus-attestation.v1.json | Nexus conformance attestation (NS-11) | uni, subjectUni, clauseUni, evaluatorRef, mandateRef, evaluatedAt, result, evidence, digest, supported claim level |
| nexus-clause.v1.json | Nexus clause (NS-10) | uni, title, status, modality, subjects, condition, evaluation, evidence, onFailure, authority, legalState, supported claim level |
| nexus-policy.v1.json | Nexus policy (NS-10) | uni, title, status, ownerRef, clauses, appliesTo, conformance, legalState, supported claim level |
| nexus-proposal.v1.json | Nexus standards proposal (NS-13) | uni, title, kind, status, proposerRef, openedAt, target, rationale, changes, legalState |
| nexus-subject-passport.v1.json | Nexus subject passport envelope (NS-15) | uni, passportVersion, durable, identityLevel, objectProfileId, representationRefs, contextUnis, relationships, chronotopeRef, evidenceRefs, policyAndReliance, correctionRefs, lifecycleState, limitations, supported claim level, certifiesTruth |
06Boundaries
What the model does and does not do.
- The model identifies and describes; it does not decide whether a record is true or may be used. Legal state and claim limit are honesty fields, not readiness claims.
- An identifier is never reused. A withdrawn record keeps its record, and a replaced one names its successor.
- The estate’s own consumers, surfaces and artefacts are being added to the Nexus Standards registry; the snapshot grows when it is regenerated. Snapshot 3.1.1, as of 2026-10-17, identifier 90a6a93b18a2bf3c.
07Sources
Where this page’s references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
08Questions
Questions and answers.
Why does the snapshot not use the catalogue schema for every type?
Only catalogue artefacts have the full schema. Sites, courses, sources and runtimes are described by their own registers, so the snapshot keeps the fields they have in common and carries the rest under one field.
Is the example the current record?
It is the record in Snapshot 3.1.1, as of 2026-10-17, identifier 90a6a93b18a2bf3c. A later snapshot may differ; the version history lists the changes.
Registry
Bring a method, a dataset or a question.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Legal
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.