- குறியீடு
NS-13- Title
- தரநிலை மேம்பாட்டுச் செயல்முறை (திறந்த முன்மொழிவுகள், விவாதம், பதிப்பிடல், ஏற்பு)
- பதிப்பு
- 0.1.0
- நிலை
- PROPOSED
- தேதி
- catalogue 2026-10-16 · circulated 17 October 2026
- Unique Nexus Identifier
NXS-STD-ST-000008- Responsible scope
- trust
- மூலம்
standards/NS-13-standards-development-process.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-01. 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.
- நிலை
- PROPOSED
- Owner
- the trust and assurance system
- Constitution
NS-0- Schema
schemas/nexus-proposal.v1.json
NS-13 makes the development of the standards themselves open, recorded and owned by the communities that use them, in contrast to closed membership bodies and static editions. It follows the openness principles practised by the internet and web standards communities (open participation, due process, consensus, transparency, availability) and adds what those bodies lack: every step is an identified artefact, the standard is data, and conformance is observed.
Cite
NS-13, clause 1. NXS-STD-ST-000008@0.1.0. https://nexustandards.com/standards/ns-13/#nx-c-11. Who may participate
Anyone: governments, international organisations, academia, industry, civil society, communities, capital, implementers and other standards bodies, as individuals (ORCID) or organisations (ROR), and agents acting under a recorded mandate and marked as agents. Participation needs no membership fee. Decisions are made by the recorded process, never by who pays.
Cite
NS-13, clause 2. NXS-STD-ST-000008@0.1.0. https://nexustandards.com/standards/ns-13/#nx-c-22. The proposal lifecycle
| நிலை | Meaning | பதிவு |
|---|---|---|
| OPEN | A proposal is filed as an artefact with a UNI (nexus-proposal.v1.json), naming the target standard, section or registry path, the rationale, the changes (with a change request or patch) and the stakeholder groups affected. | proposal record |
IN_REVIEW | Comments are collected in the open; each comment gets a disposition (accepted, rejected, deferred, open) with a reason. | comments |
LAST_CALL | A fixed period (default 30 days; 14 for errata; 90 for a new standard) announced to all stakeholder groups; objections must be addressed in writing. | lastCallEndsAt |
| ACCEPTED / REJECTED / WITHDRAWN | The editors' decision with reasons, recorded. | decision |
| ADOPTED | The authority decision that changes the standard's status (GOVERNANCE.md status ladder), recorded in the owning institution's legal registers. | decisionRef |
Every proposal, comment, decision and resulting version is itself an artefact (NS-1) and cited (NS-2); nothing is decided in private channels.
Cite
NS-13, clause 3. NXS-STD-ST-000008@0.1.0. https://nexustandards.com/standards/ns-13/#nx-c-33. Editors and authority
Editors maintain the text and registries and run the process; they do not adopt. Adoption of a Nexus Standard is a decision of the Global Standards Council by the rules of the Charter (governance/CHARTER.md), recorded as a reference; adoption in a country is a decision of its National Standards Council (governance/NATIONAL_ADOPTION_AND_SOVEREIGNTY.md). In the Foundry engines, adopt additionally requires a mandate verified in the trust and assurance system register. Editors recuse on proposals they raised. The editors' roster, their mandates and recusals are records.
Cite
NS-13, clause 4. NXS-STD-ST-000008@0.1.0. https://nexustandards.com/standards/ns-13/#nx-c-44. Versioning
Standards use semantic versions. A patch changes explanation only; a minor change is additive and backward compatible (new codes, optional fields, new clauses marked informative or recommended); a major change alters a grammar, a required field or a blocking clause and needs a crosswalk and migration note. Consumers state the versions they conform to (NS-0 §6). Registries are append-only (GOVERNANCE.md).
Cite
NS-13, clause 5. NXS-STD-ST-000008@0.1.0. https://nexustandards.com/standards/ns-13/#nx-c-55. Licensing of the standards
The text, registries, schemas and data are published under CC-BY-4.0 and the reference code under Apache-2.0, effective on public release (LICENSING.md). Contributions are made under the Developer Certificate of Origin with a royalty-free patent licence for Essential Claims (governance/OPEN_BOUNDARY_IPR_AND_LICENSING.md). Implementations may be licensed as their authors choose. No participant grants or receives a licence to another body's standard by taking part.
Cite
NS-13, clause 6. NXS-STD-ST-000008@0.1.0. https://nexustandards.com/standards/ns-13/#nx-c-66. Rules
| விதி | Text |
|---|---|
NS13-R1 | Every change to a standard, registry, clause or policy enters through a proposal with a UNI. |
NS13-R2 | Participation is open and free; identity is recorded (ORCID, ROR or an agent mandate); decisions are reasoned in writing. |
NS13-R3 | Last call is announced to every stakeholder group listed on the proposal; objections are dispositioned before acceptance. |
NS13-R4 | Editors do not adopt; authority decisions are recorded references. |
NS13-R5 | Versions are semantic; registries append-only; existing UNIs are never invalidated. |
Change history
Versions from the catalogue; entries from the changelog that name this document.
| பதிப்பு | தேதி | Note |
|---|---|---|
0.1.0 | 16 October 2026 | current version in the catalogue |
- Unreleased Circulation for technical review and comment, prepared and circulated by the Chief Steward (
registry/review-investigations.yaml,NXS-STD-DS-000015; noticeNXS-STD-DC-000034). Every document is a preparatory working draft, circulated for review and comment and not for implementation, with stage designation reserved to the Global Standards Council (NS-13). The circulation records no decision of any body. Forty-three technical review areas cover every NS document, every NRS series, every NHS-1 domain, NIS-1, the methods, the vocabulary and classifications, the machine exports, the governance instruments and the site. Each area has its scope, guiding questions, expertise sought and working groups.tools/build-investigations.mjs(NXS-STD-SW-000023) places the circulation notice on every document. The risk standards, the site pages and the disclaimers carry it from their generators. The validator refuses an uncovered area, andCALL-TECHNICAL-REVIEWopens on 20 October 2026. Wording throughout the programme instruments now distinguishes preparation and coordination by the Chief Steward from decisions of the Council. - Unreleased NS-13 proposal
NXS-STD-PC-000010(OPEN, policy), proposed by Saeed Valadbaygi, Chief Steward: the first work programme. Ingovernance/programme/: bibliography (NXS-STD-DC-000027); policy on information hazards and dual-use content (NXS-STD-PO-000001, observed as a precaution pending the Council); maintenance procedure (NXS-STD-DC-000028); NHS-2 model specification (NXS-STD-TN-000001); new work items NRS-C17 to NRS-C24 (NXS-STD-DC-000029); workstream terms of reference (NXS-STD-DC-000030); invitations and channels (NXS-STD-DC-000031); policy on accessibility and languages (NXS-STD-PO-000002); conformity assessment scheme (NXS-STD-DC-000032); cover note (NXS-STD-DC-000033). Also: NS-4 version 0.2 (structure and drafting).registry/requirements.yaml(NXS-STD-DS-000013, 108 requirements) andregistry/information-hazard-screen.yaml(NXS-STD-DS-000014), both enforced by the validator. Four targeted calls inregistry/participation.yaml. - Unreleased NS-13 proposal
NXS-STD-PC-000009(OPEN, revision): risk atlas 1.1. NHS-1 1.1.0 imported (14 domains, 120 families, 905 hazards, 1867 relations; new domainsplanetandtech; new families in every 1.0 domain; seven risk classes). Hazard standards NRS-H63 to NRS-H120 appended (349 standards);risk-classestaxonomy facet; two new hazard subsites.registry/risk-vocabulary.yaml(NXS-STD-DS-000010, 424 terms),registry/industries.yaml(NXS-STD-DS-000011, 28 groups, 249 industries, 14 proposed sector codes),registry/disciplines.yaml(NXS-STD-DS-000012, 137 disciplines), the full alpha-2 and M49 jurisdiction crosswalk, andgovernance/RISK_ATLAS_AND_VOCABULARY.md(NXS-STD-DC-000025). - Unreleased NS-13 proposal
NXS-STD-PC-000008(OPEN, policy): participation, cadence and gateways.registry/participation.yaml(NXS-STD-DS-000009) sets the start-up (founding calls from 2026-10-20, inaugural Council session 2027-01-12, first quarterly review 2027-03-09), the monthly Council cadence (second Tuesday, 14:00 UTC) with quarterly reviews, 13 working groups, 8 expert communities, 4 open calls, 6 roles, 9 contribution types with response times and 7 gateways (Council room, Commons rooms and the WordPress sites of every institution).tools/lib/cadence.mjs(NXS-STD-SW-000022),governance/PARTICIPATION_AND_CADENCE.md(NXS-STD-DC-000024) and the Participate page (NXS-STD-DC-000023). - Unreleased NS-13 proposal
NXS-STD-PC-000007(OPEN): native convergence. Every classification now derives from the Nexus-native authorities. Withdrawn before review: the hazard profiles H1 to H40 and the hazard-type facet built on an external hazard list, the six invented taxonomy facets, and the conformance classes CC1 to CC4. H series rebuilt as NRS-H1 to NRS-H62, one standard per NHS-1 family (all 350 NHS-1 hazards covered). New series M (23 Risk Master fabrics), U (28 Universe platforms) and K (50 applied domain packs); system profiles carry their rooms and station categories. 291 standards in 15 series. Conformance on NXOSI levels CL-Base to CL-Federated with EQL-1 to EQL-5; NRM CL1 to CL4 crosswalked.registry/native-register.yaml(NXS-STD-DS-000006): 86 Nexus authorities across the Foundry, the Universe and the organisation book;tools/extract-native.mjs(NXS-STD-SW-000020) pins and normalises them (2,427 files, about 104,000 terms) and proves every Universe machine file and every book page is covered.registry/harmonisation.yaml(NXS-STD-DS-000007): 52 groups, one canonical authority per concept, term maps proven complete.registry/risk-standards.source.yaml(NXS-STD-DS-000008) andtools/build-catalogue.mjs(NXS-STD-SW-000021) generate the catalogue and the ten-facet native taxonomy.machine/native-vocabularies.ttl,machine/harmonisation.ttlandmachine/alignment.ttl; SHACL requires a native source on every standard, CL and EQL on every conformance statement, an attestation from CL-Assured, and an NHS-1 hazard for every hazard.registry/native/nexus-vocabularies.json: the Foundry module vocabularies (risk chain, epistemic and presentation states, units, exposure and intensity, perils, baseline indicators, observation, station spines, specialist rooms, NEIF modes, Commons kinds, consortium programme, programme spine). Hazard subsites now follow the twelve NHS-1 domains. The agent interface and HTTP API resolve NHS-1 hazards, fabrics, platforms, packs and native authorities. - Unreleased NS-13 proposal
NXS-STD-PC-000006(OPEN): full-spectrum completion and AI-native infrastructure. The catalogue grows to 168 standards in 12 series. New: 20 hazard profiles; displacement, civil preparedness and education; security and geopolitics, legal and compliance, third-party and reputational risk; occupational, process and nuclear safety, transport and pollution; AI agents and the ML lifecycle; knowledge graphs and intelligence applications; and series A (standards as code, the ontology-native layer, the agent interface, zero-trust verification, built-in licensing, one-click kits, accessibility, AI-ready data, evaluation suites).registry/risk-taxonomy.yamlcovers the full spectrum in seven facets, enforced by the validator.machine/holds the OWL ontology, SHACL shapes, SKOS taxonomy, the catalogue in RDF, JSON-LD and OSCAL form, and ODRL policies. Zero-trust releases: per-file licences (REUSE), a Merkle-root manifest, an in-toto statement, and Ed25519 signing and verification against the trust roots. One command for everyone:tools/nexus-standards.mjs(verify, serve, mcp, kit, find, show), plus Docker and compose. Seethe network's own records. - Unreleased NS-13 proposal
NXS-STD-PC-000005(OPEN; last call ends 2027-01-15): the Nexus Risk Standards catalogue,registry/risk-standards.yaml. 124 risk standards in 11 series: the risk core the six anchor nexus streams (each with eight parts and named profiles) and their coupling 16 technology standards, 9 finance, 7 policy, 7 development and 8 cross-cutting standards 20 hazard profiles and 5 intelligence standards 8 programme standards and 21 system profiles Coverage of every ecosystem area, code, Foundry system, consortium area and technology stream is proved bynpm run validate. The architecture and one specification outline per standard are generated understandards/risk/. - 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.2.0 – 2026-10-16 NS-0 constitution; NS-2, NS-4, NS-5, NS-9, NS-10, NS-11, NS-12, NS-13, NS-14 drafted (PROPOSED). Categories DP, PR, CL, AT; record schema v1.1 with the NS-9 context; clause, policy, attestation and proposal schemas.