Skip to content
ప్రమాణాలుNS-13ప్రతిపాదితం
NS-13

NS-13: Standards development process (open proposals, debate, versioning, adoption)

NS-13 is a proposed Nexus Standard; the artefacts it governs are identified by UNIs (Unique Nexus Identifier). 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.

NS-13 in the catalogue
The standards NS-13 depends on and those that cite it, then its sections with one mark for each numbered requirement.Source: NS-13-standards-development-process.md; the Nexus Standards registry.
  • NS-13 depends on: NS-0, NS-1, NS-2.
  • NS-13 is cited by: NS-0, NS-1, NS-4, NS-10, NS-15, NS-16.
  • Section 1, Who may participate: no numbered requirement.
  • Section 2, The proposal lifecycle: no numbered requirement.
  • Section 3, Editors and authority: no numbered requirement.
  • Section 4, Versioning: no numbered requirement.
  • Section 5, Licensing of the standards: no numbered requirement.
  • Section 6, Rules: R1, R2, R3, R4, R5.
01అవలోకనం

Summary

NS-13record
  1. స్థితిప్రతిపాదించబడింది
  2. Responsible scopetrust
  3. Rules stated5
  4. Programme areas3
  5. Source filesrepository

Nexus Standards · proposed

Requirements
5
numbered rules
Sections
6
in the text
Depends on
3
NS-0, NS-1, NS-2
Cited by
6
Nexus Standards
02The standard

NS-13: the standard

The text of NS-13 as it stands in the canonical repository (commit 2cbe0d41b5f8): 6 clauses, 0 sub-clauses and 5 identified requirements, each with its anchor and citation.

కోడ్
NS-13
Title
ప్రమాణాల అభివృద్ధి ప్రక్రియ (బహిరంగ ప్రతిపాదనలు, చర్చ, సంస్కరణ, స్వీకరణ)
సంస్కరణ
0.1.0
స్థితి
ప్రతిపాదించబడింది
తేదీ
catalogue 2026-10-16 · circulated 17 October 2026
Unique Nexus Identifier
NXS-STD-ST-000008
Responsible scope
trust
మూలం
standards/NS-13-standards-development-process.md at 2cbe0d41b5f8

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.

స్థితి
ప్రతిపాదించబడింది
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.

CiteNS-13, clause 1. NXS-STD-ST-000008@0.1.0. https://nexustandards.com/standards/ns-13/#nx-c-1

1. 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.

CiteNS-13, clause 2. NXS-STD-ST-000008@0.1.0. https://nexustandards.com/standards/ns-13/#nx-c-2

2. The proposal lifecycle

స్థితిMeaningరికార్డు
OPENA 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_REVIEWComments are collected in the open; each comment gets a disposition (accepted, rejected, deferred, open) with a reason.comments
LAST_CALLA 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 / WITHDRAWNThe editors' decision with reasons, recorded.decision
స్వీకరించబడింది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.

CiteNS-13, clause 3. NXS-STD-ST-000008@0.1.0. https://nexustandards.com/standards/ns-13/#nx-c-3

3. 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.

CiteNS-13, clause 4. NXS-STD-ST-000008@0.1.0. https://nexustandards.com/standards/ns-13/#nx-c-4

4. 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).

CiteNS-13, clause 5. NXS-STD-ST-000008@0.1.0. https://nexustandards.com/standards/ns-13/#nx-c-5

5. 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.

CiteNS-13, clause 6. NXS-STD-ST-000008@0.1.0. https://nexustandards.com/standards/ns-13/#nx-c-6

6. Rules

నియమంText
NS13-R1Every change to a standard, registry, clause or policy enters through a proposal with a UNI.
NS13-R2Participation is open and free; identity is recorded (ORCID, ROR or an agent mandate); decisions are reasoned in writing.
NS13-R3Last call is announced to every stakeholder group listed on the proposal; objections are dispositioned before acceptance.
NS13-R4Editors do not adopt; authority decisions are recorded references.
NS13-R5Versions 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.016 October 2026current 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; notice NXS-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, and CALL-TECHNICAL-REVIEW opens 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. In governance/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) and registry/information-hazard-screen.yaml (NXS-STD-DS-000014), both enforced by the validator. Four targeted calls in registry/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 domains planet and tech; new families in every 1.0 domain; seven risk classes). Hazard standards NRS-H63 to NRS-H120 appended (349 standards); risk-classes taxonomy 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, and governance/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) and tools/build-catalogue.mjs (NXS-STD-SW-000021) generate the catalogue and the ten-facet native taxonomy. machine/native-vocabularies.ttl, machine/harmonisation.ttl and machine/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.yaml covers 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. See the 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 by npm run validate. The architecture and one specification outline per standard are generated under standards/risk/.
  • Unreleased NS-13 proposal NXS-STD-PC-000004 (OPEN; last call ends 2026-11-16), the first proposal held as a record under proposals/ and checked by npm 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. AAP is grandfathered. It proposes four technology domain codes: CMP compute and accelerated infrastructure, DTW digital twins and simulation, SNS sensing and measurement networks, and PNT positioning, 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.
03పరిశోధన

Research, sources and files

Recent research on NS-13

Recent peer-reviewed articles, preprints, datasets and reports on the subject of this standard, retrieved at the time of reading from open scholarly metadata services (OpenAlex, Crossref, DataCite, Zenodo, arXiv, Europe PMC, OpenAIRE Graph) with search terms composed from the registry. Each work is listed with its authors, venue, year, type, open-access status and licence, and links to its DOI or landing page. Sources not yet enabled for live display on this site are listed for reference and are not queried.

Search termsstandards development; standardisation process; standard setting; open standards; consensus standards; W3C Process Document; UK Government Open Standards Principlescombined with: governance; participation; process; stakeholders; standardsDerived from the subject of the standard and its rules, and the external standards of its crosswalk domains.

  • OpenAlexlisted for reference; not queried
  • Crossreflisted for reference; not queried
  • DataCitelisted for reference; not queried
  • Zenodolisted for reference; not queried
  • arXivlisted for reference; not queried
  • Europe PMClisted for reference; not queried
  • OpenAIRE Graphlisted for reference; not queried

No source is enabled for live display on this site yet: the sources are listed for reference and none is queried. Once the publisher of record enables a source after its terms are reviewed, recent works are listed here. Metadata and links only: title, authors, venue, year, type, open-access status and licence as each source records them; works are listed for orientation, not reviewed or endorsed.

04In practice

Where it applies and how it is developed

How it is developed and how to take part, the standard as a process, and the programme areas that list it.

How NS-13 is developed, and how to take part

NS-13 is developed in the open under NS-13 (the stages and gates of NS-13). Working groups draft, councils decide the reserved matters, and anyone may propose a change, comment, submit an implementation report, object or appeal, without membership or fee.

05బాహ్య ప్రమాణాలు

Relation to external standards

NS-13 relates to external standards by identifier, clause number and URL (NS14-R1), and directs the reader to the issuing body.

06నెట్‌వర్క్ అంతటా

Learning, the network and questions

నివేదికలుసహకరించండి

ఈ పేజీ నుండి ఆధారాలను అందించండి.

Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.

Nexus Standards

వ్యక్తిగత డేటా, సున్నితమైన మౌలిక సదుపాయాల వివరాలు లేదా పంచుకునే హక్కు మీకు లేని దేనినీ ఎప్పుడూ పంపవద్దు. సహకారం ఉపయోగానికి ముందు సమీక్షించబడుతుంది; దానిని పంపడం వల్ల రచయిత్వం లేదా సంపాదకీయ హక్కులు లభించవు, మరియు స్పాన్సర్‌షిప్ ఎప్పుడూ ఒక నిర్ధారణను కొనలేదు.

ప్రమాణాలు

ప్రమాణాలలో పాల్గొనండి.

Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.

స్థితి మరియు వినియోగం. Nexus Standards అనేవి NS-13 కింద బహిరంగ ప్రక్రియ ద్వారా అభివృద్ధి చేయబడి స్వచ్ఛంద వినియోగం కోసం ప్రచురించబడిన ప్రతిపాదిత ప్రమాణాలు; అవి ధృవీకరణ, గుర్తింపు లేదా నియంత్రణ ఆమోదం కావు, మరియు స్వీకరణ గ్లోబల్ స్టాండర్డ్స్ కౌన్సిల్ నిర్ణయంగా, మరియు ప్రతి దేశంలో దాని జాతీయ ప్రమాణాల మండలి నిర్ణయంగా ఉంటుంది. UNI (Unique Nexus Identifier) ఒక కళాఖండాన్ని గుర్తిస్తుంది; దానిని ధృవీకరించదు. ప్రమాణ సంస్థల పేర్లు మరియు వాటి ప్రమాణాలు వాటి సంరక్షకులకు చెందినవి మరియు పత్రాలను గుర్తించడానికి మాత్రమే ఉపయోగించబడతాయి; ఇక్కడ ఏ బాహ్య ప్రమాణ పాఠ్యమూ పునరుత్పత్తి చేయబడలేదు. Nexus Standardsకు ఇక్కడ పేర్కొన్న ఏ ప్రమాణ సంస్థతోనూ అనుబంధం లేదు, వాటి ఆమోదం లేదా ధృవీకరణ లేదు.

లైసెన్సులు: ప్రమాణాల పాఠ్యం, రిజిస్ట్రీలు, స్కీమాలు మరియు డేటా కోసం CC BY 4.0; సూచన కోడ్ కోసం Apache-2.0. బాహ్య ప్రమాణాలు వాటి సొంత లైసెన్సుల కింద పేరు, సంఖ్య మరియు లింక్ ద్వారా ఉల్లేఖించబడతాయి. మూడవ పక్ష డేటా, లైబ్రరీలు మరియు ఫాంట్‌లు వాటి సొంత లైసెన్సులను నిలుపుకుంటాయి: మూడవ పక్ష ప్రకటనలు చూడండి.