Skip to content
ستانداردNRSNRS-C11
NRS-C11

NRS-C11: Conformance, verification and standards maintenance

Conformance classes CC1 to CC4, test suites, verification bodies, signed attestations in a transparency log, and the maintenance cycle of every Nexus Risk Standard.

NRS-C11 in its series
NRS-C11 among the 16 standards of NRS-C (in accent), the standards it depends on and those that depend on it, and its crosswalks.Source: the risk standards catalogue.
  • NRS-C11 is standard 11 of 16 in NRS-C.
  • NRS-C11 depends on: NRS-C10.
  • Depended on by: NRS-A4, NRS-E3, NRS-E6, NRS-S0.
  • Crosswalks: iso-iec-17029, iso-iec-17065, w3c-verifiable-credentials-2, ietf-scitt, wto-tbt-code-of-good-practice.
01پوختە

پوختە

NRS-C11تۆمارگە
  1. دۆخکراوە
  2. کۆمیتەTC-CORE
  3. شەپۆل1
  4. پشت دەبەستێت بەNRS-C10
  5. بڕگەکان6

Nexus Standards · proposed

شوێن
11 of 16
in NRS-C
پشت دەبەستێت بە
1
NRS-C10
Depended on by
4
risk standards
Crosswalks
5
to external standards
02The standard

NRS-C11: the standard

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

کۆد
NRS-C11
ناونیشان
گونجان، پشتڕاستکردنەوە و چاککردنەوەی ستانداردەکان
وەشان
not yet versioned
دۆخ
کراوە
بەروار
circulated 17 October 2026
Unique Nexus Identifier
allocated when drafting starts (NS1-R2)
زنجیرە
NRS-C Risk core
کۆمیتە
TC-CORE
شەپۆل
1
سەرچاوە
standards/risk/NRS-C11.md at 2cbe0d41b5f8

Preparatory working draft, circulated for review and comment. Not for implementation. Prepared and circulated by Saeed Valadbaygi, Chief Steward, Nexus Standards (saeed@therisk.global), 17 October 2026. Technical review area: TR-05. 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.

زنجیرە
C
ناوکی مەترسی
دۆخ
OPEN (named and specified in the catalogue, not drafted)
Technical committee
TC-CORE (Risk core: vocabulary, methods, data, evidence and conformance)
شەپۆل
1 (Foundations of the risk core)
Catalogue proposal
NXS-STD-PC-000005

Conformance classes CC1 to CC4, test suites, verification bodies, signed attestations in a transparency log, and the maintenance cycle of every Nexus Risk Standard.

CiteNRS-C11, clause 1. NRS-C11. https://nexustandards.com/standards/nrs/nrs-c11/#nx-c-1

1. Scope

  • Domains: SDP Standards development and governance
  • Systems: NXS-NSF (trust, authorisation and assurance)
  • Ecosystem areas governed: the trust and assurance system Validation (continuous verification of AI models, digital twins, smart contracts) (nsf-validation); the trust and assurance system Verification (zero-trust, zero-knowledge, geospatial anchoring) (nsf-verification); the trust and assurance system Monitoring (EO, IoT telemetry, Nexus Observatory Protocol) (nsf-monitoring); the trust and assurance system infrastructure claims: distributed compute, data architecture, plugin ecosystem, simulation interface, identity system, smart contracts, verifiable storage, edge infrastructure, developer tooling, Standards Hub, Sovereign Arbitration Tribunal (nsf-infrastructure)
CiteNRS-C11, clause 2. NRS-C11. https://nexustandards.com/standards/nrs/nrs-c11/#nx-c-2

2. Parts

بەشناونیشان
NRS-C11-1Normative requirements
NRS-C11-2Machine-readable form
NRS-C11-3Conformance tests
NRS-C11-4خشتەی هاوتاکردن
NRS-C11-5Guidance and examples
CiteNRS-C11, clause 3. NRS-C11. https://nexustandards.com/standards/nrs/nrs-c11/#nx-c-3

3. Nexus-native sources

Everything this standard classifies comes from these Nexus authorities; it adds no list of its own.

  • foundry.ufb.bp05-rules Unified Fabric Blueprint 05 rules, evidence and acceptance registers
  • foundry.governance.truth-spine Ecosystem truth spine and promotion ladder
  • foundry.governance.capability-authority Capability authority and supported claim levels
  • foundry.governance.component-registry Component registry maturity ladder
  • universe.claims Universe claim rules
  • universe.state-machines Lifecycle state machines
  • universe.standards Universe standards registry
  • universe.corpus Universe evidence corpus (requirements, acceptance matrix, traceability, schemas, contracts, migrations, policy)
  • gitbook.nexus-osi NXOSI, the Nexus open standards interface (parts 0 to XIV, annexes A to U; conformance levels and evidence quality levels)
  • gitbook.nexus-rail Nexus rail and Nexus-based risk management (NRM conformance CL1 to CL4, modules, NFD, RNFD, UNFSD)
  • gitbook.standardization-root Standardisation section front pages
  • nis-1#GOV NIS-1 Nexus Indicator Standard (20 domains, 451 indicators, 106 composites) (item GOV)
CiteNRS-C11, Crosswalk to external standards. NRS-C11. https://nexustandards.com/standards/nrs/nrs-c11/#nx-c-crosswalk-to-external-standards

بەراوردکاری لەگەڵ ستانداردە دەرەکییەکان

Held at arm's length in the external standards register and mapped element by element (NS-14); never the basis of a Nexus classification and never reproduced.

Foundation: every Nexus Risk Standard applies NS-1 (identifiers), NS-2 (citation), NS-3 and NS-3b (records and metadata), NS-10 (clauses), NS-11 (verification), NS-13 (process) and NS-14 (conformance and crosswalk).

CiteNRS-C11, clause 4. NRS-C11. https://nexustandards.com/standards/nrs/nrs-c11/#nx-c-4

4. Depends on

NRS-C10 کتێبخانەی بەندەکان و کۆنترۆڵەکانی مەترسی

CiteNRS-C11, clause 5. NRS-C11. https://nexustandards.com/standards/nrs/nrs-c11/#nx-c-5

5. Conformance

Conformance levelClauseواتا
CL-BaseNXOSI 8.4.1.1Artefact schemas, receipt formats, and status semantics meet baseline requirements; verification libraries produce consistent results; basic profile import/export works with declared constraints.
CL-OperationalNXOSI 8.4.1.2Runtime enforcement points, docketing, control-plane auditability, and clock enforcement are implemented with defined degraded-mode behaviour and traceable artefacts.
CL-AssuredNXOSI 8.4.1.3Attestation-first requirements for defined classes are implemented; appraisal policies are enforced; status and correction workflows demonstrate reliance stability under change.
CL-SovereignNXOSI 8.4.1.4Sovereign zone enforcement, compute-to-data patterns, offline verification bundles, and controlled disclosure workflows are implemented with audit-ready access logs.
CL-FederatedNXOSI 8.4.1.5Multi-organisation federation is demonstrated: boundary enforcement, cross-org routing constraints, interoperable ontology exchange, and consistent verification across parties.
Evidence quality levelClauseواتا
EQL-1NXOSI 8.4.2.1Evidence is limited to public-safe or informational summaries and receipt-level artefacts suitable for low-stakes reliance.
EQL-2NXOSI 8.4.2.2Checks are reproducible and linked to telemetry; evidence is sufficient for operational remediation and internal assurance.
EQL-3NXOSI 8.4.2.3Evidence packs include sufficient raw artefacts, provenance, and linkage for audit reliance with controlled disclosure.
EQL-4NXOSI 8.4.2.4High-consequence evidence includes measured state binding and replayable verification under declared inputs, enabling strong reliance.
EQL-5NXOSI 8.4.2.5Evidence supports supervisory reliance through controlled disclosure workflows, strict handling, lawful basis matrices, and complete record discipline.

Notation: <NRS id>:<conformance level>/<evidence quality level>, for example NRS-N1:CL-Assured/EQL-4. Source: NXOSI part VIII section 8.4, with the NRM evidence quality scale.

Requirements are published as machine-readable clauses in the NRS-C10 library with identifiers NRS-C11-<part>-R<n>, each with test vectors, so CL-Operational with EQL-2 and above can be checked by machines. A conformance statement names the version, the parts, the level and the evidence quality level, for example NRS-C11:CL-Assured/EQL-3.

CiteNRS-C11, clause 6. NRS-C11. https://nexustandards.com/standards/nrs/nrs-c11/#nx-c-6

6. Drafting

Drafting is the work of TC-CORE. It delivers the normative text of each part, the clauses and test vectors, the crosswalk records, worked examples and the Academy module (programme spine handoff F09). The Global Standards Council adopts; national councils adopt or adapt in one of the six adoption modes; nothing here is a certification or a readiness claim.

Change history

Versions from the catalogue; entries from the changelog that name this document.

No version is recorded in the catalogue for this document yet.

The changelog records no entry that names NRS-C11.

ستاندارد

بەشداری لە ستانداردەکاندا بکە.

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

دۆخ و بەکارهێنان. Nexus Standards ستانداردی پێشنیارکراون کە لە ڕێگەی پرۆسەیەکی کراوەوە لەژێر NS-13 پەرەیان پێدراوە و بۆ بەکارهێنانی خۆبەخشانە بڵاو کراونەتەوە؛ بڕوانامە، متمانەپێدان یان ڕەزامەندیی ڕێکخەر نین، و پەسەندکردن بڕیاری ئەنجومەنی جیهانیی ستانداردەکان و، لە هەر وڵاتێکدا، ئەنجومەنی نیشتمانیی ستانداردەکانی ئەو وڵاتەیە. UNI (Unique Nexus Identifier) بەرهەمێک دەناسێنێت؛ بڕوانامەی پێ نادات. ناوی دەستەکانی ستاندارد و ستانداردەکانیان هی پارێزەرەکانیانن و تەنها بۆ ناساندنی بەڵگەنامەکان بەکاردێن؛ هیچ دەقێکی ستانداردێکی دەرەکی لێرەدا دووبارە نەکراوەتەوە. Nexus Standards پەیوەست نییە بە هیچ دەستەیەکی ستانداردی ناوهێنراو لێرەدا، و لەلایەن هیچیانەوە پشتگیری یان بڕوانامەی پێ نەدراوە.

مۆڵەتەکان: CC BY 4.0 بۆ دەقی ستانداردەکان، تۆمارگەکان، سکێماکان و داتا؛ Apache-2.0 بۆ کۆدی سەرچاوە. ستانداردە دەرەکییەکان بە ناو، ژمارە و بەستەر لە ژێر مۆڵەتەکانی خۆیاندا ئاماژەیان پێدەدرێت. داتا، کتێبخانە و فۆنتەکانی لایەنی سێیەم مۆڵەتەکانی خۆیان دەپارێزن: بڕوانە ئاگادارییەکانی لایەنی سێیەم.