Konformiteitsprogram
Explains conformance without certification: each standard names conformance classes and rule anchors (NS-n-Rm); every proposed standard is accompanied by an open, executable test suite (Apache-2.0) that runs in a browser test environment and in continuous integration; an implementer publishes an Implementation Conformance Statement with its evidence (NS-11); the public register lists declarations as submitted and states that the programme does not verify them. No marks, seals or badges are issued. Each artefact of the area carries a UNI (Unique Nexus Identifier).
- Nexus Standards: NS-1, NS-10, NS-11.
- Open standards: QA Framework: Specification Guidelines; RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words (BCP 14); OGC Compliance Program and TEAM Engine executable test suites; Supply-chain Levels for Software Artifacts (SLSA) v1.1; Open Security Controls Assessment Language (OSCAL).
- Data and feeds: OpenSSF Scorecard public results (reference model for published, machine-run evidence); Zenodo REST API (deposit of test-run evidence bundles with DOIs).
- Couples with: How a standard is made; The UNI and the artefact catalogue; Compatibility profiles for closed; Trust, verification and assurance.
Summary
- 01ScopeScope and boundaries
- 02KonformiteitsprogramKonformiteitsprogram
- 03Standards architectureFoundation, referenced and implementing layers
- 04PipelineThe conformance pipeline, step by step
- 05Sistemiese koppelingsSistemiese koppelings
- 06System modelHow a shock travels through this system
- 07ConsoleEvidence recorded
- Nexus Standards
- 3
- NS-1, NS-10, NS-11
- Open standards
- 5
- named, never copied
- Data and feeds
- 2
- listed for reference
- Couplings
- 4
- with other areas
- UNI
- requested · allocation in progress
- Status
- Proposednot yet in the catalogue
- Last reviewed
- area profile
Nexus Standards (2026). Conformance programme: area brief, Foundations and Governance programme. Proposed. https://nexustandards.com/foundations/conformance-programme/. Last reviewed 17 October 2026.
Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.
Scope and boundaries
An area of the Foundations and Governance programme (foundations). The area profile sets out 5 matters in scope and 3 matters addressed by other areas.
In scope 5
- Conformance classes, requirement anchors and abstract test suites
- Executable tests in a browser test environment and in continuous integration, with PASS, FAIL and INDETERMINATE verdicts per test case
- Implementation Conformance Statements (classes, version, test-run evidence, date, declarant) as NS-11 records
- The public register of declarations as submitted, with the no-verification notice
- Wording rules ("conforms to" used only alongside a published declaration)
Out of scope 3
- Certification, accreditation of test laboratories, and marks, seals or badges of any kind
- Verification of declarations by the programme
- Conformance to closed standards
Jurisdictions Application in each jurisdiction is a national decision, taken by the National Standards Council (NSC) with the competent national authorities.
Konformiteitsprogram
Classes
Conformance classes
Each standard defines its conformance classes and the requirements in each class, by rule anchor (NS-n-Rm). A class defines a scope of requirements; it does not denote a level of merit.
- NS-10: Policies and clauses (machine-readable obligations: definition, binding, evaluation and enforcement)Role in the programmemachine-readable clauses for each normative statement
- NS-11: Verification and monitoring (evidence, attestations, zero-trust conformance observation)Role in the programmeevidence, attestations and named evaluators, with results of PASS, FAIL or INDETERMINATE
- NS-14: Conformance and crosswalk to external standardsRole in the programmerelations to external standards by subject and clause
Tests
Executable test suites
- Each proposed standard is accompanied by an open test suite under Apache-2.0, executable in the browser and in continuous integration.
- A test result constitutes implementation evidence and states the suite version, the date and time, and the implementation tested.
- Test pages use worked examples and identify them as such.
Statement
Implementation Conformance Statement
| Veld | Content |
|---|---|
| Declarant | the implementer, named |
| Classes | the conformance classes claimed and the version of the standard |
| Bewyse | test results, by reference |
| Evaluator and date | named, with the date |
| Identifier | a UNI; the statement is a record under NS-11 |
Register
Public register of declarations
The public register lists implementers’ declarations as submitted, with links to their evidence; the programme does not verify them.
The register opens with the first proposed standard accompanied by a test suite. A statement that an implementation conforms to Nexus Standard NS-n may be made by anyone who publishes the supporting evidence, and only alongside that published declaration.
Closed standards
Versoenbaarheidsprofiele vir geslote standaarde
Compatibility profiles for closed standards are built on simulated data, kept on protected pages, refer to the standards by name only and are activated for each issuing body. Compatibility profiles.
The process in operation
A mandate authorises an evaluator; evidence is gathered and checked for resolution; the evaluator, outside the subject’s trust boundary, evaluates each clause; the result is recorded as an append-only attestation with its digest; monitoring observes coverage and drift; reports are generated from attestations. 8 operations in 5 phases, built from the area profile: the rows carry its own data sources, indicators, open standards, couplings and, where listed, hazards, and each operation names the rules it implements (7). Records and artefacts are cited by UNI (Unique Nexus Identifier) and version.
Prosesverkenner · Standards · kodifiseer en korrigeer
Lewensiklus van 'n standaard
17 stappe·6 fases
Standards · kodifiseer en korrigeer
Lewensiklus van 'n standaard
Siklusbevindings word veranderingsvoorstelle, die Wêreldwye Standaarderaad aanvaar ná 'n openbare laaste oproep, en elke land besluit oor sy eie aanvaarding.
01 Lei sendings
- 01Route missions to standards and profilesStep · Nexus StandardsNexus Standards routes each candidate mission to the standards and profiles that apply.
02 Profiele en ooreenstemming
- 02Stel sendingprofiele saamStap · Nexus StandardsNexus Standards stel sendingprofiele saam en teken enige nasionale aanvaarding aan waarvan die sendings afhang.
- 03Valideer bou-uitsette teen die profieleStap · Nexus StandardsNexus Standards valideer bou-uitsette teen die saamgestelde profiele en teken die bewyse aan.
- 04Moniteer konformiteit en teken verseëlde bewyse aanStap · Nexus StandardsGedurende die Aksieweek monitor Nexus Standards konformiteit en teken afwykings aan.
03 Voorstelle en beoordeling
- 05Afwykings en regstellings word veranderingsvoorstelleStap · Nexus StandardsAfwykings word veranderingsvoorstelle, en die regstelling word as 'n verandering aan die bewyse aangeteken.
- 06Siklusbevindings word veranderingsvoorstelleStap · Nexus StandardsBevindings uit 'n siklus word veranderingsvoorstelle: metode- en korreksiebevindings uit Verslae (F06) en dokketitems uit Nexus…
- 07Stel op en hersien in die openbaarStap · Komitees en werkgroepeTegniese komitees en werkgroepe stel die standaarde op en hersien dit in die oop proses van NS-13.
- 08Beoordeel met die oog op 'n raadsbesluitStap · Nexus StandardsNexus Standards beweeg veranderingsvoorstelle deur beoordeling met die oog op 'n raadsbesluit.
04 Raadsbesluit
- 09Openbare laaste oproepStap · Global Standards CouncilDie Global Standards Council aanvaar by 'n tweederdemeerderheid ná 'n laaste oproep van negentig dae.
- 10Wêreldwye aanvaarding van 'n standaardBesluit · Global Standards CouncilDie Wêreldwye Standaarderaad besluit oor die aanvaarding van elke standaard ná 'n openbare laaste oproep.
05 Publiseer en identifiseer
- 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
- 12'n UNI identifiseer en sertifiseer nooit nieRekord · Nexus StandardsElke objek van die programjaar dra een identifiseerder, 'n UNI onder NS-1, sodat dit aangehaal, geweergaweer en opgelos kan word.
- 13Publiseer die jaar se aanvaarde veranderingeStap · Nexus StandardsBy hernuwing publiseer Nexus Standards die jaar se aanvaarde veranderinge en die nasionale aanvaardingstatus.
06 Nasionale aanvaarding en toepassing
- 14Nasionale aanvaarding deur die Nasionale StandaarderaadBesluit · Nasionale StandaarderaadElke land se Nasionale Standaarderaad besluit oor nasionale aanvaarding: aanvaar soos dit is, aanvaar met 'n profiel (NS-16), pas aan, of verwys slegs.
- 15Aangenome standaarde bereik kursusse en uitgawesStap · Nexus StandardsElke aangenome standaard of profiel word 'n kursusmodule by Risk Academy (F09), en standaarde word in Reports-uitgawes (R1) toegepas.
- 16Aanvaarding is finaal vir elke jurisdiksieStandaard · Nasionale StandaarderaadAanvaarding is finaal vir elke jurisdiksie, en die GSC het geen veto oor 'n nasionale besluit nie. Geen globale liggaam hou 'n veto nie.
- 17Nasionale aanvaardingsrekordsRekord · Nexus StandardsSaamgestelde missieprofiele en nasionale aanvaardingsrekords gaan na die Foundry by gereedheidsvoorbereiding (F08).
Nexus Standards · Nexus Standards (institution) · National Standards CouncilAn outline of the designed programme cycle, not a record of operation: no cycle has run and every programme is at service level R0. Every Nexus Standard is at the PROPOSED stage and nexustandards.com governs the text and status of each one. A UNI identifies and never certifies; a validator report is evidence for review, not a conformance claim.
The operations, as a table
| Step | Phase | Operation | Who | Decision rule | Record | Implements |
|---|---|---|---|---|---|---|
| 01 | Mandaat | Mandate issued (start). The mandate states which clauses the evaluator may evaluate, for which subjects, and is named in every attestation. | the trust authority of the consumer | an evaluator holds a recorded mandate; the subject never evaluates itself | a revocable mandate naming clauses and subjects | NS11-R1, NS11-R2 |
| 02 | Bewyse | Gather evidence (record). Record references take the form recordUni@recordVersion; external reports are cited with a digest. | the subject, granting read access | evidence kinds are shared with NS-10 | record references, receipts, digests, signed attestations, observations, reports, decisions | NS11-R1 |
| 03 | Bewyse | Evidence resolves (gate). An inaccessible source or a missing mandate is itself recorded as a refusal. | the evaluator | missing or unresolvable evidence is INDETERMINATE or REFUSED, never PASS | resolved evidence, or INDETERMINATE or REFUSED | NS11-R3, NS0-P12 |
| 04 | Evaluation | Evaluate (exercise). The clause predicate is evaluated over the resolved evidence at a recorded instant. | the evaluator, outside the subject’s trust boundary | subject and evaluator are distinct; production evaluations run outside the subject’s boundary | the clause result with engine and version | NS11-R2 |
| 05 | Evaluation | Result (decision). Not applicable means the subject was outside the clause’s selectors at that instant. | the evaluator | one result per clause, subject and evaluation | PASS, FAIL, INDETERMINATE, NOT_APPLICABLE or REFUSED | NS11-R3 |
| 06 | Attestation | Attestation (record). An attestation can be exported as a Verifiable Credential, an in-toto attestation or a PROV-O activity; the Nexus attestation remains the record. | the evaluator | no attestation without an evaluator, a mandate, evidence references and a digest; attestations are append-only | an attestation (AT) with evaluator, mandate, evidence references, digest and instant | NS11-R1, NS11-R4, NS11-R6 |
| 07 | Monitering | Monitor (step). A change in the subject’s records that invalidates an attestation is recorded as drift and triggers re-evaluation. | the monitoring service | monitoring records are observations with record UNIs | observations: latest attestation per clause, coverage, drift, availability | NS11-R4 |
| 08 | Monitering | Generated report (end). Reports are generated, not written, and are published only when their legal state allows. | the reporting service | every displayed value carries its evaluation instant and evaluator; projections never store verdicts | a report (RP) clause by clause with attestation UNIs and instants | NS11-R5 |
Table.Operations in walking order; each row names the phase, the operation, its actor, its decision rule, the record it leaves and the rule identifiers it implements. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: QA Framework: Specification Guidelines · RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words (BCP 14) · NS-11: Verification and monitoring · NS-10: Policies and clauses.
Foundation, referenced and implementing layers
The standards architecture of this context, from the foundation standards to the open standards referenced (grouped by type of relation) and the services and data sources that build on them.
The interactive view requires JavaScript; the sections below present the same records.
The conformance pipeline, step by step
Declaration, selection of clauses, evidence, the evaluator’s run, attestations, the statement and its expiry.
Process explorer · NXS · Process
Conformance pipeline
10 steps·4 stages·2 gates
NXS · Process
Conformance pipeline
Lewensiklus van 'n standaard · NS-13-spoor · Bydraekanale · IETF-spoor · W3C-spoor · OGC-spoor · OASIS-spoor · ISO- en IEC-fases · Konformiteit · Rekordlewensiklus · Roetering · Monitering.
An adopter declares classes, clauses are selected, evidence referenced, a mandated evaluator attests each result, and the statement expires on a stated date.
01 Adopter
- 01DeclarationStart · the adopter, namedThe adopter names the standard version and the conformance classes it claims for a subject (a context or an artefact, NS-9).
- 03EvidenceRecord · the adopterEvidence is referenced by record identifier and digest; the evidence itself remains with the adopter.
- 10RestorationStep · the adopterAfter expiry the adopter requests a new evaluation; the history is retained.
02 Nexus records
- 02Clause selectionModel · the reference clause toolingThe standard’s machine-readable clauses are selected by the classes claimed.
- 06AttestationRecord · the evaluator’s run, recordedAn attestation names the evaluator, the instant and the evidence it read.
- 07Implementation conformance statementRecord · the adopter, listed as submittedThe public register lists statements as submitted, with their evidence links and expiry dates.
03 Evaluator
- 04Mandate checkGate · the evaluatorThe mandate states who may evaluate what; without a mandate the evaluation is REFUSED.
- 05Evaluator runExercise · the evaluatorThe run reads the evidence and applies the clause set; the result per clause is recorded.
04 Over time
- 08ExpiryGate · the registry, by validUntilAn expired statement remains listed and is shown as expired; restoration requires a new evaluation.
- 09Authority decisionOutcome · an entitled body, outside the standardA competent body’s own scheme decision is cited by reference. Nexus Standards conformance is distinct from it.
NS-10: policies and clauses · NS-11: verification and attestations · Conformance programmeAn outline of how the work is designed to run; it does not report the status of any decision or record.
The operations, as a table
| Step | Phase | Operation | Who | Decision rule | Record |
|---|---|---|---|---|---|
| 01 | Adopter | Declaration (start). The adopter names the standard version and the conformance classes it claims for a subject (a context or an artefact, NS-9). | the adopter, named | a first-party declaration, in the sense of ISO/IEC 17050 | a declaration with the classes claimed |
| 02 | Nexus records | Clause selection (model). The standard’s machine-readable clauses are selected by the classes claimed. | the reference clause tooling | every normative statement is an NS-10 clause; classes select clauses | the clause set for the classes |
| 03 | Adopter | Evidence (record). Evidence is referenced by record identifier and digest; the evidence itself remains with the adopter. | the adopter | referenced rather than embedded; missing evidence yields INDETERMINATE | evidence references: receipts, digests, record UNIs |
| 04 | Evaluator | Mandate check (gate). The mandate states who may evaluate what; without a mandate the evaluation is REFUSED. | the evaluator | an evaluator acts under a recorded mandate and is independent of the subject | a mandate reference |
| 05 | Evaluator | Evaluator run (exercise). The run reads the evidence and applies the clause set; the result per clause is recorded. | the evaluator | the open test suite, on the referenced evidence | the run with suite version and instant |
| 06 | Nexus records | Attestation (record). An attestation names the evaluator, the instant and the evidence it read. | the evaluator’s run, recorded | PASS, FAIL, INDETERMINATE, NOT_APPLICABLE or REFUSED; certifiesTruth is always false | one attestation per clause, subject and evaluation |
| 07 | Nexus records | Implementation conformance statement (record). The public register lists statements as submitted, with their evidence links and expiry dates. | the adopter, listed as submitted | listed as submitted by the adopter | the ICS with a UNI and validUntil |
| 08 | Over time | Expiry (gate). An expired statement remains listed and is shown as expired; restoration requires a new evaluation. | the registry, by validUntil | a statement expires at validUntil; the history is retained | an expired statement, still listed |
| 09 | Adopter | Restoration (step). After expiry the adopter requests a new evaluation; the history is retained. | the adopter | restoration requires a new evaluation | a new evaluation request |
| 10 | Over time | Authority decision (end). Where a competent body operates its own scheme, its decision is cited by reference; conformance to the Nexus Standards is distinct from that decision. | an entitled body, outside the standard | cited where it exists; separate from any attestation | a decision referenced by identifier |
Table.An adopter declares the conformance classes it claims; clauses are selected from the standard’s NS-10 clause set; evidence is referenced; an evaluator acting under a mandate runs the evaluation; each result is recorded as an attestation; the implementation conformance statement is listed as submitted and expires on a stated date; restoration requires a new evaluation. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: NS-10: policies and clauses · NS-11: verification and attestations · Conformance programme.
Sistemiese koppelings
4 couplings link this area to other areas and programmes, each with the mechanism of the link.
- How a standard is madeFoundations and GovernanceThe executable test suite is a gate for the Proposed stage and two independent implementations that pass it are a gate for the Candidate stage, so conformance tooling is developed during drafting rather than afterwards.
- The UNI and the artefact catalogueFoundations and GovernanceEach Implementation Conformance Statement and attestation is an AT record with a UNI, so declarations are citable, versioned and never silently edited.
- Compatibility profiles for closed standardsFoundations and GovernanceFor closed standards the same declaration model is applied to synthetic example data only, and results are not presented as conformance to the closed standard itself.
- Trust, Verification and AssuranceTrust, Verification and AssuranceThe Trust, Verification and Assurance programme covers the attestation and monitoring arrangements (evaluators, mandates, digests, INDETERMINATE results) that a declaration’s evidence points to.
How a shock travels through this system
A system model of this area built from the registry: 5 systems, 4 sectors, 9 controls, 2 feeds, 2 indicators. Select the components to include, choose an initiating hazard and run the scenario. Stress propagates through the hazard relations of the Nexus Hazard Standard (NHS-1), the exposure of each system, the recorded couplings and the sectors that carry the loss; adopted standards dampen transmission and live data sources support detection. All parameters are stated assumptions that the reader can adjust; results are illustrative scenario outputs for exercises and training, not forecasts or risk assessments.
Systems and couplings
Controls
NS-10Beleide en klousules (masjienleesbare verpligtinge: definisie, binding, evaluering en afdwinging)NS-11Verifikasie en monitering (getuienis, attestasies, zero-trust-ooreenstemmingwaarneming)NS-1Die UNI en die artefakkatalogus (grammatika v0.2: domein-, sektor-, streek- en omgewingsegmente)NRS-C11Konformiteit, verifikasie en instandhouding van standaardeNRS-S19System profile: NXS-POR (Public, client and partner delivery)NRS-S3System profile: NXS-DSS (Decision cases and deliberation)NRS-A9Evalueringsreekse vir KI in risikowerkNRS-H112Hazard family: Governance and institutional failure (NHS-1 soc.governance)NRS-S1System profile: NXS-CMD (Integrated posture and executive synthesis)
Observation
- OpenSSF Scorecard public results (reference model for published, machine-run evidence) (listed for reference)
- Zenodo REST API (deposit of test-run evidence bundles with DOIs) (listed for reference)
- Hosted build platform with signed provenance
- Metadata complies with a community standard
Evidence recorded
- Clause sets stated10
- Test suites22 in progress
- Statements submitted0
- Attestations recorded0
- Body validators linked3
Conformance statements are listed as submitted.
| Standaard | Clauses (NS-10) | Test suite | Conformance statements | Attestations | Body’s own suite or validator |
|---|---|---|---|---|---|
| NS-0 Constitution and principles | stated12 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-1 The UNI and the artefact catalogue… | stated10 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-2 Citation and attribution format for… | stated5 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-3 Risk record UNIs (grammar, legacy… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-3b Dataset and product metadata profile… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-4 Structure and drafting of Nexus… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-5 Figure, map and visualisation… | stated5 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-6 Surface wiring (API header, panel… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-7 Resolver landing pages, page meta… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-8 Zenodo publishing workflow with legal… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-9 Contextual UNIs (deployments,… | stated5 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-10 Policies and clauses… | stated7 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-11 Verification and monitoring… | stated6 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-12 Software, model and AI/ML artefacts… | stated4 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-13 Standards development process (open… | stated5 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-14 Conformance and crosswalk to… | stated5 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-15 System model binding (identity… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-16 UNI application profile (context… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NRS Nexus Risk Standards: the systemic… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| CAP 1.2 | noneno Nexus clauses yet (proposed under NS-10) | plannedin progress | nonenone submitted | nonenone recorded | linkedCAP 1.2 XML Schema |
| STAC | noneno Nexus clauses yet (proposed under NS-10) | plannedin progress | nonenone submitted | nonenone recorded | linkedstac-validator |
| PROV-O | noneno Nexus clauses yet (proposed under NS-10) | plannedin progress | nonenone submitted | nonenone recorded | linkedPROV-CONSTRAINTS validators listed in the implementation report |
Process explorer · NXS · Process
Conformance pipeline
10 steps·4 stages·2 gates
NXS · Process
Conformance pipeline
An adopter declares classes, clauses are selected, evidence referenced, a mandated evaluator attests each result, and the statement expires on a stated date.
01 Adopter
- 01DeclarationStart · the adopter, namedThe adopter names the standard version and the conformance classes it claims for a subject (a context or an artefact, NS-9).
- 03EvidenceRecord · the adopterEvidence is referenced by record identifier and digest; the evidence itself remains with the adopter.
- 10RestorationStep · the adopterAfter expiry the adopter requests a new evaluation; the history is retained.
02 Nexus records
- 02Clause selectionModel · the reference clause toolingThe standard’s machine-readable clauses are selected by the classes claimed.
- 06AttestationRecord · the evaluator’s run, recordedAn attestation names the evaluator, the instant and the evidence it read.
- 07Implementation conformance statementRecord · the adopter, listed as submittedThe public register lists statements as submitted, with their evidence links and expiry dates.
03 Evaluator
- 04Mandate checkGate · the evaluatorThe mandate states who may evaluate what; without a mandate the evaluation is REFUSED.
- 05Evaluator runExercise · the evaluatorThe run reads the evidence and applies the clause set; the result per clause is recorded.
04 Over time
- 08ExpiryGate · the registry, by validUntilAn expired statement remains listed and is shown as expired; restoration requires a new evaluation.
- 09Authority decisionOutcome · an entitled body, outside the standardA competent body’s own scheme decision is cited by reference. Nexus Standards conformance is distinct from it.
NS-10: policies and clauses · NS-11: verification and attestations · Conformance programmeAn outline of how the work is designed to run; it does not report the status of any decision or record.
The operations, as a table
| Step | Phase | Operation | Who | Decision rule | Record |
|---|---|---|---|---|---|
| 01 | Adopter | Declaration (start). The adopter names the standard version and the conformance classes it claims for a subject (a context or an artefact, NS-9). | the adopter, named | a first-party declaration, in the sense of ISO/IEC 17050 | a declaration with the classes claimed |
| 02 | Nexus records | Clause selection (model). The standard’s machine-readable clauses are selected by the classes claimed. | the reference clause tooling | every normative statement is an NS-10 clause; classes select clauses | the clause set for the classes |
| 03 | Adopter | Evidence (record). Evidence is referenced by record identifier and digest; the evidence itself remains with the adopter. | the adopter | referenced rather than embedded; missing evidence yields INDETERMINATE | evidence references: receipts, digests, record UNIs |
| 04 | Evaluator | Mandate check (gate). The mandate states who may evaluate what; without a mandate the evaluation is REFUSED. | the evaluator | an evaluator acts under a recorded mandate and is independent of the subject | a mandate reference |
| 05 | Evaluator | Evaluator run (exercise). The run reads the evidence and applies the clause set; the result per clause is recorded. | the evaluator | the open test suite, on the referenced evidence | the run with suite version and instant |
| 06 | Nexus records | Attestation (record). An attestation names the evaluator, the instant and the evidence it read. | the evaluator’s run, recorded | PASS, FAIL, INDETERMINATE, NOT_APPLICABLE or REFUSED; certifiesTruth is always false | one attestation per clause, subject and evaluation |
| 07 | Nexus records | Implementation conformance statement (record). The public register lists statements as submitted, with their evidence links and expiry dates. | the adopter, listed as submitted | listed as submitted by the adopter | the ICS with a UNI and validUntil |
| 08 | Over time | Expiry (gate). An expired statement remains listed and is shown as expired; restoration requires a new evaluation. | the registry, by validUntil | a statement expires at validUntil; the history is retained | an expired statement, still listed |
| 09 | Adopter | Restoration (step). After expiry the adopter requests a new evaluation; the history is retained. | the adopter | restoration requires a new evaluation | a new evaluation request |
| 10 | Over time | Authority decision (end). Where a competent body operates its own scheme, its decision is cited by reference; conformance to the Nexus Standards is distinct from that decision. | an entitled body, outside the standard | cited where it exists; separate from any attestation | a decision referenced by identifier |
Table.An adopter declares the conformance classes it claims; clauses are selected from the standard’s NS-10 clause set; evidence is referenced; an evaluator acting under a mandate runs the evaluation; each result is recorded as an attestation; the implementation conformance statement is listed as submitted and expires on a stated date; restoration requires a new evaluation. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: NS-10: policies and clauses · NS-11: verification and attestations · Conformance programme.
A test result is implementation evidence, stating the suite version and the date and time; a conformance statement is the implementer’s own declaration, listed as submitted; an attestation names its evaluator and mandate.
Standards that apply
The area profile lists 3 Nexus Standards. Each is a proposed standard under development.
- 01
NS-10 · Policies and clauses (machine-readable obligations: definition, binding, evaluation and enforcement)
Status: proposed · 7 requirements stated. Read NS-10.
- 02
NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)
Status: proposed · 6 requirements stated. Read NS-11.
- 03
NS-1 · The UNI and the artefact catalogue (grammar v0.2: domain, sector, region and environment segments)
Status: proposed · 10 requirements stated. Read NS-1.
Working group charter
A proposed charter for this area, open to institutions and experts.
Maintain the conformance model, the declaration record kind, the test-suite conventions and the register’s wording.
Institutions and experts are invited to charter this working group under NS-13 by filing a public change record. National Working Groups (NWGs) contribute national inputs and field exercises through their National Nexus Consortium (NNC).
- Conformance class and abstract test suite template
- Implementation Conformance Statement schema and register procedure
- Reference test harness for browser and continuous-integration use (Apache-2.0)
- OGC Compliance Program (information exchange on executable tests sought) liaison sought
- OpenSSF (information exchange on attestation levels sought) liaison sought
- NIST OSCAL community (information exchange on assessment results sought) liaison sought
Open standards referenced
5 open standards, each with its relation as recorded in the register under NS-14. Hover over or focus a relation for its definition.
Routing, monitoring and verification tools
Verification console
Test suites, conformance statements and attestations for each standard, as recorded in the registry.
In progressMonitoring console
Version and source status for each standard, as published by the issuing bodies.
Each console computes from the registry and states its reasoning; decisions remain with the competent bodies.
Open research questions
3 questions identified as priorities for the working group.
- How to prevent a self-declaration from being read as third-party assurance when a vendor quotes it out of context.
- How to test clauses whose evidence is a human decision or an institutional process rather than a machine-checkable artefact.
- How to keep test suites in step with external baselines (for example a new STAC or CAP version) without invalidating earlier declarations.
Evidence, recognition and capital pathways
What each institution of the ecosystem draws from this area: The Global Centre for Risk and Innovation (GCRI Canada), as Secretariat, for evidence; The Global Risks Forum (GRF) for recognition; and The Global Risks Alliance (GRA) for capital.
GCRI Canada
GCRI Canada decides under its own evidence rules whether a published declaration and its test-run evidence are usable; the register lists declarations without verifying them.
Die Global Risks Forum (GRF)
The Global Risks Forum (GRF) decides recognition under its own programme rules; a declaration in the register is not a GRF recognition.
Die Global Risks Alliance (GRA)
The Global Risks Alliance (GRA) decides capital readiness under its own criteria and may read declarations as one input among others.
Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.
Intended users
The area profile identifies 4 user communities.
- implementers and vendors
- adopting institutions
- auditors and reviewers
- developers
Restricted compatibility profiles
1 standard whose text is not openly available, named and linked only. Any compatibility profile is kept on protected pages until an arrangement with the issuing body is in place.
- ISO/IEC 17000:2020 Conformity assessment – Vocabulary and general principlesISO/CASCO with IECcompatibility profile (restricted)
Data sources
2 data sources named in the area profile, each with provider, licence, update frequency and delivery path.
Data sources are listed for reference; live data is displayed once licence review is complete.
- Lewendig
- 0
- on completion of licence review
- Listed in the data register
- 0
- licence terms recorded
- Proposed for the register
- 2
- licence terms to be recorded
- Delivery
- 0 governed service · 0 plugin · 0 browser · 1 snapshot · 1 listed for reference
- proposed paths in order of preference: governed data service, plugin, direct browser read, build-time snapshot; sources whose terms do not permit reuse are listed for reference only
OpenSSF Scorecard public results (reference model for published, machine-run evidence)for reference.
OpenSSF · weekly
Apache-2.0 (tool); results published by OpenSSF
build-time snapshotproposed for the data register
Zenodo REST API (deposit of test-run evidence bundles with DOIs)for reference.
CERN (Zenodo) · continuous
CC0 1.0 (record metadata); files under their stated licence.
listed for referenceproposed for the data register.
Aanwysers
The area profile names 2 indicators, each with its framework and code.
Indicator names and codes are given as published by their stewards.
Hazards, threats and sectors concerned
Hazards and threats 0
This area draws on the hazards of the areas it is coupled with.
Sektore 0
This area serves all sectors through the areas it is coupled with.
Bronne
4 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.
peer-reviewedThe economics of compatibility standards: an introduction to recent researchEconomics of Innovation and New Technology · 1990- officialNIST Cybersecurity Framework (CSF) 2.0NIST · 2024
- standardSLSA specification v1.1OpenSSF · 2025
- standardQA Framework: Specification GuidelinesW3C · 2005
Recent research on this area
Recent peer-reviewed articles, preprints, datasets and reports on the subject of this area, 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 termsconformance testing; conformity assessment; self-assessment; QA FrameworkDerived from the title and scope of the area, the NHS-1 hazards it names and the open standards it lists.
- 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.
Risk Academy courses and disciplines
2 courses and 4 disciplines of Risk Academy (risksacademy.com) that teach the knowledge and methods of this area. Each course lists its level, stream and learning hours.
Kursusse
Dissiplines
The correspondence between courses, disciplines and the Nexus Standards is maintained with Risk Academy and is subject to its academic review.
Programmes, tracks and courses for this area
GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA) and Risk Academy work on the subject of this area in distinct roles (research and evidence; governance, policy and convening; capital, finance and markets; education and training). Each entry states why it corresponds and the step it offers; each institution sets its own terms of participation.
Navorsing en bewyse
GCRI Canada
Research programmes that produce the observations, models and assessments these records describe.
Systemic Risk ManagementDevelops assurance and correction practice for risk processes, the discipline that conformance from evidence applies.Apply to this programme Systems Science and ModellingSets methods for uncertainty and validation, on which executable conformance tests and their limits rest.Apply to this programme therisk.globalAll programmes of GCRI CanadaGovernance, policy and convening
Die Global Risks Forum (GRF)
Tracks that convene public authorities, researchers and institutions on the governance of shared risks.
Governance NexusCompares authority, oversight and anti-capture arrangements in institutions, the questions that the standards process answers for its own decisions.Join this track Research NexusConvenes research on research integrity and the science-policy interface, the basis of evidence over assertion.Join this track globalriskforum.comAll tracks of The Global Risks ForumCapital, finance and markets
Die Global Risks Alliance (GRA)
Industry programmes in which financial institutions build a shared understanding of systemic risk.
AI and Financial Model RiskWorks on model validation and monitoring in finance, an established case of assurance demonstrated from evidence.Join this programme globalriskalliance.comAll programmes of The Global Risks AllianceOnderwys en opleiding
Risk Academy
Courses and disciplines that teach the knowledge and methods practitioners need to apply these standards.
Technology and DataRAT-204 · Intermediate · 19 learning hoursManaging risk data, AI, digital infrastructure and technology risk responsiblyTake this course Uncertainty and ConfidenceRAS-404 · Intermediate · 29.5 learning hoursCalibrated probability, confidence language and decisions under deep uncertaintyTake this course All courses and disciplinesListed in the education and training section of this pageKernterme
- UNI
- Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
- voorgestel
- A draft in the open development process that the Global Standards Council has not yet adopted. Each area profile is a proposal to the Nexus Standards registry.
- profile
- Relation in which a Nexus profile narrows or extends the external standard for a defined use, validated with the issuing body’s own tools where these exist.
- adopt
- Relation in which the external standard is used as published and values are validated against it.
- cite
- Relation in which the external standard is cited by identifier and URL as a reference.
- crosswalk
- Relation in which clauses of these standards are mapped to parts of the external standard by clause number, without reproducing its text.
- compatibility profile (restricted)
- Relation to a standard whose text is not openly available: the standard is named and linked only, and any compatibility profile is kept on protected pages.
- change record
- A public record of a proposed change under NS-13, decided by the editors with written reasons.
- attestation
- An evaluator’s recorded result for one clause and one subject under NS-11.
- liaison sought
- A liaison the working group intends to request from the issuing body; a liaison is established only when the body confirms it in writing.
Related areas
Recent research and sources
Peer-reviewed articles, preprints, reports and datasets on the subject of this area, retrieved at the time of reading from open scholarly metadata services (OpenAlex and Crossref) and listed with authors, venue, year, type and access status, with a link to each work. Curated references and related standards are listed first; recent works matched by subject follow and are listed for orientation.
Curated references
- QA Framework: Specification Guidelines
W3C · 2005 · Standard - The economics of compatibility standards: an introduction to recent research
Economics of Innovation and New Technology · 1990 · Peer-reviewed - NIST Cybersecurity Framework (CSF) 2.0
NIST · 2024 · Official publication - SLSA specification v1.1
OpenSSF · 2025 · Standard
Related standards and frameworks
- QA Framework: Specification Guidelines
W3C - RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words (BCP 14)
IETF (RFC Editor) - OGC Compliance Program and TEAM Engine executable test suites
Open Geospatial Consortium - Supply-chain Levels for Software Artifacts (SLSA) v1.1
OpenSSF - Open Security Controls Assessment Language (OSCAL)
NIST
Search terms, derived from the title and scope of the area: conformance testing; conformity assessment; self-assessment. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.
Questions and answers.
What is the status of the Conformance programme area?
How are data sources presented?
How can this brief be amended?
Dra bewyse vanaf hierdie bladsy by.
Reports is die Konsortium se kwartaallikse publikasie. Wat jy oor hierdie onderwerp weet, kan bewyse, 'n saak of 'n korreksie in die volgende uitgawe word, aan jou toegeskryf en onder CC BY 4.0 gepubliseer waar dit jou eie werk is.
- E-posPoort GW-STDStuur dit vanaf hierdie bladsyGetuienis, 'n regstelling, 'n geval, 'n metode, 'n beoordeling, 'n vertaling of profielinset. Dit kom aan gemerk met hierdie bladsy, sodat die redakteur wat dit besit dit ontvang.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsNexus StandardsSee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Stuur nooit persoonlike data, sensitiewe infrastruktuurbesonderhede of enigiets wat u geen reg het om te deel nie. 'n Bydrae word voor gebruik beoordeel; die stuur daarvan verleen geen outeurskap of redaksionele regte nie, en borgskap koop nooit 'n bevinding nie.
Contribute to Conformance programme
Institutions and experts are invited to propose amendments, join the working group or propose data sources. National participation is organised through each country’s National Nexus Consortium (NNC) and its National Working Groups (NWGs); competent national authorities are engaged through official channels.
Status en gebruik. Die Nexus Standards is voorgestelde standaarde wat deur 'n oop proses onder NS-13 ontwikkel en vir vrywillige gebruik gepubliseer word; hulle maak nie sertifisering, akkreditasie of regulatoriese goedkeuring uit nie, en aanvaarding bly 'n besluit van die Wêreldwye Standaarderaad en, in elke land, van sy Nasionale Standaarderaad. 'n UNI (Unique Nexus Identifier) identifiseer 'n artefak; dit sertifiseer dit nie. Name van standaardliggame en hul standaarde behoort aan hul rentmeesters en word slegs gebruik om die dokumente te identifiseer; geen teks van 'n eksterne standaard word hier gereproduseer nie. Nexus Standards is nie geaffilieer met, onderskryf deur of gesertifiseer deur enige standaardliggaam wat hier genoem word nie.
Lisensies: CC BY 4.0 vir standaardteks, registers, skemas en data; Apache-2.0 vir verwysingskode. Eksterne standaarde word volgens naam, nommer en skakel onder hul eie lisensies aangehaal. Derdeparty-data, -biblioteke en -lettertipes behou hul eie lisensies: sien Kennisgewings van derde partye.