- Код
NS-3- Название
- UNI записей о рисках (грамматика, сопоставление с прежними, орган выделения)
- Версия
- 0.1.0
- Статус
- ПРЕДЛОЖЕН
- Дата
- catalogue 2026-10-16 · circulated 17 October 2026
- Unique Nexus Identifier
NXS-STD-ST-000003- Область ответственности
- доверие; канонические данные
- Источник
standards/NS-3-grix-record-uni.mdat2cbe0d41b5f8
Подготовительный рабочий проект, распространённый для рецензирования и комментариев. Не для внедрения. Подготовлен и распространён Saeed Valadbaygi, главным распорядителем, Указатель Nexus Standards (saeed@therisk.global), 17 октября 2026 года. Область технической рецензии: TR-02. Настоящий документ не является Nexus Standard; он может быть изменён без уведомления, и его не следует внедрять, полагаться на него или ссылаться на него как на Nexus Standard. Его стадия определяется только Глобальным советом по стандартам (Global Standards Council) и его техническими комитетами в соответствии с NS-13. Получателям предлагается представить замечания с обоснованиями и сообщить о любых известных им патентных правах. См. уведомление о рассылке.
- Статус
- ПРЕДЛОЖЕН
- Владелец
- the trust and assurance system (standard) and NXS-GRX (records)
- Родительский элемент
NS-1-identifier-and-artifact-catalog.md- Эталонная реализация (nexus-foundry): библиотека
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. Грамматика
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 as well as @1.2.0; an artefact carries a semantic version, a record an integer. A ref with a semantic version is not a record ref.
| Вид | Код | Вид | Код |
|---|---|---|---|
| Факт наблюдения | OB | Версия хронотопа | CT |
| Выпуск источника | SR | Запись об исправлении | CR |
| Определение показателя | IN | Запись об аналитическом продукте | AP |
| Определение меры | ME | Subject (place, asset, organisation) | 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, optional during the transition).
Цитировать
NS-3, clause 3. NXS-STD-ST-000003@0.1.0. https://nexustandards.com/standards/ns-3/#nx-c-33. Allocation
Серийные номера никогда не выводятся и не вводятся вручную (NS1-R2). Они берутся из 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 role: serials shared across accounts, crosswalk private to the account, a forged scope writes nothing, mutation refused, the counter refused outside a scoped transaction, and the migration re-applies as a no-op.
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. Что меняется для путей приёма данных
- 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. Принятые пути
- 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? })crosswalks everyobs:unrisk:<key>@<version>ссылка гидратации на OB UNI (регион = ISO3 для гидратаций в границах страны) черезserver/unrisk/realDataRecordUni.tsи фиксирует результат вdata.uniAllocation(ALLOCATEDwith crosswalks,NOT_REQUESTED, orUNAVAILABLEс частичным прогрессом). Синхронный приём данных (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/runpasses it asuniScopeto the WDI bootstraps;UnriskFabricScope.accountIdis forwarded byrunUnriskFabricQuerythroughhydrateUnriskRealDataCompleteи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.
- Загрузка открытых данных (NS-3e):
server/grix/fusion/openData/openDataRecordUni.tsallocates an OB UNI for every observation the public-data plane writes (native indicators from World Bank, UNSD, WHO, IMF and the statistical adapters; public hazard events; Open-Meteo current, forecast and ensemble records) under the system-owned scope the plane already uses for SQL (accountACC-GRIX-PUBLIC-DATA, identitysystem:grix-public-data). REGION is the ISO3 dimension or country place ref; points and globals are unregioned. The legacyrecordUnistays 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 (пересылка подтверждённых учётных записей) и NS-3e (загрузка открытых данных) выполнены. Осталось: отдельный uni column on 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.
| Версия | Дата | Примечание |
|---|---|---|
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/.