# XIII. INTELLIGENCE

Nexus Agile Framework Intelligence defines the **NAF risk intelligence model** for GRIx, DRI, Nexus Observatory, indicators, signals, scenarios, digital twins, and public-safe risk meaning. This section explains how **risk ontology, controlled vocabularies, disaster risk intelligence, observability records, hotspot analysis, confidence labels, and uncertainty labels** support public-good learning.

This section sets the operating model for **risk intelligence architecture**, **GRIx ontology and taxonomy controls**, **DRI indicators and signal records**, **Observatory observability workflows**, and **scenario and simulation evidence**. It helps Nexus structure risk meaning, improve discoverability, strengthen observability, and support lawful handoff without creating public warnings, ratings, public authority decisions, or execution by implication.

### What this section covers

* **Risk intelligence architecture** - Defines GRIx, DRI, Nexus Observatory, and intelligence object governance.
* **Indicators and scenarios** - Explains indicators, signals, hotspots, scenarios, simulations, and digital twin evidence.
* **Boundary controls** - Defines no-warning, no-rating, no-decision, and no-deployment rules.

Use this section with [Nexus Agile Framework (NAF)](/organization/operations/frameworks/nexus-agile-framework-naf.md) for the full framework overview, [X. DATA](/organization/operations/frameworks/nexus-agile-framework-naf/x.-data.md) for data rights, metadata, and compute-to-data controls, [XI. AI](/organization/operations/frameworks/nexus-agile-framework-naf/xi.-ai.md) for AI workflows, model controls, and human review, and [XII. COMPUTE](/organization/operations/frameworks/nexus-agile-framework-naf/xii.-compute.md) for observability infrastructure, edge signals, and compute governance.

## 13.1 Risk Intelligence Architecture

### 13.1.1 GRIx as Risk Ontology and Controlled Vocabulary.

13.1.1.1 GRIx shall operate within NAF as the controlled risk-meaning layer through which risk language, hazard categories, exposure concepts, vulnerability concepts, resilience-capacity concepts, systems-risk relationships, WFEH-B taxonomies, disaster-risk categories, disaster-risk-finance concepts, disaster-risk-intelligence concepts, frontier-technology risk categories, safeguard categories, public authority boundary categories, finance and insurance boundary categories, procurement boundary categories, handoff dependency categories, correction categories, and archive categories are defined, versioned, localized, mapped, reviewed, corrected, and preserved.

13.1.1.2 GRIx shall prevent uncontrolled semantic drift by requiring that material risk terms used in Dockets, Reports, DRI indicators, Observatory records, Studio workflows, Grid inputs, TRL notes, National Portfolio objects, Nexus Universe outputs, Marketplace listings, Registry records, Campaign materials, Academy materials, Foundry outputs, public authority learning records, readiness-room records, capital-reader records, insurance-reader records, donor-reader records, and handoff dependency packages be mapped to recorded definitions, scope notes, limitations, confidence conditions, jurisdictional notes where applicable, and correction pathways.

13.1.1.3 GRIx shall support interoperability across Nexus without becoming a legal classification system, standards authority, public authority taxonomy, insurance rating taxonomy, investment taxonomy, procurement taxonomy, certification system, or operational command structure by implication. Its function is to preserve meaning, comparability, traceability, and correction across risk intelligence work.

13.1.1.4 GRIx shall be open where safe and controlled where necessary. Public-safe terms, definitions, taxonomies, and mappings may be published or listed; restricted mappings involving protected knowledge, sensitive infrastructure, cyber-sensitive categories, public authority-sensitive categories, Indigenous protocol-sensitive knowledge where applicable, community-sensitive information, or dual-use information may be held in controlled records, secure rooms, data rooms, or archive-only form.

### 13.1.2 DRI as Disaster Risk Intelligence Structure.

13.1.2.1 DRI shall operate within NAF as the disaster-risk-intelligence structure through which hazards, exposures, vulnerabilities, capacities, compounding risks, cascading risks, systemic risks, hotspots, indicators, signals, confidence labels, uncertainty labels, public-safe summaries, dashboard records, National Portfolio inputs, Nexus Universe outputs, and handoff dependency context are assembled, reviewed, corrected, archived, and routed.

13.1.2.2 DRI shall support disaster-risk reduction, disaster-risk finance literacy, resilience planning, WFEH-B systems understanding, public authority learning, public-good reporting, National Portfolio formation, Observatory acceleration, Studio scenario work, Grid and TRL evidence context, Nexus Universe arena preparation, capital-reader learning, insurance-reader learning, donor-reader learning, and lawful handoff preparation.

13.1.2.3 DRI shall not become public warning authority, emergency command, official forecast, insurance score, investment signal, credit rating, public finance allocation signal, procurement signal, public authority decision, certification, deployment authorization, or execution. DRI outputs shall be intelligence objects and learning records unless separately and lawfully converted by competent actors outside NAF’s default posture.

13.1.2.4 DRI shall preserve uncertainty and confidence discipline. No DRI output shall be released, routed, displayed, or handed off in a manner that hides source limitations, data gaps, model limitations, uncertainty, confidence status, update cadence, public-safe constraints, safeguard concerns, or correction pathways.

### 13.1.3 Nexus Observatory as Observability and Signal Layer.

13.1.3.1 Nexus Observatory shall operate within NAF as the observability and signal layer through which signals from data sources, sensors, edge nodes, geospatial layers, Earth observation sources, dashboards, field records, public-safe reports, Campaign inputs, National Working Group inputs, Competence Cell outputs, Studio workflows, digital twins, DRI indicators, GRIx mappings, public authority learning rooms, National Portfolios, Nexus Universe arenas, and lawful handoff contexts are detected, classified, reviewed, routed, corrected, and archived.

13.1.3.2 Nexus Observatory shall support situational learning, not surveillance by default. It shall produce observability records, public-safe observability outputs, signal records, edge-signal notes, degraded-mode awareness records, dashboard records, hotspot context, DRI inputs, Studio inputs, Reports inputs, Grid inputs, TRL context, National Portfolio inputs, and handoff dependency notes.

13.1.3.3 Observatory functions shall be governed by data rights, privacy, cybersecurity, geospatial sensitivity, public authority sensitivity, community safeguards, Indigenous protocols where applicable, protected knowledge controls, source limitations, public-safe publication controls, no-warning discipline, role separation, correctionability, and archive.

13.1.3.4 Observatory signals shall not create surveillance authority, public warning authority, public authority decision, emergency command, infrastructure command, operational command, deployment authorization, consent, financeability, procurement status, insurance approval, or execution.

### 13.1.4 Studio as Scenario and Runtime Learning Layer.

13.1.4.1 Nexus Studio shall operate within the intelligence architecture as the controlled scenario, simulation, digital twin, dashboard, AI workflow, secure-room, data-room, public authority learning room, readiness-room, capital-reader room, insurance-reader room, donor-reader room, and Nexus Universe demonstration environment through which intelligence objects can be explored without being converted into decisions or execution.

13.1.4.2 Studio workflows may use GRIx terms, DRI indicators, Observatory signals, datasets, models, digital twins, AI outputs, dashboard records, scenario assumptions, dependency registers, uncertainty labels, confidence labels, and public-safe summaries to support learning, sensemaking, evidence review, risk interpretation, readiness questions, and lawful handoff dependency identification.

13.1.4.3 Studio shall preserve no-command rules, no-write-back rules where applicable, output review, data-use labels, AI-use labels, public-safe review, safeguard review, public authority boundary review, finance and procurement boundary review, correction pathways, and archive rules.

13.1.4.4 Studio outputs shall not be treated as public authority decisions, public warnings, forecasts, ratings, certifications, finance approvals, insurance approvals, procurement recommendations, deployment authorizations, operational commands, or execution instructions.

### 13.1.5 Reports as Public-Safe Publication Layer.

13.1.5.1 Nexus Reports shall operate within the intelligence architecture as the public-safe publication layer through which risk intelligence, DRI summaries, Observatory outputs, GRIx explanations, scenario summaries, Studio outputs, National Portfolio intelligence, Nexus Universe intelligence outputs, Grid and TRL context notes, and handoff dependency summaries may be translated into publishable knowledge.

13.1.5.2 Reports shall transform intelligence into public-safe form through source review, evidence review, method review, public-safe drafting, no-warning language, no-rating language, no-finance language, no-procurement language, no-certification language, no-consent language, no-deployment language, no-execution language, protected knowledge controls, geospatial controls, and correction notices.

13.1.5.3 Reports shall preserve the difference between intelligence, evidence, learning, and authority. A Report may describe a risk, indicator, trend, scenario, signal, hotspot, vulnerability, resilience capacity, readiness question, or handoff dependency; it shall not create public warning, public authority decision, insurance score, investment signal, certification, procurement status, deployment authorization, or execution.

### 13.1.6 Registry as Status-Truth Layer.

13.1.6.1 Nexus Registry shall operate within the intelligence architecture as the status-truth layer for intelligence objects, including GRIx terms, DRI indicators, Observatory nodes, dashboard records, signal records, hotspot records, scenario records, simulation records, digital twin records, public-safe summaries, Reports, Grid inputs, TRL notes, National Portfolio intelligence objects, Nexus Universe outputs, and handoff dependency records.

13.1.6.2 Registry records shall preserve identity, version, steward, source basis, data-use labels, AI-use labels, review status, public-safe status, confidence status, uncertainty status, support status, correction status, withdrawal status, archive status, and no-conversion notices for intelligence objects.

13.1.6.3 Registry status shall not certify truth, validate providers, rank countries, rate communities, approve projects, create public authority action, create financeability, create procurement status, create consent, or authorize deployment. Registry status records what NAF has recorded; it does not create authority beyond the record.

### 13.1.7 Marketplace as Discovery Layer.

13.1.7.1 Nexus Marketplace shall operate within the intelligence architecture as the discovery layer for public-safe and controlled-discovery intelligence objects, including Reports, dashboards, datasets, metadata records, DRI objects, GRIx objects, Observatory objects, Studio workflows, learning objects, Foundry objects, National Portfolio objects, Nexus Universe outputs, Grid inputs, TRL notes, and handoff context objects.

13.1.7.2 Marketplace listings shall make intelligence discoverable without implying certification, endorsement, procurement approval, vendor validation, public authority approval, financeability, insurability, consent, deployment authorization, or execution.

13.1.7.3 Marketplace listings of intelligence objects shall carry metadata, Registry status where applicable, access class, support class, public-safe status, data-use label where applicable, AI-use label where applicable, confidence and uncertainty notes where applicable, limitations, correction pathway, and boundary notices.

### 13.1.8 Grid and TRL as Bounded Readiness Evidence Layers.

13.1.8.1 Nexus Grid and TRL 1–10 evidence notes shall operate within the intelligence architecture as bounded readiness evidence layers. They may receive intelligence inputs from GRIx, DRI, Observatory, Studio, Reports, Marketplace, Registry, National Portfolios, Nexus Universe, Foundry, Academy, Labs, Campaigns, and lawful handoff contexts.

13.1.8.2 Grid and TRL intelligence inputs shall record evidence sufficiency, method quality, data status, AI-use status, cyber status, public-safe status, safeguard status, support status, repository status, Marketplace status, Registry status, handoff dependency status, and correction status where applicable.

13.1.8.3 Grid and TRL intelligence inputs shall not create maturity certification, procurement readiness, financeability, insurability, public authority approval, deployment authorization, or execution. They classify bounded evidence and readiness context only.

## 13.2 GRIx Architecture

### 13.2.1 Risk Categories.

13.2.1.1 GRIx Risk Categories shall provide controlled terms for hazards, threats, vulnerabilities, exposures, capacities, impacts, likelihoods, consequences, systemic risks, compounding risks, cascading risks, emerging risks, frontier risks, technological risks, institutional risks, legal risks, social risks, ecological risks, financial-readiness questions, safeguard risks, data risks, AI risks, cyber risks, and handoff risks.

13.2.1.2 Risk Categories shall include definitions, scope notes, examples, exclusions, related terms, parent and child relationships, data needs, indicator relationships, public-safe guidance, boundary notices, localization notes where applicable, and correction history.

13.2.1.3 Risk Categories shall be used to structure intelligence, not to make legal, regulatory, insurance, investment, procurement, public warning, or operational determinations.

### 13.2.2 WFEH-B Taxonomies.

13.2.2.1 WFEH-B Taxonomies shall organize water, food, energy, health, biodiversity, nature, infrastructure, climate, community resilience, and cross-system dependency concepts in a controlled vocabulary for NAF.

13.2.2.2 WFEH-B Taxonomies shall support National Portfolios, DRI indicators, Observatory signals, Studio scenarios, Reports, Academy learning, Foundry builds, Campaigns, Nexus Universe arenas, Grid inputs, TRL notes, and lawful handoff dependency packages.

13.2.2.3 WFEH-B Taxonomies shall identify cross-system cascades, corridor dependencies, cluster dependencies, national dense Nexus Core profiles, public-safe reporting limits, protected knowledge risks, geospatial sensitivity, public authority dependencies, and handoff dependencies.

13.2.2.4 WFEH-B Taxonomy use shall not create environmental certification, public authority approval, public health decision, water rights, land-use approval, community consent, Indigenous consent where applicable, financeability, procurement status, deployment authorization, or execution.

### 13.2.3 DRR Categories.

13.2.3.1 DRR Categories shall structure disaster-risk-reduction concepts, including prevention, mitigation, preparedness, resilience capacity, exposure reduction, vulnerability reduction, risk governance, early-warning interface, response-learning interface, recovery-learning interface, risk communication, community resilience, infrastructure resilience, and systems resilience.

13.2.3.2 DRR Categories shall support all-hazards learning, National Portfolio formation, DRI interpretation, Observatory records, Studio scenarios, Reports, Campaigns, Nexus Universe arenas, public authority learning, and handoff dependency context.

13.2.3.3 DRR Category use shall not create public warning authority, emergency command, public authority decision, disaster declaration, official plan approval, procurement status, deployment authorization, or execution.

### 13.2.4 DRF Categories.

13.2.4.1 DRF Categories shall structure disaster-risk-finance literacy and readiness concepts, including protection gaps, risk layering, contingent finance, insurance-readiness questions, public finance relevance, donor-readiness questions, resilience investment context, assumptions, dependencies, diligence gaps, no-reliance rooms, capital-reader rooms, insurance-reader rooms, donor-reader rooms, and public finance learning rooms.

13.2.4.2 DRF Categories shall be used to make risk and resilience work readable to capital and insurance actors without converting NAF into a fund, broker, lender, insurer, underwriter, investment adviser, rating agency, public finance allocation body, or transaction platform.

13.2.4.3 DRF Category use shall not create investment advice, insurance advice, financeability, insurability, underwriting approval, donor commitment, public finance allocation, rating, procurement status, public authority approval, or execution.

### 13.2.5 DRI Categories.

13.2.5.1 DRI Categories shall structure disaster-risk-intelligence objects, including indicator records, signal records, confidence labels, uncertainty labels, hotspot records, multi-hazard records, cascade records, public-safe intelligence summaries, dashboard records, National DRI contributions, correction records, and archive records.

13.2.5.2 DRI Categories shall support consistent intelligence formation across countries, regions, sectors, hazards, technologies, and Nexus cycles while preserving local context, national ownership, uncertainty, and correctionability.

13.2.5.3 DRI Category use shall not create warnings, ratings, official statistics, insurance scores, investment signals, public authority decisions, procurement signals, deployment authorization, or execution.

### 13.2.6 Systems-Risk Categories.

13.2.6.1 Systems-Risk Categories shall define and structure interconnected, cascading, compounding, cross-sector, cross-border, cyber-physical, socio-technical, ecological, economic, institutional, infrastructure, climate, health, food, water, energy, biodiversity, telecom, data, AI, and supply-chain risks.

13.2.6.2 Systems-Risk Categories shall support scenario analysis, digital twin design, Observatory mapping, DRI indicators, Studio workflows, Reports, National Portfolio formation, Nexus Universe arenas, and handoff dependency packages.

13.2.6.3 Systems-Risk Category use shall not create forecast certainty, official risk determination, public warning, public authority decision, financeability, procurement status, deployment authorization, or execution.

### 13.2.7 Frontier Technology Risk Categories.

13.2.7.1 Frontier Technology Risk Categories shall structure risks associated with AI, agentic systems, frontier models, AI-RAN, O-RAN, telecom, private wireless, edge, cloud, HPC, sovereign compute, verifiable compute, cybersecurity, geospatial systems, Earth observation, digital twins, sensors, drones, robotics, IoT, OT, IIoT, DLT, DePIN, Web3, digital identity, quantum-relevant security, semiconductors, advanced manufacturing, biosecurity-sensitive systems, and frontier science infrastructure.

13.2.7.2 Frontier Technology Risk Categories shall support R\&D governance, Foundry builds, software releases, data governance, AI governance, compute governance, Observatory workflows, Studio scenarios, Grid inputs, TRL notes, Reports, Marketplace listings, Registry records, Nexus Universe demonstrations, and handoff dependency context.

13.2.7.3 Frontier Technology Risk Category use shall not certify technology safety, approve deployment, validate providers, create standards conformance, create public authority approval, create procurement status, create financeability, or create execution.

### 13.2.8 Public Authority Boundary Categories.

13.2.8.1 Public Authority Boundary Categories shall identify where risk intelligence touches public authority functions, including public warnings, emergency management, public finance, permitting, licensing, procurement, regulation, public health, public safety, critical infrastructure, national planning, official statistics, official maps, public employment systems, and public records.

13.2.8.2 These categories shall trigger public authority boundary review, no-decision notices, public-safe language, role-separation records, and escalation where needed.

13.2.8.3 Public Authority Boundary Categories shall not create official action, public authority approval, public warning, emergency command, public finance allocation, procurement decision, regulation, permit, license, or execution.

### 13.2.9 Finance and Insurance Boundary Categories.

13.2.9.1 Finance and Insurance Boundary Categories shall identify where intelligence may be read by capital readers, insurers, reinsurers, donors, public finance readers, or other finance-adjacent actors. They shall structure no-reliance, non-advisory, non-soliciting, non-transactional, no-underwriting, no-rating, no-financeability, and no-insurability discipline.

13.2.9.2 These categories shall support assumptions registers, dependency registers, diligence-gap registers, readiness-room records, capital-reader room records, insurance-reader room records, donor-reader room records, and handoff dependency notes.

13.2.9.3 Finance and Insurance Boundary Categories shall not create investment advice, offer, solicitation, transaction, underwriting, insurance approval, rating, valuation, financeability, bankability, donor commitment, public finance allocation, procurement status, or execution.

### 13.2.10 Safeguard Categories.

13.2.10.1 Safeguard Categories shall structure community safeguards, Indigenous protocols where applicable, protected knowledge, youth safeguards, disability inclusion, accessibility, humanitarian sensitivity, public-interest participation, non-extractive engagement, data protection, privacy, security, rights-sensitive impacts, and community-facing correction.

13.2.10.2 Safeguard Categories shall trigger safeguard review, community-sensitive handling, Indigenous protocol-sensitive handling where applicable, protected knowledge controls, public-safe transformation, access restriction, correction, withdrawal, sealing, or archive where needed.

13.2.10.3 Safeguard Category use shall not create consent, substitute for community process, substitute for Indigenous process where applicable, approve deployment, validate extraction, or authorize handoff.

### 13.2.11 Handoff Dependency Categories.

13.2.11.1 Handoff Dependency Categories shall classify the dependencies that must be carried forward when intelligence moves from public-good NAF work into lawful recipient contexts, including data dependencies, method dependencies, model dependencies, public authority dependencies, legal dependencies, safeguard dependencies, provider-neutrality dependencies, sponsor-boundary dependencies, finance and insurance question dependencies, procurement boundary dependencies, support dependencies, correction dependencies, and archive dependencies.

13.2.11.2 Handoff Dependency Categories shall support lawful handoff packages without transferring authority. They shall identify what must be independently reviewed by the recipient and competent actors before any implementation, procurement, finance, insurance, public authority action, deployment, or execution.

13.2.11.3 Handoff Dependency Categories shall not authorize implementation, create recipient approval, create financeability, create procurement status, create consent, create public authority approval, or execute projects.

## 13.3 DRI Architecture

### 13.3.1 Indicator Records.

13.3.1.1 Indicator Records shall document DRI indicators, including indicator name, definition, purpose, GRIx mapping, hazard relationship, exposure relationship, vulnerability relationship, capacity relationship, data source, method, geography, time period, update cadence, confidence label, uncertainty label, limitations, public-safe status, data-use label, AI-use label where applicable, review status, correction pathway, and archive rule.

13.3.1.2 Indicator Records may support dashboards, Reports, National Portfolios, Observatory signals, Studio scenarios, Nexus Universe arenas, Grid inputs, TRL notes, public authority learning, readiness-room questions, capital-reader learning, insurance-reader learning, donor-reader learning, and handoff dependency context.

13.3.1.3 Indicator Records shall not be ratings, official statistics by implication, insurance scores, investment signals, public warnings, public authority decisions, procurement scores, deployment authorizations, or execution instructions.

### 13.3.2 Signal Records.

13.3.2.1 Signal Records shall document observed, reported, inferred, modeled, simulated, sensed, or submitted intelligence signals relevant to risk, resilience, WFEH-B systems, disaster risk, frontier technology, public authority learning, safeguards, National Portfolios, Nexus Universe, or handoff dependencies.

13.3.2.2 Signal Records shall identify source, timestamp where applicable, location class where applicable, data class, sensitivity class, confidence, uncertainty, method, related indicators, related Dockets, public-safe status, review status, correction pathway, and archive rule.

13.3.2.3 Signals shall be treated as inputs requiring interpretation, not as truth by themselves. A signal shall not be a public warning, forecast certainty, public authority decision, rating, approval, consent, deployment authorization, or execution.

### 13.3.3 Confidence Labels.

13.3.3.1 Confidence Labels shall express the degree of confidence in an indicator, signal, dashboard, scenario, public-safe intelligence summary, Observatory output, Studio output, Report, Grid input, TRL note, National Portfolio object, or handoff dependency note.

13.3.3.2 Confidence Labels shall be based on data quality, source reliability, method maturity, recency, completeness, reproducibility, expert review, model limitations, uncertainty, disagreement, and correction history.

13.3.3.3 Confidence Labels shall not eliminate uncertainty, create certification, create official status, create public warning authority, create financeability, or authorize execution.

### 13.3.4 Uncertainty Labels.

13.3.4.1 Uncertainty Labels shall identify known uncertainty, including data gaps, measurement limits, model uncertainty, scenario uncertainty, geographic uncertainty, temporal uncertainty, source disagreement, bias risk, method uncertainty, emerging-risk uncertainty, and unresolved assumptions.

13.3.4.2 Uncertainty Labels shall accompany material DRI outputs, Observatory outputs, scenario outputs, digital twin outputs, Reports, dashboards, National Portfolio intelligence, Nexus Universe outputs, and handoff dependency notes where uncertainty affects interpretation.

13.3.4.3 Uncertainty shall not be hidden to create stronger claims. Where uncertainty is material, release class, public-safe language, readiness status, and handoff context shall reflect it.

### 13.3.5 Public-Safe Intelligence Summaries.

13.3.5.1 Public-Safe Intelligence Summaries shall translate intelligence into shareable form without exposing restricted data, protected knowledge, sensitive geospatial information, cyber-sensitive information, public authority-sensitive information, health-sensitive information, community-sensitive information, Indigenous protocol-sensitive information where applicable, dual-use information, or overclaiming authority.

13.3.5.2 Public-Safe Intelligence Summaries shall carry source scope, limitations, confidence label where appropriate, uncertainty label where appropriate, public-safe status, no-warning notice, no-rating notice, no-finance notice, no-procurement notice, no-certification notice, no-consent notice, no-deployment notice, no-execution notice, correction pathway, and archive rule.

13.3.5.3 Public-Safe Intelligence Summaries shall not be public warnings, official forecasts, ratings, public authority decisions, insurance scores, investment signals, procurement guidance, deployment authorizations, or execution instructions.

### 13.3.6 Dashboard Records.

13.3.6.1 Dashboard Records shall document dashboards used to display DRI indicators, Observatory signals, WFEH-B records, National Portfolio records, Studio outputs, Campaign data, Reports data, Marketplace data, Registry data, Grid inputs, TRL context, Nexus Universe outputs, or handoff dependency context.

13.3.6.2 Dashboard Records shall include data sources, update cadence, visual methods, confidence labels, uncertainty labels, sensitivity controls, geospatial masking where applicable, public-safe status, access class, AI-use status where applicable, user class, limitations, correction pathway, and archive rule.

13.3.6.3 Dashboard Records shall not make dashboards into decisions, warnings, ratings, official maps, public authority records, finance signals, procurement signals, operational commands, deployment authorizations, or execution tools.

### 13.3.7 Hotspot Records.

13.3.7.1 Hotspot Records shall document locations, systems, sectors, communities, corridors, clusters, or thematic areas where risk signals, exposure, vulnerability, capacity gaps, cascading risk, or readiness needs appear concentrated within recorded scope.

13.3.7.2 Hotspot Records shall include data basis, method, geography class, sensitivity review, geospatial controls, community safeguard review where applicable, Indigenous protocol review where applicable, public authority boundary review, confidence, uncertainty, public-safe status, correction pathway, and archive rule.

13.3.7.3 Hotspot Records shall not be public warnings, official designations, emergency declarations, insurance scores, investment signals, procurement rankings, land-use determinations, community consent determinations, public authority decisions, deployment authorizations, or execution.

### 13.3.8 Multi-Hazard Records.

13.3.8.1 Multi-Hazard Records shall document interactions among hazards, including climate, weather, water, food, energy, health, biodiversity, cyber, infrastructure, geophysical, biological, technological, social, economic, and governance-related hazards.

13.3.8.2 Multi-Hazard Records shall identify hazard relationships, cascading pathways, compounding conditions, exposure and vulnerability context, capacity context, data sources, model assumptions, uncertainty, confidence, public-safe status, scenario relevance, correction pathway, and archive rule.

13.3.8.3 Multi-Hazard Records shall not be official hazard warnings, emergency commands, public authority decisions, insurance ratings, procurement rankings, deployment authorizations, or execution instructions.

### 13.3.9 Cascade Records.

13.3.9.1 Cascade Records shall document possible or observed risk cascades across systems, sectors, geographies, infrastructure, institutions, supply chains, digital systems, WFEH-B systems, and frontier technology dependencies.

13.3.9.2 Cascade Records shall include initiating conditions, affected systems, dependency pathways, assumptions, evidence basis, confidence, uncertainty, scenario relevance, public-safe status, sensitive information controls, correction pathway, and archive rule.

13.3.9.3 Cascade Records shall support learning and preparedness thinking without becoming official forecasts, public warnings, operational commands, public authority decisions, finance signals, procurement signals, deployment authorizations, or execution.

### 13.3.10 National DRI Contributions.

13.3.10.1 National DRI Contributions shall be country-level or national-context contributions to DRI made through National Nexus Consortiums, National Councils, National Working Groups, Competence Cells, National Nodes, universities, public authorities, communities, civil society, providers, sponsors, or other lawful participants under national ownership and role separation.

13.3.10.2 National DRI Contributions shall record contributor role, national context, data class, source basis, public authority sensitivity, community sensitivity, Indigenous protocol sensitivity where applicable, protected knowledge status, public-safe status, GRIx mapping, confidence, uncertainty, review status, correction pathway, and archive rule.

13.3.10.3 National DRI Contributions shall not be country rankings, official national statistics by implication, public authority approval, public warning, procurement guidance, financeability, insurance score, consent, deployment authorization, or execution.

### 13.3.11 Correction Records.

13.3.11.1 DRI Correction Records shall document corrections to indicators, signals, dashboards, hotspots, multi-hazard records, cascade records, public-safe summaries, National DRI contributions, Reports, Registry records, Marketplace listings, Studio workflows, Grid inputs, TRL notes, Nexus Universe outputs, National Portfolio records, or handoff dependency notes.

13.3.11.2 Correction may include erratum, addendum, metadata correction, source correction, confidence change, uncertainty change, data correction, method correction, dashboard correction, public-safe correction, withdrawal, recall, suppression, sealing, archive, or non-continuation.

13.3.11.3 Correction Records shall preserve trust by making limitations, errors, changes, and supersessions visible to appropriate users and downstream recipients.

### 13.3.12 Archive Records.

13.3.12.1 DRI Archive Records shall preserve non-current, superseded, corrected, withdrawn, restricted, or historical intelligence records with archive-not-current notices, access class, sensitivity class, public-safe status, correction history, successor links, retention rule, and permitted historical use.

13.3.12.2 Archive Records shall preserve institutional memory while preventing outdated intelligence from being misused as current evidence, current warning, current readiness, current public authority context, current finance-readiness context, or current handoff context.

13.3.12.3 Archive status shall not create current authority, public warning, rating, public authority decision, financeability, procurement status, deployment authorization, or execution.

## 13.4 Observatory Architecture

### 13.4.1 Observatory Nodes.

13.4.1.1 Observatory Nodes shall be local, national, regional, thematic, sectoral, technical, institutional, edge, sensor-linked, data-linked, or Studio-linked observability points that support signal detection, DRI inputs, dashboard records, geospatial records, Earth observation records, digital twin inputs, degraded-mode awareness, public-safe outputs, and National Portfolio memory.

13.4.1.2 Observatory Node records shall identify steward, jurisdiction, source classes, data classes, AI-use labels, signal classes, network dependencies, compute dependencies, public authority sensitivity, community sensitivity, Indigenous protocol sensitivity where applicable, protected knowledge status, cyber sensitivity, geospatial sensitivity, public-safe status, correction pathway, and archive rule.

13.4.1.3 Observatory Nodes shall not create surveillance authority, public warning authority, public authority approval, operational command, deployment authorization, or execution.

### 13.4.2 Observatory Hubs.

13.4.2.1 Observatory Hubs shall coordinate multiple Observatory Nodes, data sources, dashboards, DRI indicators, GRIx mappings, public-safe summaries, Studio workflows, National Portfolio inputs, Nexus Universe inputs, and handoff dependency context across a thematic, regional, national, technical, or systems-risk scope.

13.4.2.2 Observatory Hubs shall preserve node-level source integrity, national ownership, data sovereignty, public-safe controls, safeguard controls, provider neutrality, sponsor boundary discipline, correction propagation, and archive continuity.

13.4.2.3 Observatory Hub coordination shall not create regional supremacy, national bypass, public authority action, public warning authority, provider validation, deployment authorization, or execution.

### 13.4.3 Regional Clusters.

13.4.3.1 Regional Clusters shall support cross-country, corridor, basin, ecosystem, infrastructure, supply-chain, disaster-risk, WFEH-B, climate, geospatial, telecom, compute, and frontier-technology observability where regional learning is useful and national ownership is preserved.

13.4.3.2 Regional Cluster records shall identify participating national contexts, regional dependencies, shared hazards, shared systems, data sharing rules, localization rules, public-safe release rules, public authority boundaries, community safeguards, Indigenous protocol considerations where applicable, correction pathways, and archive rules.

13.4.3.3 Regional Clusters shall not override national authority, create supranational authority, create public warning authority, create public authority approval, create procurement status, create financeability, authorize deployment, or execute projects.

### 13.4.4 National Dense Nexus Cores.

13.4.4.1 National Dense Nexus Cores shall be concentrated national capability environments where National Portfolios, National Working Groups, Competence Cells, Observatory Nodes, DRI inputs, Studio workflows, Academy pathways, Foundry builds, Reports, Marketplace objects, Registry records, Nexus Universe preparation, and lawful handoff dependency context converge.

13.4.4.2 National Dense Nexus Core records shall include national context, participating institutions, data sovereignty conditions, public authority learning rooms, readiness rooms, secure rooms, data rooms, compute environments, Observatory records, DRI records, public-safe summaries, safeguard records, correction pathways, and archive rules.

13.4.4.3 National Dense Nexus Cores shall preserve national ownership without creating public authority approval, procurement authority, finance authority, certification authority, consent, deployment authorization, or execution.

### 13.4.5 Edge Signals.

13.4.5.1 Edge Signals shall be signals generated or processed near their source, including sensor data, local infrastructure data, field observations, connectivity events, environmental readings, cyber-physical signals, edge AI outputs, local dashboards, private wireless indicators, and degraded-mode events.

13.4.5.2 Edge Signals shall be governed by source records, data class, geospatial sensitivity, cyber sensitivity, infrastructure sensitivity, privacy, community safeguards, Indigenous protocols where applicable, public authority sensitivity, AI-use labels where applicable, public-safe review, correction pathway, and archive rule.

13.4.5.3 Edge Signals shall not create surveillance authority, public warning, public authority decision, infrastructure command, deployment authorization, or execution.

### 13.4.6 Sensor Networks.

13.4.6.1 Sensor Networks shall support observability through physical, digital, environmental, infrastructure, geospatial, Earth observation, IoT, OT, IIoT, drone, robotics, edge, telecom, or community-sourced inputs where lawful and appropriate.

13.4.6.2 Sensor Network intelligence records shall include sensor purpose, steward, location class, calibration status where applicable, data class, access class, privacy controls, geospatial controls, cyber controls, public-safe output rules, public authority dependencies, community safeguards, Indigenous protocol controls where applicable, correction pathway, and archive rule.

13.4.6.3 Sensor Networks shall not create surveillance authority, official monitoring authority, public warning authority, community consent, public authority approval, operational command, deployment authorization, or execution.

### 13.4.7 Geospatial Signals.

13.4.7.1 Geospatial Signals shall include spatial data, location-based indicators, maps, polygons, rasters, routes, corridors, hotspots, sensor locations, infrastructure locations, community locations, protected locations, hazard zones, environmental data, and geospatial analytics outputs.

13.4.7.2 Geospatial Signals shall be reviewed for sensitive infrastructure, protected species, sacred sites, protected knowledge, community-sensitive locations, Indigenous protocol-sensitive locations where applicable, security-sensitive locations, private locations, public authority-sensitive locations, and dual-use risk.

13.4.7.3 Geospatial public outputs shall use masking, generalization, aggregation, delay, suppression, restricted access, or public-safe map publishing where needed.

13.4.7.4 Geospatial Signals shall not create official maps, land-use determinations, public warnings, surveillance authority, public authority decisions, deployment authorizations, or execution.

### 13.4.8 Earth Observation Signals.

13.4.8.1 Earth Observation Signals shall include satellite, aerial, remote sensing, environmental monitoring, climate, land, water, vegetation, infrastructure, disaster-impact, biodiversity, and other remotely sensed data relevant to NAF intelligence work.

13.4.8.2 Earth Observation Signals shall be governed by source licensing, resolution limits, geospatial sensitivity, public-safe transformation, uncertainty, confidence, method review, public authority boundaries, community safeguards, Indigenous protocol-sensitive controls where applicable, and correction pathways.

13.4.8.3 Earth Observation Signals shall not be official maps, public warnings, land-use approvals, environmental certifications, public authority decisions, insurance scores, investment signals, deployment authorizations, or execution.

### 13.4.9 Digital Twin Needs.

13.4.9.1 Digital Twin Needs shall record where a scenario, system, infrastructure, WFEH-B context, disaster-risk context, public authority learning context, readiness-room context, or Nexus Universe demonstration may require a digital twin or simulation model.

13.4.9.2 Digital Twin Needs shall identify data requirements, model requirements, compute requirements, uncertainty, assumptions, public-safe constraints, geospatial sensitivity, cyber sensitivity, infrastructure sensitivity, public authority dependencies, safeguard issues, review requirements, correction pathway, and archive rule.

13.4.9.3 Digital Twin Needs shall not authorize digital twin deployment, operational control, infrastructure command, public authority decision, financeability, procurement status, or execution.

### 13.4.10 Degraded-Mode Awareness.

13.4.10.1 Degraded-Mode Awareness shall record how intelligence workflows operate when data, connectivity, compute, sensors, dashboards, AI systems, Observatory Nodes, Studio environments, or public authority learning rooms are degraded, unavailable, partial, delayed, or uncertain.

13.4.10.2 Degraded-Mode Awareness records shall identify what remains usable, what is suspended, what is read-only, what requires manual review, what data is stale, what confidence is reduced, what public-safe limitations apply, what AI use is suspended, what handoff pathways are paused, and what correction may be required.

13.4.10.3 Degraded-mode outputs shall not overstate confidence, completeness, warning status, readiness, public authority relevance, finance-readiness, procurement relevance, deployment status, or execution readiness.

### 13.4.11 Public-Safe Observatory Outputs.

13.4.11.1 Public-Safe Observatory Outputs shall be Observatory-derived summaries, dashboards, maps, indicators, reports, visuals, narratives, alerts for internal learning, public-safe signal briefs, or National Portfolio inputs that have been reviewed for public-safe release or controlled sharing.

13.4.11.2 Public-Safe Observatory Outputs shall carry source scope, method notes, confidence labels, uncertainty labels, sensitivity transformations, no-warning notices, no-rating notices, no-public-authority notices, no-finance notices, no-procurement notices, no-consent notices, no-deployment notices, no-execution notices, correction pathway, and archive rule.

13.4.11.3 Public-Safe Observatory Outputs shall not be public warnings, emergency alerts, official forecasts, public authority decisions, surveillance outputs, insurance scores, investment signals, procurement guidance, deployment authorizations, or execution instructions.

## 13.5 Scenario and Simulation Role

### 13.5.1 Scenario Learning.

13.5.1.1 Scenario Learning shall use structured narratives, data, models, assumptions, DRI indicators, GRIx terms, Observatory signals, Studio workflows, digital twins, expert input, National Portfolio records, Nexus Universe records, and public authority learning questions to explore possible futures, dependencies, risks, options, and uncertainties.

13.5.1.2 Scenario Learning shall support sensemaking, preparedness, risk literacy, systems thinking, public authority learning, Academy learning, Risk Academy learning, Foundry work, Campaign planning, Reports drafting, readiness-room discussion, capital-reader learning, insurance-reader learning, donor-reader learning, and lawful handoff dependency identification.

13.5.1.3 Scenario Learning shall not be forecast certainty, public warning, official plan, public authority decision, finance decision, procurement decision, deployment authorization, or execution.

### 13.5.2 Simulation Evidence.

13.5.2.1 Simulation Evidence shall be evidence generated or supported through computational, mathematical, statistical, agent-based, system dynamics, digital twin, geospatial, climate, weather-related, hydrological, cyber-physical, infrastructure, WFEH-B, or AI-enabled simulation.

13.5.2.2 Simulation Evidence shall record model basis, data basis, assumptions, uncertainty, sensitivity, calibration where applicable, validation limits, scenario scope, computational environment, output review, public-safe status, correction pathway, and archive rule.

13.5.2.3 Simulation Evidence shall be bounded evidence only. It shall not be certification, official forecast, public warning, public authority decision, financeability, insurance approval, procurement readiness, deployment authorization, or execution.

### 13.5.3 Digital Twin Evidence.

13.5.3.1 Digital Twin Evidence shall be evidence derived from digital twin workflows, including scenario outputs, state estimates, stress tests, dependency maps, system behavior records, infrastructure context, WFEH-B context, disaster-risk context, and public authority learning context.

13.5.3.2 Digital Twin Evidence shall record source data, model assumptions, update cadence, digital twin scope, confidence, uncertainty, sensitivity, limitations, public-safe status, geospatial controls, cyber controls, infrastructure sensitivity, correction pathway, and archive rule.

13.5.3.3 Digital Twin Evidence shall not be operational control, official map, public warning, public authority decision, infrastructure command, certification, deployment authorization, or execution.

### 13.5.4 Stress Testing.

13.5.4.1 Stress Testing shall examine how systems, infrastructure, data workflows, AI systems, dashboards, DRI indicators, Observatory nodes, Studio workflows, National Portfolios, Nexus Universe environments, and handoff dependency packages perform under adverse, extreme, degraded, uncertain, or high-load conditions.

13.5.4.2 Stress Testing shall record test scope, assumptions, inputs, stressors, outputs, failure modes, limitations, confidence, uncertainty, correction actions, support implications, release implications, and archive rule.

13.5.4.3 Stress Testing shall not create certification, service warranty, public authority approval, financeability, insurance approval, procurement readiness, deployment authorization, or execution.

### 13.5.5 Red-Team Scenarios.

13.5.5.1 Red-Team Scenarios shall test intelligence workflows for misuse, overclaim, hallucination, data leakage, protected knowledge exposure, cyber-sensitive exposure, public authority overclaim, finance overclaim, procurement overclaim, consent overclaim, dashboard misuse, model misuse, scenario misuse, handoff overclaim, and execution overclaim.

13.5.5.2 Red-Team Scenarios may be open, public-safe, controlled, secure-room-only, or archive-only depending on sensitivity. Findings shall be recorded with mitigations, unresolved risks, release implications, correction actions, and archive rule.

13.5.5.3 Red-Team Scenarios shall not be operational instructions, exploit instructions, public warnings, official determinations, certification, or execution.

### 13.5.6 Drift Detection.

13.5.6.1 Drift Detection shall monitor whether data, indicators, models, dashboards, signals, scenarios, digital twins, AI workflows, public-safe summaries, risk categories, or National Portfolio intelligence become stale, misaligned, degraded, biased, inaccurate, or unsafe over time.

13.5.6.2 Drift Detection may trigger confidence change, uncertainty change, data refresh, method review, model review, dashboard review, public-safe review, safeguard review, Registry update, Marketplace update, Report correction, Grid correction, TRL correction, handoff recall, withdrawal, archive, or non-continuation.

13.5.6.3 Drift Detection shall not create surveillance authority, public warning authority, public authority decision, operational command, deployment authorization, or execution.

### 13.5.7 Model Limitations.

13.5.7.1 Model Limitations shall be recorded for every material model used in risk intelligence, including data limits, assumption limits, scope limits, geographic limits, temporal limits, language limits, population limits, hazard limits, system boundary limits, calibration limits, validation limits, uncertainty, bias, and failure modes.

13.5.7.2 Model Limitations shall be visible in Model Cards, System Cards, Benchmark Cards, Studio records, Reports, dashboards, Grid inputs, TRL notes, National Portfolio records, Nexus Universe outputs, and handoff dependency notes where material.

13.5.7.3 Model limitations shall prevent unsupported claims and shall not be suppressed to make intelligence appear more complete, certain, official, financeable, procurable, deployable, or executable.

### 13.5.8 Public Authority Learning Uses.

13.5.8.1 Public Authority Learning Uses shall allow public authorities and public authority-adjacent participants to review risk intelligence, DRI indicators, Observatory signals, dashboards, Studio scenarios, Reports, National Portfolio records, Nexus Universe outputs, and handoff dependencies for learning, capacity formation, policy literacy, systems-risk understanding, and resilience planning literacy.

13.5.8.2 Public Authority Learning Uses shall include no-decision notices, no-warning notices, no-procurement notices, no-public-finance-allocation notices, no-command notices, no-execution notices, data-use labels, AI-use labels, confidentiality controls where applicable, output review, correction pathway, and archive rule.

13.5.8.3 Public Authority Learning Uses shall not create public authority approval, official action, public warning, regulation, permit, license, emergency command, procurement decision, public finance allocation, deployment authorization, or execution.

### 13.5.9 Finance-Readiness Question Uses.

13.5.9.1 Finance-Readiness Question Uses shall allow risk intelligence to support capital-readability, insurance-readiness literacy, donor-readiness literacy, public finance relevance learning, assumptions registers, dependency registers, diligence-gap registers, protection-gap questions, risk-layering questions, readiness rooms, capital-reader rooms, insurance-reader rooms, and donor-reader rooms.

13.5.9.2 Finance-Readiness Question Uses shall be no-reliance, non-advisory, non-soliciting, non-transactional, no-underwriting, no-rating, no-financeability, no-insurability, competition-compliant, confidentiality-aware, and regulated-perimeter controlled.

13.5.9.3 Finance-Readiness Question Uses shall not create investment advice, offer, solicitation, transaction, underwriting, insurance approval, donor commitment, public finance allocation, rating, bankability, financeability, procurement status, public authority approval, deployment authorization, or execution.

### 13.5.10 No Certification by Simulation.

13.5.10.1 No simulation, scenario, model run, digital twin output, stress test, red-team scenario, benchmark, Studio demonstration, DRI dashboard, Observatory output, Grid input, TRL note, Nexus Universe demonstration, National Portfolio object, or handoff dependency package shall create certification by simulation.

13.5.10.2 Simulation may support bounded evidence, learning, readiness questions, public-safe reporting, and handoff dependency context. Certification, where applicable, must be separately issued by competent authority or recognized certifying processes outside NAF’s default posture.

## 13.6 Intelligence Review

### 13.6.1 Data Review.

13.6.1.1 Data Review shall assess data sources, data rights, data quality, metadata, lineage, completeness, bias, sensitivity, data-use labels, AI-use labels, public-safe status, data sovereignty, cross-border controls, retention, deletion, sealing, and archive.

13.6.1.2 Data Review shall be required for material intelligence outputs, including indicators, dashboards, Reports, Studio workflows, digital twins, National Portfolio intelligence, Nexus Universe outputs, Grid inputs, TRL notes, and handoff dependency packages.

13.6.1.3 Data Review shall not create unrestricted data rights, official data status, certification, public authority approval, financeability, procurement readiness, deployment authorization, or execution.

### 13.6.2 Method Review.

13.6.2.1 Method Review shall assess the methods used to create, transform, analyze, model, simulate, classify, summarize, visualize, or publish intelligence outputs.

13.6.2.2 Method Review shall consider method purpose, assumptions, limitations, reproducibility, uncertainty, confidence, bias, data fit, model fit, public-safe implications, safeguard implications, and correction pathways.

13.6.2.3 Method Review shall not create certification, standards conformance, public authority approval, financeability, procurement readiness, deployment authorization, or execution.

### 13.6.3 Indicator Review.

13.6.3.1 Indicator Review shall assess whether an indicator is clearly defined, properly sourced, methodologically bounded, useful within scope, public-safe, confidence-labeled where appropriate, uncertainty-labeled where appropriate, and correctionable.

13.6.3.2 Indicator Review shall consider whether the indicator could be misread as warning, rating, public authority decision, insurance score, investment signal, procurement score, or operational command, and shall apply boundary notices accordingly.

13.6.3.3 Indicator Review shall not make an indicator official, certified, rated, financeable, procurable, deployable, or executable.

### 13.6.4 Geospatial Sensitivity Review.

13.6.4.1 Geospatial Sensitivity Review shall assess whether intelligence outputs expose sensitive locations, critical infrastructure, protected species, sacred sites, protected knowledge, community-sensitive locations, Indigenous protocol-sensitive locations where applicable, private locations, security-sensitive locations, disaster-affected locations, or public authority-sensitive assets.

13.6.4.2 Geospatial Sensitivity Review may require masking, aggregation, generalization, delay, suppression, restricted access, metadata-only release, secure-room routing, or archive-only treatment.

13.6.4.3 Geospatial Review shall not create official maps, land-use approval, public warning, surveillance authority, public authority decision, deployment authorization, or execution.

### 13.6.5 Cyber Sensitivity Review.

13.6.5.1 Cyber Sensitivity Review shall assess whether intelligence outputs expose vulnerabilities, configurations, access pathways, critical infrastructure dependencies, cyber-physical weaknesses, exploit-adjacent information, security incidents, network diagrams, credentials, logs, or operationally sensitive cyber information.

13.6.5.2 Cyber Sensitivity Review may require redaction, restricted release, public-safe cyber summary, secure-room use, delayed disclosure, vulnerability disclosure process, or archive-only treatment.

13.6.5.3 Cyber Sensitivity Review shall not create security certification, operational instruction, public warning, public authority decision, deployment authorization, or execution.

### 13.6.6 Public-Safe Review.

13.6.6.1 Public-Safe Review shall assess whether an intelligence output may be released, displayed, cited, listed, published, taught, presented, or handed off without unsafe disclosure, overclaim, panic, misinterpretation, protected knowledge exposure, sensitive data exposure, public authority boundary breach, finance boundary breach, procurement boundary breach, consent overclaim, deployment overclaim, or execution overclaim.

13.6.6.2 Public-Safe Review shall apply no-warning, no-rating, no-approval, no-finance, no-procurement, no-certification, no-consent, no-deployment, and no-execution language where appropriate.

13.6.6.3 Public-Safe Review shall not make an output official, certified, financeable, procurable, approved, deployable, or executable.

### 13.6.7 Public Authority Boundary Review.

13.6.7.1 Public Authority Boundary Review shall assess whether an intelligence output could be mistaken for official action, public warning, emergency command, public finance allocation, regulation, permit, license, procurement decision, public health decision, official statistics, official map, public record, or public authority approval.

13.6.7.2 Public Authority Boundary Review shall require no-decision notices, no-warning notices, role-separation records, public authority learning labels, escalation to competent public authority where appropriate, and correction where overclaim occurs.

13.6.7.3 Public Authority Boundary Review shall not create public authority action. It prevents public authority overclaim.

### 13.6.8 Finance and Insurance Boundary Review.

13.6.8.1 Finance and Insurance Boundary Review shall assess whether an intelligence output could be misread as investment advice, financeability, bankability, valuation, rating, insurance score, underwriting view, premium indication, donor commitment, public finance allocation, or transaction support.

13.6.8.2 Finance and Insurance Boundary Review shall apply no-reliance, non-advisory, non-soliciting, non-transactional, no-underwriting, no-rating, no-financeability, no-insurability, no-public-finance-allocation, and no-donor-commitment notices where needed.

13.6.8.3 Finance and Insurance Boundary Review shall not create finance, insurance, donation, public finance, rating, or transaction readiness.

### 13.6.9 Safeguard Review.

13.6.9.1 Safeguard Review shall assess community impact, Indigenous protocol sensitivity where applicable, protected knowledge, youth safeguards, disability inclusion, accessibility, humanitarian sensitivity, non-extractive engagement, privacy, rights, equity, public-interest participation, and community-facing correction.

13.6.9.2 Safeguard Review may require restricted access, protected knowledge exclusion, community-facing summary, accessibility transformation, translation, consent-boundary notice, Indigenous protocol routing where applicable, withdrawal, sealing, or archive.

13.6.9.3 Safeguard Review shall not create community consent, Indigenous consent where applicable, approval, deployment authorization, or execution.

### 13.6.10 Correction Review.

13.6.10.1 Correction Review shall assess whether intelligence outputs require correction, addendum, confidence change, uncertainty change, metadata correction, data correction, method correction, dashboard correction, public-safe correction, Registry update, Marketplace update, Report correction, Studio restriction, Grid correction, TRL correction, Nexus Universe correction, National Portfolio correction, handoff recall, withdrawal, archive, or non-continuation.

13.6.10.2 Correction Review shall be triggered by error, misclassification, outdated data, drift, source withdrawal, rights issue, public-safe issue, safeguard issue, public authority overclaim, finance overclaim, procurement overclaim, consent overclaim, deployment overclaim, execution overclaim, incident, or external correction request.

13.6.10.3 Correction Review shall preserve trust and shall be treated as a normal governance function, not an exceptional failure.

## 13.7 Risk Intelligence Boundaries

### 13.7.1 Intelligence Is Not Warning.

13.7.1.1 Intelligence produced, reviewed, displayed, published, listed, recorded, routed, presented, or handed off through NAF shall not constitute public warning, emergency alert, evacuation notice, official hazard notice, public health warning, cyber alert, infrastructure warning, or emergency command.

13.7.1.2 Public warnings, where required, must be issued by competent public authorities or authorized actors through lawful channels outside NAF’s default intelligence posture.

### 13.7.2 Indicator Is Not Rating.

13.7.2.1 An indicator, index, dashboard field, signal, hotspot record, cascade record, multi-hazard record, DRI output, Grid input, TRL note, National Portfolio object, or Nexus Universe intelligence output shall not be treated as a rating, score, grade, certification, insurance score, investment score, procurement score, country ranking, provider validation, community ranking, or public authority assessment unless separately and lawfully established outside NAF.

13.7.2.2 Indicators shall remain bounded evidence and learning tools with recorded source, method, confidence, uncertainty, limitations, correction pathway, and archive rule.

### 13.7.3 Dashboard Is Not Decision.

13.7.3.1 A dashboard shall display information, context, trends, indicators, signals, maps, scenarios, records, or summaries; it shall not make decisions, issue commands, approve projects, certify readiness, allocate finance, approve insurance, recommend procurement, issue public warnings, grant consent, authorize deployment, or execute action.

13.7.3.2 Dashboard users remain responsible for independent review, lawful authority, role separation, and downstream diligence.

### 13.7.4 Scenario Is Not Forecast Certainty.

13.7.4.1 A scenario shall be a structured learning object, not a prediction of certainty. It may explore plausible futures, stress conditions, options, uncertainties, dependencies, and risks, but shall not be represented as forecast certainty, official forecast, public warning, investment basis, insurance basis, procurement basis, deployment basis, or execution basis.

13.7.4.2 Scenario outputs shall carry assumptions, limitations, uncertainty, confidence where appropriate, public-safe notes, and correction pathways.

### 13.7.5 Observatory Signal Is Not Surveillance Authority.

13.7.5.1 Observatory signals, sensor inputs, edge signals, geospatial signals, Earth observation signals, dashboards, data feeds, and digital twin inputs shall not create surveillance authority, monitoring mandate, law enforcement authority, public authority control, community consent, Indigenous consent where applicable, infrastructure access, or operational command.

13.7.5.2 Any monitoring, surveillance, public authority use, community use, Indigenous knowledge use where applicable, or infrastructure access requiring lawful authority shall be separately authorized outside NAF’s default Observatory posture.

### 13.7.6 GRIx Category Is Not Legal Classification.

13.7.6.1 A GRIx category, taxonomy, controlled vocabulary term, mapping, ontology relationship, semantic profile, or knowledge graph relationship shall not be treated as legal classification, regulatory determination, standards conformance, public authority classification, insurance classification, investment classification, procurement classification, consent determination, deployment authorization, or execution authority.

13.7.6.2 GRIx structures meaning for NAF records; competent legal, regulatory, public authority, standards, finance, insurance, procurement, community, Indigenous where applicable, and implementation decisions must be made separately by competent actors.

### 13.7.7 DRI Output Is Not Insurance Score or Investment Signal.

13.7.7.1 No DRI indicator, DRI dashboard, hotspot record, cascade record, multi-hazard record, protection-gap question, risk-layering question, public-safe intelligence summary, National DRI contribution, Nexus Universe DRI output, National Portfolio DRI record, Grid input, TRL note, or handoff dependency note shall be treated as an insurance score, underwriting view, premium indication, investment signal, rating, valuation, bankability finding, financeability finding, donor commitment, public finance allocation, or procurement signal.

13.7.7.2 Capital readers, insurers, reinsurers, donors, public finance readers, procurement bodies, public authorities, National Consortium Companies, Project SPVs, providers, operators, and other lawful actors must conduct separate independent diligence and decision processes outside NAF’s default intelligence posture.

13.7.7.3 The final intelligence rule of Part XIII is that NAF may structure, observe, analyze, simulate, summarize, publish, display, route, correct, archive, and hand off risk intelligence only through governed meaning, recorded sources, controlled vocabularies, indicators, confidence labels, uncertainty labels, public-safe summaries, Observatory records, Studio controls, Reports controls, Registry status, Marketplace discovery, Grid and TRL evidence limits, safeguard review, public authority boundary review, finance and insurance boundary review, correctionability, and no-conversion discipline. No GRIx category, DRI indicator, Observatory signal, dashboard, hotspot, cascade record, multi-hazard record, scenario, simulation, digital twin, Report, Registry record, Marketplace listing, Grid input, TRL note, Nexus Universe output, National Portfolio object, public authority learning record, capital-reader room record, insurance-reader room record, donor-reader room record, or handoff dependency package shall become public warning, rating, certification, legal classification, public authority action, financeability, insurability, procurement readiness, investment signal, insurance score, consent, deployment authorization, operational command, agency, employment, or execution 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/nexus-agile-framework-naf/xiii.-intelligence.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.