> For the complete documentation index, see [llms.txt](https://docs.therisk.global/organization/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.therisk.global/organization/acceleration/nexus-campaigns/vii.-interfaces.md). # VII. Interfaces ## 7.1 Multilateral Interface Model ### 7.1.0 Status, Purpose, and Governing Effect 7.1.0.1 This Section establishes the Multilateral Interface Model as the Nexus architecture through which Nexus records, technical-readiness records, public-safe reports, finance-readiness notes, insurance-readiness questions, public authority learning records, community safeguard records, Nexus Core outputs, Nexus Network records, Nexus Universe materials, and Nexus Rails continuation records may interface with multilateral institutions, public authorities, development actors, finance-facing actors, insurance-facing actors, standards bodies, research institutions, civil society organizations, community-facing organizations, philanthropic institutions, and private-sector technical partners without replacing their mandates. 7.1.0.2 The Multilateral Interface Model shall support lawful cooperation, technical learning, public-good readiness, risk-to-program translation, policy-learning records, development-finance readiness, public finance readability, protection-gap intelligence, standards-learning records, data safeguard records, verification records, and lawful handoff pathways. 7.1.0.3 The Multilateral Interface Model shall not be treated as a United Nations mandate, humanitarian mandate, development bank mandate, public finance approval, IMF assessment, sovereign credit view, public authority approval, government endorsement, procurement approval, regulatory approval, investment advice, underwriting, certification, social license, community consent, Indigenous consent, official representation, or implementation authority. 7.1.0.4 Nexus may support multilateral and institutional actors by making risk records more coherent, evidence-bounded, technically reviewable, public-safe, finance-readable, insurance-relevant, correction-ready, and lawfully continuable. Nexus shall not substitute itself for the mandates, governance, legal status, accountability, decision procedures, financial authority, operational authority, or public authority of those actors. 7.1.0.5 All interface activity shall remain role-separated, mandate-bounded, public-safe, data-governed, conflict-aware, competition-safe, correction-ready, and continued through Nexus Rails where material. 7.1.0.6 The governing rule of this Section is: **Nexus may interface with multilateral and institutional systems by record. Nexus does not replace their mandates, decisions, authority, finance, procurement, operations, or accountability.** ### 7.1.1 Interface Without Replacement 7.1.1.1 Interface Without Replacement shall mean that Nexus may connect records, evidence, methods, technical-readiness outputs, finance-readiness notes, public-safe reports, policy-learning records, and lawful handoff materials to competent institutions without becoming those institutions or displacing their mandates. 7.1.1.2 Interface activity may include:\ a. technical briefing;\ b. public-safe record sharing;\ c. policy-learning discussion;\ d. standards-learning discussion;\ e. development-finance readiness discussion;\ f. public finance readability discussion;\ g. insurance-readiness discussion;\ h. protection-gap discussion;\ i. data-governance coordination;\ j. scenario and stress-testing review;\ k. Nexus Core or Nexus Network demonstration;\ l. lawful handoff. 7.1.1.3 Every interface record shall identify:\ a. institution or actor category;\ b. interface purpose;\ c. records shared;\ d. mandate boundary;\ e. decision-use label;\ f. public-safe label;\ g. confidentiality and data limits;\ h. prohibited interpretations;\ i. correction pathway;\ j. Nexus Rails continuation status. 7.1.1.4 Interface shall not imply endorsement, approval, adoption, official consultation, procurement readiness, financeability, insurability, certification, consent, or implementation authority unless separately and lawfully documented. 7.1.1.5 The constitutional rule shall be: **Interface connects the record to competent actors. It does not replace competent actors.** ### 7.1.2 United Nations Entities 7.1.2.1 Nexus may interface with United Nations entities where Nexus records can support public-safe learning, technical readiness, resilience understanding, risk observability, data governance, scenario analysis, policy learning, development coordination, or lawful handoff. 7.1.2.2 Interface with United Nations entities may involve climate risk, disaster risk, water security, food systems, health systems, biodiversity, displacement, humanitarian risk, urban resilience, digital public infrastructure, AI and cyber risk, public finance exposure, and resilience programming. 7.1.2.3 United Nations Interface Records shall identify:\ a. United Nations entity or actor category;\ b. interface purpose;\ c. records shared or reviewed;\ d. mandate boundary;\ e. official-status boundary;\ f. public-safe language controls;\ g. data and confidentiality conditions;\ h. correction pathway;\ i. continuation status. 7.1.2.4 Interface with a United Nations entity shall not imply United Nations endorsement, mandate, adoption, official finding, procurement approval, funding approval, humanitarian mandate, development mandate, public authority approval, or implementation authorization unless separately and lawfully established. 7.1.2.5 The constitutional rule shall be: **Nexus may support United Nations learning by record. It shall not claim United Nations status, mandate, endorsement, or authority by proximity.** ### 7.1.3 Humanitarian Coordination Actors 7.1.3.1 Nexus may interface with humanitarian coordination actors where public-safe records, risk signals, displacement scenarios, protection-sensitive data controls, community safeguard records, infrastructure dependency records, health-system stress records, or disaster risk records can support lawful humanitarian learning or handoff. 7.1.3.2 Humanitarian interface activity shall preserve humanitarian principles, protection sensitivity, personal data safeguards, conflict sensitivity, consent boundaries, public authority boundaries, and public-safe language. 7.1.3.3 Humanitarian Interface Records shall identify:\ a. humanitarian actor category;\ b. interface purpose;\ c. protection-sensitive records;\ d. data restrictions;\ e. conflict-sensitive conditions;\ f. humanitarian mandate boundary;\ g. public-safe reporting limits;\ h. correction pathway;\ i. handoff or continuation status. 7.1.3.4 Nexus shall not determine humanitarian need, allocate aid, command humanitarian operations, represent affected populations, grant consent, determine displacement status, issue public warnings, or implement humanitarian response. 7.1.3.5 The constitutional rule shall be: **Humanitarian interface must protect people first and never convert Nexus records into humanitarian command or aid allocation.** ### 7.1.4 Development Agencies 7.1.4.1 Nexus may interface with development agencies where Nexus records can support resilience learning, national portfolio readability, programmatic resilience records, development-finance readiness, public finance readability, technical-readiness questions, safeguard learning, and lawful handoff. 7.1.4.2 Development Agency Interface Records shall identify:\ a. development actor category;\ b. interface purpose;\ c. source records;\ d. development relevance;\ e. safeguard status;\ f. public authority boundary;\ g. procurement boundary;\ h. finance-readiness boundary;\ i. decision-use label;\ j. correction pathway;\ k. continuation status. 7.1.4.3 Interface with development agencies shall not imply development approval, grant approval, loan approval, technical assistance mandate, procurement approval, public authority approval, financeability, implementation authorization, or donor endorsement. 7.1.4.4 Nexus shall not replace development agency appraisal, safeguards review, procurement procedures, country partnership processes, funding approval, supervision, or accountability systems. 7.1.4.5 The constitutional rule shall be: **Development interface prepares records for development learning. It does not approve development programs or finance.** ### 7.1.5 World Bank Group 7.1.5.1 Nexus may interface with World Bank Group actors where Nexus records can support public-safe learning on resilience, climate risk, disaster risk, infrastructure exposure, water-energy-food-health-biodiversity dependencies, public finance exposure, development-finance readiness, technical-readiness questions, and lawful handoff. 7.1.5.2 World Bank Group Interface Records shall identify:\ a. relevant actor or actor category;\ b. interface purpose;\ c. records shared;\ d. country or regional relevance;\ e. safeguard relevance;\ f. public finance readability relevance;\ g. procurement boundary;\ h. finance-readiness boundary;\ i. official-status boundary;\ j. correction pathway;\ k. Nexus Rails continuation. 7.1.5.3 Interface with World Bank Group actors shall not imply World Bank Group endorsement, appraisal, approval, financing, procurement approval, safeguard clearance, country ownership, public authority approval, project approval, implementation authority, or financeability. 7.1.5.4 Nexus shall not replace World Bank Group country engagement, project preparation, appraisal, safeguards, procurement, financing, supervision, or governance procedures. 7.1.5.5 The constitutional rule shall be: **Nexus may make resilience records readable to World Bank Group pathways. It does not become World Bank Group appraisal, approval, or finance.** ### 7.1.6 International Monetary Fund Interface Boundaries 7.1.6.1 Nexus may interface with International Monetary Fund-facing contexts only through bounded public finance readability, sovereign risk context, fiscal exposure learning, climate and disaster fiscal stress records, resilience investment readability, and policy-learning records. 7.1.6.2 IMF Interface Boundary Records shall identify:\ a. public finance question;\ b. sovereign or macro-fiscal context where relevant;\ c. source records;\ d. evidence basis;\ e. uncertainty;\ f. no-rating boundary;\ g. no-fiscal-advice boundary;\ h. no-policy-conditionality boundary;\ i. official-status boundary;\ j. correction pathway;\ k. continuation status. 7.1.6.3 Nexus shall not issue IMF assessments, macroeconomic surveillance findings, fiscal advice, debt advice, sovereign credit views, conditionality advice, public finance approval, monetary policy advice, or official country judgments. 7.1.6.4 Interface with IMF-facing actors shall not imply IMF endorsement, adoption, approval, surveillance finding, financing, public authority approval, or sovereign financeability. 7.1.6.5 The constitutional rule shall be: **IMF-facing interface may make fiscal risk readable. It shall not become macroeconomic assessment, fiscal advice, or sovereign judgment.** ### 7.1.7 Regional Development Banks 7.1.7.1 Nexus may interface with regional development banks where regional portfolio records, cross-border dependency records, infrastructure resilience records, climate adaptation records, disaster risk records, public finance readability records, and development-finance readiness records may support lawful downstream learning or handoff. 7.1.7.2 Regional Development Bank Interface Records shall identify:\ a. regional development bank actor category;\ b. regional or national pathway;\ c. source records;\ d. development relevance;\ e. public authority boundaries;\ f. safeguard relevance;\ g. procurement boundary;\ h. finance-readiness boundary;\ i. regional federation boundary;\ j. correction pathway;\ k. continuation status. 7.1.7.3 Interface with regional development banks shall not imply bank endorsement, appraisal, approval, financing, guarantee, procurement approval, safeguard clearance, public authority approval, country approval, financeability, or implementation authorization. 7.1.7.4 Nexus shall not replace regional development bank mandates, country processes, appraisal processes, safeguards, procurement, financing, supervision, or accountability systems. 7.1.7.5 The constitutional rule shall be: **Regional development bank interface connects regional readiness records to lawful finance-facing learning without approving finance.** ### 7.1.8 National Development Banks 7.1.8.1 Nexus may interface with national development banks where national portfolio records, infrastructure risk records, public finance readability records, climate finance readiness records, disaster risk finance readiness records, and programmatic resilience records may support lawful national learning. 7.1.8.2 National Development Bank Interface Records shall identify:\ a. national pathway;\ b. development bank actor category;\ c. source records;\ d. public authority boundary;\ e. public finance boundary;\ f. procurement boundary;\ g. no-financeability status;\ h. no-bankability status;\ i. diligence gaps;\ j. correction pathway;\ k. continuation status. 7.1.8.3 Interface with national development banks shall not imply national development bank approval, financing, guarantee, credit decision, public finance approval, procurement approval, government endorsement, financeability, bankability, or implementation authority. 7.1.8.4 The constitutional rule shall be: **National development bank interface prepares records for lawful review. It does not approve national development finance.** ### 7.1.9 Infrastructure Investors 7.1.9.1 Nexus may interface with infrastructure investors only through product-neutral, non-advisory, no-offer, no-allocation, no-financeability, no-false-capital-signal records. 7.1.9.2 Infrastructure Investor Interface Records shall identify:\ a. infrastructure theme;\ b. source records;\ c. evidence status;\ d. technical-readiness status;\ e. public authority boundary;\ f. procurement boundary;\ g. community consent boundary;\ h. no-advice status;\ i. no-offer status;\ j. no-financeability status;\ k. diligence gaps;\ l. correction pathway. 7.1.9.3 Nexus shall not provide investment advice, financial promotion, securities offering, deal sourcing, capital raising, valuation, lending approval, capital allocation, infrastructure project approval, procurement approval, bankability determination, financeability determination, or implementation authority. 7.1.9.4 Infrastructure investors shall make their own decisions under their own mandates, procedures, duties, approvals, regulatory obligations, and risk responsibilities. 7.1.9.5 The constitutional rule shall be: **Infrastructure investor interface makes records readable. It does not invite or approve investment.** ### 7.1.10 Sovereign Wealth Funds 7.1.10.1 Nexus may interface with sovereign wealth funds only through product-neutral, non-advisory, no-offer, no-allocation, no-financeability, and no-sovereign-endorsement records. 7.1.10.2 Sovereign Wealth Fund Interface Records shall identify:\ a. resilience theme;\ b. source records;\ c. public finance boundary;\ d. public authority boundary;\ e. investment-advice boundary;\ f. sovereign endorsement boundary;\ g. procurement boundary;\ h. diligence gaps;\ i. no-false-capital-signal controls;\ j. correction pathway;\ k. continuation status. 7.1.10.3 Interface with sovereign wealth funds shall not imply sovereign endorsement, investment approval, mandate fit, allocation approval, public investment approval, financeability, guarantee, rating, procurement approval, or implementation authority. 7.1.10.4 The constitutional rule shall be: **Sovereign wealth fund interface supports resilience readability without advising sovereign capital.** ### 7.1.11 Public Finance Institutions 7.1.11.1 Nexus may interface with public finance institutions where public finance exposure records, fiscal stress scenarios, public asset exposure maps, development-finance readiness records, climate finance readiness records, disaster risk finance readiness records, and lawful handoff records support public finance learning. 7.1.11.2 Public Finance Institution Interface Records shall identify:\ a. public finance question;\ b. source records;\ c. evidence status;\ d. public authority boundary;\ e. budget authority boundary;\ f. fiscal advice boundary;\ g. procurement boundary;\ h. no-public-finance-approval status;\ i. correction pathway;\ j. continuation status. 7.1.11.3 Nexus shall not provide fiscal advice, budget advice, debt advice, tax advice, public finance approval, appropriation decision, procurement approval, financeability determination, or implementation authorization. 7.1.11.4 Interface with public finance institutions shall not imply funding approval, budget approval, fiscal endorsement, public authority adoption, or public finance readiness beyond the record. 7.1.11.5 The constitutional rule shall be: **Public finance interface makes exposure readable. It does not decide public finance.** ### 7.1.12 Climate Finance Platforms 7.1.12.1 Nexus may interface with climate finance platforms where climate risk records, adaptation records, mitigation-adjacent resilience records, public finance exposure records, climate finance readiness records, evidence gaps, safeguard records, and lawful handoff conditions support bounded learning. 7.1.12.2 Climate Finance Platform Interface Records shall identify:\ a. climate finance question;\ b. source records;\ c. climate evidence basis;\ d. scenario assumptions where applicable;\ e. safeguard status;\ f. public authority boundary;\ g. finance-readiness boundary;\ h. no-climate-finance-approval status;\ i. no-carbon-market-approval status;\ j. correction pathway;\ k. continuation status. 7.1.12.3 Interface with climate finance platforms shall not imply climate finance eligibility, grant approval, loan approval, carbon credit approval, adaptation finance approval, public finance approval, investment advice, financeability, insurability, or implementation authorization. 7.1.12.4 The constitutional rule shall be: **Climate finance interface prepares climate-risk records for review. It does not approve climate finance.** ### 7.1.13 Disaster Risk Finance Actors 7.1.13.1 Nexus may interface with disaster risk finance actors where disaster exposure records, fiscal stress records, protection-gap intelligence, public asset exposure records, household vulnerability records, infrastructure exposure records, disaster risk finance readiness records, and lawful handoff conditions support bounded learning. 7.1.13.2 Disaster Risk Finance Interface Records shall identify:\ a. disaster risk finance question;\ b. source records;\ c. exposure status;\ d. data gaps;\ e. public finance relevance;\ f. insurance-readiness boundary;\ g. no-underwriting boundary;\ h. no-financeability boundary;\ i. public authority boundary;\ j. correction pathway;\ k. continuation status. 7.1.13.3 Interface with disaster risk finance actors shall not imply contingency finance approval, parametric insurance approval, catastrophe bond approval, public finance approval, underwriting, pricing, coverage, financeability, insurability, or implementation authority. 7.1.13.4 The constitutional rule shall be: **Disaster risk finance interface organizes readiness questions without financing or underwriting disaster risk.** ### 7.1.14 Insurance and Reinsurance Markets 7.1.14.1 Nexus may interface with insurance and reinsurance markets only through insurance-readiness questions, protection-gap intelligence, exposure records, data-quality questions, resilience measure descriptions, disaster risk finance readiness records, public-safe summaries, and market-conduct-safe learning. 7.1.14.2 Insurance and Reinsurance Interface Records shall identify:\ a. exposure category;\ b. protection-gap signal;\ c. data status;\ d. evidence gaps;\ e. resilience relevance;\ f. market-conduct boundary;\ g. no-underwriting boundary;\ h. no-pricing boundary;\ i. no-coverage boundary;\ j. no-placement boundary;\ k. correction pathway;\ l. continuation status. 7.1.14.3 Nexus shall not underwrite, price, place, broker, reinsure, determine claims, approve coverage, determine insurability, provide insurance advice, or coordinate market conduct. 7.1.14.4 Insurance and reinsurance actors shall make their own decisions under their own licenses, regulations, underwriting methods, actuarial duties, market conduct rules, governance, and risk responsibilities. 7.1.14.5 The constitutional rule shall be: **Insurance-market interface frames exposure questions. It does not underwrite, price, place, or approve coverage.** ### 7.1.15 Standards Bodies 7.1.15.1 Nexus may interface with standards bodies where risk records, technical-readiness records, verification records, data governance records, AI governance records, public-safe reporting records, interoperability records, or Nexus Network federation rules may support standards learning. 7.1.15.2 Standards Body Interface Records shall identify:\ a. standards topic;\ b. source records;\ c. technical relevance;\ d. verification relevance;\ e. standards-learning purpose;\ f. public authority boundary;\ g. certification boundary;\ h. conformance boundary;\ i. correction pathway;\ j. continuation status. 7.1.15.3 Interface with standards bodies shall not imply standard adoption, conformance, certification, accreditation, public authority approval, regulatory approval, procurement approval, or implementation authority. 7.1.15.4 Nexus shall not claim standards authority, certification authority, accreditation authority, or conformance authority unless separately and lawfully established. 7.1.15.5 The constitutional rule shall be: **Standards interface supports standards learning. It does not certify conformance.** ### 7.1.16 Universities and Research Networks 7.1.16.1 Nexus may interface with universities and research networks where research, evidence, methods, data science, AI, climate science, engineering, public health, social science, law, finance-readiness, insurance-readiness, and systems-risk learning can strengthen Nexus records. 7.1.16.2 University and Research Network Interface Records shall identify:\ a. research actor or network category;\ b. purpose;\ c. source records;\ d. research boundary;\ e. data access conditions;\ f. ethics and privacy conditions where applicable;\ g. publication boundary;\ h. intellectual property boundary;\ i. public-safe language controls;\ j. correction pathway;\ k. continuation status. 7.1.16.3 Interface with research institutions shall not imply research endorsement, peer review, ethics approval, institutional approval, certification, public authority approval, procurement approval, financeability, insurability, or implementation authorization. 7.1.16.4 Research collaboration shall preserve data rights, ethical review requirements, publication controls, public-safe language, community safeguards, Indigenous knowledge safeguards, and lawful handoff conditions. 7.1.16.5 The constitutional rule shall be: **Research interface strengthens evidence where governed. It does not convert research proximity into validation.** ### 7.1.17 Public Authorities 7.1.17.1 Nexus may interface with public authorities where public authority learning, policy-learning records, public finance questions, mandate-readiness records, technical-readiness records, public-safe reports, or lawful handoff records are appropriate. 7.1.17.2 Public Authority Interface Records shall identify:\ a. competent actor where appropriate;\ b. interface purpose;\ c. mandate status;\ d. approval status;\ e. records shared or reviewed;\ f. public language boundary;\ g. confidentiality conditions;\ h. correction pathway;\ i. handoff or continuation status. 7.1.17.3 Interface with public authorities shall not imply public authority approval, government endorsement, official adoption, regulatory approval, procurement approval, public finance approval, official consultation, mandate, or implementation authorization unless separately and lawfully documented. 7.1.17.4 Nexus shall not represent a public authority unless a specific lawful authority exists and is documented within scope. 7.1.17.5 The constitutional rule shall be: **Public authority interface supports learning and handoff. It does not create approval by proximity.** ### 7.1.18 Ministries and Regulators 7.1.18.1 Nexus may interface with ministries and regulators where records can support policy learning, regulatory learning, mandate-readiness, public-safe technical reporting, risk governance gap analysis, data governance, AI governance, public finance readability, or lawful handoff. 7.1.18.2 Ministry and Regulator Interface Records shall identify:\ a. ministry or regulator category;\ b. interface purpose;\ c. records shared;\ d. mandate boundary;\ e. regulatory boundary;\ f. official-status boundary;\ g. confidentiality and data limits;\ h. public communication boundary;\ i. correction pathway;\ j. continuation status. 7.1.18.3 Interface with ministries and regulators shall not imply regulatory approval, policy adoption, public authority approval, official consultation, procurement approval, public finance approval, mandate, or implementation authorization unless separately and lawfully documented. 7.1.18.4 Nexus shall not provide legal determinations, regulatory determinations, enforcement decisions, permit approvals, or compliance findings. 7.1.18.5 The constitutional rule shall be: **Regulatory interface supports regulatory learning. It does not become regulatory decision-making.** ### 7.1.19 Cities and Regional Governments 7.1.19.1 Nexus may interface with cities and regional governments where urban risk records, climate adaptation records, infrastructure exposure records, public service continuity records, public finance exposure records, community safeguard records, and lawful handoff records support public-safe learning. 7.1.19.2 City and Regional Government Interface Records shall identify:\ a. city or regional actor category;\ b. interface purpose;\ c. records shared;\ d. public authority boundary;\ e. municipal or regional mandate status;\ f. public finance boundary;\ g. procurement boundary;\ h. community safeguard status;\ i. correction pathway;\ j. continuation status. 7.1.19.3 Interface with cities and regional governments shall not imply city approval, regional government approval, public budget approval, zoning approval, permitting approval, procurement approval, official adoption, financeability, insurability, or implementation authorization unless separately and lawfully documented. 7.1.19.4 The constitutional rule shall be: **City and regional government interface supports local and regional learning without becoming local or regional authority.** ### 7.1.20 Civil Society Organizations 7.1.20.1 Nexus may interface with civil society organizations where participation records, community safeguard records, public-safe reports, risk signals, policy-learning records, social trust records, public authority boundary records, and lawful handoff records may be strengthened. 7.1.20.2 Civil Society Interface Records shall identify:\ a. organization or actor category;\ b. participation purpose;\ c. records shared or contributed;\ d. representation boundary;\ e. consent boundary;\ f. public-safe language boundary;\ g. data and privacy conditions;\ h. conflict or advocacy disclosure where material;\ i. correction pathway;\ j. continuation status. 7.1.20.3 Interface with civil society organizations shall not imply civil society endorsement, community consent, social license, public authority approval, project approval, finance approval, procurement approval, or implementation authority. 7.1.20.4 Civil society participation shall not be used to claim representation of communities, affected people, or Indigenous peoples unless separately and lawfully documented. 7.1.20.5 The constitutional rule shall be: **Civil society interface strengthens participation records. It does not convert participation into representation or consent.** ### 7.1.21 Community-Facing Organizations 7.1.21.1 Nexus may interface with community-facing organizations where local risk knowledge, lived experience, safeguard concerns, participation records, public-safe summaries, benefit and risk distribution, and lawful handoff conditions may be strengthened. 7.1.21.2 Community-Facing Interface Records shall identify:\ a. organization or actor category;\ b. community-facing role;\ c. participation scope;\ d. consent boundary;\ e. privacy conditions;\ f. data and knowledge safeguards;\ g. public-safe reporting limits;\ h. unresolved issues;\ i. correction pathway;\ j. continuation status. 7.1.21.3 Interface with community-facing organizations shall not imply community consent, Indigenous consent, social license, public approval, project approval, finance approval, procurement approval, official representation, or implementation authority. 7.1.21.4 Community-facing interface shall protect vulnerable people, sensitive locations, local knowledge, Indigenous knowledge, personal data, and consent-sensitive information. 7.1.21.5 The constitutional rule shall be: **Community-facing interface protects participation from being misused as consent.** ### 7.1.22 Philanthropic Institutions 7.1.22.1 Nexus may interface with philanthropic institutions where public-good capacity, research support, technical infrastructure, community safeguards, education, open methods, Nexus Core preparation, Nexus Network capacity, Nexus Universe programming, or Nexus Rails continuation may be supported. 7.1.22.2 Philanthropic Interface Records shall identify:\ a. philanthropic actor category;\ b. support purpose;\ c. supported pathway or output;\ d. no-control status;\ e. no-endorsement status where applicable;\ f. no-procurement-advantage status;\ g. public-safe language boundary;\ h. conflict disclosure where material;\ i. correction pathway;\ j. continuation status. 7.1.22.3 Philanthropic support shall not control records, evidence, governance, public-safe reports, technical verification, public authority learning, community safeguard records, finance-readiness notes, Nexus Universe outputs, or Nexus Rails continuation. 7.1.22.4 Philanthropic interface shall not imply endorsement, public authority approval, development approval, procurement advantage, financeability, insurability, social license, consent, or implementation authority. 7.1.22.5 The constitutional rule shall be: **Philanthropic support may strengthen public-good capacity. It shall not control the record.** ### 7.1.23 Private-Sector Technical Partners 7.1.23.1 Nexus may interface with private-sector technical partners where technical capability, data systems, compute, AI, cyber ranges, simulation infrastructure, digital twins, secure data environments, geospatial analysis, dashboards, or critical application testing may support bounded Nexus records. 7.1.23.2 Private-Sector Technical Partner Interface Records shall identify:\ a. partner identity or category;\ b. capability contributed;\ c. technical role;\ d. data role;\ e. security obligations;\ f. provider boundary;\ g. no-endorsement status;\ h. no-procurement-approval status;\ i. no-preferred-supplier status;\ j. conflict disclosure;\ k. public-safe language boundary;\ l. correction pathway;\ m. continuation status. 7.1.23.3 Private-sector technical participation shall not imply technology approval, vendor endorsement, procurement approval, preferred supplier status, certification, financeability, insurability, public authority approval, or implementation authority. 7.1.23.4 Technical partners shall not control the Nexus record, public-safe reports, verification status, public authority learning records, sponsor recognition, finance-readiness records, or Nexus Rails continuation by virtue of technical contribution. 7.1.23.5 The constitutional rule shall be: **Private technical partners may support capability. They shall not receive approval or control by participation.** ### 7.1.24 Multilateral Use Without Mandate Substitution 7.1.24.1 Multilateral Use Without Mandate Substitution shall mean that multilateral, development, humanitarian, public finance, standards, research, civil society, philanthropic, or technical actors may use Nexus records only within their own mandates, governance, procedures, duties, legal frameworks, safeguards, and accountability structures. 7.1.24.2 Nexus records may support learning, evidence review, technical readiness, risk mapping, scenario analysis, finance-readiness, insurance-readiness, public authority learning, public-safe reporting, and lawful handoff. 7.1.24.3 Nexus records shall not substitute for:\ a. public authority mandates;\ b. multilateral mandates;\ c. humanitarian mandates;\ d. development bank appraisal;\ e. financing approval;\ f. regulatory approval;\ g. procurement approval;\ h. safeguards review;\ i. community consent;\ j. Indigenous consent;\ k. standards certification;\ l. professional assurance;\ m. implementation authorization. 7.1.24.4 Where a Nexus record is used by an external actor, the record’s status labels, decision-use labels, public-safe labels, evidence limits, data restrictions, correction history, and prohibited-use language shall remain attached where material. 7.1.24.5 The constitutional rule shall be: **Multilateral use may carry Nexus records into competent systems. It shall not make Nexus a substitute for those systems.** ### 7.1.25 Technical Interface Without Institutional Replacement 7.1.25.1 Technical Interface Without Institutional Replacement shall mean that Nexus may provide technical infrastructure, records, methods, verification receipts, data governance, simulations, digital twins, dashboards, public-safe reports, finance-readiness notes, and Nexus Rails continuation without replacing institutions that hold legal, public, financial, humanitarian, regulatory, technical, operational, or fiduciary responsibility. 7.1.25.2 Technical interface may support:\ a. evidence organization;\ b. risk observability;\ c. technical-readiness testing;\ d. secure data review;\ e. compute-to-data workflows;\ f. AI-assisted analysis;\ g. model-risk review;\ h. public-safe reporting;\ i. finance-readiness readability;\ j. insurance-readiness questioning;\ k. policy learning;\ l. standards learning;\ m. lawful handoff. 7.1.25.3 Technical interface shall preserve the rule that records may inform competent actors but shall not decide for them. 7.1.25.4 Technical interface shall not imply that Nexus becomes a government, regulator, development bank, humanitarian actor, insurer, reinsurer, investor, public finance institution, standards body, university, operator, procurement authority, community representative, Indigenous authority, or implementing agency. 7.1.25.5 The constitutional rule shall be: **Nexus provides technical interface by record. It does not replace the institutions that decide, finance, regulate, underwrite, consent, or implement.** ## 7.2 Multilateral and Development Partner Engagement Protocols ### 7.2.0 Status, Purpose, and Governing Effect 7.2.0.1 This Section establishes the Multilateral and Development Partner Engagement Protocols through which Nexus may engage United Nations entities, humanitarian coordination actors, development agencies, international financial institutions, regional and national development banks, sovereign wealth funds, infrastructure investors, insurance and reinsurance actors, public health institutions, food security institutions, water and sanitation institutions, energy transition institutions, biodiversity and nature institutions, city and local government actors, universities, research networks, civil society organizations, philanthropic institutions, and technical partners. 7.2.0.2 These Protocols shall govern engagement for public-safe learning, technical readiness, data governance, scenario and stress-testing, public authority learning, development-finance readiness, public finance readability, insurance-readiness questions, protection-gap intelligence, standards-learning, community safeguards, Nexus Core preparation, Nexus Network participation, Nexus Universe release, and Nexus Rails continuation. 7.2.0.3 Engagement shall not be treated as endorsement, approval, adoption, mandate, official consultation, public authority approval, procurement approval, regulatory approval, investment advice, underwriting, financeability, insurability, certification, social license, community consent, Indigenous consent, official representation, professional reliance, project approval, or implementation authorization unless separately and lawfully documented within scope. 7.2.0.4 Every engagement protocol under this Section shall require a clear engagement purpose, institution or actor category, role boundary, records shared, data controls, confidentiality controls, public-safe language, decision-use labels, prohibited-use language, correction pathway, and Nexus Rails continuation where material. 7.2.0.5 Engagement shall preserve institutional dignity and legal boundaries. Nexus may support partner understanding by record, but it shall not speak for partners, replace partners, imply partner approval, claim partner mandate, or convert engagement into authority. 7.2.0.6 The governing rule of this Section is: **Engagement connects Nexus records to competent institutions. Engagement does not create endorsement, mandate, approval, finance, underwriting, procurement, consent, or implementation authority.** ### 7.2.1 UN Entity Engagement Protocol 7.2.1.1 The UN Entity Engagement Protocol shall govern engagement with United Nations entities where Nexus records may support public-safe learning, technical readiness, risk observability, data governance, resilience programming, policy learning, public authority learning, or lawful handoff. 7.2.1.2 UN Entity Engagement Records shall identify:\ a. UN entity or actor category;\ b. engagement purpose;\ c. Nexus records shared or reviewed;\ d. mandate boundary;\ e. official-status boundary;\ f. data and confidentiality conditions;\ g. public-safe language controls;\ h. prohibited interpretations;\ i. correction pathway;\ j. Nexus Rails continuation status. 7.2.1.3 Engagement with a UN entity shall not imply UN endorsement, UN mandate, UN adoption, official UN finding, procurement approval, funding approval, humanitarian mandate, development mandate, public authority approval, country approval, or implementation authorization. 7.2.1.4 Nexus shall not use UN names, participation, meetings, correspondence, or proximity to imply formal relationship, approval, or mandate beyond the documented engagement record. 7.2.1.5 The constitutional rule shall be: **Engage UN entities by record. Do not claim UN status, mandate, endorsement, or authority by proximity.** ### 7.2.2 OCHA-Adjacent Humanitarian Interface Protocol 7.2.2.1 The OCHA-Adjacent Humanitarian Interface Protocol shall govern humanitarian coordination-facing engagement where risk records, disaster records, displacement records, health-system stress records, infrastructure dependency records, protection-sensitive data records, or community safeguard records may support public-safe learning or lawful handoff. 7.2.2.2 Humanitarian Interface Records shall identify:\ a. humanitarian actor category;\ b. engagement purpose;\ c. protection-sensitive records;\ d. data restrictions;\ e. conflict-sensitive conditions;\ f. humanitarian mandate boundary;\ g. public authority boundary;\ h. public-safe reporting limits;\ i. correction pathway;\ j. handoff or continuation status. 7.2.2.3 Humanitarian interface activity shall preserve humanitarian principles, protection sensitivity, personal data safeguards, conflict sensitivity, consent boundaries, public authority boundaries, and non-execution boundaries. 7.2.2.4 Nexus shall not determine humanitarian need, allocate aid, command humanitarian operations, represent affected populations, determine displacement status, issue public warnings, grant consent, or implement humanitarian response. 7.2.2.5 The constitutional rule shall be: **Humanitarian engagement must protect people first and never convert Nexus records into humanitarian command or aid allocation.** ### 7.2.3 UNDP Interface Protocol 7.2.3.1 The UNDP Interface Protocol shall govern engagement where Nexus records may support development learning, governance-risk learning, resilience programming, national portfolio readability, public finance exposure learning, digital public infrastructure learning, climate adaptation readiness, or lawful handoff. 7.2.3.2 UNDP Interface Records shall identify:\ a. engagement purpose;\ b. national or regional pathway;\ c. source records;\ d. development relevance;\ e. governance relevance;\ f. public authority boundary;\ g. procurement boundary;\ h. funding boundary;\ i. public-safe language controls;\ j. correction pathway;\ k. Nexus Rails continuation. 7.2.3.3 Engagement with UNDP-facing actors shall not imply UNDP endorsement, adoption, project approval, funding approval, procurement approval, country programme inclusion, public authority approval, implementation mandate, or development approval. 7.2.3.4 Nexus shall not replace development programme design, national ownership procedures, partner approval processes, safeguards review, procurement procedures, funding approval, or implementation accountability. 7.2.3.5 The constitutional rule shall be: **UNDP-facing engagement supports development learning. It does not approve development programming or implementation.** ### 7.2.4 UNEP Interface Protocol 7.2.4.1 The UNEP Interface Protocol shall govern engagement where Nexus records may support environmental learning, climate and nature risk records, biodiversity records, pollution risk records, ecosystem dependency records, environmental data governance, public-safe reporting, or lawful handoff. 7.2.4.2 UNEP Interface Records shall identify:\ a. environmental risk theme;\ b. source records;\ c. evidence status;\ d. data and ecosystem sensitivity;\ e. community and Indigenous knowledge safeguards;\ f. public authority boundary;\ g. environmental approval boundary;\ h. finance-readiness boundary;\ i. public-safe publication limits;\ j. correction pathway;\ k. continuation status. 7.2.4.3 Engagement with UNEP-facing actors shall not imply UNEP endorsement, environmental approval, policy adoption, environmental permitting, biodiversity validation, nature-finance validation, climate finance approval, public authority approval, or implementation authorization. 7.2.4.4 Environmental records shall not expose sensitive species, ecosystems, community knowledge, Indigenous knowledge, or location-sensitive ecological data where public disclosure could cause harm. 7.2.4.5 The constitutional rule shall be: **UNEP-facing engagement supports environmental learning without creating environmental approval or nature-finance validation.** ### 7.2.5 UNDRR Interface Protocol 7.2.5.1 The UNDRR Interface Protocol shall govern engagement where Nexus disaster risk records, multi-hazard scenarios, resilience records, critical infrastructure risk records, disaster risk finance readiness records, public-safe reports, or Nexus Rails continuation records may support disaster risk reduction learning. 7.2.5.2 UNDRR Interface Records shall identify:\ a. disaster risk reduction theme;\ b. source records;\ c. hazard and exposure records;\ d. evidence status;\ e. scenario assumptions where applicable;\ f. public authority boundary;\ g. emergency management boundary;\ h. public-safe reporting limit;\ i. correction pathway;\ j. continuation status. 7.2.5.3 Engagement with UNDRR-facing actors shall not imply UNDRR endorsement, official disaster risk assessment, public warning, emergency command, national DRR approval, finance approval, procurement approval, or implementation authority. 7.2.5.4 Nexus shall not replace official disaster risk governance, national emergency systems, public warning systems, or competent public authority procedures. 7.2.5.5 The constitutional rule shall be: **UNDRR-facing engagement strengthens disaster risk learning. It does not create disaster authority or response command.** ### 7.2.6 WHO Interface Protocol 7.2.6.1 The WHO Interface Protocol shall govern engagement where health risk records, public health signals, pandemic scenarios, biosecurity records, health-system surge scenarios, water and sanitation links, health data safeguards, or public-safe reports may support bounded public health learning. 7.2.6.2 WHO Interface Records shall identify:\ a. health theme;\ b. source records;\ c. public health authority boundary;\ d. clinical guidance boundary;\ e. health data sensitivity;\ f. privacy controls;\ g. biosecurity and dual-use controls;\ h. public-safe communication limits;\ i. correction pathway;\ j. lawful handoff status. 7.2.6.3 Engagement with WHO-facing actors shall not imply WHO endorsement, official health guidance, public health order, disease determination, biosurveillance authority, emergency declaration, health procurement approval, funding approval, or implementation authorization. 7.2.6.4 Nexus shall not provide medical advice, clinical guidance, public health orders, pathogen handling guidance, harmful biological instructions, or official health determinations. 7.2.6.5 The constitutional rule shall be: **WHO-facing engagement supports health readiness only where health authority, privacy, and biosecurity boundaries are protected.** ### 7.2.7 FAO Interface Protocol 7.2.7.1 The FAO Interface Protocol shall govern engagement where food-system risk records, agricultural risk records, water-food-energy-health-biodiversity scenarios, food corridor disruption scenarios, nutrition-related resilience records, biodiversity records, and food security public-safe summaries may support bounded learning. 7.2.7.2 FAO Interface Records shall identify:\ a. food or agriculture theme;\ b. source records;\ c. evidence status;\ d. data limitations;\ e. market-conduct boundary;\ f. trade-policy boundary;\ g. humanitarian sensitivity where applicable;\ h. public authority boundary;\ i. public-safe reporting limit;\ j. correction pathway;\ k. continuation status. 7.2.7.3 Engagement with FAO-facing actors shall not imply FAO endorsement, food security determination, agricultural policy approval, food allocation, trade decision, procurement approval, funding approval, public authority approval, or implementation authorization. 7.2.7.4 Nexus shall not allocate food, direct markets, approve suppliers, issue official food security determinations, or coordinate market conduct. 7.2.7.5 The constitutional rule shall be: **FAO-facing engagement may strengthen food-system learning. It shall not become food policy, food allocation, or market coordination.** ### 7.2.8 WMO Interface Protocol 7.2.8.1 The WMO Interface Protocol shall govern engagement where climate, weather, hydrometeorological, early-warning, disaster risk, water basin, heat, flood, drought, storm, geospatial, or public-safe scenario records may support bounded learning. 7.2.8.2 WMO Interface Records shall identify:\ a. weather, climate, or hydrometeorological theme;\ b. source records;\ c. data status;\ d. uncertainty;\ e. model or scenario assumptions;\ f. public authority boundary;\ g. official forecast boundary;\ h. public warning boundary;\ i. public-safe reporting limit;\ j. correction pathway;\ k. continuation status. 7.2.8.3 Engagement with WMO-facing actors shall not imply WMO endorsement, official forecast status, official warning status, meteorological authority, public authority approval, climate service certification, or implementation authorization. 7.2.8.4 Nexus shall not issue official forecasts, official warnings, meteorological determinations, or public warning messages. 7.2.8.5 The constitutional rule shall be: **WMO-facing engagement may support climate and hazard learning. It does not create official forecast or warning authority.** ### 7.2.9 IOM Interface Protocol 7.2.9.1 The IOM Interface Protocol shall govern engagement where displacement, migration, mobility, shelter, climate migration, conflict-sensitive mobility, urban absorption, public health, infrastructure stress, or protection-sensitive records may support bounded learning or lawful handoff. 7.2.9.2 IOM Interface Records shall identify:\ a. mobility or displacement theme;\ b. source records;\ c. protection sensitivity;\ d. personal data safeguards;\ e. humanitarian boundary;\ f. public authority boundary;\ g. legal status boundary;\ h. public-safe reporting limit;\ i. correction pathway;\ j. handoff or continuation status. 7.2.9.3 Engagement with IOM-facing actors shall not imply IOM endorsement, official migration determination, displacement status determination, relocation approval, aid eligibility, border policy, legal status determination, funding approval, or implementation authorization. 7.2.9.4 Nexus shall not determine migration status, asylum status, refugee status, eligibility, relocation, aid allocation, border policy, or legal rights. 7.2.9.5 The constitutional rule shall be: **IOM-facing engagement must protect people and legal sensitivity before it informs mobility learning.** ### 7.2.10 WTO and Trade Interface Protocol 7.2.10.1 The WTO and Trade Interface Protocol shall govern engagement where trade dependency records, supply-chain risk records, food corridor records, critical minerals records, geopolitical risk records, market-conduct safeguards, or regional corridor records may support bounded trade-related learning. 7.2.10.2 WTO and Trade Interface Records shall identify:\ a. trade or corridor theme;\ b. source records;\ c. market-conduct boundary;\ d. competition safeguard;\ e. trade-policy boundary;\ f. public authority boundary;\ g. data sensitivity;\ h. public-safe reporting limit;\ i. correction pathway;\ j. continuation status. 7.2.10.3 Engagement with WTO-facing or trade-facing actors shall not imply trade policy advice, legal opinion, dispute position, sanctions advice, market coordination, procurement approval, public authority approval, official trade determination, or implementation authorization. 7.2.10.4 Nexus shall not coordinate prices, allocate suppliers, approve suppliers, direct trade policy, interpret trade law, or represent trade positions. 7.2.10.5 The constitutional rule shall be: **Trade-facing engagement maps dependency and disruption risk. It does not make trade policy or coordinate markets.** ### 7.2.11 OECD Interface Protocol 7.2.11.1 The OECD Interface Protocol shall govern engagement where Nexus records may support policy learning, governance learning, public finance readability, AI governance learning, risk governance gap analysis, resilience learning, standards learning, data governance, and public-safe institutional comparison. 7.2.11.2 OECD Interface Records shall identify:\ a. policy-learning theme;\ b. source records;\ c. evidence basis;\ d. public authority boundary;\ e. official-status boundary;\ f. comparison boundary;\ g. no-ranking boundary where applicable;\ h. public-safe language controls;\ i. correction pathway;\ j. continuation status. 7.2.11.3 Engagement with OECD-facing actors shall not imply OECD endorsement, policy approval, country assessment, official ranking, regulatory approval, public authority approval, procurement approval, financeability, or implementation authorization. 7.2.11.4 Nexus shall not represent its records as official OECD standards, findings, country reviews, rankings, or policy recommendations unless separately and lawfully established by the competent institution. 7.2.11.5 The constitutional rule shall be: **OECD-facing engagement supports policy learning. It does not create official policy assessment or endorsement.** ### 7.2.12 World Bank Group Interface Protocol 7.2.12.1 The World Bank Group Interface Protocol shall govern engagement where resilience records, climate adaptation records, disaster risk records, infrastructure exposure records, public finance exposure records, development-finance readiness records, technical-readiness records, safeguard records, and lawful handoff records may support bounded development-finance learning. 7.2.12.2 World Bank Group Interface Records shall identify:\ a. actor category;\ b. engagement purpose;\ c. country or regional relevance;\ d. source records;\ e. safeguard relevance;\ f. public finance readability relevance;\ g. procurement boundary;\ h. finance-readiness boundary;\ i. official-status boundary;\ j. correction pathway;\ k. Nexus Rails continuation. 7.2.12.3 Engagement with World Bank Group actors shall not imply endorsement, appraisal, project approval, financing approval, guarantee, procurement approval, safeguard clearance, country ownership, public authority approval, financeability, or implementation authority. 7.2.12.4 Nexus shall not replace World Bank Group country engagement, appraisal, safeguards, procurement, financing, supervision, governance, or accountability procedures. 7.2.12.5 The constitutional rule shall be: **World Bank Group-facing engagement may make resilience records readable. It does not become appraisal, approval, or finance.** ### 7.2.13 IMF-Adjacent Public Finance Interface Protocol 7.2.13.1 The IMF-Adjacent Public Finance Interface Protocol shall govern engagement where public finance exposure records, fiscal stress scenarios, sovereign risk context, climate and disaster fiscal exposure, tax and revenue risk, public asset exposure, and policy-learning records may support bounded public finance learning. 7.2.13.2 IMF-Adjacent Interface Records shall identify:\ a. public finance question;\ b. source records;\ c. evidence basis;\ d. uncertainty;\ e. no-rating boundary;\ f. no-fiscal-advice boundary;\ g. no-debt-advice boundary;\ h. no-policy-conditionality boundary;\ i. official-status boundary;\ j. correction pathway;\ k. continuation status. 7.2.13.3 Nexus shall not issue macroeconomic surveillance findings, fiscal advice, debt advice, tax advice, monetary policy advice, sovereign credit views, conditionality advice, public finance approval, or official country judgments. 7.2.13.4 IMF-adjacent engagement shall not imply IMF endorsement, adoption, approval, surveillance finding, financing, public authority approval, or sovereign financeability. 7.2.13.5 The constitutional rule shall be: **IMF-adjacent engagement may make fiscal risk readable. It shall not become macroeconomic assessment, debt advice, or sovereign judgment.** ### 7.2.14 Regional Development Bank Protocol 7.2.14.1 The Regional Development Bank Protocol shall govern engagement with regional development banks where regional portfolio records, cross-border dependency records, infrastructure resilience records, climate adaptation records, disaster risk records, public finance readability records, and development-finance readiness records may support lawful downstream learning. 7.2.14.2 Regional Development Bank Engagement Records shall identify:\ a. regional development bank actor category;\ b. regional or national pathway;\ c. source records;\ d. development relevance;\ e. public authority boundaries;\ f. safeguard relevance;\ g. procurement boundary;\ h. finance-readiness boundary;\ i. regional federation boundary;\ j. correction pathway;\ k. continuation status. 7.2.14.3 Engagement with regional development banks shall not imply bank endorsement, appraisal, approval, financing, guarantee, procurement approval, safeguard clearance, country approval, public authority approval, financeability, or implementation authorization. 7.2.14.4 Nexus shall not replace regional development bank mandates, country processes, appraisal, safeguards, procurement, financing, supervision, or accountability systems. 7.2.14.5 The constitutional rule shall be: **Regional development bank engagement connects regional readiness records to lawful learning without approving finance.** ### 7.2.15 National Development Bank Protocol 7.2.15.1 The National Development Bank Protocol shall govern engagement with national development banks where national portfolio records, infrastructure risk records, public finance readability records, climate finance readiness records, disaster risk finance readiness records, and programmatic resilience records may support lawful national learning. 7.2.15.2 National Development Bank Engagement Records shall identify:\ a. national pathway;\ b. development bank actor category;\ c. source records;\ d. public authority boundary;\ e. public finance boundary;\ f. procurement boundary;\ g. no-financeability status;\ h. no-bankability status;\ i. diligence gaps;\ j. correction pathway;\ k. continuation status. 7.2.15.3 Engagement with national development banks shall not imply national development bank approval, financing, guarantee, credit decision, public finance approval, procurement approval, government endorsement, bankability, financeability, or implementation authority. 7.2.15.4 Nexus shall not replace the bank’s appraisal, credit, risk, environmental and social, procurement, legal, governance, or approval processes. 7.2.15.5 The constitutional rule shall be: **National development bank engagement prepares records for lawful review. It does not approve national development finance.** ### 7.2.16 Sovereign Wealth Fund Protocol 7.2.16.1 The Sovereign Wealth Fund Protocol shall govern engagement with sovereign wealth funds through product-neutral, non-advisory, no-offer, no-allocation, no-financeability, and no-sovereign-endorsement records. 7.2.16.2 Sovereign Wealth Fund Engagement Records shall identify:\ a. resilience theme;\ b. source records;\ c. public finance boundary;\ d. public authority boundary;\ e. investment-advice boundary;\ f. sovereign endorsement boundary;\ g. procurement boundary;\ h. diligence gaps;\ i. no-false-capital-signal controls;\ j. correction pathway;\ k. continuation status. 7.2.16.3 Engagement with sovereign wealth funds shall not imply sovereign endorsement, investment approval, mandate fit, allocation approval, public investment approval, financeability, guarantee, rating, procurement approval, or implementation authority. 7.2.16.4 Sovereign wealth funds shall make their own decisions under their own mandates, governance, fiduciary duties, investment policies, approvals, and legal obligations. 7.2.16.5 The constitutional rule shall be: **Sovereign wealth fund engagement supports resilience readability without advising sovereign capital.** ### 7.2.17 Infrastructure Investor Protocol 7.2.17.1 The Infrastructure Investor Protocol shall govern engagement with infrastructure investors only through product-neutral, non-advisory, no-offer, no-allocation, no-financeability, no-bankability, no-procurement-approval records. 7.2.17.2 Infrastructure Investor Engagement Records shall identify:\ a. infrastructure theme;\ b. source records;\ c. evidence status;\ d. technical-readiness status;\ e. public authority boundary;\ f. procurement boundary;\ g. community consent boundary;\ h. no-advice status;\ i. no-offer status;\ j. no-financeability status;\ k. diligence gaps;\ l. correction pathway. 7.2.17.3 Nexus shall not provide investment advice, financial promotion, securities offering, deal sourcing, capital raising, valuation, lending approval, capital allocation, infrastructure project approval, procurement approval, bankability determination, financeability determination, or implementation authority. 7.2.17.4 Infrastructure investors shall make their own decisions under their own mandates, procedures, duties, approvals, regulatory obligations, and risk responsibilities. 7.2.17.5 The constitutional rule shall be: **Infrastructure investor engagement makes records readable. It does not invite, recommend, or approve investment.** ### 7.2.18 Insurance and Reinsurance Protocol 7.2.18.1 The Insurance and Reinsurance Protocol shall govern engagement with insurance and reinsurance actors only through insurance-readiness questions, protection-gap intelligence, exposure records, data-quality questions, resilience measure descriptions, disaster risk finance readiness records, public-safe summaries, and market-conduct-safe learning. 7.2.18.2 Insurance and Reinsurance Engagement Records shall identify:\ a. exposure category;\ b. protection-gap signal;\ c. data status;\ d. evidence gaps;\ e. resilience relevance;\ f. market-conduct boundary;\ g. no-underwriting boundary;\ h. no-pricing boundary;\ i. no-coverage boundary;\ j. no-placement boundary;\ k. correction pathway;\ l. continuation status. 7.2.18.3 Nexus shall not underwrite, price, place, broker, reinsure, determine claims, approve coverage, determine insurability, provide insurance advice, or coordinate market conduct. 7.2.18.4 Insurance and reinsurance actors shall make their own decisions under their own licenses, regulations, underwriting methods, actuarial duties, market conduct rules, governance, and risk responsibilities. 7.2.18.5 The constitutional rule shall be: **Insurance and reinsurance engagement frames exposure questions. It does not underwrite, price, place, or approve coverage.** ### 7.2.19 Public Health Institution Protocol 7.2.19.1 The Public Health Institution Protocol shall govern engagement with public health institutions where health risk records, health-system capacity records, health-system surge scenarios, biosecurity records, public health signal records, water and sanitation links, food-system health links, and public-safe reports may support lawful public health learning. 7.2.19.2 Public Health Institution Engagement Records shall identify:\ a. public health theme;\ b. source records;\ c. health data sensitivity;\ d. privacy controls;\ e. public health authority boundary;\ f. clinical guidance boundary;\ g. biosecurity controls;\ h. public-safe communication limits;\ i. correction pathway;\ j. lawful handoff status. 7.2.19.3 Engagement with public health institutions shall not imply official health guidance, public health orders, disease determinations, biosurveillance authority, emergency declaration, health procurement approval, clinical advice, or implementation authorization. 7.2.19.4 Nexus shall not provide medical advice, clinical guidance, public health orders, pathogen handling guidance, harmful biological instructions, or official health determinations. 7.2.19.5 The constitutional rule shall be: **Public health engagement supports readiness only where health authority, privacy, and biosecurity boundaries are protected.** ### 7.2.20 Food Security Institution Protocol 7.2.20.1 The Food Security Institution Protocol shall govern engagement with food security institutions where food-system risk records, agricultural risk records, supply corridor records, market disruption records, nutrition-related resilience records, public finance exposure records, and public-safe summaries may support bounded learning. 7.2.20.2 Food Security Institution Engagement Records shall identify:\ a. food security theme;\ b. source records;\ c. evidence status;\ d. market-conduct boundary;\ e. trade-policy boundary;\ f. humanitarian sensitivity where applicable;\ g. public authority boundary;\ h. public-safe reporting limit;\ i. correction pathway;\ j. continuation status. 7.2.20.3 Engagement with food security institutions shall not imply food allocation, food security determination, agricultural policy approval, trade decision, procurement approval, funding approval, public authority approval, or implementation authorization. 7.2.20.4 Nexus shall not allocate food, direct markets, approve suppliers, issue official food security determinations, or coordinate market conduct. 7.2.20.5 The constitutional rule shall be: **Food security engagement maps food-system risk without becoming food allocation, market control, or official determination.** ### 7.2.21 Water and Sanitation Institution Protocol 7.2.21.1 The Water and Sanitation Institution Protocol shall govern engagement with water, sanitation, basin, utility, public health, infrastructure, and development actors where water risk records, sanitation records, basin stress records, infrastructure exposure records, public health links, and public finance exposure records may support lawful learning. 7.2.21.2 Water and Sanitation Engagement Records shall identify:\ a. water or sanitation theme;\ b. source records;\ c. basin or utility boundary where relevant;\ d. water rights boundary;\ e. public health boundary;\ f. environmental boundary;\ g. public authority boundary;\ h. community safeguard status;\ i. public-safe reporting limit;\ j. correction pathway;\ k. continuation status. 7.2.21.3 Engagement shall not imply water allocation, utility approval, tariff approval, basin governance authority, sanitation policy approval, public health order, environmental permit, public finance approval, procurement approval, or implementation authority. 7.2.21.4 The constitutional rule shall be: **Water and sanitation engagement makes dependency visible without allocating water or governing water systems.** ### 7.2.22 Energy Transition Institution Protocol 7.2.22.1 The Energy Transition Institution Protocol shall govern engagement with energy transition institutions where energy risk records, grid stress records, infrastructure exposure records, critical minerals records, water-energy dependencies, public finance exposure records, climate adaptation records, and technical-readiness records may support bounded learning. 7.2.22.2 Energy Transition Engagement Records shall identify:\ a. energy transition theme;\ b. source records;\ c. grid or utility boundary;\ d. regulatory boundary;\ e. procurement boundary;\ f. market-conduct boundary;\ g. public authority boundary;\ h. finance-readiness boundary;\ i. public-safe reporting limit;\ j. correction pathway;\ k. continuation status. 7.2.22.3 Engagement shall not imply energy policy approval, tariff approval, grid intervention approval, technology approval, procurement approval, public finance approval, financeability, insurability, or implementation authority. 7.2.22.4 Nexus shall not direct utilities, approve technologies, allocate energy resources, set tariffs, or approve energy projects. 7.2.22.5 The constitutional rule shall be: **Energy transition engagement records resilience questions without deciding energy policy or operations.** ### 7.2.23 Biodiversity and Nature Institution Protocol 7.2.23.1 The Biodiversity and Nature Institution Protocol shall govern engagement with biodiversity, conservation, nature, land-use, ecosystem, environmental, Indigenous knowledge, and community-facing actors where nature risk records may support public-safe learning. 7.2.23.2 Biodiversity and Nature Engagement Records shall identify:\ a. biodiversity or nature theme;\ b. source records;\ c. ecosystem sensitivity;\ d. sensitive location controls;\ e. community safeguard status;\ f. Indigenous knowledge safeguard status;\ g. environmental authority boundary;\ h. land-use authority boundary;\ i. nature-finance boundary;\ j. public-safe reporting limit;\ k. correction pathway;\ l. continuation status. 7.2.23.3 Engagement shall not imply land-use approval, environmental permit, conservation authority, offset validation, nature-finance validation, community consent, Indigenous consent, public finance approval, financeability, insurability, or implementation authority. 7.2.23.4 Biodiversity and nature engagement shall protect sensitive ecosystems, species locations, cultural knowledge, Indigenous knowledge, and community data. 7.2.23.5 The constitutional rule shall be: **Nature engagement must protect ecosystems and knowledge while refusing false approval, offset, finance, or consent claims.** ### 7.2.24 City and Local Government Protocol 7.2.24.1 The City and Local Government Protocol shall govern engagement with cities, municipalities, local governments, regional governments, urban agencies, local public utilities, and metropolitan actors where urban risk records, infrastructure exposure records, public service continuity records, public finance exposure records, community safeguard records, and public-safe summaries may support learning. 7.2.24.2 City and Local Government Engagement Records shall identify:\ a. local or regional actor category;\ b. engagement purpose;\ c. records shared;\ d. municipal or regional mandate status;\ e. public finance boundary;\ f. procurement boundary;\ g. land-use boundary;\ h. community safeguard status;\ i. public-safe reporting limit;\ j. correction pathway;\ k. continuation status. 7.2.24.3 Engagement shall not imply city approval, regional government approval, public budget approval, zoning approval, permitting approval, procurement approval, official adoption, financeability, insurability, consent, or implementation authorization unless separately and lawfully documented. 7.2.24.4 Nexus shall not replace local planning, permitting, budgeting, procurement, public consultation, emergency management, public works, or implementation authority. 7.2.24.5 The constitutional rule shall be: **City and local government engagement supports local learning without becoming local authority.** ### 7.2.25 University and Research Protocol 7.2.25.1 The University and Research Protocol shall govern engagement with universities, research institutes, laboratories, technical networks, policy research networks, data science networks, and academic partners. 7.2.25.2 University and Research Engagement Records shall identify:\ a. research actor or network category;\ b. research or learning purpose;\ c. source records;\ d. data access conditions;\ e. ethics and privacy conditions where applicable;\ f. publication boundary;\ g. intellectual property boundary;\ h. public-safe language controls;\ i. community and Indigenous knowledge safeguards where applicable;\ j. correction pathway;\ k. continuation status. 7.2.25.3 Engagement with research institutions shall not imply research endorsement, peer review, ethics approval, institutional approval, certification, public authority approval, procurement approval, financeability, insurability, or implementation authorization. 7.2.25.4 Research collaboration shall preserve data rights, ethical review requirements, publication controls, public-safe language, community safeguards, Indigenous knowledge safeguards, and lawful handoff conditions. 7.2.25.5 The constitutional rule shall be: **Research engagement strengthens evidence where governed. It does not convert academic proximity into validation.** ### 7.2.26 Civil Society Protocol 7.2.26.1 The Civil Society Protocol shall govern engagement with civil society organizations, advocacy groups, professional associations, public-interest organizations, media-adjacent public-interest actors, and community-supporting institutions. 7.2.26.2 Civil Society Engagement Records shall identify:\ a. organization or actor category;\ b. participation purpose;\ c. records shared or contributed;\ d. representation boundary;\ e. consent boundary;\ f. public-safe language boundary;\ g. data and privacy conditions;\ h. conflict or advocacy disclosure where material;\ i. correction pathway;\ j. continuation status. 7.2.26.3 Engagement with civil society organizations shall not imply civil society endorsement, community consent, social license, public authority approval, project approval, finance approval, procurement approval, official representation, or implementation authority. 7.2.26.4 Civil society participation shall not be used to claim representation of communities, affected people, or Indigenous peoples unless separately and lawfully documented. 7.2.26.5 The constitutional rule shall be: **Civil society engagement strengthens participation records. It does not convert participation into representation or consent.** ### 7.2.27 Philanthropy Protocol 7.2.27.1 The Philanthropy Protocol shall govern engagement with philanthropic institutions, foundations, donor-advised structures, public-good funders, research funders, field-building funders, and capacity-building supporters. 7.2.27.2 Philanthropy Engagement Records shall identify:\ a. philanthropic actor category;\ b. support purpose;\ c. supported pathway or output;\ d. no-control status;\ e. no-endorsement status where applicable;\ f. no-procurement-advantage status;\ g. no-financeability status;\ h. no-insurability status;\ i. public-safe language boundary;\ j. conflict disclosure where material;\ k. correction pathway;\ l. continuation status. 7.2.27.3 Philanthropic support shall not control records, evidence, governance, public-safe reports, technical verification, public authority learning, community safeguard records, finance-readiness notes, Nexus Universe outputs, or Nexus Rails continuation. 7.2.27.4 Philanthropic engagement shall not imply endorsement, public authority approval, development approval, procurement advantage, financeability, insurability, social license, consent, or implementation authority. 7.2.27.5 The constitutional rule shall be: **Philanthropic support may strengthen public-good capacity. It shall not control the record.** ### 7.2.28 Engagement Without Endorsement 7.2.28.1 Engagement Without Endorsement shall apply to every partner, institution, actor, room, platform, briefing, meeting, event, report, dashboard, demonstration, or handoff under this Section. 7.2.28.2 Engagement may indicate that a conversation, review, learning activity, data-room session, technical demonstration, public-safe briefing, or handoff occurred. 7.2.28.3 Engagement shall not imply endorsement, approval, adoption, certification, procurement approval, funding approval, investment approval, underwriting approval, public authority approval, official consultation, mandate, social license, consent, representation, or implementation authorization unless separately and lawfully documented. 7.2.28.4 Engagement records shall include no-endorsement language where there is a reasonable risk of public, partner, sponsor, provider, finance-facing, media, or institutional misinterpretation. 7.2.28.5 The constitutional rule shall be: **Engagement records contact and learning. It does not create endorsement.** ### 7.2.29 Engagement Without Mandate Substitution 7.2.29.1 Engagement Without Mandate Substitution shall mean that no Nexus engagement may replace the mandate, legal authority, governance, decision process, fiduciary duty, operational duty, financial authority, humanitarian responsibility, public authority, regulatory process, procurement procedure, safeguards process, consent process, or accountability structure of the institution engaged. 7.2.29.2 Nexus may provide records, technical methods, evidence packs, verification receipts, simulations, digital twins, public-safe reports, finance-readiness notes, insurance-readiness questions, policy-learning records, and Nexus Rails continuation. 7.2.29.3 Nexus shall not substitute for:\ a. UN mandates;\ b. humanitarian mandates;\ c. development agency mandates;\ d. public authority mandates;\ e. multilateral bank appraisal;\ f. financing approval;\ g. regulatory approval;\ h. procurement approval;\ i. safeguards review;\ j. community consent;\ k. Indigenous consent;\ l. standards certification;\ m. professional assurance;\ n. implementation authorization. 7.2.29.4 Where Nexus records are used by an external actor, the records shall retain their source, status labels, decision-use labels, public-safe labels, evidence limits, data restrictions, correction history, prohibited-use language, and Nexus Rails continuation status where material. 7.2.29.5 The constitutional rule shall be: **Nexus engagement may support competent institutions. It shall not become those institutions, replace their mandates, or decide for them.** ## 7.3 Humanitarian and Crisis-Readiness Layer ### 7.3.0 Status, Purpose, and Governing Effect 7.3.0.1 This Section establishes the Humanitarian and Crisis-Readiness Layer as the Nexus architecture through which humanitarian risk mapping, crisis scenario simulation, WASH-health-food-energy dependency mapping, logistics and supply-chain exposure, health, shelter, and infrastructure dependency records, Emergency Risk Rooms, rapid public-safe reporting, crisis data protection, sensitive population data safeguards, community safeguard records, humanitarian neutrality safeguards, mandated humanitarian actor interfaces, crisis mode protocols, misinformation controls, and post-crisis continuation records may be organized without converting Nexus into a humanitarian response actor. 7.3.0.2 The Humanitarian and Crisis-Readiness Layer shall support National Nexus Consortiums, Regional Nexus Consortiums, the Swiss Nexus Global Node, Nexus Core, Nexus Network, Nexus Universe, Nexus Registry, Nexus Reports, Nexus Rails, public-safe intelligence, public authority learning, community safeguards, humanitarian interface records, and lawful handoff pathways. 7.3.0.3 The Humanitarian and Crisis-Readiness Layer shall not be treated as humanitarian mandate, emergency command, public warning authority, needs assessment authority, relief allocation authority, protection mandate, displacement-status authority, refugee-status authority, migration-status authority, public health authority, public authority approval, social license, community consent, Indigenous consent, implementation authorization, or operational response authority unless separately and lawfully granted within a documented scope. 7.3.0.4 Nexus may support crisis-readiness by making humanitarian risk records more coherent, evidence-bounded, technically reviewable, public-safe, data-protected, safeguard-aware, correction-ready, and lawfully handoff-ready. Nexus shall not replace mandated humanitarian actors, public authorities, emergency responders, public health institutions, protection actors, community authorities, or competent operational institutions. 7.3.0.5 Crisis-readiness records shall be privacy-protective, protection-sensitive, conflict-sensitive, public-safe, data-minimized, role-separated, correction-ready, decision-use-labeled, and continued through Nexus Rails where material. 7.3.0.6 The governing rule of this Section is: **Nexus may strengthen humanitarian and crisis-readiness records. Nexus does not command response, allocate relief, assess needs, grant protection, or implement crisis operations unless separately and lawfully mandated.** ### 7.3.1 Humanitarian Risk Mapping 7.3.1.1 Humanitarian Risk Mapping shall identify hazards, exposures, vulnerabilities, protection concerns, infrastructure dependencies, public health risks, WASH risks, food-system risks, shelter risks, displacement pressures, logistics constraints, community safeguard issues, and crisis-sensitive data risks. 7.3.1.2 Humanitarian Risk Mapping may support crisis-readiness records, public-safe reports, humanitarian interface records, public authority learning records, community safeguard records, rapid reporting, Emergency Risk Rooms, and lawful handoff to mandated actors. 7.3.1.3 A Humanitarian Risk Mapping Record shall identify:\ a. risk theme;\ b. affected geography where appropriate and safe;\ c. population sensitivity;\ d. evidence basis;\ e. data sources;\ f. privacy and protection controls;\ g. public authority boundaries;\ h. humanitarian mandate boundaries;\ i. community safeguard conditions;\ j. public-safe reporting limits;\ k. correction pathway;\ l. Nexus Rails continuation status. 7.3.1.4 Humanitarian Risk Mapping shall not determine needs, eligibility, relief allocation, displacement status, protection status, beneficiary status, public authority priority, or operational response. 7.3.1.5 The constitutional rule shall be: **Humanitarian risk mapping makes crisis exposure visible without becoming humanitarian assessment or response authority.** ### 7.3.2 Crisis Scenario Simulation 7.3.2.1 Crisis Scenario Simulation shall examine how hazards, conflict-sensitive conditions, infrastructure failures, health-system stress, food-system disruption, WASH breakdown, energy outage, logistics disruption, displacement pressure, misinformation, and public finance stress may affect crisis readiness. 7.3.2.2 Crisis Scenario Simulation may be conducted through Nexus Core, Nexus Network, Emergency Risk Rooms, secure data environments, scenario records, public-safe dashboards, and Nexus Rails continuation. 7.3.2.3 A Crisis Scenario Simulation Record shall identify:\ a. crisis scenario;\ b. initiating hazard or stressor;\ c. affected systems;\ d. assumptions;\ e. evidence basis;\ f. data sensitivity;\ g. protection sensitivity;\ h. public-safe reporting limits;\ i. humanitarian interface relevance;\ j. correction pathway;\ k. continuation status. 7.3.2.4 Crisis Scenario Simulation shall not be treated as prediction, official warning, emergency command, humanitarian response plan, public authority order, needs assessment, relief allocation, or operational authorization. 7.3.2.5 The constitutional rule shall be: **Crisis simulations support readiness learning. They do not predict crises or command response.** ### 7.3.3 WASH-Health-Food-Energy Dependency Mapping 7.3.3.1 WASH-Health-Food-Energy Dependency Mapping shall identify how water, sanitation, hygiene, health systems, food systems, and energy systems depend on one another in crisis conditions. 7.3.3.2 Dependency mapping may address:\ a. water access and quality;\ b. sanitation and hygiene continuity;\ c. health facility functionality;\ d. cold-chain and food storage;\ e. energy reliability;\ f. fuel supply;\ g. transport and logistics;\ h. public health implications;\ i. shelter and settlement conditions;\ j. community safeguards. 7.3.3.3 A WASH-Health-Food-Energy Dependency Record shall identify:\ a. systems mapped;\ b. dependency pathways;\ c. evidence basis;\ d. data quality;\ e. population sensitivity;\ f. health data safeguards;\ g. WASH authority boundaries;\ h. humanitarian mandate boundaries;\ i. public-safe reporting limits;\ j. correction pathway;\ k. continuation status. 7.3.3.4 Dependency mapping shall not allocate water, food, shelter, medicine, fuel, or services; direct public health operations; issue WASH orders; approve interventions; or implement response. 7.3.3.5 The constitutional rule shall be: **WASH-health-food-energy mapping shows dependency before crisis response decisions are made by competent actors.** ### 7.3.4 Logistics and Supply-Chain Exposure 7.3.4.1 Logistics and Supply-Chain Exposure records shall identify crisis-relevant dependencies affecting transport, ports, corridors, warehouses, cold chains, medical supplies, food supplies, WASH supplies, fuel, telecommunications, last-mile delivery, and emergency stock movement. 7.3.4.2 Logistics exposure records may support crisis scenario simulation, public-safe reporting, Emergency Risk Rooms, humanitarian interface records, supply-chain risk records, and lawful handoff. 7.3.4.3 A Logistics and Supply-Chain Exposure Record shall identify:\ a. supply chain or logistics system;\ b. exposure or bottleneck;\ c. affected crisis function;\ d. evidence basis;\ e. data sensitivity;\ f. market-conduct boundary;\ g. security sensitivity;\ h. humanitarian boundary;\ i. public-safe reporting limit;\ j. correction pathway;\ k. continuation status. 7.3.4.4 Nexus shall not coordinate suppliers, allocate goods, set prices, direct logistics operations, approve procurement, allocate relief, or command humanitarian delivery. 7.3.4.5 The constitutional rule shall be: **Logistics exposure records support readiness. They do not coordinate markets or direct relief supply.** ### 7.3.5 Health, Shelter, and Infrastructure Dependencies 7.3.5.1 Health, Shelter, and Infrastructure Dependency records shall identify how health services, emergency shelter, housing, transport, water, sanitation, energy, telecommunications, waste management, public safety, and public administration interact in crisis conditions. 7.3.5.2 Dependency records may support crisis-readiness planning, scenario simulation, public-safe dashboards, community safeguard records, public authority learning, humanitarian interface, and lawful handoff. 7.3.5.3 A Health, Shelter, and Infrastructure Dependency Record shall identify:\ a. dependency mapped;\ b. affected services;\ c. affected population sensitivity;\ d. evidence basis;\ e. health data safeguards;\ f. shelter and protection safeguards;\ g. infrastructure owner or operator boundaries;\ h. public authority boundaries;\ i. public-safe reporting limits;\ j. correction pathway;\ k. continuation status. 7.3.5.4 Nexus shall not allocate shelter, command health facilities, direct infrastructure operators, issue public health guidance, approve housing policy, or implement crisis services. 7.3.5.5 The constitutional rule shall be: **Dependency records help reveal crisis fragility without making Nexus the operator, responder, or allocator.** ### 7.3.6 Emergency Risk Rooms 7.3.6.1 Emergency Risk Rooms may be established as controlled, time-bounded, role-separated spaces for reviewing crisis risk records, scenario outputs, public-safe intelligence, data safeguards, community safeguard records, logistics exposure, public authority learning, and humanitarian interface records. 7.3.6.2 Emergency Risk Rooms shall require:\ a. purpose record;\ b. activation trigger;\ c. participant roles;\ d. access controls;\ e. data protection controls;\ f. protection-sensitive handling rules;\ g. humanitarian neutrality safeguards;\ h. public authority boundaries;\ i. public-safe reporting controls;\ j. correction pathway;\ k. Nexus Rails continuation status. 7.3.6.3 Emergency Risk Rooms shall not become emergency operations centers, humanitarian cluster meetings, public authority command rooms, relief allocation rooms, needs assessment authorities, protection case-management spaces, procurement rooms, or public warning centers unless separately and lawfully mandated. 7.3.6.4 Emergency Risk Room outputs shall carry public-safe labels, decision-use labels, data restrictions, mandate boundaries, and correction pathways. 7.3.6.5 The constitutional rule shall be: **Emergency Risk Rooms review crisis records. They do not command crisis response.** ### 7.3.7 Rapid Public-Safe Reporting 7.3.7.1 Rapid Public-Safe Reporting shall provide bounded crisis-relevant summaries where timely public-safe communication is necessary to prevent misunderstanding, reduce overclaim, support learning, or route records to competent actors. 7.3.7.2 Rapid Public-Safe Reports may include:\ a. risk signal summaries;\ b. dependency summaries;\ c. scenario summaries;\ d. evidence-gap notes;\ e. public authority boundary notes;\ f. humanitarian interface notes;\ g. data protection notes;\ h. misinformation correction notes;\ i. correction notices;\ j. Nexus Rails continuation notes. 7.3.7.3 Rapid Public-Safe Reporting shall identify source records, evidence status, uncertainty, data limitations, public authority boundaries, humanitarian mandate boundaries, protection sensitivity, prohibited uses, correction pathway, and continuation status. 7.3.7.4 Rapid Public-Safe Reporting shall not issue public warnings, official needs assessments, emergency orders, humanitarian appeals, aid allocation decisions, public health orders, or operational instructions unless separately and lawfully mandated. 7.3.7.5 The constitutional rule shall be: **Rapid reporting must be fast enough to be useful and bounded enough not to become false authority.** ### 7.3.8 Data Protection in Crisis Contexts 7.3.8.1 Data Protection in Crisis Contexts shall govern crisis-related personal data, sensitive population data, location data, health data, protection data, displacement data, shelter data, biometric data where applicable, community data, Indigenous knowledge, infrastructure-sensitive data, and humanitarian-sensitive data. 7.3.8.2 Crisis data protection shall require:\ a. lawful access basis;\ b. purpose limitation;\ c. data minimization;\ d. sensitivity classification;\ e. role-based access controls;\ f. secure storage;\ g. restricted export;\ h. retention and deletion rules;\ i. public-safe publishing limits;\ j. breach and incident response;\ k. correction pathway;\ l. Nexus Rails continuation. 7.3.8.3 Crisis conditions shall not justify unrestricted collection, reuse, sharing, publication, or retention of sensitive data. 7.3.8.4 Nexus shall not treat data visibility, data access, data contribution, or urgency as ownership, consent, public disclosure permission, or unrestricted processing authority. 7.3.8.5 The constitutional rule shall be: **Crisis urgency increases the duty to protect data; it does not suspend it.** ### 7.3.9 Sensitive Population Data 7.3.9.1 Sensitive Population Data shall include data relating to displaced persons, children, older persons, persons with disabilities, migrants, refugees, asylum seekers, stateless persons, affected communities, Indigenous peoples, patients, survivors of violence, households in crisis, and other vulnerable or protection-sensitive groups. 7.3.9.2 Sensitive Population Data records shall identify:\ a. data category;\ b. sensitivity level;\ c. lawful basis;\ d. data steward;\ e. collection context;\ f. consent or lawful-use condition where applicable;\ g. access controls;\ h. anonymization, aggregation, or redaction requirements;\ i. public-safe reporting limits;\ j. correction and deletion pathway;\ k. continuation status. 7.3.9.3 Sensitive Population Data shall not be used for public visibility, finance-readiness, public authority learning, donor reporting, media outputs, dashboards, maps, or demonstrations unless the use is lawful, necessary, proportionate, safe, and bounded. 7.3.9.4 Nexus shall not expose individuals or communities through identifiable, stigmatizing, location-sensitive, legal-status-sensitive, health-sensitive, or protection-sensitive records. 7.3.9.5 The constitutional rule shall be: **Sensitive population data must protect people before it informs systems.** ### 7.3.10 Community Safeguard Records 7.3.10.1 Community Safeguard Records shall document crisis-related community participation, lived-risk evidence, local knowledge, benefit and risk distribution, consent boundaries, feedback pathways, privacy safeguards, unresolved harms, protection-sensitive issues, and public-safe reporting limits. 7.3.10.2 A Community Safeguard Record shall identify:\ a. community-facing issue;\ b. participation scope;\ c. knowledge or evidence contributed;\ d. consent boundary;\ e. privacy and protection safeguards;\ f. unresolved issues;\ g. public-safe reporting limits;\ h. correction pathway;\ i. handoff or continuation status. 7.3.10.3 Community participation in crisis-readiness shall not imply social license, community consent, Indigenous consent, public approval, project authorization, aid allocation approval, data ownership transfer, or implementation authority. 7.3.10.4 Community safeguard records shall not be used to expose vulnerable people, sensitive locations, cultural knowledge, Indigenous knowledge, legal status, or protection-sensitive information. 7.3.10.5 The constitutional rule shall be: **Community safeguard records preserve participation without converting participation into consent or exposure.** ### 7.3.11 Humanitarian Neutrality Safeguards 7.3.11.1 Humanitarian Neutrality Safeguards shall ensure that Nexus crisis-readiness activities do not compromise the perceived or actual neutrality, impartiality, independence, safety, or protection responsibilities of mandated humanitarian actors. 7.3.11.2 Humanitarian Neutrality Safeguards shall address:\ a. role separation;\ b. public language;\ c. data sharing;\ d. conflict-sensitive records;\ e. political neutrality;\ f. military or security actor boundaries;\ g. sponsor and provider boundaries;\ h. media boundaries;\ i. public authority boundaries;\ j. protection-sensitive publication;\ k. correction pathway;\ l. lawful handoff conditions. 7.3.11.3 Nexus shall not use humanitarian engagement to imply endorsement, access, protection mandate, operational role, field authority, public authority approval, or crisis legitimacy. 7.3.11.4 Where Nexus records or communications could compromise neutrality or protection, they shall be restricted, corrected, delayed, withdrawn, superseded, archived, or routed through secure handoff. 7.3.11.5 The constitutional rule shall be: **Humanitarian neutrality is a safeguard condition, not a communications feature.** ### 7.3.12 Interface With Mandated Humanitarian Actors 7.3.12.1 Interface With Mandated Humanitarian Actors shall govern how Nexus may share public-safe records, restricted records, scenario outputs, dependency maps, data safeguard notes, crisis-risk summaries, and lawful handoff materials with actors holding humanitarian mandates. 7.3.12.2 A Mandated Humanitarian Actor Interface Record shall identify:\ a. actor category;\ b. interface purpose;\ c. mandate boundary;\ d. records shared;\ e. data sensitivity;\ f. protection sensitivity;\ g. conflict-sensitive conditions;\ h. public-safe reporting limits;\ i. handoff conditions;\ j. correction obligations;\ k. continuation status. 7.3.12.3 Interface shall not imply that Nexus has the humanitarian actor’s mandate, that the humanitarian actor endorses Nexus, that the humanitarian actor approves Nexus outputs, or that Nexus participates in operational response. 7.3.12.4 Mandated actors shall decide whether and how to use Nexus records within their own mandates, procedures, data responsibilities, protection standards, and operational accountability. 7.3.12.5 The constitutional rule shall be: **Nexus may hand records to mandated humanitarian actors. Nexus does not become a mandated humanitarian actor.** ### 7.3.13 Crisis Mode Protocol 7.3.13.1 Crisis Mode Protocol may be activated where a risk event, emerging crisis, rapid-onset disaster, conflict-sensitive emergency, public health concern, infrastructure outage, humanitarian risk, misinformation event, or cascading failure requires accelerated Nexus record handling. 7.3.13.2 Crisis Mode Protocol shall define:\ a. activation trigger;\ b. responsible steward;\ c. scope;\ d. participant roles;\ e. data protection rules;\ f. public-safe reporting rules;\ g. Emergency Risk Room rules;\ h. correction acceleration;\ i. public authority boundary;\ j. humanitarian mandate boundary;\ k. lawful handoff process;\ l. deactivation and archive conditions. 7.3.13.3 Crisis Mode Protocol shall accelerate record discipline, not loosen it. 7.3.13.4 Crisis Mode Protocol shall not create emergency command, public warning authority, relief allocation authority, protection mandate, public health authority, public authority mandate, or implementation authority. 7.3.13.5 The constitutional rule shall be: **Crisis Mode accelerates bounded record handling. It does not create crisis command.** ### 7.3.14 Non-Interference With Mandated Response 7.3.14.1 Nexus shall not interfere with mandated humanitarian, emergency, public health, public safety, public authority, protection, security, or operational response. 7.3.14.2 Non-interference shall require:\ a. role clarity;\ b. public-safe language;\ c. no command language;\ d. no operational instruction;\ e. no relief allocation claim;\ f. no needs assessment claim;\ g. no protection mandate claim;\ h. no public authority claim;\ i. no public warning claim;\ j. no media overclaim;\ k. correction pathway. 7.3.14.3 Nexus records may be offered to competent actors through lawful handoff, but competent actors shall decide whether and how to use them. 7.3.14.4 Where Nexus activity could interfere with response, confuse authority, expose sensitive data, create operational risk, or mislead affected populations, the activity shall be paused, restricted, corrected, withdrawn, or routed to competent actors. 7.3.14.5 The constitutional rule shall be: **Support the record. Do not interfere with the response.** ### 7.3.15 No Relief Allocation Authority 7.3.15.1 Nexus shall not allocate relief. 7.3.15.2 Nexus shall not decide who receives food, water, shelter, medicine, cash, protection services, transport, fuel, equipment, reconstruction assistance, humanitarian assistance, public support, or private support. 7.3.15.3 Nexus may record risk signals, dependency maps, public-safe summaries, data safeguard records, community safeguard records, and lawful handoff records that may be reviewed by competent relief actors. 7.3.15.4 Any language suggesting Nexus decides relief allocation, beneficiary eligibility, prioritization of aid, or distribution of assistance shall be corrected, withdrawn, or restricted. 7.3.15.5 The constitutional rule shall be: **Nexus may help make crisis risk readable. It does not allocate relief.** ### 7.3.16 No Needs Assessment Authority Unless Mandated 7.3.16.1 Nexus shall not claim needs assessment authority unless a competent mandated actor lawfully grants a specific needs assessment mandate within a documented scope. 7.3.16.2 Nexus may support readiness records, dependency records, exposure records, community safeguard records, evidence-gap records, public-safe reports, and lawful handoff records that may inform competent actors. 7.3.16.3 Nexus outputs shall not be described as official needs assessments, humanitarian needs overviews, beneficiary assessments, vulnerability assessments, eligibility determinations, damage assessments, or public authority assessments unless separately and lawfully authorized. 7.3.16.4 Where Nexus records are used in relation to needs assessment, the record shall include decision-use labels, mandate status, evidence status, data safeguards, public-safe limits, and correction pathways. 7.3.16.5 The constitutional rule shall be: **Nexus may prepare records that inform needs assessment. Nexus does not conduct official needs assessment unless lawfully mandated.** ### 7.3.17 No Protection Mandate Unless Granted 7.3.17.1 Nexus shall not claim protection mandate unless a competent mandated actor lawfully grants a specific protection-related role within a documented scope. 7.3.17.2 Nexus may record protection-sensitive risk context, community safeguard issues, data protection needs, public-safe language controls, humanitarian interface records, and lawful handoff conditions. 7.3.17.3 Nexus shall not conduct protection case management, determine protection status, provide legal protection determinations, manage survivor data, determine eligibility, represent affected persons, or act as a protection actor unless separately and lawfully authorized. 7.3.17.4 Protection-sensitive records shall be handled with heightened privacy, confidentiality, minimization, access control, public-safe publishing restriction, and correction controls. 7.3.17.5 The constitutional rule shall be: **Protection-sensitive records require protection discipline. They do not grant Nexus a protection mandate.** ### 7.3.18 No Emergency Command Authority Without Lawful Grant 7.3.18.1 Nexus shall not claim emergency command authority without a separate lawful grant by a competent authority within a documented scope. 7.3.18.2 Nexus shall not command public authorities, emergency responders, humanitarian actors, public health institutions, security actors, infrastructure operators, utilities, providers, communities, volunteers, or implementing actors. 7.3.18.3 Nexus may support emergency-readiness records, public-safe summaries, crisis scenario simulations, dependency records, data safeguard records, Emergency Risk Rooms, and lawful handoff pathways. 7.3.18.4 Any Nexus communication that could be interpreted as emergency command, public warning, evacuation instruction, medical instruction, operational order, or official directive shall be restricted, corrected, withdrawn, or referred to competent authorities. 7.3.18.5 The constitutional rule shall be: **Emergency command exists only by lawful grant. Nexus readiness records do not command response.** ### 7.3.19 Crisis Misinformation Controls 7.3.19.1 Crisis Misinformation Controls shall prevent Nexus records, reports, dashboards, briefings, media outputs, event materials, partner references, and public-safe summaries from spreading, amplifying, or legitimizing false, harmful, stigmatizing, panic-inducing, or authority-confusing information during crisis contexts. 7.3.19.2 Crisis Misinformation Controls shall address:\ a. source verification;\ b. evidence status;\ c. uncertainty labeling;\ d. public-safe language;\ e. false authority claims;\ f. rumor amplification risk;\ g. synthetic media risk;\ h. harmful identity or community framing;\ i. public health misinformation;\ j. humanitarian misinformation;\ k. correction and withdrawal pathways;\ l. Nexus Rails continuation. 7.3.19.3 Nexus shall not repeat unverified crisis claims in ways that amplify harm, identify vulnerable persons, expose sensitive locations, confuse official authority, or create operational risk. 7.3.19.4 Where misinformation risk is identified, Nexus outputs shall be corrected, restricted, delayed, withdrawn, superseded, archived, or routed to competent actors. 7.3.19.5 The constitutional rule shall be: **Correct crisis misinformation without amplifying the harm.** ### 7.3.20 Post-Crisis Continuation Records 7.3.20.1 Post-Crisis Continuation Records shall preserve crisis-related records after the acute phase ends so that learning, correction, accountability, safeguard review, public-safe reporting, technical readiness, finance-readiness, insurance-readiness, policy learning, and lawful handoff may continue. 7.3.20.2 Post-Crisis Continuation Records may include:\ a. risk signal records;\ b. dependency maps;\ c. crisis scenario records;\ d. public-safe reports;\ e. correction records;\ f. misinformation correction records;\ g. data safeguard records;\ h. community safeguard records;\ i. humanitarian interface records;\ j. public authority boundary records;\ k. finance-readiness notes;\ l. insurance-readiness questions;\ m. lawful handoff records;\ n. archive and re-entry records. 7.3.20.3 Post-crisis continuation shall identify what changed, what was tested, what evidence improved, what assumptions failed, what safeguards changed, what claims were corrected, what outputs were withdrawn, what handoff occurred, and what remains unresolved. 7.3.20.4 Post-crisis continuation shall not imply official evaluation authority, public inquiry authority, humanitarian evaluation authority, needs assessment authority, relief allocation authority, protection mandate, public authority approval, or implementation authority. 7.3.20.5 The constitutional rule shall be: **A crisis record remains useful only if its lessons, corrections, safeguards, and unresolved issues continue lawfully after the crisis.** ## 7.4 Infrastructure Investment Layer ### 7.4.0 Status, Purpose, and Governing Effect 7.4.0.1 This Section establishes the Infrastructure Investment Layer as the Nexus architecture through which infrastructure exposure records, climate resilience records, water-energy-food-health-biodiversity dependencies, critical infrastructure risk records, technical testing, digital twin outputs, finance-readiness notes, insurance-readiness questions, social and community safeguard records, public authority boundary records, procurement boundary records, environmental and biodiversity risk records, data-quality notes, verification records, infrastructure portfolio readiness records, pre-procurement learning records, and market-sounding boundary records may be organized for lawful downstream review. 7.4.0.2 The Infrastructure Investment Layer shall support National Nexus Consortiums, Regional Nexus Consortiums, Nexus Core, Nexus Network, Nexus Universe, Nexus Registry, Nexus Reports, Nexus Rails, development-finance readiness, public finance readability, infrastructure finance readiness, climate finance readiness, disaster risk finance readiness, capital-readability, insurance-readiness, public authority learning, and lawful handoff pathways. 7.4.0.3 The Infrastructure Investment Layer shall not be treated as investment advice, financial promotion, securities offering, capital raising, project finance approval, bankability determination, financeability determination, insurability determination, underwriting, insurance placement, procurement approval, engineering approval, environmental approval, public authority approval, social license, community consent, Indigenous consent, sponsor endorsement, provider endorsement, or implementation authorization. 7.4.0.4 Nexus may make infrastructure records more coherent, evidence-bounded, technically reviewable, digitally modeled, finance-readable, insurance-relevant, safeguard-aware, public-safe, correction-ready, and lawfully handoff-ready. Nexus shall not decide whether an infrastructure project is investable, bankable, insurable, procureable, approved, permitted, consented to, or ready for implementation. 7.4.0.5 Infrastructure investment-facing records shall be product-neutral, no-advice, no-offer, no-allocation, no-bankability, no-financeability, no-insurability, no-procurement-approval, public-safe, decision-use-labeled, and continued through Nexus Rails where material. 7.4.0.6 The governing rule of this Section is: **Nexus may prepare infrastructure readiness records for lawful downstream review. Nexus does not provide investment advice, approve procurement, determine bankability, determine insurability, or authorize infrastructure implementation.** ### 7.4.1 Infrastructure Exposure Records 7.4.1.1 Infrastructure Exposure Records shall identify the exposure of infrastructure systems, assets, corridors, networks, facilities, services, and dependencies to hazards, stressors, failures, and systemic risks. 7.4.1.2 Infrastructure exposure may include physical exposure, climate exposure, cyber exposure, operational exposure, public finance exposure, supply-chain exposure, social exposure, environmental exposure, digital dependency, interdependency, and cascading-failure risk. 7.4.1.3 An Infrastructure Exposure Record shall identify:\ a. infrastructure system or asset category;\ b. exposure type;\ c. hazard or stressor;\ d. affected services;\ e. dependency pathways;\ f. evidence basis;\ g. data quality;\ h. owner or operator boundary where known;\ i. public authority boundary;\ j. security sensitivity;\ k. public-safe reporting limit;\ l. correction pathway;\ m. Nexus Rails continuation status. 7.4.1.4 Infrastructure Exposure Records shall not imply engineering certification, safety approval, asset valuation, procurement readiness, project approval, financeability, insurability, or implementation authority. 7.4.1.5 The constitutional rule shall be: **Infrastructure exposure records make risk visible. They do not approve infrastructure or investment.** ### 7.4.2 Climate Resilience Records 7.4.2.1 Climate Resilience Records shall document climate hazards, adaptation needs, infrastructure stress, service continuity risks, public finance exposure, community vulnerability, nature-related dependencies, and resilience measures relevant to infrastructure pathways. 7.4.2.2 Climate Resilience Records may address heat, flood, storm, drought, wildfire, sea-level exposure, coastal erosion, water stress, energy stress, food-system dependency, health-system impacts, biodiversity loss, and disaster recovery implications. 7.4.2.3 A Climate Resilience Record shall identify:\ a. climate hazard or stressor;\ b. infrastructure system affected;\ c. exposure and vulnerability;\ d. scenario basis where applicable;\ e. uncertainty;\ f. adaptation relevance;\ g. safeguard status;\ h. public authority boundary;\ i. climate finance-readiness boundary;\ j. insurance-readiness questions;\ k. correction pathway;\ l. continuation status. 7.4.2.4 Climate Resilience Records shall not imply adaptation approval, climate finance approval, environmental approval, project approval, investment advice, underwriting, financeability, insurability, or implementation authorization. 7.4.2.5 The constitutional rule shall be: **Climate resilience records prepare infrastructure learning. They do not approve adaptation finance or implementation.** ### 7.4.3 Water-Energy-Food-Health-Biodiversity Dependencies 7.4.3.1 Infrastructure Investment Layer records shall identify water-energy-food-health-biodiversity dependencies where infrastructure performance, resilience, finance-readiness, public finance exposure, insurance relevance, or social safeguards depend on central nexus systems. 7.4.3.2 Dependency records may include:\ a. water infrastructure reliance on energy;\ b. energy infrastructure reliance on water;\ c. food logistics reliance on energy and transport;\ d. health-system reliance on water, sanitation, energy, and supply chains;\ e. biodiversity contribution to flood, heat, disease, soil, and water resilience;\ f. public finance exposure from cascading system failure;\ g. protection-gap implications. 7.4.3.3 A Dependency Record shall identify:\ a. systems connected;\ b. dependency pathway;\ c. affected infrastructure;\ d. evidence basis;\ e. data quality;\ f. scenario or stress-test relevance;\ g. public authority boundaries;\ h. community and Indigenous knowledge safeguards where applicable;\ i. finance-readiness relevance;\ j. insurance-readiness questions;\ k. correction pathway;\ l. Nexus Rails continuation. 7.4.3.4 Dependency records shall not allocate water, direct energy systems, decide food policy, issue health orders, approve biodiversity interventions, approve procurement, determine financeability, determine insurability, or authorize implementation. 7.4.3.5 The constitutional rule shall be: **Infrastructure readiness must record central nexus dependencies before infrastructure value is overstated.** ### 7.4.4 Critical Infrastructure Risk Records 7.4.4.1 Critical Infrastructure Risk Records shall document exposure, dependencies, vulnerabilities, stress conditions, cyber risks, physical risks, operational risks, service continuity risks, and cascading failure risks affecting essential infrastructure functions. 7.4.4.2 Critical infrastructure may include water, energy, health, food logistics, transport, ports, aviation, telecommunications, digital infrastructure, financial infrastructure, emergency services, public administration, sanitation, and other systems essential to public continuity. 7.4.4.3 A Critical Infrastructure Risk Record shall identify:\ a. critical function;\ b. infrastructure system;\ c. risk condition;\ d. dependency pathway;\ e. security sensitivity;\ f. cyber sensitivity;\ g. owner or operator boundary;\ h. public authority boundary;\ i. public-safe reporting limit;\ j. technical-readiness requirement;\ k. correction pathway;\ l. continuation status. 7.4.4.4 Critical Infrastructure Risk Records shall not disclose sensitive vulnerabilities, certify infrastructure, approve interventions, direct operators, approve procurement, approve finance, underwrite risks, or authorize implementation. 7.4.4.5 The constitutional rule shall be: **Critical infrastructure records must protect the systems they make visible.** ### 7.4.5 Technical Testing 7.4.5.1 Technical Testing may be used to examine infrastructure exposure, failure modes, dependencies, digital twin outputs, scenario performance, cyber resilience, data quality, model assumptions, public-safe dashboard outputs, and critical application performance. 7.4.5.2 Technical Testing may occur through Nexus Core, Nexus Network, secure data environments, compute-to-data environments, cyber ranges, digital twin environments, sector-specific testing environments, and verification workflows. 7.4.5.3 A Technical Testing Record shall identify:\ a. infrastructure question tested;\ b. test scope;\ c. test environment;\ d. data used;\ e. model or method;\ f. assumptions;\ g. limitations;\ h. security review;\ i. verification status;\ j. public-safe label;\ k. correction pathway;\ l. continuation status. 7.4.5.4 Technical Testing shall not imply engineering approval, safety certification, operational authorization, technology endorsement, procurement approval, financeability, insurability, or implementation readiness. 7.4.5.5 The constitutional rule shall be: **Technical testing strengthens the infrastructure record. It does not approve infrastructure action.** ### 7.4.6 Digital Twin Outputs 7.4.6.1 Digital Twin Outputs may represent infrastructure systems, corridors, basins, grids, cities, logistics systems, health capacity, climate adaptation pathways, public finance exposure, finance-readiness exposure, and insurance protection gaps. 7.4.6.2 Digital Twin Outputs shall be governed by data governance, model governance, verification records, public-safe labels, decision-use labels, publication boundaries, correction pathways, and Nexus Rails continuation. 7.4.6.3 A Digital Twin Output Record shall identify:\ a. twin or model used;\ b. system represented;\ c. output purpose;\ d. data sources;\ e. model assumptions;\ f. uncertainty;\ g. limitations;\ h. verification status;\ i. public-safe publication limit;\ j. prohibited interpretations;\ k. correction pathway;\ l. continuation status. 7.4.6.4 Digital Twin Outputs shall not be treated as reality, official system models, engineering approvals, investment conclusions, underwriting conclusions, procurement approvals, financeability determinations, insurability determinations, or implementation authorizations. 7.4.6.5 The constitutional rule shall be: **Digital twin outputs are decision-support artifacts. They are not the infrastructure, the approval, or the investment decision.** ### 7.4.7 Finance-Readiness Notes 7.4.7.1 Finance-Readiness Notes shall organize infrastructure records so that competent downstream finance-facing actors may understand risk, resilience, exposure, evidence, technical readiness, public authority boundaries, procurement boundaries, safeguard status, and diligence gaps. 7.4.7.2 Finance-Readiness Notes may address development-finance readiness, infrastructure finance readiness, climate finance readiness, disaster risk finance readiness, public finance readability, resilience investment readiness, and capital-readability. 7.4.7.3 An Infrastructure Finance-Readiness Note shall identify:\ a. source infrastructure record;\ b. finance-readiness purpose;\ c. evidence status;\ d. technical-readiness status;\ e. public authority boundary;\ f. procurement boundary;\ g. environmental and social safeguard status;\ h. community consent boundary;\ i. no-advice status;\ j. no-offer status;\ k. no-financeability status;\ l. diligence gaps;\ m. correction pathway;\ n. continuation status. 7.4.7.4 Finance-Readiness Notes shall not imply investment advice, financial promotion, securities offering, lending approval, capital allocation, guarantee, rating, bankability, financeability, public finance approval, procurement approval, or market execution. 7.4.7.5 The constitutional rule shall be: **Finance-readiness notes make infrastructure records readable. They do not make infrastructure financeable.** ### 7.4.8 Insurance-Readiness Questions 7.4.8.1 Insurance-Readiness Questions shall organize infrastructure exposure, data gaps, protection-gap signals, resilience measures, public asset exposure, loss-relevance questions, and disaster risk finance relevance for lawful downstream review by competent insurance-facing actors. 7.4.8.2 An Infrastructure Insurance-Readiness Question Record shall identify:\ a. exposure category;\ b. infrastructure system;\ c. protection-gap signal;\ d. data status;\ e. evidence gaps;\ f. resilience relevance;\ g. market-conduct boundary;\ h. no-underwriting boundary;\ i. no-pricing boundary;\ j. no-coverage boundary;\ k. public-safe reporting limit;\ l. correction pathway;\ m. continuation status. 7.4.8.3 Insurance-Readiness Questions shall not imply underwriting, pricing, coverage, claims determination, insurance placement, brokerage, reinsurance placement, risk acceptance, insurance advice, insurability, or insurance product approval. 7.4.8.4 The constitutional rule shall be: **Insurance-readiness questions frame infrastructure exposure. They do not underwrite infrastructure risk.** ### 7.4.9 Social and Community Safeguard Records 7.4.9.1 Social and Community Safeguard Records shall document infrastructure-related participation, benefit and risk distribution, displacement risk, access impacts, affordability concerns, livelihood impacts, cultural heritage concerns, Indigenous knowledge safeguards, consent boundaries, grievance and feedback pathways, privacy safeguards, and unresolved issues. 7.4.9.2 A Social and Community Safeguard Record shall identify:\ a. infrastructure pathway or record;\ b. affected community or group where appropriate and safe;\ c. participation scope;\ d. benefit and risk distribution;\ e. consent boundary;\ f. privacy and protection safeguards;\ g. unresolved issues;\ h. public-safe reporting limits;\ i. correction pathway;\ j. handoff or continuation status. 7.4.9.3 Community participation shall not imply social license, community consent, Indigenous consent, public approval, project authorization, finance approval, procurement approval, data ownership transfer, or implementation authorization. 7.4.9.4 Social and Community Safeguard Records shall not be used to expose vulnerable people, sensitive locations, cultural knowledge, Indigenous knowledge, legal status, household vulnerability, or consent-sensitive information. 7.4.9.5 The constitutional rule shall be: **Infrastructure safeguard records protect participation and risk visibility without granting consent or approval.** ### 7.4.10 Public Authority Boundary Records 7.4.10.1 Public Authority Boundary Records shall document whether and how competent public authorities, regulators, utilities, municipalities, ministries, public finance institutions, or public agencies have been engaged, referenced, or identified in relation to infrastructure readiness records. 7.4.10.2 A Public Authority Boundary Record shall identify:\ a. competent actor where appropriate;\ b. engagement purpose;\ c. mandate status;\ d. approval status;\ e. records shared or reviewed;\ f. public language boundary;\ g. confidentiality conditions;\ h. correction pathway;\ i. handoff or continuation status. 7.4.10.3 Public authority engagement shall not imply public authority approval, government endorsement, official adoption, regulatory approval, procurement approval, public finance approval, official consultation, mandate, or implementation authorization unless separately and lawfully documented. 7.4.10.4 Public authority boundary records shall be corrected where proximity, participation, correspondence, review, or visibility is overstated as approval or mandate. 7.4.10.5 The constitutional rule shall be: **Public authority boundaries must be recorded before infrastructure readiness is mistaken for public approval.** ### 7.4.11 Procurement Boundary Records 7.4.11.1 Procurement Boundary Records shall prevent infrastructure readiness records, technical testing, provider participation, sponsor support, market-sounding activity, public-safe reports, finance-readiness notes, and Nexus Universe visibility from being misused as procurement approval or supplier preference. 7.4.11.2 A Procurement Boundary Record shall identify:\ a. infrastructure pathway or record;\ b. procurement-sensitive context;\ c. provider participation where applicable;\ d. sponsor participation where applicable;\ e. public authority boundary;\ f. no-procurement-approval status;\ g. no-preferred-supplier status;\ h. no-technical-award status;\ i. no-market-advantage status;\ j. public-safe language controls;\ k. correction pathway;\ l. continuation status. 7.4.11.3 Nexus shall not approve procurement, prequalify suppliers, recommend vendors, rank bidders, direct public procurement, approve technical specifications for procurement, or create preferred supplier status unless separately and lawfully authorized. 7.4.11.4 The constitutional rule shall be: **Infrastructure readiness may inform learning before procurement. It shall not become procurement approval.** ### 7.4.12 Environmental and Biodiversity Risk Records 7.4.12.1 Environmental and Biodiversity Risk Records shall document infrastructure-related ecosystem impacts, biodiversity dependencies, land-use sensitivities, watershed effects, coastal effects, pollution risks, habitat risks, species sensitivity, nature-based resilience, cultural landscape issues, and environmental safeguard questions. 7.4.12.2 An Environmental and Biodiversity Risk Record shall identify:\ a. infrastructure pathway or system;\ b. environmental or biodiversity risk;\ c. data sources;\ d. sensitive location controls;\ e. environmental authority boundary;\ f. land-use authority boundary;\ g. community and Indigenous knowledge safeguards;\ h. public-safe publication limits;\ i. finance-readiness relevance;\ j. insurance-readiness questions;\ k. correction pathway;\ l. continuation status. 7.4.12.3 Environmental and Biodiversity Risk Records shall not imply environmental approval, permitting approval, land-use approval, offset validation, nature-finance validation, community consent, Indigenous consent, financeability, insurability, or implementation authorization. 7.4.12.4 The constitutional rule shall be: **Environmental and biodiversity records must protect ecosystems and knowledge while refusing false approval claims.** ### 7.4.13 Data-Quality Notes 7.4.13.1 Data-Quality Notes shall identify the suitability, limitations, uncertainty, provenance, lineage, completeness, timeliness, coverage, resolution, bias, and permitted use of data supporting infrastructure readiness records. 7.4.13.2 A Data-Quality Note shall identify:\ a. dataset or derived output;\ b. source;\ c. provenance;\ d. lineage;\ e. quality condition;\ f. completeness;\ g. timeliness;\ h. uncertainty;\ i. sensitivity level;\ j. permitted use;\ k. public-safe publishing limit;\ l. correction pathway;\ m. continuation status. 7.4.13.3 Data-quality acceptance shall not imply data certification, official statistics, public authority approval, engineering approval, procurement readiness, financeability, insurability, or implementation readiness. 7.4.13.4 Data-quality gaps shall be visible where they affect infrastructure exposure records, digital twin outputs, finance-readiness notes, insurance-readiness questions, public-safe reports, or lawful handoff. 7.4.13.5 The constitutional rule shall be: **Infrastructure data must be fit for the claim made, not merely available.** ### 7.4.14 Verification Records 7.4.14.1 Verification Records shall document bounded verification of infrastructure-related evidence, data, models, simulations, digital twin outputs, stress tests, technical testing, public-safe dashboards, finance-readiness notes, and insurance-readiness questions. 7.4.14.2 An Infrastructure Verification Record shall identify:\ a. item verified;\ b. verification scope;\ c. evidence reviewed;\ d. data-quality controls;\ e. method or model reviewed;\ f. assumptions;\ g. limitations;\ h. security review where applicable;\ i. public-safe label;\ j. decision-use label;\ k. verification receipt status;\ l. correction pathway;\ m. continuation status. 7.4.14.3 Verification shall not imply certification, engineering approval, regulatory approval, procurement approval, public authority approval, financeability, insurability, professional assurance, technology endorsement, or implementation authorization. 7.4.14.4 Verification records shall be corrected, downgraded, withdrawn, superseded, archived, or re-entered where evidence, data, methods, models, security status, public-safe use, or decision-use changes. 7.4.14.5 The constitutional rule shall be: **Infrastructure verification strengthens the record within scope. It does not certify the infrastructure or approve the project.** ### 7.4.15 Infrastructure Portfolio Readiness Records 7.4.15.1 Infrastructure Portfolio Readiness Records shall organize infrastructure pathways, exposure records, climate resilience records, dependency records, safeguard records, technical testing records, digital twin outputs, data-quality notes, verification records, finance-readiness notes, insurance-readiness questions, public authority boundaries, procurement boundaries, and lawful handoff conditions. 7.4.15.2 An Infrastructure Portfolio Readiness Record shall identify:\ a. portfolio or pathway;\ b. infrastructure category;\ c. readiness purpose;\ d. exposure status;\ e. technical-readiness status;\ f. safeguard status;\ g. public authority boundary;\ h. procurement boundary;\ i. environmental and biodiversity boundary;\ j. finance-readiness status;\ k. insurance-readiness questions;\ l. diligence gaps;\ m. correction pathway;\ n. Nexus Rails continuation status. 7.4.15.3 Infrastructure Portfolio Readiness Records shall not be treated as investment memoranda, offering documents, procurement packages, appraisal documents, underwriting submissions, feasibility approvals, bankability determinations, insurability determinations, or implementation dossiers unless separately and lawfully authorized. 7.4.15.4 The constitutional rule shall be: **Infrastructure portfolio readiness organizes the record for review. It does not approve the portfolio for finance, insurance, procurement, or delivery.** ### 7.4.16 Pre-Procurement Learning 7.4.16.1 Pre-Procurement Learning shall support public-safe, product-neutral, supplier-neutral, no-award, no-approval learning before any competent procurement actor decides whether to initiate or conduct procurement. 7.4.16.2 Pre-Procurement Learning may address:\ a. risk evidence;\ b. infrastructure exposure;\ c. technical-readiness questions;\ d. data gaps;\ e. safeguard issues;\ f. public authority boundaries;\ g. procurement risks;\ h. provider boundary controls;\ i. market-sounding limits;\ j. public-safe reporting controls;\ k. correction pathways. 7.4.16.3 Pre-Procurement Learning shall not approve procurement, define binding specifications, shortlist suppliers, rank providers, recommend vendors, grant preferred supplier status, create procurement advantage, or substitute for public procurement procedures. 7.4.16.4 Where provider participation occurs, provider controls and procurement boundary records shall be mandatory. 7.4.16.5 The constitutional rule shall be: **Pre-procurement learning prepares questions before procurement. It does not conduct procurement.** ### 7.4.17 Market-Sounding Boundaries 7.4.17.1 Market-Sounding Boundaries shall govern infrastructure-related discussions with providers, sponsors, investors, insurers, lenders, technical partners, public finance actors, and other market participants. 7.4.17.2 Market-sounding records shall identify:\ a. purpose;\ b. participants;\ c. topic scope;\ d. information shared;\ e. no-advice status;\ f. no-offer status;\ g. no-procurement-approval status;\ h. no-financeability status;\ i. no-insurability status;\ j. competition safeguards;\ k. conflict disclosures;\ l. correction pathway;\ m. continuation status. 7.4.17.3 Market-sounding shall not become investment solicitation, securities offering, procurement negotiation, supplier prequalification, bid coordination, price coordination, market allocation, underwriting discussion, coverage placement, or capital allocation. 7.4.17.4 Where market-sounding risks creating false procurement, finance, insurance, or market signals, the activity shall be paused, restricted, corrected, restructured, withdrawn, archived, or routed to competent actors. 7.4.17.5 The constitutional rule shall be: **Market sounding may inform readiness questions. It shall not become market coordination or transaction activity.** ### 7.4.18 Infrastructure Readiness Without Bankability 7.4.18.1 Infrastructure readiness shall not be described as bankability. 7.4.18.2 Infrastructure readiness may include exposure records, technical-readiness records, safeguard records, data-quality notes, verification records, public authority boundary records, procurement boundary records, finance-readiness notes, insurance-readiness questions, and lawful handoff records. 7.4.18.3 None of these records shall imply bankability, credit approval, lending approval, guarantee, debt capacity, project finance approval, capital allocation, public finance approval, investment advice, securities offering, or financeability determination. 7.4.18.4 Bankability, where relevant, may be assessed only by competent finance-facing actors within their own lawful mandates, credit procedures, risk frameworks, investment policies, approvals, and regulatory obligations. 7.4.18.5 The constitutional rule shall be: **Infrastructure readiness may make records more reviewable. It does not make infrastructure bankable.** ### 7.4.19 Infrastructure Readiness Without Insurability 7.4.19.1 Infrastructure readiness shall not be described as insurability. 7.4.19.2 Infrastructure readiness may include exposure records, protection-gap signals, data-quality notes, resilience measure descriptions, risk engineering questions, disaster risk finance readiness records, and insurance-readiness questions. 7.4.19.3 None of these records shall imply underwriting, pricing, coverage, claims determination, risk acceptance, insurance placement, brokerage, reinsurance placement, insurance advice, or insurability determination. 7.4.19.4 Insurability, where relevant, may be assessed only by competent insurance or reinsurance actors operating within their own lawful underwriting, actuarial, regulatory, market, and professional duties. 7.4.19.5 The constitutional rule shall be: **Infrastructure readiness may frame insurance-relevance questions. It does not make infrastructure insurable.** ### 7.4.20 Infrastructure Readiness Without Procurement Approval 7.4.20.1 Infrastructure readiness shall not be described as procurement approval. 7.4.20.2 Infrastructure readiness may include technical testing, provider demonstrations, data-quality records, exposure records, safeguard records, digital twin outputs, verification receipts, and pre-procurement learning records. 7.4.20.3 None of these records shall approve procurement, prequalify suppliers, rank bidders, recommend vendors, create preferred supplier status, approve specifications, authorize public purchasing, or substitute for public procurement law and procedures. 7.4.20.4 Procurement may be initiated, designed, evaluated, approved, or awarded only by competent procurement actors operating within their own lawful authority, rules, procedures, conflicts controls, accountability, and review mechanisms. 7.4.20.5 The constitutional rule shall be: **Infrastructure readiness may support pre-procurement learning. It does not approve procurement.** ### 7.4.21 Infrastructure Readiness Without Investment Advice 7.4.21.1 Infrastructure readiness shall not be described as investment advice. 7.4.21.2 Infrastructure readiness may make infrastructure risk more readable through evidence, exposure records, digital twin outputs, scenario records, technical-readiness records, safeguard records, finance-readiness notes, diligence gap maps, and lawful handoff records. 7.4.21.3 None of these records shall recommend buying, selling, holding, financing, lending, investing, underwriting, guaranteeing, allocating capital, entering a transaction, issuing securities, or approving an infrastructure opportunity. 7.4.21.4 Investment decisions may be made only by competent actors operating within their own mandates, fiduciary duties, regulatory obligations, investment policies, risk frameworks, approvals, and accountability structures. 7.4.21.5 The constitutional rule shall be: **Infrastructure readiness can make risk legible to investors. It shall not advise investment.** ## 7.5 Sovereign and Public Finance Layer ### 7.5.0 Status, Purpose, and Governing Effect 7.5.0.1 This Section establishes the Sovereign and Public Finance Layer as the Nexus architecture through which public finance stress records, disaster contingent liability mapping, sovereign resilience exposure, infrastructure exposure, insurance protection gaps, climate adaptation readiness, food and energy security exposure, health-system fiscal risk, biodiversity and natural capital dependencies, development-finance readiness, sovereign fund risk-readiness, national resilience portfolio records, fiscal risk learning records, contingent liability records, and public-safe reporting may be organized for bounded learning and lawful downstream review. 7.5.0.2 The Sovereign and Public Finance Layer shall support National Nexus Consortiums, Regional Nexus Consortiums, Nexus Core, Nexus Network, Nexus Universe, Nexus Registry, Nexus Reports, Nexus Rails, development-finance readiness, public finance readability, infrastructure finance readiness, climate finance readiness, disaster risk finance readiness, sovereign fund readability, policy learning, mandate-readiness, and lawful handoff pathways. 7.5.0.3 The Sovereign and Public Finance Layer shall not be treated as sovereign borrowing advice, debt policy advice, fiscal policy advice, monetary policy advice, tax advice, investment advice, sovereign credit analysis, sovereign rating, public finance approval, budget approval, appropriation decision, public debt management, development bank approval, climate finance approval, disaster risk finance approval, procurement approval, financeability determination, insurability determination, guarantee, underwriting, or implementation authorization. 7.5.0.4 Nexus may make sovereign and public finance exposure more coherent, evidence-bounded, technically reviewable, climate-aware, disaster-aware, infrastructure-aware, food-security-aware, energy-security-aware, health-system-aware, biodiversity-aware, finance-readable, insurance-relevant, public-safe, correction-ready, and lawfully continuable. Nexus shall not decide fiscal policy, debt policy, monetary policy, tax policy, public borrowing, public expenditure, public investment, sovereign allocation, public finance approval, or public authority action. 7.5.0.5 Sovereign and public finance-facing records shall be non-advisory, non-rating, no-borrowing-advice, no-debt-policy-advice, no-fiscal-policy-advice, no-monetary-policy-advice, no-investment-advice, no-public-finance-approval, public-safe, decision-use-labeled, correction-ready, and continued through Nexus Rails where material. 7.5.0.6 The governing rule of this Section is: **Nexus may make sovereign and public finance risk more readable by record. Nexus does not advise borrowing, debt, fiscal policy, monetary policy, investment, public finance approval, or public expenditure.** ### 7.5.1 Public Finance Stress Records 7.5.1.1 Public Finance Stress Records shall document how hazards, shocks, chronic stressors, infrastructure failure, health-system pressure, food and energy insecurity, climate adaptation needs, biodiversity loss, disaster recovery costs, and contingent liabilities may affect public finance exposure. 7.5.1.2 Public Finance Stress Records may support public finance readability, policy-learning records, development-finance readiness, climate finance readiness, disaster risk finance readiness, national resilience portfolio records, public-safe reports, and lawful handoff records. 7.5.1.3 A Public Finance Stress Record shall identify:\ a. stressor or risk event;\ b. affected public finance area;\ c. evidence basis;\ d. exposure pathway;\ e. uncertainty;\ f. assumptions;\ g. public authority boundary;\ h. fiscal advice boundary;\ i. public-safe reporting limit;\ j. correction pathway;\ k. Nexus Rails continuation status. 7.5.1.4 Public Finance Stress Records shall not provide fiscal forecasts, budget advice, debt advice, tax advice, monetary advice, public finance approval, appropriation decisions, public borrowing advice, financeability determination, or implementation authorization. 7.5.1.5 The constitutional rule shall be: **Public finance stress records make fiscal exposure visible. They do not decide fiscal policy.** ### 7.5.2 Disaster Contingent Liability Mapping 7.5.2.1 Disaster Contingent Liability Mapping shall identify potential public financial exposure arising from disasters, recovery obligations, public asset damage, emergency response costs, infrastructure restoration, social protection needs, public health surge, housing and shelter needs, and resilience gaps. 7.5.2.2 Disaster Contingent Liability Mapping may support disaster risk finance readiness, insurance-readiness questions, protection-gap intelligence, public finance readability, development-finance readiness, national resilience portfolio records, and public authority learning. 7.5.2.3 A Disaster Contingent Liability Map Record shall identify:\ a. disaster risk or hazard;\ b. affected public asset or public function;\ c. potential liability pathway;\ d. evidence basis;\ e. data quality;\ f. uncertainty;\ g. assumptions;\ h. public authority boundary;\ i. no-fiscal-advice status;\ j. insurance-readiness questions;\ k. correction pathway;\ l. continuation status. 7.5.2.4 Disaster Contingent Liability Mapping shall not imply official fiscal estimates, public finance approval, budget allocation, debt advice, contingent credit approval, insurance approval, underwriting, financeability, insurability, or implementation authority. 7.5.2.5 The constitutional rule shall be: **Disaster contingent liability mapping frames fiscal exposure questions. It does not approve or advise public finance response.** ### 7.5.3 Sovereign Resilience Exposure 7.5.3.1 Sovereign Resilience Exposure shall identify national-level exposure to risks that may affect resilience, public services, public finance, infrastructure continuity, food and energy security, health systems, water security, biodiversity, social cohesion, development capacity, and regional stability. 7.5.3.2 Sovereign Resilience Exposure records may support national resilience portfolio records, public finance stress records, development-finance readiness, sovereign fund risk-readiness, policy-learning records, and lawful handoff. 7.5.3.3 A Sovereign Resilience Exposure Record shall identify:\ a. sovereign resilience theme;\ b. affected national system;\ c. evidence basis;\ d. exposure pathway;\ e. uncertainty;\ f. public authority boundary;\ g. no-rating boundary;\ h. no-borrowing-advice boundary;\ i. no-fiscal-policy-advice boundary;\ j. public-safe reporting limit;\ k. correction pathway;\ l. continuation status. 7.5.3.4 Sovereign Resilience Exposure records shall not be described as sovereign ratings, sovereign credit views, macroeconomic assessments, debt sustainability assessments, fiscal policy advice, borrowing advice, public finance approval, investment advice, or implementation authorization. 7.5.3.5 The constitutional rule shall be: **Sovereign resilience exposure makes national risk readable without becoming sovereign rating, advice, or authority.** ### 7.5.4 Infrastructure Exposure 7.5.4.1 Infrastructure Exposure records shall identify how public infrastructure, critical infrastructure, natural infrastructure, social infrastructure, and digital infrastructure may create or transmit public finance exposure. 7.5.4.2 Infrastructure exposure may include public asset damage, service disruption, maintenance backlog, climate adaptation costs, disaster recovery costs, cyber disruption, health-system infrastructure pressure, water and energy system failure, transport disruption, and public-private interface risk. 7.5.4.3 An Infrastructure Exposure Record under this Layer shall identify:\ a. infrastructure system;\ b. public finance exposure pathway;\ c. hazard or stressor;\ d. affected public service;\ e. evidence basis;\ f. data quality;\ g. owner or operator boundary where known;\ h. public authority boundary;\ i. procurement boundary;\ j. no-financeability status;\ k. correction pathway;\ l. continuation status. 7.5.4.4 Infrastructure Exposure records shall not imply engineering approval, public investment approval, procurement approval, public finance approval, bankability, financeability, insurability, or implementation authority. 7.5.4.5 The constitutional rule shall be: **Infrastructure exposure records show where public finance may be exposed. They do not approve infrastructure finance or delivery.** ### 7.5.5 Insurance Protection Gaps 7.5.5.1 Insurance Protection Gaps shall identify where public assets, households, infrastructure, agriculture, health systems, businesses, communities, or sovereign exposure may exceed existing insurance or risk-transfer arrangements. 7.5.5.2 Protection-gap records may support disaster risk finance readiness, public finance readability, insurance-readiness questions, climate adaptation readiness, infrastructure exposure records, and national resilience portfolio records. 7.5.5.3 An Insurance Protection Gap Record shall identify:\ a. exposure category;\ b. protection-gap signal;\ c. affected public finance pathway;\ d. data sources;\ e. data gaps;\ f. resilience relevance;\ g. market-conduct boundary;\ h. no-underwriting boundary;\ i. no-pricing boundary;\ j. no-coverage boundary;\ k. public-safe reporting limit;\ l. correction pathway. 7.5.5.4 Insurance Protection Gap records shall not imply underwriting, pricing, coverage, claims determination, insurance placement, brokerage, reinsurance placement, risk acceptance, insurance advice, insurability, or public finance approval. 7.5.5.5 The constitutional rule shall be: **Protection-gap records make insurance-readiness questions visible. They do not insure public finance exposure.** ### 7.5.6 Climate Adaptation Readiness 7.5.6.1 Climate Adaptation Readiness shall organize climate risk records, exposure records, adaptation needs, resilience logic, infrastructure stress records, public finance exposure records, community safeguard records, environmental risk records, finance-readiness notes, and lawful handoff conditions. 7.5.6.2 Climate Adaptation Readiness may address heat, flood, drought, wildfire, storm, sea-level exposure, coastal erosion, water stress, food-system stress, health impacts, infrastructure adaptation, biodiversity resilience, and disaster recovery exposure. 7.5.6.3 A Climate Adaptation Readiness Record shall identify:\ a. climate risk or adaptation theme;\ b. affected public system;\ c. evidence basis;\ d. scenario assumptions where applicable;\ e. uncertainty;\ f. safeguard status;\ g. public authority boundary;\ h. public finance boundary;\ i. climate finance-readiness boundary;\ j. insurance-readiness questions;\ k. correction pathway;\ l. continuation status. 7.5.6.4 Climate Adaptation Readiness shall not imply adaptation approval, climate finance approval, public finance approval, environmental approval, procurement approval, investment advice, financeability, insurability, or implementation authorization. 7.5.6.5 The constitutional rule shall be: **Climate adaptation readiness makes climate exposure reviewable. It does not approve climate finance, policy, or implementation.** ### 7.5.7 Food and Energy Security Exposure 7.5.7.1 Food and Energy Security Exposure records shall document how food-system risks and energy-system risks may affect public finance, public services, social protection, health systems, infrastructure, supply chains, import dependency, affordability, public trust, and resilience. 7.5.7.2 Food and Energy Security Exposure records may support public finance stress records, sovereign resilience exposure, national resilience portfolio records, disaster risk finance readiness, public authority learning, and public-safe reporting. 7.5.7.3 A Food and Energy Security Exposure Record shall identify:\ a. food or energy exposure pathway;\ b. affected public finance or public service function;\ c. dependency links;\ d. evidence basis;\ e. data quality;\ f. market-conduct boundary;\ g. public authority boundary;\ h. trade-policy boundary where relevant;\ i. no-fiscal-policy-advice status;\ j. public-safe reporting limit;\ k. correction pathway;\ l. continuation status. 7.5.7.4 Food and Energy Security Exposure records shall not allocate food, direct energy systems, decide subsidies, approve tariffs, set trade policy, approve public finance, coordinate markets, approve procurement, or authorize implementation. 7.5.7.5 The constitutional rule shall be: **Food and energy security exposure records show fiscal and resilience dependencies without deciding food, energy, or fiscal policy.** ### 7.5.8 Health-System Fiscal Risk 7.5.8.1 Health-System Fiscal Risk shall identify public finance exposure arising from health-system surge, service disruption, workforce gaps, infrastructure stress, public health emergencies, climate-health effects, water and sanitation failures, food insecurity, supply-chain disruption, digital health dependency, and biosecurity risk. 7.5.8.2 Health-System Fiscal Risk records may support public finance stress records, public health learning, pandemic and biosecurity scenario records, development-finance readiness, insurance-readiness questions, and lawful handoff. 7.5.8.3 A Health-System Fiscal Risk Record shall identify:\ a. health-system stressor;\ b. affected fiscal or service pathway;\ c. evidence basis;\ d. health data sensitivity;\ e. privacy controls;\ f. public health authority boundary;\ g. clinical guidance boundary;\ h. biosecurity boundary where applicable;\ i. public-safe reporting limit;\ j. correction pathway;\ k. continuation status. 7.5.8.4 Health-System Fiscal Risk records shall not provide medical advice, clinical guidance, public health orders, fiscal advice, public finance approval, public health authority approval, procurement approval, financeability, insurability, or implementation authorization. 7.5.8.5 The constitutional rule shall be: **Health-system fiscal risk records make health-related exposure visible without becoming health authority or fiscal advice.** ### 7.5.9 Biodiversity and Natural Capital Dependencies 7.5.9.1 Biodiversity and Natural Capital Dependencies shall document how ecosystems, watersheds, forests, wetlands, soils, pollination, fisheries, coastal systems, disease regulation, disaster risk reduction, and climate adaptation functions affect public finance exposure and sovereign resilience. 7.5.9.2 Biodiversity and Natural Capital Dependency records may support public finance stress records, climate adaptation readiness, food and water security exposure, disaster risk finance readiness, environmental risk records, and public-safe reports. 7.5.9.3 A Biodiversity and Natural Capital Dependency Record shall identify:\ a. ecosystem or natural capital function;\ b. public finance or resilience dependency;\ c. evidence basis;\ d. data sensitivity;\ e. sensitive location controls;\ f. community and Indigenous knowledge safeguards;\ g. environmental authority boundary;\ h. land-use authority boundary;\ i. nature-finance boundary;\ j. correction pathway;\ k. continuation status. 7.5.9.4 Biodiversity and Natural Capital Dependency records shall not imply natural capital valuation advice, offset approval, nature-finance validation, environmental permitting, land-use approval, public finance approval, financeability, insurability, community consent, Indigenous consent, or implementation authority. 7.5.9.5 The constitutional rule shall be: **Natural capital dependency records make ecological reliance visible without approving nature finance, land use, or public finance decisions.** ### 7.5.10 Development-Finance Readiness 7.5.10.1 Development-Finance Readiness shall organize sovereign and public finance exposure records so that development-finance actors may understand resilience relevance, evidence status, safeguard status, public authority boundaries, public finance questions, diligence gaps, and lawful handoff conditions. 7.5.10.2 Development-Finance Readiness records may address climate adaptation, disaster risk reduction, public infrastructure, public health resilience, food security, energy resilience, water security, biodiversity resilience, digital public infrastructure, and national or regional resilience portfolios. 7.5.10.3 A Development-Finance Readiness Record shall identify:\ a. development relevance;\ b. source records;\ c. evidence status;\ d. public-good relevance;\ e. safeguard status;\ f. institutional capacity questions;\ g. public authority boundary;\ h. public finance boundary;\ i. procurement boundary;\ j. no-finance-approval status;\ k. diligence gaps;\ l. continuation status. 7.5.10.4 Development-Finance Readiness shall not imply development bank approval, concessional finance approval, grant approval, loan approval, guarantee, public finance approval, procurement approval, financeability, or implementation authorization. 7.5.10.5 The constitutional rule shall be: **Development-finance readiness prepares records for lawful review. It does not approve development finance.** ### 7.5.11 Sovereign Fund Risk-Readiness 7.5.11.1 Sovereign Fund Risk-Readiness shall organize resilience records, public finance exposure records, infrastructure exposure records, climate adaptation records, food and energy security exposure records, and national resilience portfolio records so that sovereign funds or state-linked investment institutions may understand risk-readiness context within their own mandates. 7.5.11.2 Sovereign Fund Risk-Readiness records shall be product-neutral, non-advisory, no-offer, no-allocation, no-financeability, no-sovereign-endorsement, and no-public-investment-approval records. 7.5.11.3 A Sovereign Fund Risk-Readiness Record shall identify:\ a. resilience theme;\ b. source records;\ c. evidence status;\ d. public finance boundary;\ e. public authority boundary;\ f. investment-advice boundary;\ g. sovereign endorsement boundary;\ h. procurement boundary;\ i. diligence gaps;\ j. no-false-capital-signal controls;\ k. correction pathway;\ l. continuation status. 7.5.11.4 Sovereign Fund Risk-Readiness shall not imply sovereign endorsement, investment approval, mandate fit, allocation approval, public investment approval, guarantee, rating, financeability, procurement approval, or implementation authority. 7.5.11.5 The constitutional rule shall be: **Sovereign fund risk-readiness supports resilience readability without advising sovereign capital.** ### 7.5.12 National Resilience Portfolio Records 7.5.12.1 National Resilience Portfolio Records shall organize country-level risk, resilience, exposure, dependency, technical-readiness, public finance, development-finance readiness, insurance-readiness, public authority learning, community safeguard, and lawful handoff records. 7.5.12.2 A National Resilience Portfolio Record may include:\ a. sovereign resilience exposure;\ b. public finance stress records;\ c. infrastructure exposure records;\ d. climate adaptation readiness records;\ e. food and energy security exposure records;\ f. health-system fiscal risk records;\ g. biodiversity and natural capital dependency records;\ h. disaster contingent liability records;\ i. insurance protection gap records;\ j. development-finance readiness records;\ k. fiscal risk learning records;\ l. mandate-readiness records;\ m. correction and continuation history. 7.5.12.3 National Resilience Portfolio Records shall identify national ownership status, mandate status, public authority boundaries, public finance boundaries, evidence status, safeguard status, decision-use labels, public-safe labels, correction pathways, and Nexus Rails continuation. 7.5.12.4 National Resilience Portfolio Records shall not imply national strategy adoption, government approval, public finance approval, sovereign borrowing approval, procurement approval, investment advice, financeability, insurability, or implementation authority. 7.5.12.5 The constitutional rule shall be: **A national resilience portfolio organizes the public finance risk record. It does not decide national fiscal or investment policy.** ### 7.5.13 Fiscal Risk Learning Records 7.5.13.1 Fiscal Risk Learning Records shall document lessons arising from public finance stress records, disaster contingent liability mapping, sovereign resilience exposure, infrastructure exposure, climate adaptation readiness, food and energy security exposure, health-system fiscal risk, biodiversity dependencies, and development-finance readiness. 7.5.13.2 A Fiscal Risk Learning Record shall identify:\ a. learning question;\ b. source records;\ c. evidence basis;\ d. public finance exposure;\ e. uncertainty;\ f. public authority boundary;\ g. no-fiscal-advice status;\ h. policy-learning relevance;\ i. correction implication;\ j. handoff or continuation status. 7.5.13.3 Fiscal Risk Learning Records shall not provide fiscal advice, debt advice, borrowing advice, tax advice, monetary advice, budget advice, public finance approval, investment advice, or implementation authorization. 7.5.13.4 Fiscal Risk Learning Records shall be corrected where learning is overstated as fiscal recommendation, budget position, debt position, official assessment, or public authority approval. 7.5.13.5 The constitutional rule shall be: **Fiscal risk learning helps institutions understand exposure. It does not advise fiscal decisions.** ### 7.5.14 Contingent Liability Records 7.5.14.1 Contingent Liability Records shall document potential public obligations, exposures, or fiscal pressures that may arise from disasters, infrastructure failure, public guarantees, public-private interfaces, climate adaptation gaps, health crises, public asset loss, social protection pressure, or resilience gaps. 7.5.14.2 A Contingent Liability Record shall identify:\ a. liability pathway;\ b. triggering risk;\ c. affected public function;\ d. evidence basis;\ e. uncertainty;\ f. assumptions;\ g. data limitations;\ h. public authority boundary;\ i. no-debt-advice status;\ j. no-budget-advice status;\ k. correction pathway;\ l. continuation status. 7.5.14.3 Contingent Liability Records shall not imply official fiscal recognition, accounting treatment, debt classification, budget allocation, sovereign borrowing advice, guarantee approval, public finance approval, or implementation authorization. 7.5.14.4 Contingent Liability Records shall be public-safe where published and restricted where fiscal sensitivity, security sensitivity, market sensitivity, or public authority sensitivity requires control. 7.5.14.5 The constitutional rule shall be: **Contingent liability records make potential exposure reviewable. They do not classify, approve, or advise public liabilities.** ### 7.5.15 Public-Safe Reporting 7.5.15.1 Public-Safe Reporting under the Sovereign and Public Finance Layer shall communicate selected sovereign resilience, public finance stress, contingent liability, infrastructure exposure, climate adaptation, protection-gap, fiscal risk learning, and development-finance readiness records in bounded, non-advisory, non-rating, non-authoritative form. 7.5.15.2 Public-Safe Reports shall include or be governed by:\ a. source records;\ b. evidence status;\ c. uncertainty;\ d. assumptions;\ e. data-quality notes;\ f. public authority boundaries;\ g. no-fiscal-advice status;\ h. no-debt-advice status;\ i. no-borrowing-advice status;\ j. no-investment-advice status;\ k. public-safe labels;\ l. decision-use labels;\ m. correction pathway;\ n. Nexus Rails continuation. 7.5.15.3 Public-Safe Reporting shall not imply official statistics, official fiscal estimates, sovereign ratings, debt advice, fiscal advice, monetary advice, tax advice, public finance approval, investment advice, underwriting, financeability, insurability, procurement approval, or implementation authority. 7.5.15.4 Where public-safe reporting risks market confusion, sovereign sensitivity, public authority confusion, fiscal misinterpretation, or false capital signals, the output shall be restricted, corrected, withdrawn, superseded, archived, or re-issued. 7.5.15.5 The constitutional rule shall be: **Public-safe reporting may explain public finance exposure. It shall not become fiscal advice, sovereign rating, or public finance approval.** ### 7.5.16 No Sovereign Borrowing Advice 7.5.16.1 Nexus shall not provide sovereign borrowing advice. 7.5.16.2 Nexus shall not recommend borrowing, refinancing, debt issuance, debt restructuring, guarantees, contingent credit, fiscal instruments, bond issuance, loan instruments, market access strategies, borrowing volumes, maturities, currencies, counterparties, or timing. 7.5.16.3 Nexus may record public finance exposure, disaster contingent liabilities, climate adaptation readiness, development-finance readiness, and lawful handoff conditions in a non-advisory form. 7.5.16.4 Sovereign borrowing decisions may be made only by competent public authorities and authorized financial actors operating within their own legal mandates, policies, approvals, fiduciary duties, and accountability structures. 7.5.16.5 The constitutional rule shall be: **Nexus may make sovereign exposure readable. It does not advise sovereign borrowing.** ### 7.5.17 No Debt Policy Advice 7.5.17.1 Nexus shall not provide debt policy advice. 7.5.17.2 Nexus shall not advise on debt sustainability, debt management strategy, debt restructuring, debt limits, public guarantees, liability recognition, creditor engagement, bond strategy, debt instruments, or debt policy reforms. 7.5.17.3 Nexus may record risk-to-public-finance exposure, contingent liability questions, disaster recovery exposure, climate adaptation exposure, and development-finance readiness questions in a non-advisory, public-safe form. 7.5.17.4 Debt policy may be determined only by competent authorities and authorized advisers operating within lawful mandates and professional duties. 7.5.17.5 The constitutional rule shall be: **Nexus may record fiscal exposure. It shall not advise debt policy.** ### 7.5.18 No Fiscal Policy Advice 7.5.18.1 Nexus shall not provide fiscal policy advice. 7.5.18.2 Nexus shall not recommend tax policy, expenditure policy, budget allocations, subsidy policy, social protection policy, public investment policy, deficit targets, fiscal rules, fiscal consolidation, fiscal expansion, or revenue measures. 7.5.18.3 Nexus may provide public finance readability records, fiscal risk learning records, public-safe reports, exposure records, and lawful handoff records that competent actors may review within their own mandates. 7.5.18.4 Fiscal policy decisions may be made only by competent public authorities and authorized actors under their own legal, democratic, institutional, and professional accountability structures. 7.5.18.5 The constitutional rule shall be: **Fiscal risk learning is not fiscal policy advice.** ### 7.5.19 No Monetary Policy Advice 7.5.19.1 Nexus shall not provide monetary policy advice. 7.5.19.2 Nexus shall not advise on interest rates, inflation targeting, exchange rates, central bank operations, reserves, liquidity facilities, monetary transmission, currency policy, capital controls, or macroprudential settings. 7.5.19.3 Nexus may record resilience exposure, financial-system risk context, public finance stress context, disaster and climate exposure, and policy-learning questions only in a non-monetary-advisory form. 7.5.19.4 Monetary policy decisions may be made only by competent monetary authorities and authorized institutions under their own lawful mandates and accountability structures. 7.5.19.5 The constitutional rule shall be: **Nexus may record systemic risk context. It does not advise monetary policy.** ### 7.5.20 No Investment Advice 7.5.20.1 Nexus shall not provide investment advice. 7.5.20.2 Nexus shall not recommend buying, selling, holding, financing, lending, investing, underwriting, guaranteeing, allocating capital, entering a transaction, issuing securities, selecting instruments, selecting managers, or approving an investment opportunity. 7.5.20.3 Sovereign and public finance records may support capital-readability, development-finance readiness, public finance readability, sovereign fund readability, diligence gap mapping, and lawful handoff where they remain product-neutral, no-offer, no-advice, no-allocation, and no-financeability records. 7.5.20.4 Investment decisions may be made only by competent actors operating within their own mandates, fiduciary duties, regulatory obligations, investment policies, risk frameworks, approvals, and accountability structures. 7.5.20.5 The constitutional rule shall be: **Nexus may make risk legible to finance-facing actors. It shall not advise investment.** ## 7.6 Risk Finance Product-Neutral Layer ### 7.6.0 Status, Purpose, and Governing Effect 7.6.0.1 This Section establishes the Risk Finance Product-Neutral Layer as the Nexus architecture through which resilience bonds, catastrophe bonds, parametric insurance, contingent credit, climate adaptation finance, blended finance, guarantees, public-private infrastructure finance, sovereign risk pools, insurance facilities, development-finance programs, loss-and-damage finance readiness, nature finance readiness, product-neutral readiness records, and instrument suitability boundaries may be discussed, recorded, compared, or made readable without recommendation, arrangement, sale, brokerage, underwriting, rating, or approval. 7.6.0.2 The Risk Finance Product-Neutral Layer shall support finance-readiness, capital-readability, insurance-readiness, public finance readability, disaster risk finance readiness, climate finance readiness, development-finance readiness, infrastructure finance readiness, sovereign fund readability, protection-gap intelligence, diligence gap mapping, public-safe reporting, and lawful handoff pathways. 7.6.0.3 The Risk Finance Product-Neutral Layer shall not be treated as investment advice, financial promotion, securities offering, product recommendation, product arrangement, product sale, brokerage, underwriting, insurance placement, reinsurance placement, rating, guarantee approval, credit approval, public finance approval, procurement approval, financeability determination, insurability determination, suitability determination, fiduciary advice, or implementation authorization. 7.6.0.4 Nexus may record that certain risk finance instruments exist, may be relevant to a type of risk question, or may require further review by competent actors. Nexus shall not recommend an instrument, rank instruments, arrange transactions, sell products, solicit investors, place insurance, underwrite risk, rate credit, approve guarantees, approve finance, determine suitability, or decide whether a product should be used. 7.6.0.5 Product-neutral records shall be no-advice, no-offer, no-sale, no-arrangement, no-brokerage, no-underwriting, no-rating, no-approval, no-financeability, no-insurability, public-safe, decision-use-labeled, correction-ready, and continued through Nexus Rails where material. 7.6.0.6 The governing rule of this Section is: **Nexus may make risk finance instruments understandable as product-neutral readiness context. Nexus does not recommend, arrange, sell, broker, underwrite, rate, approve, or determine suitability of any product or instrument.** ### 7.6.1 Resilience Bonds 7.6.1.1 Resilience Bonds may be referenced only as a product-neutral instrument category where risk reduction, resilience investment, infrastructure adaptation, disaster risk reduction, or public finance exposure may require lawful downstream review by competent finance-facing actors. 7.6.1.2 A Resilience Bond Readiness Record may identify:\ a. risk or resilience theme;\ b. source records;\ c. evidence status;\ d. technical-readiness status;\ e. public authority boundary;\ f. public finance boundary;\ g. procurement boundary;\ h. no-recommendation status;\ i. no-offer status;\ j. no-financeability status;\ k. diligence gaps;\ l. correction pathway;\ m. Nexus Rails continuation status. 7.6.1.3 Nexus shall not recommend resilience bonds, structure resilience bonds, arrange resilience bond transactions, market securities, solicit investors, provide yield analysis, provide credit analysis, determine issuer suitability, determine investor suitability, or approve issuance. 7.6.1.4 Resilience bond decisions, where relevant, may be made only by competent issuers, public authorities, investors, advisers, underwriters, arrangers, legal counsel, and regulated actors operating within their own mandates, licenses, duties, approvals, and accountability structures. 7.6.1.5 The constitutional rule shall be: **Resilience bond references may support product-neutral learning. They do not recommend or arrange a bond.** ### 7.6.2 Catastrophe Bonds 7.6.2.1 Catastrophe Bonds may be referenced only as a product-neutral instrument category where disaster risk, hazard exposure, public asset exposure, insurance protection gaps, sovereign risk transfer, or disaster risk finance readiness may require lawful downstream review. 7.6.2.2 A Catastrophe Bond Readiness Record may identify:\ a. disaster risk theme;\ b. exposure category;\ c. source records;\ d. data status;\ e. trigger-relevance question where applicable;\ f. public finance boundary;\ g. no-rating status;\ h. no-offer status;\ i. no-underwriting status;\ j. no-placement status;\ k. diligence gaps;\ l. correction pathway;\ m. continuation status. 7.6.2.3 Nexus shall not recommend catastrophe bonds, structure catastrophe bonds, model transaction pricing for advice, provide securities advice, solicit investors, arrange issuance, underwrite securities, rate risk, approve triggers, approve issuance, or determine suitability. 7.6.2.4 Catastrophe bond decisions may be made only by competent issuers, sponsors, investors, arrangers, underwriters, modeling firms, legal counsel, rating agencies, regulators, and other authorized actors within their own mandates and duties. 7.6.2.5 The constitutional rule shall be: **Catastrophe bond references frame disaster risk finance questions. They do not issue, rate, sell, or approve securities.** ### 7.6.3 Parametric Insurance 7.6.3.1 Parametric Insurance may be referenced only as a product-neutral insurance category where hazard exposure, trigger data, protection gaps, disaster risk finance readiness, public asset exposure, household exposure, agricultural exposure, or infrastructure exposure may require lawful downstream review by competent insurance-facing actors. 7.6.3.2 A Parametric Insurance Readiness Record may identify:\ a. hazard or exposure category;\ b. data availability;\ c. trigger-data question where applicable;\ d. basis-risk question;\ e. resilience relevance;\ f. market-conduct boundary;\ g. no-underwriting status;\ h. no-pricing status;\ i. no-coverage status;\ j. no-placement status;\ k. public-safe reporting limit;\ l. correction pathway;\ m. continuation status. 7.6.3.3 Nexus shall not recommend parametric insurance, design coverage, price coverage, approve triggers, underwrite risk, place insurance, broker insurance, determine claims, determine insurability, provide insurance advice, or approve a product. 7.6.3.4 Parametric insurance decisions may be made only by competent insurers, reinsurers, brokers, regulators, insureds, public authorities, advisers, and other authorized actors within their own lawful mandates and duties. 7.6.3.5 The constitutional rule shall be: **Parametric insurance references may identify exposure and data questions. They do not underwrite, price, place, or approve coverage.** ### 7.6.4 Contingent Credit 7.6.4.1 Contingent Credit may be referenced only as a product-neutral public finance or disaster risk finance category where liquidity, disaster response, climate shock, public finance stress, contingent liability, or recovery financing questions may require lawful downstream review. 7.6.4.2 A Contingent Credit Readiness Record may identify:\ a. public finance stressor;\ b. contingent liability pathway;\ c. liquidity relevance question;\ d. source records;\ e. evidence status;\ f. public authority boundary;\ g. no-borrowing-advice status;\ h. no-debt-policy-advice status;\ i. no-credit-approval status;\ j. no-financeability status;\ k. diligence gaps;\ l. correction pathway. 7.6.4.3 Nexus shall not recommend contingent credit, advise borrowing, structure credit, arrange financing, approve credit, determine debt policy, determine creditworthiness, provide fiscal advice, provide sovereign borrowing advice, or approve public finance. 7.6.4.4 Contingent credit decisions may be made only by competent public authorities, lenders, development finance institutions, legal advisers, financial advisers, and authorized actors within their own mandates, credit processes, approvals, and accountability structures. 7.6.4.5 The constitutional rule shall be: **Contingent credit references make liquidity questions visible. They do not advise or approve borrowing.** ### 7.6.5 Climate Adaptation Finance 7.6.5.1 Climate Adaptation Finance may be referenced only as a product-neutral finance category where climate risk, adaptation need, infrastructure resilience, ecosystem resilience, public finance exposure, community safeguards, or development-finance readiness may require lawful downstream review. 7.6.5.2 A Climate Adaptation Finance Readiness Record may identify:\ a. climate risk or adaptation theme;\ b. source records;\ c. scenario assumptions where applicable;\ d. evidence status;\ e. safeguard status;\ f. public authority boundary;\ g. environmental boundary;\ h. no-climate-finance-approval status;\ i. no-investment-advice status;\ j. no-financeability status;\ k. diligence gaps;\ l. continuation status. 7.6.5.3 Nexus shall not recommend climate adaptation finance instruments, approve eligibility, approve grants, approve loans, validate adaptation claims, approve carbon-market claims, allocate finance, provide investment advice, or authorize implementation. 7.6.5.4 Climate adaptation finance decisions may be made only by competent public authorities, climate finance institutions, development finance actors, funders, investors, regulators, and authorized advisers within their own mandates and procedures. 7.6.5.5 The constitutional rule shall be: **Climate adaptation finance references prepare climate-risk records for review. They do not approve climate finance.** ### 7.6.6 Blended Finance 7.6.6.1 Blended Finance may be referenced only as a product-neutral structuring category where public, philanthropic, development, concessional, commercial, or private capital may require lawful downstream review by competent actors. 7.6.6.2 A Blended Finance Readiness Record may identify:\ a. resilience theme;\ b. source records;\ c. public-good relevance;\ d. public finance boundary;\ e. subsidy or concessionality question where applicable;\ f. public authority boundary;\ g. no-structuring status;\ h. no-allocation status;\ i. no-investment-advice status;\ j. no-financeability status;\ k. conflicts and competition safeguards;\ l. correction pathway. 7.6.6.3 Nexus shall not recommend blended finance, structure transactions, allocate concessional capital, provide investment advice, arrange finance, solicit investors, determine subsidy levels, approve guarantees, approve public finance, or determine financeability. 7.6.6.4 Blended finance decisions may be made only by competent funders, public authorities, development finance institutions, investors, advisers, legal counsel, and authorized actors within their own mandates and procedures. 7.6.6.5 The constitutional rule shall be: **Blended finance references may support readiness learning. They do not structure, allocate, or approve finance.** ### 7.6.7 Guarantees 7.6.7.1 Guarantees may be referenced only as a product-neutral risk-sharing category where public finance exposure, credit risk, infrastructure finance readiness, disaster risk finance readiness, development-finance readiness, or investment-risk questions may require lawful downstream review. 7.6.7.2 A Guarantee Readiness Record may identify:\ a. risk-sharing question;\ b. source records;\ c. exposure pathway;\ d. public finance relevance;\ e. contingent liability relevance;\ f. public authority boundary;\ g. no-guarantee-approval status;\ h. no-credit-approval status;\ i. no-financeability status;\ j. no-investment-advice status;\ k. diligence gaps;\ l. continuation status. 7.6.7.3 Nexus shall not recommend guarantees, approve guarantees, structure guarantee terms, advise credit enhancement, determine guarantee eligibility, determine creditworthiness, allocate public support, or approve public finance. 7.6.7.4 Guarantee decisions may be made only by competent guarantors, public authorities, development finance institutions, lenders, investors, legal advisers, financial advisers, and authorized actors under their own mandates and approvals. 7.6.7.5 The constitutional rule shall be: **Guarantee references identify risk-sharing questions. They do not approve or advise guarantees.** ### 7.6.8 Public-Private Infrastructure Finance 7.6.8.1 Public-Private Infrastructure Finance may be referenced only as a product-neutral infrastructure finance category where public finance exposure, infrastructure exposure, procurement boundaries, public-private interface risks, climate resilience, safeguard records, or finance-readiness questions require lawful downstream review. 7.6.8.2 A Public-Private Infrastructure Finance Readiness Record may identify:\ a. infrastructure theme;\ b. source records;\ c. public finance boundary;\ d. procurement boundary;\ e. public authority boundary;\ f. social and environmental safeguard status;\ g. no-investment-advice status;\ h. no-procurement-approval status;\ i. no-financeability status;\ j. no-arrangement status;\ k. diligence gaps;\ l. correction pathway. 7.6.8.3 Nexus shall not recommend public-private finance structures, advise PPPs, structure concessions, approve procurement, rank bidders, approve contracts, arrange financing, provide investment advice, determine bankability, or authorize implementation. 7.6.8.4 Public-private infrastructure finance decisions may be made only by competent public authorities, procurement bodies, investors, lenders, advisers, regulators, and legal counsel under their own mandates and procedures. 7.6.8.5 The constitutional rule shall be: **Public-private infrastructure finance references support pre-procurement learning. They do not approve procurement, finance, or delivery.** ### 7.6.9 Sovereign Risk Pools 7.6.9.1 Sovereign Risk Pools may be referenced only as a product-neutral risk-pooling category where sovereign exposure, disaster risk, climate risk, insurance protection gaps, public finance stress, and regional risk sharing may require lawful downstream review. 7.6.9.2 A Sovereign Risk Pool Readiness Record may identify:\ a. risk-pooling theme;\ b. participating geography or exposure category where appropriate;\ c. source records;\ d. data status;\ e. public finance boundary;\ f. sovereign authority boundary;\ g. no-underwriting status;\ h. no-pricing status;\ i. no-coverage status;\ j. no-insurability status;\ k. regional governance boundary;\ l. correction pathway. 7.6.9.3 Nexus shall not recommend joining a risk pool, design coverage, price premiums, underwrite risk, approve participation, determine sovereign suitability, allocate public finance, or approve risk-pooling arrangements. 7.6.9.4 Sovereign risk pool decisions may be made only by competent sovereign authorities, pool administrators, insurers, reinsurers, development partners, regulators, and authorized advisers within their own mandates and duties. 7.6.9.5 The constitutional rule shall be: **Sovereign risk pool references frame risk-sharing questions. They do not approve pooling, pricing, or participation.** ### 7.6.10 Insurance Facilities 7.6.10.1 Insurance Facilities may be referenced only as a product-neutral category where insurance-readiness, protection-gap intelligence, public asset exposure, household exposure, agricultural exposure, infrastructure exposure, disaster risk finance readiness, or regional risk protection may require lawful downstream review. 7.6.10.2 An Insurance Facility Readiness Record may identify:\ a. exposure category;\ b. protection-gap signal;\ c. source records;\ d. data status;\ e. public finance relevance;\ f. market-conduct boundary;\ g. no-underwriting status;\ h. no-pricing status;\ i. no-placement status;\ j. no-coverage status;\ k. no-insurability status;\ l. correction pathway. 7.6.10.3 Nexus shall not recommend insurance facilities, design facility terms, price coverage, underwrite risk, place insurance, broker insurance, approve facility participation, determine eligibility, or approve insurance products. 7.6.10.4 Insurance facility decisions may be made only by competent insurers, reinsurers, brokers, public authorities, regulators, facility administrators, insureds, and authorized advisers within their own mandates and duties. 7.6.10.5 The constitutional rule shall be: **Insurance facility references identify protection questions. They do not provide or approve insurance.** ### 7.6.11 Development-Finance Programs 7.6.11.1 Development-Finance Programs may be referenced only as a product-neutral program category where resilience records, public finance exposure, infrastructure exposure, climate adaptation needs, disaster risk finance readiness, social safeguards, environmental safeguards, and development-finance readiness may require lawful downstream review. 7.6.11.2 A Development-Finance Program Readiness Record may identify:\ a. development theme;\ b. source records;\ c. public-good relevance;\ d. safeguard status;\ e. public authority boundary;\ f. procurement boundary;\ g. no-finance-approval status;\ h. no-grant-approval status;\ i. no-loan-approval status;\ j. no-implementation-approval status;\ k. diligence gaps;\ l. continuation status. 7.6.11.3 Nexus shall not recommend development-finance programs, approve grants, approve loans, approve guarantees, approve project inclusion, replace appraisal, replace safeguards review, approve procurement, or authorize implementation. 7.6.11.4 Development-finance program decisions may be made only by competent development finance actors, public authorities, donors, funders, and authorized institutions within their own mandates and procedures. 7.6.11.5 The constitutional rule shall be: **Development-finance program references prepare records for review. They do not approve development finance or implementation.** ### 7.6.12 Loss-and-Damage Finance Readiness 7.6.12.1 Loss-and-Damage Finance Readiness may be referenced only as a product-neutral readiness category where climate impacts, disaster losses, vulnerable communities, public finance exposure, adaptation gaps, displacement risk, infrastructure damage, ecosystem loss, and lawful handoff conditions require bounded learning. 7.6.12.2 A Loss-and-Damage Finance Readiness Record shall identify:\ a. loss-and-damage theme;\ b. source records;\ c. evidence basis;\ d. affected systems or communities where appropriate and safe;\ e. public finance relevance;\ f. community safeguard status;\ g. public authority boundary;\ h. no-finance-approval status;\ i. no-compensation-determination status;\ j. no-eligibility-determination status;\ k. correction pathway;\ l. continuation status. 7.6.12.3 Nexus shall not determine loss-and-damage eligibility, compensation, entitlement, allocation, funding approval, climate finance approval, public finance approval, legal responsibility, liability, or implementation authorization. 7.6.12.4 Loss-and-damage finance decisions may be made only by competent public authorities, funds, institutions, legal actors, communities, and mandated processes within their own lawful structures. 7.6.12.5 The constitutional rule shall be: **Loss-and-damage finance readiness records exposure and need questions. They do not determine entitlement, liability, or finance.** ### 7.6.13 Nature Finance Readiness 7.6.13.1 Nature Finance Readiness may be referenced only as a product-neutral readiness category where biodiversity, ecosystem services, land use, watershed function, coastal resilience, natural infrastructure, community safeguards, Indigenous knowledge safeguards, and public finance exposure require lawful downstream review. 7.6.13.2 A Nature Finance Readiness Record shall identify:\ a. nature or biodiversity theme;\ b. source records;\ c. ecosystem sensitivity;\ d. data sensitivity;\ e. community safeguard status;\ f. Indigenous knowledge safeguard status;\ g. environmental authority boundary;\ h. land-use authority boundary;\ i. no-offset-validation status;\ j. no-nature-finance-approval status;\ k. no-financeability status;\ l. correction pathway. 7.6.13.3 Nexus shall not validate offsets, approve credits, approve nature finance, determine natural capital value for transaction purposes, approve land use, grant community consent, grant Indigenous consent, recommend investment, or authorize implementation. 7.6.13.4 Nature finance decisions may be made only by competent authorities, communities, Indigenous authorities where applicable, environmental institutions, finance actors, verifiers, regulators, and authorized processes within their own mandates. 7.6.13.5 The constitutional rule shall be: **Nature finance readiness protects ecological and community records without validating nature finance or consent.** ### 7.6.14 Product-Neutral Readiness Records 7.6.14.1 Product-Neutral Readiness Records shall present risk finance instruments, instrument categories, readiness questions, exposure records, diligence gaps, public finance implications, insurance-readiness questions, and lawful handoff conditions without recommending, ranking, arranging, selling, brokering, underwriting, rating, approving, or determining suitability. 7.6.14.2 A Product-Neutral Readiness Record shall identify:\ a. instrument category;\ b. risk or exposure theme;\ c. source records;\ d. evidence status;\ e. data quality;\ f. public authority boundary;\ g. finance boundary;\ h. insurance boundary;\ i. no-recommendation status;\ j. no-arrangement status;\ k. no-sale status;\ l. no-brokerage status;\ m. no-underwriting status;\ n. no-rating status;\ o. no-approval status;\ p. correction pathway;\ q. Nexus Rails continuation. 7.6.14.3 Product-Neutral Readiness Records shall not include product recommendations, suitability conclusions, ranking of instruments, transaction terms, investor targeting, pricing advice, underwriting appetite, issuer recommendations, broker referrals, or approval language. 7.6.14.4 Product-neutrality shall be reviewed where sponsors, providers, investors, insurers, public finance institutions, development finance actors, or market participants are involved. 7.6.14.5 The constitutional rule shall be: **A product-neutral readiness record explains the question. It does not recommend the product.** ### 7.6.15 Instrument Suitability Boundaries 7.6.15.1 Instrument Suitability Boundaries shall prevent Nexus records from being interpreted as determining whether any instrument is suitable for any country, community, institution, project, portfolio, issuer, investor, insured, sponsor, provider, or beneficiary. 7.6.15.2 Suitability boundary records shall identify:\ a. instrument category;\ b. context reviewed;\ c. records considered;\ d. suitability-not-determined status;\ e. actor responsible for suitability review;\ f. public authority boundary;\ g. finance boundary;\ h. insurance boundary;\ i. legal and regulatory boundary;\ j. correction pathway;\ k. continuation status. 7.6.15.3 Nexus shall not determine suitability, appropriateness, eligibility, compatibility, affordability, value-for-money, financial viability, risk acceptance, issuer readiness, investor readiness, insured readiness, or beneficiary eligibility for any instrument. 7.6.15.4 Suitability may be determined only by competent actors operating under their own lawful mandates, professional duties, regulatory obligations, fiduciary responsibilities, underwriting standards, financial policies, and accountability structures. 7.6.15.5 The constitutional rule shall be: **Instrument suitability belongs to competent actors, not to Nexus readiness records.** ### 7.6.16 No Recommendation 7.6.16.1 Nexus shall not recommend any risk finance product, insurance product, public finance instrument, development finance program, security, guarantee, credit facility, risk pool, facility, fund, or transaction structure. 7.6.16.2 Nexus shall not state or imply that an instrument should be used, preferred, selected, purchased, issued, invested in, financed, insured, guaranteed, or adopted. 7.6.16.3 Nexus may record product-neutral instrument categories, readiness questions, diligence gaps, public finance boundaries, finance-readiness records, insurance-readiness questions, and lawful handoff conditions. 7.6.16.4 Any Nexus language that reasonably appears to recommend an instrument shall be corrected, restricted, withdrawn, superseded, archived, or re-issued. 7.6.16.5 The constitutional rule shall be: **Nexus may explain instrument categories. Nexus does not recommend instruments.** ### 7.6.17 No Arrangement 7.6.17.1 Nexus shall not arrange any financial, insurance, reinsurance, public finance, development finance, guarantee, securities, credit, risk-pooling, or investment transaction. 7.6.17.2 Nexus shall not coordinate transaction terms, parties, pricing, allocation, subscriptions, commitments, coverage, placement, guarantees, credit approval, or execution. 7.6.17.3 Nexus may support lawful handoff by making records available to competent actors, subject to decision-use labels, public-safe labels, confidentiality controls, data safeguards, no-advice language, and correction obligations. 7.6.17.4 Any activity that risks becoming transaction arrangement shall be paused, restricted, restructured, corrected, or routed to competent authorized actors. 7.6.17.5 The constitutional rule shall be: **Nexus may hand off records. Nexus does not arrange transactions.** ### 7.6.18 No Sale 7.6.18.1 Nexus shall not sell any financial product, insurance product, reinsurance product, development finance product, public finance instrument, guarantee, security, credit facility, risk pool participation, or investment opportunity. 7.6.18.2 Nexus shall not solicit purchases, subscriptions, commitments, coverage, investments, debt issuance, securities transactions, insurance purchases, or fund participation. 7.6.18.3 Nexus materials shall not be used as offering documents, marketing materials, sales materials, subscription materials, insurance sales materials, financial promotion materials, or product-placement materials. 7.6.18.4 Any Nexus output that may be interpreted as product sales material shall be corrected, restricted, withdrawn, superseded, archived, or re-issued in product-neutral form. 7.6.18.5 The constitutional rule shall be: **Nexus does not sell risk finance products.** ### 7.6.19 No Brokerage 7.6.19.1 Nexus shall not act as broker, placement agent, insurance broker, reinsurance broker, securities broker, investment intermediary, credit intermediary, guarantee broker, or transaction intermediary. 7.6.19.2 Nexus shall not introduce parties for transaction execution, negotiate on behalf of parties, place coverage, place securities, arrange investors, arrange lenders, arrange guarantors, arrange insurers, or receive transaction-based compensation unless a separate lawful authority exists outside the default Nexus role. 7.6.19.3 Nexus may maintain role-separated, product-neutral records and lawful handoff pathways that allow competent actors to independently determine whether they wish to engage each other within their own mandates. 7.6.19.4 Brokerage-like conduct shall be prohibited unless separately and lawfully authorized, segregated, disclosed, and removed from default Nexus public-good record functions. 7.6.19.5 The constitutional rule shall be: **Nexus may connect records. Nexus does not broker transactions.** ### 7.6.20 No Underwriting 7.6.20.1 Nexus shall not underwrite risk. 7.6.20.2 Nexus shall not price risk, accept risk, decline risk, bind coverage, recommend coverage, structure coverage, approve claims, approve insurance facilities, approve reinsurance placement, determine insurability, determine underwriting appetite, or act as insurer or reinsurer. 7.6.20.3 Nexus may record exposure, data gaps, protection-gap signals, resilience measures, disaster risk finance readiness, insurance-readiness questions, and lawful handoff conditions. 7.6.20.4 Underwriting may be performed only by competent insurance, reinsurance, risk-transfer, or authorized actors operating under their own lawful mandates, licenses, governance, actuarial duties, underwriting standards, and market conduct obligations. 7.6.20.5 The constitutional rule shall be: **Nexus records insurance-readiness questions. It does not underwrite risk.** ### 7.6.21 No Rating 7.6.21.1 Nexus shall not rate any sovereign, public authority, institution, issuer, project, portfolio, infrastructure asset, resilience program, insurance facility, financial product, credit, bond, guarantee, risk pool, fund, investment opportunity, provider, sponsor, or instrument. 7.6.21.2 Nexus shall not issue credit ratings, ESG ratings, resilience ratings, investment ratings, insurance ratings, project ratings, sovereign ratings, or product ratings unless a separate lawful rating authority exists outside the default Nexus role and is expressly documented within scope. 7.6.21.3 Nexus may use status labels, readiness labels, evidence labels, decision-use labels, public-safe labels, and maturity labels only as internal or public-safe record disciplines, not as ratings. 7.6.21.4 Any record label that may be mistaken for a rating shall include clear non-rating language or be corrected, restricted, withdrawn, superseded, archived, or re-issued. 7.6.21.5 The constitutional rule shall be: **Nexus may label record status. Nexus does not rate credit, investment, insurance, or institutional quality.** ### 7.6.22 No Approval 7.6.22.1 Nexus shall not approve any risk finance product, public finance instrument, insurance product, reinsurance arrangement, guarantee, credit facility, development-finance program, investment structure, securities issuance, risk pool, infrastructure finance pathway, climate finance pathway, nature finance pathway, or loss-and-damage finance pathway. 7.6.22.2 Nexus shall not approve eligibility, suitability, bankability, financeability, insurability, pricing, coverage, creditworthiness, transaction terms, procurement readiness, public finance readiness, or implementation readiness. 7.6.22.3 Nexus may provide product-neutral readiness records, finance-readiness notes, insurance-readiness questions, public-safe reports, evidence packs, diligence gap maps, verification records, and lawful handoff records. 7.6.22.4 Approval may occur only where competent actors exercise their own lawful mandates, procedures, licenses, approvals, fiduciary duties, underwriting duties, public finance authority, regulatory authority, or procurement authority. 7.6.22.5 The constitutional rule shall be: **Nexus may prepare the record for review. Nexus does not approve the product, instrument, transaction, or pathway.** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.therisk.global/organization/acceleration/nexus-campaigns/vii.-interfaces.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.