# XVII. STATEMENT **Summary** This part closes the National Investors Council gateway by defining what the Council is, what it may prepare, and what it must never become. It ties [readiness](/organization/cooperation/consortiums/gateways/national-councils/investors/vii.-readiness.md), [rooms](/organization/cooperation/consortiums/gateways/national-councils/investors/viii.-rooms.md), [handoff](/organization/cooperation/consortiums/gateways/national-councils/investors/ix.-handoff.md), [records](/organization/cooperation/consortiums/gateways/national-councils/investors/xi.-records.md), [claims](/organization/cooperation/consortiums/gateways/national-councils/investors/xii.-claims.md), [safeguards](/organization/cooperation/consortiums/gateways/national-councils/investors/xiii.-safeguards.md), [conflicts](/organization/cooperation/consortiums/gateways/national-councils/investors/xiv.-conflicts.md), [boundaries](/organization/cooperation/consortiums/gateways/national-councils/investors/xv.-boundaries.md), [correction](/organization/cooperation/consortiums/gateways/national-councils/investors/xvi.-correction.md), [Nexus Rails](/organization/organization/architecture/ii.-definitions/xv.-nexus-rails.md), and [Nexus Universe](/organization/cooperation/nexus-universe.md) into one final operating statement. It preserves a strict separation between finance-readiness and finance, routeability and execution, public-good clarity and external authority. ## 17.1 National Investors Council Operating Formula This formula shows how participation becomes recorded input, readable questions, mapped gaps, and bounded handoff. ### 17.1.1 Participation Begins as No-Reliance Engagement **17.1.1.1** Participation in the National Investors Council shall begin as **no-reliance engagement**. **17.1.1.2** No-reliance engagement means that each participant, whether acting as a capital reader, investor, bank, insurer, reinsurer, donor, philanthropy, public finance reader, development actor, sponsor, provider, public authority learner, expert, observer, guest, National Consortium Company interface participant, Project SPV-readiness participant, Nexus Universe participant, AEP Passport finance-layer contributor, Nexus Rail contributor, Docket contributor, or other recorded participant, enters the Council only for disciplined participation, question formation, gap identification, finance-readiness interpretation, and public-good learning. **17.1.1.3** No-reliance engagement shall not create investment advice, financial advice, insurance advice, legal advice, tax advice, securities offering, capital solicitation, transaction arrangement, brokerage, lending, underwriting, insurance placement, rating, guarantee, public finance approval, donor commitment, philanthropic commitment, procurement status, project approval, Project SPV approval, National Consortium Company approval, public authority approval, certification, consent, Nexus-ready status, AEP Passport status, or execution authority. **17.1.1.4** No participant shall rely on Council participation, room discussion, record, note, output, public-safe report, Nexus Universe activity, National Model finance layer, AEP Passport finance-layer input, Nexus Rail input, Docket item, or handoff material as a substitute for separate legal, financial, investment, insurance, public authority, procurement, safeguard, consent, technical, corporate, donor, public finance, or execution process. **17.1.1.5** The governing formula shall be: **Participation begins as no-reliance engagement, or it does not properly begin at all.** *** ### 17.1.2 No-Reliance Engagement Becomes Recorded Finance-Readiness Input **17.1.2.1** No-reliance engagement may become recorded finance-readiness input where the participant contributes relevant questions, observations, dependencies, gaps, assumptions, risk interpretations, public authority dependencies, safeguard conditions, insurance-readiness questions, public finance relevance questions, donor relevance questions, Project SPV-readiness questions, National Consortium Company interface questions, Nexus Rail routeability questions, AEP Passport finance-layer questions, Docket issues, or handoff conditions. **17.1.2.2** Recorded finance-readiness input shall identify its source, role classification, contribution context, no-reliance status, confidentiality class, publication class, conflict status, safeguard conditions, claims limits, affected pathway, and correction route. **17.1.2.3** Finance-readiness input shall not become finance status, investment status, insurance status, donor status, public finance status, procurement status, project status, public authority status, Passport status, Rail execution status, Company status, SPV status, consent status, or execution status. **17.1.2.4** Input that is not recorded shall not support a claim, output, handoff, public-safe report, National Model layer, Nexus Universe statement, AEP Passport finance-layer contribution, Nexus Rail contribution, Docket item, or participant profile. **17.1.2.5** The governing formula shall be: **No-reliance engagement becomes useful only when it becomes recorded finance-readiness input.** *** ### 17.1.3 Finance-Readiness Input Becomes Capital-Readable Question **17.1.3.1** Recorded finance-readiness input may become a **capital-readable question** where it is translated into a disciplined question that capital readers, insurers, donors, public finance readers, development actors, National Consortium Company interfaces, Project SPV pathways, public authorities, or lawful receiving actors may understand without relying on it as advice, approval, commitment, finance, insurance, procurement, consent, or execution. **17.1.3.2** A capital-readable question may address evidence basis, technical maturity, public authority dependency, legal pathway, procurement dependency, revenue and cost assumption, lifecycle obligation, risk allocation, insurance dependency, donor relevance, public finance relevance, safeguard condition, data and cyber condition, community or Indigenous protocol condition where applicable, environmental and social condition, SPV-readiness, Company interface, Nexus Rail routeability, AEP Passport finance-layer status, Docket status, or handoff limitation. **17.1.3.3** A capital-readable question shall remain a question. It shall not become valuation, rating, recommendation, investment material, securities material, underwriting submission, donor application, public finance request, procurement material, project approval material, legal conclusion, insurance conclusion, safeguard clearance, or execution instruction. **17.1.3.4** Capital-readable questions shall preserve uncertainty, state assumptions, identify unresolved matters, avoid promotional language, and carry no-reliance and claims-limit discipline. **17.1.3.5** The governing formula shall be: **Finance-readiness input becomes capital-readable only when it is framed as a question, not as a conclusion.** *** ### 17.1.4 Capital-Readable Question Becomes Diligence-Gap Map **17.1.4.1** A capital-readable question may become part of a **Diligence-Gap Map** where the Council records what remains unresolved before any matter may be responsibly routed, reviewed, presented, handed off, or considered by competent external actors. **17.1.4.2** A Diligence-Gap Map may organize gaps relating to evidence, technical readiness, legal pathway, public authority status, procurement, revenue, cost, lifecycle, governance, risk allocation, insurance, reinsurance, disaster-risk finance, donor relevance, public finance relevance, data, cyber, safeguards, community protocols, Indigenous protocols where applicable, environmental and social conditions, Project SPV-readiness, National Consortium Company interface, Nexus Rail routeability, AEP Passport finance-layer status, Docket status, and handoff conditions. **17.1.4.3** A Diligence-Gap Map shall not imply diligence completion, financeability, bankability, insurability, investment readiness, donor approval, public finance approval, procurement clearance, public authority approval, safeguard clearance, certification, Passport status, Rail execution, SPV approval, Company approval, project approval, consent, or execution readiness. **17.1.4.4** The Diligence-Gap Map shall identify whether each gap is informational, evidentiary, technical, legal, public-authority-dependent, procurement-dependent, finance-readiness-dependent, insurance-dependent, donor-dependent, safeguard-dependent, Docketed, blocking, restricting, deferring, correcting, handoff-limiting, or archive-relevant. **17.1.4.5** The governing formula shall be: **A capital-readable question matures into discipline only when the unresolved gap is mapped, not hidden.** *** ### 17.1.5 Diligence-Gap Map Becomes Nexus Rail or AEP Passport Finance-Layer Input **17.1.5.1** A Diligence-Gap Map may become a **Nexus Rail finance-readiness input** or an **AEP Passport finance-layer input** where the mapped gaps, dependencies, safeguards, claims limits, and correction pathways are suitable for a recorded Nexus pathway. **17.1.5.2** A Nexus Rail finance-readiness input may support routeability by identifying source record, proposed route, receiving pathway, routeability status, finance-readiness status, insurance-readiness status, donor relevance, public finance relevance, public authority dependencies, safeguard conditions, unresolved gaps, no-reliance status, confidentiality class, Docket linkage, handoff conditions, and correction pathway. **17.1.5.3** An AEP Passport finance-layer input may support a Passport candidate pathway by identifying finance-readiness layer content, capital-readability layer content, insurance-readiness layer content, public finance relevance layer content, donor and philanthropic relevance layer content, diligence-gap layer content, Project SPV-readiness layer content, handoff condition layer content, and correction layer content. **17.1.5.4** Neither Nexus Rail input nor AEP Passport finance-layer input shall imply Rail execution, Passport issuance, Nexus-ready status, certification, standards conformance, financeability, bankability, insurability, donor support, public finance allocation, public authority approval, procurement status, SPV approval, Company approval, project approval, consent, or execution. **17.1.5.5** The governing formula shall be: **A diligence-gap map may enter Nexus Rails or AEP Passport only as a recorded input, never as approval.** *** ### 17.1.6 Nexus Rail or AEP Passport Input May Support Lawful Handoff **17.1.6.1** A Nexus Rail finance-readiness input or AEP Passport finance-layer input may support lawful handoff only where the input is current, classified, claims-limited, no-reliance, safeguard-aware, conflict-reviewed, public authority-aware, and correctionable. **17.1.6.2** Lawful handoff may be directed to a competent receiving pathway, including the National Council, National Leadership Council, Helix Council, National Working Group, Stewardship Board where formed, GCRI evidence pathway, GRF claims or public-safe reporting pathway, GRA-aligned finance-readiness pathway, Nexus Rail pathway, AEP Passport pathway, National Consortium Company interface, Project SPV pathway, public authority pathway, donor pathway, public finance pathway, insurance pathway, safeguard pathway, or other lawful enterprise or implementation pathway. **17.1.6.3** Handoff shall carry source record, purpose, receiving pathway, no-reliance status, confidentiality class, publication class, public authority dependencies, finance-readiness dependencies, insurance-readiness dependencies, donor relevance, public finance relevance, safeguard conditions, data and cyber conditions, conflicts, claims limits, unresolved gaps, restrictions, Docket status, correction pathway, and prohibited inferences. **17.1.6.4** Handoff shall not imply handoff completion, finance approval, insurance approval, donor approval, public finance allocation, procurement status, certification, public authority approval, SPV approval, Company approval, project approval, consent, contract formation, transaction execution, or operational authority. **17.1.6.5** The governing formula shall be: **Nexus Rail or AEP Passport input may support handoff only by carrying conditions forward, not by carrying authority forward.** *** ### 17.1.7 Lawful Handoff Requires Competent External Actors **17.1.7.1** Lawful handoff shall require competent external actors. **17.1.7.2** Competent external actors may include public authorities, legal counsel, finance actors, insurers, reinsurers, donors, philanthropies, public finance bodies, procurement authorities, National Consortium Companies, Project SPVs, operators, providers, hosts, sponsors, safeguard bodies, community or Indigenous rights-holder processes where applicable, corporate governance bodies, technical assurance bodies, standards bodies, or other lawful actors acting within their own mandates. **17.1.7.3** The National Investors Council shall not become the competent external actor merely because it prepared finance-readiness input, convened capital readers, supported Nexus Universe rooms, contributed to an AEP Passport finance layer, identified a Nexus Rail pathway, captured a Docket issue, prepared a National Model finance layer, or produced a handoff note. **17.1.7.4** External actors receiving handoff materials shall remain responsible for their own lawful review, authority, diligence, advice, approvals, decisions, safeguards, compliance, contracts, finance, insurance, procurement, public authority processes, consent processes, and execution. **17.1.7.5** The governing formula shall be: **Handoff becomes lawful only when competent external actors act through their own lawful processes, not through Council implication.** *** ### 17.1.8 External Finance, Insurance, Donor, Public Finance, Procurement, and Project Decisions Remain Outside the Council **17.1.8.1** External finance, insurance, donor, public finance, procurement, and project decisions shall remain outside the National Investors Council. **17.1.8.2** Investment decisions, lending decisions, capital commitments, insurance decisions, reinsurance decisions, underwriting decisions, guarantee decisions, donor decisions, philanthropic decisions, public finance decisions, procurement decisions, provider-selection decisions, Project SPV decisions, National Consortium Company decisions, public authority decisions, safeguard decisions, community consent decisions, Indigenous consent decisions where applicable, certification decisions, standards-conformance decisions, project-authorization decisions, and execution decisions shall not be made by the Council. **17.1.8.3** The Council’s records may help external actors understand what questions, gaps, dependencies, safeguards, and conditions may need attention, but shall not decide those matters. **17.1.8.4** Any attempt to use Council outputs as substitute decisions shall be corrected, restricted, withdrawn, superseded, archived, or referred to competent processes. **17.1.8.5** The governing formula shall be: **The Council prepares disciplined readability; all external decisions remain external.** *** ### 17.1.9 Every Output Remains Record-Based, Claims-Limited, Public-Safe, and Correctionable **17.1.9.1** Every National Investors Council output shall remain **record-based, claims-limited, public-safe where released, and correctionable**. **17.1.9.2** Outputs shall include registers, participation records, role classifications, capital-reader records, insurance-readiness records, public finance relevance records, donor relevance records, conflict records, no-reliance acknowledgments, claims permissions, confidentiality and publication class records, finance-readiness notes, capital-readability questions, insurance-readiness questions, reinsurance-readiness questions, public finance relevance notes, donor relevance notes, philanthropic relevance notes, development-readiness notes, diligence-gap maps, risk-to-capital notes, Project SPV-readiness notes, Company handoff-readiness notes, Nexus Rail finance-readiness inputs, AEP Passport finance-layer inputs, room rules, Nexus Universe records, Docket notes, public-safe reporting inputs, handoff notes, correction notes, archive notes, and renewal notes. **17.1.9.3** No output shall outgrow its record, outrun its claims limits, bypass safeguards, ignore no-reliance discipline, escape confidentiality class, avoid conflict review, or resist correction. **17.1.9.4** Outputs shall be amended, narrowed, reclassified, restricted, withdrawn, superseded, archived, renewed, or corrected when truth, risk, sensitivity, public authority status, finance context, insurance context, donor context, public finance context, safeguard status, market conduct risk, or reliance risk changes. **17.1.9.5** The final operating formula shall be: **Every output lives only as a record, speaks only within claims limits, travels only where public-safe or controlled, and survives only while correctionable.** *** ## 17.2 Final Public-Good Statement These statements define the Council's public-good role without turning readability into approval, capital, or execution. ### 17.2.1 Finance-Readiness as Service **17.2.1.1** Finance-readiness shall be understood as a service to the national Nexus public-good architecture. **17.2.1.2** The National Investors Council exists to help national priorities, National Models, Nexus Universe outputs, AEP Passport candidate pathways, Nexus Rail pathways, National Working Group outputs, public authority learning records, safeguard conditions, Project SPV-readiness questions, National Consortium Company interface questions, Docket issues, and lawful handoff candidates become more legible to finance-related readers. **17.2.1.3** Finance-readiness as service shall not become finance execution, financial advice, investment promotion, insurance placement, donor solicitation, public finance allocation, procurement, project development, or enterprise control. **17.2.1.4** The service is performed for public-good clarity, not for private capital control. **17.2.1.5** The governing public-good statement shall be: **Finance-readiness serves the record; it shall not rule the record.** *** ### 17.2.2 Capital-Readability as Interpretation **17.2.2.1** Capital-readability shall be understood as interpretation. **17.2.2.2** Capital-readability translates evidence, public-good value, technical status, risk, governance, public authority dependency, safeguard conditions, legal pathway, procurement dependency, lifecycle obligations, insurance questions, donor relevance, public finance relevance, SPV-readiness, Company interface, Rail routeability, AEP Passport finance-layer status, and Docket issues into questions that capital readers can understand. **17.2.2.3** Capital-readability shall not become capital commitment, investment interest, financeability, bankability, rating, securities activity, transaction readiness, lender approval, guarantee support, or capital availability. **17.2.2.4** Capital-readability is valuable because it prevents capital-facing confusion before external finance processes exist. **17.2.2.5** The governing public-good statement shall be: **Capital-readability interprets readiness for capital readers; it does not convert readiness into capital.** *** ### 17.2.3 Insurance-Readiness as Learning **17.2.3.1** Insurance-readiness shall be understood as learning. **17.2.3.2** Insurance-readiness helps national Nexus pathways identify exposure questions, loss questions, data and model dependencies, risk-transfer questions, reinsurance-readiness questions, protection-gap questions, disaster-risk finance questions, infrastructure risk questions, cyber risk questions, public authority insurance interface questions, safeguard conditions, and Project SPV insurance dependencies. **17.2.3.3** Insurance-readiness shall not become insurance approval, reinsurance approval, underwriting, coverage availability, premium indication, guarantee support, insurance advice, insurance placement, insurability, or risk-transfer execution. **17.2.3.4** Insurance-readiness strengthens public-good preparedness by making risk questions visible before insurance actors make any separate lawful determination. **17.2.3.5** The governing public-good statement shall be: **Insurance-readiness teaches the system what risk questions remain; it does not insure the system.** *** ### 17.2.4 Public Finance Relevance as Context **17.2.4.1** Public finance relevance shall be understood as context. **17.2.4.2** Public finance relevance may identify where national Nexus matters intersect with public investment, public grants, public guarantees, subsidies, concessional finance, climate finance, resilience finance, disaster-risk finance, infrastructure finance, public authority funding, public-private pathways, budget processes, public value, and public-good outcomes. **17.2.4.3** Public finance relevance shall not become public finance allocation, budget approval, grant approval, subsidy approval, public guarantee, procurement status, government endorsement, official position, public authority approval, or funding expectation. **17.2.4.4** Public finance relevance is included so that public-good records do not ignore public authority and public finance dependencies. **17.2.4.5** The governing public-good statement shall be: **Public finance relevance gives context to public-good readiness; it shall not spend, allocate, or approve public money.** *** ### 17.2.5 Donor and Philanthropic Relevance as Non-Commitment Inquiry **17.2.5.1** Donor and philanthropic relevance shall be understood as non-commitment inquiry. **17.2.5.2** Donor and philanthropic relevance may identify mission fit, development relevance, humanitarian relevance, climate relevance, resilience relevance, disaster-risk relevance, research relevance, capacity-building relevance, community-support relevance, youth relevance, accessibility relevance, institutional-strengthening relevance, evidence needs, reporting needs, safeguard expectations, and public-good value. **17.2.5.3** Donor and philanthropic relevance shall not become donor commitment, philanthropic commitment, grant approval, foundation approval, CSR commitment, pledge, award, allocation, sponsorship, development assistance commitment, endorsement, funding pipeline, or project approval. **17.2.5.4** Donor and philanthropic relevance strengthens public-good readiness by clarifying mission fit without creating false funding expectations. **17.2.5.5** The governing public-good statement shall be: **Donor and philanthropic relevance asks whether a matter may fit a mission; it shall not promise that the mission will fund it.** *** ### 17.2.6 Diligence-Gap Mapping as Readiness Discipline **17.2.6.1** Diligence-gap mapping shall be understood as readiness discipline. **17.2.6.2** Diligence-gap mapping records unresolved questions across evidence, technical readiness, law, governance, public authority status, procurement, finance-readiness, insurance-readiness, donor relevance, public finance relevance, data, cyber, safeguards, community protocols, Indigenous protocols where applicable, environmental and social conditions, Project SPV-readiness, National Consortium Company interface, Nexus Rail routeability, AEP Passport finance-layer status, Docket status, and handoff conditions. **17.2.6.3** Diligence-gap mapping shall not become completed diligence, legal clearance, financial clearance, insurance clearance, donor approval, public finance approval, procurement clearance, safeguard clearance, certification, project approval, consent, or execution readiness. **17.2.6.4** Diligence-gap mapping is valuable because it prevents incomplete matters from being promoted as complete. **17.2.6.5** The governing public-good statement shall be: **Diligence-gap mapping protects readiness by recording what is not ready.** *** ### 17.2.7 Project SPV-Readiness as Handoff Preparation **17.2.7.1** Project SPV-readiness shall be understood as handoff preparation. **17.2.7.2** Project SPV-readiness may identify governance questions, capitalization questions, revenue and cost questions, contracting questions, public authority dependencies, insurance questions, procurement questions, safeguard conditions, data and cyber conditions, community and Indigenous protocol conditions where applicable, environmental and social conditions, lifecycle obligations, operator responsibility, National Consortium Company interface, Nexus Rail status, AEP Passport finance-layer status, Docket status, handoff conditions, and correction pathway. **17.2.7.3** Project SPV-readiness shall not become Project SPV approval, SPV formation, project approval, financeability, bankability, insurability, procurement readiness, provider selection, public authority approval, donor support, public finance allocation, consent, certification, or execution authority. **17.2.7.4** Project SPV-readiness prepares possible future lawful review without authorizing the future vehicle. **17.2.7.5** The governing public-good statement shall be: **Project SPV-readiness prepares questions for a possible lawful vehicle; it shall not create the vehicle.** *** ### 17.2.8 Nexus Rails as Routeability, Not Execution **17.2.8.1** Nexus Rails shall be understood as routeability, not execution. **17.2.8.2** Nexus Rails may help route records, questions, gaps, dependencies, safeguards, Docket issues, AEP Passport finance-layer inputs, National Model finance layers, Project SPV-readiness issues, Company interface issues, public authority dependencies, donor relevance, insurance-readiness, public finance relevance, public-safe reporting inputs, and handoff conditions. **17.2.8.3** Nexus Rails shall not execute finance, insurance, donor support, public finance, procurement, public authority action, certification, SPV formation, Company action, project approval, consent, contract, operation, deployment, or implementation. **17.2.8.4** Rail routeability is valuable because it disciplines how matters move without pretending that movement is execution. **17.2.8.5** The governing public-good statement shall be: **Nexus Rails may route readiness; they shall not execute readiness.** *** ### 17.2.9 AEP Passport Finance Layers as Records, Not Ratings **17.2.9.1** AEP Passport finance layers shall be understood as records, not ratings. **17.2.9.2** AEP Passport finance layers may record finance-readiness input, capital-readability input, insurance-readiness input, public finance relevance input, donor and philanthropic relevance input, diligence-gap input, Project SPV-readiness input, handoff condition input, and correction input. **17.2.9.3** AEP Passport finance layers shall not become ratings, guarantees, certifications, financeability determinations, bankability determinations, insurability determinations, investment-readiness determinations, donor-readiness determinations, public finance approvals, procurement statuses, public authority approvals, Nexus-ready statuses, project approvals, consent records, or execution permissions. **17.2.9.4** AEP Passport finance layers are valuable because they preserve structured finance-readiness evidence without creating market or authority status. **17.2.9.5** The governing public-good statement shall be: **AEP Passport finance layers record readiness inputs; they shall not rate, certify, approve, or guarantee.** *** ### 17.2.10 Finance-Readiness as Public-Good Readiness, Not Finance **17.2.10.1** Finance-readiness shall be understood as public-good readiness, not finance. **17.2.10.2** The National Investors Council shall help the Nexus architecture become more disciplined, more intelligible, more safeguard-aware, more capital-readable, more insurance-readable, more donor-readable, more public finance-aware, more handoff-ready, more correctionable, and less vulnerable to overclaim. **17.2.10.3** Finance-readiness shall not collapse into finance, capital control, investor control, insurer control, donor control, public finance control, sponsor control, provider control, public authority substitution, community tokenization, Project SPV authorization, National Consortium Company capture, procurement advantage, certification, or execution. **17.2.10.4** The Council’s highest value is not that it promises finance, but that it prevents finance-related misunderstanding before national priorities, public-good records, safeguards, and lawful handoff pathways are mature enough to travel. **17.2.10.5** The final public-good statement shall be: **Finance-readiness is the public-good discipline that makes national Nexus pathways legible to finance-related readers without turning those readers into owners, approvers, financiers, insurers, donors, public authorities, or execution actors.** *** ## 17.3 Closing Clause This closing clause consolidates the Council's final limits, mandate, and continuing conditions of validity. ### 17.3.1 National Investors Council Gateway Charter Closing Statement **17.3.1.1** The **National Investors Council** is the national gateway through which **capital-readability, finance-readiness, insurance-readiness, public finance relevance, donor relevance, philanthropic relevance, diligence-gap mapping, Project SPV-readiness, Nexus Rail routing, and AEP Passport finance-layer inputs** are developed as public-good records under **no-reliance, non-advisory, non-solicitation, non-transaction, non-placement, claims-limited, safeguard-aware, public authority-aware, conflict-managed, market-conduct disciplined, publication-classified, and correctionable discipline**. **17.3.1.2** The National Investors Council helps national Nexus pathways become intelligible to finance-related readers, insurers, donors, public finance readers, development actors, National Consortium Company interfaces, Project SPV pathways, public authorities, safeguard pathways, Nexus Universe rooms, Nexus Rail pathways, AEP Passport pathways, Docket pathways, and lawful receiving actors without converting intelligibility into approval, commitment, finance, insurance, donor support, public finance, procurement, consent, certification, project authorization, or execution. **17.3.1.3** The National Investors Council shall preserve the operating separation between: **a.** participation and authority; **b.** capital-readability and capital commitment; **c.** finance-readiness and financeability; **d.** bankability questions and bankability determinations; **e.** insurance-readiness and insurance approval; **f.** reinsurance-readiness and reinsurance support; **g.** public finance relevance and public finance allocation; **h.** donor relevance and donor commitment; **i.** philanthropic relevance and grant approval; **j.** diligence-gap mapping and completed diligence; **k.** Nexus Rail routeability and execution; **l.** AEP Passport finance-layer input and AEP Passport status; **m.** Project SPV-readiness and Project SPV approval; **n.** National Consortium Company interface and Company authority; **o.** public authority learning and public authority action; **p.** community participation and community consent; **q.** Indigenous participation and Indigenous consent where applicable; **r.** provider contribution and provider validation; **s.** sponsor support and sponsor control; **t.** public-safe reporting and public warning; and **u.** lawful handoff preparation and lawful execution. **17.3.1.4** The National Investors Council shall support the Nexus Consortium architecture, National Nexus Consortiums, National Councils, National Leadership Councils, Helix Councils, National Working Groups, Regional Nexus Consortiums, Global Nexus Consortium, Nexus Universe, Nexus Network, Nexus Observatory, Nexus Rails, AEP Passport pathways, Docket pathways, National Models, National Consortium Companies, Project SPV pathways, GCRI evidence pathways, GRF claims and public-good legitimacy pathways, and GRA finance-readiness pathways only within its recorded mandate and boundaries. **17.3.1.5** The National Investors Council shall never be used, described, marketed, represented, or relied upon as an investment committee, fund, lender, broker, underwriter, insurer, reinsurer, rating agency, securities platform, crowdfunding platform, public finance authority, donor approval body, philanthropic grant-maker, guarantee facility, transaction arranger, financial adviser, investment adviser, insurance adviser, tax adviser, legal adviser, fiduciary, procurement body, certification body, standards-conformance body, public authority, project developer, National Consortium Company, Project SPV, operator, contractor, emergency-command body, public-warning body, consent body, or execution vehicle. **17.3.1.6** The National Investors Council shall remain valid only while its records remain accurate, its rooms remain no-reliance, its claims remain narrow, its safeguards remain attached, its conflicts remain managed, its market conduct remains disciplined, its public authority language remains capacity-classified, its finance language remains non-advisory, its donor language remains non-commitment, its insurance language remains non-placement, its public finance language remains non-allocation, its handoff materials remain bounded, and its correction pathways remain active. **17.3.1.7** The closing rule of this Charter shall be: **The National Investors Council exists to make national Nexus readiness legible to finance-related readers without making finance, to make insurance questions visible without making insurance, to make public finance relevance intelligible without allocating public finance, to make donor and philanthropic relevance understandable without creating commitments, to make Project SPV-readiness disciplined without approving vehicles, to make Nexus Rails routeable without executing routes, to make AEP Passport finance layers recordable without rating or certifying, and to make lawful handoff safer without converting handoff into authority.** **Next steps** * Revisit [XVI. CORRECTION](/organization/cooperation/consortiums/gateways/national-councils/investors/xvi.-correction.md) to manage amendment, withdrawal, supersession, archive, and renewal after this closing statement. * Use [XII. CLAIMS](/organization/cooperation/consortiums/gateways/national-councils/investors/xii.-claims.md), [XIII. SAFEGUARDS](/organization/cooperation/consortiums/gateways/national-councils/investors/xiii.-safeguards.md), and [XV. BOUNDARIES](/organization/cooperation/consortiums/gateways/national-councils/investors/xv.-boundaries.md) when applying this statement to communications, publication, rooms, and handoff. * Return to [Nexus Rails](/organization/organization/architecture/ii.-definitions/xv.-nexus-rails.md) and [Nexus Universe](/organization/cooperation/nexus-universe.md) when this gateway needs routing context or annual operating context. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.therisk.global/organization/cooperation/consortiums/gateways/national-councils/investors/xvii.-statement.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.