# VII. READINESS The **National Investors Council** defines finance-readiness as disciplined capital readability without implying financeability, bankability, approval, or execution. This section sets the architecture for finance-readiness, including evidence translation, gap visibility, no-reliance interpretation, handoff preparation, and correctionable records across the [National Investors Council](/organization/cooperation/consortiums/gateways/national-councils/investors.md), [Nexus Rails](/organization/organization/architecture/ii.-definitions/xv.-nexus-rails.md), and [Nexus Universe](/organization/cooperation/nexus-universe.md). This architecture keeps public-good records readable to capital while preserving boundaries set by [GCRI](/organization/cooperation/consortiums/frontiers/gcri.md), [GRF](/organization/cooperation/consortiums/frontiers/grf.md), and [GRA](/organization/cooperation/consortiums/frontiers/gra.md). It strengthens search visibility for finance-readiness, capital-readability, diligence gaps, no-reliance, and lawful handoff. ## 7.1 Finance-Readiness Defined ### 7.1.1 Finance-Readiness as Readability **7.1.1.1** Finance-readiness, for purposes of the National Investors Council, shall mean the disciplined condition in which a national Nexus matter is sufficiently described, classified, evidenced, limited, and recorded so that capital readers may understand the matter without mistaking such understanding for finance, investment, insurance, donor support, public finance allocation, transaction readiness, project approval, or execution authority. **7.1.1.2** Finance-readiness as readability shall require that the relevant matter be translated into capital-readable language without removing its public-good purpose, technical limitations, public authority dependencies, safeguard conditions, legal constraints, procurement dependencies, data and cyber conditions, community and Indigenous protocol conditions where applicable, environmental and social conditions, lifecycle obligations, and correction pathways. **7.1.1.3** Readability shall not be measured by investor enthusiasm, sponsor interest, donor preference, insurer appetite, public finance visibility, media appeal, or ease of presentation. It shall be measured by whether the matter can be understood honestly, precisely, safely, and without reliance. **7.1.1.4** The National Investors Council shall ensure that finance-readiness materials use controlled vocabulary, status labels, no-reliance language, public-safe framing, and claims limits so that a reader can distinguish between evidence, assumption, dependency, gap, candidate status, routeability, handoff condition, approval, and execution. **7.1.1.5** The governing rule shall be: **Finance-readiness begins when a matter becomes readable to capital without becoming finance by implication.** *** ### 7.1.2 Finance-Readiness as Gap Identification **7.1.2.1** Finance-readiness shall include disciplined identification of gaps. **7.1.2.2** A finance-readiness review shall identify what is missing, unresolved, uncertain, restricted, unverified, conflicted, dependent, unsafe, premature, or not yet suitable for capital-reader understanding or lawful handoff. **7.1.2.3** Gaps may include evidence gaps, technical gaps, data gaps, cyber gaps, public authority gaps, legal gaps, regulatory gaps, procurement gaps, governance gaps, financial assumption gaps, revenue gaps, lifecycle cost gaps, insurance gaps, donor relevance gaps, public finance gaps, safeguard gaps, community protocol gaps, Indigenous protocol gaps where applicable, environmental and social gaps, provider-neutrality gaps, National Consortium Company interface gaps, Project SPV-readiness gaps, Nexus Rail routing gaps, AEP Passport finance-layer gaps, Docket gaps, and handoff gaps. **7.1.2.4** A matter shall not be made more finance-readable by hiding gaps. The National Investors Council shall treat gap identification as a protective public-good function and not as a weakness to be managed away for capital-facing presentation. **7.1.2.5** The governing rule shall be: **Finance-readiness is honest only when its gaps are visible.** *** ### 7.1.3 Finance-Readiness as Evidence Translation **7.1.3.1** Finance-readiness shall include evidence translation. **7.1.3.2** Evidence translation means converting technical, public-good, observability, National Model, Nexus Universe, AEP Passport candidate, Nexus Rail, Docket, public authority learning, safeguard, community, environmental, social, operational, and enterprise-interface evidence into capital-readable form without altering its meaning. **7.1.3.3** Evidence translation shall identify source, method, maturity, reliability, assumptions, limitations, uncertainty, data quality, verification status, publication class, confidentiality class, safeguard conditions, public authority status, and correction history. **7.1.3.4** Evidence translation shall not convert evidence into certification, rating, due diligence completion, investment advice, insurance advice, public finance approval, donor approval, procurement status, public authority approval, SPV approval, project approval, or execution authorization. **7.1.3.5** The governing rule shall be: **Evidence may be translated for capital understanding only if its limits remain attached to the translation.** *** ### 7.1.4 Finance-Readiness as No-Reliance Interpretation **7.1.4.1** Finance-readiness shall be interpreted on a no-reliance basis. **7.1.4.2** No-reliance interpretation means that finance-readiness outputs may inform learning, issue-spotting, diligence-gap identification, capital-readability, public finance relevance, donor relevance, insurance-readiness, SPV-readiness, routeability, and handoff preparation, but shall not be relied upon as investment advice, financial advice, insurance advice, securities advice, legal advice, tax advice, accounting advice, procurement advice, public finance advice, donor advice, underwriting, guarantee approval, rating, public authority approval, certification, consent, SPV approval, project approval, or execution authorization. **7.1.4.3** No-reliance interpretation shall apply to all finance-readiness notes, capital-readability question sets, diligence-gap maps, public authority dependency notes, procurement dependency notes, insurance-readiness notes, public finance relevance notes, donor relevance notes, philanthropic relevance notes, Project SPV-readiness notes, National Consortium Company finance-interface notes, Nexus Rail finance-readiness notes, AEP Passport finance-readiness layer inputs, correction notes, and Nexus Universe capital-reader room materials. **7.1.4.4** No-reliance shall not prevent future lawful external action. It means that any future action must be independently authorized, advised, approved, financed, insured, procured, consented, contracted, or executed by competent actors through separate lawful records. **7.1.4.5** The governing rule shall be: **Finance-readiness may inform lawful consideration; it shall not become the basis of reliance.** *** ### 7.1.5 Finance-Readiness as Public-Good Output **7.1.5.1** Finance-readiness shall be a public-good output of the National Investors Council. **7.1.5.2** As a public-good output, finance-readiness shall serve national resilience, public-good legitimacy, evidence integrity, safeguard protection, public authority learning, capital-reader understanding, development-readiness, disaster-risk finance learning, lawful handoff discipline, and correctionability. **7.1.5.3** Finance-readiness shall not be a private deal product, proprietary investment memorandum, provider sales document, sponsor promotion, securities material, insurance submission, donor application, public finance request, procurement document, or transaction document by default. **7.1.5.4** Where public-good finance-readiness outputs are later used by lawful external actors, they must retain their source status, no-reliance language, limitations, safeguards, claims limits, and correction history unless lawfully transformed by a separate competent process outside the Council. **7.1.5.5** The governing rule shall be: **Finance-readiness belongs first to the public-good record, not to private transaction use.** *** ### 7.1.6 Finance-Readiness as Handoff Preparation **7.1.6.1** Finance-readiness may support lawful handoff preparation. **7.1.6.2** Handoff preparation means identifying the conditions, dependencies, restrictions, gaps, claims limits, safeguards, public authority requirements, finance and insurance questions, donor and public finance relevance, National Consortium Company interface questions, Project SPV-readiness questions, Nexus Rail routes, AEP Passport finance-layer inputs, Docket items, and correction requirements that must travel with a matter before a competent receiving actor may consider next steps. **7.1.6.3** Handoff preparation shall not be handoff completion. It shall not mean transaction readiness, investment approval, insurance approval, donor support, public finance allocation, procurement status, Company approval, SPV approval, project approval, public authority approval, consent, certification, or execution authorization. **7.1.6.4** Any handoff record shall identify what has been prepared, what remains unresolved, who may receive the matter, what the recipient may and may not infer, and what further lawful processes are required. **7.1.6.5** The governing rule shall be: **Finance-readiness may prepare the path to lawful handoff; it does not cross the handoff line by itself.** *** ### 7.1.7 Finance-Readiness as Correctionable Record **7.1.7.1** Finance-readiness shall be a correctionable record. **7.1.7.2** A finance-readiness record shall remain subject to amendment, narrowing, reclassification, restriction, withdrawal, supersession, suspension, renewal, archive, or public-safe correction where facts change, errors are identified, assumptions fail, evidence is updated, public authority status changes, safeguards are revised, conflicts emerge, claims are overstated, or reliance risk arises. **7.1.7.3** Correction shall apply to both substance and language. A technically accurate record may still require correction where its wording implies financeability, bankability, investment readiness, insurance approval, donor commitment, public finance allocation, project approval, SPV authorization, public authority approval, procurement status, certification, consent, or execution. **7.1.7.4** Correction records shall preserve the history of what changed and why so that superseded finance-readiness statements do not continue circulating as current claims. **7.1.7.5** The governing rule shall be: **Finance-readiness is trustworthy only while it remains correctable.** *** ### 7.1.8 Finance-Readiness as Distinct From Financeability **7.1.8.1** Finance-readiness shall be strictly distinguished from financeability. **7.1.8.2** Finance-readiness means a matter has been structured for capital-reader understanding and gap identification. Financeability means a determination, if any, by competent finance actors through their own lawful processes that a matter may be financed under specific conditions. **7.1.8.3** The National Investors Council shall not determine financeability. **7.1.8.4** No finance-readiness output, capital-reader room, investor question, donor relevance note, public finance relevance note, insurance-readiness note, AEP Passport finance-layer input, Nexus Rail finance-readiness note, Docket item, National Model inclusion, Nexus Universe presentation, or handoff record shall be described as financeability unless a separate competent external finance process supports that exact claim. **7.1.8.5** The governing rule shall be: **Finance-readiness is the ability to be understood; financeability is not created by understanding.** *** ### 7.1.9 Finance-Readiness as Distinct From Bankability **7.1.9.1** Finance-readiness shall be strictly distinguished from bankability. **7.1.9.2** Finance-readiness may identify whether banks or lenders could understand the evidence, risks, assumptions, dependencies, safeguards, and gaps of a matter. Bankability, if applicable, belongs to competent banks, lenders, credit committees, public finance authorities, guarantee actors, or other lawful finance actors through separate processes. **7.1.9.3** The National Investors Council shall not declare any matter bankable. **7.1.9.4** Bank participation, lender participation, capital-reader room participation, credit-readability review, public finance relevance, guarantee-readiness questions, or SPV-readiness review shall not imply bankability. **7.1.9.5** The governing rule shall be: **A bank may read a matter in Council context; that does not make the matter bankable.** *** ### 7.1.10 Finance-Readiness as Distinct From Investment Readiness **7.1.10.1** Finance-readiness shall be strictly distinguished from investment readiness. **7.1.10.2** Finance-readiness may identify whether investors can understand the matter’s evidence, risk, assumptions, dependencies, safeguards, gaps, and handoff conditions. Investment readiness, if applicable, belongs to investors and their lawful investment, fiduciary, compliance, diligence, valuation, mandate, risk, legal, tax, and governance processes. **7.1.10.3** The National Investors Council shall not declare any matter investment-ready. **7.1.10.4** Investor participation, institutional investor interest, family office attendance, infrastructure investor questions, Nexus Universe capital-room visibility, AEP Passport candidacy, Nexus Rail candidacy, or SPV-readiness review shall not imply investment readiness. **7.1.10.5** The governing rule shall be: **Investment readiness cannot be created by Council participation, Council visibility, or Council language.** *** ## 7.2 Finance-Readiness Dimensions ### 7.2.1 Evidence Basis **7.2.1.1** Every finance-readiness review shall identify the evidence basis of the matter under review. **7.2.1.2** Evidence basis may include technical studies, GCRI-aligned methods, observability records, National Model records, Nexus Universe outputs, National Working Group outputs, public authority learning records, safeguard records, community inputs, environmental and social information, provider materials, sponsor materials, public datasets, geospatial data, risk models, infrastructure assessments, financial assumptions, insurance information, and prior Docket or correction records. **7.2.1.3** The evidence basis shall distinguish verified evidence, preliminary evidence, modelled evidence, simulation evidence, pilot evidence, provider-supplied evidence, sponsor-supplied evidence, public authority evidence, community evidence, confidential evidence, public-safe evidence, and unresolved evidence. **7.2.1.4** Evidence basis review shall not certify the evidence, complete diligence, validate providers, approve finance, approve insurance, approve donor support, approve public finance, or authorize execution. **7.2.1.5** The governing rule shall be: **Finance-readiness must begin by stating what evidence exists, what evidence does not exist, and how far the evidence can safely travel.** *** ### 7.2.2 Technical Readiness **7.2.2.1** Finance-readiness shall include review of technical readiness where technical systems, infrastructure, software, hardware, AI models, observability systems, digital twins, cyber systems, geospatial systems, sensor networks, AI-RAN/O-RAN/private wireless, compute, energy, water, transport, health, nature, or other technical matters affect capital-readability. **7.2.2.2** Technical readiness review may identify maturity, interoperability, deployment status, operational limits, testing status, maintenance requirements, cyber requirements, data dependencies, standards-interface questions, provider-neutral capability needs, and technical uncertainty. **7.2.2.3** Technical readiness review shall not constitute technical certification, standards conformance, provider validation, procurement eligibility, Nexus-ready status, public authority approval, financeability, bankability, insurability, or execution readiness. **7.2.2.4** Technical limitations shall be carried into finance-readiness outputs so that capital readers do not overread technical materials as mature, deployable, or financeable. **7.2.2.5** The governing rule shall be: **Technical readiness can support finance-readiness only when technical uncertainty remains visible.** *** ### 7.2.3 Public Authority Status **7.2.3.1** Finance-readiness shall include review of public authority status. **7.2.3.2** Public authority status review shall identify whether a matter involves public authority participation, observation, learning, technical input, official review, public finance relevance, procurement dependency, regulatory dependency, permit dependency, licence dependency, public utility dependency, emergency-management dependency, public safety dependency, public data dependency, or no public authority status. **7.2.3.3** Public authority presence shall be capacity-classified and shall not be treated as approval, endorsement, policy adoption, public finance allocation, procurement status, permit, licence, delegation, public warning, emergency command, or official position unless a lawful public authority record supports that exact status. **7.2.3.4** Public authority status shall be reviewed before any capital-facing, donor-facing, insurer-facing, public finance-facing, Nexus Universe, AEP Passport, Nexus Rail, Docket, National Model, or handoff material is circulated. **7.2.3.5** The governing rule shall be: **Capital-readiness cannot safely speak about public matters without exact public authority status.** *** ### 7.2.4 Governance Structure **7.2.4.1** Finance-readiness shall include review of governance structure. **7.2.4.2** Governance structure may include National Council role, National Investors Council role, National Leadership Council role, Helix Council inputs, National Working Group outputs, Stewardship Board oversight where formed, National Secretariat or National Desk support, GCRI evidence interface, GRF claims and legitimacy interface, GRA finance-readiness interface, Regional Nexus Consortium interface, Global Nexus Consortium interface, National Consortium Company interface, Project SPV-readiness pathway, public authority dependency, and enterprise handoff. **7.2.4.3** Governance review shall identify who may record, review, recommend, adopt, reject, defer, restrict, hand off, correct, archive, or renew a matter. **7.2.4.4** Governance review shall not create authority where none exists, appoint boards, bind institutions, approve finance, approve insurance, approve donor support, approve public finance, approve projects, or authorize execution. **7.2.4.5** The governing rule shall be: **Finance-readiness requires knowing who governs the record before anyone reads it as opportunity.** *** ### 7.2.5 Legal Pathway **7.2.5.1** Finance-readiness shall include identification of the legal pathway relevant to the matter. **7.2.5.2** Legal pathway review may identify corporate authority, nonprofit authority, public authority authority, contractual requirements, permits, licences, procurement rules, securities laws, banking laws, insurance laws, public finance laws, tax issues, data laws, privacy laws, cyber laws, environmental law, Indigenous rights where applicable, land and asset rights, sanctions, anti-corruption, competition law, fiduciary obligations, and regulated-perimeter constraints. **7.2.5.3** Legal pathway review by the Council shall be issue-spotting only and shall not constitute legal advice, legal clearance, regulatory approval, tax advice, securities advice, insurance advice, procurement advice, fiduciary advice, compliance certification, or project authorization. **7.2.5.4** Material legal dependencies shall be routed to competent legal or public authority pathways. **7.2.5.5** The governing rule shall be: **Finance-readiness may identify the legal path; it does not walk or approve the legal path.** *** ### 7.2.6 Procurement Dependency **7.2.6.1** Finance-readiness shall include review of procurement dependencies where public authority, National Consortium Company, Project SPV, provider, infrastructure, technology, service, operator, contractor, or public finance pathways may require procurement or contracting. **7.2.6.2** Procurement dependency review may identify public procurement requirements, competitive process requirements, vendor eligibility, technical specification requirements, provider-neutrality requirements, conflict conditions, anti-corruption requirements, bid integrity issues, contract award dependencies, and procurement timing. **7.2.6.3** Procurement dependency review shall not create procurement status, prequalification, preferred-provider status, tender status, contract award, purchasing approval, provider validation, or procurement advice. **7.2.6.4** Procurement dependencies shall be carried into finance-readiness and handoff records so that capital readers do not mistake readiness for procurement eligibility. **7.2.6.5** The governing rule shall be: **A matter cannot be finance-ready for handoff if procurement dependencies are hidden or misclassified.** *** ### 7.2.7 Revenue and Cost Assumptions **7.2.7.1** Finance-readiness shall include review of revenue and cost assumptions where such assumptions affect capital-readability, donor relevance, public finance relevance, insurance-readiness, SPV-readiness, or handoff. **7.2.7.2** Revenue and cost assumptions may include capital expenditure, operating expenditure, service fees, public payments, user fees, tariffs, grants, subsidies, donor support, philanthropic support, public finance, insurance costs, maintenance costs, data costs, cyber costs, staffing costs, decommissioning costs, lifecycle costs, and contingent liabilities. **7.2.7.3** The Council shall distinguish actual records, estimates, assumptions, modelled scenarios, provider-supplied figures, sponsor-supplied figures, public authority figures, audited figures, unaudited figures, and unknown figures. **7.2.7.4** Review of revenue and cost assumptions shall not approve forecasts, valuations, budgets, financeability, bankability, public finance, donor funding, investment, lending, tax treatment, accounting treatment, or transaction structure. **7.2.7.5** The governing rule shall be: **Revenue and cost assumptions are readable only when their source, uncertainty, and non-approval status are clear.** *** ### 7.2.8 Lifecycle and Maintenance Assumptions **7.2.8.1** Finance-readiness shall include review of lifecycle and maintenance assumptions. **7.2.8.2** Lifecycle and maintenance assumptions may include long-term operations, maintenance, replacement, software support, cybersecurity updates, hardware refresh, data stewardship, model maintenance, training, staffing, spare parts, energy requirements, resilience upgrades, decommissioning, continuity, insurance renewal, compliance, and governance renewal. **7.2.8.3** The Council shall identify whether lifecycle obligations are funded, unfunded, estimated, unknown, public authority-dependent, donor-dependent, provider-dependent, Company-dependent, SPV-dependent, or unresolved. **7.2.8.4** Lifecycle and maintenance review shall not approve budgets, financing, procurement, operations, provider selection, insurance, public finance, donor support, or execution. **7.2.8.5** The governing rule shall be: **A capital-readable matter must disclose who may carry the lifecycle burden before anyone can safely discuss readiness.** *** ### 7.2.9 Risk Allocation **7.2.9.1** Finance-readiness shall include review of risk allocation questions. **7.2.9.2** Risk allocation may include technology risk, construction risk, operating risk, data risk, cyber risk, public authority risk, procurement risk, legal risk, revenue risk, demand risk, climate risk, disaster risk, environmental risk, social risk, community risk, Indigenous protocol risk where applicable, safeguard risk, insurance risk, finance risk, donor risk, public finance risk, political risk, counterparty risk, and lifecycle risk. **7.2.9.3** The Council may identify who may need to consider, accept, mitigate, insure, transfer, retain, or govern a risk, but shall not allocate risk contractually or financially. **7.2.9.4** Risk allocation questions shall be routed to competent legal, finance, insurance, public authority, procurement, Company, SPV, safeguard, or operational pathways where required. **7.2.9.5** The governing rule shall be: **Finance-readiness can identify risk allocation questions; it cannot allocate risk by record.** *** ### 7.2.10 Insurance and Risk Transfer **7.2.10.1** Finance-readiness shall include review of insurance and risk-transfer questions where relevant. **7.2.10.2** Insurance and risk-transfer review may include coverage needs, insurable interests, risk-transfer structures, reinsurance considerations, public guarantee questions, private guarantee questions, contingent finance, parametric concepts, catastrophe exposure, protection gaps, basis risk, triggers, data dependencies, loss modelling, and claims processes. **7.2.10.3** The Council shall not approve insurance, place insurance, bind coverage, approve reinsurance, approve guarantees, issue risk-transfer conclusions, indicate premiums, determine insurability, or provide insurance advice. **7.2.10.4** Insurance and risk-transfer dependencies shall be recorded as questions, gaps, dependencies, or external-process requirements. **7.2.10.5** The governing rule shall be: **Insurance and risk-transfer readiness identifies what risk actors must examine; it does not transfer the risk.** *** ### 7.2.11 Safeguard Conditions **7.2.11.1** Finance-readiness shall include safeguard conditions. **7.2.11.2** Safeguard conditions may include privacy, cybersecurity, sovereign data, public authority sensitivity, finance sensitivity, insurance sensitivity, donor sensitivity, commercial sensitivity, provider sensitivity, sponsor sensitivity, community sensitivity, Indigenous or protected knowledge where applicable, accessibility, biodiversity, health, infrastructure security, location sensitivity, environmental and social safeguards, consent boundaries, and public-safe reporting limits. **7.2.11.3** Safeguard conditions shall be recorded, carried forward, and not removed to increase apparent financeability, donor appeal, public finance relevance, insurance readiness, SPV-readiness, or project attractiveness. **7.2.11.4** Safeguard condition review shall not constitute safeguard clearance, community consent, Indigenous consent, data authorization, publication authorization, or handoff authorization. **7.2.11.5** The governing rule shall be: **Finance-readiness is invalid in Nexus terms if it improves capital-readability by weakening safeguards.** *** ### 7.2.12 Data, Cyber, and Sovereign Data Conditions **7.2.12.1** Finance-readiness shall include data, cyber, and sovereign data conditions. **7.2.12.2** These conditions may include data rights, data ownership, data quality, data provenance, privacy, consent, cybersecurity controls, access controls, sovereign data requirements, localization requirements, cross-border transfer limits, AI processing limits, model dependency, observability data restrictions, dashboard restrictions, repository controls, digital twin reliability, critical infrastructure sensitivity, and incident-response obligations. **7.2.12.3** Data, cyber, and sovereign data review shall not authorize data sharing, AI processing, publication, commercialization, operationalization, public authority use, provider use, investor use, insurer use, donor use, public finance use, or handoff. **7.2.12.4** Finance-facing records shall disclose material data and cyber limitations in a manner consistent with security and confidentiality requirements. **7.2.12.5** The governing rule shall be: **Capital cannot safely read a digital or observability matter unless data, cyber, and sovereignty conditions are carried with it.** *** ### 7.2.13 Community and Indigenous Protocol Conditions Where Applicable **7.2.13.1** Finance-readiness shall include community and Indigenous protocol conditions where applicable. **7.2.13.2** Such conditions may include community participation limits, Indigenous rights, rights-holder processes, protected knowledge, land relationships, data sovereignty, cultural heritage, consent boundaries, benefit-sharing considerations, local legitimacy, accessibility, language, dignity, non-extractive engagement, and place-based safeguards. **7.2.13.3** Community or Indigenous participation in Council-related work shall not imply community consent, Indigenous consent, rights-holder approval, protected-knowledge permission, social licence, data permission, project approval, finance approval, donor legitimacy, public finance legitimacy, or handoff permission. **7.2.13.4** Finance-readiness records shall carry such protocol conditions into capital-reader, donor, public finance, insurance, SPV-readiness, and handoff materials. **7.2.13.5** The governing rule shall be: **No matter becomes finance-ready by converting community or Indigenous presence into consent.** *** ### 7.2.14 Environmental and Social Conditions **7.2.14.1** Finance-readiness shall include environmental and social conditions. **7.2.14.2** Environmental and social conditions may include climate impacts, biodiversity impacts, nature dependencies, water impacts, energy impacts, food systems impacts, health impacts, pollution risks, land impacts, displacement risks, labour conditions, accessibility, gender and inclusion considerations, community impacts, ecosystem services, resilience benefits, and environmental and social safeguard requirements. **7.2.14.3** Environmental and social condition review shall not constitute environmental approval, social approval, safeguard clearance, donor approval, public finance approval, insurance approval, community consent, Indigenous consent, procurement approval, or project authorization. **7.2.14.4** Environmental and social limitations shall not be omitted from finance-readiness outputs to improve apparent bankability, financeability, donor relevance, public finance relevance, or SPV-readiness. **7.2.14.5** The governing rule shall be: **Capital-readiness must include environmental and social truth before it can claim readiness as public-good output.** *** ### 7.2.15 Project SPV-Readiness Conditions **7.2.15.1** Finance-readiness shall include Project SPV-readiness conditions where a matter may later require a project-specific lawful vehicle. **7.2.15.2** SPV-readiness conditions may include legal form, governance, ownership, public authority approvals, procurement, permits, licences, finance, insurance, donor support, public finance, contracts, revenue or value logic, risk allocation, provider-neutrality, data rights, land or asset rights, safeguards, consent boundaries, lifecycle obligations, operator responsibility, reporting, audit, and exit or decommissioning. **7.2.15.3** SPV-readiness conditions shall not constitute SPV approval, project approval, financeability, bankability, insurability, procurement readiness, provider selection, public authority approval, consent, or execution authorization. **7.2.15.4** The Council shall identify unresolved SPV-readiness conditions and route them to competent legal, governance, finance, insurance, public authority, procurement, safeguard, Company, SPV, or Docket pathways. **7.2.15.5** The governing rule shall be: **SPV-readiness conditions show what must be true before an SPV can be considered; they do not make the SPV true.** *** ### 7.2.16 National Consortium Company Interface Conditions **7.2.16.1** Finance-readiness shall include National Consortium Company interface conditions where a matter may later be routed toward a National Consortium Company. **7.2.16.2** Company interface conditions may include public-good source record, National Council authorization, Stewardship Board oversight where formed, finance-readiness dependencies, insurance-readiness dependencies, donor relevance, public finance relevance, public authority dependencies, safeguard dependencies, provider-neutrality requirements, conflicts, claims limits, enterprise-stack boundary controls, handoff conditions, and correction pathway. **7.2.16.3** Company interface conditions shall not constitute Company approval, Company obligation, Company authority, finance approval, insurance approval, public finance approval, donor approval, procurement status, project approval, consent, or execution authority. **7.2.16.4** The Council shall not act as or for the National Consortium Company. **7.2.16.5** The governing rule shall be: **A Company interface condition may prepare a lawful handoff question; it does not create Company action.** *** ## 7.3 Finance-Readiness Outputs ### 7.3.1 Finance-Readiness Gap Note **7.3.1.1** The National Investors Council may produce a Finance-Readiness Gap Note. **7.3.1.2** A Finance-Readiness Gap Note shall identify material gaps affecting capital-readability, including evidence gaps, technical gaps, public authority gaps, legal gaps, procurement gaps, data and cyber gaps, safeguard gaps, insurance gaps, donor gaps, public finance gaps, SPV-readiness gaps, Company interface gaps, Nexus Rail gaps, AEP Passport finance-layer gaps, Docket issues, and handoff gaps. **7.3.1.3** The Note shall classify each gap as information-needed, evidence-needed, technical-needed, data-needed, cyber-needed, legal-needed, public-authority-needed, procurement-needed, finance-readiness-needed, insurance-readiness-needed, public-finance-needed, donor-needed, safeguard-needed, SPV-needed, Company-interface-needed, Docketed, restricted, handoff-blocking, or correction-needed. **7.3.1.4** A Finance-Readiness Gap Note shall not be treated as completed diligence, finance approval, investment advice, insurance approval, donor approval, public finance approval, procurement clearance, certification, SPV approval, project approval, or execution readiness. **7.3.1.5** The governing rule shall be: **A Finance-Readiness Gap Note exists to prevent unresolved gaps from being hidden behind readiness language.** *** ### 7.3.2 Capital-Readability Question Set **7.3.2.1** The National Investors Council may produce a Capital-Readability Question Set. **7.3.2.2** The Question Set may identify questions that capital readers would need answered to understand the matter, including problem definition, evidence basis, technical status, public authority status, governance, legal pathway, procurement dependency, cost and revenue assumptions, lifecycle obligations, risk allocation, insurance-readiness, donor relevance, public finance relevance, safeguards, data and cyber conditions, SPV-readiness, Company interface, and handoff limits. **7.3.2.3** The Question Set shall be framed as questions and not as conclusions, approvals, commitments, ratings, recommendations, diligence completion, investment materials, loan materials, insurance submissions, donor applications, public finance requests, procurement documents, or transaction documents. **7.3.2.4** The Question Set shall carry no-reliance, non-advisory, non-soliciting, non-transactional, confidentiality, claims, and correction language. **7.3.2.5** The governing rule shall be: **A Capital-Readability Question Set helps readers ask what matters; it does not answer as finance authority.** *** ### 7.3.3 Diligence-Gap Map **7.3.3.1** The National Investors Council may produce a Diligence-Gap Map. **7.3.3.2** A Diligence-Gap Map shall organize unresolved diligence issues across evidence, technical readiness, public authority status, legal pathway, procurement, data, cyber, safeguards, community protocols, environmental and social conditions, revenue and cost assumptions, lifecycle, risk allocation, insurance, public finance, donor relevance, SPV-readiness, Company interface, Nexus Rail routing, AEP Passport finance-layer inputs, Docket status, and handoff conditions. **7.3.3.3** A Diligence-Gap Map shall identify which gaps block public release, capital-reader review, donor review, insurer review, public finance review, SPV-readiness review, AEP Passport finance-layer input, Nexus Rail routing, or enterprise handoff. **7.3.3.4** A Diligence-Gap Map shall not be treated as due diligence completion or clearance. **7.3.3.5** The governing rule shall be: **A Diligence-Gap Map is valuable because it records what still prevents reliance.** *** ### 7.3.4 Public Authority Dependency Note **7.3.4.1** The National Investors Council may produce a Public Authority Dependency Note. **7.3.4.2** The Note shall identify public authority dependencies relevant to finance-readiness, including regulatory approvals, permits, licences, procurement, public finance, public guarantees, budget actions, public utility permissions, public data permissions, emergency-management authority, public safety authority, environmental authority, infrastructure authority, health authority, or other official processes. **7.3.4.3** The Note shall state public authority participation status, including whether public authority actors are official, observer, learner, technical, public-safe reviewer, public finance reader, personal-capacity participant, no official position, or not yet engaged. **7.3.4.4** A Public Authority Dependency Note shall not be treated as public authority approval, public finance allocation, procurement status, permit, licence, policy adoption, public warning, emergency command, official position, or endorsement. **7.3.4.5** The governing rule shall be: **A Public Authority Dependency Note identifies official dependencies; it does not satisfy them.** *** ### 7.3.5 Procurement Dependency Note **7.3.5.1** The National Investors Council may produce a Procurement Dependency Note. **7.3.5.2** The Note shall identify procurement-related conditions affecting finance-readiness, including public procurement requirements, competitive process needs, vendor-neutral specifications, technical requirements, conflicts, anti-corruption controls, bid integrity, contract award dependencies, provider-neutrality conditions, and procurement timing. **7.3.5.3** The Note shall distinguish provider information from procurement status and shall identify whether a matter is provider-supplied, provider-neutral, procurement-dependent, procurement-restricted, procurement-blocked, or procurement-unreviewed. **7.3.5.4** A Procurement Dependency Note shall not create procurement status, prequalification, preferred-provider status, tender status, contract award, purchasing approval, provider validation, or procurement advice. **7.3.5.5** The governing rule shall be: **Procurement dependencies may be recorded only so that readiness is not mistaken for procurement eligibility.** *** ### 7.3.6 Insurance-Readiness Note **7.3.6.1** The National Investors Council may produce an Insurance-Readiness Note. **7.3.6.2** The Note may identify exposure questions, hazard questions, vulnerability questions, loss questions, risk controls, resilience measures, insurance requirements, reinsurance questions, data and model dependencies, cyber conditions, infrastructure insurance questions, public authority insurance interfaces, risk-transfer questions, protection gaps, and insurance boundary issues. **7.3.6.3** The Note shall state that it is not insurance advice, underwriting, coverage approval, premium indication, insurability determination, reinsurance support, guarantee approval, or insurance placement. **7.3.6.4** Insurance-Readiness Notes shall be no-reliance, competition-compliant, confidentiality-aware, claims-limited, and correctionable. **7.3.6.5** The governing rule shall be: **An Insurance-Readiness Note records insurance questions; it shall never be read as insurance approval.** *** ### 7.3.7 Public Finance Relevance Note **7.3.7.1** The National Investors Council may produce a Public Finance Relevance Note. **7.3.7.2** The Note may identify public finance relevance, public investment logic, budget dependencies, public guarantee questions, public grant questions, subsidy questions, concessional finance relevance, resilience finance relevance, disaster-risk finance relevance, climate finance relevance, infrastructure finance relevance, public-private interface questions, and public authority dependencies. **7.3.7.3** The Note shall state that public finance relevance is not public finance allocation, public funding approval, budget approval, public guarantee, grant award, subsidy approval, procurement status, official position, or government endorsement. **7.3.7.4** Public Finance Relevance Notes shall be public authority-sensitive and claims-limited. **7.3.7.5** The governing rule shall be: **A Public Finance Relevance Note may identify a public finance pathway; it cannot open that pathway by itself.** *** ### 7.3.8 Donor Relevance Note **7.3.8.1** The National Investors Council may produce a Donor Relevance Note. **7.3.8.2** The Note may identify donor mission fit, humanitarian relevance, development relevance, climate relevance, resilience relevance, disaster-risk relevance, public-good value, capacity-building relevance, community-support relevance, evidence needs, reporting needs, safeguard expectations, public authority dependencies, and implementation conditions. **7.3.8.3** The Note shall state that donor relevance is not donor commitment, grant approval, pledge, award, allocation, funding pipeline, development assistance commitment, endorsement, or project approval. **7.3.8.4** Donor Relevance Notes shall avoid creating public expectation of support. **7.3.8.5** The governing rule shall be: **A Donor Relevance Note identifies possible relevance; it never commits donor resources.** *** ### 7.3.9 Philanthropic Relevance Note **7.3.9.1** The National Investors Council may produce a Philanthropic Relevance Note. **7.3.9.2** The Note may identify foundation relevance, CSR relevance, mission-aligned philanthropy relevance, public-good innovation relevance, community relevance, climate relevance, health relevance, nature relevance, education relevance, youth relevance, accessibility relevance, institutional-development relevance, outcome logic, evidence needs, reporting conditions, and safeguard expectations. **7.3.9.3** The Note shall state that philanthropic relevance is not grant approval, foundation commitment, CSR commitment, pledge, award, allocation, sponsorship, philanthropic endorsement, or funding expectation. **7.3.9.4** Philanthropic Relevance Notes shall be public-safe and claims-limited where released. **7.3.9.5** The governing rule shall be: **A Philanthropic Relevance Note may show mission fit, but it shall not imply philanthropic commitment.** *** ### 7.3.10 Project SPV-Readiness Note **7.3.10.1** The National Investors Council may produce a Project SPV-Readiness Note. **7.3.10.2** The Note may identify legal structure questions, governance requirements, public authority approvals, procurement requirements, permits, licences, finance-readiness, insurance-readiness, donor relevance, public finance relevance, revenue or value logic, risk allocation, provider-neutral capability requirements, contracts, data rights, land or asset rights, community consent boundaries, Indigenous consent boundaries where applicable, environmental and social safeguards, cyber obligations, lifecycle responsibility, operator role, National Consortium Company interface, and handoff conditions. **7.3.10.3** The Note shall state that SPV-readiness is not SPV approval, project approval, company formation, financeability, bankability, insurability, procurement readiness, provider selection, public authority approval, consent, or execution authorization. **7.3.10.4** Project SPV-Readiness Notes shall be conflict-reviewed where future enterprise actors may benefit. **7.3.10.5** The governing rule shall be: **A Project SPV-Readiness Note identifies what a future project vehicle would require; it shall not authorize the vehicle.** *** ### 7.3.11 National Consortium Company Finance-Interface Note **7.3.11.1** The National Investors Council may produce a National Consortium Company Finance-Interface Note. **7.3.11.2** The Note may identify conditions relevant to possible future interface with a National Consortium Company, including public-good source record, National Council routing, Stewardship Board oversight where formed, finance-readiness dependencies, insurance-readiness dependencies, donor relevance, public finance relevance, public authority dependencies, safeguard dependencies, provider-neutrality requirements, conflicts, claims limits, enterprise-stack boundary controls, handoff conditions, and correction pathway. **7.3.11.3** The Note shall state that it does not create Company approval, Company obligation, Company authority, finance approval, insurance approval, donor approval, public finance approval, procurement status, project approval, consent, or execution authority. **7.3.11.4** The Council shall not use a Company Finance-Interface Note to direct or bind the Company. **7.3.11.5** The governing rule shall be: **A Company Finance-Interface Note prepares questions for possible enterprise interface; it does not create enterprise action.** *** ### 7.3.12 Nexus Rail Finance-Readiness Note **7.3.12.1** The National Investors Council may produce a Nexus Rail Finance-Readiness Note. **7.3.12.2** The Note may identify source record, proposed route, receiving pathway, routeability status, finance-readiness status, insurance-readiness status, donor relevance, public finance relevance, safeguard conditions, public authority dependencies, unresolved gaps, claims limits, confidentiality class, no-reliance status, Docket status, AEP Passport finance-layer status, handoff status, and correction pathway. **7.3.12.3** The Note shall state that Rail finance-readiness is not Rail execution, finance approval, insurance approval, donor approval, public finance allocation, procurement status, certification, consent, handoff completion, or execution authority. **7.3.12.4** Rail notes shall identify whether the route is proposed, candidate, deferred, restricted, blocked, Docketed, corrected, superseded, archived, or renewed. **7.3.12.5** The governing rule shall be: **A Nexus Rail Finance-Readiness Note maps possible routeability; it does not execute the route.** *** ### 7.3.13 AEP Passport Finance-Readiness Layer Input **7.3.13.1** The National Investors Council may produce an AEP Passport Finance-Readiness Layer Input for AEP Passport candidate pathways. **7.3.13.2** The Input may identify capital-readable evidence needs, finance-readiness dependencies, insurance-readiness questions, donor relevance, public finance relevance, diligence gaps, risk allocation questions, safeguard conditions, public authority dependencies, SPV-readiness conditions, Docket issues, Nexus Rail routeability, and handoff limitations. **7.3.13.3** The Input shall state that it does not issue an AEP Passport, approve AEP Passport status, certify a candidate, create Nexus-ready status, approve financeability, approve bankability, approve insurability, approve procurement, approve public authority status, create consent, approve a project, or authorize execution. **7.3.13.4** The Input shall remain subject to competent AEP Passport process authority and shall not be used independently as a status claim. **7.3.13.5** The governing rule shall be: **An AEP Passport Finance-Readiness Layer Input contributes intelligence to the Passport pathway; it does not become the Passport.** *** ### 7.3.14 Finance-Readiness Correction Note **7.3.14.1** The National Investors Council may produce a Finance-Readiness Correction Note. **7.3.14.2** A Correction Note shall identify the overclaim, error, omission, misclassification, outdated record, false reliance risk, public authority ambiguity, finance overstatement, insurance overstatement, donor overstatement, public finance overstatement, SPV overstatement, Rail overstatement, AEP Passport overstatement, Company interface overstatement, safeguard omission, confidentiality issue, or execution implication requiring correction. **7.3.14.3** The Correction Note may prescribe claim narrowing, no-reliance clarification, public clarification, controlled clarification, role reclassification, publication reclassification, conflict disclosure, safeguard correction, Docket entry, handoff restriction, withdrawal, suspension, supersession, archive, or renewal. **7.3.14.4** Correction Notes shall be implemented with urgency where external reliance, public trust, market signal, donor expectation, public finance expectation, insurer expectation, sponsor advantage, provider advantage, public authority confusion, or community harm risk exists. **7.3.14.5** The governing rule shall be: **A Finance-Readiness Correction Note prevents readiness language from becoming false reliance.** *** ## 7.4 Finance-Readiness Boundaries ### 7.4.1 No Investment Advice **7.4.1.1** Finance-readiness shall not include investment advice. **7.4.1.2** The National Investors Council shall not recommend that any person buy, sell, hold, invest in, finance, fund, lend to, participate in, or avoid any security, project, Company, SPV, provider, sponsor, transaction, instrument, or opportunity. **7.4.1.3** Any discussion of investor questions, capital-readability, risk-to-capital translation, SPV-readiness, or handoff shall remain no-reliance and non-advisory. **7.4.1.4** Participants shall not use Council outputs as investment advice internally or externally. **7.4.1.5** The governing rule shall be: **Finance-readiness may organize questions for investors; it shall never advise investment.** *** ### 7.4.2 No Financial Advice **7.4.2.1** Finance-readiness shall not include financial advice. **7.4.2.2** The National Investors Council shall not advise on financial structuring, financing strategy, capital structure, debt terms, equity terms, valuations, returns, pricing, guarantees, public finance strategy, donor strategy, tax implications, accounting treatment, transaction timing, or financial suitability. **7.4.2.3** The Council may identify that financial advice may be required from competent external advisers outside the Council. **7.4.2.4** No finance-readiness output shall be used as financial advice. **7.4.2.5** The governing rule shall be: **The Council may identify financial questions; it shall not give financial answers as advice.** *** ### 7.4.3 No Securities Offering **7.4.3.1** Finance-readiness shall not include securities offering activity. **7.4.3.2** The National Investors Council shall not offer securities, market securities, list securities, distribute offering documents, promote securities, facilitate securities trading, solicit securities investment, or match securities issuers with investors. **7.4.3.3** Council materials shall not be used as offering memoranda, private placement memoranda, securities summaries, investor decks, subscription materials, or capital-raising materials. **7.4.3.4** Any securities-related matter shall be routed outside the Council to competent lawful actors and regulated processes. **7.4.3.5** The governing rule shall be: **The Council is not a securities platform, and finance-readiness is not an offering.** *** ### 7.4.4 No Capital Solicitation **7.4.4.1** Finance-readiness shall not include capital solicitation. **7.4.4.2** The National Investors Council shall not solicit investments, loans, guarantees, donations, grants, philanthropic commitments, public finance, insurance, reinsurance, sponsorship, or transaction participation. **7.4.4.3** Capital-reader rooms, Nexus Universe sessions, National Model finance layers, AEP Passport finance-layer inputs, Nexus Rail finance notes, and handoff discussions shall be structured to prevent solicitation. **7.4.4.4** Any solicitation activity shall be stopped, corrected, restricted, or routed outside the Council. **7.4.4.5** The governing rule shall be: **Finance-readiness asks what would need to be understood; it does not ask for money.** *** ### 7.4.5 No Brokerage **7.4.5.1** Finance-readiness shall not include brokerage. **7.4.5.2** The National Investors Council shall not broker investments, loans, insurance, reinsurance, guarantees, donor funding, public finance, securities, procurement, or transactions. **7.4.5.3** The Council shall not introduce parties for compensation, intermediate negotiations, arrange deals, structure placements, or act as finder. **7.4.5.4** Participant networking shall not be represented as Council brokerage, transaction arrangement, or capital introduction. **7.4.5.5** The governing rule shall be: **The Council connects records to readiness pathways, not counterparties to deals.** *** ### 7.4.6 No Lending **7.4.6.1** Finance-readiness shall not include lending. **7.4.6.2** The National Investors Council shall not originate loans, approve loans, negotiate credit, issue term sheets, assess creditworthiness as lender, provide credit support, approve debt service capacity, or create lending commitments. **7.4.6.3** Bank or lender participation shall not imply lending interest, credit approval, debt availability, guarantee support, bankability, financeability, or transaction readiness. **7.4.6.4** Lending matters shall be handled by competent lending actors through separate lawful processes. **7.4.6.5** The governing rule shall be: **Finance-readiness may identify lending questions; lending happens only outside the Council.** *** ### 7.4.7 No Underwriting **7.4.7.1** Finance-readiness shall not include underwriting. **7.4.7.2** The National Investors Council shall not underwrite securities, loans, insurance, reinsurance, guarantees, risks, projects, SPVs, National Consortium Company activities, public finance instruments, donor commitments, or disaster-risk-finance instruments. **7.4.7.3** Underwriter, insurer, bank, investor, or guarantee actor participation shall not imply underwriting appetite, capacity, approval, pricing, coverage, term support, or risk acceptance. **7.4.7.4** Underwriting matters shall be routed to competent external actors where lawful and appropriate. **7.4.7.5** The governing rule shall be: **The Council may identify underwriting information needs; it shall not underwrite.** *** ### 7.4.8 No Insurance Placement **7.4.8.1** Finance-readiness shall not include insurance placement. **7.4.8.2** The National Investors Council shall not place insurance, arrange insurance, bind coverage, recommend policies, approve coverage, approve premiums, act as broker, assume risk, settle claims, or provide insurance advice. **7.4.8.3** Insurance-readiness notes, insurer participation, risk-transfer questions, and Nexus Universe insurance-readiness rooms shall not be treated as insurance placement or insurance approval. **7.4.8.4** Insurance placement may occur only through competent lawful insurance processes outside the Council. **7.4.8.5** The governing rule shall be: **Insurance-readiness can prepare questions for insurance actors; it cannot place insurance.** *** ### 7.4.9 No Rating or Guarantee **7.4.9.1** Finance-readiness shall not include rating or guarantee activity. **7.4.9.2** The National Investors Council shall not issue credit ratings, project ratings, financeability ratings, bankability ratings, insurability ratings, maturity ratings, provider ratings, SPV ratings, public finance ratings, donor-readiness ratings, Nexus-ready ratings, guarantees, credit enhancements, loss protection, or guarantee commitments. **7.4.9.3** Any maturity, Grid, AEP Passport, Nexus Rail, Docket, or readiness input shall not be described as a rating or guarantee. **7.4.9.4** Guarantee-readiness questions shall not imply guarantee availability. **7.4.9.5** The governing rule shall be: **The Council may identify rating or guarantee questions; it shall not rate or guarantee.** *** ### 7.4.10 No Bankability or Financeability Determination **7.4.10.1** Finance-readiness shall not include bankability or financeability determination. **7.4.10.2** The National Investors Council shall not determine that any matter is bankable, financeable, fundable, lender-ready, capital-ready, investable, or transaction-ready. **7.4.10.3** Capital-readability, finance-readiness, investor participation, bank participation, donor relevance, public finance relevance, insurance-readiness, SPV-readiness, Nexus Universe visibility, AEP Passport candidacy, Nexus Rail candidacy, or handoff notes shall not be used to imply bankability or financeability. **7.4.10.4** Any bankability or financeability assessment belongs only to competent external actors through separate lawful processes. **7.4.10.5** The governing rule shall be: **The Council can make a matter readable to finance; it cannot declare the matter financeable.** *** ### 7.4.11 No Investment Approval **7.4.11.1** Finance-readiness shall not include investment approval. **7.4.11.2** The National Investors Council shall not approve investments, recommend investment, rank investment opportunities, select projects for investment, approve investor participation, approve portfolios, approve mandates, approve capital allocation, or approve transaction terms. **7.4.11.3** Investment approval belongs only to competent investment actors through their own fiduciary, legal, diligence, risk, compliance, mandate, and governance processes. **7.4.11.4** Any statement implying Council investment approval shall be corrected immediately. **7.4.11.5** The governing rule shall be: **Investment approval is outside the Council in every form.** *** ### 7.4.12 No Transaction Readiness by Participation **7.4.12.1** Participation in the National Investors Council shall not create transaction readiness. **7.4.12.2** A matter shall not be described as transaction-ready because it was discussed in the Council, read by capital readers, presented in Nexus Universe, reviewed for finance-readiness, included in the National Model, referenced in an AEP Passport finance-layer input, routed through Nexus Rails, Docketed, or described in a handoff note. **7.4.12.3** Transaction readiness, if applicable, requires separate lawful documentation, competent approval, professional advice, due diligence, finance process, insurance process, legal process, public authority process, procurement process, corporate process, safeguard process, consent process, and execution authority. **7.4.12.4** Council outputs shall not be used as transaction documents unless lawfully transformed by competent external actors outside the Council with clear separation from the Council source record. **7.4.12.5** The final boundary rule of this Part shall be: **Participation may create a readiness record; it never creates a transaction.** ### Summary Finance-readiness means a matter becomes readable to capital without becoming finance by implication. The Council uses this architecture to translate evidence, expose gaps, preserve safeguards, and prepare lawful handoff without crossing into advice, solicitation, approval, or execution. These readiness rules also define the outputs that can move through [Nexus Rails](/organization/organization/architecture/ii.-definitions/xv.-nexus-rails.md), appear in [Nexus Universe](/organization/cooperation/nexus-universe.md), or inform later enterprise pathways. Every output stays no-reliance, correctionable, and public-good first. ### Next steps 1. [Continue to VIII. ROOMS](/organization/cooperation/consortiums/gateways/national-councils/investors/viii.-rooms.md) 2. [Review VI. PROCEDURE](/organization/cooperation/consortiums/gateways/national-councils/investors/vi.-procedure.md) 3. [Return to 0. Context](/organization/cooperation/consortiums/gateways/national-councils/investors/0.-context.md) --- # 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/vii.-readiness.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.