# XV. RISK

## **15.1 Risk Intelligence Competency Doctrine**

### **15.1.1 Risk Intelligence as Competency System.**

15.1.1.1 **SCF shall treat risk intelligence as a competency system, not merely as an analytical function, dashboard output, expert opinion, warning product, or institutional report.** Risk intelligence competence shall mean the ability to identify, classify, interpret, contextualize, communicate, review, correct, and safely use risk-related information across Nexus Academy, Risk Academy, Nexus Foundry, Nexus Labs, Nexus Campaigns, Nexus Reports, Nexus Marketplace, Nexus Registry, Nexus Studio, Nexus Grid, Nexus Universe, Nexus Observatory, Nexus Rails, Nexus Network, National Portfolios, National Working Groups, Nexus Competence Cells, public authority learning rooms, readiness rooms, and lawful handoff contexts.

15.1.1.2 Risk intelligence competence shall include the ability to work with risk categories, controlled vocabulary, hazard signals, exposure context, vulnerability context, resilience capacity, uncertainty, confidence, data quality, indicator limitations, scenario assumptions, model limitations, public-safe language, safeguard conditions, protected knowledge controls, public authority boundaries, finance-readiness boundaries, insurance-readiness boundaries, procurement neutrality, and correction pathways.

15.1.1.3 SCF shall ensure that risk intelligence is learned as an applied capability across technical, institutional, public-good, workforce, community, policy-learning, and handoff contexts. A participant shall not be treated as risk-intelligence competent merely because they can read a dashboard, produce a map, run a model, generate a chart, summarize a report, or use a risk label. Competence shall require judgment about provenance, scope, uncertainty, sensitivity, authority boundaries, public-safe communication, and downstream consequences.

15.1.1.4 Risk intelligence competence shall support public-good capability formation, whole-of-society learning, disaster-risk reduction, disaster-risk finance literacy, disaster-risk intelligence literacy, WFEH-B systems understanding, public authority learning, national capability formation, resilience planning support, safe technology interpretation, and lawful handoff context.

15.1.1.5 Risk intelligence competence shall not create public warning authority, emergency command authority, public authority decision status, regulatory approval, official risk rating, insurance score, investment signal, country ranking, procurement preference, certification, consent, deployment authorization, or execution authority by implication.

### **15.1.2 GRIx as Controlled Vocabulary Competence.**

15.1.2.1 **SCF shall treat GRIx competence as the ability to understand, apply, maintain, and correct a controlled vocabulary for risk meaning across Nexus.** GRIx competence shall enable participants to classify and communicate risk concepts consistently across reports, dashboards, data objects, learning objects, public-safe summaries, Observatory outputs, DRI indicators, Studio scenarios, Grid inputs, TRL notes, Registry records, Marketplace listings, National Portfolios, Nexus Universe outputs, and handoff packages.

15.1.2.2 GRIx competence shall include:\
(a) risk category literacy;\
(b) controlled vocabulary use;\
(c) taxonomy interpretation;\
(d) ontology awareness;\
(e) cross-domain mapping;\
(f) WFEH-B category mapping;\
(g) DRR, DRF, and DRI category mapping;\
(h) frontier technology risk classification;\
(i) public authority boundary category recognition;\
(j) finance and insurance boundary category recognition;\
(k) safeguard category recognition;\
(l) handoff dependency category recognition;\
(m) correction of misclassification.

15.1.2.3 GRIx competence shall help prevent semantic drift, inconsistent claims, misleading translations, false equivalence, overbroad category use, informal rankings, and unreviewed public authority or finance implications.

15.1.2.4 GRIx terms shall be treated as Nexus-controlled meaning records, not as legal determinations, regulatory classifications, insurance ratings, investment classifications, procurement qualifications, country rankings, or standards certifications unless separately and lawfully adopted by competent authorities.

### **15.1.3 DRI as Indicator and Public-Safe Intelligence Competence.**

15.1.3.1 **SCF shall treat DRI competence as the ability to understand, interpret, review, communicate, and correct disaster-risk intelligence indicators and related public-safe intelligence outputs.** DRI competence shall apply to hazard, exposure, vulnerability, resilience, protection-gap, readiness, cascade, hotspot, multi-hazard, systems-risk, climate-risk, infrastructure-risk, community-risk, and WFEH-B intelligence contexts.

15.1.3.2 DRI competence shall include:\
(a) indicator literacy;\
(b) signal interpretation;\
(c) source review;\
(d) confidence labeling;\
(e) uncertainty labeling;\
(f) dashboard interpretation;\
(g) hotspot and cascade literacy;\
(h) public-safe intelligence writing;\
(i) no-warning communication;\
(j) no-rating communication;\
(k) correction and archive.

15.1.3.3 DRI competence shall train participants to distinguish between indicators, signals, evidence, scenarios, forecasts, warnings, ratings, decisions, and official actions. DRI outputs may support learning, preparedness literacy, public-safe reporting, National Portfolio formation, public authority learning, finance-readiness questions, insurance-readiness questions, and lawful handoff context, but shall not themselves become official warning products, emergency commands, public authority decisions, insurance scores, investment signals, or procurement triggers.

15.1.3.4 DRI competence shall remain bounded by recorded method, source, data quality, temporal scope, spatial scope, confidence, uncertainty, sensitivity, public-safe status, and correction pathway.

### **15.1.4 Observatory as Signal and Observability Competence.**

15.1.4.1 **SCF shall treat Nexus Observatory competence as the ability to understand observability, signals, indicators, sensor contexts, geospatial context, Earth observation context, digital twin needs, degraded-mode awareness, public-safe observability outputs, and correction pathways.**

15.1.4.2 Observatory competence shall include:\
(a) signal source literacy;\
(b) observability method awareness;\
(c) sensor and edge signal literacy;\
(d) geospatial literacy;\
(e) Earth observation literacy;\
(f) digital twin input literacy;\
(g) dashboard signal review;\
(h) sensitive location controls;\
(i) public-safe Observatory output skills;\
(j) degraded-mode awareness;\
(k) correction and archive.

15.1.4.3 Observatory competence shall train participants to distinguish observability from surveillance, signal from warning, indicator from rating, dashboard from decision, map from official public authority record, and public-safe summary from unrestricted disclosure.

15.1.4.4 Observatory competence shall not create surveillance authority, monitoring authority, emergency command authority, public warning authority, public authority approval, geospatial disclosure permission, protected knowledge permission, or deployment authorization by implication.

### **15.1.5 Studio as Scenario Learning Competence.**

15.1.5.1 **SCF shall treat Studio competence as the ability to use Nexus Studio environments for controlled scenario learning, simulation interpretation, dashboard exploration, digital twin review, public authority learning, readiness-room discussion, capital-reader literacy, insurance-reader literacy, and handoff-context demonstration without converting such activity into decisions, approvals, certifications, forecasts, warnings, or execution.**

15.1.5.2 Studio competence shall include:\
(a) scenario design;\
(b) scenario interpretation;\
(c) simulation literacy;\
(d) dashboard interpretation;\
(e) assumption register use;\
(f) dependency register use;\
(g) model limitation awareness;\
(h) controlled demonstration skills;\
(i) no-decision runtime controls;\
(j) output review;\
(k) correction and archive.

15.1.5.3 Studio competence shall require awareness of access control, role-based permissions, no-write-back rules, no-command rules, no-download rules where applicable, AI-use restrictions, data export restrictions, public-safe restrictions, logging, shutdown triggers, correction triggers, and archive rules.

15.1.5.4 Studio participation shall not create deployment approval, public authority decision, public warning, emergency command, finance approval, insurance approval, donor commitment, procurement status, certification, community consent, Indigenous consent, or execution authority.

### **15.1.6 Simulation as Bounded Evidence Competence.**

15.1.6.1 **SCF shall treat simulation competence as the ability to understand simulations as bounded evidence objects whose meaning depends on data basis, model basis, assumptions, parameters, uncertainty, sensitivity, limitations, scenario scope, review status, and public-safe interpretation.**

15.1.6.2 Simulation competence shall include:\
(a) model basis review;\
(b) data basis review;\
(c) assumption review;\
(d) uncertainty interpretation;\
(e) confidence interpretation;\
(f) sensitivity awareness;\
(g) limitation statements;\
(h) scenario scope control;\
(i) public-safe communication;\
(j) correction and archive.

15.1.6.3 Simulation competence shall train participants to distinguish simulation from forecast certainty, model output from determination, scenario from prediction, digital twin view from operational command, and demonstration from deployment.

15.1.6.4 Simulation outputs shall not create certification, public authority approval, emergency warning, operational command, financeability, insurability, procurement readiness, deployment authorization, or execution authority by implication.

### **15.1.7 Risk Intelligence Without Warning Authority.**

15.1.7.1 **SCF shall maintain the rule that risk intelligence competence does not create warning authority.** Participants may learn to interpret hazards, vulnerabilities, exposures, indicators, dashboards, scenarios, maps, simulations, DRI outputs, Observatory signals, and public-safe reports without being authorized to issue public warnings, emergency alerts, evacuation notices, health warnings, infrastructure warnings, financial warnings, insurance warnings, or official public authority communications.

15.1.7.2 Risk intelligence learning shall include no-warning language, escalation literacy, competent authority routing, public-safe reporting discipline, and correction pathways.

15.1.7.3 Where risk intelligence suggests that public authority action, emergency communication, public warning, operational response, public health action, infrastructure action, or legal escalation may be required, SCF shall require routing to competent actors through recorded escalation channels rather than informal publication or participant action.

### **15.1.8 Scenario Literacy Without Forecast Certainty.**

15.1.8.1 **SCF shall maintain the rule that scenario literacy does not create forecast certainty.** Participants shall understand that scenarios are structured learning tools used to explore possible conditions, dependencies, vulnerabilities, options, stressors, and consequences; they are not predictions, guarantees, official forecasts, ratings, decisions, or determinations.

15.1.8.2 Scenario literacy shall include awareness of:\
(a) scenario purpose;\
(b) scenario scope;\
(c) assumptions;\
(d) model limitations;\
(e) data limitations;\
(f) uncertainty;\
(g) sensitivity;\
(h) alternative pathways;\
(i) public-safe interpretation;\
(j) correction.

15.1.8.3 SCF shall require scenario outputs to avoid false precision, inevitability language, public authority overclaim, financeability overclaim, insurance overclaim, procurement overclaim, community consent overclaim, and execution overclaim.

***

## **15.2 GRIx Competencies**

### **15.2.1 Risk Taxonomy Literacy.**

15.2.1.1 **Risk Taxonomy Literacy** shall mean the ability to understand, apply, and interpret structured categories of risk used within Nexus, including hazards, exposures, vulnerabilities, resilience capacities, safeguards, dependencies, uncertainties, systems risks, frontier technology risks, public authority boundary risks, finance and insurance boundary risks, and handoff dependency risks.

15.2.1.2 Risk taxonomy literacy shall include:\
(a) category purpose;\
(b) category scope;\
(c) category hierarchy;\
(d) cross-domain relationships;\
(e) classification limits;\
(f) source and evidence requirements;\
(g) localization and translation limits;\
(h) public-safe communication;\
(i) correction of category misuse;\
(j) archive of superseded categories.

15.2.1.3 Risk taxonomy literacy shall support consistent learning, DRI interpretation, Observatory outputs, Reports drafting, Registry records, Marketplace metadata, Studio scenarios, Grid inputs, TRL evidence notes, National Portfolio records, and lawful handoff packages.

15.2.1.4 Risk taxonomy literacy shall not create legal classification, regulatory status, official public authority category, insurance rating, investment classification, procurement category, or certification by implication.

### **15.2.2 Controlled Vocabulary Skills.**

15.2.2.1 **Controlled Vocabulary Skills** shall mean the ability to use approved Nexus terms consistently, avoid uncontrolled synonyms where they create ambiguity, distinguish defined terms from informal language, apply public-safe wording, and escalate term conflicts for review.

15.2.2.2 Controlled vocabulary skills shall include:\
(a) term lookup;\
(b) definition interpretation;\
(c) term scope;\
(d) term source;\
(e) term version;\
(f) multilingual and localization awareness;\
(g) synonym control;\
(h) ambiguity identification;\
(i) term correction;\
(j) deprecated term avoidance.

15.2.2.3 Controlled vocabulary skills shall be required for contributors preparing learning objects, reports, dashboards, risk intelligence summaries, public-safe communications, Registry records, Marketplace listings, Studio scenarios, Grid inputs, TRL notes, and handoff-context materials.

15.2.2.4 Controlled vocabulary use shall not imply standards authority, legal equivalence, regulatory adoption, public authority approval, or certification.

### **15.2.3 WFEH-B Category Mapping.**

15.2.3.1 **WFEH-B Category Mapping** shall mean competence in mapping risk, resilience, data, learning, portfolio, and handoff objects across water, food, energy, health, biodiversity, nature, and related cross-system dependencies.

15.2.3.2 WFEH-B mapping competence shall include:\
(a) water-system risk categories;\
(b) food-system risk categories;\
(c) energy-system risk categories;\
(d) health-system risk categories;\
(e) biodiversity and nature-system categories;\
(f) cross-system cascade categories;\
(g) corridor and cluster dependencies;\
(h) national systems-risk context;\
(i) public-safe WFEH-B communication;\
(j) handoff dependency notes.

15.2.3.3 WFEH-B category mapping shall support whole-of-society capability formation and National Portfolio development, but shall not create environmental certification, public health decision, infrastructure approval, public warning, procurement preference, financeability, or implementation authority.

### **15.2.4 DRR / DRF / DRI Mapping.**

15.2.4.1 **DRR / DRF / DRI Mapping** shall mean competence in distinguishing and connecting Disaster Risk Reduction, Disaster Risk Finance, and Disaster Risk Intelligence concepts within Nexus learning, risk intelligence, public-safe reporting, National Portfolios, and handoff context.

15.2.4.2 DRR / DRF / DRI mapping competence shall include:\
(a) risk reduction categories;\
(b) prevention and preparedness categories;\
(c) protection-gap concepts;\
(d) risk-layering concepts;\
(e) insurance-readiness questions;\
(f) donor-readiness questions;\
(g) public finance relevance questions;\
(h) indicator and signal categories;\
(i) public-safe disaster-risk communication;\
(j) correction of finance or warning overclaim.

15.2.4.3 DRR / DRF / DRI mapping shall not create finance, insurance, donor commitment, public finance allocation, investment advice, underwriting, official warning, public authority approval, or emergency command.

### **15.2.5 Systems-Risk Classification.**

15.2.5.1 **Systems-Risk Classification** shall mean competence in identifying risks that arise from interdependencies, feedback loops, cascading failures, threshold effects, infrastructure dependencies, social vulnerability, supply-chain fragility, cyber-physical coupling, climate stressors, ecological degradation, institutional weakness, and technology interactions.

15.2.5.2 Systems-risk classification shall include:\
(a) system boundary identification;\
(b) dependency mapping;\
(c) cascade mapping;\
(d) feedback-loop awareness;\
(e) fragility and resilience factors;\
(f) cross-sector implications;\
(g) time horizon;\
(h) uncertainty;\
(i) public-safe summary;\
(j) correction.

15.2.5.3 Systems-risk classification shall support learning and portfolio formation, but shall not constitute official systemic-risk designation, regulatory classification, investment warning, insurance rating, country ranking, public warning, or public authority decision.

### **15.2.6 Frontier Technology Risk Classification.**

15.2.6.1 **Frontier Technology Risk Classification** shall mean competence in identifying and classifying risks associated with AI, agentic systems, AI-RAN, O-RAN, telecom, private wireless, edge computing, HPC, sovereign compute, cloud, cybersecurity, geospatial systems, Earth observation, digital twins, drones, robotics, sensors, IoT, OT, IIoT, DLT, DePIN, Web3, quantum-relevant security, semiconductors, advanced manufacturing, biosecurity-sensitive systems, and frontier science infrastructure.

15.2.6.2 Frontier technology risk classification shall include:\
(a) technical capability context;\
(b) deployment context;\
(c) data context;\
(d) AI-use context;\
(e) cyber and privacy context;\
(f) dual-use sensitivity;\
(g) public authority dependency;\
(h) provider-neutrality considerations;\
(i) safeguard considerations;\
(j) handoff dependency notes.

15.2.6.3 Frontier technology risk classification shall not constitute technology approval, safety certification, security certification, public authority approval, procurement readiness, financeability, insurability, export-control determination, medical or public health decision, or deployment authorization.

### **15.2.7 Safeguard Category Literacy.**

15.2.7.1 **Safeguard Category Literacy** shall mean competence in identifying and applying categories related to community safeguards, Indigenous protocols where applicable, protected knowledge, youth safeguards, disability inclusion, accessibility, humanitarian sensitivity, non-extractive engagement, public-interest participation, and community-facing correction.

15.2.7.2 Safeguard category literacy shall include:\
(a) safeguard trigger recognition;\
(b) affected stakeholder awareness;\
(c) protected knowledge awareness;\
(d) consent boundary literacy;\
(e) cultural and community context;\
(f) accessibility and inclusion review;\
(g) public-safe communication;\
(h) escalation pathways;\
(i) correction and public repair;\
(j) archive.

15.2.7.3 Safeguard category literacy shall not create consent, replace community governance, replace Indigenous protocols, authorize protected knowledge use, certify ethical compliance, or authorize deployment.

### **15.2.8 Handoff Dependency Category Literacy.**

15.2.8.1 **Handoff Dependency Category Literacy** shall mean competence in identifying dependencies that must be carried into lawful handoff context, including evidence dependencies, data dependencies, method dependencies, public authority dependencies, legal dependencies, safeguard dependencies, finance-readiness questions, insurance-readiness questions, procurement boundaries, provider-neutrality notes, sponsor-boundary notes, support status, correction pathways, and recipient responsibilities.

15.2.8.2 Handoff dependency literacy shall include:\
(a) dependency identification;\
(b) dependency classification;\
(c) recipient responsibility awareness;\
(d) unresolved issue marking;\
(e) no-authority-transfer language;\
(f) public authority boundary notes;\
(g) finance and insurance boundary notes;\
(h) procurement neutrality notes;\
(i) correction and recall pathways;\
(j) archive.

15.2.8.3 Handoff dependency literacy shall not create project authorization, contract award, procurement eligibility, financeability, insurance approval, public authority approval, provider validation, sponsor control, or execution authority.

***

## **15.3 DRI Competencies**

### **15.3.1 Indicator Literacy.**

15.3.1.1 **Indicator Literacy** shall mean competence in understanding what an indicator measures, what it does not measure, how it is constructed, what source data supports it, what assumptions it carries, what uncertainty attaches to it, how frequently it is updated, and how it may be corrected.

15.3.1.2 Indicator literacy shall include:\
(a) indicator definition;\
(b) source data;\
(c) calculation method;\
(d) temporal scope;\
(e) spatial scope;\
(f) sensitivity;\
(g) uncertainty;\
(h) confidence;\
(i) limitation statement;\
(j) correction pathway.

15.3.1.3 Indicator literacy shall train participants to avoid treating indicators as ratings, rankings, warnings, public authority decisions, insurance scores, investment signals, or procurement signals.

### **15.3.2 Signal Interpretation.**

15.3.2.1 **Signal Interpretation** shall mean competence in reading risk-related signals from data, reports, observations, sensors, geospatial layers, dashboards, field records, community inputs, public authority learning records, climate information, infrastructure information, and technology records.

15.3.2.2 Signal interpretation shall include:\
(a) source review;\
(b) signal strength;\
(c) noise and uncertainty;\
(d) trend awareness;\
(e) anomaly awareness;\
(f) confidence labels;\
(g) corroboration needs;\
(h) sensitivity review;\
(i) public-safe summary;\
(j) escalation and correction.

15.3.2.3 Signal interpretation shall not create warning authority, forecast certainty, operational command, public authority action, insurance scoring, investment signaling, or deployment authorization.

### **15.3.3 Uncertainty Labels.**

15.3.3.1 **Uncertainty Label Competence** shall mean the ability to identify, apply, interpret, and communicate uncertainty associated with indicators, models, dashboards, scenarios, forecasts, simulations, Observatory signals, DRI outputs, and public-safe intelligence summaries.

15.3.3.2 Uncertainty label competence shall include:\
(a) data uncertainty;\
(b) model uncertainty;\
(c) measurement uncertainty;\
(d) temporal uncertainty;\
(e) spatial uncertainty;\
(f) scenario uncertainty;\
(g) incomplete source awareness;\
(h) conflicting evidence awareness;\
(i) public-safe language;\
(j) correction when uncertainty changes.

15.3.3.3 Uncertainty labels shall prevent false precision, overclaim, inappropriate comparison, public warning overreach, finance overclaim, insurance overclaim, procurement overclaim, and public authority overclaim.

### **15.3.4 Confidence Labels.**

15.3.4.1 **Confidence Label Competence** shall mean the ability to apply and interpret confidence descriptions for risk intelligence outputs based on source quality, method quality, corroboration, evidence sufficiency, recency, consistency, review status, and known limitations.

15.3.4.2 Confidence label competence shall include:\
(a) confidence basis;\
(b) confidence level;\
(c) source strength;\
(d) method strength;\
(e) corroboration level;\
(f) review level;\
(g) limitation notes;\
(h) update cadence;\
(i) public-safe phrasing;\
(j) correction and downgrade.

15.3.4.3 Confidence labels shall not convert intelligence into certainty, rating, certification, warning, public authority decision, financeability, insurability, or procurement status.

### **15.3.5 Dashboard Interpretation.**

15.3.5.1 **Dashboard Interpretation** shall mean competence in reading dashboards as bounded, source-dependent, method-dependent, update-dependent, and public-safe visual interfaces rather than as decisions, ratings, warnings, or commands.

15.3.5.2 Dashboard interpretation shall include:\
(a) source identification;\
(b) update cadence;\
(c) metric definition;\
(d) visual scale interpretation;\
(e) uncertainty display;\
(f) confidence display;\
(g) sensitive data masking;\
(h) public-safe wording;\
(i) drill-down limits;\
(j) correction notices.

15.3.5.3 Dashboard interpretation competence shall not authorize operational decisions, emergency action, public warning, public authority decision, investment decision, insurance decision, procurement decision, community consent claim, or deployment.

### **15.3.6 Public-Safe Intelligence Writing.**

15.3.6.1 **Public-Safe Intelligence Writing** shall mean competence in writing risk intelligence summaries that are useful, accurate within scope, non-alarmist, non-misleading, non-authority-claiming, rights-aware, safeguard-aware, and correctionable.

15.3.6.2 Public-safe intelligence writing shall include:\
(a) plain-language clarity;\
(b) source limits;\
(c) uncertainty statement;\
(d) confidence statement;\
(e) no-warning language where applicable;\
(f) no-rating language where applicable;\
(g) no-finance language where applicable;\
(h) no-procurement language where applicable;\
(i) protected knowledge controls;\
(j) correction notice.

15.3.6.3 Public-safe intelligence writing shall not replace official warnings, public authority communications, regulated disclosures, professional advice, insurance analysis, investment advice, or operational instructions.

### **15.3.7 Hotspot and Cascade Literacy.**

15.3.7.1 **Hotspot and Cascade Literacy** shall mean competence in understanding areas, systems, communities, infrastructures, sectors, supply chains, or portfolios where multiple risks may concentrate or propagate through interdependent systems.

15.3.7.2 Hotspot and cascade literacy shall include:\
(a) hotspot definition;\
(b) cascade pathway identification;\
(c) exposure context;\
(d) vulnerability context;\
(e) resilience capacity context;\
(f) cross-system dependencies;\
(g) sensitivity and public-safe mapping;\
(h) community safeguard implications;\
(i) public authority escalation boundaries;\
(j) correction and archive.

15.3.7.3 Hotspot and cascade literacy shall not create official hazard designation, emergency warning, public authority decision, country ranking, insurance score, investment signal, or deployment priority.

### **15.3.8 DRI Correction Skills.**

15.3.8.1 **DRI Correction Skills** shall mean competence in identifying, reporting, reviewing, correcting, superseding, withdrawing, downgrading, updating, and archiving DRI indicators, signals, dashboards, summaries, hotspot records, cascade records, confidence labels, uncertainty labels, and public-safe intelligence outputs.

15.3.8.2 DRI correction skills shall include:\
(a) error identification;\
(b) outdated-source identification;\
(c) method change recognition;\
(d) indicator recalculation awareness;\
(e) confidence downgrade;\
(f) uncertainty update;\
(g) public-safe correction notice;\
(h) downstream correction propagation;\
(i) Registry status update;\
(j) archive.

15.3.8.3 DRI correction shall preserve trust by making risk intelligence amendable, traceable, and non-final where evidence changes.

### **15.3.9 No-Warning Communication.**

15.3.9.1 **No-Warning Communication** shall mean competence in communicating risk intelligence without implying official warning authority, emergency alert status, evacuation instruction, public health instruction, infrastructure warning, security alert, market warning, insurance warning, or public authority directive.

15.3.9.2 No-warning communication shall include:\
(a) learning-purpose language;\
(b) public-safe framing;\
(c) competent authority routing;\
(d) escalation language where required;\
(e) no-command wording;\
(f) no-alert wording;\
(g) no-certainty wording;\
(h) no-official-action wording;\
(i) correction pathway;\
(j) archive.

15.3.9.3 No-warning communication shall not prevent responsible escalation to competent authorities where risk intelligence indicates possible need for official action.

### **15.3.10 No-Rating Communication.**

15.3.10.1 **No-Rating Communication** shall mean competence in communicating indicators, comparisons, maps, dashboards, readiness notes, and DRI summaries without implying official ratings, rankings, scores, grades, insurance classifications, investment rankings, procurement qualifications, country rankings, provider rankings, or maturity certifications.

15.3.10.2 No-rating communication shall include:\
(a) descriptive language;\
(b) context statements;\
(c) scope limits;\
(d) non-comparability warnings where needed;\
(e) uncertainty labels;\
(f) confidence labels;\
(g) no-finance wording;\
(h) no-procurement wording;\
(i) no-certification wording;\
(j) correction notices.

15.3.10.3 No-rating communication shall preserve the distinction between learning metrics, public-good indicators, and official rating or certification systems.

***

## **15.4 Observatory Competencies**

### **15.4.1 Observability Literacy.**

15.4.1.1 **Observability Literacy** shall mean competence in understanding how signals, indicators, data streams, field observations, sensors, dashboards, geospatial layers, Earth observation, digital twins, and public-safe outputs contribute to situational learning and systems understanding.

15.4.1.2 Observability literacy shall include:\
(a) signal source awareness;\
(b) data provenance;\
(c) indicator construction;\
(d) update cadence;\
(e) sensor limitations;\
(f) coverage gaps;\
(g) uncertainty;\
(h) confidence;\
(i) sensitivity;\
(j) correction.

15.4.1.3 Observability literacy shall not create surveillance authority, public warning authority, operational command, public authority decision, or unrestricted data access.

### **15.4.2 Sensor and Edge Signal Literacy.**

15.4.2.1 **Sensor and Edge Signal Literacy** shall mean competence in understanding signals produced by sensors, IoT devices, edge nodes, field instruments, mobile devices, drones, robotics, telecom infrastructure, private wireless systems, and other distributed technical systems.

15.4.2.2 Sensor and edge signal literacy shall include:\
(a) sensor purpose;\
(b) measurement limits;\
(c) calibration awareness;\
(d) latency;\
(e) data loss;\
(f) spoofing or manipulation risk;\
(g) cyber sensitivity;\
(h) geospatial sensitivity;\
(i) degraded-mode awareness;\
(j) public-safe output control.

15.4.2.3 Sensor and edge signal literacy shall not authorize device control, network control, surveillance, operational response, emergency command, or deployment.

### **15.4.3 Geospatial Literacy.**

15.4.3.1 **Geospatial Literacy** shall mean competence in reading, interpreting, classifying, and safely communicating spatial data, maps, layers, coordinates, boundaries, buffers, exposure zones, hazard zones, infrastructure layers, community layers, ecological layers, and sensitive location information.

15.4.3.2 Geospatial literacy shall include:\
(a) scale;\
(b) resolution;\
(c) projection awareness;\
(d) spatial uncertainty;\
(e) sensitive location masking;\
(f) aggregation;\
(g) delay rules where applicable;\
(h) protected knowledge awareness;\
(i) public-safe map language;\
(j) correction and archive.

15.4.3.3 Geospatial literacy shall not create official map status, land-use decision authority, public warning authority, surveillance authority, protected location disclosure permission, or public authority approval.

### **15.4.4 Earth Observation Literacy.**

15.4.4.1 **Earth Observation Literacy** shall mean competence in understanding satellite, aerial, remote sensing, climate, hydrological, land, water, vegetation, built environment, and other Earth observation data within recorded scope and limitations.

15.4.4.2 Earth observation literacy shall include:\
(a) source platform awareness;\
(b) spatial resolution;\
(c) temporal resolution;\
(d) spectral limitations;\
(e) cloud cover and data gaps;\
(f) ground-truthing needs;\
(g) uncertainty;\
(h) public-safe interpretation;\
(i) sensitive location controls;\
(j) correction and archive.

15.4.4.3 Earth observation literacy shall not create official monitoring authority, public authority record status, public warning authority, enforcement authority, land-use approval, or operational command.

### **15.4.5 Digital Twin Literacy.**

15.4.5.1 **Digital Twin Literacy** shall mean competence in understanding digital twins as bounded representations of systems, assets, environments, processes, or scenarios, based on selected data, assumptions, models, update cadences, and intended uses.

15.4.5.2 Digital twin literacy shall include:\
(a) twin purpose;\
(b) system boundary;\
(c) data basis;\
(d) model basis;\
(e) assumptions;\
(f) update cadence;\
(g) uncertainty;\
(h) limitations;\
(i) scenario interpretation;\
(j) public-safe output controls.

15.4.5.3 Digital twin literacy shall not create operational command, forecast certainty, deployment approval, public authority decision, infrastructure control, or emergency authority.

### **15.4.6 Degraded-Mode Awareness.**

15.4.6.1 **Degraded-Mode Awareness** shall mean competence in recognizing when systems, data streams, sensors, communications, networks, dashboards, models, field reporting, public authority channels, or infrastructure conditions are operating under impaired, partial, delayed, uncertain, low-bandwidth, offline, disrupted, or failure-prone conditions.

15.4.6.2 Degraded-mode awareness shall include:\
(a) missing data recognition;\
(b) delayed data recognition;\
(c) partial coverage recognition;\
(d) unreliable signal recognition;\
(e) fallback process awareness;\
(f) low-bandwidth operation awareness;\
(g) manual review needs;\
(h) public-safe communication;\
(i) escalation pathways;\
(j) correction after restoration.

15.4.6.3 Degraded-mode awareness shall not authorize emergency command, operational workaround, public warning, cyber intervention, infrastructure intervention, or deployment action.

### **15.4.7 Dashboard Signal Review.**

15.4.7.1 **Dashboard Signal Review** shall mean competence in reviewing dashboard signals before interpretation, communication, publication, escalation, or handoff.

15.4.7.2 Dashboard signal review shall include:\
(a) source check;\
(b) update check;\
(c) method check;\
(d) outlier check;\
(e) missingness check;\
(f) confidence check;\
(g) uncertainty check;\
(h) sensitivity check;\
(i) public-safe review;\
(j) correction notice review.

15.4.7.3 Dashboard signal review shall not convert dashboard information into a decision, rating, warning, finance signal, insurance score, procurement signal, public authority action, or operational command.

### **15.4.8 Sensitive Location Controls.**

15.4.8.1 **Sensitive Location Controls** shall mean competence in identifying, masking, aggregating, delaying, restricting, or otherwise protecting location information whose disclosure could create harm, exploitation, security risk, privacy risk, protected knowledge exposure, community harm, ecological harm, infrastructure risk, or public authority risk.

15.4.8.2 Sensitive location controls shall apply to:\
(a) critical infrastructure;\
(b) protected species;\
(c) sacred sites;\
(d) protected knowledge locations;\
(e) community-sensitive places;\
(f) vulnerable populations;\
(g) public authority-sensitive facilities;\
(h) cyber-physical assets;\
(i) emergency response assets;\
(j) handoff-sensitive sites.

15.4.8.3 Sensitive location control competence shall not authorize access to sensitive locations, disclosure of protected locations, field operations, surveillance, official mapping, or public authority action.

### **15.4.9 Public-Safe Observatory Output Skills.**

15.4.9.1 **Public-Safe Observatory Output Skills** shall mean competence in preparing Observatory outputs for learning, reporting, dashboard display, public-safe summaries, National Portfolio use, Nexus Universe presentation, Registry records, Marketplace discovery, Grid inputs, or handoff context without disclosing unsafe detail or implying authority.

15.4.9.2 Public-safe Observatory output skills shall include:\
(a) source statement;\
(b) method statement;\
(c) confidence label;\
(d) uncertainty label;\
(e) sensitivity review;\
(f) location masking where required;\
(g) no-warning language;\
(h) no-surveillance language;\
(i) no-decision language;\
(j) correction notice.

15.4.9.3 Public-safe Observatory outputs shall not create official warnings, surveillance authority, public authority records, operational instructions, ratings, rankings, finance signals, insurance scores, or procurement signals.

### **15.4.10 Observatory Correction Skills.**

15.4.10.1 **Observatory Correction Skills** shall mean competence in identifying, reporting, correcting, withdrawing, superseding, downgrading, recalling, or archiving Observatory signals, dashboards, geospatial layers, sensor records, digital twin inputs, public-safe summaries, and related Registry or Marketplace records.

15.4.10.2 Observatory correction skills shall include:\
(a) source error identification;\
(b) sensor error identification;\
(c) geospatial error identification;\
(d) update failure recognition;\
(e) misclassification correction;\
(f) sensitive location correction;\
(g) public-safe correction notice;\
(h) downstream correction propagation;\
(i) Registry status update;\
(j) archive.

15.4.10.3 Observatory correction shall preserve trust by ensuring that signals and outputs remain amendable, scoped, traceable, and publicly safe.

***

## **15.5 Studio and Simulation Competencies**

### **15.5.1 Scenario Design.**

15.5.1.1 **Scenario Design** shall mean competence in creating structured learning scenarios that explore possible conditions, hazards, system dependencies, risks, technology interactions, public authority questions, safeguard concerns, readiness questions, finance-readiness questions, insurance-readiness questions, and handoff dependencies.

15.5.1.2 Scenario design shall include:\
(a) scenario purpose;\
(b) system boundary;\
(c) assumptions;\
(d) data basis;\
(e) model basis;\
(f) time horizon;\
(g) stakeholder context;\
(h) uncertainty statement;\
(i) sensitivity controls;\
(j) public-safe interpretation.

15.5.1.3 Scenario design shall not create forecasts, warnings, decisions, approvals, ratings, financeability, insurability, procurement readiness, deployment authorization, or execution authority.

### **15.5.2 Simulation Interpretation.**

15.5.2.1 **Simulation Interpretation** shall mean competence in understanding simulation outputs as bounded, assumption-dependent, model-dependent, data-dependent, and uncertainty-bearing learning objects.

15.5.2.2 Simulation interpretation shall include:\
(a) input review;\
(b) model review;\
(c) parameter awareness;\
(d) sensitivity awareness;\
(e) uncertainty interpretation;\
(f) confidence interpretation;\
(g) limitation statement review;\
(h) comparison limits;\
(i) public-safe summary;\
(j) correction.

15.5.2.3 Simulation interpretation shall not create forecast certainty, certification, operational command, public authority decision, financeability, insurability, procurement readiness, or deployment approval.

### **15.5.3 Assumption Register Use.**

15.5.3.1 **Assumption Register Use** shall mean competence in recording, reading, reviewing, updating, and correcting assumptions that support scenarios, simulations, models, dashboards, National Portfolios, readiness questions, public authority learning records, finance-readiness notes, insurance-readiness notes, and handoff packages.

15.5.3.2 Assumption register competence shall include:\
(a) assumption identification;\
(b) assumption source;\
(c) assumption owner or steward;\
(d) confidence level;\
(e) uncertainty relationship;\
(f) dependency relationship;\
(g) review date;\
(h) change trigger;\
(i) correction pathway;\
(j) archive.

15.5.3.3 Assumption registers shall not create fact status, legal reliance, approval, certification, warning, rating, financeability, insurability, or procurement readiness.

### **15.5.4 Dependency Register Use.**

15.5.4.1 **Dependency Register Use** shall mean competence in identifying, recording, reviewing, communicating, and correcting dependencies affecting learning pathways, risk intelligence, scenarios, simulations, public authority learning, National Portfolios, Foundry builds, Studio workflows, Grid inputs, TRL notes, Nexus Universe outputs, and lawful handoff packages.

15.5.4.2 Dependency register competence shall include:\
(a) technical dependencies;\
(b) data dependencies;\
(c) method dependencies;\
(d) public authority dependencies;\
(e) legal dependencies;\
(f) safeguard dependencies;\
(g) finance and insurance question dependencies;\
(h) provider-neutrality dependencies;\
(i) support dependencies;\
(j) correction and recall dependencies.

15.5.4.3 Dependency registers shall not authorize execution, allocate responsibility to public authorities by implication, create financeability, create insurability, approve procurement, validate providers, or approve deployment.

### **15.5.5 Model Limitation Literacy.**

15.5.5.1 **Model Limitation Literacy** shall mean competence in identifying and communicating the limits of statistical models, AI models, forecasting models, simulation models, digital twin models, optimization models, risk models, and decision-support models.

15.5.5.2 Model limitation literacy shall include:\
(a) intended use;\
(b) prohibited use;\
(c) data limitations;\
(d) training or development limitations;\
(e) generalization limits;\
(f) uncertainty;\
(g) bias and harm considerations;\
(h) validation scope;\
(i) drift risk;\
(j) correction and withdrawal.

15.5.5.3 Model limitation literacy shall not create model approval, AI safety certification, deployment authorization, public authority decision, financeability, insurability, or procurement readiness.

### **15.5.6 Public Authority Learning Room Skills.**

15.5.6.1 **Public Authority Learning Room Skills** shall mean competence in participating in controlled learning rooms where public authority-related questions, risk intelligence, scenarios, dashboards, simulations, readiness questions, and handoff dependencies may be discussed without converting learning into official action.

15.5.6.2 Public Authority Learning Room skills shall include:\
(a) non-decision status awareness;\
(b) no public authority substitution;\
(c) no-warning boundary;\
(d) no-procurement boundary;\
(e) no-public-finance-allocation boundary;\
(f) confidentiality awareness;\
(g) public-safe output review;\
(h) escalation pathways;\
(i) correction;\
(j) archive.

15.5.6.3 Public Authority Learning Room participation shall not imply public authority approval, regulatory action, policy adoption, emergency command, public warning, funding allocation, procurement status, or official decision.

### **15.5.7 Readiness Room Literacy.**

15.5.7.1 **Readiness Room Literacy** shall mean competence in participating in controlled environments where evidence readiness, data readiness, technical readiness, safeguard readiness, public-safe readiness, National Portfolio readiness, Universe readiness, finance-readiness questions, insurance-readiness questions, and handoff dependency readiness are reviewed.

15.5.7.2 Readiness room literacy shall include:\
(a) readiness as bounded evidence;\
(b) readiness question framing;\
(c) unresolved dependency identification;\
(d) evidence sufficiency review;\
(e) support status review;\
(f) safeguard review;\
(g) public-safe review;\
(h) no-certification boundary;\
(i) correction and recall;\
(j) archive.

15.5.7.3 Readiness Room participation shall not create certification, finance approval, insurance approval, public authority approval, procurement readiness, deployment authorization, or execution authority.

### **15.5.8 Capital and Insurance Reader Room Literacy.**

15.5.8.1 **Capital and Insurance Reader Room Literacy** shall mean competence in understanding controlled, no-reliance, non-advisory, non-soliciting, non-transactional, competition-compliant environments where capital readers, insurers, reinsurers, donors, public finance readers, and related actors may review readiness questions and dependency context without creating finance, insurance, investment, underwriting, donor commitment, public finance allocation, procurement status, or execution.

15.5.8.2 Capital and insurance reader room literacy shall include:\
(a) no-reliance status;\
(b) no investment advice;\
(c) no solicitation;\
(d) no transaction;\
(e) insurance-readiness question framing;\
(f) finance-readiness question framing;\
(g) diligence-gap awareness;\
(h) confidentiality awareness;\
(i) regulated-perimeter escalation;\
(j) correction and archive.

15.5.8.3 Capital-reader or insurance-reader participation shall not imply investment interest, underwriting interest, financeability, insurability, donor commitment, public finance approval, bankability, procurement readiness, or project approval.

### **15.5.9 Controlled Demonstration Skills.**

15.5.9.1 **Controlled Demonstration Skills** shall mean competence in demonstrating dashboards, simulations, digital twins, AI workflows, data workflows, software prototypes, Studio workflows, Observatory outputs, DRI indicators, Grid inputs, TRL notes, Marketplace objects, Registry records, and handoff-context materials within recorded scope and boundary conditions.

15.5.9.2 Controlled demonstration skills shall include:\
(a) demonstration purpose;\
(b) audience classification;\
(c) data sensitivity review;\
(d) AI-use review;\
(e) public-safe language;\
(f) no-deployment language;\
(g) no-decision language;\
(h) no-finance language;\
(i) no-procurement language;\
(j) correction and archive.

15.5.9.3 Demonstration shall not constitute deployment, operational use, public authority approval, certification, provider validation, procurement recommendation, financeability, insurability, endorsement, consent, or execution.

### **15.5.10 No-Decision Runtime Controls.**

15.5.10.1 **No-Decision Runtime Controls** shall mean controls that prevent Studio workflows, dashboards, simulations, digital twins, AI outputs, readiness rooms, public authority learning rooms, capital-reader rooms, insurance-reader rooms, and controlled demonstrations from being used as decision systems by implication.

15.5.10.2 No-decision runtime controls shall include:\
(a) no-command rules;\
(b) no-write-back rules;\
(c) no automated high-stakes decision rules;\
(d) human review requirements;\
(e) output review;\
(f) access controls;\
(g) public-safe notices;\
(h) reliance labels;\
(i) escalation pathways;\
(j) shutdown and correction triggers.

15.5.10.3 No-decision runtime controls shall preserve the distinction between learning, simulation, review, demonstration, readiness context, and lawful decision-making by competent actors outside SCF default posture.

***

## **15.6 Risk Intelligence Boundary Rules**

### **15.6.1 Indicator Is Not Rating.**

15.6.1.1 No indicator, DRI output, dashboard metric, Observatory signal, National Portfolio metric, Grid input, TRL note, public-safe summary, or Studio output shall be treated as a rating, ranking, score, certification, maturity determination, insurance classification, investment classification, procurement qualification, country ranking, provider validation, or public authority classification by implication.

15.6.1.2 Any formal rating, ranking, certification, maturity determination, insurance classification, investment classification, procurement qualification, or public authority classification must be separately and lawfully established by competent actors.

### **15.6.2 Dashboard Is Not Decision.**

15.6.2.1 No dashboard, visual interface, map, chart, signal panel, digital twin view, Studio interface, risk intelligence display, Marketplace display, Registry display, National Portfolio display, or Nexus Universe display shall constitute a decision, approval, authorization, command, warning, allocation, procurement action, finance action, insurance action, consent, or deployment action by implication.

15.6.2.2 Dashboards shall be interpreted as bounded, source-dependent, method-dependent, update-dependent, review-dependent, and correctionable learning and communication interfaces.

### **15.6.3 Scenario Is Not Forecast Certainty.**

15.6.3.1 No scenario, simulation, stress test, tabletop exercise, digital twin run, model output, forecast-adjacent output, AI-generated scenario, or Studio exercise shall be treated as forecast certainty, prediction guarantee, official forecast, public warning, rating, decision, finance signal, insurance signal, procurement signal, or execution trigger by implication.

15.6.3.2 Scenario outputs shall carry assumptions, uncertainty, confidence, limitations, scope, and correction pathways.

### **15.6.4 DRI Output Is Not Warning.**

15.6.4.1 No DRI indicator, signal, hotspot record, cascade record, dashboard, public-safe summary, National Portfolio record, Nexus Universe output, Report, Registry record, Marketplace listing, Studio workflow, Grid input, or TRL note shall constitute an official warning, alert, emergency communication, evacuation instruction, public health warning, infrastructure warning, security warning, or public authority action by implication.

15.6.4.2 Where escalation is appropriate, DRI outputs shall be routed to competent actors through recorded channels rather than issued as public warnings by SCF participants.

### **15.6.5 Observatory Signal Is Not Surveillance Authority.**

15.6.5.1 No Observatory signal, sensor record, edge signal, geospatial layer, Earth observation layer, digital twin input, dashboard, field observation, public-safe output, or degraded-mode record shall create surveillance authority, monitoring authority, public authority record status, enforcement authority, operational control, public warning authority, or emergency command by implication.

15.6.5.2 Observatory competence shall remain bounded by public-good learning, public-safe observability, recorded purpose, access controls, sensitivity controls, correction, and archive.

### **15.6.6 Simulation Competence Is Not Deployment Approval.**

15.6.6.1 No simulation competence, scenario design record, Studio exercise completion, digital twin literacy record, dashboard interpretation record, readiness room participation, model limitation literacy, or controlled demonstration record shall constitute deployment approval, operational readiness, public authority approval, safety certification, procurement readiness, financeability, insurability, or execution authorization by implication.

15.6.6.2 Deployment, operational use, procurement, finance, insurance, public authority action, and implementation decisions shall remain with competent lawful actors outside SCF default posture.

***

## **15.7 Final Part XV Operating Statement**

15.7.1 SCF shall treat GRIx, DRI, Nexus Observatory, risk intelligence, scenarios, simulations, dashboards, digital twins, and Nexus Studio competencies as essential public-good capabilities for all-hazards resilience, WFEH-B systems, disaster-risk literacy, national capability formation, public authority learning, Nexus Foundry production, Nexus Reports publication, Nexus Registry status truth, Nexus Marketplace discovery, Nexus Grid readiness review, Nexus Universe preparation, and lawful handoff context.

15.7.2 SCF shall ensure that risk intelligence competence includes controlled vocabulary use, risk taxonomy literacy, WFEH-B category mapping, DRR / DRF / DRI mapping, systems-risk classification, frontier technology risk classification, safeguard category literacy, handoff dependency category literacy, indicator literacy, signal interpretation, uncertainty labels, confidence labels, dashboard interpretation, public-safe intelligence writing, hotspot and cascade literacy, DRI correction, no-warning communication, and no-rating communication.

15.7.3 SCF shall ensure that Observatory competence includes observability literacy, sensor and edge signal literacy, geospatial literacy, Earth observation literacy, digital twin literacy, degraded-mode awareness, dashboard signal review, sensitive location controls, public-safe Observatory output skills, and Observatory correction skills.

15.7.4 SCF shall ensure that Studio and simulation competence includes scenario design, simulation interpretation, assumption register use, dependency register use, model limitation literacy, public authority learning room skills, readiness room literacy, capital and insurance reader room literacy, controlled demonstration skills, and no-decision runtime controls.

15.7.5 SCF shall preserve the rule that risk intelligence is a competence system for learning, public-safe interpretation, evidence formation, national capability development, and lawful handoff context, not a substitute for public authorities, emergency services, regulators, insurers, investors, procurement bodies, standards authorities, professional certifiers, or execution actors.

15.7.6 The final rule of Part XV is that SCF shall make Nexus learners, workers, contributors, reviewers, mentors, Competence Cells, National Working Groups, public authority learning participants, employers, providers, sponsors, capital readers, insurance readers, and lawful downstream actors more capable of understanding and using risk intelligence safely, but shall not convert any risk taxonomy, controlled vocabulary, indicator, dashboard, signal, Observatory output, scenario, simulation, digital twin, Studio workflow, readiness room participation, capital-reader room participation, insurance-reader room participation, public-safe intelligence summary, Registry record, Marketplace listing, Grid input, TRL note, or handoff-context package into a rating, warning, forecast certainty, public authority decision, surveillance authority, financeability, insurability, procurement status, certification, deployment approval, community consent, Indigenous consent, or execution authority by implication.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.therisk.global/organization/operations/frameworks/sustainable-competency-framework-scf/xv.-risk.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.