# XIV. BOUNDARIES

This section defines what participation and contribution do not create.

It prevents public-good work from being misread as authority, approval, finance status, provider status, consent, or execution.

These boundaries reduce unsafe reliance, false meaning, and premature operational claims.

## **14.1 Participation Boundaries**

### **14.1.1 Participation Is Not Authority**

**14.1.1.1** Participation in the National Leadership Council shall not, by itself, create authority. A participant may contribute to discussion, evidence review, agenda formation, leadership-pool development, cross-helix coordination, Nexus Universe mobilization, National Model support, public-safe reporting input, safeguard review, Docket identification, AEP Passport candidate preparation, Nexus Rail candidate preparation, or handoff awareness only within the participant’s recorded role.

**14.1.1.2** Participation shall not create power to bind the National Leadership Council, National Council, National Nexus Consortium, Regional Nexus Consortium, Global Nexus Consortium, Nexus Universe, The Global Centre for Risk and Innovation (GCRI), The Global Risks Forum (GRF), The Global Risks Alliance (GRA), any National Consortium Company, any Project SPV, any public authority, any sponsor, any provider, any investor, any insurer, any donor, any community, any Indigenous group, or any other actor.

**14.1.1.3** Participation shall not imply appointment, delegation, representation, agency, fiduciary status, voting right, public authority role, financial role, certification role, procurement role, consent role, operational role, or execution authority unless a separate competent record expressly creates that status.

**14.1.1.4** A person may be present, active, senior, visible, invited, subscribed, named, photographed, quoted, acknowledged, or listed and still possess no authority beyond the recorded participation role.

**14.1.1.5** The governing rule shall be:

**Participation opens a contribution pathway; it does not create power.**

***

### **14.1.2 Leadership-Pool Status Is Not Appointment**

**14.1.2.1** Leadership-pool status shall not be treated as appointment, election, nomination, confirmation, designation, office, board status, stewardship status, chair status, lead status, delegation status, public authority status, or authority to act.

**14.1.2.2** Leadership-pool status means only that a person has been identified, classified, or recorded for possible future consideration in a defined role pathway, subject to contribution review, conflict review, claims discipline, confidentiality reliability, safeguard competence, formal selection, and correction.

**14.1.2.3** A participant recorded in a leadership pool shall not claim to be an incoming board member, board-designate, appointed steward, official leader, selected representative, confirmed nominee, National Desk lead, Nexus Universe delegation lead, working-group lead, committee chair, or institutional representative unless a separate competent record supports that precise status.

**14.1.2.4** Leadership-pool status may be withdrawn, restricted, corrected, superseded, or archived where eligibility, conduct, contribution, conflict, confidentiality, safeguard, claims, or role facts change.

**14.1.2.5** The governing rule shall be:

**Leadership-pool status is readiness for review, not appointment to authority.**

***

### **14.1.3 Recommendation Is Not Adoption**

**14.1.3.1** A recommendation by the National Leadership Council shall not be treated as adoption by the National Council, National Nexus Consortium, Stewardship Board, Regional Nexus Consortium, Global Nexus Consortium, GRF, GCRI, GRA, public authority, National Consortium Company, Project SPV, investor, insurer, donor, sponsor, provider, community, Indigenous actor, or any other competent body.

**14.1.3.2** Recommendations may support agenda prioritization, leadership-pool review, National Working Group formation, Nexus Universe preparation, National Model update, public-safe reporting, Docket entry, AEP Passport candidate preparation, Nexus Rail routing, handoff awareness, correction, or renewal, but adoption requires a separate record by the competent receiving body.

**14.1.3.3** A recommendation shall carry its source, basis, limitations, conflicts, public authority status, finance-readiness boundaries, safeguard conditions, claims limits, and correction pathway.

**14.1.3.4** No participant shall publicly describe a recommendation as approved, adopted, accepted, authorized, certified, financed, procured, consented, endorsed, or execution-ready unless a competent adoption record exists.

**14.1.3.5** The governing rule shall be:

**A recommendation invites competent action; it is not the competent action itself.**

***

### **14.1.4 Agenda Input Is Not Policy**

**14.1.4.1** Agenda input by the National Leadership Council, National Council, Helix Councils, National Investors Council, National Working Groups, Nexus Universe participants, public authority learners, capital readers, sponsors, providers, communities, Indigenous participants where applicable, or regional/global actors shall not be treated as policy unless a competent policy-making authority separately adopts the matter through lawful process.

**14.1.4.2** Agenda input may identify national priority themes, public authority learning needs, finance-readiness gaps, safeguard issues, technical evidence needs, community concerns, Nexus Universe priorities, National Model topics, AEP Passport candidates, Nexus Rail candidates, Docket items, or handoff questions.

**14.1.4.3** Agenda input shall not imply public policy adoption, government decision, regulation, procurement priority, public finance allocation, official national position, public warning, emergency-management decision, or public authority mandate.

**14.1.4.4** Where public authority-related agenda input is discussed, capacity classification and no-approval language shall be applied unless a lawful public authority record states otherwise.

**14.1.4.5** The governing rule shall be:

**Agenda input identifies what should be considered; it does not become public policy by being considered.**

***

### **14.1.5 Handoff Input Is Not Execution**

**14.1.5.1** Handoff input by the National Leadership Council shall not constitute execution, project approval, enterprise authorization, procurement action, financial action, insurance action, public authority decision, certification, consent, or operational command.

**14.1.5.2** Handoff input may identify that a matter could require further consideration by a National Consortium Company, Project SPV, public authority, provider-neutral capability process, finance-readiness process, safeguard process, GCRI pathway, GRF pathway, GRA pathway, Regional Nexus Consortium, Global Nexus Consortium, Nexus Observatory, Nexus Rail, AEP Passport pathway, Docket pathway, or other competent actor.

**14.1.5.3** Handoff input shall carry all unresolved conditions, including evidence gaps, technical limitations, public authority dependencies, finance-readiness dependencies, insurance-readiness questions, safeguard dependencies, data restrictions, provider-neutrality requirements, sponsor or provider conflicts, claims limits, and correction requirements.

**14.1.5.4** No handoff input shall be used to imply that the receiving actor has accepted, approved, financed, insured, procured, certified, consented, or authorized the matter unless a separate competent receiving record exists.

**14.1.5.5** The governing rule shall be:

**Handoff input begins routeability; it does not execute the route.**

***

## **14.2 Public Authority Boundaries**

This section defines limits that prevent government presence or policy discussion from being misread as official action.

### **14.2.1 No Public Authority Delegation**

**14.2.1.1** The National Leadership Council shall not receive, assume, imply, or exercise public authority delegation unless a competent public authority lawfully grants a specific delegation through a separate written instrument, and such delegation is compatible with applicable law and the Council’s public-good character.

**14.2.1.2** Public authority delegation shall not arise from public authority attendance, public authority learning, public authority questions, public authority data sharing, public authority participation in Nexus Universe, Government Portfolio Showcase participation, National Model review, public-safe reporting review, or public authority-facing meetings.

**14.2.1.3** The Council shall not act as a delegated regulator, procurement authority, public finance body, emergency authority, public warning authority, licensing body, permitting body, standards authority, public utility authority, public health authority, environmental authority, infrastructure authority, or government agency by implication.

**14.2.1.4** Any communication suggesting public authority delegation shall be corrected immediately unless supported by a lawful delegation record.

**14.2.1.5** The governing rule shall be:

**Public authority delegation exists only where public law and public record create it.**

***

### **14.2.2 No Government Endorsement**

**14.2.2.1** National Leadership Council participation, National Council participation, Nexus Universe participation, National Model inclusion, public authority learning, Government Portfolio Showcase activity, public authority room attendance, public authority questions, or public authority-facing communication shall not imply government endorsement.

**14.2.2.2** Government endorsement may be claimed only where a competent public authority record expressly provides endorsement and permits the claim.

**14.2.2.3** References to government or public authorities shall distinguish between official endorsement, official participation, observer status, learning status, technical contribution, data-stewardship role, public-safe review, public finance reading, personal-capacity participation, and no official position.

**14.2.2.4** Where government status is unclear, communications shall apply the default rule of no endorsement, no approval, no adoption, no funding, no procurement, no public finance commitment, no public warning, no emergency command, no delegation, and no official position.

**14.2.2.5** The governing rule shall be:

**Government presence is not government endorsement.**

***

### **14.2.3 No Regulatory Approval**

**14.2.3.1** Nothing in the National Leadership Council’s work shall constitute regulatory approval.

**14.2.3.2** Regulatory approval shall not arise from public authority learning sessions, regulator observation, technical review, National Model inclusion, Nexus Universe presentation, Nexus Core demonstration, AEP Passport candidacy, Nexus Rail candidacy, Docket entry, public-safe reporting, Government Portfolio Showcase activity, or handoff note.

**14.2.3.3** The Council shall not state or imply that any technology, provider, project, method, dataset, AI system, dashboard, digital twin, infrastructure pathway, finance-readiness pathway, National Consortium Company, Project SPV, or public authority learning item is regulator-approved unless a competent regulator has issued lawful approval.

**14.2.3.4** Any regulatory approval overclaim shall be corrected, restricted, withdrawn, or publicly clarified where necessary.

**14.2.3.5** The governing rule shall be:

**Regulatory approval belongs to regulators acting through lawful process.**

***

### **14.2.4 No Policy Adoption**

**14.2.4.1** The National Leadership Council shall not adopt public policy for any government, public authority, regulator, municipality, public agency, public utility, public finance body, emergency-management body, or public institution.

**14.2.4.2** Policy learning, policy discussion, policy input, agenda prioritization, National Model materials, public authority learning notes, Nexus Universe materials, or public-safe reporting shall not be described as policy adoption unless a competent public authority separately adopts policy through lawful process.

**14.2.4.3** The Council may identify policy questions, policy gaps, public authority learning needs, standards-interface questions, regulatory dependencies, public finance dependencies, and public-safe communication risks.

**14.2.4.4** The Council shall not imply that such identification creates public policy, government program, official strategy, national plan, regulatory reform, procurement priority, public finance commitment, or public authority instruction.

**14.2.4.5** The governing rule shall be:

**The Council may help clarify policy questions; it cannot adopt policy for public authorities.**

***

### **14.2.5 No Public Finance Allocation**

**14.2.5.1** The National Leadership Council shall not allocate public finance, approve public funding, recommend public funding as a public authority, authorize grants, approve subsidies, direct budget commitments, approve guarantees, approve concessional finance, or create public finance entitlement.

**14.2.5.2** Public finance relevance, public finance reading, donor relevance, philanthropic relevance, capital-readability, disaster-risk-finance relevance, or Government Portfolio Showcase activity shall not imply public finance allocation.

**14.2.5.3** The Council may identify public finance dependencies or questions for lawful public authority or finance-readiness processes.

**14.2.5.4** Communications shall not state or imply that public funds are approved, committed, allocated, reserved, recommended by government, or expected unless a lawful public finance record supports the claim.

**14.2.5.5** The governing rule shall be:

**Public finance can be mapped as a dependency; it cannot be allocated by the Council.**

***

### **14.2.6 No Procurement Status**

**14.2.6.1** The National Leadership Council shall not create procurement status, procurement eligibility, prequalification, preferred-provider status, tender status, contract award, vendor approval, government purchasing status, or buyer endorsement.

**14.2.6.2** Procurement status shall not arise from provider participation, sponsor participation, technical contribution, National Working Group participation, Nexus Core demonstration, Nexus Universe visibility, National Model inclusion, AEP Passport candidacy, Nexus Rail candidacy, public authority attendance, Government Portfolio Showcase activity, finance-readiness discussion, or handoff candidate identification.

**14.2.6.3** The Council may identify provider-neutral capability needs, technical requirements, interoperability gaps, evidence needs, and procurement-neutral considerations.

**14.2.6.4** Any procurement claim or implication shall be corrected because it may create unfair advantage, public trust risk, market distortion, and legal exposure.

**14.2.6.5** The governing rule shall be:

**Nexus readiness work is procurement-neutral unless a separate lawful procurement process says otherwise.**

***

### **14.2.7 No Public Warning**

**14.2.7.1** The National Leadership Council shall not issue public warnings, emergency alerts, evacuation orders, public health orders, disaster declarations, official forecasts, infrastructure alerts, safety directives, emergency-management instructions, or operational commands.

**14.2.7.2** Public-safe reporting, Nexus Observatory inputs, dashboards, National Model materials, risk notes, Docket items, Nexus Universe materials, working-group outputs, AEP Passport candidate notes, Rail candidate notes, or handoff notes shall not be described as public warnings unless issued by a competent public authority or lawful warning body through the proper process.

**14.2.7.3** Where Council work identifies information potentially relevant to public warning, the matter shall be routed to competent public authority or lawful emergency-management channels.

**14.2.7.4** Public communications shall include no-public-warning language where needed to prevent reliance.

**14.2.7.5** The governing rule shall be:

**The Council may identify risk information; it does not warn the public as a public authority.**

***

### **14.2.8 No Emergency Command**

**14.2.8.1** The National Leadership Council shall not command emergency response, direct operations, activate public systems, deploy assets, allocate emergency resources, issue incident instructions, direct responders, trigger emergency protocols, or manage crisis operations.

**14.2.8.2** Nexus Observatory information, Nexus Universe simulations, risk dashboards, public authority learning rooms, public-safe reports, National Model materials, technical demonstrations, or working-group outputs shall not create emergency command authority.

**14.2.8.3** Emergency command belongs to competent public authorities, emergency-management bodies, operators, utilities, first responders, or lawful command structures acting through their own authority.

**14.2.8.4** Any communication implying emergency command by the Council shall be corrected immediately.

**14.2.8.5** The governing rule shall be:

**Nexus may support learning and readiness; emergency command remains with lawful command authorities.**

***

### **14.2.9 No Data Authorization by Presence**

**14.2.9.1** Public authority presence, community presence, Indigenous presence where applicable, provider presence, sponsor presence, capital-reader presence, university presence, or participant presence shall not authorize data access, data use, data sharing, publication, mapping, AI processing, dashboarding, commercialization, handoff, or operationalization.

**14.2.9.2** Data authorization requires a separate lawful, contractual, ethical, consent-based, rights-respecting, or governance record appropriate to the data type and context.

**14.2.9.3** The Council shall not infer data permission from meeting attendance, verbal discussion, public presentation, Nexus Universe participation, Government Portfolio Showcase participation, National Model inclusion, working-group contribution, public authority learning, community consultation, or sponsor support.

**14.2.9.4** Where data authorization is unclear, the default shall be no authorization, restricted handling, and further review.

**14.2.9.5** The governing rule shall be:

**Presence in a room is not permission to use data from the room.**

***

### **14.2.10 Correction of Public Authority Overclaim**

**14.2.10.1** Public authority overclaim shall be corrected whenever a communication, record, presentation, website listing, media reference, sponsor material, provider material, investor-facing material, public-safe report, National Model summary, Nexus Universe material, Government Portfolio Showcase material, AEP Passport candidate note, Nexus Rail candidate note, Docket item, or handoff note implies public authority approval, endorsement, adoption, delegation, procurement, funding, regulatory comfort, public finance allocation, public warning, emergency command, permit, licence, policy decision, or official position not supported by lawful public authority record.

**14.2.10.2** Correction may include revised language, withdrawal, participant notice, public-safe clarification, public correction, public authority-facing clarification, media correction, website correction, sponsor correction, provider correction, investor-facing correction, Docket entry, restriction, or suspension of claims permission.

**14.2.10.3** Public authority overclaim shall be treated as a high-priority correction because external audiences may rely on perceived official status.

**14.2.10.4** Repeated or intentional public authority overclaim may result in participation restriction, leadership-pool removal, Nexus Universe participation restriction, handoff suspension, or referral to competent governance or legal process.

**14.2.10.5** The governing rule shall be:

**False public authority meaning must be corrected before it becomes public reliance.**

***

## **14.3 Finance Boundaries**

This section defines limits that prevent finance-readiness work from becoming advice, solicitation, approval, or market signal.

### **14.3.1 No Investment Advice**

**14.3.1.1** The National Leadership Council shall not provide investment advice.

**14.3.1.2** Nothing in Council participation, National Investors Council interface, finance-readiness note, capital-reader room, Nexus Universe session, National Model finance-readiness layer, AEP Passport candidate note, Nexus Rail candidate note, Docket item, handoff note, National Consortium Company interface note, or Project SPV-readiness awareness note shall be interpreted as a recommendation to buy, sell, hold, invest, lend, finance, insure, underwrite, guarantee, sponsor, donate, fund, or participate in any transaction.

**14.3.1.3** The Council may identify readiness questions, evidence gaps, diligence gaps, public authority dependencies, safeguard dependencies, and capital-readable information needs, but such identification shall remain non-advisory and no-reliance.

**14.3.1.4** Any material that could be read as investment advice shall be corrected, restricted, or labelled appropriately before external use.

**14.3.1.5** The governing rule shall be:

**Finance-readiness analysis is not investment advice.**

***

### **14.3.2 No Financial Advice**

**14.3.2.1** The National Leadership Council shall not provide financial advice, financial planning, structuring advice, capital-raising advice, project-finance advice, debt advice, equity advice, tax advice, accounting advice, valuation advice, guarantee advice, public finance advice, donor strategy advice, philanthropic strategy advice, or transaction advice.

**14.3.2.2** Council outputs may identify that such advice may later be required from competent professionals or lawful actors, but the Council shall not provide that advice by implication.

**14.3.2.3** Finance-readiness discussions shall remain non-advisory, no-reliance, non-soliciting, non-transactional, confidentiality-aware, competition-compliant, and regulated-perimeter controlled.

**14.3.2.4** Participants shall not use Council status to market financial advisory services or imply financial advisory endorsement.

**14.3.2.5** The governing rule shall be:

**The Council may identify financial questions; it does not answer them as financial adviser.**

***

### **14.3.3 No Insurance Advice**

**14.3.3.1** The National Leadership Council shall not provide insurance advice, underwriting advice, reinsurance advice, coverage advice, claims advice, premium advice, risk-transfer advice, guarantee advice, brokerage advice, or insurance placement.

**14.3.3.2** Insurance-readiness discussion may identify information that insurers or reinsurers may need to understand risk, but such discussion shall not imply insurance availability, insurability, underwriting approval, coverage approval, premium indication, guarantee, or placement.

**14.3.3.3** Insurance-related participation by insurers, reinsurers, brokers, risk advisers, or public finance actors shall be conflict-classified and claims-limited.

**14.3.3.4** Any insurance approval implication shall be corrected.

**14.3.3.5** The governing rule shall be:

**Insurance-readiness is not insurance advice or insurance approval.**

***

### **14.3.4 No Securities Offering**

**14.3.4.1** The National Leadership Council shall not offer securities, promote securities, recommend securities, solicit securities investment, distribute offering materials, arrange securities transactions, or create investment interest.

**14.3.4.2** Nothing in Nexus Universe, capital-reader rooms, National Investors Council input, finance-readiness notes, National Model finance-readiness layers, SPV-readiness awareness, Project SPV references, National Consortium Company references, public-safe reports, handoff notes, or investor-facing materials shall be treated as a securities offering.

**14.3.4.3** Where a matter may later involve securities or regulated financial instruments, it shall be routed to competent regulated actors and handled separately from Council activity.

**14.3.4.4** Communications shall avoid investment-promotion language.

**14.3.4.5** The governing rule shall be:

**Nexus participation is not an offer of securities.**

***

### **14.3.5 No Capital Solicitation**

**14.3.5.1** The National Leadership Council shall not solicit capital, raise funds for investments, solicit loans, solicit insurance commitments, solicit guarantees, solicit public finance, solicit donor commitments, solicit philanthropic commitments, or solicit transaction participation.

**14.3.5.2** Capital-reader engagement may occur only to improve readability, identify diligence gaps, understand insurance-readiness questions, understand public finance relevance, understand donor or philanthropic information needs, and prepare lawful handoff awareness.

**14.3.5.3** Capital-reader presence shall not be represented as capital interest, investor commitment, lender interest, insurer interest, donor commitment, philanthropic commitment, public finance commitment, or transaction pipeline.

**14.3.5.4** Any capital solicitation implication shall be corrected.

**14.3.5.5** The governing rule shall be:

**Capital-readability work shall not become capital solicitation.**

***

### **14.3.6 No Brokerage, Lending, Underwriting, or Fund Activity**

**14.3.6.1** The National Leadership Council shall not act as broker, dealer, lender, underwriter, fund, fund manager, insurance broker, reinsurance intermediary, investment adviser, rating agency, guarantor, placement agent, arranger, or transaction platform.

**14.3.6.2** The Council shall not arrange transactions, negotiate finance, syndicate capital, place insurance, issue ratings, underwrite risk, lend funds, manage investments, manage funds, approve guarantees, or broker counterparties.

**14.3.6.3** National Investors Council interface, GRA-aligned finance-readiness work, capital-reader rooms, donor-readiness discussions, or SPV-readiness discussions shall not alter this boundary.

**14.3.6.4** Any participant acting in a regulated financial capacity shall do so outside Council authority and under separate lawful authorization, without implying Council endorsement.

**14.3.6.5** The governing rule shall be:

**The Council reads readiness; it does not intermediate finance.**

***

### **14.3.7 No Bankability, Financeability, or Insurability Determination**

**14.3.7.1** The National Leadership Council shall not determine that a project, provider, National Model item, AEP Passport candidate, Rail candidate, National Consortium Company pathway, Project SPV pathway, public authority dependency, safeguard pathway, or Nexus Universe output is bankable, financeable, insurable, investment-ready, lender-ready, donor-ready, philanthropic-ready, or public-finance-ready.

**14.3.7.2** The Council may identify gaps that affect capital-readability or insurance-readiness, but it shall not determine market readiness.

**14.3.7.3** Terms such as “bankable,” “financeable,” “insurable,” “investment-ready,” “underwritable,” “fundable,” “guarantee-ready,” or similar terms shall not be used unless supported by a competent external finance or insurance process and permitted by the claims record.

**14.3.7.4** Where partial readiness exists, communications shall state the precise status, such as “finance-readiness questions identified,” “diligence gaps mapped,” “insurance-readiness issues identified,” or “SPV-readiness dependencies noted.”

**14.3.7.5** The governing rule shall be:

**Capital-readable does not mean bankable, financeable, or insurable.**

***

### **14.3.8 No Public Finance Approval**

**14.3.8.1** The National Leadership Council shall not approve public finance, recommend public finance as a public authority, allocate public funds, confirm eligibility for public funds, approve guarantees, approve subsidies, approve grants, approve concessional finance, or approve budgetary support.

**14.3.8.2** Public finance relevance may be identified where national priorities, disaster-risk-finance issues, public authority dependencies, infrastructure needs, climate or resilience needs, National Model priorities, Nexus Universe outputs, or Project SPV-readiness questions suggest a possible public finance interface.

**14.3.8.3** Public finance relevance shall not be described as public finance approval, public finance commitment, public funding allocation, public grant award, public guarantee, or public budget decision.

**14.3.8.4** Only competent public finance authorities or lawful finance actors may approve public finance.

**14.3.8.5** The governing rule shall be:

**Public finance relevance is not public finance approval.**

***

### **14.3.9 No Donor or Philanthropic Commitment**

**14.3.9.1** The National Leadership Council shall not approve, secure, promise, imply, solicit, or represent donor commitment, philanthropic commitment, grant commitment, sponsorship commitment, charitable commitment, foundation approval, CSR commitment, development assistance commitment, or concessional support.

**14.3.9.2** Donor or philanthropic participation, observation, interest, learning, capital-reader presence, Nexus Universe participation, National Model inclusion, public-safe reporting, or finance-readiness discussion shall not imply commitment.

**14.3.9.3** Any donor or philanthropic relevance note shall be non-committal, no-reliance, and claims-limited unless a separate donor or philanthropic record states otherwise.

**14.3.9.4** Donor or philanthropic commitment overclaims shall be corrected because they may create false public expectation and institutional reliance.

**14.3.9.5** The governing rule shall be:

**Donor relevance is not donor commitment; philanthropic relevance is not philanthropic commitment.**

***

### **14.3.10 Correction of Finance Overclaim**

**14.3.10.1** Finance overclaim shall be corrected wherever a communication, record, report, presentation, Nexus Universe material, National Model summary, capital-reader room note, National Investors Council input, GRA-aligned note, AEP Passport candidate note, Nexus Rail candidate note, Docket item, handoff note, National Consortium Company interface note, or Project SPV-readiness note implies finance, insurance, investment, public finance, donor, philanthropic, guarantee, rating, underwriting, lending, brokerage, securities, transaction, bankability, financeability, or insurability status not supported by competent external record.

**14.3.10.2** Correction may include revised language, withdrawal, no-reliance clarification, participant notice, investor-facing correction, insurer-facing correction, donor-facing correction, public finance-facing correction, public-safe correction, Docket entry, handoff restriction, or leadership eligibility review.

**14.3.10.3** Finance overclaim shall be treated as high-risk because it may create market reliance, legal exposure, reputational harm, public authority confusion, and capital distortion.

**14.3.10.4** Repeated finance overclaim may justify restriction from finance-readiness pathways, National Investors Council interface, Nexus Universe capital-reader rooms, handoff activity, or leadership-pool eligibility.

**14.3.10.5** The governing rule shall be:

**False finance meaning must be corrected before readiness becomes reliance.**

***

## **14.4 Technical and Provider Boundaries**

This section defines limits that prevent technical work or provider input from becoming validation, certification, procurement, or authorization.

### **14.4.1 No Provider Validation**

**14.4.1.1** The National Leadership Council shall not validate providers.

**14.4.1.2** Provider validation shall not arise from participation in the Council, contribution to National Working Groups, technical input, Nexus Core participation, Nexus Universe demonstration, National Model inclusion, Government Portfolio Showcase involvement, public authority learning, AEP Passport candidacy, Nexus Rail candidacy, public-safe reporting, or handoff awareness.

**14.4.1.3** A provider may contribute information, technology, expertise, infrastructure, data, software, demonstration capability, or implementation insight, but such contribution shall not be described as validation, endorsement, approval, selection, certification, procurement status, standards conformance, public authority approval, finance-readiness, or Nexus-ready status.

**14.4.1.4** Provider-provided information shall be distinguished from independent evidence and public-good records.

**14.4.1.5** The governing rule shall be:

**Provider contribution is useful input; it is not provider validation.**

***

### **14.4.2 No Preferred-Provider Status**

**14.4.2.1** The National Leadership Council shall not create preferred-provider status, approved-provider status, official-provider status, strategic-provider status, certified-provider status, implementation-partner status, or exclusive-provider status.

**14.4.2.2** Preferred-provider status shall not be implied by sponsor support, provider contribution, Nexus Universe visibility, technical demonstration, working-group participation, National Model inclusion, Government Portfolio Showcase involvement, public authority attendance, AEP Passport candidacy, Nexus Rail candidacy, or handoff candidate identification.

**14.4.2.3** Any provider description shall be accurate, source-based, claims-limited, conflict-aware, and provider-neutral.

**14.4.2.4** If a separate lawful procurement, contracting, or partnership record creates a provider role outside the Council, communications shall distinguish that separate record from Council participation.

**14.4.2.5** The governing rule shall be:

**No provider becomes preferred because they participate in public-good readiness work.**

***

### **14.4.3 No Procurement Eligibility**

**14.4.3.1** The National Leadership Council shall not create procurement eligibility, prequalification, bid advantage, public tender status, vendor eligibility, contract eligibility, supplier status, purchasing approval, or marketplace access.

**14.4.3.2** Technical capability mapping, provider-neutral requirements, National Working Group outputs, Nexus Core participation, National Model inclusion, Nexus Universe participation, AEP Passport candidacy, Nexus Rail candidacy, Government Portfolio Showcase materials, or handoff notes shall not create procurement eligibility.

**14.4.3.3** Procurement eligibility belongs to competent procurement bodies and lawful procurement processes.

**14.4.3.4** Provider-linked participants shall not use Council activity to imply procurement eligibility.

**14.4.3.5** The governing rule shall be:

**Public-good readiness does not prequalify vendors.**

***

### **14.4.4 No Certification**

**14.4.4.1** The National Leadership Council shall not certify technologies, providers, systems, datasets, AI models, dashboards, digital twins, infrastructure pathways, National Models, National Working Groups, Nexus Universe outputs, AEP Passport candidates, Nexus Rail candidates, public-safe reports, National Consortium Companies, Project SPVs, or participants.

**14.4.4.2** Certification shall not arise from technical review, evidence preparation, public-safe reporting, working-group participation, National Model inclusion, Nexus Core demonstration, Nexus Observatory input, AEP Passport candidacy, Rail candidacy, Docket handling, or handoff note.

**14.4.4.3** Where certification or conformity assessment may be relevant, the Council may identify the need for separate competent certification, standards, conformity, assurance, or regulatory processes.

**14.4.4.4** Certification language shall not be used unless supported by a competent certification record.

**14.4.4.5** The governing rule shall be:

**The Council may identify evidence; it does not certify evidence or systems.**

***

### **14.4.5 No Standards Conformance**

**14.4.5.1** The National Leadership Council shall not determine standards conformance, conformity, compliance, accreditation, audit completion, maturity status, assurance status, or technical approval.

**14.4.5.2** Standards-interface work, GCRI-aligned methods, Nexus Observatory work, AEP Passport candidacy, Nexus Rail candidacy, public-safe reporting, technical working-group review, Nexus Core demonstration, or National Model inclusion shall not imply standards conformance.

**14.4.5.3** Where standards conformance is relevant, the matter shall be routed to a competent standards, conformity assessment, assurance, certification, accreditation, regulatory, or technical-review body as applicable.

**14.4.5.4** Any standards conformance implication shall be corrected.

**14.4.5.5** The governing rule shall be:

**Standards-interface readiness is not standards conformance.**

***

### **14.4.6 No Nexus-Ready Status**

**14.4.6.1** The National Leadership Council shall not declare any participant, provider, sponsor, technology, project, public authority pathway, finance-readiness pathway, National Model item, Nexus Universe output, AEP Passport candidate, Nexus Rail candidate, National Consortium Company, Project SPV, or handoff matter to be “Nexus-ready” unless a competent Nexus readiness record expressly creates that status and permits that claim.

**14.4.6.2** The phrase “Nexus-ready” shall be treated as a controlled status label, not a general descriptive phrase.

**14.4.6.3** Where partial readiness exists, precise terms shall be used, including “candidate,” “under review,” “evidence-needed,” “safeguard-needed,” “public-authority-needed,” “finance-readiness-needed,” “public-safe-ready,” “controlled-review-ready,” “Docketed,” “Rail candidate,” or “AEP Passport candidate,” as applicable.

**14.4.6.4** Nexus-ready overclaim shall be corrected immediately.

**14.4.6.5** The governing rule shall be:

**Nexus-ready means only what a competent Nexus readiness record says it means.**

***

### **14.4.7 No AEP Passport Status by Participation**

**14.4.7.1** Participation in the National Leadership Council, National Council, National Working Group, Nexus Universe, Nexus Core, National Model preparation, Nexus Observatory pathway, public authority room, capital-reader room, safeguard room, or technical demonstration shall not create AEP Passport status.

**14.4.7.2** AEP Passport status shall exist only where the competent AEP Passport process issues, records, recognizes, or otherwise creates such status.

**14.4.7.3** Candidate status, input status, evidence contribution, public authority learning, finance-readiness review, safeguard review, or Rail routing shall be described only as such.

**14.4.7.4** Any claim that participation created or implied AEP Passport status shall be corrected.

**14.4.7.5** The governing rule shall be:

**AEP Passport status is issued by record, not earned by attendance or visibility.**

***

### **14.4.8 No Nexus Node Approval**

**14.4.8.1** The National Leadership Council shall not approve, designate, certify, validate, or recognize any Nexus Node, National Observatory Node, regional node, technical node, data node, dashboard node, infrastructure node, institutional node, or operating node unless a competent Nexus Node process expressly grants such authority and creates the relevant record.

**14.4.8.2** Node candidacy, Observatory discussion, technical demonstration, National Model inclusion, Nexus Universe participation, public authority learning, provider contribution, or National Working Group output shall not imply Nexus Node approval.

**14.4.8.3** Node-related claims shall distinguish between candidate, proposed, under review, pilot, test, controlled, public-safe, active, suspended, withdrawn, corrected, or recognized status.

**14.4.8.4** Node approval overclaim shall be corrected because it can create technical, public authority, finance, procurement, and operational reliance.

**14.4.8.5** The governing rule shall be:

**Node status requires node record; Council participation does not create it.**

***

### **14.4.9 No Project Authorization**

**14.4.9.1** The National Leadership Council shall not authorize projects.

**14.4.9.2** Project authorization shall not arise from National Model inclusion, National Working Group output, Nexus Universe presentation, Government Portfolio Showcase activity, Nexus Core demonstration, AEP Passport candidacy, Nexus Rail candidacy, public authority learning, capital-reader participation, sponsor support, provider contribution, community participation, Indigenous participation where applicable, or handoff input.

**14.4.9.3** Project authorization requires competent lawful authority, which may include public authority approvals, procurement records, contracts, finance records, insurance records, permits, licences, consent records, safeguard approvals, corporate approvals, SPV records, operational approvals, and other project-specific instruments.

**14.4.9.4** The Council may identify project-readiness questions, but it shall not answer them with authorization.

**14.4.9.5** The governing rule shall be:

**Projects are authorized by lawful project processes, not by leadership readiness discussion.**

***

### **14.4.10 Correction of Provider or Technical Overclaim**

**14.4.10.1** Provider or technical overclaim shall be corrected whenever a communication, record, presentation, website listing, media reference, sponsor material, provider material, investor-facing material, public authority-facing material, public-safe report, National Model summary, Nexus Universe material, Government Portfolio Showcase material, AEP Passport candidate note, Nexus Rail candidate note, Docket item, or handoff note implies provider validation, preferred-provider status, procurement eligibility, certification, standards conformance, Nexus-ready status, AEP Passport status, Nexus Node approval, project authorization, or technical approval not supported by competent record.

**14.4.10.2** Correction may include revised technical language, provider-neutral clarification, withdrawal of promotional materials, separation of provider-provided claims from public-good records, public-safe correction, public authority-facing clarification, investor-facing clarification, Docket entry, handoff restriction, or participant standing review.

**14.4.10.3** Provider or technical overclaim shall be corrected promptly because it may create procurement distortion, technical reliance, public authority confusion, market signal, sponsor advantage, provider advantage, or public trust risk.

**14.4.10.4** Repeated provider or technical overclaim may result in restriction from technical pathways, Nexus Universe demonstrations, National Model references, AEP Passport candidate work, Rail candidate work, public-safe reporting input, or handoff support.

**14.4.10.5** The governing rule shall be:

**Technical credibility depends on correcting technical and provider claims before they become reliance.**

***

## **14.5 Community and Safeguard Boundaries**

This section defines limits that prevent participation, safeguard input, or protected knowledge reference from being misread as consent, endorsement, or permission.

### **14.5.1 Community Participation Is Not Community Consent**

**14.5.1.1** Community participation in the National Leadership Council, National Council, Helix Council, National Working Group, Nexus Universe, public-safe reporting, National Model preparation, safeguard room, public authority learning room, Nexus Observatory pathway, Nexus Rail pathway, AEP Passport candidate process, or handoff discussion shall not constitute community consent.

**14.5.1.2** Community consent requires its own lawful, ethical, context-specific, informed, accessible, culturally appropriate, documented, and rights-respecting process where required.

**14.5.1.3** Community participants may provide lived experience, local knowledge, safeguard concerns, accessibility issues, place-based risk insight, public-interest perspective, or public-safe communication input, but such contribution shall not be used as approval for projects, data use, publication, mapping, commercialization, operationalization, handoff, finance-readiness, public authority action, or implementation.

**14.5.1.4** Any communication implying community consent from participation shall be corrected immediately.

**14.5.1.5** The governing rule shall be:

**Community voice informs readiness; community consent requires its own record.**

***

### **14.5.2 Indigenous Participation Is Not Indigenous Consent**

**14.5.2.1** Indigenous participation, where applicable, in any National Leadership Council, National Council, Helix Council, National Working Group, Nexus Universe, public-safe reporting, National Model, safeguard room, public authority learning room, Observatory, Rail, AEP Passport candidate, Docket, or handoff process shall not constitute Indigenous consent.

**14.5.2.2** Indigenous consent, rights-holder authorization, Indigenous data authorization, protected-knowledge permission, land-related permission, cultural permission, mapping permission, publication permission, commercialization permission, operationalization permission, or project approval requires the relevant lawful, rights-respecting, culturally appropriate, and recorded process.

**14.5.2.3** Indigenous participants may contribute knowledge, questions, safeguards, public-interest perspective, protected-knowledge warnings, or community priorities only within the role and permission recorded.

**14.5.2.4** Where Indigenous or protected knowledge is implicated and authorization status is unclear, the default shall be restricted handling and no public use.

**14.5.2.5** The governing rule shall be:

**Indigenous presence must never be converted into Indigenous consent by implication.**

***

### **14.5.3 Diaspora Participation Is Not National or Community Authorization**

**14.5.3.1** Diaspora participation may provide valuable knowledge, networks, resources, cultural understanding, professional expertise, finance-readiness insight, public-interest perspective, and regional/global linkage, but it shall not constitute national authorization, public authority approval, community approval, Indigenous approval, rights-holder consent, or local consent.

**14.5.3.2** A diaspora participant shall not claim to speak for a country, community, public authority, local population, Indigenous group, rights-holder group, or national institution unless separately authorized by competent record.

**14.5.3.3** Diaspora contributions shall be classified according to role, affiliation, conflict, public claims permission, and safeguard sensitivity.

**14.5.3.4** Diaspora participation shall not be used to bypass national ownership, local participation, community safeguards, or public authority processes.

**14.5.3.5** The governing rule shall be:

**Diaspora contribution can enrich national readiness; it cannot replace national or local authorization.**

***

### **14.5.4 Youth Participation Is Not Future-Generation Approval**

**14.5.4.1** Youth participation in National Leadership Council activity shall not be treated as future-generation approval, youth constituency consent, intergenerational consent, community consent, public authority approval, or endorsement of any project, policy, provider, sponsor, finance-readiness claim, or Nexus Universe output.

**14.5.4.2** Youth participants may contribute future-risk awareness, digital literacy, public-interest perspective, accessibility insight, Nexus Academy pathway intelligence, leadership renewal, and innovation capacity.

**14.5.4.3** Youth participation shall be meaningful, protected, age-appropriate where relevant, mentorship-supported, non-tokenized, and not used as publicity without permission and safeguards.

**14.5.4.4** Youth views shall not be generalized to all future generations, all youth, or affected communities.

**14.5.4.5** The governing rule shall be:

**Youth participation strengthens future-facing legitimacy; it does not approve the future on behalf of others.**

***

### **14.5.5 Protected Knowledge Reference Is Not Authorization**

**14.5.5.1** Reference to protected knowledge, Indigenous knowledge where applicable, community knowledge, local knowledge, traditional knowledge, cultural knowledge, place-based knowledge, ecological knowledge, health-related knowledge, biodiversity knowledge, or security-sensitive knowledge shall not authorize use, publication, mapping, digitization, AI processing, dashboarding, commercialization, operationalization, or handoff.

**14.5.5.2** Protected knowledge may be referenced only within the limits of permission, confidentiality, cultural protocol, rights-holder instruction, public-safe classification, and safeguard record.

**14.5.5.3** Where protected knowledge is identified but permission is unclear, the knowledge shall be treated as restricted and not for publication.

**14.5.5.4** Protected knowledge shall not be extracted into Nexus Universe materials, National Model summaries, AEP Passport candidate notes, Rail candidate notes, public-safe reports, finance-readiness notes, provider materials, sponsor materials, or handoff notes without proper authorization.

**14.5.5.5** The governing rule shall be:

**Knowing that protected knowledge exists is not permission to use it.**

***

### **14.5.6 Safeguard Input Is Not Consent**

**14.5.6.1** Safeguard input shall not be treated as consent, approval, clearance, waiver, authorization, social license, community approval, Indigenous consent, public authority approval, data permission, publication permission, project approval, or handoff permission.

**14.5.6.2** A participant may identify safeguard issues, recommend restrictions, propose public-safe language, flag consent requirements, identify protected-knowledge concerns, or recommend routing without granting authority to proceed.

**14.5.6.3** Safeguard input may identify what must be done before a matter can proceed; it shall not be treated as the completion of what must be done.

**14.5.6.4** Any communication suggesting that safeguard input resolved consent or approval shall be corrected.

**14.5.6.5** The governing rule shall be:

**Safeguard input identifies conditions; it does not satisfy them unless the proper process says so.**

***

### **14.5.7 Public-Interest Participation Is Not Endorsement**

**14.5.7.1** Participation by civil society, media, academia, community actors, youth, accessibility advocates, diaspora, public-interest technologists, public-interest lawyers, public-interest researchers, or other public-interest participants shall not imply endorsement of the National Leadership Council, National Council, Nexus Universe, National Model, provider, sponsor, public authority pathway, finance-readiness pathway, AEP Passport candidate, Rail candidate, handoff candidate, National Consortium Company, Project SPV, or project.

**14.5.7.2** Public-interest participants may contribute critique, caution, questions, public-safe communication review, safeguard review, transparency concerns, accessibility issues, and correction needs without being treated as endorsers.

**14.5.7.3** Public-interest participation shall not be used in sponsor, provider, investor-facing, public authority-facing, media, or Nexus Universe materials as legitimacy proof unless the participant has authorized the specific use and the record supports the meaning.

**14.5.7.4** Any public-interest endorsement overclaim shall be corrected.

**14.5.7.5** The governing rule shall be:

**Public-interest participation strengthens accountability; it is not endorsement by implication.**

***

### **14.5.8 Public-Safe Reporting Is Not Public Warning**

**14.5.8.1** Public-safe reporting supported by the National Leadership Council shall not constitute public warning, emergency alert, disaster declaration, evacuation instruction, public health order, operational command, official forecast, safety directive, security alert, or public authority notice.

**14.5.8.2** Public-safe reporting may communicate general, scoped, claims-limited, safeguard-reviewed information suitable for the intended audience and purpose.

**14.5.8.3** Where public-safe reporting identifies risk information that may require public warning or emergency action, the matter shall be routed to competent public authorities or lawful warning channels.

**14.5.8.4** Public-safe materials shall include no-public-warning language where necessary to prevent reliance.

**14.5.8.5** The governing rule shall be:

**Public-safe reporting informs safely; it does not command or warn as public authority.**

***

### **14.5.9 Handoff Must Carry Safeguard Conditions**

**14.5.9.1** Any handoff input, handoff candidate note, National Consortium Company interface note, Project SPV-readiness awareness note, public authority dependency note, finance-readiness dependency note, safeguard dependency note, Nexus Rail candidate note, AEP Passport candidate note, Docket item, or National Model handoff reference shall carry applicable safeguard conditions.

**14.5.9.2** Handoff shall not remove or dilute privacy restrictions, cyber restrictions, sovereign data restrictions, public authority-sensitive restrictions, community restrictions, Indigenous restrictions where applicable, protected-knowledge restrictions, accessibility conditions, health-data restrictions, biodiversity restrictions, infrastructure-security restrictions, publication limits, consent requirements, or public-safe reporting limits.

**14.5.9.3** A receiving actor shall not treat handoff as permission to use, publish, commercialize, map, automate, operationalize, finance, insure, procure, implement, or execute without satisfying the applicable safeguard conditions.

**14.5.9.4** Where safeguard conditions are unresolved, the handoff record shall state that unresolved status expressly.

**14.5.9.5** The governing rule shall be:

**Handoff does not cleanse risk; it carries risk conditions to the next lawful process.**

***

### **14.5.10 Correction of Consent or Legitimacy Overclaim**

**14.5.10.1** Consent or legitimacy overclaim shall be corrected wherever a communication, record, presentation, website listing, media reference, sponsor material, provider material, investor-facing material, public authority-facing material, public-safe report, National Model summary, Nexus Universe material, Government Portfolio Showcase material, AEP Passport candidate note, Nexus Rail candidate note, Docket item, handoff note, National Consortium Company interface note, or Project SPV-readiness note implies community consent, Indigenous consent, rights-holder approval, social license, diaspora authorization, youth approval, public-interest endorsement, protected-knowledge authorization, data permission, publication permission, commercialization permission, operationalization permission, or handoff permission not supported by competent record.

**14.5.10.2** Correction may include revised language, withdrawal, participant notice, community-facing clarification, Indigenous-facing clarification where applicable, public-safe correction, website correction, media correction, sponsor correction, provider correction, investor-facing correction, public authority-facing correction, Docket entry, handoff restriction, access restriction, or leadership eligibility review.

**14.5.10.3** Consent or legitimacy overclaim shall be treated as high-priority because it may harm people, communities, rights holders, public trust, safeguard integrity, public authority learning, finance-readiness discipline, and lawful handoff.

**14.5.10.4** Repeated or intentional consent or legitimacy overclaim may result in restriction from community-facing pathways, safeguard rooms, Nexus Universe participation, public-safe reporting input, leadership-pool eligibility, handoff support, or National Model reference.

**14.5.10.5** The governing rule shall be:

**False legitimacy must be corrected because public-good systems cannot be built on extracted consent.**

### Related topics

* [XI. CLAIMS](/organization/cooperation/consortiums/gateways/national-councils/leadership/xi.-claims.md) — the claims and communications rules that keep boundaries explicit in public and controlled language.
* [XII. SAFEGUARDS](/organization/cooperation/consortiums/gateways/national-councils/leadership/xii.-safeguards.md) — the safeguard and classification controls that apply when boundary issues affect sensitive material or public-safe release.
* [XV. CORRECTION](/organization/cooperation/consortiums/gateways/national-councils/leadership/xv.-correction.md) — correction, withdrawal, restriction, and supersession rules when boundary overclaims create unsafe meaning.

### Summary

This section defines the limits that keep participation, public authority interaction, finance-readiness work, technical contribution, and community participation from being overstated.

It also defines the prohibited effects that must not arise by implication, visibility, proximity, recommendation, handoff, or public narrative.

### Next steps

1. Review [XI. CLAIMS](/organization/cooperation/consortiums/gateways/national-councils/leadership/xi.-claims.md) before describing any role, status, recommendation, or readiness matter in public or controlled communications.
2. Review [XII. SAFEGUARDS](/organization/cooperation/consortiums/gateways/national-councils/leadership/xii.-safeguards.md) before releasing material that could expose sensitive information or create unsafe public meaning.
3. Review [XV. CORRECTION](/organization/cooperation/consortiums/gateways/national-councils/leadership/xv.-correction.md) for how to correct, restrict, withdraw, or supersede boundary overclaims.


---

# 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/leadership/xiv.-boundaries.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.