- Code
NS-4- Title
- Structure and drafting of Nexus Standards and documents (v0.2: clause structure, verbal forms, registered requirements; document front matter)
- Version
- 0.2.0
- Isimo
- KUHLONGOZIWE
- Date
- catalogue 2026-10-16 · circulated 17 October 2026
- Unique Nexus Identifier
NXS-STD-ST-000010- Responsible scope
- knowledge
- Umthombo
standards/NS-4-document-template.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-03. 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.
| Version | 0.2.0 (working draft of the revision; on adoption it supersedes the 0.1 document template) |
| Isimo | PROPOSED · Proposal NXS-STD-PC-000010 |
| Prepared and circulated by | Saeed Valadbaygi, Chief Steward, Nexus Standards (saeed@therisk.global), 17 October 2026 |
| Isigaba | Preparatory working draft, circulated for review and comment. Not for implementation. Stage designation reserved to the Global Standards Council (NS-13) |
| Owner | WG-DEV with the editors; committee TC-CORE |
| Parent | NS-1; process NS-13 |
| Requirements | NS4-R1 to NS4-R24, registered in registry/requirements.yaml |
Cite
NS-4, Foreword. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-forewordForeword
This revision turns NS-4 from a document template into the drafting rules of the Nexus Standards. Version 0.1 fixed the front matter that gives a document its identity and provenance, and that front matter is retained unchanged in clause 9.
What 0.1 did not do was say how a standard states a requirement, how a reader distinguishes a requirement from advice, and how a conformance claim can be tested. Mature standards bodies settled these questions long ago [ISO-D2; RFC2119; RFC8174; W3C-P]. This revision adopts their settled practice in the Nexus voice and adds what a machine-readable programme needs: a register in which every requirement can be found, tested and traced.
Cite
NS-4, Introduction. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-introductionIntroduction
A standard is useful to the degree that two independent parties, reading it, reach the same judgement about whether a thing conforms. Four drafting disciplines serve that end:
- a fixed structure, so the reader knows where to look;
- a controlled vocabulary of obligation, so the reader knows what is required;
- atomic requirements, so each can be tested on its own;
- a stated test, so the judgement does not depend on who makes it.
Cite
NS-4, clause 1. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-11. Scope
1.1 This document specifies:
Cite
NS-4, clause 1.1. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-1-1- the structure of Nexus Standards and of the specifications, policies and technical notes of the programme;
- the verbal forms that express requirements, recommendations, permissions and possibilities;
- the rules for writing requirements and for registering them;
- the front matter and structure of other documents of the ecosystem (clause 9).
1.2 It applies to every document of categories ST (standard), PO (policy), TN (technical note) and PC (proposal) drafted after its adoption, and to every existing NS document when that document is next revised. Clause 9 applies to documents of categories RP, DC, DL, WP, PP, AR, BK, CP and TH.
Cite
NS-4, clause 1.2. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-1-21.3 It does not specify the content of any standard, the development process (NS-13), or conformity assessment (NS-14 and NXS-STD-DC-000032).
Cite
NS-4, clause 1.3. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-1-3Cite
NS-4, clause 2. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-22. Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references only the edition cited applies. For undated references the latest edition applies.
- NS-1, *Identifier and artefact catalogue*
- NS-2, *Citation and attribution*
- NS-13, *Standards development process*
- NS-14, *Conformance and crosswalk*
registry/requirements.yaml, *Register of normative requirements* (NXS-STD-DS-000013)
Cite
NS-4, clause 3. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-33. Terms and definitions
3.1 requirement: an expression in the content of a document conveying objectively verifiable criteria to be fulfilled and from which no deviation is permitted if conformance with the document is to be claimed (after [ISO-D2]).
Cite
NS-4, clause 3.1. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-13.2 recommendation: an expression conveying that, among several possibilities, one is recommended as particularly suitable, without excluding others.
Cite
NS-4, clause 3.2. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-23.3 permission: an expression conveying consent or liberty to do something.
Cite
NS-4, clause 3.3. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-33.4 possibility: an expression conveying that something is materially, physically or causally possible.
Cite
NS-4, clause 3.4. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-43.5 conformance target: the kind of thing to which a requirement applies, for example a record, a dataset, a software release, an organisation or a process.
Cite
NS-4, clause 3.5. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-53.6 test method: the procedure by which conformance with a requirement is determined. It is one of:
Cite
NS-4, clause 3.6. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-6automated: by a published executable test;inspection: by examination of an artefact against stated criteria;audit: by examination of records and practice over a period;demonstration: by observed performance.
3.7 normative: content that a claimant must satisfy. informative: content that explains, illustrates or credits, and that a claimant need not satisfy.
Cite
NS-4, clause 3.7. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-7Cite
NS-4, clause 4. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-44. Structure of a standard
4.1 NS4-R5. A Nexus Standard shall contain the following elements in this order. An element marked conditional may be omitted only when it would be empty.
Cite
NS-4, NS4-R5. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r5| Element | Kind | Conditional |
|---|---|---|
| Title | normative | no |
| Foreword (status, proposal, owners, relation to other documents, changes from the previous edition) | informative | no |
| Introduction (purpose and rationale) | informative | yes |
| 1 Scope (what the document covers, and what it does not) | normative | no |
| 2 Normative references | normative | no; states "There are no normative references in this document." when there are none |
| 3 Terms and definitions | normative | no; refers to the Nexus-native risk vocabulary for terms it does not define itself |
| 4 onwards: Requirements, organised by subject | normative | no |
| Conformance (conformance targets, levels, classes, and how a claim is made) | normative | no |
| Annexes, each marked normative or informative | either | yes |
| Bibliography of informative references | informative | yes |
4.2 NS4-R6. The scope shall be written as statements of fact. It shall not contain requirements.
Cite
NS-4, NS4-R6. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r64.3 NS4-R7. A normative reference shall be cited by identifier and, where a dated edition is intended, by year. The text of an external document shall not be reproduced (NS14-R1).
Cite
NS-4, NS4-R7. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r74.4 NS4-R8. A term defined in clause 3 shall be defined once, as a substitutable phrase without an article, and shall be used with that meaning throughout the document.
Cite
NS-4, NS4-R8. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r84.5 Clauses are numbered in arabic numerals to at most four levels (4.2.1.3). Annexes are lettered (Annex A).
Cite
NS-4, clause 4.5. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-4-5Cite
NS-4, clause 5. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-55. Verbal forms
5.1 NS4-R9. The following verbal forms shall be used, and only with these meanings.
Cite
NS-4, NS4-R9. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r9| Ifomu | Expresses | Negative |
|---|---|---|
| shall | a requirement | shall not |
| should | a recommendation | should not |
| may | a permission | need not |
| can | a possibility or capability | cannot |
5.2 NS4-R10. The words "must", "required", "mandatory" and "is to" shall not be used to express a requirement. The word "must" may appear only to describe an external constraint, such as a law of nature or a legal duty that the document does not itself create.
Cite
NS-4, NS4-R10. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r105.3 The forms of clause 5.1 correspond to the keywords of [RFC2119] as clarified by [RFC8174]. A Nexus document that is also published as an internet specification may state that correspondence.
Cite
NS-4, clause 5.3. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-5-3Cite
NS-4, clause 6. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-66. Writing requirements
6.1 NS4-R11. Each requirement shall be atomic: it states one obligation on one conformance target.
Cite
NS-4, NS4-R11. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r116.2 NS4-R12. Each requirement shall be identified by a requirement identifier of the form <DOC>-R<n>, where <DOC> is the document's short code (for example NS4, IHP, NRS-C17) and <n> is a positive integer. The identifier shall be written in bold at the start of the sentence that contains the requirement. Identifiers are never reused. A withdrawn requirement keeps its identifier with status WITHDRAWN.
Cite
NS-4, NS4-R12. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r126.3 NS4-R13. A requirement shall be verifiable. It shall state, or refer to, the criteria by which conformance is judged. Words without a stated criterion, such as "appropriate", "adequate", "sufficient", "timely" and "state-of-the-art", shall not be used as the sole criterion of a requirement.
Cite
NS-4, NS4-R13. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r136.4 NS4-R14. A requirement that depends on a quantity shall state the quantity, its unit and its tolerance, in accordance with the units and measurement standard of the programme once adopted (proposed NRS-C24).
Cite
NS-4, NS4-R14. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r146.5 NS4-R15. Notes and examples shall be informative and shall not contain requirements.
Cite
NS-4, NS4-R15. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r156.6 A requirement may refer to another document. A reference to a requirement in another document cites its identifier.
Cite
NS-4, clause 6.6. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-6-6Cite
NS-4, clause 7. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-77. Register of requirements
7.1 NS4-R16. Every requirement of an adopted or proposed Nexus document shall be recorded in registry/requirements.yaml with the following:
Cite
NS-4, NS4-R16. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r16- identifier;
- document UNI;
- clause;
- verbal form;
- the conformance target;
- the test method (clause 3.6);
- the reference of the executable test, where the method is
automated; - status.
7.2 NS4-R17. A requirement shall have one of the statuses PROPOSED, IN_COMMENT, ADOPTED, SUPERSEDED or WITHDRAWN. The status of a requirement shall not run ahead of the status of its document.
Cite
NS-4, NS4-R17. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r177.3 NS4-R18. The validator shall refuse:
Cite
NS-4, NS4-R18. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r18- a register entry whose identifier does not appear in the clause it cites;
- a document requirement identifier that is not registered;
- an
automatedrequirement without a test reference once the document is in comment.
7.4 The register is the source from which conformance checklists, test suites and the requirement pages of the site are generated.
Cite
NS-4, clause 7.4. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-7-4Cite
NS-4, clause 8. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-88. Conformance clause
8.1 NS4-R19. The conformance clause shall state:
Cite
NS-4, NS4-R19. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r19- the conformance targets;
- any conformance levels or classes;
- the requirements each level or class comprises;
- the form of a conformance claim.
8.2 NS4-R20. A conformance claim shall cite:
Cite
NS-4, NS4-R20. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r20- the document's UNI and version;
- the level or class claimed;
- the evidence quality level (EQL) of the supporting evidence;
- the date of the claim;
- the party making it.
A claim never states or implies certification unless an accredited certification under the conformity assessment scheme supports it.
Cite
NS-4, clause 9. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-99. Front matter and structure of other documents
9.1 NS4-R1. Front matter, or the first-line UNI, shall be present in every document. The record shall be minted before the document is shared.
Cite
NS-4, NS4-R1. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r1--- uni: NXS-GRX-RP-M002-000007 version: 1.2.0 title: ... creators: [{ name: ..., orcid: ... }] publisherRef: GCRI_CANADA publicationDate: 2026-10-16 legalState: LEGAL_REVIEW_REQUIRED claimCeiling: INTEGRATED derivedFrom: [NXS-GRX-DS-M002-000003@2.0.0] conformsTo: [NS-0, NS-1, NS-2, NS-4] language: en ---Plain Markdown without front matter starts with Nexus-UNI: <uni> on the first line (NS1-R5). HTML carries <meta name="nexus-uni"> and the Schema.org JSON-LD of the record (NS-7). Word, PDF and slide formats carry the UNI on the title page and in the document properties.
9.2 Documents other than standards follow this structure:
Cite
NS-4, clause 9.2. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-9-2- Summary: what the document is, for whom, its supported claim level and its legal state, in one paragraph.
- Scope and definitions.
- Body.
- Evidence and provenance: datasets, records, models and runs, cited by UNI (NS-2).
- Limitations.
- Conformance: the standards and clauses claimed (NS-14).
- References.
- Change log.
9.3 NS4-R2. Every number, figure and map in a document shall cite its source UNI (NS-2, NS-5).
Cite
NS-4, NS4-R2. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r29.4 NS4-R3. The limitations section shall be present. It shall state the supported claim level and the legal state in plain words.
Cite
NS-4, NS4-R3. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r39.5 NS4-R4. Versions shall be semantic in accordance with the maintenance procedure (NXS-STD-DC-000028). A changed number or conclusion is a new version with a change-log line and digest.
Cite
NS-4, NS4-R4. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r4Cite
NS-4, clause 10. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-1010. Language and style
10.1 NS4-R21. Standards shall be written in plain, impersonal and precise language. Each sentence shall carry a single idea where a requirement is stated.
Cite
NS-4, NS4-R21. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r2110.2 NS4-R22. Abbreviations shall be expanded at first use in each document.
Cite
NS-4, NS4-R22. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r2210.3 NS4-R23. No document shall name, promote or disparage a for-profit company, product or mark, except where a normative reference to a published standard requires it, and then only by the standard's identifier.
Cite
NS-4, NS4-R23. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r2310.4 NS4-R24. The English text is the reference text. Translations follow the policy on accessibility and languages (NXS-STD-PO-000002).
Cite
NS-4, NS4-R24. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r24Cite
NS-4, clause 11. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-1111. Conformance
11.1 The conformance target of this document is a document of the categories listed in 1.2.
Cite
NS-4, clause 11.1. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-11-111.2 A document conforms to NS-4 when it satisfies NS4-R1 to NS4-R24 as they apply to its category. Requirements NS4-R5 to NS4-R20 apply to standards, policies, technical notes and proposals. Requirements NS4-R1 to NS4-R4 and NS4-R21 to NS4-R24 apply to every document.
Cite
NS-4, clause 11.2. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-11-2Cite
NS-4, Annex A. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-annex-aAnnex A (informative): changes from version 0.1
| Version 0.1 | Version 0.2 |
|---|---|
| NS4-R1 to NS4-R4 (front matter, citation of numbers, limitations, semantic versions) | Retained with the same identifiers in clause 9 |
| No structure for standards | Clause 4 |
| No verbal forms | Clause 5 |
| Rules in tables | Atomic, identified, verifiable requirements (clause 6) |
| No register | Clause 7 |
| No conformance clause rule | Clause 8 |
Cite
NS-4, Bibliography. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-bibliographyBibliography
[ISO-D2], [RFC2119], [RFC8174], [W3C-P] in governance/programme/BIBLIOGRAPHY.md.
Change history
Versions from the catalogue; entries from the changelog that name this document.
| Version | Date | Note |
|---|---|---|
0.1.0 | 16 October 2026 | current version in the catalogue |
- 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. - 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.