# XII. CLAIMS ### Summary This section allows claims only where a competent record supports them. It blocks any drift from participation into approval, commitment, finance effect, or execution meaning. It ties claims discipline to the registers and permissions defined in [XI. RECORDS](/organization/cooperation/consortiums/gateways/national-councils/investors/xi.-records.md), to room conduct in [VIII. ROOMS](/organization/cooperation/consortiums/gateways/national-councils/investors/viii.-rooms.md), and to finance-readiness boundaries in [VII. READINESS](/organization/cooperation/consortiums/gateways/national-councils/investors/vii.-readiness.md). It also defines how public-safe reporting may explain readiness learning across [Nexus Universe](/organization/cooperation/nexus-universe.md) and [Nexus Rails](/organization/organization/architecture/ii.-definitions/xv.-nexus-rails.md) without creating market signal, donor expectation, public finance expectation, or public authority confusion. ## 12.1 Permitted Claims Permitted claims depend on recorded participation, role classification, and claims permissions. They must stay inside the record controls defined in [XI. RECORDS](/organization/cooperation/consortiums/gateways/national-councils/investors/xi.-records.md) and the readiness boundaries defined in [VII. READINESS](/organization/cooperation/consortiums/gateways/national-councils/investors/vii.-readiness.md). ### 12.1.1 Participation Claim **12.1.1.1** A person or institution may make a participation claim only where participation in the National Investors Council, a Council room, a Council workstream, a Nexus Universe finance-readiness activity, an AEP Passport finance-layer input process, a Nexus Rail finance-readiness process, a Project SPV-readiness discussion, or a National Consortium Company finance-interface discussion is supported by a competent record. **12.1.1.2** A permitted participation claim may state, in approved language, that the person or institution participated in a defined National Investors Council activity, at a defined level, in a defined role, during a defined period, subject to the applicable no-reliance, non-advisory, non-solicitation, non-transaction, confidentiality, safeguard, and claims limits. **12.1.1.3** A participation claim shall not state or imply investment approval, financeability, bankability, insurability, insurance approval, reinsurance approval, underwriting, guarantee support, rating, public finance approval, donor commitment, philanthropic commitment, capital commitment, securities offering, solicitation, transaction readiness, project approval, Project SPV approval, AEP Passport status, Nexus-ready status, procurement status, public authority approval, community consent, Indigenous consent, National Consortium Company approval, or execution authority. **12.1.1.4** Participation claims shall use role-specific and record-specific language and shall not enlarge participation into authority, endorsement, commitment, validation, certification, approval, or finance effect. **12.1.1.5** The governing rule shall be: **Participation may be claimed only as participation, never as approval, commitment, finance, insurance, public authority action, consent, or execution.** *** ### 12.1.2 National Investors Council Membership Claim **12.1.2.1** A National Investors Council membership claim may be made only where the participant’s membership, participation standing, subscription standing where applicable, or Council status is recorded in the National Investors Council Participation Register. **12.1.2.2** A permitted membership claim may state that the person or institution is a member, participant, observer, guest, institutional representative, capital reader, finance-readiness contributor, insurance-readiness contributor, public finance relevance contributor, donor relevance contributor, philanthropic relevance contributor, development-readiness contributor, or other recorded category of the National Investors Council, as applicable. **12.1.2.3** A membership claim shall state or imply no more than the recorded status, and shall remain subject to role classification, good standing, conflict status, confidentiality obligations, no-reliance terms, claims permissions, safeguard duties, and correctionability. **12.1.2.4** National Investors Council membership shall not mean investment committee membership, fund membership, GRA membership, GRF membership, GCRI membership, public authority appointment, National Consortium Company office, Project SPV role, fiduciary appointment, procurement role, certification role, donor role, insurer role, or execution role unless separately and lawfully recorded by the competent body. **12.1.2.5** The governing rule shall be: **Membership in the National Investors Council is participation in a finance-readiness gateway, not membership in a finance-execution body.** *** ### 12.1.3 Capital-Reader Participation Claim **12.1.3.1** A capital-reader participation claim may be made only where the participant is recorded in the Capital-Reader Register or other competent Council record. **12.1.3.2** A permitted capital-reader claim may state that the person or institution participated as a capital reader, attended a Capital-Reader Room, reviewed capital-readability questions, contributed to a no-reliance finance-readiness discussion, or helped identify capital-readability gaps, subject to the record. **12.1.3.3** A capital-reader claim shall not state or imply investment interest, lending interest, capital commitment, underwriting interest, donor interest, public finance support, guarantee support, financing mandate, investor endorsement, bankability, financeability, transaction readiness, project approval, or capital availability. **12.1.3.4** Where a capital reader is named in public or controlled materials, the reference shall be authorized, capacity-classified, claims-limited, and consistent with confidentiality and no-reliance obligations. **12.1.3.5** The governing rule shall be: **A capital-reader claim means the participant read or contributed to readiness questions; it does not mean capital moved or may move.** *** ### 12.1.4 Insurance-Readiness Participation Claim **12.1.4.1** An insurance-readiness participation claim may be made only where the participant is recorded in the Insurance-Readiness Participant Register or other competent Council record. **12.1.4.2** A permitted claim may state that the participant contributed to insurance-readiness questions, reinsurance-readiness questions, risk-transfer questions, protection-gap questions, disaster-risk finance questions, exposure questions, data and model dependency questions, or Insurance-Readiness Room discussion, subject to the record. **12.1.4.3** The claim shall not state or imply insurance approval, coverage availability, underwriting, premium indication, reinsurance support, risk-transfer approval, guarantee support, insurance advice, broker engagement, insurance placement, insurability, or insurer endorsement. **12.1.4.4** Insurer, reinsurer, broker, risk-transfer, or guarantee-related references shall be especially controlled where public or market audiences may infer approval or capacity. **12.1.4.5** The governing rule shall be: **Insurance-readiness participation may identify risk questions; it shall not be claimed as insurance support.** *** ### 12.1.5 Public Finance Relevance Participation Claim **12.1.5.1** A public finance relevance participation claim may be made only where the participant’s role is recorded in the Public Finance Relevance Register or other competent Council record. **12.1.5.2** A permitted claim may state that a person or institution participated in public finance relevance discussion, public finance dependency review, public investment relevance mapping, public guarantee question formation, public finance learning, or Public Finance Relevance Room activity. **12.1.5.3** A public finance relevance claim shall not state or imply public finance allocation, budget approval, grant approval, subsidy approval, public guarantee, procurement status, official position, government endorsement, public authority approval, or funding expectation. **12.1.5.4** Public authority and public finance participants shall be capacity-classified before any external reference is made. **12.1.5.5** The governing rule shall be: **Public finance relevance may be claimed only as relevance or learning; it shall never be claimed as public finance approval.** *** ### 12.1.6 Donor or Philanthropic Relevance Participation Claim **12.1.6.1** A donor or philanthropic relevance participation claim may be made only where the participant’s role is recorded in the Donor and Philanthropic Relevance Register or other competent Council record. **12.1.6.2** A permitted claim may state that a donor, philanthropy, foundation, CSR actor, humanitarian actor, development-support actor, or mission-aligned participant contributed to relevance discussion, mission-fit review, evidence-needs review, reporting-needs review, safeguard expectation review, or donor and philanthropic relevance room activity. **12.1.6.3** The claim shall not state or imply donor commitment, philanthropic commitment, foundation approval, CSR commitment, grant approval, pledge, award, allocation, sponsorship, development assistance commitment, endorsement, funding pipeline, or project approval. **12.1.6.4** Donor and philanthropic references shall be public-safe, claims-limited, and reviewed where external audiences may infer support. **12.1.6.5** The governing rule shall be: **Donor and philanthropic participation may be claimed as relevance participation, not as funding commitment.** *** ### 12.1.7 Nexus Universe Capital-Reader Room Participation Claim **12.1.7.1** A Nexus Universe Capital-Reader Room participation claim may be made only where the participant’s attendance or contribution is recorded in the Nexus Universe Preparation Register, Capital-Reader Room Record, or other competent Nexus Universe finance-readiness record. **12.1.7.2** A permitted claim may state that the participant attended, contributed to, observed, or supported a no-reliance Capital-Reader Room, Insurance-Readiness Room, Public Finance Relevance Room, Donor and Philanthropic Relevance Room, or other finance-readiness room within the Nexus Universe annual cycle. **12.1.7.3** The claim shall identify the role and room type without implying investment interest, finance approval, insurance approval, donor commitment, public finance allocation, guarantee support, project approval, SPV approval, public authority approval, certification, procurement status, consent, or execution. **12.1.7.4** Public statements about Nexus Universe room participation shall be narrower than internal records and shall use approved public-safe language. **12.1.7.5** The governing rule shall be: **Nexus Universe room participation may be visible only as disciplined participation, not as annual-stage finance, endorsement, or approval.** *** ### 12.1.8 AEP Passport Finance-Layer Contribution Claim **12.1.8.1** An AEP Passport finance-layer contribution claim may be made only where the contribution is recorded in an AEP Passport Finance-Readiness Input, AEP Passport Candidate Finance-Layer Note, AEP Passport finance-layer record, or other competent record. **12.1.8.2** A permitted claim may state that the person or institution contributed finance-readiness input, capital-readability input, insurance-readiness input, public finance relevance input, donor relevance input, diligence-gap input, Project SPV-readiness input, handoff-condition input, or correction input to an AEP Passport candidate pathway. **12.1.8.3** The claim shall not state or imply AEP Passport issuance, Passport approval, certification, Nexus-ready status, financeability, bankability, insurability, procurement status, public authority approval, project approval, consent, or execution readiness. **12.1.8.4** AEP Passport-related claims shall state candidate, draft, under-review, restricted, Docketed, corrected, superseded, archived, accepted-input, or other recorded status exactly as recorded. **12.1.8.5** The governing rule shall be: **Contribution to an AEP Passport finance layer is an input claim, not a Passport status claim.** *** ### 12.1.9 Nexus Rail Finance-Readiness Contribution Claim **12.1.9.1** A Nexus Rail finance-readiness contribution claim may be made only where the contribution is recorded in a Nexus Rail Finance-Readiness Input, Nexus Rail Candidate Finance-Readiness Note, Rail record, Docket record, or other competent record. **12.1.9.2** A permitted claim may state that the participant contributed to Rail finance-readiness, Rail routeability questions, Rail public authority dependency review, Rail insurance-readiness questions, Rail SPV-readiness questions, Rail handoff conditions, Rail claims limits, or Rail correction. **12.1.9.3** The claim shall not state or imply Rail execution, Nexus-ready status, finance approval, insurance approval, donor approval, public finance allocation, procurement status, certification, consent, handoff completion, project approval, SPV approval, Company approval, or execution authority. **12.1.9.4** Rail-related claims shall state whether the matter is proposed, candidate, deferred, restricted, blocked, Docketed, corrected, superseded, archived, renewed, or otherwise classified. **12.1.9.5** The governing rule shall be: **A Nexus Rail contribution claim identifies routing support; it shall not imply that the route has been executed.** *** ### 12.1.10 Project SPV-Readiness Discussion Contribution Claim **12.1.10.1** A Project SPV-readiness discussion contribution claim may be made only where the contribution is recorded in a Project SPV-Readiness Note, Project SPV-Readiness Register, handoff record, room record, or other competent Council record. **12.1.10.2** A permitted claim may state that the participant contributed to SPV governance questions, capitalization questions, revenue and cost questions, contracting questions, public authority dependency questions, insurance questions, procurement questions, safeguard questions, data and cyber questions, handoff requirements, or SPV-readiness correction. **12.1.10.3** The claim shall not state or imply SPV approval, SPV formation, project approval, financeability, bankability, insurability, procurement readiness, provider selection, public authority approval, donor support, public finance allocation, certification, consent, or execution authority. **12.1.10.4** SPV-readiness claims shall use “discussion,” “question,” “dependency,” “gap,” “candidate,” “awareness,” or “readiness input” language, not “approved,” “authorized,” “ready,” “financed,” “insured,” “procured,” or “launched” language. **12.1.10.5** The governing rule shall be: **A Project SPV-readiness contribution claim may describe questions raised; it shall not describe a project vehicle approved.** *** ### 12.1.11 Claims Subject to Record **12.1.11.1** Every permitted claim under this Charter shall be subject to record. **12.1.11.2** No participant, institution, sponsor, provider, capital reader, insurer, donor, public finance actor, public authority participant, National Consortium Company, Project SPV pathway actor, media actor, or external party shall make a claim about the National Investors Council, its rooms, its outputs, its records, Nexus Universe finance-readiness activity, AEP Passport finance-layer inputs, Nexus Rail finance-readiness inputs, Docket items, National Model finance layers, handoff materials, or Council-related participation unless the claim is supported by a competent record and permitted by the Claims Permission Register. **12.1.11.3** Where a claim is not clearly supported, the claim shall be withheld, narrowed, or routed for approval before use. **12.1.11.4** Where a claim exceeds the record, it shall be corrected regardless of whether the overclaim was intentional. **12.1.11.5** The governing rule shall be: **No record, no claim; narrow record, narrow claim; corrected record, corrected claim.** *** ## 12.2 Prohibited Claims ### 12.2.1 Investment Approval Claim **12.2.1.1** No person or institution shall claim or imply that the National Investors Council, a Capital-Reader Room, Nexus Universe finance-readiness activity, AEP Passport finance-layer input, Nexus Rail finance-readiness input, National Model finance layer, Docket item, or handoff record has approved an investment. **12.2.1.2** Prohibited investment approval claims include statements that a project, company, SPV, provider, technology, infrastructure, portfolio, programme, instrument, or opportunity has been “approved for investment,” “cleared for investors,” “accepted by investors,” “endorsed by the Investors Council,” “investor-approved,” “investment-ready,” or equivalent language. **12.2.1.3** Investor attendance, capital-reader presence, finance-readiness review, or capital-readability discussion shall not support an investment approval claim. **12.2.1.4** Investment approval claims shall be corrected immediately where external reliance risk exists. **12.2.1.5** The governing rule shall be: **The National Investors Council never approves investments.** *** ### 12.2.2 Financeability Claim **12.2.2.1** No person or institution shall claim or imply financeability by reason of National Investors Council participation, finance-readiness review, capital-readability review, Nexus Universe visibility, National Model inclusion, AEP Passport finance-layer input, Nexus Rail candidacy, Docket treatment, handoff discussion, or capital-reader room participation. **12.2.2.2** Prohibited financeability claims include “financeable,” “financing-ready,” “fundable,” “capital-ready,” “ready for financing,” “approved for financing,” “finance-cleared,” or equivalent language unless a separate competent external finance process supports the exact claim. **12.2.2.3** Finance-readiness shall not be translated into financeability. **12.2.2.4** Financeability overclaims shall be corrected and may require public-safe clarification where public or market audiences may rely. **12.2.2.5** The governing rule shall be: **Finance-readiness is not financeability.** *** ### 12.2.3 Bankability Claim **12.2.3.1** No person or institution shall claim or imply bankability by reason of Council activity. **12.2.3.2** Prohibited bankability claims include “bankable,” “bank-ready,” “lender-approved,” “credit-ready,” “loan-ready,” “bank-cleared,” “accepted by banks,” or equivalent language unless a separate competent bank, lender, credit, or finance process supports the exact claim. **12.2.3.3** Bank participation, lender participation, capital-reader discussion, public finance relevance mapping, guarantee-readiness questions, or SPV-readiness review shall not support a bankability claim. **12.2.3.4** Bankability overclaims shall be corrected promptly because they create high reliance and market risk. **12.2.3.5** The governing rule shall be: **A bank may read a matter without making the matter bankable.** *** ### 12.2.4 Insurability Claim **12.2.4.1** No person or institution shall claim or imply insurability by reason of Insurance-Readiness Room participation, insurance-readiness review, insurer attendance, reinsurance-readiness discussion, risk-transfer question formation, or Nexus Universe visibility. **12.2.4.2** Prohibited insurability claims include “insurable,” “insurance-ready,” “coverage-ready,” “accepted by insurers,” “risk-transfer-ready,” “underwritable,” or equivalent language unless a separate competent insurance process supports the exact claim. **12.2.4.3** Insurance-readiness questions identify what insurance actors would need to examine; they do not determine insurability. **12.2.4.4** Insurability overclaims shall be corrected where reliance, public finance, donor, market, or public authority risk may arise. **12.2.4.5** The governing rule shall be: **Insurance-readiness is not insurability.** *** ### 12.2.5 Insurance Approval Claim **12.2.5.1** No person or institution shall claim or imply insurance approval through National Investors Council activity. **12.2.5.2** Prohibited insurance approval claims include “insured,” “approved by insurers,” “coverage approved,” “insurance secured,” “insurance-backed,” “risk-transfer approved,” “accepted for coverage,” or equivalent language unless a separate lawful insurance record supports the exact claim. **12.2.5.3** Insurance-Readiness Room attendance, insurer presence, risk discussion, data review, model review, protection-gap discussion, or insurance dependency note shall not support insurance approval language. **12.2.5.4** Insurance approval overclaims shall be corrected immediately. **12.2.5.5** The governing rule shall be: **The Council may discuss insurance questions; it never approves insurance.** *** ### 12.2.6 Reinsurance Approval Claim **12.2.6.1** No person or institution shall claim or imply reinsurance approval through Council activity. **12.2.6.2** Prohibited claims include “reinsured,” “reinsurance-backed,” “accepted by reinsurers,” “reinsurance capacity secured,” “treaty-supported,” “facultative support obtained,” or equivalent language unless a separate competent reinsurance record supports the exact claim. **12.2.6.3** Reinsurer participation, reinsurance-readiness questions, catastrophe-risk discussion, exposure aggregation discussion, or disaster-risk finance discussion shall not support reinsurance approval language. **12.2.6.4** Reinsurance overclaims shall be corrected with urgency where market or public reliance risk exists. **12.2.6.5** The governing rule shall be: **Reinsurance-readiness is not reinsurance approval.** *** ### 12.2.7 Underwriting Claim **12.2.7.1** No person or institution shall claim or imply underwriting through the National Investors Council. **12.2.7.2** Prohibited underwriting claims include statements that a matter has been “underwritten,” “underwriting-approved,” “accepted by underwriters,” “priced by underwriters,” “cleared by underwriters,” or equivalent language unless a separate competent underwriting record supports the exact claim. **12.2.7.3** Underwriter attendance, insurer attendance, capital-reader attendance, risk review, insurance-readiness review, or due-diligence question formation shall not support underwriting claims. **12.2.7.4** Underwriting overclaims shall be corrected promptly because they may create false market reliance. **12.2.7.5** The governing rule shall be: **The Council does not underwrite anything.** *** ### 12.2.8 Guarantee Claim **12.2.8.1** No person or institution shall claim or imply guarantee support through Council activity. **12.2.8.2** Prohibited guarantee claims include “guaranteed,” “guarantee-backed,” “credit-enhanced,” “loss-protected,” “public guarantee secured,” “guarantee-ready,” “guarantor-approved,” or equivalent language unless a separate competent guarantee record supports the exact claim. **12.2.8.3** Guarantee-readiness questions, public finance relevance discussion, donor relevance discussion, risk-transfer discussion, or capital-reader participation shall not support guarantee claims. **12.2.8.4** Guarantee overclaims shall be corrected where public finance, donor, market, or project reliance risk exists. **12.2.8.5** The governing rule shall be: **Guarantee-readiness questions do not create guarantee support.** *** ### 12.2.9 Rating Claim **12.2.9.1** No person or institution shall claim or imply that the National Investors Council has issued a rating. **12.2.9.2** Prohibited rating claims include credit rating, project rating, maturity rating, financeability rating, bankability rating, insurability rating, provider rating, SPV rating, National Consortium Company rating, donor-readiness rating, public finance rating, Nexus-ready rating, or equivalent score or grade unless a separate competent rating or maturity process supports that exact status. **12.2.9.3** Finance-readiness notes, diligence-gap maps, risk-to-capital interpretation notes, AEP Passport finance-layer inputs, Nexus Rail notes, or Docket records shall not be described as ratings. **12.2.9.4** Rating overclaims shall be corrected before external circulation. **12.2.9.5** The governing rule shall be: **The Council may record readiness questions; it shall not rate readiness as status.** *** ### 12.2.10 Public Finance Approval Claim **12.2.10.1** No person or institution shall claim or imply public finance approval through Council activity. **12.2.10.2** Prohibited public finance approval claims include “publicly funded,” “public finance approved,” “budget-approved,” “grant-approved,” “subsidy-approved,” “public guarantee approved,” “government-funded,” “public investment approved,” “eligible for public finance,” or equivalent language unless a separate competent public finance record supports the exact claim. **12.2.10.3** Public finance relevance, public authority participation, Government Portfolio Showcase visibility, National Model inclusion, public finance room discussion, or public authority learning shall not support public finance approval claims. **12.2.10.4** Public finance approval overclaims shall be corrected urgently because they may create public trust, budget, donor, media, and market consequences. **12.2.10.5** The governing rule shall be: **Public finance relevance is not public finance approval.** *** ### 12.2.11 Donor Commitment Claim **12.2.11.1** No person or institution shall claim or imply donor commitment through Council activity. **12.2.11.2** Prohibited donor commitment claims include “donor-backed,” “donor-funded,” “grant committed,” “donor approved,” “pledged,” “funding secured,” “development assistance secured,” or equivalent language unless a separate competent donor record supports the exact claim. **12.2.11.3** Donor participation, donor relevance review, Nexus Universe donor room attendance, donor mission-fit discussion, or donor relevance note shall not support donor commitment language. **12.2.11.4** Donor commitment overclaims shall be corrected promptly to prevent false funding expectations. **12.2.11.5** The governing rule shall be: **Donor relevance is not donor commitment.** *** ### 12.2.12 Philanthropic Commitment Claim **12.2.12.1** No person or institution shall claim or imply philanthropic commitment through Council activity. **12.2.12.2** Prohibited philanthropic commitment claims include “foundation-backed,” “philanthropy-funded,” “grant awarded,” “foundation approved,” “CSR committed,” “philanthropic support secured,” “pledged,” or equivalent language unless a separate competent philanthropic record supports the exact claim. **12.2.12.3** Philanthropic relevance, foundation participation, CSR discussion, mission-fit review, or Nexus Universe philanthropic room attendance shall not support commitment language. **12.2.12.4** Philanthropic commitment overclaims shall be corrected where public, community, donor, or project expectation may arise. **12.2.12.5** The governing rule shall be: **Philanthropic relevance is not philanthropic commitment.** *** ### 12.2.13 Capital Commitment Claim **12.2.13.1** No person or institution shall claim or imply capital commitment through Council activity. **12.2.13.2** Prohibited capital commitment claims include “capital committed,” “funding committed,” “investor-backed,” “investor-supported,” “capital secured,” “financing secured,” “lender-supported,” “bank-backed,” or equivalent language unless a separate competent finance record supports the exact claim. **12.2.13.3** Capital-reader participation, questions, expressions of interest, room attendance, or Nexus Universe visibility shall not be treated as capital commitment. **12.2.13.4** Capital commitment overclaims shall be corrected immediately where market, public finance, donor, media, or project reliance risk exists. **12.2.13.5** The governing rule shall be: **Capital-reader presence is not capital commitment.** *** ### 12.2.14 Securities Offering Claim **12.2.14.1** No person or institution shall claim or imply that National Investors Council activity constitutes a securities offering. **12.2.14.2** Prohibited securities offering claims include offering securities, marketing securities, listing securities, facilitating investment subscriptions, circulating offering documents, promoting securities, matching securities issuers with investors, or presenting Council outputs as offering materials. **12.2.14.3** Council materials shall not be used as private placement memoranda, investor decks, subscription materials, securities summaries, token offering materials, fund materials, or other capital-raising documents. **12.2.14.4** Any securities-related activity shall be stopped, corrected, and routed outside the Council to competent lawful processes where appropriate. **12.2.14.5** The governing rule shall be: **The Council is not a securities platform, and no Council claim may suggest otherwise.** *** ### 12.2.15 Solicitation Claim **12.2.15.1** No person or institution shall claim or imply that the National Investors Council solicits capital, investments, loans, guarantees, insurance, reinsurance, donor support, philanthropic support, public finance, sponsorship, procurement, project participation, or transaction participation. **12.2.15.2** Prohibited solicitation includes direct solicitation, indirect solicitation, soft solicitation, implied solicitation, investor targeting, donor targeting, public finance targeting, insurer targeting, sponsor targeting, or provider-driven solicitation through Council rooms or outputs. **12.2.15.3** Council activities may identify readiness questions and relevance but shall not ask any participant to provide finance, insurance, donor support, public finance, guarantee, sponsorship, or transaction support. **12.2.15.4** Solicitation overclaims or conduct shall be corrected, restricted, or referred for appropriate handling. **12.2.15.5** The governing rule shall be: **The Council may ask what must be understood; it shall not ask for money, insurance, guarantees, or transactions.** *** ### 12.2.16 Transaction Readiness Claim **12.2.16.1** No person or institution shall claim or imply transaction readiness through Council participation, finance-readiness review, capital-reader room discussion, Nexus Universe visibility, AEP Passport finance-layer input, Nexus Rail candidacy, Docket status, National Model inclusion, SPV-readiness note, or handoff record. **12.2.16.2** Prohibited transaction readiness claims include “transaction-ready,” “deal-ready,” “closing-ready,” “term-sheet-ready,” “investment-ready,” “funding-ready,” “insurance-ready” in an approval sense, “SPV-ready” in an authorization sense, or equivalent language. **12.2.16.3** Transaction readiness requires separate lawful professional, legal, finance, insurance, public authority, procurement, corporate, safeguard, consent, and execution processes. **12.2.16.4** Transaction readiness overclaims shall be corrected before market reliance forms. **12.2.16.5** The governing rule shall be: **Council readiness is not transaction readiness.** *** ### 12.2.17 Project Approval Claim **12.2.17.1** No person or institution shall claim or imply that the National Investors Council approves projects. **12.2.17.2** Prohibited project approval claims include “project approved,” “approved by Nexus,” “approved by the Investors Council,” “ready for implementation,” “authorized for deployment,” “cleared for execution,” “approved for rollout,” or equivalent language. **12.2.17.3** Finance-readiness review, SPV-readiness discussion, National Model inclusion, Nexus Universe visibility, Rail candidacy, AEP Passport finance-layer input, capital-reader attendance, insurer attendance, donor relevance, or public finance relevance shall not support project approval language. **12.2.17.4** Project approval overclaims shall be corrected with urgency where public authority, community, capital, provider, sponsor, or execution reliance may arise. **12.2.17.5** The governing rule shall be: **The Council may identify project-readiness questions; it cannot approve projects.** *** ### 12.2.18 Project SPV Approval Claim **12.2.18.1** No person or institution shall claim or imply Project SPV approval through Council activity. **12.2.18.2** Prohibited SPV approval claims include “SPV approved,” “SPV authorized,” “SPV-ready” in an approval sense, “SPV cleared,” “project vehicle approved,” “vehicle authorized,” or equivalent language. **12.2.18.3** Project SPV-readiness notes, SPV-readiness discussion, handoff records, Nexus Rail routeability, AEP Passport finance-layer inputs, or Nexus Universe visibility shall not support SPV approval claims. **12.2.18.4** SPV approval claims shall be corrected where enterprise, finance, public authority, or project momentum risk exists. **12.2.18.5** The governing rule shall be: **SPV-readiness identifies vehicle questions; it does not approve the vehicle.** *** ### 12.2.19 AEP Passport Status Claim **12.2.19.1** No person or institution shall claim or imply AEP Passport status through National Investors Council activity unless a competent AEP Passport record supports the exact status. **12.2.19.2** Prohibited AEP Passport claims include “AEP Passport approved,” “Passport issued,” “Passport-ready,” “Passport-cleared,” “AEP validated,” “AEP certified,” or equivalent language based solely on finance-layer contribution or Council review. **12.2.19.3** AEP Passport finance-layer contribution may be claimed only as contribution or input, not as Passport status. **12.2.19.4** Passport status overclaims shall be corrected before public, capital-facing, sponsor-facing, provider-facing, public authority-facing, or media-facing use. **12.2.19.5** The governing rule shall be: **The Council may contribute to a Passport layer; it shall not create Passport status.** *** ### 12.2.20 Nexus-Ready Claim **12.2.20.1** No person or institution shall claim or imply Nexus-ready status through National Investors Council activity unless a competent Nexus process has separately and lawfully recorded that exact status. **12.2.20.2** Prohibited Nexus-ready claims include “Nexus-ready,” “Nexus-approved,” “Nexus-certified,” “Nexus-cleared,” “ready for Nexus deployment,” “ready for Nexus execution,” or equivalent language based on Council participation, finance-readiness review, Nexus Universe visibility, National Model inclusion, AEP Passport finance-layer input, Nexus Rail candidacy, Docket status, or handoff discussion. **12.2.20.3** Finance-readiness shall not be converted into Nexus-ready status. **12.2.20.4** Nexus-ready overclaims shall be corrected immediately where public reliance, provider advantage, sponsor advantage, public authority confusion, capital expectation, or execution momentum may arise. **12.2.20.5** The final prohibited-claim rule of this subsection shall be: **No National Investors Council record shall be used to claim Nexus-ready status unless competent Nexus authority has separately and lawfully recorded that status.** *** ## 12.3 Communications Controls Communications controls keep external wording narrower than internal records. They also preserve safe movement into [IX. HANDOFF](/organization/cooperation/consortiums/gateways/national-councils/investors/ix.-handoff.md) and annual visibility through [Nexus Universe](/organization/cooperation/nexus-universe.md). ### 12.3.1 Name Use **12.3.1.1** Use of the National Investors Council name shall be controlled. **12.3.1.2** The name may be used only to describe accurately recorded participation, outputs, rooms, records, public-safe reports, Nexus Universe activities, AEP Passport finance-layer inputs, Nexus Rail finance-readiness inputs, Docket items, or handoff materials within approved claims limits. **12.3.1.3** The name shall not be used in a manner implying investment approval, financeability, bankability, insurability, insurance approval, public finance approval, donor commitment, philanthropic commitment, capital commitment, guarantee support, rating, securities offering, solicitation, transaction readiness, project approval, SPV approval, AEP Passport status, Nexus-ready status, public authority approval, procurement status, consent, or execution. **12.3.1.4** Name use may be restricted, suspended, corrected, or withdrawn where overclaim, confusion, market reliance, public authority confusion, sponsor advantage, provider advantage, donor expectation, public finance expectation, or public trust risk exists. **12.3.1.5** The governing rule shall be: **The name of the National Investors Council may identify the gateway; it shall not be used to imply gateway authority beyond the record.** *** ### 12.3.2 Logo and Mark Use **12.3.2.1** Use of any National Investors Council, National Nexus Consortium, Nexus Universe, Nexus, GRF, GCRI, GRA, AEP Passport, Nexus Rail, National Model, or related logo, mark, seal, badge, designation, or visual identifier shall be controlled by competent name-use and mark-use rules. **12.3.2.2** Logo or mark use shall require approval, scope, duration, format, context, claims limits, public-safe language, and correction obligations. **12.3.2.3** No logo, mark, badge, or visual identifier shall be used to imply finance approval, investor backing, insurance approval, donor support, public finance allocation, guarantee support, certification, standards conformance, public authority approval, procurement status, SPV approval, project authorization, community consent, Indigenous consent, or execution. **12.3.2.4** Unauthorized or misleading logo and mark use shall be corrected, withdrawn, or publicly clarified where reliance risk exists. **12.3.2.5** The governing rule shall be: **A mark may evidence affiliation or participation only where permitted; it shall never become a visual substitute for approval.** *** ### 12.3.3 Public Profiles **12.3.3.1** Participants may reference National Investors Council participation in public profiles only where the claim is supported by record and permitted by the Claims Permission Register. **12.3.3.2** Permitted profile language may state the participant’s recorded role, such as participant, member, capital reader, finance-readiness contributor, insurance-readiness contributor, donor relevance contributor, public finance relevance contributor, or Nexus Universe finance-readiness participant, subject to approved wording. **12.3.3.3** Public profiles shall not imply that the participant has authority to approve investments, finance, insurance, donor support, public finance, procurement, certification, projects, SPVs, AEP Passports, Nexus-ready status, public authority action, consent, or execution. **12.3.3.4** Public profile references shall be corrected where they create market signal, public authority confusion, donor expectation, public finance expectation, insurer expectation, sponsor or provider advantage, or public reliance. **12.3.3.5** The governing rule shall be: **Public profiles may identify participation; they shall not convert participation into status, authority, or market signal.** *** ### 12.3.4 Website Listings **12.3.4.1** Website listings of National Investors Council participants, rooms, outputs, partners, sponsors, capital readers, insurers, donors, public finance readers, public authorities, National Consortium Companies, Project SPV pathways, Nexus Universe activities, AEP Passport finance-layer inputs, Nexus Rail finance-readiness inputs, or Docket items shall be controlled. **12.3.4.2** Listings shall identify role, capacity, status, limitation, and claims boundaries where needed to prevent reliance. **12.3.4.3** Website listings shall not imply investment approval, financeability, bankability, insurability, insurance approval, donor commitment, philanthropic commitment, public finance allocation, guarantee support, procurement status, certification, public authority approval, project approval, SPV approval, AEP Passport status, Nexus-ready status, consent, or execution. **12.3.4.4** Website listings shall be reviewed periodically and corrected, narrowed, removed, archived, or superseded where the record changes. **12.3.4.5** The governing rule shall be: **A website listing is a public claim and must be narrower than the record where reliance risk exists.** *** ### 12.3.5 Press and Media References **12.3.5.1** Press and media references involving the National Investors Council shall be reviewed for claims discipline and public-safe communication. **12.3.5.2** Media references may describe finance-readiness themes, public-good participation, capital-readability learning, insurance-readiness questions, donor relevance, public finance relevance, Nexus Universe activity, AEP Passport finance-layer contribution, Nexus Rail finance-readiness contribution, Docket themes, and public-safe reporting outputs only within permitted claims and without sensitive disclosure. **12.3.5.3** Press and media references shall not imply investment approval, financeability, bankability, insurability, insurance approval, underwriting, donor commitment, philanthropic commitment, capital commitment, public finance allocation, guarantee support, rating, securities offering, solicitation, transaction readiness, project approval, SPV approval, public authority approval, certification, AEP Passport status, Nexus-ready status, consent, or execution. **12.3.5.4** Media overclaim shall be corrected promptly through public-safe clarification, controlled clarification, or other appropriate corrective action. **12.3.5.5** The governing rule shall be: **Media visibility must never be allowed to outrun the record.** *** ### 12.3.6 Sponsor and Partner References **12.3.6.1** Sponsor, host, anchor, supporter, and partner references involving the National Investors Council shall be controlled to prevent sponsor capture, partner overclaim, donor confusion, provider advantage, public authority confusion, and public reliance. **12.3.6.2** A sponsor or partner may be acknowledged only where support, participation, or partnership is recorded and where the claims language states the nature of the relationship accurately. **12.3.6.3** Sponsor or partner references shall not imply control over agenda, control over outputs, control over rooms, approval authority, investment backing, donor commitment, public finance allocation, provider validation, procurement status, public authority endorsement, certification, project approval, SPV approval, consent, or execution. **12.3.6.4** Sponsor and partner references shall preserve the rule of support without control. **12.3.6.5** The governing rule shall be: **Sponsor or partner support may be visible only where it cannot be mistaken for control, endorsement, finance, or authority.** *** ### 12.3.7 Public Authority References **12.3.7.1** Public authority references shall be capacity-classified, claims-limited, and reviewed before use. **12.3.7.2** Public authority references may identify participation, observation, learning, technical contribution, public-safe review, public finance relevance reading, or official action only where the exact status is supported by a competent public authority or Council record. **12.3.7.3** Public authority references shall not imply government endorsement, public finance allocation, procurement status, regulatory approval, permit, licence, policy adoption, official position, public warning, emergency command, public authority approval, or public data authorization unless a lawful public authority record supports the exact statement. **12.3.7.4** Public authority language shall be corrected where attendance, learning, or observation is overread as approval. **12.3.7.5** The governing rule shall be: **Public authority presence must be described by capacity, not by implication.** *** ### 12.3.8 Investor and Capital-Reader References **12.3.8.1** Investor and capital-reader references shall be controlled because such references may create market signal, finance expectation, or transaction inference. **12.3.8.2** Investor and capital-reader references may identify participation, attendance, capital-reader status, capital-readability discussion, or finance-readiness contribution only where authorized and supported by record. **12.3.8.3** Such references shall not imply investment interest, capital commitment, lending interest, mandate, endorsement, approval, financeability, bankability, transaction readiness, or funding availability. **12.3.8.4** Named investor or capital-reader references shall be subject to confidentiality, permission, and public-safe review. **12.3.8.5** The governing rule shall be: **Capital-reader references must prevent the public from reading attention as capital.** *** ### 12.3.9 Insurer and Reinsurer References **12.3.9.1** Insurer and reinsurer references shall be controlled because such references may imply underwriting, coverage, risk-transfer capacity, or insurance approval. **12.3.9.2** Insurer and reinsurer references may identify participation in insurance-readiness, reinsurance-readiness, risk-transfer question formation, exposure review, protection-gap learning, or disaster-risk finance discussion only where authorized and supported by record. **12.3.9.3** Such references shall not imply insurance approval, reinsurance approval, underwriting, coverage availability, premium indication, guarantee support, risk-transfer approval, insurability, insurance advice, or placement. **12.3.9.4** Insurance-related public references shall be reviewed for competition, confidentiality, market, and public reliance risk. **12.3.9.5** The governing rule shall be: **An insurer may help ask risk questions without being represented as having answered coverage questions.** *** ### 12.3.10 Donor and Philanthropic References **12.3.10.1** Donor and philanthropic references shall be controlled because such references may create funding expectation, public legitimacy inference, or project momentum. **12.3.10.2** Donor and philanthropic references may identify participation in donor relevance, philanthropic relevance, mission-fit, grant-readiness questions, development-readiness discussion, safeguard expectation review, or Nexus Universe relevance rooms only where authorized and supported by record. **12.3.10.3** Such references shall not imply donor commitment, philanthropic commitment, grant approval, foundation endorsement, CSR commitment, pledge, award, allocation, sponsorship, development assistance commitment, funding pipeline, or project approval. **12.3.10.4** Donor and philanthropic references shall be public-safe and claims-limited where released externally. **12.3.10.5** The governing rule shall be: **Donor and philanthropic visibility may show relevance participation; it shall not create expectation of support.** *** ### 12.3.11 Project SPV and National Consortium Company References **12.3.11.1** Project SPV and National Consortium Company references shall be controlled to preserve public-good and enterprise-stack separation. **12.3.11.2** References may identify SPV-readiness questions, Company finance-interface questions, handoff candidate status, enterprise handoff awareness, or lawful receiving-pathway considerations only where supported by competent record and permitted by claims rules. **12.3.11.3** Such references shall not imply SPV formation, SPV approval, Company approval, Company mandate, Company obligation, project approval, finance approval, insurance approval, donor approval, public finance allocation, procurement status, provider selection, public authority approval, consent, certification, or execution. **12.3.11.4** Company-linked and SPV-linked materials shall carry handoff limits, no-reliance terms, claims limits, conflict disclosure where required, safeguard dependencies, and correction pathways. **12.3.11.5** The governing rule shall be: **Enterprise references may describe possible lawful interface; they shall not announce enterprise action by implication.** *** ### 12.3.12 Correction Notices **12.3.12.1** The National Investors Council may issue correction notices where claims, communications, public-safe reports, media references, website listings, profiles, sponsor references, provider references, investor references, insurer references, donor references, public finance references, public authority references, Company references, SPV references, AEP Passport references, Nexus Rail references, Docket references, National Model references, or handoff references exceed the record. **12.3.12.2** A correction notice shall identify the incorrect statement or implication, the correct record status, the permitted claim, any withdrawn claim, any revised language, any affected public-safe material, any affected controlled material, and any further correction required. **12.3.12.3** Correction notices may be public, public-safe, controlled, restricted, participant-specific, recipient-specific, media-facing, donor-facing, public finance-facing, insurer-facing, capital-reader-facing, public authority-facing, sponsor-facing, provider-facing, Company-facing, or SPV-facing depending on the reliance risk. **12.3.12.4** Correction notices shall be issued promptly where an overclaim may affect market reliance, public finance expectation, donor expectation, insurance expectation, public authority understanding, sponsor advantage, provider advantage, community trust, media narrative, or lawful handoff. **12.3.12.5** The governing rule shall be: **A correction notice is required when the public meaning of a claim has exceeded the recorded truth.** *** ## 12.4 Public-Safe Reporting Public-safe reporting applies these claims limits to external communication. Publication class, confidentiality, and sensitivity controls continue in [XIII. SAFEGUARDS](/organization/cooperation/consortiums/gateways/national-councils/investors/xiii.-safeguards.md), including material that may travel through [Nexus Rails](/organization/organization/architecture/ii.-definitions/xv.-nexus-rails.md). ### 12.4.1 Public-Safe Reporting Role **12.4.1.1** The National Investors Council may contribute finance-readiness inputs to public-safe reporting where authorized by the National Council, National Nexus Consortium authority, GRF-aligned public-safe reporting pathway, Nexus Universe cycle, National Model process, AEP Passport pathway, Nexus Rail pathway, Docket pathway, or other competent record. **12.4.1.2** The Council’s public-safe reporting role shall be to identify finance-readiness themes, capital-readability questions, insurance-readiness questions, public finance relevance, donor relevance, philanthropic relevance, development-readiness, diligence gaps, Project SPV-readiness questions, National Consortium Company interface questions, safeguard dependencies, public authority dependencies, Nexus Rail routeability learning, AEP Passport finance-layer learning, Docket themes, and correction themes in language safe for public understanding. **12.4.1.3** Public-safe reporting shall not serve as investor marketing, securities material, donor solicitation, public finance request, insurance submission, project announcement, procurement communication, certification statement, public authority decision, consent record, SPV authorization, Company action, or execution notice. **12.4.1.4** The Council shall ensure that public-safe reporting preserves no-reliance status, claims limits, confidentiality, safeguards, public authority capacity classification, and correctionability. **12.4.1.5** The governing rule shall be: **Public-safe reporting may communicate readiness learning; it shall not create readiness reliance.** *** ### 12.4.2 Publication Class Review **12.4.2.1** Every finance-readiness public-safe reporting input shall undergo publication class review before release. **12.4.2.2** Publication class review shall determine whether material is public, public-safe, controlled, restricted, confidential, finance-sensitive, insurance-sensitive, donor-sensitive, public finance-sensitive, public authority-sensitive, safeguard-sensitive, provider-sensitive, sponsor-sensitive, community-sensitive, Indigenous or protected-knowledge-sensitive where applicable, cyber-sensitive, infrastructure-sensitive, health-sensitive, biodiversity-sensitive, not-for-publication, archived, or superseded. **12.4.2.3** Publication class review shall identify redactions, aggregation requirements, anonymization requirements, public-safe summaries, no-release restrictions, AI-processing restrictions, external-sharing limits, and correction pathways. **12.4.2.4** No material shall be released publicly merely because it is useful, impressive, finance-readable, sponsor-supported, provider-developed, media-friendly, or Nexus Universe-relevant. **12.4.2.5** The governing rule shall be: **A finance-readiness record may become public only when its publication class allows it.** *** ### 12.4.3 Sensitive Information Handling **12.4.3.1** Public-safe reporting shall protect sensitive information. **12.4.3.2** Sensitive information may include personal information, public authority-sensitive information, finance-sensitive information, insurance-sensitive information, donor-sensitive information, public finance-sensitive information, commercially sensitive information, provider-sensitive information, sponsor-sensitive information, community-sensitive information, Indigenous or protected knowledge where applicable, cybersecurity-sensitive information, infrastructure-sensitive information, health-sensitive information, biodiversity-sensitive information, location-sensitive information, legal-sensitive information, procurement-sensitive information, and not-for-publication material. **12.4.3.3** Sensitive information shall not be disclosed in public-safe reporting unless release is authorized, necessary, proportionate, appropriately redacted or aggregated, and consistent with applicable law, safeguards, confidentiality obligations, public authority boundaries, and community or Indigenous protocol conditions where applicable. **12.4.3.4** Public-safe reporting shall not use sensitivity as a pretext to conceal overclaim, conflicts, correction needs, or public-interest risks. Where sensitive information cannot be disclosed, a safe status label or controlled explanation may be used. **12.4.3.5** The governing rule shall be: **Public-safe reporting protects sensitive information while still preserving truthful status and correctionability.** *** ### 12.4.4 Finance-Readiness Language Review **12.4.4.1** Public-safe reporting shall include finance-readiness language review. **12.4.4.2** Finance-readiness language review shall ensure that terms such as finance-readiness, capital-readability, investment interest, funding, financeability, bankability, capital, readiness, handoff, SPV-readiness, and National Consortium Company interface are used precisely and without reliance implication. **12.4.4.3** Public-safe reporting may use language such as “finance-readiness questions,” “capital-readability review,” “diligence gaps,” “public finance relevance,” “donor relevance,” “insurance-readiness questions,” “SPV-readiness dependencies,” “handoff conditions,” or “routeability input” where supported by record. **12.4.4.4** Public-safe reporting shall avoid language such as “funded,” “financeable,” “bankable,” “investment-ready,” “capital secured,” “investor-backed,” “deal-ready,” “transaction-ready,” or equivalent unless separately and lawfully supported by competent external record. **12.4.4.5** The governing rule shall be: **Finance-readiness language must describe inquiry and record status, not finance outcome.** *** ### 12.4.5 Public Authority Language Review **12.4.5.1** Public-safe reporting shall include public authority language review. **12.4.5.2** Public authority language review shall determine whether public authority references are official, observer, learner, technical, public-safe reviewer, public finance reader, regulator observer, personal-capacity, no official position, not yet engaged, or otherwise classified. **12.4.5.3** Public-safe reporting shall not imply public authority approval, government endorsement, policy adoption, public finance allocation, procurement status, regulatory approval, permit, licence, public data authorization, public warning, emergency command, or official position unless a lawful public authority record supports the exact claim. **12.4.5.4** Where public authority involvement is relevant but not official, reporting shall use accurate capacity language and shall not invite inference of approval. **12.4.5.5** The governing rule shall be: **Public authority language must describe capacity exactly because public authority inference creates reliance quickly.** *** ### 12.4.6 Insurance-Readiness Language Review **12.4.6.1** Public-safe reporting shall include insurance-readiness language review. **12.4.6.2** Insurance-readiness language review shall ensure that insurance, reinsurance, risk-transfer, disaster-risk finance, guarantee, protection-gap, exposure, underwriting, coverage, premium, insurability, and insurer participation references are accurate and claims-limited. **12.4.6.3** Public-safe reporting may refer to “insurance-readiness questions,” “risk-transfer questions,” “protection-gap learning,” “exposure questions,” “data and model dependencies,” or “disaster-risk finance questions” where supported by record. **12.4.6.4** Public-safe reporting shall not imply insurance approval, reinsurance approval, underwriting, coverage availability, premium indication, insurability, risk-transfer approval, guarantee support, insurance advice, or insurance placement. **12.4.6.5** The governing rule shall be: **Insurance-readiness reporting may describe risk questions; it shall not describe insurance outcomes.** *** ### 12.4.7 Donor and Philanthropic Language Review **12.4.7.1** Public-safe reporting shall include donor and philanthropic language review. **12.4.7.2** Donor and philanthropic language review shall ensure that donor relevance, philanthropic relevance, foundation relevance, CSR relevance, grant-readiness, development-support, humanitarian support, mission fit, and public-good support references do not imply commitment. **12.4.7.3** Public-safe reporting may refer to “donor relevance,” “philanthropic relevance,” “mission-fit questions,” “grant-readiness questions,” “development-readiness questions,” “safeguard expectations,” and “reporting needs” where supported by record. **12.4.7.4** Public-safe reporting shall not imply donor commitment, philanthropic commitment, foundation approval, CSR commitment, pledge, award, allocation, sponsorship, development assistance commitment, funding pipeline, endorsement, or project approval. **12.4.7.5** The governing rule shall be: **Donor and philanthropic reporting may describe possible relevance; it shall not create funding expectation.** *** ### 12.4.8 Sponsor and Provider Language Review **12.4.8.1** Public-safe reporting shall include sponsor and provider language review. **12.4.8.2** Sponsor language review shall ensure that sponsor, host, anchor, partner, supporter, donor, or contributor references do not imply control over agenda, outputs, rooms, records, public-safe reports, Nexus Universe visibility, National Model inclusion, AEP Passport inputs, Nexus Rail routing, handoff, public authority relationships, finance, insurance, donor outcomes, public finance outcomes, certification, project approval, or execution. **12.4.8.3** Provider language review shall ensure that provider, vendor, operator, contractor, technology, infrastructure, system, demonstration, pilot, or contribution references do not imply provider validation, preferred-provider status, procurement eligibility, standards conformance, certification, technical approval, finance approval, insurance approval, public authority approval, AEP Passport status, Nexus-ready status, project authorization, or execution. **12.4.8.4** Sponsor and provider references shall preserve sponsor support without control and provider contribution without validation. **12.4.8.5** The governing rule shall be: **Public-safe reporting may acknowledge support and contribution only where it cannot be read as control, validation, procurement, approval, or execution.** *** ### 12.4.9 No Public Finance Signal by Reporting **12.4.9.1** Public-safe reporting shall not create a public finance signal. **12.4.9.2** A public finance signal includes any statement, implication, headline, listing, graphic, room title, public authority reference, public finance reader reference, National Model layer, Nexus Universe summary, AEP Passport finance-layer summary, Nexus Rail note, or handoff reference that could reasonably suggest public finance allocation, budget approval, public grant, subsidy, public guarantee, concessional finance approval, public procurement, government endorsement, or public authority funding support. **12.4.9.3** Public-safe reporting may identify public finance relevance, budget dependency, public guarantee questions, public investment questions, and public authority dependencies only with no-allocation language and capacity classification. **12.4.9.4** Any public finance signal shall be corrected before or immediately after release. **12.4.9.5** The governing rule shall be: **Public-safe reporting may identify public finance relevance; it shall not signal public finance.** *** ### 12.4.10 No Capital Signal by Reporting **12.4.10.1** Public-safe reporting shall not create a capital signal. **12.4.10.2** A capital signal includes any statement, implication, headline, listing, graphic, participant reference, room reference, capital-reader reference, investor reference, bank reference, donor reference, insurer reference, National Model reference, Nexus Universe summary, AEP Passport finance-layer summary, Nexus Rail note, or handoff reference that could reasonably suggest investment interest, capital commitment, financeability, bankability, funding availability, lender support, guarantee support, transaction readiness, or financing momentum. **12.4.10.3** Public-safe reporting may identify capital-readability, finance-readiness questions, diligence gaps, and capital-reader participation only with no-reliance and non-commitment language. **12.4.10.4** Any capital signal shall be corrected before it becomes market reliance. **12.4.10.5** The governing rule shall be: **Public-safe reporting may explain capital-readability; it shall not signal capital availability.** *** ### 12.4.11 No Public Warning by Reporting **12.4.11.1** Public-safe reporting shall not create a public warning unless a competent public authority or expressly authorized public-safe warning pathway has separately and lawfully issued such warning. **12.4.11.2** Finance-readiness reporting, insurance-readiness reporting, disaster-risk finance reporting, exposure discussion, protection-gap discussion, public authority dependency reporting, climate or disaster risk reporting, infrastructure risk reporting, cyber risk reporting, health risk reporting, biodiversity risk reporting, or community safeguard reporting shall not be framed as public warning, emergency notice, emergency command, public authority instruction, public safety order, or official alert. **12.4.11.3** Public-safe reporting may describe risk-learning, readiness questions, protection gaps, and resilience needs in language that does not trigger public warning reliance or public authority confusion. **12.4.11.4** Any public-warning overclaim shall be corrected urgently. **12.4.11.5** The governing rule shall be: **Public-safe reporting may explain risk-readiness learning; it shall not warn the public as an authority.** *** ### 12.4.12 Public-Safe Correction **12.4.12.1** Public-safe reporting shall remain correctionable. **12.4.12.2** Public-safe correction may be required where a report misstates finance-readiness, capital-readability, insurance-readiness, public finance relevance, donor relevance, philanthropic relevance, development-readiness, SPV-readiness, Company interface, AEP Passport finance-layer status, Nexus Rail status, Docket status, National Model status, public authority status, safeguard status, sponsor role, provider role, public warning status, public finance signal, capital signal, insurance signal, donor signal, or handoff condition. **12.4.12.3** Correction may include public clarification, controlled clarification, revised public-safe report, withdrawal, supersession, archive, updated status label, participant notice, media notice, public authority notice, donor notice, public finance notice, insurer notice, capital-reader notice, sponsor notice, provider notice, Company notice, SPV notice, or Docket entry. **12.4.12.4** Public-safe correction shall preserve trust by correcting the record visibly enough to neutralize the overclaim while protecting sensitive information. **12.4.12.5** The final operating rule of this Part shall be: **Public-safe reporting is safe only while it remains narrow, truthful, classified, claims-limited, and correctionable.** ### Next steps 1. Continue to [XIII. SAFEGUARDS](/organization/cooperation/consortiums/gateways/national-councils/investors/xiii.-safeguards.md) for safeguard conditions, confidentiality, publication class, and market conduct. 2. Revisit [XI. RECORDS](/organization/cooperation/consortiums/gateways/national-councils/investors/xi.-records.md) if you need the controlling registers behind these claim limits. 3. Review [IX. HANDOFF](/organization/cooperation/consortiums/gateways/national-councils/investors/ix.-handoff.md) for how claims travel when material moves into a receiving pathway. --- # 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/xii.-claims.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.