- Code
NS-3- शीर्षक
- जोखिम अभिलेख UNI (व्याकरण, पुरानी प्रणाली से मिलान, आवंटन प्राधिकार)
- संस्करण
- 0.1.0
- स्थिति
- प्रस्तावित
- Date
- catalogue 2026-10-16 · circulated 17 October 2026
- Unique Nexus Identifier
NXS-STD-ST-000003- उत्तरदायित्व का दायरा
- विश्वास; मानक डेटा
- स्रोत
standards/NS-3-grix-record-uni.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.
- स्थिति
- प्रस्तावित
- स्वामी
- the trust and assurance system (standard) and NXS-GRX (records)
- Reference implementation (nexus-foundry): library
the network's own records, storeserver/grix/uni/recordUniStore.ts, migrationthe network's own records, proofthe network's own records
NS-1 gives artefacts (software, reports, datasets, figures) a UNI allocated by the catalogue. NS-3 gives NXS-GRX records (observation facts, source releases, indicators, boundaries, chronotopes, corrections, analytical products, subjects) a UNI allocated by the UNI fabric in PostgreSQL, on the same grammar, so a record can be cited, resolved and crosswalked like any other Nexus artefact. A UNI identifies and resolves a record; it never certifies the record's truth (V3 directive, section 12).
उद्धरण दें
NS-3, clause 1. NXS-STD-ST-000003@0.1.0. https://nexustandards.com/standards/ns-3/#nx-c-11. Grammar
NXS-GRX-<KIND>[-<REGION>]-<SERIAL> the record concept (ObservationFact.recordUni) NXS-GRX-<KIND>[-<REGION>]-<SERIAL>@<version> one record version (recordUni@recordVersion) NXS-GRX-OB-KEN-000042@3 observation fact 42 for Kenya, version 3 NXS-GRX-SR-000001 source release 1 (global)The version segment is the NXS-GRX integer recordVersion. NS-1 v1.1 therefore accepts @3 साथ ही @1.2.0; an artefact carries a semantic version, a record an integer. A ref with a semantic version is not a record ref.
| प्रकार | Code | प्रकार | Code |
|---|---|---|---|
| प्रेक्षण तथ्य | OB | क्रोनोटोप संस्करण | CT |
| स्रोत संस्करण | SR | सुधार अभिलेख | CR |
| संकेतक की परिभाषा | IN | विश्लेषणात्मक उत्पाद अभिलेख | AP |
| माप की परिभाषा | ME | विषय (स्थान, परिसंपत्ति, संगठन) | SU |
| सीमा संस्करण | BD |
Record kinds and artefact categories never share a code (registry/nexus-standards.yaml#recordCategories; tools/validate.mjs and the consumer unit test enforce it).
उद्धरण दें
NS-3, clause 2. NXS-STD-ST-000003@0.1.0. https://nexustandards.com/standards/ns-3/#nx-c-22. Legacy ids stay valid
NXS-GRX already carries record ids such as obs:unrisk:<key>, uni:source:worldbank.wdi, uni:indicator:<code> and dotted ids such as grix.eo.stac.catalogue. They parse as LEGACY, keep working in <ref>@<version> refs (parseRecordRef, now used by the governed risk data-cut binder), and are crosswalked to an NS-1 UNI when allocated. Nothing is renamed in place; a record either carries an NS-1 recordUni (new records) or a legacy recordUni plus the allocated uni (ObservationFact.uni, संक्रमण अवधि के दौरान वैकल्पिक)।
उद्धरण दें
NS-3, clause 3. NXS-STD-ST-000003@0.1.0. https://nexustandards.com/standards/ns-3/#nx-c-33. आवंटन
Serials are never derived or typed by hand (NS1-R2). They come from nexus_uni.allocate_record_serial(scope, category, region), an atomic counter per (GRX, kind, region) in nexus_uni.record_serial_sequence, advanced only inside a scoped tenant transaction (or the platform bypass). Every allocation is one append-only row in nexus_uni.record_uni_allocation (tenant, workspace, account, UNI, kind, region, serial, legacy_uni, verified principal). The legacy id is the idempotency key within an account: allocating the same legacy id twice returns the same UNI with reused: true. UNIs are never reused or reassigned: UPDATE, DELETE and TRUNCATE raise UNI_RECORD_ALLOCATION_IMMUTABLE, and a CHECK keeps the UNI string equal to its segment columns.
पृथक्करण रिपॉज़िटरी के FORCE RLS पैटर्न का अनुसरण करता है (v956 खाता-स्कोप युग्म, प्रणालीगत स्कोप गार्ड, v959 सदस्यता गार्ड)। काउंटरों में किसी टेनेंट का डेटा नहीं होता; उन्हें किसी भी स्कोप से पढ़ा जा सकता है। इंटीग्रेशन परीक्षण वास्तविक PostgreSQL पर सिद्ध करता है, एक NOSUPERUSER NOBYPASSRLS भूमिका: खातों में साझा क्रमांक, खाते तक सीमित निजी मिलान, जाली दायरा कुछ नहीं लिखता, परिवर्तन अस्वीकृत, दायरे वाले लेन-देन के बाहर काउंटर अस्वीकृत, और माइग्रेशन दोबारा लागू होने पर कोई प्रभाव नहीं डालता।
const store = resolveRecordUniStore(); const { uni, reused } = await store.allocate(scope, { kind: "OB", region: "KEN", legacyUni: "obs:unrisk:wdi.KEN.SP.POP.TOTL.2020" }); // uni = "NXS-GRX-OB-KEN-000042"; ref for version 3: formatRecordRef(uni, 3)Offline is a typed 503 (AuthoritativeStoreUnavailableError); there is no memory fallback.
उद्धरण दें
NS-3, clause 4. NXS-STD-ST-000003@0.1.0. https://nexustandards.com/standards/ns-3/#nx-c-44. What changes for ingest paths
- New records: allocate through the store at write time and store the NS-1 form in
recordUni. - Existing paths (
obs:unrisk:…inserver/unrisk/realDataObservationIngest.tsand the others): unchanged until each path is migrated; they can allocate and setunion the fact without changing theirrecordUnikey. - संदर्भ: इनसे निर्मित
formatRecordRef(recordUni, recordVersion)and read withparseRecordRef(ref); both forms are accepted so correction dependencies keep resolving across the transition.
उद्धरण दें
NS-3, clause 4a. NXS-STD-ST-000003@0.1.0. https://nexustandards.com/standards/ns-3/#nx-c-4a4a. Adopted paths
- WDI bootstrap (CGRIC-03): allocates SR and OB UNIs with a verified
uniScope;WdiBootstrapResult.uniAllocation. - Real-data hydration (
server/unrisk/realDataHydration.ts, NS-3c):hydrateUnriskRealData(context, { uniScope: { accountId }, recordUniStore? })हर एक का मिलान करता हैobs:unrisk:<key>@<version>ref of the hydration to an OB UNI (region = ISO3 for country-scoped hydrations) throughserver/unrisk/realDataRecordUni.tsऔर परिणाम को इसमें दर्ज करता हैdata.uniAllocation(ALLOCATEDwith crosswalks,NOT_REQUESTED, orUNAVAILABLEwith partial progress). The synchronous ingest (realDataObservationIngest.ts) keeps its legacy keys; the data cut and consumers keep matching them, and a product's PROV-O bundle maps both forms (NS-3b). The envelope's requester carries no account id, so callers supply it (NS-3d below); without it hydration reportsNOT_REQUESTED.
- Verified account forwarding (NS-3d):
server/standards/verifiedUniScope.tsreads{ accountId, principalId }from the request's verified claims only; a header, body or query account is never authority, and theacct:<tenant>the authority context synthesises is never used.POST /source-bootstrap/runइसे इस रूप में आगे भेजता हैuniScopeto the WDI bootstraps;UnriskFabricScope.accountIdद्वारा अग्रेषित किया गया हैrunUnriskFabricQuerythroughhydrateUnriskRealDataCompleteऔरhydrateUnriskRealDataExtendedtohydrateUnriskRealData. The fabric query, NEIF mission-agent, data-agent and Commons agent-team routes and the hex-intel UNRISK contributor forward it; the Builder v2 UNRISK tool does not (its scope accepts a header account, NS3D-G1). Without a claim every path staysNOT_REQUESTED.
- Open-data ingests (NS-3e):
server/grix/fusion/openData/openDataRecordUni.tsसार्वजनिक-डेटा तल द्वारा लिखे गए प्रत्येक प्रेक्षण के लिए एक OB UNI आवंटित करता है (World Bank, UNSD, WHO, IMF और सांख्यिकीय एडेप्टरों से मूल संकेतक; सार्वजनिक संकट घटनाएँ; Open-Meteo के वर्तमान, पूर्वानुमान और एन्सेम्बल अभिलेख) उस सिस्टम-स्वामित्व वाले दायरे के अंतर्गत जिसे यह तल SQL के लिए पहले से उपयोग करता है (accountACC-GRIX-PUBLIC-DATA, identitysystem:grix-public-data)। REGION ISO3 आयाम या देश का स्थान संदर्भ है; बिंदु और वैश्विक मान क्षेत्र-रहित हैं। पुरानाrecordUnistays the fabric key; the UNI rides on the stored fact (durable file and the PostgreSQL record payload), is kept across corrections, and a current version written before NS-3e receives its UNI on its next correction through the legacy crosswalk. Unchanged rows cost no fabric round-trip. A fabric outage never blocks an observation write: the first typed outage trips a per-pass circuit and the receipt'suniAllocationरिपोर्टUNAVAILABLEwith the partial counts; any other scope isNOT_REQUESTED.
उद्धरण दें
NS-3, clause 5. NXS-STD-ST-000003@0.1.0. https://nexustandards.com/standards/ns-3/#nx-c-55. Follow-on
NS-3b delivered (NS-3b-dataset-and-product-metadata-profile.md). NS-3d (verified account forwarding) and NS-3e (open-data ingests) delivered. Remaining: a dedicated uni स्तंभ चालू grix_chrono.observation_facts so the UNI is queryable without reading the record payload; the Builder v2 scope becomes claims-only so its tool can forward too.
परिवर्तन इतिहास
Versions from the catalogue; entries from the changelog that name this document.
| संस्करण | Date | टिप्पणी |
|---|---|---|
0.1.0 | 16 अक्टूबर 2026 | current version in the catalogue |
- 0.1.0 – 2026-10-16 Canonical repository bootstrapped from the standards first drafted inside nexus-foundry (work items LEGAL-NAME-ARCHITECTURE-001, NS-3-7-RECORD-UNI-RESOLVER-001, NS-3B-DATA-PROFILE-001).
- 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/.