Skip to content
ImigangathoImigangatho yomngcipheko wezemali nezoqoqoshoUkuhambelana
Financial and economic risk

Financial and economic risk: conformance

How an implementer in financial and economic risk demonstrates conformance: a self-assessment against the rules, clauses evaluated from evidence, attestations and a generated report. Each result names its evaluator and the time of evaluation, and each artefact is identified by a UNI (Unique Nexus Identifier).

Imigangatho yomngcipheko wezemali nezoqoqosho
What this area is built from: the Nexus Standards it applies (marked), the open standards it names and the data and feeds it reads, then the areas it couples with.Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-0, NS-3, NS-9, NS-10, NS-11, NS-14.
  • Open standards: Basel Framework; BCBS 239 Principles for effective risk data aggregation and risk reporting; Statistical Data and Metadata eXchange (SDMX); IMF Data Standards Initiatives (SDDS Plus, SDDS, e-GDDS); NGFS climate scenarios; Key Attributes of Effective Resolution Regimes for Financial Institutions.
  • Data and feeds: IMF data services (WEO, IFS, FSI via SDMX); BIS Data Portal (credit, debt service, property prices, banking statistics); World Bank Open Data and World Development Indicators API; OECD Data Explorer (SDMX API).
  • Couples with: Climate; Financial stability and prudential risk; Political and governance; Supply chain and trade risk.
01Isishwankathelo

Summary

  1. 01Self-assessmentagainst the rules
  2. 02Clause setNS-10
  3. 03Evidencereferenced, not embedded
  4. 04AttestationNS-11, named evaluator
  5. 05Reportgenerated from results
Nexus Standards
6
NS-0, NS-3, NS-9
Open standards
6
named, never copied
Data and feeds
4
listed for reference
Couplings
4
with other areas
02Ubungakanani bokugubungela

Standards listed in the hazard and threat families tier

The programme areas of this tier against the standards they list in the registry; the row for this area sets the initial scope of a self-assessment.

Coverage matrix · standards across, programme areas downNexus Standards registry
126 of 231 programme and standard pairs are listed, across 33 programmes and 7 standards. Source: Nexus Standards programme register and standards index.

Coverage matrixA filled cell indicates that the area lists the standard in the registry. Status terms are those of the registry.

03The baseline

Conformance to NS-0

An implementation conforms to NS-0 when it:

  • names the canonical repository and the versions of the standards it applies;
  • does not fork a registry;
  • runs the repository validator, or an equivalent, on the copies of the registries it uses;
  • records its implementation status per standard in registry/consumers.yaml truthfully; and
  • carries the honesty fields (legalState, claimCeiling, status) on every record it publishes.

Conformance to NS-0 is a statement by the implementation, verifiable under NS-11. It is not a certification by the Secretariat or by the Global Standards Council.

04Self-assessment

Initial self-assessment for financial and economic risk

The first rules of each applicable standard. A self-assessment is a statement by the implementer, verifiable under NS-11.

UmthethoRequirementUmgangatho
NS0-P1Open · 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.NS-0
NS0-P2Machine-readable first · Every normative element exists as data (registry, schema, clause) before it exists as prose; prose explains, data governs. A standard with no machine form is not a Nexus Standard.NS-0
NS0-P3Identified · Every artefact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone.NS-0
NS9-R1Each deployment or programme instance shall have one context record; the concept keeps its own UNI; context.ofUni is required and shall resolve.NS-9
NS9-R2Context identifiers shall be allocated by the catalogue for their SCOPE; they shall not be derived from names or typed by hand.NS-9
NS9-R3The 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.NS-9
NS11-R1A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest.NS-11
NS11-R2Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject’s trust boundary.NS-11
NS11-R3Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12).NS-11
05NS-11 · Attestations

Attestations

One attestation is recorded per clause, per subject, per evaluation (AT category, append-only). Results: PASS; FAIL; INDETERMINATE (evidence missing or unresolvable); NOT_APPLICABLE (the subject was outside the clause’s selectors at that instant); REFUSED (the evaluator lacked a mandate or the evidence was not accessible; the refusal is itself recorded). An attestation carries a canonical digest and, optionally, a signature; certifiesTruth is always false. A later attestation supersedes an earlier one for the same clause and subject, and the history is kept.

Crosswalks: an attestation can be exported as a W3C Verifiable Credential under the Verifiable Credentials Data Model 2.0 (subject: the contextual UNI; issuer: the evaluator; evidence: the refs), as an in-toto attestation (for software subjects) or as a PROV-O activity (NS-3b). The Nexus attestation remains the key and the record of truth.

06NS-11 · Monitoring

Ukubeka iliso

Monitoring is continuous evaluation together with observation records. For each bound policy and context, the monitoring service records (a) the latest attestation per clause, (b) coverage (which clauses have no current attestation, and why), (c) drift (a change in a subject’s records that invalidates an attestation) and (d) the availability of evaluators and evidence sources. Monitoring records are observations with record UNIs. Dashboards and panels are projections of them and show the timestamp and the evaluator for every value; no verdict is stored.

07NS-11 · Reporting

Reporting

A conformance report for a context is generated, not written: policy by policy and clause by clause, with attestation UNIs, evidence refs, conformance levels (NS-10 section 3) and the honesty fields. Reports are catalogued artefacts (RP) and may be published (NS-8) only when their legalState allows. A report does not say "certified" or "compliant" except when it quotes an authority decision by reference.

08NS-14 · claims

Display of conformance statements

A context (NS-9) or artefact claims a relation to an external standard only through a clause set (NS-10) that cites that standard and is evaluated (NS-11). The claim is displayed as "implements clauses derived from <standard> (n of m with a current PASS)", with attestation UNIs. It is never displayed as "compliant with" or "certified to" unless a decision of the body entitled to say so is referenced. Where a body operates its own certification, conformance under the Nexus Standards is explicitly not that certification.

09Imibuzo

Imibuzo neempendulo.

How does a conformance report in financial and economic risk relate to the decisions of other bodies?
A conformance report states clause results and their evidence. Where a decision of an authority or another body is relevant, the report cites it by reference.
What happens when evidence is missing?
The attestation is recorded as indeterminate rather than as a pass. Missing evidence, rights state or verification results in a reasoned refusal (NS0-P12).
Imigangatho

Shape the standards for financial and economic risk.

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.

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.