- کوڈ
NS-1- Title
- UNI اور دستاویزات کا کیٹلاگ (قواعد v0.2: دائرہ، شعبہ، خطہ اور ماحول کے حصے)
- ورژن
- 0.1.0
- حیثیت
- مجوزہ
- تاریخ
- catalogue 2026-10-15 · circulated 17 October 2026
- Unique Nexus Identifier
NXS-STD-ST-000001- Responsible scope
- trust
- ماخذ
standards/NS-1-identifier-and-artifact-catalog.mdat2cbe0d41b5f8
Preparatory working draft, circulated for review and comment. Not for implementation. Prepared and circulated by Saeed Valadbaygi, Chief Steward, Nexus Standards (saeed@therisk.global), 17 October 2026. Technical review area: TR-02. This document is not a Nexus Standard; it may change without notice and is not to be implemented, relied upon or cited as a Nexus Standard. Its stage is designated only by the Global Standards Council and its technical committees under NS-13. Recipients are invited to submit comments with supporting reasons, and to notify any patent rights of which they are aware. See the notice of circulation.
- حیثیت
- مجوزہ
- Owner
- the trust and assurance system (trust, authorisation, policy and assurance;
NXS-S13) - Issuing fabric
- UNI identifier fabric
- Canonical home
- this repository
- Machine registry
registry/nexus-standards.yaml- Record schema
schemas/nexus-artifact-record.v1.json- STD catalogue
catalog/artifact-catalog.yaml- Reference CLI
node tools/nexus-id.mjs- Consumer implementations
registry/consumers.yaml
NS-1 gives every artefact the ecosystem produces one stable, machine-readable identifier, the UNI (Unique Nexus Identifier), and one catalogue record that says what the artefact is, who made it, who publishes it, what rights apply and where it lives. Code, services, schemas, datasets, models, reports, articles, figures, maps, lessons, policies and standards all follow the same scheme, so any agent, developer, researcher, machine or expert reader can find and cite an artefact the same way across all systems, rooms, runtimes, organisations and sites.
the trust and assurance system owns and versions the Nexus Standards. Every other system, site engine, editorial surface and agent applies them and never forks them. A UNI identifies and resolves; it never certifies truth, readiness or authority (V3 directive, section 12).
Cite
NS-1, clause 0. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-00. Where the standard lives
This repository is the canonical home of the Nexus Standards: the documents under standards/, the machine registry under registry/, the record schema under schemas/, the STD-scope catalogue under catalog/ and the reference CLI under tools/. Consuming repositories (nexus-foundry, the WordPress plugin, institutional sites) implement the standard, keep their own catalogues for their own scopes, and never fork the registry; registry/consumers.yaml lists them with their status. Paths written as server/..., src/... or scripts/... in this document are paths inside the nexus-foundry consumer.
Cite
NS-1, clause 1. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-11. The UNI
Grammar version 0.2 (context segments added 2026-10-16; every v0.1 identifier is unchanged and still valid).
NXS-<SCOPE>-<CAT>[-<DOMAIN>][-<SECTOR>][-<REGION>][-<ENV>]-<SERIAL>[@<VERSION>] NXS-EWS-DS-000042 dataset 42 of the early-warning system NXS-EWS-DS-KEN-000003 a Kenyan early-warning dataset NXS-GRX-RP-M002-000007@1.2.0 report 7 of the data system for Africa, version 1.2.0 NXS-GRX-AR-WAT-CAN-000012 article 12 of the data system on water in Canada NXS-GRX-DP-WAT-WUT-CAN-PRD-000001 production deployment 1 of the data system for Canadian water utilities (NS-9) NXS-GCR-AR-000015 an article published by GCRI Canada NXS-STD-ST-000001 this standard| Segment | فارم | Meaning |
|---|---|---|
NXS | fixed | Prefix. Chosen over NEX because it reads as a code, not a word; NEX- is crowded by brands (Nexo, Nexi, Nexor) and NXS is already the neutral system prefix in public-identity.json |
| SCOPE | three letters | A canonical system (EWS, EOP, SIG, GRX, OPS...), an organisation (GCR, GRF, GRA, NXO) or a cross-cutting scope (STD, LEG, GOV, PRG) |
| CAT | two letters | Artefact category, mapped to Zenodo upload and publication types and to DataCite resource types; or an NXS-GRX (canonical data, provenance and risk) record kind (OB, SR, IN, ME, BD, CT, CR, AP, SU, NS-3). The two lists never share a code |
| DOMAIN | optional, three letters | Nexus domain code from registry/domains.yaml (WAT water, ENE energy, FOO food, HLT health, BIO biodiversity, CLI climate, DRR, EWN, HUM, INF, SCH, SEC, ZTA, FNC, DSC, ERM, DRG, AIS, DAT, GSP, PRV, IDF, SFW, NAT, SDP, LIC; proposed: CMP, DTW, SNS, PNT) |
| SECTOR | optional, three letters | Sector code from registry/sectors.yaml (AGR, WUT, EUT, HSY, FNI, TRL, CIT, INM, DTC, PUB, RED, HUO, IGO) |
| REGION | optional | ISO 3166-1 alpha-3 (KEN, CAN) or UN M49 region as M + three digits (M002 Africa, M142 Asia); registry registry/regions.yaml |
| ENV | optional, three letters | PRD production, STG staging, LBX lab, FIX fixture; used by contextual records (NS-9) |
| SERIAL | six digits | Allocated by the catalogue or the UNI fabric per full prefix (SCOPE + CAT + context segments), never reused |
| VERSION | optional | Semantic version of an artefact (1.2.0) or the integer recordVersion of an NXS-GRX record (3, NS-3). The UNI without version names the concept |
Context segments. The four optional segments always appear in the order DOMAIN, SECTOR, REGION, ENV; each is a three-letter code from its registry, and the registries are pairwise disjoint and disjoint from the scope codes and the M49 form (checked by tools/nexus-id.mjs catalog validate), so an identifier parses deterministically without separators. The identifier without CAT and SERIAL is the context name, NXS-GRX-WAT-CAN: the data system, water domain, Canada. The context name is what articles, pages, datasets, deployments, dashboards and code about that context carry as their name (NS-16); their UNIs differ only in CAT and SERIAL. A context name is never allocated and never carries a serial; the NS-9 contextual record (DP or PR) is the record of truth for a context.
Machine forms: URN urn:nexus:uni:NXS-EWS-DS-000042; resolver path /uni/NXS-EWS-DS-000042 (HTML landing page for browsers, JSON for machines, /uni/<uni>.json always JSON; /uni lists published records); context path /ctx/NXS-GRX-WAT-CAN (every published record of that context); field name uni in every record, API, schema and table.
Existing dotted identifiers (grix.eo.stac.catalogue) are UNI v0. They are recorded as legacyUni on the new record for crosswalk and are never allocated again.
Cite
NS-1, clause 1.1. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-1-11.1 Context code allocation
Proposal NXS-STD-PC-000004 introduces this section and is OPEN; the rules apply to every code allocated from now on. Machine form: registry/nexus-standards.yaml identifier.codeAllocation. Check: node tools/nexus-id.mjs catalog validate.
A scope, domain, sector or environment code is a three-letter classification that machines parse and people never need to read. The allocation rules exist so that no code ever becomes ambiguous, including after future changes in other code lists.
| قاعدہ | Text |
|---|---|
| CA-1 | Three capital letters A–Z. No digits, and never the M + three digits form of UN M49. |
| CA-2 | Unique across every registry: scopes, domains, sectors, environments and ISO 3166-1 alpha-3. |
| CA-3 | Never one of the following, all listed in registry/regions.yaml, so a future country assignment cannot collide:• an ISO 3166-1 exceptionally, transitionally or formerly reserved code element; • a code in the user-assigned ranges ( AAA–AAZ, QMA–QZZ, XAA–XZZ, ZZA–ZZZ);• an ICAO Doc 9303 nationality code. |
| CA-4 | Mnemonic of the English label: the first letter of the label's head term, followed by consonants that keep the code recognisable. |
| CA-5 | Never a product name, a mark, a company name or a stock ticker, and never a word that reads as a brand. |
| CA-6 | One concept per code. Each code has a definition, what it includes and excludes, and the external standards it crosswalks to. |
| CA-7 | Ids are stable, lowercase kebab-case English. Labels are in sentence case. Neither encodes a status. |
| CA-8 | Append-only. A code is never reassigned or deleted. A retired code keeps its entry with deprecated: true and supersededBy. |
| CA-9 | A new code stays PROPOSED, with its proposal UNI, until the Global Standards Council adopts the registry change. Consumers may use a PROPOSED identifier but must show its status. |
| CA-10 | Adding a code is a minor, additive registry version. Changing what a code means is a major change and needs a crosswalk. |
Grandfathered: AAP, the system scope of the anticipatory-action system. It was allocated before CA-3 and lies inside the user-assigned range AAA–AAZ. It stays, under CA-8.
Technology domains proposed under these rules:
| کوڈ | Id | لیبل | Crosswalks to |
|---|---|---|---|
CMP | compute | Compute and accelerated infrastructure | ISO/IEC JTC 1/SC 38 and SC 39; ISO/IEC 22123 |
DTW | digital-twins | ڈیجیٹل جڑواں اور نقلی مشقیں | ISO/IEC 30173:2023; ISO/IEC JTC 1/SC 41; ISO 23247 |
SNS | sensing | Sensing and measurement networks | OGC SensorThings API and SensorML; W3C/OGC SOSA/SSN; IEEE 1451 |
PNT | pnt | مقام کا تعین، رہنمائی اور وقت بندی | IEEE 1588; ITU-T G.8271 and G.8272; ITU-R TF series; UN ICG |
Sensing and positioning-navigation-timing are separate codes because different communities standardise them: sensor and observation encodings on one side, timing and GNSS profiles on the other. A technology stream that covers both carries SNS and lists PNT as related.
A future quantum-technology code cannot be QTM or QNT, because both fall in the user-assigned range QMA–QZZ. CA-3 catches this kind of collision before allocation.
Cite
NS-1, clause 2. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-22. Scope codes
| نظام | کوڈ | نظام | کوڈ | |
|---|---|---|---|---|
| nexus (posture, executive synthesis) | CMD | sig (signal, timing, PNT) | SIG | |
| northstar (common operating picture) | NST | nsf (trust, authorisation) | the trust and assurance system | |
| dss (decisions) | DSS | hub (knowledge, records) | HUB | |
| nexcore (compute, runtimes) | COR | studio (composition, workflows) | STU | |
| nexq (packages, models, capabilities) | NXQ | factory (builds, signing) | FAC | |
| grix (data, provenance, risk) | GRX | apps (application lifecycle) | APP | |
| eop (earth observation) | EOP | rails (agreements, protocols) | RLS | |
| ews (early warning) | EWS | portals (public, client, partner delivery) | POR | |
| aap (anticipatory action) | AAP | labs (research, simulations) | LAB | |
| net (network continuity) | NET | |||
| op (instruments, calibration) | OPS |
Organisations: GCR The Global Centre for Risk and Innovation (GCRI Canada) · GRF The Global Risks Forum · GRA The Global Risks Alliance · NXO the consortium · ELP and OBS reserved organisation scopes (withdrawn before use; parseable, never issued). Cross-cutting: STD standards · LEG legal and IP · GOV governance · PRG programme · UXK UI/UX kit · ALL ecosystem-wide.
Scope codes are classification, not names. Public labels follow the name architecture standard (nexus-foundry the network's own records); the trust and assurance system as a code is fine, "the trust and assurance system" as a public product name is not. The canonical systemId and neutralId stay unchanged.
Cite
NS-1, clause 3. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-33. Category codes
| کوڈ | Artefact | Zenodo | DataCite |
|---|---|---|---|
| SW | Software | software | Software |
| SV | Service or API | software | Service |
| SC | Schema or contract | other | دیگر |
| MG | Database migration | software | Software |
| WF | Workflow | workflow | Workflow |
| MD | ماڈل | model | ماڈل |
| DS | Dataset | dataset | Dataset |
| EV | شواہد کا ریکارڈ | dataset | Dataset |
| AR | مضمون | publication / article | JournalArticle |
| PP | Preprint | publication / preprint | Preprint |
| RP | رپورٹ | publication / report | رپورٹ |
| TN | Technical note | publication / technicalnote | Text |
| DC | دستاویزات | publication / softwaredocumentation | Text |
| DL | Deliverable | publication / deliverable | رپورٹ |
| WP | Working paper | publication / | Text |
| BK | Book or chapter | publication / book | Book |
| CP | Conference paper | publication / conferencepaper | ConferencePaper |
| TH | Thesis | publication / thesis | Dissertation |
| PT | Patent | publication / patent | دیگر |
| ST | معیار | publication / other | معیار |
| PC | Policy or directive | publication / other | Text |
| PS | Presentation | presentation | Text |
| PO | Poster | poster | Text |
| FG | شکل | image / figure | Image |
| PL | Plot or visualisation | image / plot | Image |
| DG | Diagram | image / diagram | Image |
| PH | Photo | image / photo | Image |
| MP | Map product | image / other | Image |
| VD | Video | video | Audiovisual |
| LS | Lesson or course | lesson | InteractiveResource |
| PY | Physical object | physicalobject | PhysicalObject |
| PA | Participation record | other | دیگر |
| RS | Programme status record | other | دیگر |
| OT | دیگر | other | دیگر |
node tools/nexus-id.mjs export <uni> --format zenodo produces Zenodo deposition metadata; --format datacite produces a DataCite-shaped record, so a catalogued artefact can be deposited or minted a DOI without re-describing it.
Cite
NS-1, clause 3.1. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-3-13.1 The public Registry crosswalk
The registry at therisk.global/nexus-registry/ (publisher GCRI Canada) shows record ids NX-R-nnnnn (programme status), NX-P-nnnnn (publication), NX-E-nnnnn (evidence) and NX-C-nnnnn (participation) with a version, a hash and a state. Those forms become display aliases of UNIs: NX-R-47092 → NXS-GCR-RS-047092, NX-P → RP (or AR, PP, WP when the record says so), NX-E → EV, NX-C → PA. The registry version becomes currentVersion, the hash versions[].digest, the state registryState (REGISTERED, CORRECTION_OPEN, RIGHTS_HOLD, WITHDRAWN). The page says no public record has been released yet, so nothing live breaks. Full rule: registry/nexus-standards.yaml#registryCrosswalk.
Cite
NS-1, clause 4. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-44. The record
Each UNI has one record in the catalogue (schema: nexus-artifact-record.v1.json). Required: uni, title, scope, category, status, creators, publisherRef, publicationDate, rights, legalState, claimCeiling, locations. Optional: region, systemId, legacyUni, description, keywords, language, currentVersion, versions (with git SHA and sha256 digest), relatedIdentifiers (DataCite relation types, so parts, derivations, supersessions and citations form a graph), supersededBy, workPackageId, directiveRefs.
Assurance fields: legalState defaults to LEGAL_REVIEW_REQUIRED; claimCeiling never exceeds the claim registry (FIXTURE_VERIFIED, IMPLEMENTATION_COMPLETE, INTEGRATED, LAB_OBSERVED); publisherRef is the institution for institutional artefacts (the institution stays publisher of record; ownership of the technology does not make its owner the publisher).
Cite
NS-1, clause 5. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-55. Rules
| قاعدہ | Text |
|---|---|
NS1-R1 | One UNI per artefact concept; versions share the UNI and differ in @VERSION |
NS1-R2 | UNIs are allocated only through the catalogue (mint); never typed by hand |
NS1-R3 | UNIs are never deleted or reused. Withdrawn artefacts keep their record (WITHDRAWN); replaced ones record supersededBy |
NS1-R4 | Every record carries the required metadata; legalState defaults to review-required; claimCeiling stays inside the claim registry |
NS1-R5 | The UNI is embedded in the artefact itself so machines and people can find the record (section 6) |
NS1-R6 | Regional artefacts carry REGION; public regional or national use still follows the name architecture's geographic rules |
NS1-R7 | Codes are classification, never product names |
NS1-R8 | New scope, domain, sector and environment codes meet the allocation rules CA-1 to CA-10 (section 1.1) and enter through an NS-13 proposal |
NS1-R9 | A code is never reassigned or deleted; a retired code is deprecated with supersededBy, and identifiers that use it stay valid |
NS1-R10 | A PROPOSED identifier may be used and is shown with its status until the registry change is adopted |
Cite
NS-1, clause 6. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-66. Embedding: how each surface carries the UNI
| Surface | Owner | How |
|---|---|---|
| Source files | the trust and assurance system | Header comment Nexus-UNI: <uni> |
| Documents and reports | HUB | Front matter uni: or first line Nexus-UNI: <uni> |
| Datasets and products | GRX | Sidecar <file>.uni.json with the record, or a uni key in STAC and DataCite metadata |
| Figures and maps | EOP | Caption suffix [<uni>] and image metadata |
| Foundry HTTP APIs | the trust and assurance system | Response header X-Nexus-UNI: <uni> on every JSON response whose body carries a uni (server/middleware/uniHeader.ts); GET /api/uni/catalog, GET /api/uni/:uni, GET /api/uni/:uni/export?format=zenodo|datacite|schema-org|codemeta|citation-cff|stac|dcat|prov under the trust and assurance system scope; public GET /uni/:uni for PUBLISHED, non-restricted records with Schema.org JSON-LD |
| Rooms and panels | STU | Room-binding projects the payload uni (or uniKey) per source and shows it as a link; any cell that is a UNI links to /uni/<uni>; the trust and assurance system room's Standards surface reads the catalogue (ns6StandardsRoomDefinitions.ts) |
| Passports | GRX | PASSPORT_UNI_FIELD (nexus:uni) is the first field of the shared Identity section; format uni links valid UNIs to /uni/<uni> and shows legacy dotted ids unlinked; the account passport links its registered UNI |
| Landing and Trust pages | POR | <meta name="nexus-uni" content="<uni>"> and data-nexus-uni on the component root |
| WordPress plugin and institutional sites | POR | Post meta _nexus_uni (validated; uni in the provenance REST body), <meta name="nexus-uni"> and X-Nexus-UNI are wired in the plugin (the network's own records); block attribute nexusUni follows in NS-6. See nexus-foundry the network's own records |
| Agents | the trust and assurance system | Mint through the CLI and embed the UNI in every artefact produced |
Every surface in registry/nexus-standards.yaml#surfaces has a status. A surface without a declared embedding is non-compliant; PLANNED means the hook is specified and not yet wired. NS-6 wired the API header and routes, rooms and passports; landing-page meta tags and JSON-LD follow with the resolver pages (NS-7).
Cite
NS-1, clause 7. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-77. Commands
node tools/nexus-id.mjs validate NXS-EWS-DS-000042 node tools/nexus-id.mjs parse NXS-GRX-RP-M002-000007@1.2.0 node tools/nexus-id.mjs next --scope EWS --category DS --region KEN node tools/nexus-id.mjs mint --scope EWS --category DS --title "Kenya flood observations 2026" \ --path the approved sources of the network --region KEN --publisher GCRI_CANADA --work-package RF-21 node tools/nexus-id.mjs catalog validate # npm run validate node tools/nexus-id.mjs catalog list --scope GRX node tools/nexus-id.mjs export NXS-STD-ST-000001 --format zenodoCite
NS-1, clause 8. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-88. The open-standards stack
registry/open-standards-stack.yaml fixes the external standards and indexes under the UNI. the network's own records crosswalks a record to Zenodo deposition metadata, DataCite 4.5, Schema.org JSON-LD (for landing pages and Google Dataset Search), CodeMeta 3.0 and CITATION.cff; zenodoClient.ts deposits to Zenodo (sandbox by default, dry-run by default, token supplied by the publishing institution) after the legal gate zenodoDepositEligibility (APPROVED, open or embargoed, SPDX licence). The returned DOI is written back as relatedIdentifiers[IsIdenticalTo, DOI], so the UNI stays the key and the DOI is the citable crosswalk. Zenodo is registered in the network's legal texts#zenodo and external-apis.yaml#zenodo.deposit at LEGAL_REVIEW_REQUIRED.
Runtime hooks (NS-6): room-binding sources accept uniKey, every RoomSourceProjection carries uni and the room view links it; passports carry PASSPORT_UNI_FIELD in the shared Identity section with format uni; every JSON API response with a uni carries X-Nexus-UNI; /api/uni serves the catalogue and exports. The Global Risks Index (NXS-GRX) recordUni adopts the NS-1 grammar for new records with dotted ids kept as legacyUni (NS-3).
Cite
NS-1, clause 9. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-99. Relationship to the other standards
- Name architecture (
the network's own records): public display names and trademark safety. NS-1 is the machine layer underneath it; the two never contradict because codes are never names. - Claim registry (
the network's own records):claimCeilingon every record. - Legal registers (
the network's legal texts/**):legalState,publisherRef,rights.license. - UNI identifier fabric (V3 directive section 12): artefacts are allocated by the catalogue file (reconstructable source, served by
/api/uniand/uni); NXS-GRX records are allocated by PostgreSQLnexus_uni(NS-3,the network's own records). - Work items: every work item lists the UNIs it creates or changes in
evidenceOutputs.
Cite
NS-1, clause 10. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-1010. Follow-on packages
Delivered: NS-3 NXS-GRX record UNIs (allocation, grammar, crosswalk; WDI bootstrap in use), NS-3b STAC, DCAT and PROV-O profile (the network's own records), NS-6 surface wiring, NS-7 resolver landing pages. Open: NS-2 citation and attribution format · per-path adoption of the record allocator (realDataObservationIngest, open-data ingests) · NS-4 document template with uni front matter · NS-5 figure, map and visualisation standard (with the UI/UX kit) · NS-7b SPA landing-page meta tags and sitemap · NS-8 Zenodo publishing workflow with legal gate, DOI write-back and Software Heritage archival.
Change history
Versions from the catalogue; entries from the changelog that name this document.
| ورژن | تاریخ | Note |
|---|---|---|
0.1.0 | 15 October 2026 | current version in the catalogue |
- Unreleased NS-13 proposal
NXS-STD-PC-000004(OPEN; last call ends 2026-11-16), the first proposal held as a record underproposals/and checked bynpm run validate: NS-1 section 1.1 sets context code allocation rules CA-1 to CA-10 and rules NS1-R8 to NS1-R10. ISO 3166-1 reserved and user-assigned code elements and ICAO Doc 9303 codes are now refused.AAPis grandfathered. It proposes four technology domain codes:CMPcompute and accelerated infrastructure,DTWdigital twins and simulation,SNSsensing and measurement networks, andPNTpositioning, navigation and timing. The domains registry becomes schemaVersion 1.1.0 (minor, additive). - 0.1.0 – 2026-10-16 NS-1 (the UNI and the artefact catalogue), NS-3 (NXS-GRX record UNIs) and NS-3b (STAC, DCAT, PROV-O profile) as PROPOSED documents under
standards/.