- کد
NS-9- عنوان
- UNIهای زمینهای (استقرارها، نمونهها، نمونههای برنامه)
- نسخه
- 0.1.0
- وضعیت
- پیشنهادشده
- تاریخ
- catalogue 2026-10-16 · circulated 17 October 2026
- Unique Nexus Identifier
NXS-STD-ST-000005- دامنهٔ مسئول
- اعتماد
- منبع
standards/NS-9-contextual-uni.mdat2cbe0d41b5f8
پیشنویس کاری مقدماتی، منتشرشده برای بازبینی و ارائهٔ نظر. برای اجرا نیست. تهیه و منتشرشده توسط Saeed Valadbaygi، متولی ارشد، Nexus Standards (saeed@therisk.global)، 17 اکتبر 2026. حوزهٔ بازبینی فنی: TR-02. این سند یک Nexus Standard نیست؛ ممکن است بدون اطلاع قبلی تغییر کند و نباید بهعنوان Nexus Standard اجرا، مورد اتکا یا استناد قرار گیرد. مرحلهٔ آن تنها از سوی شورای جهانی استانداردها و کمیتههای فنی آن ذیل NS-13 تعیین میشود. از دریافتکنندگان دعوت میشود نظرات خود را همراه با دلایل پشتیبان ارائه کنند و هرگونه حق ثبت اختراعی را که از آن آگاهاند اعلام کنند. اطلاعیهٔ توزیع را ببینید.
- وضعیت
- پیشنهادشده
- مالک
- نظام اعتماد و اطمینان
- اساسنامه
NS-0-constitution-and-principles.md
A system, component, product or service exists once as a concept and many times in context: the early-warning system deployed for Kenya's water sector, the same system for a Sahel food-security programme, a data product published for an African region, a command room instance for one host city. NS-9 gives each context its own UNI, so that a page, a passport, a report, a policy, a clause or a monitoring record can name exactly which deployment it is about, while the concept keeps one UNI and the public name never changes with context and never infringes a mark.
استناد کنید
NS-9, clause 1. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-11. Grammar (unchanged)
NS-9 adds no segment to the NS-1 grammar. A contextual UNI is an ordinary NS-1 identifier whose category is a context category and whose REGION segment carries the geography:
NXS-<SCOPE>-DP[-<REGION>]-<SERIAL> a deployment or instance of a system or component NXS-<SCOPE>-PR[-<REGION>]-<SERIAL> a programme or engagement instance (a pathway run in a context) NXS-EWS-DP-KEN-000001 deployment 1 of the early-warning system in Kenya NXS-EWS-DP-M011-000003 deployment 3 of the early-warning system in Western Africa (UN M49 011) NXS-GRX-DP-000002 a global deployment of the data system (no region) NXS-GCR-PR-COL-000001 GCRI programme instance 1 in ColombiaWith NS-1 grammar v0.2 a contextual UNI also carries the domain, sector and environment of the context as segments, so the identifier alone names the context: NXS-GRX-DP-WAT-WUT-CAN-PRD-000001 is production deployment 1 of the data system for Canadian water utilities, and its context name NXS-GRX-WAT-WUT-CAN-PRD (the identifier without CAT and SERIAL) is the name every page, article, dataset and dashboard about that deployment carries (NS-16). The context object below stays the record of truth: finer jurisdictions, several domains or sectors, the host and the validity window live there, and the segments in the identifier are the primary ones.
DP (deployment or instance) and PR (programme instance) are new artefact categories in registry/nexus-standards.yaml#categories (append-only, NS1-R3). Zenodo and DataCite mappings are other/Other: a deployment is catalogued, not deposited, unless its evidence is published separately.
استناد کنید
NS-9, clause 2. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-22. The context record
A contextual record is an NS-1 record (schema v1.1) with a context object:
| حوزه | معنا |
|---|---|
context.ofUni | مفهومی که زمینه آن را مصداق میدهد: سامانه، مؤلفه، محصول یا برنامهٔ UNI (الزامی). این سابقه همچنین شامل موارد زیر است relatedIdentifiers[IsPartOf, <ofUni>]. |
context.domains | حوزههای Nexus از registry/domains.yaml (water, energy, food, health, biodiversity, climate and the others the ecosystem covers), one or more. |
context.sectors | بخشها از registry/sectors.yaml (one or more). |
context.jurisdictions | ISO 3166-1 alpha-2 country codes and, where relevant, subdivision codes (ISO 3166-2) or INTL for international. |
context.hostRef | The institution, host city, tenant or programme that operates the context (entity reference from the consumer's legal registers). |
context.environment | production, staging, lab یا fixture; the environment never raises a supported claim level. |
context.validFrom / context.validUntil | When the context is live; a closed context keeps its record. |
context.conformsTo | The Nexus Standards and external standards (registry/external-standards.yaml ids) this context claims and evidences (NS-11, NS-14). |
REGION in the identifier is the primary geography (one country or one M49 region); finer or multiple jurisdictions go in context.jurisdictions. The identifier is allocated by the consumer's catalogue for the SCOPE (NS1-R2); the catalogue is append-only.
استناد کنید
NS-9, clause 3. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-3۳. وضوح و نمایش
/uni/NXS-EWS-DP-KEN-000001resolves to the deployment's landing page: the concept it instantiates, its domains, sectors, jurisdictions, host, environment, conformance claims with evidence state, and the records (NS-3) it produces.- The display name is the concept's neutral public name plus a context phrase from the name architecture standard, for example "Early Warning · Kenya · Water". The context phrase is derived from the record, never hand-typed, and never composes a geographic term with a protected mark in a way the name architecture forbids (NS0-P10).
- Every page, passport, report and monitoring record about the deployment carries the contextual UNI (NS1-R5), and a
X-Nexus-UNIheader ornexus-unimeta tag names it.
استناد کنید
NS-9, clause 4. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-44. سیاستها، بندها و پایش
A policy or clause (NS-10) binds to a contextual UNI, not to a name: "clause C applies to NXS-EWS-DP-KEN-000001". Verification and monitoring services (NS-11) observe a contextual UNI and record conformance per context. A command room or commons instance is itself a context (DP تحت STU یا CMD scope) so that what it enforces is identifiable.
استناد کنید
NS-9, clause 5. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-5۵. قواعد
| قاعده | متن |
|---|---|
NS9-R1 | یک سابقهٔ بافتار برای هر استقرار یا نمونهٔ برنامه؛ مفهوم UNI; context.ofUni الزامی است و باید قابل بازیابی و تحلیل باشد. |
NS9-R2 | Context identifiers are allocated by the catalogue for their SCOPE, never derived from names or typed by hand. |
NS9-R3 | A context's supported claim level, legal state and conformance evidence are its own; they are never inherited from the concept or from another context. |
NS9-R4 | بستن یک بافتار هرگز آن را حذف نمیکند؛ context.validUntil تعیین میشود و وضعیت تبدیل میشود به WITHDRAWN یا SUPERSEDED با supersededBy. |
NS9-R5 | نامهای نمایشی در بافتار از استاندارد معماری نام پیروی میکنند؛ در همه جا UNI و نه نام، کلید است. |
استناد کنید
NS-9, clause 6. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-6۶. پذیرش
Domains and sectors registers (registry/domains.yaml, registry/sectors.yaml) are populated from the ecosystem coverage study (research/ECOSYSTEM_COVERAGE.md). First contexts to catalogue: the foundry's tenant deployments and command rooms, the Global Risks Forum (GRF) host cities and national hubs, the Global Centre for Risk and Innovation (GCRI Canada) programmes per country, the Global Risks Alliance (GRA) capital-readiness engagements. Each consumer records its contexts in its own catalogue under its scopes.
تاریخچهٔ تغییرات
Versions from the catalogue; entries from the changelog that name this document.
| نسخه | تاریخ | یادداشت |
|---|---|---|
0.1.0 | 16 اکتبر 2026 | current version in the catalogue |
- 0.2.0 – 2026-10-16 اساسنامهٔ NS-0؛ NS-2، NS-4، NS-5، NS-9، NS-10، NS-11، NS-12، NS-13، NS-14 پیشنویس شدند (PROPOSED). ردههای DP، PR، CL، AT؛ طرحوارهٔ سابقه v1.1 همراه با بافتار NS-9؛ طرحوارههای بند، سیاست، گواهی و پیشنهاد.