Skip to content
ImigangathoIziseko noLawuloIziseko
Area · proposed

Conformance programme

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

Conformance programme
What this area is built from: the Nexus Standards it applies, the open standards it names and the data and feeds it reads, then the areas its record couples it with (marked).Source: the Nexus Standards registry: the area record.
  • 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.
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
Imeko
Proposednot yet in the catalogue
Last reviewed
area profile
Cite this page

Nexus Standards (2026). Conformance programme: area brief, Foundations and Governance programme. Proposed. https://nexustandards.com/foundations/conformance-programme/. Last reviewed 17 October 2026.

Download the profile

Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.

02Ubungakanani bomsebenzi

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.

03Conformance programme

Conformance programme

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

IbalaContent
Declarantthe implementer, named
Classesthe conformance classes claimed and the version of the standard
Ubungqinatest results, by reference
Evaluator and datenamed, with the date
Identifiera 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

Compatibility profiles for closed standards

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.

04Inkqubo yokusebenza

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.

Umhloli weenkqubo · Standards · ukuchaza nokulungisa

Umjikelo wobomi bomgangatho

Amanyathelo ali-17Izigaba ezi-6

Standards · ukuchaza nokulungisa

Umjikelo wobomi bomgangatho

Iziphumo zomjikelo ziba ziziphakamiso zotshintsho, iBhunga leMigangatho yeHlabathi liyamkela emva komnxeba wokugqibela woluntu, kwaye ilizwe ngalinye ligqiba ukwamkela kwalo.

  1. 01 Thumela iimishini

    1. 01Route missions to standards and profilesStep · Nexus StandardsNexus Standards routes each candidate mission to the standards and profiles that apply.
  2. 02 Iiprofayile nokuhambelana

    1. 02Qamba iiprofayile zeemishiniInyathelo · Nexus StandardsI-Nexus Standards iqamba iiprofayile zeemishini kwaye ibhale nakuphi na ukwamkelwa kwesizwe iimishini ezixhomekeke kuko.
    2. 03Qinisekisa iziphumo zokwakha ngokwamaprofayileInyathelo · Nexus StandardsI-Nexus Standards iqinisekisa iziphumo zokwakha ngokwamaprofayile aqanjiweyo kwaye ibhale ubungqina.
    3. 04Beka iliso kukuhambelana uze ubhale ubungqina obutywiniweyoInyathelo · Nexus StandardsNgexesha leVeki yeNtshukumo i-Nexus Standards ibeka iliso kukuhambelana kwaye ibhale ukuphambuka.
  3. 03 Iziphakamiso nophononongo

    1. 05Ukuphambuka nolungiso ziba ziziphakamiso zotshintshoInyathelo · Nexus StandardsUkuphambuka kuba ziziphakamiso zotshintsho, kwaye ulungiso lubhalwa njengotshintsho kubungqina.
    2. 06Iziphumo zomjikelo ziba ziziphakamiso zotshintshoInyathelo · Nexus StandardsIziphumo zomjikelo ziba ziziphakamiso zotshintsho: iziphumo zendlela nezolungiso ezivela Iingxelo (F06) nezinto zedokethi ezivela kwi-Nexus…
    3. 07Yila uze uhlaziye ekuhleniInyathelo · Iikomiti namaqela asebenzayoIikomiti zobugcisa namaqela asebenzayo ayila kwaye ahlaziye imigangatho kwinkqubo evulekileyo ye-NS-13.
    4. 08Uphononongo olusingise kwisigqibo sebhungaInyathelo · Nexus StandardsI-Nexus Standards ihambisa iziphakamiso zotshintsho kuphononongo zisingise kwisigqibo sebhunga.
  4. 04 Isigqibo sebhunga

    1. 09Umnxeba wokugqibela woluntuInyathelo · IBhunga leMigangatho yeHlabathiIBhunga leMigangatho yeHlabathi liyamkela ngesininzi sesibini kwisithathu emva komnxeba wokugqibela weentsuku ezingamashumi alithoba.
    2. 10Ukwamkelwa kwehlabathi komgangathoIsigqibo · IBhunga leMigangatho yeHlabathiIBhunga leMigangatho yeHlabathi ligqiba ukwamkelwa komgangatho ngamnye emva komnxeba wokugqibela woluntu.
  5. 05 Papasha uze uchonge

    1. 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
    2. 12I-UNI iyachonga kwaye ayize iqinisekiseIrekhodi · Nexus StandardsYonke into yonyaka wenkqubo ithwele isichongi esinye, i-UNI phantsi kwe-NS-1, ukuze icatshulwe, inikwe iinguqulelo kwaye isonjululwe.
    3. 13Papasha utshintsho olwamkelweyo lonyakaInyathelo · Nexus StandardsEkuhlaziyweni i-Nexus Standards ipapasha utshintsho olwamkelweyo lonyaka nemeko yokwamkelwa kwesizwe.
  6. 06 Ukwamkelwa nokusetyenziswa kwesizwe

    1. 14Ukwamkelwa kwesizwe liBhunga leMigangatho leSizweIsigqibo · IBhunga leMigangatho leSizweIBhunga leMigangatho leSizwe lelizwe ngalinye ligqiba ukwamkelwa kwesizwe: yamkela njengoko injalo, yamkela ngeprofayile (NS-16), lungelelanisa, okanye bhekisa kuphela.
    2. 15Imigangatho eyamkelweyo ifikelela kwizifundo nakwiinguquleloInyathelo · Nexus StandardsUmgangatho ngamnye owamkelweyo okanye iprofayile iba yimodyuli yekhosi kwi-Risk Academy (F09), kwaye imigangatho isetyenziswa kwiinguqulelo ze-Reports (R1).
    3. 16Ukwamkelwa kugqibelele kummandla wolawulo ngamnyeUmgangatho · IBhunga leMigangatho leSizweUkwamkelwa kugqibelele kummandla wolawulo ngamnye, kwaye i-GSC ayinalo ilungelo lokuvala isigqibo sesizwe. Akukho qumrhu lehlabathi linelungelo lokuvala.
    4. 17Iirekhodi zokwamkelwa kwesizweIrekhodi · Nexus StandardsIiprofayile zeemishini eziqanjiweyo neerekhodi zokwamkelwa kwesizwe ziya kwi-Foundry ngexesha lokulungiselela ukulungela (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
Process · evaluation and attestation under zero trust (NS-11)8 operations · 5 phases
InyatheloPhaseUkusebenzaWhoDecision ruleIrekhodiImplements
01IgunyaMandate 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 consumeran evaluator holds a recorded mandate; the subject never evaluates itselfa revocable mandate naming clauses and subjectsNS11-R1, NS11-R2
02UbungqinaGather evidence (record). Record references take the form recordUni@recordVersion; external reports are cited with a digest.the subject, granting read accessevidence kinds are shared with NS-10record references, receipts, digests, signed attestations, observations, reports, decisionsNS11-R1
03UbungqinaEvidence resolves (gate). An inaccessible source or a missing mandate is itself recorded as a refusal.the evaluatormissing or unresolvable evidence is INDETERMINATE or REFUSED, never PASSresolved evidence, or INDETERMINATE or REFUSEDNS11-R3, NS0-P12
04UvavanyoEvaluate (exercise). The clause predicate is evaluated over the resolved evidence at a recorded instant.the evaluator, outside the subject’s trust boundarysubject and evaluator are distinct; production evaluations run outside the subject’s boundarythe clause result with engine and versionNS11-R2
05UvavanyoResult (decision). Not applicable means the subject was outside the clause’s selectors at that instant.the evaluatorone result per clause, subject and evaluationPASS, FAIL, INDETERMINATE, NOT_APPLICABLE or REFUSEDNS11-R3
06AttestationAttestation (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 evaluatorno attestation without an evaluator, a mandate, evidence references and a digest; attestations are append-onlyan attestation (AT) with evaluator, mandate, evidence references, digest and instantNS11-R1, NS11-R4, NS11-R6
07Ukubeka ilisoMonitor (step). A change in the subject’s records that invalidates an attestation is recorded as drift and triggers re-evaluation.the monitoring servicemonitoring records are observations with record UNIsobservations: latest attestation per clause, coverage, drift, availabilityNS11-R4
08Ukubeka ilisoGenerated report (end). Reports are generated, not written, and are published only when their legal state allows.the reporting serviceevery displayed value carries its evaluation instant and evaluator; projections never store verdictsa report (RP) clause by clause with attestation UNIs and instantsNS11-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.

05Standards architecture

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.

06Pipeline

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 steps4 stages2 gates

NXS · Process

Conformance pipeline

Umjikelo wobomi bomgangatho · Indlela ye-NS-13 · Iindlela zokunikela · Indlela ye-IETF · Indlela ye-W3C · Indlela ye-OGC · Indlela ye-OASIS · Izigaba ze-ISO ne-IEC · Ukuhambelana · Umjikelo wobomi werekhodi · Ukuthumela · Ukubeka iliso.

An adopter declares classes, clauses are selected, evidence referenced, a mandated evaluator attests each result, and the statement expires on a stated date.

  1. 01 Adopter

    1. 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).
    2. 03EvidenceRecord · the adopterEvidence is referenced by record identifier and digest; the evidence itself remains with the adopter.
    3. 10RestorationStep · the adopterAfter expiry the adopter requests a new evaluation; the history is retained.
  2. 02 Nexus records

    1. 02Clause selectionModel · the reference clause toolingThe standard’s machine-readable clauses are selected by the classes claimed.
    2. 06AttestationRecord · the evaluator’s run, recordedAn attestation names the evaluator, the instant and the evidence it read.
    3. 07Implementation conformance statementRecord · the adopter, listed as submittedThe public register lists statements as submitted, with their evidence links and expiry dates.
  3. 03 Evaluator

    1. 04Mandate checkGate · the evaluatorThe mandate states who may evaluate what; without a mandate the evaluation is REFUSED.
    2. 05Evaluator runExercise · the evaluatorThe run reads the evidence and applies the clause set; the result per clause is recorded.
  4. 04 Over time

    1. 08ExpiryGate · the registry, by validUntilAn expired statement remains listed and is shown as expired; restoration requires a new evaluation.
    2. 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
Process · the conformance pipeline10 operations
InyatheloPhaseUkusebenzaWhoDecision ruleIrekhodi
01AdopterDeclaration (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, nameda first-party declaration, in the sense of ISO/IEC 17050a declaration with the classes claimed
02Nexus recordsClause selection (model). The standard’s machine-readable clauses are selected by the classes claimed.the reference clause toolingevery normative statement is an NS-10 clause; classes select clausesthe clause set for the classes
03AdopterEvidence (record). Evidence is referenced by record identifier and digest; the evidence itself remains with the adopter.the adopterreferenced rather than embedded; missing evidence yields INDETERMINATEevidence references: receipts, digests, record UNIs
04EvaluatorMandate check (gate). The mandate states who may evaluate what; without a mandate the evaluation is REFUSED.the evaluatoran evaluator acts under a recorded mandate and is independent of the subjecta mandate reference
05EvaluatorEvaluator run (exercise). The run reads the evidence and applies the clause set; the result per clause is recorded.the evaluatorthe open test suite, on the referenced evidencethe run with suite version and instant
06Nexus recordsAttestation (record). An attestation names the evaluator, the instant and the evidence it read.the evaluator’s run, recordedPASS, FAIL, INDETERMINATE, NOT_APPLICABLE or REFUSED; certifiesTruth is always falseone attestation per clause, subject and evaluation
07Nexus recordsImplementation conformance statement (record). The public register lists statements as submitted, with their evidence links and expiry dates.the adopter, listed as submittedlisted as submitted by the adopterthe ICS with a UNI and validUntil
08Over timeExpiry (gate). An expired statement remains listed and is shown as expired; restoration requires a new evaluation.the registry, by validUntila statement expires at validUntil; the history is retainedan expired statement, still listed
09AdopterRestoration (step). After expiry the adopter requests a new evaluation; the history is retained.the adopterrestoration requires a new evaluationa new evaluation request
10Over timeAuthority 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 standardcited where it exists; separate from any attestationa 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.

07Ukudibana kweenkqubo

Ukudibana kweenkqubo

4 couplings link this area to other areas and programmes, each with the mechanism of the link.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
08System model

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.

Izilawuli

  • NS-10 Imigaqo-nkqubo namagatya (izibophelelo ezifundeka ngoomatshini: inkcazo, ukubopha, uvavanyo nokunyanzeliswa)
  • NS-11 Ukuqinisekiswa nokubekwa kweliso (ubungqina, iziqinisekiso, uqwalaselo lokuhambelana ngaphandle kokuthemba)
  • NS-1I-UNI nekhathalogu yezinto (igrama v0.2: amacandelo enkalo, ecandelo, ommandla nokusingqongileyo)
  • NRS-C11 Ukuhambelana, ukuqinisekisa nokugcinwa kwemigangatho
  • NRS-S19 System profile: NXS-POR (Public, client and partner delivery)
  • NRS-S3 System profile: NXS-DSS (Decision cases and deliberation)
  • NRS-A9 Iiseti zovavanyo ze-AI kumsebenzi womngcipheko
  • NRS-H112 Hazard family: Governance and institutional failure (NHS-1 soc.governance)
  • NRS-S1 System profile: NXS-CMD (Integrated posture and executive synthesis)

Uqwalaselo

  • 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
09Ikhonsoli

Evidence recorded

Verification console · test suites, conformance statements and attestations as a matrixFrom the registry
Evidence recorded22 standards
  1. Clause sets stated10
  2. Test suites22 in progress
  3. Statements submitted0
  4. Attestations recorded0
  5. Body validators linked3

Conformance statements are listed as submitted.

UmgangathoClauses (NS-10)Test suiteConformance statementsAttestationsBody’s own suite or validator
NS-0 Constitution and principlesstated12 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-1 The UNI and the artefact catalogue…stated10 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-2 Citation and attribution format for…stated5 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-3 Risk record UNIs (grammar, legacy…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-3b Dataset and product metadata profile…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-4 Structure and drafting of Nexus…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-5 Figure, map and visualisation…stated5 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-6 Surface wiring (API header, panel…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-7 Resolver landing pages, page meta…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-8 Zenodo publishing workflow with legal…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-9 Contextual UNIs (deployments,…stated5 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-10 Policies and clauses…stated7 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-11 Verification and monitoring…stated6 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-12 Software, model and AI/ML artefacts…stated4 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-13 Standards development process (open…stated5 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-14 Conformance and crosswalk to…stated5 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-15 System model binding (identity…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-16 UNI application profile (context…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NRS Nexus Risk Standards: the systemic…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
CAP 1.2noneno Nexus clauses yet (proposed under NS-10)plannedin progressnonenone submittednonenone recordedlinkedCAP 1.2 XML Schema
STACnoneno Nexus clauses yet (proposed under NS-10)plannedin progressnonenone submittednonenone recordedlinkedstac-validator
PROV-Ononeno Nexus clauses yet (proposed under NS-10)plannedin progressnonenone submittednonenone recordedlinkedPROV-CONSTRAINTS validators listed in the implementation report
stated: the text of the standard sets out its rulesplanned: in progresslinked: published by the body and run at the sourcenone: nothing recordedA passing test run constitutes implementation evidence.

Process explorer · NXS · Process

Conformance pipeline

10 steps4 stages2 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.

  1. 01 Adopter

    1. 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).
    2. 03EvidenceRecord · the adopterEvidence is referenced by record identifier and digest; the evidence itself remains with the adopter.
    3. 10RestorationStep · the adopterAfter expiry the adopter requests a new evaluation; the history is retained.
  2. 02 Nexus records

    1. 02Clause selectionModel · the reference clause toolingThe standard’s machine-readable clauses are selected by the classes claimed.
    2. 06AttestationRecord · the evaluator’s run, recordedAn attestation names the evaluator, the instant and the evidence it read.
    3. 07Implementation conformance statementRecord · the adopter, listed as submittedThe public register lists statements as submitted, with their evidence links and expiry dates.
  3. 03 Evaluator

    1. 04Mandate checkGate · the evaluatorThe mandate states who may evaluate what; without a mandate the evaluation is REFUSED.
    2. 05Evaluator runExercise · the evaluatorThe run reads the evidence and applies the clause set; the result per clause is recorded.
  4. 04 Over time

    1. 08ExpiryGate · the registry, by validUntilAn expired statement remains listed and is shown as expired; restoration requires a new evaluation.
    2. 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
Process · the conformance pipeline10 operations
InyatheloPhaseUkusebenzaWhoDecision ruleIrekhodi
01AdopterDeclaration (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, nameda first-party declaration, in the sense of ISO/IEC 17050a declaration with the classes claimed
02Nexus recordsClause selection (model). The standard’s machine-readable clauses are selected by the classes claimed.the reference clause toolingevery normative statement is an NS-10 clause; classes select clausesthe clause set for the classes
03AdopterEvidence (record). Evidence is referenced by record identifier and digest; the evidence itself remains with the adopter.the adopterreferenced rather than embedded; missing evidence yields INDETERMINATEevidence references: receipts, digests, record UNIs
04EvaluatorMandate check (gate). The mandate states who may evaluate what; without a mandate the evaluation is REFUSED.the evaluatoran evaluator acts under a recorded mandate and is independent of the subjecta mandate reference
05EvaluatorEvaluator run (exercise). The run reads the evidence and applies the clause set; the result per clause is recorded.the evaluatorthe open test suite, on the referenced evidencethe run with suite version and instant
06Nexus recordsAttestation (record). An attestation names the evaluator, the instant and the evidence it read.the evaluator’s run, recordedPASS, FAIL, INDETERMINATE, NOT_APPLICABLE or REFUSED; certifiesTruth is always falseone attestation per clause, subject and evaluation
07Nexus recordsImplementation conformance statement (record). The public register lists statements as submitted, with their evidence links and expiry dates.the adopter, listed as submittedlisted as submitted by the adopterthe ICS with a UNI and validUntil
08Over timeExpiry (gate). An expired statement remains listed and is shown as expired; restoration requires a new evaluation.the registry, by validUntila statement expires at validUntil; the history is retainedan expired statement, still listed
09AdopterRestoration (step). After expiry the adopter requests a new evaluation; the history is retained.the adopterrestoration requires a new evaluationa new evaluation request
10Over timeAuthority 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 standardcited where it exists; separate from any attestationa 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.

10Imigangatho

Imigangatho esebenzayo

The area profile lists 3 Nexus Standards. Each is a proposed standard under development.

  1. 01

    NS-10 · Policies and clauses (machine-readable obligations: definition, binding, evaluation and enforcement)

    Status: proposed · 7 requirements stated. Read NS-10.

  2. 02

    NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)

    Status: proposed · 6 requirements stated. Read NS-11.

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

11Iqela elisebenzayo

Working group charter

A proposed charter for this area, open to institutions and experts.

Ubungakanani bomsebenzi

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

Deliverables · 3
  1. Conformance class and abstract test suite template
  2. Implementation Conformance Statement schema and register procedure
  3. Reference test harness for browser and continuous-integration use (Apache-2.0)
Liaison targets · 3
  • 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
14Research questions

Open research questions

3 questions identified as priorities for the working group.

  1. How to prevent a self-declaration from being read as third-party assurance when a vendor quotes it out of context.
  2. How to test clauses whose evidence is a human decision or an institutional process rather than a machine-checkable artefact.
  3. How to keep test suites in step with external baselines (for example a new STAC or CAP version) without invalidating earlier declarations.
15Ukulungela

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.

Evidence pathway

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.

Read the evidence pathway

Indlela yokwamkelwa

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

Read the recognition pathway

Indlela yemali

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

Read the capital pathway

Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.

16Audiences

Intended users

The area profile identifies 4 user communities.

  1. implementers and vendors
  2. adopting institutions
  3. auditors and reviewers
  4. developers
17Restricted standards

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.

18Data sources

Data sources

2 data sources named in the area profile, each with provider, licence, update frequency and delivery path.

Data sources

Data sources are listed for reference; live data is displayed once licence review is complete.

Ngoku
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
19Izalathisi

Izalathisi

The area profile names 2 indicators, each with its framework and code.

20Hazards and sectors

Hazards, threats and sectors concerned

Hazards and threats 0

This area draws on the hazards of the areas it is coupled with.

Amacandelo 0

This area serves all sectors through the areas it is coupled with.

21Imithombo

Imithombo

4 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.

  1. peer-reviewedThe economics of compatibility standards: an introduction to recent researchEconomics of Innovation and New Technology · 1990
  2. officialNIST Cybersecurity Framework (CSF) 2.0NIST · 2024
  3. standardSLSA specification v1.1OpenSSF · 2025
  4. standardQA Framework: Specification GuidelinesW3C · 2005
22Research hub

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.

24Kuyo yonke inethiwekhi

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.

Capital, finance and markets

I-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 Alliance
25Amagama aphambili

Amagama aphambili

UNI
Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
kuphakanyisiwe
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.
27Uphando

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

Related standards and frameworks

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.

28Imibuzo

Imibuzo neempendulo.

What is the status of the Conformance programme area?
The area profile is a proposal to the Nexus Standards registry; the area is not yet in the catalogue. Standards are adopted by the Global Standards Council after last call; in each country, adoption is a decision of its National Standards Council (NSC).
How are data sources presented?
Each data source is listed with its provider, licence, update frequency and delivery path, and links to the provider’s own publication.
How can this brief be amended?
Through a public change record under NS-13: a proposed amendment to the area profile or the registry, decided by the editors with written reasons.
IingxeloYiba negalelo

Faka ubungqina obuvela kweli phepha.

I-Reports lupapasho lwekota lweConsortium. Oko ukwaziyo ngalo mxholo kunokuba bubungqina, imeko okanye ulungiso kuhlelo olulandelayo, kubongwe wena kwaye kupapashwe phantsi kwe-CC BY 4.0 apho ingumsebenzi wakho.

Nexus Standards
Imigangatho

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.

Imeko nokusetyenziswa. I-Nexus Standards yimigangatho ecetywayo ephuhliswe ngenkqubo evulekileyo phantsi kwe-NS-13 kwaye ipapashelwe ukusetyenziswa ngokuzithandela; ayisiso isatifikethi, ugunyaziso okanye imvume yolawulo, kwaye ukwamkelwa kuhlala kusisigqibo seBhunga leMigangatho yeHlabathi kwaye, kwilizwe ngalinye, seBhunga lalo leMigangatho leSizwe. I-UNI (Unique Nexus Identifier) ichonga into; ayiyiqinisekisi. Amagama amaqumrhu emigangatho nemigangatho yawo ngawabagcini bawo kwaye asetyenziswa kuphela ukuchonga amaxwebhu; akukho mbhalo womgangatho wangaphandle uphindwe apha. I-Nexus Standards ayidibananga, ayixhaswanga okanye ayiqinisekiswanga nguwuphi na umbutho wemigangatho okhankanywe apha.

Iilayisenisi: CC BY 4.0 yombhalo wemigangatho, iirejista, iischema nedatha; Apache-2.0 yekhowudi yereferensi. Imigangatho yangaphandle icatshulwa ngegama, inombolo nekhonkco phantsi kweelayisenisi zayo. Idatha yamaqela esithathu, iilayibrari neefonti zigcina iilayisenisi zazo: bona iZaziso zamaqela esithathu.