GRA · AI and Financial Model Risk
Spatial financeWhere capital meets hazard, exposure and transition
Reader questions and safeguards
A model can only be reviewed if its purpose, data, assumptions, limits and monitoring are written down. This checklist sets out the documentation a model owner prepares before independent validation or supervisory review, adapted for machine-learning and generative AI components, without asking for any proprietary code.
The order things happen in.
- 01QuestionNational, regional or institutional priority
- 02EvidenceSTEM foundation of the platform
- 03BuildFoundry
- 04OrganiseNexus ecosystem
- 05TestUniverse (independent site)
- 06ChapishaRipoti
- 07DecideCompetent authorities and institutions, through NXS-RLS (participants, agreements and handoffs)
- 08RenewCorrections and the next annual agenda
Seven questions.
- 01
Madhumuni
What problem does the programme address, and for whom?
- 02
Ushahidi
What hazard, exposure and vulnerability evidence supports it, with what uncertainty?
- 03
Ownership
Who owns the programme and answers for it?
- 04
Utawala
How are decisions taken, recorded and challenged?
- 05
Data
Which data is used, on what terms, and how is it protected?
- 06
Risks
What could go wrong, and how is it managed?
- 07
Ufuatiliaji
How will results be measured and reported?
A model record, field by field.
- Purpose and use: the decision the model informs and who relies on it.
- Data: sources, lineage, representativeness and known biases.
- Method: assumptions and limitations, in plain language.
- Validation: conceptual soundness, outcomes analysis, benchmarking.
- Monitoring: drift indicators and thresholds for review.
- Human oversight: who can override, and how overrides are recorded.
How the process runs.
Process explorer · Process
Reader questions and safeguards: Programme through eight gates
Hatua 11·Hatua 4·Malango 8
Mchakato
Reader questions and safeguards: Programme through eight gates
The Global Risks Forum (GRF) records eight yearly gates, each a programme decision; a gate not passed stops its work, and the competent authority decides outside.
01 Robo ya 1 · Mipango
- 01G0 · Annual programme authorisedGate · The Global Risks ForumGRF authorises the annual mandate. It never sets a national agenda.
- 03Route the candidate mission to standardsStep · Nexus StandardsNexus Standards routes each candidate mission to the standards and profiles that apply.
02 Robo ya 2 · Utayari na ujenzi
- 04G1 · Missions admittedGate · The Global Risks ForumGRF admits missions with reasons recorded. It cannot admit a mission without an accountable owner.
- 05G2 · Data and resources qualifiedGate · The Global Risks ForumReadiness preparation closes when data, people and resources are qualified.
- 06G3 · Build accepted for exerciseGate · The Global Risks ForumGRF records whether the build is accepted for exercise. A gate not passed stops the work it governs.
03 Q3 · Action Week
- 07G4 · Controlled live operation authorisedGate · The Global Risks ForumGRF authorises controlled live operation for Action Week.
- 08G5 · Evidence sealed and stand-down recordedGate · The Global Risks ForumThe evidence is sealed with its provenance and the stand-down is recorded.
04 Robo ya 4 · Utoaji ripoti na upyaishaji
- 02Competent authority decides and actsActor · The competent authorityThe competent authority decides and acts under its own rules. The programme informs it and never decides for it.
- 09Scientific and editorial reviewStep · Reviewers and the publisherQualified, conflict-managed reviewers and the publisher decide what is accepted. Institutions cannot decide a scientific conclusion.
- 10G6 · Publication authorisedGate · The Global Risks ForumGRF authorises publication of results that have passed scientific and editorial review. It cannot publish personal data.
- 11G7 · Renewal reviewedGate · The Global Risks ForumGRF reviews renewal and sets the next cycle’s mandate.
The programme year · The Global Risks Forum · Decision rightsDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation.
Third-party models need the same record.
Vendor catastrophe, credit and market-data models are used across the industry; the user is still responsible for understanding them. Topic depth at third-party models.
Where this page’s references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
Questions and answers.
Is the checklist a standard?
Bring an exposure or capital question to the Alliance.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.