The finance and insurance entry section of the Finance, Insurance and the Economy subsite is written for risk officers, underwriters, supervisors and disclosure preparers: it shows the disclosure crosswalks to ISSB, TCFD and TNFD, the conformance pipeline, the implementation conformance statement register and CAP as a trigger-source example, so risk data and triggers can be traced and verified without any sales claim attached. Every artifact of the area carries a UNI (Unique Nexus Identifier), which identifies and never certifies.
Context entry PROPOSED for the Nexus Standards registry.
Nexus Standards (2026). For finance and insurance: area brief, Finance, Insurance and the Economy (PROPOSED). https://nexustandards.com/finance/for-finance-and-insurance/. Last reviewed 2026-10-17.
Files carry the credits and the licence line; they are generated in your browser and nothing is sent. Downloads need script.
The audiences section of Finance, Insurance and the Economy. Scope as the area context entry states it (PROPOSED).
In scope 5
Out of scope 3
Jurisdictions No jurisdiction note is recorded for this area yet; jurisdiction narrows what applies and never implies that a Nexus profile satisfies a law.
Standards
| Standard | Title | Status | UNI |
|---|---|---|---|
| NS-1 | The UNI and the artifact catalog (grammar v0.2: domain, sector, region and environment segments) | proposed | NXS-STD-ST-000001 |
| NS-9 | Contextual UNIs (deployments, instances, programme instances) | proposed | NXS-STD-ST-000005 |
| NS-10 | Policies and clauses (machine-readable obligations, enforcement in commons and command rooms) | proposed | NXS-STD-ST-000006 |
| NS-11 | Verification and monitoring (evidence, attestations, zero-trust conformance observation) | proposed | NXS-STD-ST-000007 |
| NS-14 | Conformance and crosswalk to external standards | proposed | NXS-STD-ST-000013 |
Areas
NS-0, NS-1, NS-3, NS-3b, NS-9, NS-10, NS-11 · planned
Nexus domainsNS-0, NS-1, NS-3, NS-9, NS-10, NS-11 · planned
Nexus domainsNS-0, NS-1, NS-3, NS-3b, NS-9, NS-10, NS-11 · planned
Nexus domainsNS-0, NS-1, NS-3, NS-3b, NS-5, NS-9, NS-11 · planned
Nexus domainsNS-0, NS-1, NS-3, NS-3b, NS-9, NS-11, NS-14 · planned
Hazard and threat familiesNS-0, NS-3, NS-3b, NS-11 · planned
Hazard and threat familiesNS-0, NS-3, NS-11 · planned
Hazard and threat familiesNS-0, NS-3, NS-11 · planned
Hazard and threat familiesNS-0, NS-3, NS-9, NS-11 · planned
Hazard and threat familiesNS-0, NS-3, NS-9, NS-11 · planned
Hazard and threat familiesNS-0, NS-3, NS-9, NS-11 · planned
Hazard and threat familiesNS-0, NS-3, NS-11 · planned
External standards
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.
8 more in the crosswalk pages of the areas above.
Tools
Implementation status per consumer, not readiness or certification.
| Consumer | Role | This audience's standards |
|---|---|---|
| nexus-foundry | runtime (Foundry server, rooms, passports, GRIx fabric) and catalog for the system, organisation, LEG, GOV and PRG scopes | NS-1 planned (wired on a branch not yet merged, #3043) · NS-9 planned (wired on a branch not yet merged, #3043) · NS-10 planned (wired on a branch not yet merged, #3043) · NS-11 planned (wired on a branch not yet merged, #3043) |
| nexus-foundry-wordpress-plugin | editorial and institutional sites (GCRI Canada, GRF, GRA subsites; therisk.global Nexus Registry) | NS-1 planned (wired on a branch not yet merged, #3043) |
| Record | Title | Status |
|---|---|---|
NXS-STD-ST-000001 | Nexus Standards NS-1 - the UNI and artifact catalog | draft |
NXS-STD-SW-000001 | UNI runtime library (TypeScript, nexus-foundry consumer implementation) | draft |
NXS-STD-SW-000002 | UNI command-line tool (validate, parse, next, mint, catalog, export) - reference implementation | draft |
NXS-STD-SC-000001 | UNI artifact record schema v1 | draft |
NXS-STD-SW-000003 | UNI crosswalk exports (Zenodo, DataCite, Schema.org, CodeMeta, CITATION.cff) - nexus-foundry consumer implementation | draft |
NXS-STD-SW-000004 | Zenodo deposit client (sandbox default, dry-run default, legal gate) - nexus-foundry consumer implementation | draft |
NXS-STD-ST-000002 | Open-standards and open-source stack under the UNI | draft |
NXS-STD-SW-000005 | UNI data profile (STAC, DCAT, PROV-O crosswalks) - standard text here, nexus-foundry consumer implementation | draft |
NXS-STD-ST-000003 | Nexus Standards NS-3 - GRIx record UNIs (grammar, legacy crosswalk, allocation authority) | draft |
NXS-STD-ST-000005 | Nexus Standards NS-9 - contextual UNIs (deployments, instances, programme instances) | draft |
Pathways
Each institution decides under its own rules; no pathway is an approval.
What a project or portfolio must evidence for capital-readiness assessment; never investment advice or endorsement. Open the pathway
The Nexus Standards the area context entry lists. Every one is proposed or specified; none is adopted by an authority.
Status proposed · 5 rules stated. Read NS-9
Status proposed · 7 rules stated. Read NS-10
Status proposed · 6 rules stated. Read NS-11
Status proposed · 5 rules stated. Read NS-14
Test suites, conformance statements and attestations per standard; no attestation is recorded yet, and none would certify.
Today · a draft in your browserMix standards and clauses into a profile draft with citations; YAML or JSON; nothing is submitted.
Today · in your browserPick a sector, hazard family, capability and artifact type; the registry routes the standards and says why.
A console computes from the registry and shows its reasons; it never decides, approves or certifies.
Relations are register entries (NS-14), never conformance or equivalence statements; hover or focus a relation for its meaning. 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.
crosswalk3
Principles for effective risk data aggregation and risk reporting (BCBS 239)Basel Committee on Banking Supervision (BIS)register · bcbs-239IFRS S2 Climate-related DisclosuresInternational Sustainability Standards Board (IFRS Foundation)register · ifrs-s2Recommendations of the Taskforce on Nature-related Financial DisclosuresTNFDregister · tnfd-recommendationscite2
Recommendations of the Task Force on Climate-related Financial DisclosuresFSB Task Force on Climate-related Financial Disclosures (disbanded 2023; monitoring passed to the IFRS Foundation)register · tcfd-recommendationsNGFS climate scenarios for central banks and supervisorsNetwork for Greening the Financial Systemregister · ngfs-climate-scenariosEach coupling names the mechanism that links this area to another; select a card on the canvas to trace it. Mechanisms are stated in the context bank (PROPOSED).
Fig.RUNNING marks the area you are reading; DONE an area in the same subsite, QUEUED an area elsewhere and GATE a subsite reached. Tags give reading order only, never a status. Design, not a record.
Finance readers learn which loss and exposure records GCRI Canada can read as evidence, with admissibility decided by GCRI Canada.
Finance readers see how a programme's disclosure crosswalk and attestations form a trail GRF may consider under its own rules.
Finance readers see what a GRA capital-readiness file must contain and that GRA alone decides readiness; nothing is investment advice or approval.
Each institution decides under its own rules what it reads as evidence; no pathway is an approval, a readiness statement or investment advice.
Sources the area reads or proposes. Delivery follows GRIx first; a source is shown live only after an owner decision admits it for public pages.
No legal register row admits any of these sources for live display on public pages yet, so nothing is read from them here. A register row that exists records the source for the governed GRIx path; admission for public pages is a separate owner decision.
IMF data services (IFS, FSI, WEO, GFS)pending admission
International Monetary Fund · monthly to annual
IMF copyright and usage terms (reuse with attribution; not an open licence)
GRIx governed readregister row exists
NGFS Scenario Explorerpending admission
NGFS with IIASA · per scenario phase
IIASA NGFS Scenario Explorer terms (to be recorded by Legal/IP)
build-time snapshotregister row exists
BIS statistics (banking, credit, debt securities, property prices)pending admission
Bank for International Settlements · quarterly
BIS terms of permitted use of statistics (unrestricted use with the BIS cited as source)
GRIx governed readproposed register row
Indicator names and codes as their stewards publish them; values appear only from a governed GRIx source, never typed into a page.
Curate the finance learning path and keep its crosswalk references aligned with the finance sections.
No working group is chartered yet; a community may charter this one under NS-13 through a docket.
Closed or paywalled standards appear by name and link only; any compatibility profile of one is built on simulated data and kept on protected pages until an institutional arrangement with the issuing body is recorded. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.
The working group may name closed standards later; they would be listed here by name and link only.
Hazards and threats 0
No hazard or threat is listed for this area; it reads the hazards of the areas it couples with.
Sectors 0
No sector is listed for this area; it serves every sector through the areas it couples with.
Peer-reviewed sources and published statistics on the publishers' own domains, as the context entry cites them.
Plain links to the faculty pages of Risk Academy; no course, credential, recognition or endorsement is implied.
Risk Academy disciplines that teach For finance and insurance, with their courses; the GCRI Canada, The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) subsites that carry those disciplines; and the Nexus Foundry systems the standards name. Mappings are proposed for review (Risk Academy standards map, 2026-10-17); a link says a page on the same subject exists, never an endorsement or a conformance statement; framework names in course titles are named and linked, never reproduced.
Propose a change, join the working group or name a source. Area entries are PROPOSED content for the Nexus Standards registry; a UNI identifies and never certifies, and nothing on this site is a certification, an approval or a readiness statement.
Nexus Standards documents CC BY 4.0 · tooling Apache-2.0 · counsel review pending (DEC-2026-10-16-NEXUS-STANDARDS-OPEN-LICENCE). External standards are named and linked under their own licences; a UNI (Unique Nexus Identifier) identifies, it never certifies. · Generated from the Nexus Standards corpus at commit 437ae044c5cb (2026-10-17); proposed and open.