# XXII. BOUNDARIES

### 22. Boundaries and Prohibited Effects

### 22.1 Federation Boundary Principles

#### 22.1.1 Participation Is Not Authority

**22.1.1.1** **Participation Is Not Authority** shall be a foundational boundary of the Nexus Consortium Federation. Participation in any global, regional, national, council, helix, Working Group, Competence Cell, Nexus Universe, AEP Passport, Nexus Rail, Docket, Grid, public-safe reporting, sponsorship, partnership, public authority learning, finance-readiness, safeguard, handoff, National Consortium Company interface, Project SPV interface, or other Nexus-related pathway shall create only the standing, access, contribution opportunity, and record-based role expressly stated in the applicable record.

**22.1.1.2** Participation shall not create governance authority, board appointment, agency, representation authority, institutional endorsement, public authority status, government approval, regulatory comfort, procurement status, financeability, bankability, insurability, capital commitment, insurance approval, donor approval, public finance allocation, provider validation, certification, standards conformance, community consent, Indigenous consent, FPIC satisfaction, project authorization, Nexus-ready status, AEP Passport status, Nexus Node status, public warning authority, emergency command authority, or execution authority.

**22.1.1.3** Participation shall be interpreted according to role, capacity, layer, geography, term, access class, publication class, permitted claims, prohibited claims, conflict classification, safeguard conditions, data conditions, public authority boundaries, finance boundaries, provider-neutrality conditions, sponsor restrictions, correction history, renewal status, and archive status.

**22.1.1.4** Participation by a person shall not bind that person’s employer, public authority, fund, insurer, donor, university, company, community, Indigenous body where applicable, media organization, sponsor, provider, National Consortium Company, Project SPV, or other affiliated institution unless a separate lawful record expressly creates that institutional commitment.

**22.1.1.5** Participation by an institution shall not bind its affiliates, subsidiaries, parent entities, investors, public authorities, clients, providers, communities, Indigenous bodies where applicable, project vehicles, or downstream counterparties unless separately recorded.

**22.1.1.6** All public and external participation language shall preserve the distinction between access and authority, contribution and approval, support and control, readiness and execution, learning and official action, safeguard input and consent, and handoff and implementation.

**22.1.1.7** Participation boundary records shall be correctionable. If participation is used to imply authority, endorsement, approval, financeability, certification, consent, project authorization, or execution, the relevant participation record, claim, public-safe listing, report, handoff, enterprise material, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.1.2 Subscription Is Not Membership in GCRI, GRF, or GRA

**22.1.2.1** **Subscription Is Not Membership in GCRI, GRF, or GRA** shall mean that a subscription, participation level, access tier, council participation, helix participation, regional participation, global participation, Nexus Universe access, sponsor listing, partner listing, anchor status, host status, provider-candidate status, public authority learner status, capital-reader status, public-safe reporting contributor status, or other Consortium participation record shall not create membership, governance rights, voting rights, board rights, committee rights, officer status, fiduciary status, employment, agency, representation authority, or institutional standing in **The Global Centre for Risk and Innovation (GCRI)**, **The Global Risks Forum (GRF)**, or **The Global Risks Alliance (GRA)**.

**22.1.2.2** Any pathway into GCRI, GRF, or GRA shall be separate, institution-specific, eligibility-based, record-based, and governed by the applicable institution’s own governing documents, policies, participation rules, membership rules where applicable, conflicts rules, claims rules, safeguard rules, and correction rules.

**22.1.2.3** A person or institution may, where eligible and separately accepted, participate in one, two, or all three of GCRI, GRF, and GRA, but such participation shall not arise automatically from Consortium subscription and shall not collapse the separate roles of the three institutions.

**22.1.2.4** Consortium subscription shall be gateway access to Federation participation only. It shall not confer technical authority from GCRI, legitimacy authority from GRF, finance-readiness authority from GRA, or any cross-institutional authority unless separately and lawfully recorded.

**22.1.2.5** Subscription records shall identify only the subscribed pathway, participation level, access class, term, scope, permitted claims, prohibited claims, renewal conditions, correction conditions, and archive treatment.

**22.1.2.6** Public subscription claims shall avoid language implying institutional membership in GCRI, GRF, or GRA unless a separate institution-specific membership or participation record permits the exact claim.

**22.1.2.7** Subscription boundary records shall be correctionable. If subscription is used to imply membership, authority, endorsement, governance rights, technical approval, legitimacy approval, finance approval, or cross-institutional status in GCRI, GRF, or GRA, the relevant subscription record, claim, listing, and public materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.1.3 Council Status Is Not Board Appointment

**22.1.3.1** **Council Status Is Not Board Appointment** shall mean that participation in a National Council, National Leadership Council, National Investors Council, Helix Council, regional council, global council interface, advisory room, Working Group, Competence Cell, Nexus Universe delegation, or leadership pool shall not create appointment to any Stewardship Board, corporate board, nonprofit board, public authority board, National Consortium Company board, Project SPV board, GCRI board, GRF board, GRA board, committee, fiduciary body, officer role, or formal governance organ unless a separate lawful appointment record expressly provides that status.

**22.1.3.2** Council participation may support leadership formation, stakeholder formation, evidence formation, public authority learning, finance-readiness literacy, safeguard review, Nexus Universe preparation, Working Group referral, National Model input, public-safe reporting input, AEP Passport and Nexus Rail candidate preparation, Docket and Grid input, and lawful handoff literacy, but shall not itself create governance authority.

**22.1.3.3** Council titles, chair roles, co-chair roles, facilitator roles, convenor roles, helix lead roles, Working Group lead roles, delegation roles, public-stage roles, and senior participant roles shall be interpreted strictly according to the applicable record and shall not be treated as board roles unless expressly appointed.

**22.1.3.4** Council status shall not create fiduciary authority, voting authority, institutional representation authority, ability to bind the Federation, ability to bind a National Nexus Consortium, ability to bind a Regional Headquarters Consortium, ability to bind the Global Nexus Consortium, or ability to bind GCRI, GRF, GRA, a National Consortium Company, or a Project SPV.

**22.1.3.5** Public descriptions of councils shall distinguish participation, leadership-pool eligibility, advisory contribution, and stakeholder formation from formal governance appointment.

**22.1.3.6** Any pathway from council participation to board consideration shall be separately recorded, conflict-reviewed, eligibility-reviewed, and appointment-reviewed, and shall not be automatic.

**22.1.3.7** Council-status boundary records shall be correctionable. If council status is used to imply board appointment, governance authority, voting rights, fiduciary status, institutional control, approval, or execution authority, the relevant record and claim shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.1.4 Regional Participation Is Not Regional Supremacy

**22.1.4.1** **Regional Participation Is Not Regional Supremacy** shall mean that participation in a Regional Headquarters Consortium, regional interface, regional council, regional Working Group, regional Nexus Universe pathway, Regional Cluster Room, regional sponsor pathway, regional partner pathway, regional AEP Passport or Nexus Rail pathway, regional Docket or Grid pathway, or Regional Cluster Program Plan pathway shall not create authority over countries, National Nexus Consortiums, public authorities, national councils, national helixes, communities, Indigenous peoples where applicable, National Consortium Companies, Project SPVs, providers, sponsors, or projects.

**22.1.4.2** Regional participation shall be support, translation, synthesis, coordination, learning, mobilization, public-safe reporting, and routing participation within the recorded scope. It shall not authorize national bypass, country approval, public authority approval, procurement status, financeability, provider validation, certification, consent, project authorization, or execution.

**22.1.4.3** A Regional Headquarters Consortium shall be a regional support hub, not a supremacy hub. A regional host, regional sponsor, regional partner, regional capital reader, regional public authority learner, regional provider, or regional technical contributor shall not use regional participation to control national records or country activation.

**22.1.4.4** Country coverage within a regional map shall not imply country endorsement. Regional Top-Three status shall not imply country ranking, public authority approval, or project priority. Regional threshold activation shall not imply regional authority over national decision-making.

**22.1.4.5** Regional claims shall preserve country source records, national gateway discipline, public authority boundaries, finance boundaries, provider-neutrality conditions, safeguard conditions, protected knowledge restrictions, and correction histories.

**22.1.4.6** Any regional synthesis shall synthesize national records without overriding them.

**22.1.4.7** Regional boundary records shall be correctionable. If regional participation is used to imply regional supremacy, national bypass, country approval, public authority approval, financeability, provider validation, consent, project authorization, or execution, the relevant regional record, claim, public-safe report, handoff, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.1.5 Global Participation Is Not Global Authority

**22.1.5.1** **Global Participation Is Not Global Authority** shall mean that participation in the Global Nexus Consortium, global interface, global council surface, global Nexus Universe pathway, Global Nexus Core, global sponsor pathway, global partner pathway, global AEP Passport or Nexus Rail pathway, global Docket or Grid pathway, global public-safe reporting pathway, or global handoff-readiness pathway shall not create authority over regions, countries, public authorities, National Nexus Consortiums, Regional Headquarters Consortiums, communities, Indigenous peoples where applicable, providers, sponsors, capital actors, National Consortium Companies, Project SPVs, or projects.

**22.1.5.2** Global participation shall create only the recorded global role, access, contribution opportunity, and public-safe standing. It shall not create global supremacy, intergovernmental authority, regulatory authority, public authority approval, procurement authority, finance authority, certification authority, standards authority by default, consent authority, project authorization, public warning authority, emergency command authority, or execution authority.

**22.1.5.3** Global visibility, global public-stage participation, global sponsorship, global hosting, global technical contribution, global capital-reader participation, global public authority room participation, global media visibility, or global Nexus Universe participation shall not be used as approval or authority.

**22.1.5.4** Global claims shall preserve regional and national source limitations and shall not convert global synthesis into national approval or regional supremacy.

**22.1.5.5** Global coordination may support common rail discipline, public-good records, Nexus Universe architecture, AEP Passport and Nexus Rail coordination, Docket and Grid comparability, public-safe reporting, and correction, but shall not execute or authorize downstream action.

**22.1.5.6** Public global participation language shall identify scope and limitations where needed to prevent reliance.

**22.1.5.7** Global boundary records shall be correctionable. If global participation is used to imply global authority, regional override, country approval, public authority approval, financeability, provider validation, certification, consent, project authorization, or execution, the relevant global record, claim, public-safe report, handoff, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.1.6 Handoff Is Not Execution by Public-Good Stack

**22.1.6.1** **Handoff Is Not Execution by Public-Good Stack** shall mean that transmission, routing, referral, provision, explanation, or publication of a public-good record to a National Consortium Company, Project SPV, provider, host, operator, public authority, investor, insurer, donor, development actor, public finance actor, procurement body, community process, Indigenous governance process where applicable, environmental process, data process, cyber process, or other downstream recipient shall not make any public-good stack body an executing party.

**22.1.6.2** A handoff shall permit only separate downstream review, diligence, decision, structuring, public authority process, finance process, procurement process, safeguard process, community or Indigenous process where applicable, enterprise process, project process, or implementation process within the recipient’s own lawful authority.

**22.1.6.3** Handoff shall not create project approval, finance approval, insurance approval, donor approval, public finance approval, procurement approval, certification, standards conformance, consent, public authority decision, provider selection, investment memorandum, transaction document, insurance submission, donor application, public finance application, implementation plan, or execution mandate.

**22.1.6.4** Public-good stack bodies shall not become agents, joint venturers, partners in execution, contractors, operators, developers, funders, insurers, underwriters, brokers, advisers, procurement bodies, public authorities, consent bodies, public warning bodies, emergency command centers, or implementation vehicles by reason of handoff.

**22.1.6.5** Handoff records shall include non-execution, non-agency, no-shared-liability, public authority boundary, finance boundary, procurement-neutrality, provider-neutrality, safeguard, consent-boundary, protected knowledge, correction, and archive language.

**22.1.6.6** A downstream recipient shall remain responsible for all independent lawful decisions and obligations.

**22.1.6.7** Handoff boundary records shall be correctionable. If handoff is used as execution, approval, financeability, provider validation, consent, project authorization, agency, or shared liability, the handoff record and affected downstream materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.1.7 Nexus Universe Participation Is Not Approval

**22.1.7.1** **Nexus Universe Participation Is Not Approval** shall mean that participation in Nexus Universe, including preparation participation, delegation participation, public-stage participation, speaking, sponsorship, hosting, technical contribution, controlled-room access, public authority learning-room participation, capital-reader room participation, insurance-readiness room participation, donor room participation, provider-neutral room participation, safeguard-room participation, AEP Passport room participation, Nexus Rail room participation, Docket or Grid participation, handoff discussion, media visibility, or public-safe reporting contribution, shall not create approval.

**22.1.7.2** Nexus Universe participation shall not create endorsement, public authority approval, government endorsement, regulatory comfort, policy adoption, procurement status, financeability, bankability, insurability, capital commitment, insurance approval, donor approval, public finance allocation, provider validation, certification, standards conformance, community consent, Indigenous consent, FPIC satisfaction, project authorization, AEP Passport status, Nexus-ready status, Nexus Node status, public warning authority, emergency command authority, or execution authority.

**22.1.7.3** Nexus Universe shall be an annual public-good systems-build arena, not an approval forum, investment platform, procurement venue, certification body, consent process, public authority substitute, standards authority by default, or execution vehicle.

**22.1.7.4** Room participation shall be classified by purpose. Public authority rooms are learning rooms, not approval rooms. Capital-reader rooms are readability rooms, not investment rooms. Insurance-readiness rooms are readiness rooms, not underwriting rooms. Safeguard rooms are safeguard rooms, not consent rooms. Provider-neutral rooms are capability-mapping rooms, not validation rooms. Handoff rooms are routing rooms, not execution rooms.

**22.1.7.5** Nexus Universe public-safe materials shall include boundary language where a reasonable reader could infer approval.

**22.1.7.6** Nexus Universe outputs shall remain subject to records, claims, safeguard, public-safe reporting, and correction controls.

**22.1.7.7** Nexus Universe boundary records shall be correctionable. If Nexus Universe participation is used as approval, finance signal, public authority endorsement, provider validation, certification, consent, project authorization, Nexus-ready status, AEP Passport status, Nexus Node status, public warning, or execution authority, the relevant record, claim, report, room material, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.1.8 AEP Passport Input Is Not AEP Passport Status

**22.1.8.1** **AEP Passport Input Is Not AEP Passport Status** shall mean that a record, system, project, provider, node, pathway, National Model element, Regional Cluster Program Plan element, Nexus Universe output, public-good contribution, technical contribution, safeguard record, finance-readiness note, public authority dependency note, Docket item, Grid input, Proof Receipt input where authorized, or handoff-readiness note submitted to or discussed within an AEP Passport pathway shall not itself create AEP Passport status.

**22.1.8.2** AEP Passport candidate status, layer input, discussion, reference, public-safe mention, Nexus Universe session, Docket linkage, Grid linkage, Nexus Rail linkage, or handoff linkage shall not create approval, certification, financeability, procurement status, provider validation, public authority approval, consent, Nexus-ready status, Nexus Node status, project authorization, or execution.

**22.1.8.3** AEP Passport status may be claimed only where a competent AEP Passport process has issued the relevant status and the applicable record permits the exact claim.

**22.1.8.4** Proof Receipt references, where authorized, shall mean only what the applicable record expressly states. They shall not be expanded into approval, certification, maturity approval, AEP Passport status, financeability, procurement status, provider validation, public authority approval, consent, project authorization, or execution.

**22.1.8.5** AEP Passport language shall distinguish candidate input, layer input, Proof Receipt input where authorized, discussion, public-safe reference, issued status, restricted status, corrected status, withdrawn status, superseded status, and archive status.

**22.1.8.6** Public AEP Passport-related claims shall be reviewed before use.

**22.1.8.7** AEP Passport boundary records shall be correctionable. If AEP Passport input is used as AEP Passport status, approval, certification, financeability, provider validation, public authority approval, consent, project authorization, Nexus-ready status, Nexus Node status, or execution authority, the relevant record, claim, public-safe report, handoff, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.1.9 Rail Input Is Not Execution

**22.1.9.1** **Rail Input Is Not Execution** shall mean that contribution to, discussion within, candidate routing through, or reference by a Nexus Rail pathway shall not create execution authority, project implementation, project approval, provider selection, procurement status, financeability, public authority approval, consent, certification, Nexus-ready status, AEP Passport status, Nexus Node status, or operational mandate.

**22.1.9.2** Nexus Rail inputs may identify routeability questions, dependencies, technical interfaces, public authority dependencies, finance-readiness dependencies, provider-neutrality conditions, safeguard conditions, data and cyber requirements, infrastructure dependencies, Docket items, Grid inputs, Nexus Universe outputs, and handoff-readiness conditions, but shall not execute or authorize downstream activity.

**22.1.9.3** A Nexus Rail candidate record shall not be treated as a corridor approval, infrastructure approval, technology approval, procurement approval, implementation approval, public authority decision, provider validation, or project authorization.

**22.1.9.4** Rail-related language shall distinguish routeability, candidate status, dependency mapping, technical review, public-safe reference, handoff-readiness, and execution by separate lawful actors.

**22.1.9.5** Rail inputs shall preserve safeguards, public authority dependencies, finance dependencies, procurement dependencies, provider-neutrality conditions, data restrictions, cyber restrictions, protected knowledge restrictions, and correction rights.

**22.1.9.6** Rail-related public-safe materials shall include limitations where needed to prevent execution inference.

**22.1.9.7** Rail boundary records shall be correctionable. If Rail input is used as execution, project approval, financeability, procurement status, provider validation, public authority approval, certification, consent, Nexus-ready status, AEP Passport status, or Nexus Node status, the relevant record, claim, public-safe report, handoff, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.1.10 Correction of Boundary Overclaim

**22.1.10.1** **Correction of Boundary Overclaim** shall be the mandatory process through which any overstatement, ambiguity, misuse, public-safe reporting error, sponsor claim, provider claim, finance claim, public authority claim, community or Indigenous claim where applicable, Nexus Universe claim, AEP Passport claim, Nexus Rail claim, Docket or Grid claim, handoff claim, National Consortium Company claim, Project SPV claim, or enterprise-interface claim that crosses a Federation boundary is corrected.

**22.1.10.2** Boundary overclaim may include participation-as-authority, subscription-as-GCRI/GRF/GRA-membership, council-status-as-board-appointment, regional-participation-as-regional-supremacy, global-participation-as-global-authority, handoff-as-execution, Nexus-Universe-participation-as-approval, AEP-Passport-input-as-status, Rail-input-as-execution, and any similar role-collapse claim.

**22.1.10.3** Correction measures may include claim withdrawal, language narrowing, public-safe clarification, record reclassification, public listing correction, mark-use restriction, room correction, sponsor or provider correction, public authority reference correction, finance no-reliance correction, safeguard reattachment, handoff suspension, recipient notice, public material withdrawal, supersession, non-renewal, and archive notation.

**22.1.10.4** Urgent correction shall occur where delay may create public authority confusion, finance reliance, procurement advantage, provider validation, certification drift, consent overclaim, protected knowledge exposure, public warning confusion, market confusion, reputational misuse, or execution implication.

**22.1.10.5** Boundary correction shall preserve confidentiality and public-safe discipline and shall not expose sensitive information unnecessarily.

**22.1.10.6** Boundary corrections shall be linked to the relevant claims register, correction register, public-safe reporting register, handoff record, and archive entry.

**22.1.10.7** Boundary correction records shall themselves be correctionable. If a correction is incomplete, inaccurate, unsafe, publicized beyond permission, or creates a new overclaim, the correction record shall be corrected, restricted, superseded, publicly clarified where necessary, or archived.

***

### 22.2 Public Authority Boundaries

#### 22.2.1 No Public Authority Delegation

**22.2.1.1** **No Public Authority Delegation** shall mean that no Nexus-related participation, subscription, council role, helix role, Working Group role, Competence Cell role, Nexus Universe participation, public authority learning room, public-safe report, National Model, Regional Cluster Program Plan, AEP Passport input, Nexus Rail input, Docket item, Grid input, handoff-readiness record, sponsorship, partnership, National Consortium Company interface, or Project SPV interface shall be interpreted as delegation of public authority to the Federation or any public-good stack body.

**22.2.1.2** The Federation shall not exercise governmental, regulatory, permitting, procurement, public finance, public warning, emergency command, enforcement, licensing, inspection, standards-conformance, public health, infrastructure approval, environmental approval, data authorization, or other public-law authority unless separately and lawfully authorized by a competent public authority in a controlling record.

**22.2.1.3** Public authority learning, dependency mapping, dashboard review, Government Portfolio awareness, public finance relevance discussion, public authority room participation, AEP Passport public authority layer discussion, Nexus Rail dependency routing, Docket or Grid input, and public-safe reporting shall not constitute delegation.

**22.2.1.4** Public authorities retain their own lawful powers, duties, procedures, liabilities, discretion, records, and accountability.

**22.2.1.5** Any public authority engagement shall identify capacity, jurisdiction, authority, record limits, confidentiality, publication permissions, public-safe status, and correction conditions.

**22.2.1.6** Public communications shall avoid language suggesting that Nexus acts for, as, or in place of public authorities.

**22.2.1.7** Public authority delegation overclaims shall be corrected. If delegation is implied without lawful record, the relevant claim, record, report, handoff, and public material shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.2.2 No Government Endorsement

**22.2.2.1** **No Government Endorsement** shall mean that participation by a government, ministry, agency, regulator, municipality, public enterprise, public finance body, public infrastructure body, public official, former public official, public-sector employee, public health body, emergency authority, Indigenous or Tribal public-governance body where applicable, or public authority learner shall not imply governmental endorsement of Nexus, a participant, sponsor, provider, project, National Model, Regional Cluster Program Plan, Nexus Universe output, AEP Passport candidate, Nexus Rail candidate, Docket item, Grid input, National Consortium Company, Project SPV, or handoff pathway.

**22.2.2.2** Government endorsement may be claimed only where a competent government or public authority has separately and lawfully issued the endorsement and permitted the exact claim.

**22.2.2.3** Meetings, attendance, correspondence, room participation, speeches, photographs, public-stage appearance, Government Portfolio showcase preparation, public-safe reporting reference, or participation in a Nexus event shall not constitute endorsement.

**22.2.2.4** Government names, logos, seals, titles, quotations, email domains, and official affiliations shall not be used to imply endorsement without permission and controlling record support.

**22.2.2.5** Government-related claims shall distinguish learning, consultation where lawful, observation, official process, official decision, and endorsement.

**22.2.2.6** Public materials shall include limitation language where government participation could be misunderstood.

**22.2.2.7** Government endorsement overclaims shall be corrected. If government endorsement is implied without lawful record, the claim and affected materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.2.3 No Regulatory Approval

**22.2.3.1** **No Regulatory Approval** shall mean that no Nexus record, participation, Nexus Universe session, public authority learning room, AEP Passport input, Nexus Rail input, Docket item, Grid input, National Model, Regional Cluster Program Plan, public-safe report, sponsor role, provider role, handoff-readiness record, National Consortium Company interface, or Project SPV interface shall be treated as regulatory approval, regulatory comfort, regulatory non-objection, regulatory finding, compliance determination, licensing decision, permitting decision, or enforcement decision.

**22.2.3.2** Regulatory approval may be claimed only where a competent regulator or public authority has separately and lawfully issued the relevant approval or decision and permitted the exact claim.

**22.2.3.3** Regulatory participation in learning, dependency mapping, public-safe review, AEP Passport public authority layers, Nexus Rail dependency routing, Docket input, Grid input, or Nexus Universe rooms shall not create regulatory approval.

**22.2.3.4** Public-safe materials shall not describe matters as compliant, cleared, approved, authorized, accepted, permitted, regulatory-ready, or regulator-supported unless supported by a competent record.

**22.2.3.5** Participants remain responsible for their own regulatory compliance and approvals outside the public-good stack.

**22.2.3.6** Regulatory language shall be reviewed before external use.

**22.2.3.7** Regulatory approval overclaims shall be corrected. If regulatory approval is implied without lawful record, the relevant claim, report, handoff, public material, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.2.4 No Policy Adoption

**22.2.4.1** **No Policy Adoption** shall mean that no National Model, Regional Cluster Program Plan, Global Annual Record, Nexus Universe output, public authority learning note, AEP Passport input, Nexus Rail input, Docket item, Grid input, public-safe report, council output, helix output, Working Group output, sponsor-supported output, provider-supported output, or handoff-readiness record shall be described as adopted public policy unless a competent public authority has separately and lawfully adopted the relevant policy and permitted the claim.

**22.2.4.2** Nexus may support public authority learning, evidence translation, systems-risk framing, dependency mapping, public-safe reporting, finance-readiness literacy, and policy-relevant knowledge, but such support shall not constitute policy adoption.

**22.2.4.3** Policy discussion, policy learning, government attendance, public authority room participation, Government Portfolio showcase preparation, public-safe report receipt, or National Model reference shall not create policy adoption.

**22.2.4.4** Public-safe language shall distinguish policy-relevant learning from official policy.

**22.2.4.5** Participants shall not describe Nexus outputs as national strategy, government plan, public authority program, regional policy, official roadmap, or adopted policy without competent record support.

**22.2.4.6** Policy-related materials shall preserve public authority boundaries and avoid official-action language.

**22.2.4.7** Policy adoption overclaims shall be corrected. If Nexus materials are misrepresented as adopted policy, the claim and affected materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.2.5 No Public Finance Allocation

**22.2.5.1** **No Public Finance Allocation** shall mean that no Nexus participation, public authority learning, finance-readiness discussion, public finance relevance note, capital-reader room, donor room, development room, National Investors Council participation, Nexus Universe participation, AEP Passport finance-layer input, Nexus Rail finance-readiness input, Docket item, Grid input, public-safe report, National Model, Regional Cluster Program Plan, handoff-readiness record, National Consortium Company interface, or Project SPV interface shall be treated as allocation, approval, commitment, reservation, prioritization, endorsement, guarantee, or award of public finance.

**22.2.5.2** Public finance allocation may be claimed only where a competent public finance authority or public body has separately and lawfully issued the allocation or decision and permitted the exact claim.

**22.2.5.3** Public finance relevance is not public finance approval. Public finance reader participation is not public finance commitment. Government Portfolio showcase preparation is not funding allocation.

**22.2.5.4** Public finance-related materials shall include no-reliance and public authority boundary language where needed.

**22.2.5.5** Public finance discussions shall preserve unresolved dependencies, including public authority, procurement, finance, insurance, legal, tax, accounting, technical, safeguard, community, Indigenous where applicable, data, cyber, and project dependencies.

**22.2.5.6** Public finance language shall be reviewed before external use.

**22.2.5.7** Public finance allocation overclaims shall be corrected. If allocation, approval, commitment, guarantee, or funding is implied without competent record, the relevant claim, report, material, handoff, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.2.6 No Procurement Status

**22.2.6.1** **No Procurement Status** shall mean that participation in Nexus, sponsorship, partnership, provider-candidate status, technical contribution, Working Group participation, Competence Cell participation, Nexus Universe participation, public authority learning-room participation, provider-neutral mapping, AEP Passport candidate input, Nexus Rail candidate input, Docket input, Grid input, National Model reference, Regional Cluster Program Plan reference, handoff-readiness, National Consortium Company interface, or Project SPV interface shall not create procurement eligibility, prequalification, shortlist status, preferred-provider status, procurement award, procurement recommendation, public buyer approval, or procurement advantage.

**22.2.6.2** Procurement status may be claimed only where a competent procurement body has separately and lawfully issued the relevant procurement decision and permitted the exact claim.

**22.2.6.3** Provider-neutral capability mapping shall not rank, endorse, validate, recommend, select, approve, certify, or procure providers.

**22.2.6.4** Public authority learning rooms and procurement-neutral learning pathways shall not be used as procurement access or procurement advantage.

**22.2.6.5** National Consortium Companies and Project SPVs shall maintain separate lawful procurement processes and shall not use public-good records to shortcut procurement.

**22.2.6.6** Procurement-related language shall be reviewed for competition, conflicts, anti-corruption, public authority boundaries, provider-neutrality, procurement-neutrality, and correctionability.

**22.2.6.7** Procurement status overclaims shall be corrected. If procurement status is implied without lawful procurement record, the relevant claim, record, public-safe report, handoff, provider material, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.2.7 No Public Warning

**22.2.7.1** **No Public Warning** shall mean that public-safe reporting, observability summaries, dashboard summaries, National Model summaries, Regional Cluster Program Plan summaries, Nexus Universe outputs, AEP Passport references, Nexus Rail references, Docket summaries, Grid summaries, safeguard summaries, correction notices, renewal notices, or archive summaries shall not constitute public warnings, emergency alerts, public health warnings, disaster warnings, safety orders, evacuation notices, regulatory notices, consumer warnings, market warnings, infrastructure warnings, cyber warnings, or official emergency communications unless issued by a competent public authority through a separate lawful process.

**22.2.7.2** Nexus public-safe reporting may describe risk themes, dependencies, learning areas, readiness questions, evidence limits, safeguard issues, correction items, and unresolved matters, but shall not command public action or substitute for official warning systems.

**22.2.7.3** Public-safe reports involving hazards, disasters, cyber incidents, infrastructure risks, public health risks, humanitarian settings, security risks, environmental risks, or emergency conditions shall be reviewed to prevent warning confusion.

**22.2.7.4** Where a matter may require public warning, the record shall identify the public authority dependency and shall not issue the warning itself.

**22.2.7.5** Media and public-stage materials shall not use directive, alarmist, or official-warning language unless separately authorized by a competent public authority.

**22.2.7.6** Public reporting language shall distinguish evidence, observability, learning, readiness, dependency mapping, public-safe publication, and official warning.

**22.2.7.7** Public warning overclaims shall be corrected. If a report or material is interpreted as official warning without lawful authority, it shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.2.8 No Emergency Command

**22.2.8.1** **No Emergency Command** shall mean that the Federation, GCRI, GRF, GRA, the Global Nexus Consortium, a Regional Headquarters Consortium, a National Nexus Consortium, Central Nexus Bureau, Nexus Universe, National Councils, Helix Councils, Working Groups, Competence Cells, public-safe reporting pathways, AEP Passport pathways, Nexus Rail pathways, Docket pathways, Grid pathways, sponsors, partners, providers, capital readers, public authority learners, National Consortium Companies, and Project SPVs shall not act as emergency command centers by reason of Nexus participation or records.

**22.2.8.2** Nexus-related bodies may support learning, evidence, observability, public-safe reporting, preparedness literacy, resilience framing, dependency mapping, and post-cycle correction, but shall not command emergency response, issue evacuation orders, deploy responders, direct public authorities, operate emergency systems, allocate emergency resources, or substitute for emergency management bodies.

**22.2.8.3** Nexus Universe live operation shall not be emergency operation. Nexus Core build shall not be emergency command. Observatory outputs shall not be emergency orders. Public-safe reports shall not be emergency instructions.

**22.2.8.4** Any emergency-related public authority interface shall be capacity-classified and boundary-controlled.

**22.2.8.5** Emergency-related language shall be reviewed before publication or external use.

**22.2.8.6** If emergency command authority is required, it must be exercised only by competent lawful public authorities or authorized emergency actors outside the public-good stack.

**22.2.8.7** Emergency command overclaims shall be corrected. If Nexus materials imply emergency command, response authority, public warning authority, or emergency execution, the relevant record and public materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.2.9 No Data Authorization by Presence

**22.2.9.1** **No Data Authorization by Presence** shall mean that attendance, participation, contribution, room access, Nexus Universe presence, public authority learner participation, community participation, Indigenous participation where applicable, provider participation, sponsor participation, capital-reader participation, media participation, National Council participation, Helix Council participation, Working Group participation, or handoff discussion shall not authorize collection, use, disclosure, transfer, publication, AI use, mapping, digitization, aggregation, commercialization, or handoff of data beyond the applicable record.

**22.2.9.2** Data authorization shall require a lawful basis, purpose limitation, source permission where required, sensitivity classification, access controls, permitted use, prohibited use, retention conditions, correction rights, withdrawal rights where applicable, and archive treatment.

**22.2.9.3** The presence of a public authority shall not authorize public authority data use. The presence of a provider shall not authorize provider-sensitive data use. The presence of a community participant shall not authorize community data use. The presence of an Indigenous participant shall not authorize Indigenous data or protected knowledge use. The presence of a capital reader shall not authorize finance-sensitive data use.

**22.2.9.4** Data collected for one Nexus pathway shall not be reused for another pathway, public-safe report, sponsor material, provider material, investor material, AI system, dashboard, digital twin, map, handoff package, Company record, or SPV record unless authorized.

**22.2.9.5** Data-related public-safe summaries shall preserve privacy, confidentiality, protected knowledge, community sensitivity, public authority sensitivity, finance sensitivity, provider sensitivity, infrastructure sensitivity, security sensitivity, cyber sensitivity, and correctionability.

**22.2.9.6** Data authorization language shall be reviewed where data may be sensitive, personal, protected, public authority-sensitive, finance-sensitive, provider-sensitive, community-sensitive, Indigenous-sensitive where applicable, cyber-sensitive, or infrastructure-sensitive.

**22.2.9.7** Data authorization overclaims shall be corrected. If presence is used as authorization, or data is used beyond record scope, the relevant data record, public material, handoff, enterprise record, and archive entry shall be corrected, restricted, withdrawn, deleted where required, superseded, publicly clarified where necessary, or archived.

***

#### 22.2.10 Correction of Public Authority Overclaim

**22.2.10.1** **Correction of Public Authority Overclaim** shall be the mandatory process for correcting any claim, record, report, public-safe material, Nexus Universe material, AEP Passport reference, Nexus Rail reference, Docket or Grid summary, National Model, Regional Cluster Program Plan, sponsor material, provider material, investor material, public authority material, handoff record, National Consortium Company material, Project SPV material, or archive entry that implies public authority delegation, government endorsement, regulatory approval, policy adoption, public finance allocation, procurement status, public warning, emergency command, data authorization, project authorization, or official action without lawful support.

**22.2.10.2** Public Authority Overclaim may be triggered by misuse of public authority names, logos, titles, email domains, meeting attendance, public-stage appearance, public authority room participation, Government Portfolio references, public finance references, regulatory-learning references, public-safe report references, or public authority dependency notes.

**22.2.10.3** Correction measures may include claim withdrawal, language narrowing, public-safe clarification, public authority reference removal, logo or mark removal, public listing correction, report correction, handoff suspension, recipient notice, public authority notice where appropriate, supersession, and archive notation.

**22.2.10.4** Urgent correction shall occur where delay may create public reliance, procurement advantage, public finance reliance, regulatory confusion, public warning confusion, emergency confusion, market confusion, reputational misuse, or execution implication.

**22.2.10.5** Correction shall preserve confidentiality and shall not disclose public authority-sensitive information unnecessarily.

**22.2.10.6** Public authority overclaim corrections shall be linked to the relevant claims register, public-safe reporting register, correction register, and source record.

**22.2.10.7** Public Authority Overclaim Correction records shall themselves be correctionable. If a correction is incomplete, inaccurate, unsafe, publicized beyond permission, or creates a new public authority overclaim, the correction record shall be corrected, restricted, superseded, publicly clarified where necessary, or archived.

***

### 22.3 Finance and Insurance Boundaries

#### 22.3.1 No Investment Advice

**22.3.1.1** **No Investment Advice** shall mean that no Nexus-related participation, finance-readiness contribution, capital-reader participation, National Investors Council participation, GRA-aligned readiness activity, Nexus Universe capital-reader room, AEP Passport finance-layer input, Nexus Rail finance-readiness input, Docket item, Grid input, National Model, Regional Cluster Program Plan, public-safe report, handoff-readiness record, National Consortium Company interface, Project SPV interface, sponsor role, or partner role shall be treated as investment advice.

**22.3.1.2** Nexus-related finance-readiness activity may identify readability questions, diligence gaps, dependencies, risk-to-capital translation issues, SPV-readiness questions, insurance-readiness questions, donor relevance questions, development-readiness questions, and public finance relevance questions, but shall not recommend purchase, sale, holding, financing, investment, divestment, allocation, valuation, risk-taking, or transaction participation.

**22.3.1.3** Capital-reader participation shall be no-reliance, non-advisory, non-solicitation, non-placement, non-underwriting, non-rating, non-guarantee, non-transactional, non-fiduciary, and non-executing.

**22.3.1.4** Any investment decision shall be made outside the public-good stack by competent actors using independent legal, financial, tax, accounting, technical, environmental, social, procurement, public authority, safeguard, community, Indigenous where applicable, data, cyber, and project diligence.

**22.3.1.5** Public-safe materials shall avoid investment recommendation language.

**22.3.1.6** Investment-related language shall be reviewed before external use.

**22.3.1.7** Investment advice overclaims shall be corrected. If Nexus materials are used or interpreted as investment advice, they shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.3.2 No Financial Advice

**22.3.2.1** **No Financial Advice** shall mean that no Nexus finance-readiness, capital-readability, insurance-readiness, donor relevance, development-readiness, public finance relevance, disaster-risk finance, diligence-gap, SPV-readiness, AEP Passport finance-layer, Nexus Rail finance-readiness, Docket, Grid, public-safe reporting, handoff, National Consortium Company interface, or Project SPV interface activity shall be treated as financial advice.

**22.3.2.2** Nexus-related materials shall not advise on financing structure, capital stack, debt, equity, grants, guarantees, hedging, insurance, valuation, investment suitability, risk-return, credit, underwriting, tax, accounting, securities, or transaction terms unless a separate competent lawful advisory engagement outside the public-good stack exists.

**22.3.2.3** Finance-readiness materials may describe dependencies and questions, but shall not tell any person to finance, fund, insure, invest in, guarantee, structure, acquire, sell, hold, or transact.

**22.3.2.4** Recipients shall be responsible for independent financial advice where required.

**22.3.2.5** Finance-readiness outputs shall carry no-reliance language where externally circulated.

**22.3.2.6** Financial language shall be reviewed for regulated-perimeter discipline.

**22.3.2.7** Financial advice overclaims shall be corrected. If Nexus materials are used as financial advice, they shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.3.3 No Insurance Advice

**22.3.3.1** **No Insurance Advice** shall mean that no Nexus insurance-readiness, risk-transfer, disaster-risk finance, capital-reader, National Investors Council, GRA-aligned readiness, Nexus Universe insurance-readiness room, AEP Passport finance-layer, Nexus Rail finance-readiness, Docket, Grid, public-safe reporting, handoff, National Consortium Company interface, or Project SPV interface activity shall be treated as insurance advice.

**22.3.3.2** Nexus may identify insurance-readiness questions, risk-transfer dependencies, data needs, underwriting-relevant gaps, resilience questions, and risk-to-capital translation issues, but shall not advise on insurance purchase, coverage, pricing, underwriting, insurability, risk acceptance, policy terms, reinsurance, claims, brokerage, placement, or guarantee.

**22.3.3.3** Insurer, reinsurer, broker, or risk-transfer actor participation shall not imply insurance approval, underwriting appetite, coverage availability, premium terms, risk acceptance, guarantee, or insurability.

**22.3.3.4** Any insurance decision shall occur outside the public-good stack through competent insurance actors and lawful processes.

**22.3.3.5** Insurance-readiness materials shall include no-reliance and non-placement language where externally circulated.

**22.3.3.6** Insurance language shall be reviewed for regulated insurance and market-conduct risk.

**22.3.3.7** Insurance advice overclaims shall be corrected. If Nexus materials are used as insurance advice or insurance approval, the relevant materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.3.4 No Securities Offering

**22.3.4.1** **No Securities Offering** shall mean that no Nexus-related record, finance-readiness note, capital-reader room, National Investors Council discussion, GRA-aligned readiness activity, Nexus Universe session, AEP Passport finance-layer input, Nexus Rail finance-readiness input, Docket item, Grid input, National Model, Regional Cluster Program Plan, public-safe report, handoff-readiness record, National Consortium Company interface, Project SPV interface, deck, publication, sponsor material, provider material, or public-safe communication shall constitute an offer, solicitation, invitation, placement, recommendation, marketing, promotion, sale, purchase, subscription, or distribution of securities or investment products.

**22.3.4.2** Any securities offering, if ever undertaken, shall occur outside the public-good stack through competent lawful actors, with appropriate legal, regulatory, disclosure, market-conduct, investor-protection, tax, accounting, financial, and jurisdictional controls.

**22.3.4.3** Nexus materials shall not include offering terms, subscription invitations, investor calls to action, return projections, investment suitability claims, investment recommendations, valuations, ratings, commitments, or transaction instructions.

**22.3.4.4** Public-safe reports shall not be used as offering documents, private placement memoranda, investment teasers, term sheets, prospectuses, offering circulars, information memoranda, rating materials, or transaction documents.

**22.3.4.5** Capital-reader rooms shall not be transaction rooms by default.

**22.3.4.6** Securities-sensitive language shall be reviewed before circulation.

**22.3.4.7** Securities offering overclaims shall be corrected. If Nexus materials are used or interpreted as an offering or solicitation, the materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.3.5 No Capital Solicitation

**22.3.5.1** **No Capital Solicitation** shall mean that no Nexus-related activity shall solicit capital, investment, debt, equity, grants, insurance, guarantees, donor funding, development finance, public finance, or other financial commitments unless a separate competent lawful process outside the public-good stack expressly authorizes such solicitation.

**22.3.5.2** Nexus finance-readiness may improve readability and identify diligence gaps, but shall not ask capital actors to invest, commit, underwrite, insure, donate, lend, guarantee, fund, or allocate.

**22.3.5.3** National Investors Council participation, capital-reader room participation, finance-readiness contribution, Nexus Universe visibility, AEP Passport finance-layer discussion, Nexus Rail finance-readiness input, Docket input, Grid input, and handoff-readiness shall not be used to solicit capital.

**22.3.5.4** Public-safe materials shall avoid language that creates investment urgency, investment opportunity framing, exclusive access, priority allocation, capital commitment implication, or transaction momentum.

**22.3.5.5** Any lawful capital solicitation shall be separate from public-good records and shall comply with all applicable legal, regulatory, market-conduct, disclosure, tax, accounting, investor-protection, donor, development, public finance, and procurement requirements.

**22.3.5.6** Capital-solicitation language shall be reviewed before use.

**22.3.5.7** Capital solicitation overclaims shall be corrected. If Nexus materials are used as solicitation, the relevant records, claims, public materials, and handoff materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.3.6 No Insurance Placement

**22.3.6.1** **No Insurance Placement** shall mean that no Nexus-related insurance-readiness activity, disaster-risk finance discussion, capital-reader room, National Investors Council participation, GRA-aligned readiness activity, Nexus Universe insurance-readiness room, AEP Passport finance-layer input, Nexus Rail finance-readiness input, Docket item, Grid input, public-safe report, handoff-readiness record, National Consortium Company interface, or Project SPV interface shall constitute brokerage, placement, underwriting, reinsurance placement, policy issuance, risk acceptance, insurance arrangement, or insurance distribution.

**22.3.6.2** Nexus may support insurance-readiness literacy and dependency mapping, but shall not place, broker, underwrite, issue, arrange, bind, price, guarantee, or recommend insurance.

**22.3.6.3** Participation by insurers, reinsurers, brokers, risk-transfer actors, donors, or development actors shall not imply insurance placement or approval.

**22.3.6.4** Insurance placement, if pursued, shall occur outside the public-good stack through competent lawful insurance actors and processes.

**22.3.6.5** Insurance-related materials shall include non-placement language where needed.

**22.3.6.6** Insurance placement language shall be reviewed before external use.

**22.3.6.7** Insurance placement overclaims shall be corrected. If Nexus materials are used or interpreted as placement, the relevant materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.3.7 No Bankability, Financeability, or Insurability Determination

**22.3.7.1** **No Bankability, Financeability, or Insurability Determination** shall mean that no Nexus record, finance-readiness note, capital-reader contribution, National Investors Council output, insurance-readiness note, donor relevance note, development-readiness note, public finance relevance note, SPV-readiness input, AEP Passport finance-layer input, Nexus Rail finance-readiness input, Docket item, Grid input, National Model, Regional Cluster Program Plan, public-safe report, handoff-readiness record, National Consortium Company interface, or Project SPV interface shall determine that a project, pathway, system, portfolio, provider, National Consortium Company, Project SPV, or opportunity is bankable, financeable, investable, insurable, underwritable, fundable, de-risked for capital, or transaction-ready.

**22.3.7.2** Nexus finance-readiness may identify conditions that a competent actor may later consider in separate diligence, but shall not make the determination.

**22.3.7.3** Bankability, financeability, or insurability may be claimed only where a competent lawful finance, insurance, public finance, donor, development, or project process has separately issued the relevant determination and permitted the exact claim.

**22.3.7.4** Capital-reader participation shall not be described as determination, appetite, approval, or commitment.

**22.3.7.5** Public materials shall use “readiness,” “readability,” “dependency,” “question,” or “gap” language only where supported by record and shall avoid status language.

**22.3.7.6** Determination-like language shall be reviewed before use.

**22.3.7.7** Bankability, financeability, or insurability overclaims shall be corrected. If Nexus materials are used as determinations, the relevant record, claim, report, handoff, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.3.8 No Public Finance Approval

**22.3.8.1** **No Public Finance Approval** shall mean that no Nexus-related public finance relevance note, donor relevance note, development-readiness note, finance-readiness record, capital-reader room, National Investors Council participation, Nexus Universe session, AEP Passport finance-layer input, Nexus Rail finance-readiness input, Docket item, Grid input, public-safe report, National Model, Regional Cluster Program Plan, handoff-readiness record, National Consortium Company interface, or Project SPV interface shall be treated as public finance approval.

**22.3.8.2** Public finance approval may be claimed only where a competent public finance body has separately and lawfully issued the relevant approval, allocation, award, guarantee, or commitment and permitted the claim.

**22.3.8.3** Public finance relevance shall not imply allocation. Public finance reader participation shall not imply approval. Government Portfolio showcase preparation shall not imply public funding.

**22.3.8.4** Any public finance process shall remain outside the public-good stack and subject to its own law, policy, governance, eligibility, diligence, procurement, transparency, and accountability requirements.

**22.3.8.5** Public finance language shall include no-reliance and public authority boundary language where needed.

**22.3.8.6** Public finance claims shall be reviewed before external use.

**22.3.8.7** Public finance approval overclaims shall be corrected. If public finance approval is implied without competent record, the relevant claim and materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.3.9 No Donor or Philanthropic Commitment

**22.3.9.1** **No Donor or Philanthropic Commitment** shall mean that no donor relevance note, philanthropic discussion, development-readiness discussion, public-good contribution, sponsorship, Nexus Universe participation, capital-reader room, National Investors Council participation, AEP Passport finance-layer input, Nexus Rail finance-readiness input, Docket item, Grid input, public-safe report, National Model, Regional Cluster Program Plan, handoff-readiness record, National Consortium Company interface, or Project SPV interface shall imply donor, foundation, philanthropic, development, or grant commitment.

**22.3.9.2** Donor or philanthropic commitment may be claimed only where the relevant donor, foundation, philanthropic institution, development actor, or competent body has separately issued a lawful commitment, grant, award, allocation, or approval and permitted the claim.

**22.3.9.3** Donor participation, donor room attendance, donor relevance discussion, public-safe reporting reference, Nexus Universe visibility, or handoff-readiness shall not be described as donor support or commitment.

**22.3.9.4** Public-good contribution by a donor or philanthropic actor shall be distinguished from project funding, grant approval, or institutional endorsement.

**22.3.9.5** Donor-related language shall preserve no-reliance, non-solicitation, public authority boundary, safeguard, and correction discipline.

**22.3.9.6** Donor or philanthropic language shall be reviewed before external use.

**22.3.9.7** Donor or philanthropic commitment overclaims shall be corrected. If commitment is implied without competent record, the relevant claim and materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.3.10 Correction of Finance Overclaim

**22.3.10.1** **Correction of Finance Overclaim** shall be the mandatory process through which investment advice, financial advice, insurance advice, securities offering, capital solicitation, insurance placement, bankability, financeability, insurability, public finance approval, donor commitment, philanthropic commitment, transaction readiness, capital commitment, underwriting appetite, insurance approval, guarantee, valuation, rating, or other finance-related overclaim is corrected.

**22.3.10.2** Finance overclaim may arise in Nexus Universe materials, finance-readiness notes, capital-reader room summaries, National Investors Council materials, GRA-aligned materials, AEP Passport finance-layer references, Nexus Rail finance-readiness references, Docket or Grid summaries, public-safe reports, National Model summaries, Regional Cluster Program Plan summaries, sponsor materials, provider materials, investor materials, donor materials, public finance materials, handoff records, National Consortium Company materials, Project SPV materials, or media materials.

**22.3.10.3** Correction measures may include claim withdrawal, no-reliance clarification, language narrowing, public-safe report correction, investor-material correction, sponsor-material correction, provider-material correction, donor-material correction, public finance-material correction, handoff restriction, recipient notice, publication withdrawal, supersession, and archive notation.

**22.3.10.4** Urgent correction shall occur where delay may create investor reliance, market confusion, insurance reliance, donor reliance, public finance reliance, procurement advantage, sponsor capture, provider validation, public authority confusion, project approval implication, or execution implication.

**22.3.10.5** Correction shall not provide financial, legal, insurance, tax, accounting, or investment advice while correcting the overclaim.

**22.3.10.6** Finance overclaim corrections shall be linked to the relevant claims register, public-safe reporting register, correction register, finance-readiness record, and archive entry.

**22.3.10.7** Finance Overclaim Correction records shall themselves be correctionable. If a correction is incomplete, inaccurate, unsafe, creates new reliance, or is publicized beyond permission, the correction record shall be corrected, restricted, superseded, publicly clarified where necessary, or archived.

***

### 22.4 Technical, Provider, and Project Boundaries

#### 22.4.1 No Provider Validation

**22.4.1.1** **No Provider Validation** shall mean that no Nexus participation, technical contribution, public-good software contribution, Working Group participation, Competence Cell participation, provider-neutral capability mapping, Nexus Universe demonstration, AEP Passport candidate input, Nexus Rail input, Docket item, Grid input, public-safe report, National Model reference, Regional Cluster Program Plan reference, sponsor support, partnership, handoff-readiness, National Consortium Company interface, or Project SPV interface shall validate, approve, endorse, recommend, rank, qualify, certify, or select a provider.

**22.4.1.2** Providers include vendors, operators, hosts, platforms, manufacturers, integrators, technology actors, infrastructure actors, consultants, professional firms, enterprise participants, public-good software contributors, technical partners, and provider candidates.

**22.4.1.3** Provider validation may be claimed only where a separate competent lawful provider qualification, procurement, contracting, certification, or approval process has issued the exact status and permitted the claim.

**22.4.1.4** Provider-neutral capability mapping may identify capabilities, gaps, dependencies, interoperability issues, safeguards, and readiness questions, but shall not validate.

**22.4.1.5** Provider participation shall be described as contribution-only, candidate-only, technical input, demonstration, or capability input within the record.

**22.4.1.6** Provider language shall be reviewed for procurement-neutrality and competition risk.

**22.4.1.7** Provider validation overclaims shall be corrected. If provider participation is used as validation, the relevant record, claim, listing, report, handoff, and downstream materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.4.2 No Preferred-Provider Status

**22.4.2.1** **No Preferred-Provider Status** shall mean that no provider shall be treated as preferred, recommended, shortlisted, prequalified, first-ranked, priority, approved, strategic supplier, default implementer, default operator, default host, default platform, default contractor, or preferred enterprise actor by reason of Nexus participation, sponsorship, hosting, technical contribution, public-good software contribution, Nexus Universe visibility, Working Group participation, Competence Cell participation, AEP Passport input, Nexus Rail input, Docket input, Grid input, public-safe reporting, or handoff-readiness.

**22.4.2.2** Preferred-provider status may be claimed only where a separate competent lawful procurement, contracting, qualification, or selection process creates that status and permits the claim.

**22.4.2.3** Sponsorship shall not buy preferred-provider status. Hosting shall not create preferred-provider status. Technical contribution shall not create preferred-provider status. Public-good software contribution shall not create preferred-provider status.

**22.4.2.4** Provider lists, capability maps, room rosters, sponsor lists, partner lists, public-safe reports, National Model references, Regional Cluster Program Plan references, and Nexus Universe materials shall not be ordered, described, or framed in a way that implies preference unless the record supports that exact status.

**22.4.2.5** National Consortium Companies and Project SPVs shall conduct any provider selection through separate lawful processes.

**22.4.2.6** Preferred-provider language shall be reviewed before use.

**22.4.2.7** Preferred-provider overclaims shall be corrected. If preferred status is implied without lawful record, the relevant claim, list, report, handoff, Company material, SPV material, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.4.3 No Procurement Eligibility

**22.4.3.1** **No Procurement Eligibility** shall mean that Nexus participation, subscription, sponsorship, partnership, provider-candidate status, technical contribution, public-good software contribution, Working Group participation, Competence Cell participation, Nexus Universe visibility, public authority learning-room participation, provider-neutral mapping, AEP Passport input, Nexus Rail input, Docket input, Grid input, National Model reference, Regional Cluster Program Plan reference, handoff-readiness, National Consortium Company interface, or Project SPV interface shall not create eligibility to bid, eligibility to contract, prequalification, shortlist status, procurement access, procurement advantage, procurement award, procurement recommendation, or public buyer approval.

**22.4.3.2** Procurement eligibility may be claimed only where a competent procurement body or lawful procurement process has separately created that status and permitted the exact claim.

**22.4.3.3** Public authority learning and procurement-neutral rooms shall not be described as procurement access.

**22.4.3.4** Provider-candidate records shall state candidate status only and shall not imply eligibility.

**22.4.3.5** Public-good records shall not replace due diligence, competition, procurement law, conflict review, anti-corruption controls, contracting, or public authority requirements.

**22.4.3.6** Procurement eligibility language shall be reviewed before external use.

**22.4.3.7** Procurement eligibility overclaims shall be corrected. If eligibility is implied without lawful record, the claim and affected materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.4.4 No Certification

**22.4.4.1** **No Certification** shall mean that Nexus participation, technical evidence, research contribution, public-good software contribution, benchmark input, system card, model card, method record, observability record, Nexus Universe presentation, AEP Passport candidate input, Nexus Rail routeability input, Docket item, Grid input, National Model, Regional Cluster Program Plan, public-safe report, handoff-readiness, sponsor role, provider role, National Consortium Company interface, or Project SPV interface shall not certify any person, institution, product, service, provider, project, system, method, technology, maturity level, or outcome.

**22.4.4.2** Certification may be claimed only where a competent authorized certification process has issued the relevant certification and permitted the exact claim.

**22.4.4.3** Words such as certified, accredited, verified, validated, assured, approved, guaranteed, authorized, cleared, compliant, or equivalent terms shall not be used unless supported by competent record.

**22.4.4.4** Public-safe reporting may describe evidence, methods, inputs, candidates, dependencies, and limitations without certifying.

**22.4.4.5** Technical contribution shall not be represented as certification.

**22.4.4.6** Certification language shall be reviewed before use.

**22.4.4.7** Certification overclaims shall be corrected. If certification is implied without competent certification record, the relevant claim and materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.4.5 No Standards Conformance

**22.4.5.1** **No Standards Conformance** shall mean that no person, institution, product, service, system, provider, project, method, record, National Model, Regional Cluster Program Plan, AEP Passport candidate, Nexus Rail candidate, Docket item, Grid input, public-safe report, National Consortium Company, or Project SPV shall claim conformance to a standard, protocol, specification, regulatory standard, procurement standard, technical standard, safety standard, maturity standard, or Nexus standard by reason of Nexus participation or records.

**22.4.5.2** Standards conformance may be claimed only where a competent standards authority or authorized conformance process has issued the relevant conformance record and permitted the exact claim.

**22.4.5.3** Standards-interface activity, common rail vocabulary, ontology alignment, method records, evidence records, public-good software baselines, AEP Passport candidate layers, Nexus Rail routeability inputs, Docket items, Grid inputs, or public-safe reports shall not be described as conformance by default.

**22.4.5.4** Claims that a system is Nexus-compliant, Nexus-conformant, Nexus-standard, protocol-approved, standards-ready, or standard-certified are prohibited unless expressly supported.

**22.4.5.5** Public-safe reports may describe alignment questions, standards interfaces, interoperability issues, and dependencies without claiming conformance.

**22.4.5.6** Standards-conformance language shall be reviewed before use.

**22.4.5.7** Standards-conformance overclaims shall be corrected. If conformance is implied without competent record, the relevant claim and materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.4.6 No Nexus-Ready Status

**22.4.6.1** **No Nexus-Ready Status** shall mean that no person, institution, project, provider, product, service, system, National Model, Regional Cluster Program Plan, AEP Passport candidate, Nexus Rail candidate, National Consortium Company, Project SPV, node, portfolio, or pathway shall claim to be Nexus-ready, Nexus-approved, Nexus-qualified, Nexus-compatible, Nexus-validated, Nexus-cleared, Nexus-endorsed, or ready for Nexus implementation by reason of participation, contribution, visibility, candidate status, or handoff-readiness.

**22.4.6.2** Nexus-ready status may be claimed only where a competent Nexus readiness process has been separately established, the relevant readiness record has been issued, and the exact claim is permitted.

**22.4.6.3** Participation in Nexus, Nexus Universe, AEP Passport candidate preparation, Nexus Rail routeability, Docket input, Grid input, Working Group participation, Competence Cell participation, National Model preparation, Regional Cluster Program Plan preparation, public-safe reporting, or handoff-readiness shall not be described as Nexus-ready status.

**22.4.6.4** Readiness language shall be limited to recorded readiness questions, dependencies, candidate status, or handoff-readiness within the record and shall not imply approval.

**22.4.6.5** Nexus-ready vocabulary shall be treated as high-risk claim language.

**22.4.6.6** Public-safe reporting shall avoid Nexus-ready language unless expressly permitted.

**22.4.6.7** Nexus-ready overclaims shall be corrected. If Nexus-ready status is implied without competent record, the relevant claim and materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.4.7 No AEP Passport Status by Participation

**22.4.7.1** **No AEP Passport Status by Participation** shall mean that participation in Nexus, Nexus Universe, AEP Passport discussions, technical rooms, safeguard rooms, capital-reader rooms, public authority rooms, Working Groups, Competence Cells, National Models, Regional Cluster Program Plans, public-safe reports, Docket, Grid, Nexus Rail, sponsor pathways, provider pathways, National Consortium Company interfaces, or Project SPV interfaces shall not confer AEP Passport status.

**22.4.7.2** AEP Passport status may be claimed only where a competent AEP Passport process has issued the status and permitted the exact claim.

**22.4.7.3** Candidate records, layer inputs, Proof Receipt inputs where authorized, public-safe references, routeability discussions, handoff-readiness notes, and Nexus Universe sessions shall not be described as AEP Passport status.

**22.4.7.4** A participant shall not imply that its organization, product, service, project, system, node, portfolio, or pathway is AEP Passported because it participated in an AEP-related process.

**22.4.7.5** AEP Passport-related claims shall distinguish candidate, input, discussion, Proof Receipt reference, issued status, restricted status, corrected status, withdrawn status, superseded status, and archive status.

**22.4.7.6** AEP Passport language shall be reviewed before publication or external use.

**22.4.7.7** AEP Passport participation overclaims shall be corrected. If participation is used as AEP Passport status, the relevant claim, record, report, handoff, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.4.8 No Nexus Node Approval

**22.4.8.1** **No Nexus Node Approval** shall mean that hosting, anchoring, sponsorship, regional headquarters hosting, national desk hosting, Nexus Universe participation, Nexus Core support, observability contribution, technical contribution, AEP Passport candidate input, Nexus Rail routeability, Docket input, Grid input, public-safe reporting, handoff-readiness, National Consortium Company interface, or Project SPV interface shall not approve any person, institution, location, facility, city, region, country, system, project, provider, host, operator, observability environment, technical environment, or platform as a Nexus Node.

**22.4.8.2** Nexus Node status may be claimed only where a competent Nexus Node process has issued the relevant status and the claim is permitted by the applicable record.

**22.4.8.3** A facility, platform, country, region, host, provider, public authority, university, company, or community shall not claim Node status by reason of supporting Nexus-related activities.

**22.4.8.4** Public-safe language shall distinguish host, venue, platform, observability contributor, node candidate where authorized, and issued Node status.

**22.4.8.5** Node-related claims shall preserve public authority, data, cyber, infrastructure, security, safeguard, consent, provider-neutrality, finance, and handoff boundaries.

**22.4.8.6** Nexus Node language shall be reviewed before use.

**22.4.8.7** Nexus Node approval overclaims shall be corrected. If Node status is implied without competent record, the relevant claim and materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.4.9 No Project Authorization

**22.4.9.1** **No Project Authorization** shall mean that no Nexus participation, record, National Model, Regional Cluster Program Plan, Nexus Universe output, AEP Passport candidate, Nexus Rail candidate, Docket item, Grid input, public-safe report, safeguard record, finance-readiness note, public authority dependency note, provider-neutral capability map, handoff-readiness record, National Consortium Company interface, or Project SPV interface shall authorize a project, portfolio, corridor, system, node, deployment, construction, procurement, financing, insurance, operation, or implementation.

**22.4.9.2** Project authorization may occur only through separate competent lawful actors and processes, including public authority approvals, enterprise governance, procurement processes, finance processes, insurance processes, community and Indigenous processes where applicable, environmental processes, data and cyber processes, contracting, National Consortium Company decisions, Project SPV decisions, or other lawful project processes.

**22.4.9.3** Handoff-readiness shall not be project authorization. SPV-readiness shall not be project authorization. Finance-readiness shall not be project authorization. AEP Passport input shall not be project authorization. Nexus Rail routeability shall not be project authorization.

**22.4.9.4** National Consortium Companies and Project SPVs shall not use public-good records as project approvals.

**22.4.9.5** Public-safe reporting may describe project-related themes, dependencies, candidate pathways, and handoff-readiness conditions without implying authorization.

**22.4.9.6** Project-related language shall be reviewed for public authority, finance, procurement, provider, safeguard, consent, environmental, data, cyber, and execution boundaries.

**22.4.9.7** Project authorization overclaims shall be corrected. If project authorization is implied without competent record, the relevant claim, record, report, handoff, Company material, SPV material, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.4.10 No Execution Authority

**22.4.10.1** **No Execution Authority** shall mean that the Federation, GCRI, GRF, GRA, the Global Nexus Consortium, a Regional Headquarters Consortium, a National Nexus Consortium, Central Nexus Bureau, Nexus Universe, National Councils, Helix Councils, Working Groups, Competence Cells, public-safe reporting pathways, AEP Passport pathways, Nexus Rail pathways, Docket pathways, Grid pathways, sponsors, partners, public authority learners, capital readers, media contributors, safeguard contributors, or other public-good stack bodies shall not execute, command, procure, finance, insure, build, deploy, operate, contract, direct, approve, warn, respond, authorize, consent, or implement by reason of their Nexus roles.

**22.4.10.2** Execution authority, where it exists, shall belong only to separate competent lawful actors, including public authorities, enterprise actors, National Consortium Companies, Project SPVs, providers, operators, contractors, financiers, insurers, donors, development actors, public finance actors, procurement bodies, community processes, Indigenous governance processes where applicable, environmental processes, data and cyber processes, or other lawful implementation actors.

**22.4.10.3** The public-good stack may form records, evidence, methods, observability, public-safe reports, learning rooms, readiness notes, safeguard records, claims controls, correction records, and handoff-readiness records, but shall not execute.

**22.4.10.4** Nexus Universe live operation shall not be project operation. Nexus Core build shall not be implementation. Public-safe reporting shall not be command. Handoff shall not be execution.

**22.4.10.5** Public communications shall include non-execution language where needed.

**22.4.10.6** Downstream execution shall remain subject to separate lawful authority, diligence, governance, contracts, safeguards, public authority approvals, finance, insurance, procurement, community and Indigenous processes where applicable, and liability.

**22.4.10.7** Execution authority overclaims shall be corrected. If public-good bodies are described as executing or authorizing execution, the relevant records, claims, reports, handoffs, enterprise materials, and archive entries shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

### 22.5 Community and Safeguard Boundaries

#### 22.5.1 No Community Consent

**22.5.1.1** **No Community Consent** shall mean that participation by communities, affected stakeholders, civil society actors, rights-aware organizations, diaspora actors, youth actors, accessibility advocates, environmental and social safeguard contributors, humanitarian actors, local institutions, public-interest researchers, place-based legitimacy contributors, or other community participants shall not constitute consent, approval, endorsement, authorization, social license, local approval, project approval, or execution authority.

**22.5.1.2** Community consent may be claimed only where a competent and lawful community process, rights-holder process, local authorization process, or applicable governance process has produced the exact consent record and permitted the claim.

**22.5.1.3** Attendance, contribution, public-safe listing, Nexus Universe participation, safeguard-room input, National Model input, Regional Cluster Program Plan input, AEP Passport safeguard input, Nexus Rail safeguard condition, Docket input, Grid input, public-safe reporting input, or handoff restriction shall not be described as consent.

**22.5.1.4** No participant shall be treated as speaking for all affected communities unless a separate lawful record supports that capacity.

**22.5.1.5** Public materials shall use consent-boundary language where community input is described.

**22.5.1.6** Community-related claims shall be reviewed before external use.

**22.5.1.7** Community consent overclaims shall be corrected. If community participation is used as consent, approval, social license, project authorization, or execution authority, the relevant record, claim, report, handoff, enterprise material, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.5.2 No Indigenous Consent

**22.5.2.1** **No Indigenous Consent** shall mean that participation by Indigenous peoples, Tribal actors, Indigenous governance bodies, traditional authorities, Indigenous knowledge holders, protected knowledge holders, Indigenous organizations, or Indigenous participants shall not constitute Indigenous consent, approval, authorization, endorsement, rights waiver, land approval, cultural approval, protected knowledge authorization, Indigenous data authorization, project approval, or execution authority unless a separate lawful and protocol-consistent record supports the exact claim.

**22.5.2.2** Indigenous consent may be claimed only where the relevant competent Indigenous governance, rights-holder, legal, protocol, or authorization process has produced the exact record and permitted the claim.

**22.5.2.3** Indigenous attendance, contribution, public-safe listing, Nexus Universe participation, safeguard-room input, National Model input, Regional Cluster Program Plan input, AEP Passport safeguard input, Nexus Rail safeguard condition, Docket input, Grid input, public-safe reporting input, or handoff restriction shall not be described as consent.

**22.5.2.4** No individual or organization shall be treated as speaking for an Indigenous people, nation, community, Tribal actor, rights-holder group, or protected knowledge holder unless a separate lawful and protocol-consistent record supports that representation.

**22.5.2.5** Indigenous-related public materials shall avoid simplifying protocol, rights, representation, consent, knowledge, data, land, water, cultural, or governance conditions into generic stakeholder language.

**22.5.2.6** Indigenous-related claims shall receive heightened review.

**22.5.2.7** Indigenous consent overclaims shall be corrected. If Indigenous participation is used as consent, approval, FPIC satisfaction, protected knowledge authorization, land access, cultural approval, project authorization, or execution authority, the relevant record, claim, report, handoff, enterprise material, and archive entry shall be corrected, restricted, withdrawn, deleted where required, superseded, publicly clarified where necessary, or archived under protective conditions.

***

#### 22.5.3 No FPIC Satisfaction by Participation

**22.5.3.1** **No FPIC Satisfaction by Participation** shall mean that participation by Indigenous peoples, Tribal actors, Indigenous governance bodies, traditional authorities, Indigenous knowledge holders, protected knowledge holders, or Indigenous participants in any Nexus-related pathway shall not satisfy Free, Prior and Informed Consent requirements where such requirements apply.

**22.5.3.2** FPIC satisfaction may be claimed only where a competent and lawful FPIC process has been completed according to applicable law, protocol, governance authority, and record requirements, and the resulting record permits the exact claim.

**22.5.3.3** Nexus participation, safeguard-room input, public-safe reporting, Nexus Universe presence, National Model input, Regional Cluster Program Plan input, AEP Passport safeguard input, Nexus Rail safeguard condition, Docket input, Grid input, or handoff discussion shall not be described as FPIC.

**22.5.3.4** FPIC-related dependencies shall be identified as unresolved unless separately and lawfully addressed.

**22.5.3.5** Public-safe materials shall not use language that implies FPIC progress beyond the record.

**22.5.3.6** FPIC language shall be subject to heightened legal, protocol, safeguard, and public-safe review.

**22.5.3.7** FPIC overclaims shall be corrected. If participation is used to imply FPIC satisfaction, consultation completion, accommodation completion, or rights waiver, the relevant record, claim, report, handoff, enterprise material, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived under protective conditions.

***

#### 22.5.4 No Social License

**22.5.4.1** **No Social License** shall mean that no Nexus participation, community contribution, Indigenous contribution where applicable, civil society participation, diaspora input, youth input, accessibility input, public-safe reporting, Nexus Universe visibility, safeguard-room participation, National Model reference, Regional Cluster Program Plan reference, AEP Passport safeguard input, Nexus Rail safeguard condition, Docket input, Grid input, handoff-readiness record, National Consortium Company interface, or Project SPV interface shall be described as social license.

**22.5.4.2** Social license language is prohibited unless a competent lawful and context-specific record supports the exact claim and the claim is permitted by that record.

**22.5.4.3** Public-good legitimacy, stakeholder participation, safeguard input, place-based insight, and public-safe reporting shall not be converted into social license.

**22.5.4.4** Sponsor, provider, investor, public authority, National Consortium Company, or Project SPV materials shall not use community or Indigenous presence to imply social license.

**22.5.4.5** Public-safe reports may describe safeguard themes and unresolved legitimacy questions without claiming social license.

**22.5.4.6** Social-license language shall be reviewed and generally avoided.

**22.5.4.7** Social license overclaims shall be corrected. If social license is implied without competent record, the relevant claim and materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.5.5 No Protected Knowledge Authorization

**22.5.5.1** **No Protected Knowledge Authorization** shall mean that participation in Nexus shall not authorize collection, recording, translation, mapping, digitization, modeling, AI use, observability use, digital twin use, publication, transfer, commercialization, handoff, or downstream use of Protected Knowledge.

**22.5.5.2** Protected Knowledge authorization may exist only where a specific lawful, protocol-consistent, source-approved, purpose-limited, record-based authorization permits the exact use.

**22.5.5.3** Community participation, Indigenous participation where applicable, safeguard-room input, public-safe reporting input, Nexus Universe presence, National Model input, Regional Cluster Program Plan input, AEP Passport safeguard input, Nexus Rail safeguard condition, Docket input, Grid input, or handoff discussion shall not authorize use of Protected Knowledge.

**22.5.5.4** Protected Knowledge shall not be inferred from context and then used. It shall not be extracted from participation, stories, maps, examples, images, recordings, oral contributions, chat logs, documents, dashboards, or public-stage statements beyond the record.

**22.5.5.5** Protected Knowledge restrictions shall travel with records and handoffs.

**22.5.5.6** Protected Knowledge language and use shall receive heightened review.

**22.5.5.7** Protected Knowledge authorization overclaims shall be corrected. If Protected Knowledge is used beyond authority or participation is treated as authorization, the relevant record, data, material, model, map, report, handoff, enterprise record, and archive entry shall be corrected, restricted, withdrawn, deleted where required, superseded, publicly clarified where necessary, or archived under protective conditions.

***

#### 22.5.6 No Land, Site, Cultural, or Environmental Approval

**22.5.6.1** **No Land, Site, Cultural, or Environmental Approval** shall mean that no Nexus participation, community input, Indigenous input where applicable, safeguard record, National Model, Regional Cluster Program Plan, Nexus Universe output, AEP Passport input, Nexus Rail input, Docket item, Grid input, public-safe report, handoff-readiness record, National Consortium Company interface, Project SPV interface, sponsor role, provider role, or public authority learning record shall be treated as land approval, site access, cultural approval, heritage approval, environmental approval, environmental clearance, social approval, or rights-holder approval.

**22.5.6.2** Land, site, cultural, heritage, environmental, social, or rights-holder approval may be claimed only where the competent lawful authority, rights-holder process, Indigenous governance process where applicable, environmental process, land process, cultural process, or project process has issued the relevant approval and permitted the exact claim.

**22.5.6.3** Sensitive location records, community input, Indigenous input, protected knowledge cautions, environmental and social safeguard notes, or public-safe reporting shall not be described as approval.

**22.5.6.4** Project proponents, providers, sponsors, National Consortium Companies, and Project SPVs shall obtain required approvals through separate lawful processes.

**22.5.6.5** Public-safe materials shall preserve unresolved land, site, cultural, environmental, and social dependencies.

**22.5.6.6** Land, site, cultural, and environmental language shall be reviewed before external use.

**22.5.6.7** Land, site, cultural, or environmental approval overclaims shall be corrected. If approval is implied without competent record, the relevant claim, report, handoff, enterprise material, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.5.7 No Youth or Future-Generation Approval

**22.5.7.1** **No Youth or Future-Generation Approval** shall mean that participation by youth, youth groups, student groups, future-generation advocates, educators, researchers, community participants, civil society actors, or intergenerational public-interest contributors shall not be treated as approval by youth, future generations, students, young people, future residents, or affected future stakeholders.

**22.5.7.2** Youth or future-generation participation may support public-good learning, accessibility, intergenerational awareness, public-safe reporting, safeguard input, education, Nexus Universe participation, National Model input, Regional Cluster Program Plan input, Docket or Grid input, and correction, but shall not create consent, approval, endorsement, social license, project authorization, or execution authority.

**22.5.7.3** No person or institution shall claim to represent all youth or future generations unless a separate lawful and credible record supports the exact represented capacity, and even then such representation shall not substitute for lawful approvals or consent processes.

**22.5.7.4** Youth-related information shall be subject to heightened privacy, safety, accessibility, and public-safe reporting controls.

**22.5.7.5** Public-safe materials shall avoid symbolic use of youth participation to legitimize sponsors, providers, finance pathways, public authority actions, projects, or execution.

**22.5.7.6** Youth and future-generation language shall be reviewed before external use.

**22.5.7.7** Youth or future-generation approval overclaims shall be corrected. If youth participation is used as approval, legitimacy substitute, consent, project authorization, or execution authority, the relevant record and materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.5.8 Safeguard Input Is Not Clearance

**22.5.8.1** **Safeguard Input Is Not Clearance** shall mean that safeguard contribution, safeguard-room participation, community-risk input, Indigenous protocol input where applicable, protected knowledge caution, accessibility input, environmental and social safeguard note, humanitarian note, health-sensitive note, cyber-sensitive note, infrastructure-sensitive note, public-safe reporting input, AEP Passport safeguard input, Nexus Rail safeguard condition, Docket safeguard item, Grid safeguard input, handoff safeguard condition, National Consortium Company safeguard register, or Project SPV safeguard dependency record shall not clear, approve, authorize, certify, satisfy, or remove the underlying safeguard issue.

**22.5.8.2** Safeguard input may identify risks, conditions, dependencies, restrictions, and correction needs, but shall not determine that those risks have been resolved unless a competent lawful record supports that determination.

**22.5.8.3** Safeguard input shall not be treated as community consent, Indigenous consent, FPIC satisfaction, environmental approval, public authority approval, financeability, procurement status, provider validation, project authorization, or execution.

**22.5.8.4** Safeguard records shall preserve unresolved conditions and shall travel with records and handoffs.

**22.5.8.5** Public-safe reports may describe safeguard themes and unresolved issues without implying clearance.

**22.5.8.6** Safeguard-clearance language shall be reviewed and avoided unless supported by competent record.

**22.5.8.7** Safeguard clearance overclaims shall be corrected. If safeguard input is used as clearance, the relevant record, claim, report, handoff, enterprise material, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.5.9 Public-Safe Reporting Is Not Consent

**22.5.9.1** **Public-Safe Reporting Is Not Consent** shall mean that publication of a public-safe report, National Model summary, Regional Cluster Program Plan summary, Nexus Universe summary, AEP Passport reference, Nexus Rail reference, Docket summary, Grid summary, safeguard summary, correction notice, renewal notice, archive summary, dashboard summary, media statement, or public-stage material shall not create consent by any community, Indigenous people where applicable, rights-holder, public authority, provider, sponsor, capital actor, or downstream recipient.

**22.5.9.2** Public-safe reporting may describe participation, learning, evidence, safeguards, dependencies, corrections, unresolved issues, and public-good meaning, but shall not substitute for lawful consent, approval, authorization, consultation, accommodation, FPIC, protected knowledge authorization, land approval, cultural approval, environmental approval, or project authorization.

**22.5.9.3** A person or institution listed, described, or referenced in a public-safe report shall not be deemed to have consented to a project, policy, finance pathway, procurement pathway, provider selection, public authority action, or execution unless a separate lawful record supports that exact consent.

**22.5.9.4** Public-safe reports shall include consent-boundary language where community, Indigenous, safeguard, public authority, project, or handoff themes are discussed.

**22.5.9.5** Public-safe reporting shall not expose protected knowledge or sensitive community information in order to demonstrate participation.

**22.5.9.6** Public-safe reporting language shall be reviewed for consent overclaim before publication.

**22.5.9.7** Public-safe reporting consent overclaims shall be corrected. If a report is used as consent, the relevant report, claim, handoff, enterprise material, and archive entry shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 22.5.10 Correction of Safeguard Overclaim

**22.5.10.1** **Correction of Safeguard Overclaim** shall be the mandatory process through which any claim, record, report, Nexus Universe material, AEP Passport reference, Nexus Rail reference, Docket or Grid summary, National Model, Regional Cluster Program Plan, sponsor material, provider material, investor material, public authority material, handoff record, National Consortium Company material, Project SPV material, or archive entry is corrected where it implies community consent, Indigenous consent, FPIC satisfaction, social license, protected knowledge authorization, land approval, site approval, cultural approval, environmental approval, youth approval, future-generation approval, safeguard clearance, public-safe reporting consent, project authorization, or execution without competent support.

**22.5.10.2** Safeguard overclaim may be triggered by misuse of community participation, Indigenous participation where applicable, safeguard-room materials, protected knowledge references, public-safe reports, media materials, sponsor materials, provider materials, investor materials, public authority materials, handoff packages, Company materials, SPV materials, maps, dashboards, digital twins, images, quotes, attendance lists, or public-stage statements.

**22.5.10.3** Correction measures may include claim withdrawal, consent-boundary clarification, public-safe report correction, public listing correction, protected knowledge containment, takedown request, deletion where required, translation correction, map suppression, dashboard correction, AI-use restriction, handoff suspension, recipient notice, sponsor or provider restriction, enterprise-material correction, supersession, and archive notation.

**22.5.10.4** Urgent correction shall occur where delay may create community harm, Indigenous protocol harm where applicable, protected knowledge exposure, privacy harm, public authority confusion, finance reliance, procurement advantage, provider validation, project approval implication, public warning confusion, or execution implication.

**22.5.10.5** Correction shall not disclose additional protected, community-sensitive, Indigenous-sensitive, location-sensitive, security-sensitive, health-sensitive, humanitarian-sensitive, or confidential information.

**22.5.10.6** Safeguard overclaim corrections shall be linked to source records, safeguard records, claims registers, public-safe reporting registers, correction registers, handoff records, and archive entries.

**22.5.10.7** Safeguard Overclaim Correction records shall themselves be correctionable. If a correction is incomplete, inaccurate, unsafe, publicized beyond permission, or creates new safeguard overclaim, the correction record shall be corrected, restricted, superseded, publicly clarified where necessary, or archived.


---

# 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/charter/xxii.-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.