Capital pathway, The Global Risks Alliance (GRA): standards that apply
The 4 standards listed for capital pathway, The Global Risks Alliance (GRA) in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.
- Nexus Standards: NS-9, NS-10, NS-11, NS-14.
- Open standards: IFRS S2 Climate-related Disclosures; Recommendations of the Task Force on Climate-related Financial Disclosures; Recommendations of the Taskforce on Nature-related Financial Disclosures; Principles for effective risk data aggregation and risk reporting (BCBS 239); NGFS climate scenarios for central banks and supervisors; IATI Standard 2.03.
- Data and feeds: World Development Indicators; IMF data services (IFS, FSI, WEO, GFS); NGFS Scenario Explorer; OECD Data Explorer (incl. Creditor Reporting System, insurance and pension statistics).
- Couples with: Finance, insurance and capital markets; the Global Centre for Risk and Innovation (GCRI Canada) evidence pathway; Development finance institutions; Conformance programme.
- Nexus Standards
- 4
- NS-9, NS-10, NS-11
- Open standards
- 6
- named, never copied
- Data and feeds
- 4
- listed for reference
- Couplings
- 4
- with other areas
Contextual UNIs (deployments, instances, programme instances)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000005.
| Rule | Text |
|---|---|
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 is set and the status becomes WITHDRAWN or SUPERSEDED with supersededBy. |
NS9-R5 | Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere. |
Policies and clauses (machine-readable obligations: definition, binding, evaluation and enforcement)
Status proposed · trust, authorisation and assurance; integrated posture and executive synthesis · NXS-STD-ST-000006.
| Rule | Text |
|---|---|
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 is the default for blocking clauses in production contexts. |
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. |
Verification and monitoring (evidence, attestations, zero-trust conformance observation)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000007.
| Rule | Text |
|---|---|
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. |
Conformance and crosswalk to external standards
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000013.
| Rule | Text |
|---|---|
NS14-R1 | The text of an external standard shall not be reproduced; it shall be cited by identifier, clause number and URL. |
NS14-R2 | Relation claims shall come from the register and from clause sets, not from prose. |
NS14-R3 | "Compliant" and "certified" shall appear only as quotations of an authority decision cited by reference. |
NS14-R4 | Marks of standards bodies shall not form part of a Nexus name. |
NS14-R5 | Unverified register entries shall be displayed as unverified. |
Questions and answers.
Are these all the rules for capital pathway, The Global Risks Alliance (GRA)?
What does a rule identifier such as NS1-R5 denote?
Around capital pathway, The Global Risks Alliance (GRA).
Shape the standards for capital pathway, the global risks alliance (gra).
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.
Status and use. The Nexus Standards are proposed standards developed through an open process under NS-13 and published for voluntary use; they do not constitute certification, accreditation or regulatory approval, and adoption remains a decision of the Global Standards Council and, in each country, of its National Standards Council. A UNI (Unique Nexus Identifier) identifies an artefact; it does not certify it. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.
Licences: CC BY 4.0 for standards text, registries, schemas and data; Apache-2.0 for reference code. External standards are cited by name, number and link under their own licences. Third-party data, libraries and fonts keep their own licences: see Third-party notices.
