Parcours de reconnaissance, The Global Risks Forum (GRF) : normes applicables
The 5 standards listed for recognition pathway, The Global Risks Forum (GRF) in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.
- Nexus Standards: NS-0, NS-9, NS-10, NS-11, NS-13.
- Normes ouvertes : principes OpenStand (RFC 6852) ; Verifiable Credentials Data Model 2.0 ; W3C Process Document (2025) ; Directives ISO/IEC.
- Données et flux : IATI Datastore ; SDG Global Database.
- Se couple avec : le parcours de données probantes du Global Centre for Risk and Innovation (GCRI Canada) ; l'élaboration de normes ouvertes ; le programme de conformité ; le parcours des chapitres régionaux.
- Nexus Standards
- 5
- NS-0, NS-9, NS-10
- Normes ouvertes
- 4
- nommées, jamais copiées
- Données et flux
- 2
- cité pour référence
- Couplages
- 4
- avec d'autres domaines
Constitution et principes
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000004.
| Règle | Texte |
|---|---|
NS0-P1 | Open · The standards, their registries, schemas, catalogues and reference tools are published in the canonical repository under the licences recorded in LICENSING.md. Participation in development is open to every community and stakeholder under GOVERNANCE.md. No standard depends on a proprietary artefact, product, account or mark to be applied. |
NS0-P2 | Lisible par machine d'abord · Chaque élément normatif existe sous forme de données (registre, schéma, clause) avant d'exister sous forme de prose ; la prose explique, les données régissent. Une norme sans forme lisible par machine n'est pas une Nexus Standard. |
NS0-P3 | Identified · Every artefact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone. |
NS0-P4 | Verified, not asserted · Conformance is a claim with evidence: receipts, digests, signed attestations and observations (NS-11). A claim without evidence is recorded as a claim, never as a fact, and the supported claim level of the implementation bounds every statement it makes. |
NS0-P5 | Zero trust · Authenticated is not authorised; entitled is not authorised; access is denied by default. Every verification, monitoring and enforcement path assumes no implicit trust between systems, tenants, sites or agents, and records who verified what under which mandate. |
NS0-P6 | Real-time · Standards express obligations that can be evaluated continuously against live records (observations, releases, corrections, deployments), and the standards themselves are versioned so that an implementation can state exactly which version it conforms to at any instant. |
NS0-P7 | Provenance everywhere · Every artefact records what it was derived from, who produced it, under which release and policy decision, and what corrected it (NS-3b, PROV-O profile). Corrections supersede; nothing is silently rewritten. |
NS0-P8 | Honnête · Un UNI identifie et résout ; il ne certifie jamais. legalState defaults to review-required. Readiness, approval and production status are never implied by a standard, a status, a page, a score or a badge. |
NS0-P9 | Nexus-aware · Standards address cross-domain interdependence (water, energy, food, health, biodiversity, climate and the sectors they touch) explicitly: an obligation can reference artefacts in another domain, and cascades are first-class. |
NS0-P10 | Names are governed · Codes are never names. Public names follow the marks policy (governance/OPEN_BOUNDARY_IPR_AND_LICENSING.md, section 7). A system or component is shown by its neutral display name and its UNI; the UNI may change with context (NS-9), and no name infringes anyone’s mark. |
NS0-P11 | Community-owned development · Proposals, comments, decisions and versions of every standard are themselves artefacts with UNIs. The development process is specified (NS-13) and open, and authority to adopt is recorded, never assumed. |
NS0-P12 | Fail closed · Missing evidence, a missing legal state, a missing policy decision or unavailable verification results in a refusal with a typed reason, never in a pass. |
UNI contextuels (déploiements, instances, instances de programme)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000005.
| Règle | Texte |
|---|---|
NS9-R1 | Each deployment or programme instance shall have one context record; the concept keeps its own UNI; context.ofUni is required and shall resolve. |
NS9-R2 | Context identifiers shall be allocated by the catalogue for their SCOPE; they shall not be derived from names or typed by hand. |
NS9-R3 | The supported claim level, legal state and conformance evidence of a context are its own; they shall not be inherited from the concept or from another context. |
NS9-R4 | Closing a context shall not delete it: context.validUntil est défini et le statut devient WITHDRAWN or SUPERSEDED avec supersededBy. |
NS9-R5 | Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere. |
Politiques et clauses (obligations lisibles par machine : définition, caractère contraignant, évaluation et application)
Status proposed · trust, authorisation and assurance; integrated posture and executive synthesis · NXS-STD-ST-000006.
| Règle | Texte |
|---|---|
NS10-R1 | Every obligation that an implementation enforces shall be a clause with a UNI; code may implement a rule, but no rule shall be enforced without a clause record that names it. |
NS10-R2 | Subjects shall be contextual UNIs; names, labels or free text shall not bind. |
NS10-R3 | The predicate shall be data in a declared language; evaluators shall record the engine and its version; two conformant evaluators shall reach the same result for the same clause and the same inputs. |
NS10-R4 | External obligations shall be cited, not copied. |
NS10-R5 | Failure effects shall be typed; refuse est la valeur par défaut pour blocking clauses dans des contextes de production. |
NS10-R6 | A clause or policy whose legalState is other than APPROVED may be evaluated, but its results shall be displayed as claims under review. |
NS10-R7 | Policies and clauses shall be append-only artefacts: withdrawal and supersession keep the record. |
Vérification et suivi (preuves, attestations, observation de la conformité en confiance zéro)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000007.
| Règle | Texte |
|---|---|
NS11-R1 | A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest. |
NS11-R2 | Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject’s trust boundary. |
NS11-R3 | Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12). |
NS11-R4 | Attestations shall be append-only and superseded rather than changed; monitoring records shall be observations with record UNIs. |
NS11-R5 | Every displayed conformance value shall carry its evaluation instant and its evaluator; projections shall not store verdicts. |
NS11-R6 | Exports to Verifiable Credentials, in-toto or PROV-O are crosswalks; the Nexus attestation shall remain the record of truth. |
Processus d’élaboration des normes (propositions ouvertes, revue, versionnage, adoption)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000008.
| Règle | Texte |
|---|---|
NS13-R1 | Every change to a standard, registry, clause or policy shall enter through a proposal with a UNI. |
NS13-R2 | Participation shall be open and free of charge; identity shall be recorded (ORCID iD, ROR ID or an agent mandate); decisions shall be reasoned in writing. |
NS13-R3 | Last call shall be announced to every stakeholder group listed on the proposal; objections shall be dispositioned before acceptance. |
NS13-R4 | Editors shall not adopt; authority decisions shall be recorded by reference. |
NS13-R5 | Versions shall be semantic; registries shall be append-only; existing UNIs shall not be invalidated. |
Questions et réponses.
Are these all the rules for recognition pathway, The Global Risks Forum (GRF)?
Que désigne un identifiant de règle tel que NS1-R5 ?
Around recognition pathway, The Global Risks Forum (GRF).
Contribuez à façonner les normes relatives au parcours de reconnaissance, le Global Risks Forum (GRF).
Les gouvernements, les autorités de réglementation, les organismes de normalisation, l'industrie, le monde universitaire et les communautés sont invités à façonner le catalogue avant sa première version officielle, prévue pour 2030 : commenter un projet, proposer une modification, rejoindre un groupe de travail ou accueillir un exercice sur le terrain.
Statut et usage. Les Nexus Standards sont des normes proposées, élaborées selon un processus ouvert sous NS-13 et publiées pour un usage volontaire ; elles ne constituent ni une certification, ni une accréditation, ni une approbation réglementaire, et leur adoption reste une décision du Global Standards Council et, dans chaque pays, de son Conseil national des normes. Un UNI (Unique Nexus Identifier) identifie un artefact ; il ne le certifie pas. Les noms des organismes de normalisation et de leurs normes appartiennent à leurs détenteurs et ne servent qu’à identifier les documents ; aucun texte de norme externe n’est reproduit ici. Nexus Standards n’est ni affilié à, ni approuvé ou certifié par un organisme de normalisation nommé ici.
Licences : CC BY 4.0 pour le texte des normes, les registres, les schémas et les données ; Apache-2.0 pour le code de référence. Les normes externes sont citées par leur nom, leur numéro et un lien, sous leurs propres licences. Les données, bibliothèques et polices de tiers conservent leurs propres licences : voir Mentions relatives aux tiers.