# XIX. CLAIMS

### 19. Claims, Communications, and Public-Safe Reporting

### 19.1 Federation Claims Principles

#### 19.1.1 Record Before Claim

**19.1.1.1** **Record Before Claim** shall be the controlling communications principle of the Nexus Consortium Federation. No person, institution, council, helix, working group, competence cell, sponsor, partner, host, provider, public authority learner, capital reader, media contributor, National Consortium Company, Project SPV, or other participant shall make, approve, publish, repeat, rely upon, or permit a Nexus-related claim unless the claim is grounded in a current controlling record.

**19.1.1.2** A controlling record shall identify the source pathway, record owner, version, date, role, scope, geography, term, publication class, permitted language, prohibited language, required limitations, public authority boundaries, finance boundaries, provider-neutrality conditions, sponsor restrictions, safeguard conditions, protected knowledge restrictions, data and cyber conditions where applicable, correction history, renewal status, and archive status.

**19.1.1.3** Claims shall not be made valid by repetition, prominence, public visibility, sponsor use, provider use, investor use, public authority reference, media reference, Nexus Universe stage presence, public-safe report circulation, inclusion in a deck, inclusion on a website, appearance in a register, archive presence, or passage of time. Validity shall arise only from the record.

**19.1.1.4** Where a claim is ambiguous, the most restrictive lawful reading shall apply. Ambiguity shall not be used to imply endorsement, approval, financeability, certification, procurement status, provider validation, public authority action, community consent, Indigenous consent, project authorization, Nexus-ready status, AEP Passport status, Nexus Node status, Docket resolution, Grid maturity approval, handoff approval, or execution authority.

**19.1.1.5** Claims shall preserve the difference between participation and endorsement, access and authority, support and control, contribution and validation, readiness and financeability, learning and public authority action, technical input and certification, safeguard input and consent, public-safe reporting and public warning, candidate status and approval, handoff and execution, and record maturity and downstream maturity.

**19.1.1.6** Any claim that relies on a corrected, withdrawn, superseded, restricted, or archived record shall identify that status or shall not be made.

**19.1.1.7** Claims made without a controlling record, or beyond the scope of a controlling record, shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.1.2 Participation Claim

**19.1.2.1** A **Participation Claim** shall be any statement that a person or institution participates in, has joined, contributes to, supports, attends, is listed in, has access to, is associated with, or is otherwise involved in a Nexus Consortium, National Council, Helix Council, Regional Headquarters Consortium, Global Nexus Consortium, Nexus Universe, Working Group, Competence Cell, AEP Passport pathway, Nexus Rail pathway, Docket pathway, Grid pathway, public-safe reporting pathway, or handoff-readiness pathway.

**19.1.2.2** A Participation Claim shall be permitted only where a current participation record supports the claim and identifies the participant’s role, capacity, level, geography, term, access rights, publication permissions, conflicts, claims limits, and correction status.

**19.1.2.3** Participation shall create standing and access only within the recorded scope. Participation shall not create governance authority, board appointment, endorsement, public authority approval, government support, procurement status, financeability, certification, provider validation, community consent, Indigenous consent, project authorization, Nexus-ready status, AEP Passport status, Nexus Node status, or execution authority.

**19.1.2.4** Participation Claims shall identify capacity where capacity matters. A person participating personally shall not be described as committing an employer, public authority, fund, insurer, donor, university, community, Indigenous body, media organization, provider, sponsor, National Consortium Company, Project SPV, or government unless a separate lawful record supports that claim.

**19.1.2.5** Participation Claims shall not imply that access to a room, invitation to Nexus Universe, appearance on a public stage, attendance at a public authority learning room, attendance at a capital-reader room, participation in a safeguard room, or presence in a public-safe report constitutes approval or authority.

**19.1.2.6** Public Participation Claims shall use approved language and shall include limitation language where needed to prevent reliance.

**19.1.2.7** Participation Claims shall be correctionable. If participation is overstated, misclassified, publicly listed beyond permission, used as endorsement, used as finance signal, used as provider validation, used as consent, or used to imply execution, the claim shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.1.3 Council Claim

**19.1.3.1** A **Council Claim** shall be any statement concerning participation in, formation of, leadership of, contribution to, sponsorship of, support for, outputs of, or status within a National Council, National Leadership Council, National Investors Council, regional council, global council interface, or related council pathway.

**19.1.3.2** A Council Claim shall be permitted only where supported by a current Council Register or Council Formation Record identifying the council, participant, role, capacity, term, geography, access class, public-safe listing status, permitted language, prohibited language, conflicts, correction history, and renewal status.

**19.1.3.3** Council Claims shall preserve the distinction between council participation and authority. Council membership, leadership, chairing, sponsorship, speaking, or contribution shall not create board appointment, public authority status, government endorsement, procurement status, financeability, certification, provider validation, community consent, Indigenous consent, project authorization, or execution.

**19.1.3.4** National Leadership Council Claims shall not imply national leadership authority, public authority approval, government endorsement, national adoption, or permission to speak for the country. National Investors Council Claims shall not imply capital interest, investment approval, underwriting appetite, insurance approval, donor support, public finance allocation, financeability, transaction readiness, or project approval.

**19.1.3.5** Council Claims shall distinguish personal capacity from institutional capacity and shall not convert a council participant’s public office, former office, investor role, academic role, media role, community role, Indigenous role where applicable, or enterprise role into institutional endorsement.

**19.1.3.6** Public Council Claims may describe participation, formation, contribution, leadership-pool involvement, investor-literacy involvement, Nexus Universe contribution, or Working Group referral only within the record.

**19.1.3.7** Council Claims shall be correctionable. If council status is overstated, leadership is used as authority, investor participation is used as finance signal, public authority status is implied, provider validation is implied, consent is implied, or execution is suggested, the claim shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.1.4 Helix Claim

**19.1.4.1** A **Helix Claim** shall be any statement concerning participation in, formation of, sponsorship of, contribution to, support for, outputs of, or status within a Government / Public Authority Helix Council, Academia / Research / Science Helix Council, Industry / Enterprise / Infrastructure / Technology Helix Council, Capital / Insurance / Donor / Development Helix Council, Media / Civic / Public-Interest Helix Council, or Community / Indigenous / Diaspora / Place-Based Legitimacy Interface.

**19.1.4.2** A Helix Claim shall be permitted only where supported by a current Helix Council Register or Helix Council Formation Record identifying the helix, participant, role, capacity, term, geography, access class, public-safe listing status, contribution type, permitted language, prohibited language, conflicts, correction history, and renewal status.

**19.1.4.3** Helix Claims shall preserve functional boundaries. Government / Public Authority Helix Claims shall not imply public authority action. Academia / Research / Science Helix Claims shall not imply certification. Industry / Enterprise / Infrastructure / Technology Helix Claims shall not imply provider selection or validation. Capital / Insurance / Donor / Development Helix Claims shall not imply financeability or commitment. Media / Civic / Public-Interest Helix Claims shall not imply public warning authority. Community / Indigenous / Diaspora / Place-Based Legitimacy Claims shall not imply consent.

**19.1.4.4** Helix Claims shall identify institutional or personal capacity where necessary and shall not convert participation into endorsement by an institution, ministry, agency, regulator, university, company, investor, insurer, donor, media organization, community, Indigenous body, or civil society organization unless separately and lawfully recorded.

**19.1.4.5** Helix Claims may describe contribution to learning, evidence, capability mapping, finance-readiness literacy, public-safe reporting, safeguard review, Nexus Universe preparation, AEP Passport candidate preparation, Nexus Rail routeability, Docket or Grid input, or handoff-readiness only within the controlling record.

**19.1.4.6** Public Helix Claims shall include limitation language where needed to prevent overclaim.

**19.1.4.7** Helix Claims shall be correctionable. If helix status is overstated, institutional roles are misclassified, safeguards are tokenistic or absent, public authority approval is implied, financeability is implied, provider validation is implied, certification is implied, consent is implied, or execution is suggested, the claim shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.1.5 Regional Claim

**19.1.5.1** A **Regional Claim** shall be any statement concerning a Regional Headquarters Consortium, regional activation, regional threshold, regional Top-Three status, regional country coverage, Regional Cluster Program Plan, regional Nexus Universe role, regional sponsor or partner role, regional AEP Passport or Nexus Rail candidate, regional Docket or Grid item, regional public-safe report, regional correction, or regional handoff-readiness.

**19.1.5.2** A Regional Claim shall be permitted only where supported by a current Regional Formation Register, Regional Country Activation Register, Regional Participation Register, Regional Sponsor and Partner Register, Regional Nexus Universe Register, Regional AEP Passport and Rail Register, Regional Docket and Grid Register, Regional Public-Safe Reporting Register, Regional Claims Register, Regional Correction Register, Regional Cluster Program Plan, or equivalent controlling record.

**19.1.5.3** Regional Claims shall preserve the distinction between regional coordination and regional supremacy. A Regional Headquarters Consortium may coordinate, synthesize, translate, route, report, and support, but shall not claim authority over countries, national pathways, public authorities, communities, Indigenous peoples where applicable, providers, sponsors, capital actors, National Consortium Companies, Project SPVs, or projects unless separately and lawfully recorded.

**19.1.5.4** Regional Claims shall distinguish country mapping, signal-stage engagement, founding-circle status, council formation, helix formation, National Model preparation, Nexus Universe readiness, Top-Three status, regional threshold status, handoff-readiness, and execution by separate classification.

**19.1.5.5** Regional Claims shall not imply government endorsement, public authority approval, procurement status, financeability, provider validation, certification, consent, project authorization, AEP Passport status, Nexus-ready status, Nexus Node status, Docket resolution, Grid maturity approval, or execution.

**19.1.5.6** Public Regional Claims shall preserve national source limitations and shall not publicize country records beyond national permission.

**19.1.5.7** Regional Claims shall be correctionable. If regional status is overstated, country activation is inflated, national gateways are bypassed, public authority approval is implied, financeability is implied, provider validation is implied, consent is implied, or execution is suggested, the claim shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.1.6 Global Claim

**19.1.6.1** A **Global Claim** shall be any statement concerning the Global Nexus Consortium, Global Activation, global threshold, global completeness, Regional Headquarters coverage, G7 activation coverage, G20 expansion coverage, regional Top-Three coverage, Nexus Universe global role, Global Nexus Core, global sponsor or partner role, global AEP Passport or Nexus Rail candidate, global Docket or Grid theme, global public-safe report, global correction, or global handoff-readiness.

**19.1.6.2** A Global Claim shall be permitted only where supported by a current Global Consortium Register, Regional Headquarters Register, Global Participation Register, Global Sponsor and Partner Register, Global Nexus Universe Register, Global AEP Passport and Rail Register, Global Docket and Grid Register, Global Public-Safe Reporting Register, Global Claims Register, Global Correction Register, Global Nexus Consortium Annual Record, or equivalent controlling record.

**19.1.6.3** Global Claims shall preserve the distinction between global coordination and global supremacy. The global layer may coordinate the common rail, synthesize records, support Nexus Universe, support public-safe reporting, compare regional and national records, support AEP Passport and Nexus Rail coordination, support Docket and Grid comparability, and guide claims discipline, but shall not govern countries, override regions, bind public authorities, approve projects, allocate finance, select providers, certify systems, grant consent, issue public warnings, command emergencies, or execute.

**19.1.6.4** Global Claims shall distinguish foundational global spine formation, global threshold status, G7 activation, G20 expansion, regional Top-Three coverage, Nexus Universe surge capacity, National Model Library development, Regional Cluster Program Plan Library development, public-safe reporting capacity, handoff-readiness themes, and execution by separate classification.

**19.1.6.5** Global Claims shall not imply official global endorsement, intergovernmental approval, public authority approval, procurement status, financeability, provider validation, certification, standards conformance, community consent, Indigenous consent, project authorization, AEP Passport status, Nexus-ready status, Nexus Node status, Docket resolution, Grid maturity approval, or execution.

**19.1.6.6** Public Global Claims shall preserve national and regional source limitations and shall not convert global visibility into authority.

**19.1.6.7** Global Claims shall be correctionable. If global activation is overstated, regional or national status is inflated, G7 or G20 coverage is used as official endorsement, public authority approval is implied, financeability is implied, provider validation is implied, certification is implied, consent is implied, or execution is suggested, the claim shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.1.7 Sponsorship Claim

**19.1.7.1** A **Sponsorship Claim** shall be any statement that a person or institution sponsors, funds, supports, backs, underwrites, enables, contributes resources to, provides in-kind support for, or is publicly recognized as supporting a Nexus-related pathway.

**19.1.7.2** A Sponsorship Claim shall be permitted only where supported by a current sponsor record identifying the sponsor, pathway, support type, geography, term, permitted references, prohibited claims, influence restrictions, conflict status, logo or mark-use permission, public-safe listing permission, correction rights, and archive status.

**19.1.7.3** Sponsorship Claims shall preserve support-without-control. Sponsorship shall not be described as governance authority, agenda control, output control, participant-selection authority, public authority influence, procurement advantage, finance signal, provider validation, certification, community legitimacy, Indigenous consent, project authorization, Nexus-ready status, AEP Passport status, Nexus Node status, or execution authority.

**19.1.7.4** Sponsorship Claims shall distinguish global sponsorship, regional sponsorship, national sponsorship, council sponsorship, helix sponsorship, Nexus Universe sponsorship, technical support, public-good contribution, hosting, anchoring, and partnership.

**19.1.7.5** Sponsor names, marks, logos, statements, event presence, room presence, public-stage presence, or public-safe listings shall not imply endorsement of sponsor products, services, projects, investments, technologies, public authority relationships, provider offerings, or downstream roles.

**19.1.7.6** Sponsorship Claims shall be reviewed before use in sponsor materials, public-safe reports, websites, pitch decks, investor materials, media materials, provider materials, public authority materials, procurement materials, Nexus Universe materials, and handoff documents.

**19.1.7.7** Sponsorship Claims shall be correctionable. If sponsorship is used as procurement advantage, finance signal, provider validation, public authority influence, certification implication, consent implication, Nexus Universe endorsement, project authorization, or execution claim, the claim shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.1.8 Partnership Claim

**19.1.8.1** A **Partnership Claim** shall be any statement that a person or institution is a partner, strategic partner, knowledge partner, technical partner, public-good contributor, software contributor, country support partner, host, anchor, provider candidate, capital reader, public authority learner, safeguard contributor, media contributor, or other collaborator in a Nexus-related pathway.

**19.1.8.2** A Partnership Claim shall be permitted only where supported by a current partner or contributor record identifying the partner, pathway, role, scope, geography, term, contribution, permitted references, prohibited claims, conflict status, confidentiality obligations, publication class, correction rights, and archive status.

**19.1.8.3** Partnership Claims shall not imply merger, agency, joint venture, shared liability, governance authority, public authority status, procurement status, financeability, certification, provider validation, consent, project authorization, or execution unless separately and lawfully recorded.

**19.1.8.4** Partnership with one Nexus-related body or layer shall not imply partnership with another. Partnership with a National Nexus Consortium shall not imply partnership with GCRI, GRF, GRA, the Global Nexus Consortium, a Regional Headquarters Consortium, a public authority, a National Consortium Company, or a Project SPV unless separately recorded.

**19.1.8.5** Technical Partnership Claims shall not imply technical approval or certification. Knowledge Partnership Claims shall not imply academic validation or policy approval. Provider Candidate Claims shall not imply provider qualification. Capital Reader Claims shall not imply financeability. Public Authority Learner Claims shall not imply public authority approval. Safeguard Contributor Claims shall not imply consent. Media Contributor Claims shall not imply public warning authority.

**19.1.8.6** Partnership Claims shall use approved language and shall include role and scope limitations where needed.

**19.1.8.7** Partnership Claims shall be correctionable. If partnership is overclaimed, used to imply agency, creates shared-liability confusion, creates finance signaling, implies provider validation, implies public authority approval, implies consent, suppresses safeguards, or creates execution implication, the claim shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.1.9 Handoff Claim

**19.1.9.1** A **Handoff Claim** shall be any statement that a record, pathway, 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, National Consortium Company interface, or Project SPV interface has been prepared, routed, transmitted, accepted, reviewed, or made handoff-ready for a downstream recipient.

**19.1.9.2** A Handoff Claim shall be permitted only where supported by a Handoff Readiness Record, Lawful Handoff Trigger record, recipient acknowledgement, Company interface record, Project SPV interface record, or equivalent controlling record.

**19.1.9.3** Handoff Claims shall preserve the distinction between routing and approval. Handoff-ready shall mean sufficiently organized for separate lawful review within stated limits; it shall not mean project-approved, financeable, bankable, insurable, procured, certified, consented, permitted, AEP Passported, Nexus-ready, Nexus Node-approved, accepted for execution, or execution-ready.

**19.1.9.4** Handoff Claims shall identify the recipient or recipient class, purpose of routing, record version, unresolved dependencies, public authority dependencies, finance dependencies, procurement dependencies, provider-neutrality conditions, sponsor-boundary conditions, safeguard and consent-boundary conditions, protected knowledge restrictions, data and cyber restrictions, permitted claims, prohibited claims, correction rights, and archive status.

**19.1.9.5** Handoff Claims shall not imply that the public-good stack has executed, instructed execution, accepted liability, created agency, created shared liability, selected a provider, allocated finance, granted consent, or approved a project.

**19.1.9.6** Public Handoff Claims shall be rare, public-safe, limitation-heavy, and permitted only where publication does not create reliance, market confusion, public authority confusion, procurement advantage, finance signaling, provider validation, consent overclaim, protected knowledge exposure, or execution implication.

**19.1.9.7** Handoff Claims shall be correctionable. If handoff status is overstated, recipient status is misrepresented, safeguards are stripped, financeability is implied, provider validation is implied, public authority approval is implied, consent is implied, or execution is suggested, the claim shall be corrected, restricted, withdrawn, superseded, notified to affected recipients where appropriate, publicly clarified where necessary, or archived.

***

#### 19.1.10 Correction of Claims

**19.1.10.1** **Correction of Claims** shall be the mandatory process through which any claim concerning Nexus participation, council status, helix status, regional status, global status, sponsorship, partnership, public authority learning, finance-readiness, provider participation, safeguard contribution, Nexus Universe participation, AEP Passport, Nexus Rail, Docket, Grid, public-safe reporting, handoff-readiness, National Consortium Company status, Project SPV status, or execution implication is corrected when inaccurate, incomplete, misleading, unsafe, unauthorized, overbroad, outdated, superseded, or beyond the controlling record.

**19.1.10.2** Claim correction may include private notice, controlled clarification, public-safe clarification, language narrowing, claim withdrawal, public listing correction, mark-use restriction, access restriction, room restriction, role reclassification, sponsor or partner correction, provider-candidate correction, public authority reference correction, finance-readiness correction, safeguard correction, AEP Passport or Nexus Rail reference correction, Docket or Grid reference correction, handoff note correction, suspension, termination, non-renewal, supersession, and archive notation.

**19.1.10.3** Correction shall be urgent where delay would create public authority confusion, finance reliance, procurement advantage, provider validation, certification drift, sponsor capture, consent overclaim, protected knowledge exposure, public-safe reporting harm, market confusion, reputational misuse, institutional role collapse, national bypass, regional supremacy confusion, or execution implication.

**19.1.10.4** Correction may be private, controlled, restricted, public-safe, or public depending on sensitivity, audience, reliance risk, public harm risk, and public-safe reporting requirements.

**19.1.10.5** A person or institution that made, repeated, relied upon, or benefited from an incorrect claim may be required to correct downstream materials, notify recipients, remove public statements, cease mark use, revise materials, or acknowledge supersession.

**19.1.10.6** No claim shall become valid because it was not immediately corrected. Correction may occur after publication, media circulation, sponsor use, provider use, investor use, public authority reference, Nexus Universe visibility, archive, or passage of time.

**19.1.10.7** Claim correction records shall themselves be correctionable. If a correction is incomplete, wrong, unsafe, publicized beyond permission, or fails to correct the underlying overclaim, the correction record shall be corrected, restricted, superseded, publicly clarified where necessary, or archived.

***

### 19.2 Permitted Claims

#### 19.2.1 Participation in Nexus Consortium

**19.2.1.1** A person or institution may claim **participation in a Nexus Consortium** only where a current participation record supports the claim and identifies the relevant consortium layer, including national, regional, or global participation.

**19.2.1.2** A permitted participation claim may state that the person or institution participates in, contributes to, supports, or has access to a specified Nexus Consortium pathway, provided the claim is limited to the recorded role, geography, term, and participation class.

**19.2.1.3** The claim shall not state or imply that participation creates governance authority, public authority approval, government endorsement, procurement status, financeability, certification, provider validation, consent, project authorization, Nexus-ready status, AEP Passport status, Nexus Node status, or execution authority.

**19.2.1.4** Where participation is at national level, it shall not imply regional or global participation. Where participation is at regional level, it shall not imply national authority or global authority. Where participation is at global level, it shall not imply authority over regions or countries.

**19.2.1.5** Institutional participation shall not imply participation by affiliates, subsidiaries, parents, public authorities, investors, insurers, donors, providers, communities, Indigenous bodies, or project vehicles unless separately recorded.

**19.2.1.6** Public-safe participation language may include “participant,” “contributor,” “member of the participation pathway,” “registered participant,” or other approved wording, subject to the applicable record.

**19.2.1.7** Participation claims remain correctionable. If the claim exceeds the record, becomes outdated, omits required limitations, or creates reliance, the claim shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.2.2 Participation in National Council

**19.2.2.1** A person may claim **participation in a National Council** only where a current National Council Register, National Leadership Council Register, or National Investors Council Register supports the claim.

**19.2.2.2** A permitted claim may identify the person as a participant in the National Council, National Leadership Council, or National Investors Council, provided the claim is limited to the recorded capacity, country, term, participation level, access class, and public-safe listing permission.

**19.2.2.3** A National Leadership Council participation claim shall not imply national authority, public authority status, government endorsement, board appointment, policy authority, project approval, or execution.

**19.2.2.4** A National Investors Council participation claim shall not imply investment interest, financeability, bankability, insurability, capital commitment, insurance approval, donor support, public finance allocation, transaction readiness, project approval, or execution.

**19.2.2.5** The claim shall not imply that the participant’s employer, public office, fund, firm, government, university, community, Indigenous body where applicable, or institution has endorsed Nexus unless separately and lawfully recorded.

**19.2.2.6** Public-safe National Council language may include “participant in the National Council,” “participant in the National Leadership Council,” “participant in the National Investors Council,” “leadership-pool participant,” or “capital-readiness discussion participant,” subject to the applicable record and no-reliance language where required.

**19.2.2.7** National Council participation claims remain correctionable. If the claim is overstated, misclassified, used as authority, used as finance signal, or used to imply approval or execution, it shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.2.3 Participation in Helix Council

**19.2.3.1** A person or institution may claim **participation in a Helix Council** only where a current Helix Council Register supports the claim.

**19.2.3.2** A permitted claim may identify participation in the Government / Public Authority Helix Council, Academia / Research / Science Helix Council, Industry / Enterprise / Infrastructure / Technology Helix Council, Capital / Insurance / Donor / Development Helix Council, Media / Civic / Public-Interest Helix Council, or Community / Indigenous / Diaspora / Place-Based Legitimacy Interface, provided the claim is limited to the recorded role, country, term, capacity, contribution, and public-safe listing permission.

**19.2.3.3** Government / Public Authority Helix participation may be described only as learning, contribution, or dependency-mapping within capacity and shall not imply public authority action. Academia participation may be described only as knowledge, research, evidence, or methods contribution and shall not imply certification. Industry participation may be described only as capability or technical contribution and shall not imply provider selection. Capital participation may be described only as finance-readiness or capital-readability contribution and shall not imply financeability. Media participation may be described only as public-safe reporting or civic communication contribution and shall not imply public warning. Community or Indigenous participation may be described only as safeguard or place-based input and shall not imply consent.

**19.2.3.4** Institutional Helix Council participation shall not imply institutional endorsement beyond the recorded role and shall not extend to affiliates, subsidiaries, public authorities, funders, clients, communities, Indigenous peoples, or projects unless separately recorded.

**19.2.3.5** Helix Council claims shall preserve conflicts, sponsor boundaries, provider-neutrality, finance no-reliance, public authority boundaries, safeguard restrictions, and public-safe reporting limits.

**19.2.3.6** Public-safe Helix language may include “participant,” “contributor,” “institutional participant,” “learning participant,” “technical contributor,” “safeguard contributor,” or other approved wording, subject to the applicable record.

**19.2.3.7** Helix Council participation claims remain correctionable. If the claim is overstated, tokenistic, captured, misclassified, used as approval, used as finance signal, used as provider validation, used as consent, or used to imply execution, it shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.2.4 Participation in Regional Interface

**19.2.4.1** A person or institution may claim **participation in a Regional Interface** only where a current Regional Participation Register, Regional Sponsor and Partner Register, Regional Nexus Universe Register, Regional AEP Passport and Rail Register, Regional Docket and Grid Register, or other controlling regional record supports the claim.

**19.2.4.2** A permitted claim may identify participation in a Regional Headquarters Consortium pathway, regional council or interface, Regional Cluster Room, regional public authority learning room, regional capital-reader room, regional safeguard room, regional technical room, regional Nexus Universe pathway, regional AEP Passport or Nexus Rail candidate pathway, regional Docket or Grid pathway, regional public-safe reporting pathway, or regional handoff-readiness pathway, provided the claim is limited to the recorded role, region, countries affected if any, term, capacity, and public-safe listing permission.

**19.2.4.3** Participation in a Regional Interface shall not imply regional supremacy, country approval, national authority, public authority approval, financeability, procurement status, provider validation, certification, consent, project authorization, or execution.

**19.2.4.4** A Regional Interface claim shall not imply participation in all countries within the region, in the global layer, or in a national pathway unless separately recorded.

**19.2.4.5** Where a claim references a country through a regional interface, the claim shall preserve national source-record limits and shall not bypass national gateway conditions.

**19.2.4.6** Public-safe Regional Interface language may include “regional participant,” “regional contributor,” “regional support participant,” “regional Nexus Universe participant,” or other approved wording, subject to the record.

**19.2.4.7** Regional Interface participation claims remain correctionable. If the claim overstates regional role, implies country approval, bypasses national records, creates finance signaling, implies provider validation, implies public authority approval, implies consent, or suggests execution, it shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.2.5 Participation in Global Interface

**19.2.5.1** A person or institution may claim **participation in a Global Interface** only where a current Global Participation Register, Global Sponsor and Partner Register, Global Nexus Universe Register, Global AEP Passport and Rail Register, Global Docket and Grid Register, or other controlling global record supports the claim.

**19.2.5.2** A permitted claim may identify participation in a Global Nexus Consortium pathway, Nexus Universe global pathway, Global Nexus Core pathway, global public authority learning room, global capital-reader room, global safeguard room, global technical room, global AEP Passport or Nexus Rail pathway, global Docket or Grid pathway, global public-safe reporting pathway, or global handoff-readiness pathway, provided the claim is limited to the recorded role, term, capacity, access class, and public-safe listing permission.

**19.2.5.3** Participation in a Global Interface shall not imply global supremacy, authority over regions or countries, public authority approval, intergovernmental approval, financeability, procurement status, provider validation, certification, standards conformance, community consent, Indigenous consent, project authorization, or execution.

**19.2.5.4** A Global Interface claim shall not imply participation in regional or national pathways unless separately recorded.

**19.2.5.5** Global Interface claims shall preserve source limitations and shall not convert global visibility, public-stage participation, global room access, public-safe reporting contribution, or Nexus Universe prominence into authority.

**19.2.5.6** Public-safe Global Interface language may include “global participant,” “global contributor,” “global interface participant,” “Nexus Universe global participant,” or other approved wording, subject to the record.

**19.2.5.7** Global Interface participation claims remain correctionable. If the claim overstates global role, implies authority, creates finance signaling, implies provider validation, implies public authority approval, implies consent, or suggests execution, it shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.2.6 Nexus Universe Participation

**19.2.6.1** A person or institution may claim **Nexus Universe Participation** only where a current Nexus Universe Preparation Record, Global Nexus Universe Register, Regional Nexus Universe Register, National Nexus Universe Register, or equivalent controlling record supports the claim.

**19.2.6.2** A permitted claim may identify preparation participation, delegation participation, speaker participation, controlled-room access, public-stage participation, public-safe reporting contribution, AEP Passport discussion participation, Nexus Rail discussion participation, Docket or Grid participation, safeguard-room contribution, public authority learning-room participation, capital-reader room participation, technical-room contribution, media-room contribution, or handoff-discussion participation only within the record.

**19.2.6.3** Nexus Universe Participation shall not imply Nexus Universe approval, endorsement, financeability, procurement status, provider validation, certification, public authority approval, government endorsement, community consent, Indigenous consent, project authorization, AEP Passport status, Nexus-ready status, Nexus Node status, Docket resolution, Grid maturity approval, handoff approval, or execution.

**19.2.6.4** A participant may not claim broader access than granted. Attendance at a public stage shall not imply access to controlled rooms. Access to a capital-reader room shall not imply investment interest. Access to a public authority room shall not imply public authority approval. Participation in a safeguard room shall not imply consent.

**19.2.6.5** Nexus Universe claims shall distinguish annual cycle, role, room, access, publication class, and geography where relevant.

**19.2.6.6** Public-safe Nexus Universe language may include “participant in Nexus Universe,” “speaker at Nexus Universe,” “delegate to Nexus Universe,” “contributor to a Nexus Universe room,” or other approved wording, subject to the record and limitations.

**19.2.6.7** Nexus Universe Participation claims remain correctionable. If participation is used as approval, finance signal, provider validation, public authority endorsement, consent, project authorization, or execution authority, the claim shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.2.7 Public-Good Contribution

**19.2.7.1** A person or institution may claim **Public-Good Contribution** only where a current contribution record, public-good software contribution record, knowledge partner record, technical partner record, safeguard contributor record, public-safe reporting contributor record, or equivalent controlling record supports the claim.

**19.2.7.2** A permitted claim may describe contribution of knowledge, software, methods, data where lawful, technical expertise, public-safe reporting support, safeguard input, translation, accessibility support, administrative support, Nexus Universe support, AEP Passport candidate input, Nexus Rail routeability input, Docket input, Grid input, or other public-good support, provided the claim is limited to the recorded scope.

**19.2.7.3** Public-Good Contribution shall not imply institutional endorsement, technical approval, certification, standards conformance, financeability, procurement status, provider validation, public authority approval, consent, project authorization, or execution.

**19.2.7.4** Public-Good Software Contribution shall not imply maintainership, production readiness, security approval, public authority approval, procurement readiness, certification, or execution readiness unless separately recorded.

**19.2.7.5** Technical contribution shall not imply provider validation. Knowledge contribution shall not imply scientific or policy endorsement. Safeguard contribution shall not imply consent. Public-safe reporting contribution shall not imply public warning authority.

**19.2.7.6** Public-safe Public-Good Contribution language may include “contributor,” “technical contributor,” “knowledge contributor,” “public-good software contributor,” “safeguard contributor,” or other approved wording, subject to the record.

**19.2.7.7** Public-Good Contribution claims remain correctionable. If contribution is used as approval, certification, financeability, provider validation, public authority endorsement, consent, project authorization, or execution authority, the claim shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.2.8 Finance-Readiness Contribution

**19.2.8.1** A person or institution may claim **Finance-Readiness Contribution** only where a current finance-readiness, capital-reader, National Investors Council, Capital / Insurance / Donor / Development Helix, GRA-aligned, Nexus Universe capital-reader room, AEP Passport finance-layer, Nexus Rail finance-readiness, Docket, Grid, or handoff-readiness record supports the claim.

**19.2.8.2** A permitted claim may describe contribution to finance-readiness, capital-readability, insurance-readiness, donor relevance, development-readiness, public finance relevance, disaster-risk finance literacy, diligence-gap mapping, Project SPV-readiness questions, no-reliance capital-reader rooms, or lawful handoff-readiness, provided the claim is limited to the recorded scope.

**19.2.8.3** Finance-Readiness Contribution shall be no-reliance, non-advisory, non-solicitation, non-placement, non-underwriting, non-rating, non-guarantee, non-transactional, non-fiduciary, and non-executing.

**19.2.8.4** Finance-Readiness Contribution shall not imply investment interest, financeability, bankability, insurability, underwriting appetite, insurance approval, donor approval, development finance approval, public finance allocation, transaction readiness, capital commitment, project approval, or execution.

**19.2.8.5** Finance-readiness claims shall identify no-reliance status where public or external.

**19.2.8.6** Public-safe Finance-Readiness Contribution language may include “finance-readiness contributor,” “capital-readability contributor,” “capital-reader participant,” “insurance-readiness contributor,” or other approved wording, subject to the record and no-reliance language.

**19.2.8.7** Finance-Readiness Contribution claims remain correctionable. If contribution is used as finance signal, investment endorsement, bankability, insurance approval, donor approval, public finance allocation, transaction readiness, project approval, or execution authority, the claim shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.2.9 Public-Safe Reporting Contribution

**19.2.9.1** A person or institution may claim **Public-Safe Reporting Contribution** only where a current public-safe reporting contributor record, media and civic contributor record, Public-Safe Reporting Register entry, Nexus Universe reporting record, National Model summary record, Regional Cluster Program Plan summary record, correction notice record, or equivalent controlling record supports the claim.

**19.2.9.2** A permitted claim may describe contribution to public-safe reporting, civic communication, knowledge translation, accessibility, plain-language explanation, translation, localization, media literacy, information integrity, misinformation risk review, public-interest reporting, public narrative discipline, public-safe publication, correction notices, archive summaries, or Nexus Universe public-stage communication.

**19.2.9.3** Public-Safe Reporting Contribution shall not imply editorial control, public relations control, public warning authority, emergency communication authority, sponsor promotion, provider marketing, public authority endorsement, finance promotion, certification communication, consent communication, project approval, or execution authority.

**19.2.9.4** A contributor shall not disclose or claim access to restricted, confidential, protected knowledge, public authority-sensitive, finance-sensitive, provider-sensitive, sponsor-sensitive, community-sensitive, Indigenous-sensitive where applicable, cyber-sensitive, infrastructure-sensitive, security-sensitive, health-sensitive, humanitarian-sensitive, or not-for-publication materials.

**19.2.9.5** Public-safe reporting contribution shall remain subject to correction, withdrawal, supersession, and archive controls.

**19.2.9.6** Public-safe Public-Safe Reporting Contribution language may include “public-safe reporting contributor,” “civic communication contributor,” “knowledge translation contributor,” “accessibility contributor,” or other approved wording, subject to the record.

**19.2.9.7** Public-Safe Reporting Contribution claims remain correctionable. If reporting contribution is used as public warning authority, sponsor promotion, provider validation, public authority approval, finance signal, consent, project authorization, or execution authority, the claim shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.2.10 Claims Subject to Record

**19.2.10.1** All permitted claims shall remain **subject to record**. A claim that is generally permitted shall be prohibited in any specific case where no controlling record exists, the record has expired, the record has been corrected, the record has been restricted, the record has been withdrawn, the record has been superseded, the record has been archived, the participant lacks public-safe listing permission, or the claim exceeds the permitted scope.

**19.2.10.2** A permitted claim shall remain limited by geography, term, role, capacity, layer, pathway, publication class, audience, source limitations, conflicts, public authority boundaries, finance boundaries, provider-neutrality conditions, sponsor restrictions, safeguard conditions, data and cyber restrictions, protected knowledge restrictions, correction history, renewal requirements, and archive status.

**19.2.10.3** A claim shall not be expanded by implication. A national claim shall not become regional or global. A regional claim shall not become national authority or global authority. A global claim shall not become authority over regions or countries. A public-good claim shall not become enterprise approval. A readiness claim shall not become execution.

**19.2.10.4** Translations, summaries, social media posts, speeches, decks, proposals, sponsor materials, provider materials, investor materials, public authority materials, procurement materials, press releases, media interviews, public-safe reports, and handoff documents shall remain subject to the same record limits as the original claim.

**19.2.10.5** A claim may require limitation language even if the underlying role is valid.

**19.2.10.6** When claim status is uncertain, the claim shall be withheld, narrowed, or routed for review rather than published.

**19.2.10.7** Claims Subject to Record shall be correctionable. If a permitted claim is used outside the record, the claim shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

### 19.3 Prohibited Claims

#### 19.3.1 Public Authority Approval Claim

**19.3.1.1** A **Public Authority Approval Claim** shall mean any statement, implication, logo use, title use, public authority reference, room reference, Government Portfolio reference, public finance reference, regulatory-learning reference, public-stage reference, or public-safe reporting language that suggests a public authority has approved, authorized, adopted, endorsed, cleared, validated, permitted, procured, financed, funded, certified, warned, commanded, or otherwise officially acted on a Nexus-related matter where no separate lawful public authority record supports the exact claim.

**19.3.1.2** Public Authority Approval Claims are prohibited unless a competent public authority has separately and lawfully issued the relevant decision and the claim is permitted by the applicable public authority and Nexus records.

**19.3.1.3** Public authority participation in Nexus, including attendance, learning, dashboard review, room participation, receipt of materials, contribution to dependency notes, Nexus Universe presence, Government Portfolio showcase participation, AEP Passport public authority layer discussion, Nexus Rail dependency routing, Docket input, Grid input, or public-safe report reference, shall not be described as approval.

**19.3.1.4** Prohibited formulations include statements that imply approval by a ministry, regulator, municipality, public finance body, public infrastructure body, emergency authority, public health body, public enterprise, Indigenous or Tribal public-governance body where applicable, or other public-law body unless separately and lawfully supported.

**19.3.1.5** Public authority names, seals, logos, titles, quotations, photographs, email domains, official affiliations, or attendance lists shall not be used to imply approval.

**19.3.1.6** Any public authority-related claim shall be reviewed for capacity, jurisdiction, authority, public-safe status, and permitted language before publication.

**19.3.1.7** Public Authority Approval Claims shall be corrected. If such a claim is made without lawful support, it shall be withdrawn, narrowed, corrected, publicly clarified where necessary, and archived.

***

#### 19.3.2 Government Endorsement Claim

**19.3.2.1** A **Government Endorsement Claim** shall mean any statement or implication that a government, ministry, agency, regulator, municipality, public enterprise, public finance body, legislature, court, public infrastructure body, emergency authority, public health authority, Indigenous or Tribal public-governance body where applicable, or other public authority endorses, supports, recommends, adopts, sponsors, approves, validates, or authorizes a Nexus-related pathway.

**19.3.2.2** Government Endorsement Claims are prohibited unless a competent government or public authority has separately and lawfully issued the endorsement and the claim is permitted by the applicable record.

**19.3.2.3** Participation by public officials, former officials, public-sector employees, public authorities, public finance readers, procurement learners, regulatory learners, or public authority learners shall not be used as government endorsement.

**19.3.2.4** Government-hosted or government-attended meetings shall not be described as endorsement unless separately and lawfully recorded.

**19.3.2.5** Public-stage appearance with public officials, photographs, agendas, room titles, public authority learning sessions, or public-safe summaries shall not imply endorsement.

**19.3.2.6** Claims concerning government relationships shall identify learning, consultation, dependency mapping, public-safe discussion, or official action accurately and separately.

**19.3.2.7** Government Endorsement Claims shall be corrected. If made without lawful support, the claim shall be withdrawn, narrowed, corrected, publicly clarified where necessary, and archived.

***

#### 19.3.3 Certification Claim

**19.3.3.1** A **Certification Claim** shall mean any statement or implication that Nexus, GCRI, GRF, GRA, the Global Nexus Consortium, a Regional Headquarters Consortium, a National Nexus Consortium, Nexus Universe, AEP Passport, Nexus Rail, Nexus Grid, Nexus Observatory, a council, a helix, a Working Group, a Competence Cell, a public-safe report, a National Model, a Regional Cluster Program Plan, a sponsor, a partner, a provider, a National Consortium Company, or a Project SPV has certified, approved, accredited, assured, verified, validated, guaranteed, or formally attested to a person, institution, product, service, project, system, provider, method, technology, maturity level, or outcome where no separate competent certification record supports the exact claim.

**19.3.3.2** Certification Claims are prohibited unless a competent authorized body has separately and lawfully established a certification process, issued the relevant certification, and permitted the exact claim.

**19.3.3.3** 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, Docket item, Grid input, or public-safe report shall not be described as certification.

**19.3.3.4** Claims using words such as certified, accredited, verified, validated, assured, approved, guaranteed, authorized, compliant, or equivalent terms shall receive heightened review.

**19.3.3.5** Public-safe reporting may describe records, evidence, methods, inputs, candidates, readiness questions, and limitations, but shall not certify.

**19.3.3.6** A participant shall not use Nexus participation to claim certification of its organization, technology, project, product, service, capability, or system.

**19.3.3.7** Certification Claims shall be corrected. If made without competent certification authority and record, the claim shall be withdrawn, narrowed, corrected, publicly clarified where necessary, and archived.

***

#### 19.3.4 Standards-Conformance Claim

**19.3.4.1** A **Standards-Conformance Claim** shall mean any statement or implication that a 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 conforms to a standard, protocol, specification, certification scheme, regulatory standard, procurement standard, technical standard, safety standard, maturity standard, or Nexus standard where no competent standards or conformance record supports the exact claim.

**19.3.4.2** Standards-Conformance Claims are prohibited unless a competent standards authority or authorized conformance process has separately issued the relevant conformance record and permitted the claim.

**19.3.4.3** Nexus 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 standards conformance by default.

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

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

**19.3.4.6** Standards-Conformance Claims shall preserve the separation between standards-interface and standards authority.

**19.3.4.7** Standards-Conformance Claims shall be corrected. If made without competent conformance record, the claim shall be withdrawn, narrowed, corrected, publicly clarified where necessary, and archived.

***

#### 19.3.5 Procurement Status Claim

**19.3.5.1** A **Procurement Status Claim** shall mean any statement or implication that participation in Nexus, sponsorship, partnership, provider-candidate status, technical contribution, Nexus Universe participation, public authority 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 creates procurement eligibility, prequalification, shortlist status, preferred-provider status, procurement award, public buyer approval, procurement endorsement, or procurement advantage.

**19.3.5.2** Procurement Status Claims are prohibited unless a competent procurement body has separately and lawfully issued the relevant procurement decision and the claim is permitted by the applicable record.

**19.3.5.3** Provider participation, sponsor support, technical demonstrations, public-good software contribution, Working Group participation, Competence Cell participation, Nexus Universe visibility, or public-safe report reference shall not be described as procurement status.

**19.3.5.4** Public authority learning rooms and procurement-neutral learning pathways shall not be used to imply procurement access, procurement eligibility, or procurement advantage.

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

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

**19.3.5.7** Procurement Status Claims shall be corrected. If made without lawful procurement record, the claim shall be withdrawn, narrowed, corrected, publicly clarified where necessary, and archived.

***

#### 19.3.6 Provider Validation Claim

**19.3.6.1** A **Provider Validation Claim** shall mean any statement or implication that Nexus, GCRI, GRF, GRA, a Nexus Consortium, Nexus Universe, AEP Passport, Nexus Rail, Docket, Grid, public-safe reporting, a National Model, a Regional Cluster Program Plan, a Working Group, a Competence Cell, a public authority learner, a capital reader, a sponsor, or a partner has approved, validated, selected, preferred, qualified, certified, recommended, ranked, endorsed, or accepted a provider, vendor, operator, host, platform, manufacturer, integrator, technology actor, infrastructure actor, consultant, professional firm, or enterprise participant.

**19.3.6.2** Provider Validation Claims are prohibited unless a separate competent provider qualification, procurement, contracting, certification, or approval process has lawfully created the exact status and the claim is permitted by the applicable record.

**19.3.6.3** Provider-neutral capability mapping, technical contribution, public-good software contribution, demonstrations, Nexus Universe participation, AEP Passport candidate input, Nexus Rail input, Docket input, Grid input, sponsor support, or handoff discussion shall not be described as provider validation.

**19.3.6.4** Provider Candidate status shall be described only as candidate, contributor, participant, or provider-neutral capability input within the record.

**19.3.6.5** Provider claims shall preserve procurement neutrality and shall not create competitive advantage through public-good participation.

**19.3.6.6** Provider Validation Claims shall be reviewed especially where the provider is also a sponsor, host, technical partner, capital actor, public authority contractor, National Consortium Company participant, Project SPV participant, or downstream handoff recipient.

**19.3.6.7** Provider Validation Claims shall be corrected. If made without competent provider validation record, the claim shall be withdrawn, narrowed, corrected, publicly clarified where necessary, and archived.

***

#### 19.3.7 Financeability or Bankability Claim

**19.3.7.1** A **Financeability or Bankability Claim** shall mean any statement or implication that a project, pathway, National Model, Regional Cluster Program Plan, AEP Passport candidate, Nexus Rail candidate, Docket item, Grid input, National Consortium Company, Project SPV, provider, system, portfolio, or opportunity is financeable, bankable, investable, investment-ready, capital-ready, lender-ready, fundable, de-risked for capital, transaction-ready, or otherwise ready for financing by reason of Nexus participation, finance-readiness work, capital-reader room participation, GRA-aligned review, National Investors Council involvement, Nexus Universe visibility, or handoff-readiness.

**19.3.7.2** Financeability or Bankability Claims are prohibited unless a competent lawful finance process has separately produced the exact record supporting the claim and the claim is permitted by applicable legal, financial, securities, market-conduct, and Nexus records.

**19.3.7.3** Finance-readiness, capital-readability, diligence-gap mapping, insurance-readiness, donor relevance, development-readiness, public finance relevance, SPV-readiness input, AEP Passport finance-layer input, Nexus Rail finance-readiness input, Docket input, Grid input, or handoff-readiness shall not be described as financeability or bankability.

**19.3.7.4** Capital-reader participation shall not imply investor interest, lender interest, underwriting appetite, capital commitment, transaction readiness, valuation, rating, or investment endorsement.

**19.3.7.5** Public materials shall use no-reliance language for finance-readiness discussions and shall avoid investment solicitation.

**19.3.7.6** Financeability language shall be reviewed for regulated-perimeter discipline before any use.

**19.3.7.7** Financeability or Bankability Claims shall be corrected. If made without competent finance record, the claim shall be withdrawn, narrowed, corrected, publicly clarified where necessary, and archived.

***

#### 19.3.8 Insurance Approval Claim

**19.3.8.1** An **Insurance Approval Claim** shall mean any statement or implication that an insurer, reinsurer, risk-transfer actor, insurance-readiness room, capital-reader room, GRA-aligned process, National Investors Council, Nexus Universe session, AEP Passport finance layer, Nexus Rail finance-readiness input, Docket item, Grid input, public-safe report, National Consortium Company, or Project SPV has approved, agreed to insure, underwrite, cover, price, guarantee, de-risk, accept, or support insurance for a project, pathway, technology, provider, system, portfolio, or SPV.

**19.3.8.2** Insurance Approval Claims are prohibited unless a competent insurer or reinsurer has separately and lawfully issued the relevant insurance, underwriting, coverage, or risk-transfer record and the claim is permitted by that record.

**19.3.8.3** Insurance-readiness, insurability questions, risk-transfer literacy, disaster-risk finance discussion, reinsurer attendance, capital-reader participation, or insurance-room participation shall not be described as insurance approval.

**19.3.8.4** Insurance-related claims shall not imply coverage, premium terms, underwriting appetite, risk acceptance, guarantee, claims-paying commitment, or insurability unless separately recorded.

**19.3.8.5** Public-safe reporting may describe insurance-readiness questions and risk-transfer dependencies without implying insurance approval.

**19.3.8.6** Insurance language shall be reviewed for regulated insurance, market conduct, reliance, and confidentiality risks before use.

**19.3.8.7** Insurance Approval Claims shall be corrected. If made without competent insurance record, the claim shall be withdrawn, narrowed, corrected, publicly clarified where necessary, and archived.

***

#### 19.3.9 Donor or Public Finance Commitment Claim

**19.3.9.1** A **Donor or Public Finance Commitment Claim** shall mean any statement or implication that a donor, foundation, development finance actor, multilateral institution, public finance body, government fund, climate finance facility, disaster-risk finance facility, philanthropic actor, or public-sector finance reader has committed, approved, allocated, endorsed, funded, financed, guaranteed, or agreed to support a Nexus-related project, pathway, National Model, Regional Cluster Program Plan, AEP Passport candidate, Nexus Rail candidate, National Consortium Company, Project SPV, provider, system, or portfolio.

**19.3.9.2** Donor or Public Finance Commitment Claims are prohibited unless the relevant donor, development finance actor, public finance body, or competent lawful body has separately issued the relevant commitment, allocation, approval, or funding record and the claim is permitted by that record.

**19.3.9.3** Donor relevance, development-readiness, public finance relevance, public finance reader participation, donor room participation, Nexus Universe visibility, National Investors Council participation, AEP Passport finance-layer input, Nexus Rail finance-readiness input, Docket input, Grid input, or handoff-readiness shall not be described as donor or public finance commitment.

**19.3.9.4** Public finance relevance shall not imply public finance allocation.

**19.3.9.5** Donor and public finance language shall preserve no-reliance, non-solicitation, and public authority boundary discipline.

**19.3.9.6** Public-safe reporting may describe donor relevance or public finance relevance questions without implying commitment.

**19.3.9.7** Donor or Public Finance Commitment Claims shall be corrected. If made without competent funding or allocation record, the claim shall be withdrawn, narrowed, corrected, publicly clarified where necessary, and archived.

***

#### 19.3.10 Community or Indigenous Consent Claim

**19.3.10.1** A **Community or Indigenous Consent Claim** shall mean any statement or implication that a community, affected stakeholder group, Indigenous people, Tribal actor, rights-holder, protected knowledge holder, diaspora group, youth group, civil society actor, local institution, traditional authority, or place-based participant has consented to, approved, endorsed, authorized, accepted, supported, granted social license for, validated, or permitted a Nexus-related project, pathway, National Model, Regional Cluster Program Plan, AEP Passport candidate, Nexus Rail candidate, public-safe report, National Consortium Company, Project SPV, provider, system, or implementation.

**19.3.10.2** Community or Indigenous Consent Claims are prohibited unless a competent and lawful consent, consultation, accommodation, FPIC, community approval, rights-holder approval, protected knowledge authorization, land access, cultural approval, environmental approval, or local authorization record supports the exact claim and the claim is permitted by that record.

**19.3.10.3** Community participation, Indigenous participation where applicable, safeguard-room attendance, diaspora input, youth input, accessibility input, protected knowledge caution, public-safe reporting input, Nexus Universe participation, National Model contribution, Regional Cluster Program Plan contribution, AEP Passport safeguard layer input, Nexus Rail safeguard condition, Docket input, Grid input, or handoff restriction shall not be described as consent.

**19.3.10.4** No individual or institution shall be treated as speaking for all affected communities, Indigenous peoples, rights-holders, future generations, diaspora groups, or places unless a separate lawful record supports that authority.

**19.3.10.5** Indigenous-related claims shall follow heightened boundary discipline and shall not imply consultation completion, accommodation completion, FPIC satisfaction, rights waiver, land approval, cultural approval, Indigenous data authorization, protected knowledge authorization, or consent.

**19.3.10.6** Public-safe reporting may describe safeguard themes, lived-risk input, public-safe limitations, and unresolved community or Indigenous dependencies without implying consent.

**19.3.10.7** Community or Indigenous Consent Claims shall be corrected. If made without competent consent or authorization record, the claim shall be withdrawn, narrowed, corrected, publicly clarified where necessary, and archived.

***

#### 19.3.11 Nexus-Ready Claim

**19.3.11.1** A **Nexus-Ready Claim** shall mean any statement or implication that a 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 is Nexus-ready, Nexus-approved, Nexus-qualified, Nexus-compatible, Nexus-validated, Nexus-endorsed, Nexus-cleared, or ready for Nexus implementation.

**19.3.11.2** Nexus-Ready Claims are prohibited unless a competent Nexus readiness process has been separately established, the relevant readiness record has been issued, and the exact claim is permitted by that record.

**19.3.11.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.

**19.3.11.4** Nexus-ready language shall not be used as shorthand for participation, candidate status, readiness discussion, public-good contribution, technical contribution, finance-readiness, or handoff-readiness.

**19.3.11.5** Any readiness vocabulary that may imply approval shall be reviewed against the Claims Register before use.

**19.3.11.6** Public-safe reporting may describe candidate status, readiness questions, dependencies, and limitations without using Nexus-ready status unless permitted.

**19.3.11.7** Nexus-Ready Claims shall be corrected. If made without competent readiness record, the claim shall be withdrawn, narrowed, corrected, publicly clarified where necessary, and archived.

***

#### 19.3.12 AEP Passport Status Claim

**19.3.12.1** An **AEP Passport Status Claim** shall mean any statement or implication that a person, institution, project, provider, product, service, system, node, portfolio, National Model element, Regional Cluster Program Plan element, public-good output, Nexus Universe output, National Consortium Company, Project SPV, or pathway has received, holds, qualifies for, has been approved for, or is covered by an AEP Passport.

**19.3.12.2** AEP Passport Status Claims are prohibited unless a competent AEP Passport process has issued the relevant status and the claim is permitted by the applicable AEP Passport record.

**19.3.12.3** AEP Passport candidate records, layer inputs, Proof Receipt inputs where authorized, Nexus Universe discussions, public-safe references, Docket items, Grid inputs, Nexus Rail references, and handoff-readiness records shall not be described as AEP Passport status.

**19.3.12.4** A Proof Receipt reference shall mean only what the applicable record expressly states and shall not be expanded into AEP Passport status, approval, certification, financeability, procurement status, provider validation, consent, project authorization, or execution.

**19.3.12.5** Public-safe AEP Passport language shall distinguish candidate, input, layer, Proof Receipt reference where authorized, discussion, public-safe reference, and issued status.

**19.3.12.6** AEP Passport Status Claims shall be reviewed before publication in public-safe reports, sponsor materials, provider materials, investor materials, public authority materials, procurement materials, media materials, Nexus Universe materials, and handoff documents.

**19.3.12.7** AEP Passport Status Claims shall be corrected. If made without competent AEP Passport record, the claim shall be withdrawn, narrowed, corrected, publicly clarified where necessary, and archived.

***

#### 19.3.13 Nexus Node Status Claim

**19.3.13.1** A **Nexus Node Status Claim** shall mean any statement or implication that a person, institution, location, facility, city, region, country, system, project, provider, host, operator, National Consortium Company, Project SPV, observability environment, technical environment, or platform has become, hosts, operates, controls, or has been approved as a Nexus Node.

**19.3.13.2** Nexus Node Status Claims are prohibited unless a competent Nexus Node process has issued the relevant status and the claim is permitted by the applicable Nexus Node record.

**19.3.13.3** Hosting, anchoring, sponsorship, Nexus Universe participation, Regional Headquarters hosting, National Desk hosting, Nexus Core support, observability contribution, AEP Passport candidate input, Nexus Rail routeability, Docket input, Grid input, public-safe reporting, or handoff-readiness shall not be described as Nexus Node status.

**19.3.13.4** A facility, platform, country, region, host, or provider shall not claim Node status by reason of supporting Nexus-related activities.

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

**19.3.13.6** Nexus Node Status Claims shall be reviewed before use in websites, public-safe reports, sponsor materials, provider materials, public authority materials, investor materials, Nexus Universe materials, and handoff documents.

**19.3.13.7** Nexus Node Status Claims shall be corrected. If made without competent Nexus Node record, the claim shall be withdrawn, narrowed, corrected, publicly clarified where necessary, and archived.

***

#### 19.3.14 Project Authorization Claim

**19.3.14.1** A **Project Authorization Claim** shall mean any statement or implication that a project, portfolio, system, corridor, node, National Consortium Company activity, Project SPV activity, provider activity, public authority pathway, finance pathway, procurement pathway, construction pathway, deployment pathway, operation, or implementation has been approved, authorized, cleared, permitted, adopted, consented, procured, financed, certified, or greenlit by Nexus, GCRI, GRF, GRA, a Nexus Consortium, Nexus Universe, AEP Passport, Nexus Rail, Docket, Grid, public-safe reporting, a National Model, a Regional Cluster Program Plan, or a public-good record.

**19.3.14.2** Project Authorization Claims are prohibited unless a competent lawful authority or project governance body has separately issued the relevant authorization and the claim is permitted by that record.

**19.3.14.3** Handoff-readiness, SPV-readiness, finance-readiness, public authority dependency mapping, provider-neutral capability mapping, safeguard records, AEP Passport candidate input, Nexus Rail routeability, Docket item, Grid input, public-safe report reference, National Model reference, Regional Cluster Program Plan reference, or Nexus Universe visibility shall not be described as project authorization.

**19.3.14.4** A National Consortium Company or Project SPV shall not claim project authorization from public-good stack participation or record receipt.

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

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

**19.3.14.7** Project Authorization Claims shall be corrected. If made without competent project authorization record, the claim shall be withdrawn, narrowed, corrected, publicly clarified where necessary, and archived.

***

#### 19.3.15 Execution Authority Claim

**19.3.15.1** An **Execution Authority Claim** shall mean any statement or implication that Nexus, GCRI, GRF, GRA, the Global Nexus Consortium, a Regional Headquarters Consortium, a National Nexus Consortium, the Central Nexus Bureau, Nexus Universe, a National Council, a Helix Council, a Working Group, a Competence Cell, a public-safe reporting pathway, an AEP Passport pathway, Nexus Rail, Docket, Grid, a sponsor, a partner, a public authority learner, or a public-good stack body has authority to execute, command, procure, finance, insure, build, deploy, operate, contract, direct, approve, warn, respond, authorize, consent, or implement.

**19.3.15.2** Execution Authority Claims are prohibited unless a separate competent lawful execution vehicle, public authority, National Consortium Company, Project SPV, provider, operator, contractor, finance actor, insurer, procurement body, community process, Indigenous governance process where applicable, or other lawful actor has independently and lawfully acquired the relevant authority.

**19.3.15.3** Public-good stack bodies shall not be described as project developers, operators, contractors, lenders, funds, insurers, reinsurers, underwriters, brokers, investment advisers, financial advisers, procurement bodies, regulators, certifiers, standards authorities by default, public warning bodies, emergency command centers, consent bodies, or execution vehicles.

**19.3.15.4** Handoff shall not be described as execution. Readiness shall not be described as authority. Participation shall not be described as action. Nexus Universe live operation shall not be described as project operation.

**19.3.15.5** Downstream execution, if any, shall occur only through separate lawful actors and processes outside the public-good stack.

**19.3.15.6** Communications shall include non-execution language where a reasonable reader could infer execution authority.

**19.3.15.7** Execution Authority Claims shall be corrected. If made without lawful execution authority, the claim shall be withdrawn, narrowed, corrected, publicly clarified where necessary, and archived.

***

### 19.4 Public-Safe Reporting

#### 19.4.1 Global Public-Safe Reports

**19.4.1.1** **Global Public-Safe Reports** shall be approved global-level reports, summaries, statements, dashboards, Nexus Universe outputs, Global Nexus Consortium Annual Records, global AEP Passport and Nexus Rail references, global Docket and Grid summaries, correction notices, renewal notices, or archive summaries prepared for public-safe release under the Global Public-Safe Reporting Register.

**19.4.1.2** Global Public-Safe Reports may describe, within approved limits, the global agenda, Regional Headquarters status, country activation status by classification, G7 and G20 coverage by classification, regional Top-Three coverage by classification, Nexus Universe cycle themes, public authority learning areas, finance-readiness themes, technical and evidence themes, provider-neutral capability themes, safeguard themes, AEP Passport and Nexus Rail candidate themes, Docket and Grid themes, correction and renewal items, and lawful handoff-readiness themes where public-safe.

**19.4.1.3** Global Public-Safe Reports shall synthesize without overriding national or regional source records and shall preserve source limitations, unresolved dependencies, public authority boundaries, finance boundaries, procurement-neutrality conditions, provider-neutrality conditions, sponsor restrictions, safeguard conditions, protected knowledge restrictions, data and cyber restrictions, claims limits, correction histories, and handoff limitations.

**19.4.1.4** Global Public-Safe Reports shall not be global approval reports, public authority reports, finance reports, procurement reports, certification reports, standards-conformance reports, consent reports, project pipelines, investment pipelines, public warnings, emergency command reports, or execution reports.

**19.4.1.5** Global Public-Safe Reports shall be reviewed for factual accuracy, source-record validity, public authority overclaim, finance overclaim, procurement implication, provider validation risk, certification or standards-conformance drift, community consent overclaim, Indigenous consent overclaim where applicable, protected knowledge exposure, data and cyber sensitivity, infrastructure and security sensitivity, humanitarian or health sensitivity, sponsor influence, media misuse, accessibility, translation, localization, and correction readiness.

**19.4.1.6** Public versions shall include limitations and no-reliance language where required.

**19.4.1.7** Global Public-Safe Reports shall be correctionable. If a report becomes inaccurate, unsafe, overbroad, incomplete, misleading, outdated, superseded, publicized beyond permission, or misused, it shall be corrected, narrowed, withdrawn, reclassified, superseded, archived, or publicly clarified where necessary.

***

#### 19.4.2 Regional Public-Safe Reports

**19.4.2.1** **Regional Public-Safe Reports** shall be approved regional-level reports, summaries, statements, dashboards, Regional Cluster Program Plan summaries, regional Nexus Universe outputs, regional AEP Passport and Nexus Rail references, regional Docket and Grid summaries, correction notices, renewal notices, or archive summaries prepared for public-safe release under the Regional Public-Safe Reporting Register.

**19.4.2.2** Regional Public-Safe Reports may describe, within approved limits, regional formation, Regional Headquarters status, country activation status by classification, regional Top-Three coverage by classification, Regional Cluster Program Plan themes, regional Nexus Universe outputs, public authority learning areas, finance-readiness and insurance-readiness themes, technical and evidence themes, provider-neutral capability themes, safeguard themes, AEP Passport and Nexus Rail candidate themes, Docket and Grid themes, correction and renewal items, and lawful handoff-readiness themes where public-safe.

**19.4.2.3** Regional Public-Safe Reports shall synthesize without overriding national source records and shall preserve country-specific limitations, unresolved dependencies, public authority boundaries, finance boundaries, procurement-neutrality conditions, provider-neutrality conditions, sponsor restrictions, safeguard conditions, protected knowledge restrictions, data and cyber restrictions, claims limits, correction histories, and handoff limitations.

**19.4.2.4** Regional Public-Safe Reports shall not be regional approval reports, country approval reports, public authority reports, finance reports, procurement reports, certification reports, standards-conformance reports, consent reports, project pipelines, investment pipelines, public warnings, emergency command reports, or execution reports.

**19.4.2.5** Regional Public-Safe Reports shall be reviewed for national source permissions, factual accuracy, public authority overclaim, finance overclaim, procurement implication, provider validation risk, certification drift, community consent overclaim, Indigenous consent overclaim where applicable, protected knowledge exposure, sponsor influence, media risk, accessibility, translation, localization, and correction readiness.

**19.4.2.6** Public versions shall identify activation classifications and limitations clearly enough to prevent regional supremacy, national bypass, country approval, financeability, certification, consent, or execution inference.

**19.4.2.7** Regional Public-Safe Reports shall be correctionable. If a report becomes inaccurate, unsafe, overbroad, incomplete, misleading, outdated, superseded, publicized beyond permission, or misused, it shall be corrected, narrowed, withdrawn, reclassified, superseded, archived, or publicly clarified where necessary.

***

#### 19.4.3 National Public-Safe Reports

**19.4.3.1** **National Public-Safe Reports** shall be approved country-level reports, summaries, statements, dashboards, National Model summaries, National Council summaries, Helix Council summaries, Working Group summaries, Nexus Universe national outputs, Government Portfolio showcase summaries where applicable, AEP Passport and Nexus Rail references, Docket and Grid summaries, correction notices, renewal notices, or archive summaries prepared for public-safe release under the National Public-Safe Reporting pathway.

**19.4.3.2** National Public-Safe Reports may describe, within approved limits, national formation status, National Council and Helix Council status, Working Group and Competence Cell themes, National Model public-safe themes, public authority learning areas, finance-readiness and capital-readability questions, technical and evidence themes, provider-neutral capability themes, safeguard themes, Nexus Universe national outputs, AEP Passport and Nexus Rail candidate references, Docket and Grid themes, correction and renewal items, and lawful handoff-readiness themes where public-safe.

**19.4.3.3** National Public-Safe Reports shall preserve national source limitations, unresolved dependencies, public authority boundaries, finance boundaries, procurement-neutrality conditions, provider-neutrality conditions, sponsor restrictions, safeguard conditions, protected knowledge restrictions, data and cyber restrictions, claims limits, correction histories, and handoff limitations.

**19.4.3.4** National Public-Safe Reports shall not be national approval reports, government reports by default, public authority reports, finance reports, procurement reports, certification reports, standards-conformance reports, consent reports, project pipelines, investment pipelines, public warnings, emergency command reports, or execution reports.

**19.4.3.5** National Public-Safe Reports shall be reviewed for factual accuracy, source-record validity, public authority overclaim, government endorsement implication, finance overclaim, procurement implication, provider validation risk, certification or standards-conformance drift, community consent overclaim, Indigenous consent overclaim where applicable, protected knowledge exposure, data and cyber sensitivity, infrastructure and security sensitivity, humanitarian or health sensitivity, sponsor influence, media misuse, accessibility, translation, localization, and correction needs.

**19.4.3.6** Public versions shall identify whether content is signal-stage, forming, provisional, active, public-safe, restricted, corrected, superseded, withdrawn, renewal-stage, or handoff-ready within limits.

**19.4.3.7** National Public-Safe Reports shall be correctionable. If a report becomes inaccurate, unsafe, overbroad, incomplete, misleading, outdated, superseded, publicized beyond permission, or misused, it shall be corrected, narrowed, withdrawn, reclassified, superseded, archived, or publicly clarified where necessary.

***

#### 19.4.4 Nexus Universe Public-Safe Reports

**19.4.4.1** **Nexus Universe Public-Safe Reports** shall be approved reports, summaries, statements, public-stage materials, annual cycle summaries, room summaries, delegation summaries, Nexus Core summaries, AEP Passport and Nexus Rail summaries, Docket and Grid summaries, correction notices, renewal notices, or archive summaries arising from the annual Nexus Universe cycle.

**19.4.4.2** Nexus Universe Public-Safe Reports may describe, within approved limits, one-year mobilization themes, one-month Nexus Core build themes, one-week live operation themes, global public-stage themes, regional room themes, national delegation themes, public authority learning themes, finance-readiness themes, technical and evidence themes, safeguard themes, public-safe reporting themes, AEP Passport and Nexus Rail candidate themes, Docket and Grid themes, correction themes, renewal themes, and handoff-readiness themes where public-safe.

**19.4.4.3** Nexus Universe Public-Safe Reports shall preserve room-boundary discipline. Public authority rooms shall not be described as approval rooms. Capital-reader rooms shall not be described as investment rooms. Insurance-readiness rooms shall not be described as underwriting rooms. Donor and development rooms shall not be described as commitment rooms. Provider-neutral rooms shall not be described as validation rooms. Sponsor-supported rooms shall not be described as control rooms. Safeguard rooms shall not be described as consent rooms. Media rooms shall not be described as public warning rooms. Handoff rooms shall not be described as execution rooms.

**19.4.4.4** Nexus Universe Public-Safe Reports shall not imply Nexus Universe approval, public authority approval, government endorsement, financeability, procurement status, provider validation, certification, consent, project authorization, AEP Passport status, Nexus-ready status, Nexus Node status, Docket resolution, Grid maturity approval, or execution.

**19.4.4.5** Nexus Universe Public-Safe Reports shall be reviewed for factual accuracy, source-record validity, room classification, participant capacity, public authority overclaim, finance overclaim, provider validation risk, certification drift, safeguard and consent overclaim, protected knowledge exposure, sponsor influence, media risk, accessibility, translation, localization, and correction readiness.

**19.4.4.6** Public versions shall distinguish preparation, live operation, discussion, input, candidate, public-safe summary, correction, renewal, and handoff-readiness.

**19.4.4.7** Nexus Universe Public-Safe Reports shall be correctionable. If a report becomes inaccurate, unsafe, overbroad, incomplete, misleading, outdated, superseded, publicized beyond permission, or misused, it shall be corrected, narrowed, withdrawn, reclassified, superseded, archived, or publicly clarified where necessary.

***

#### 19.4.5 Public Authority Language Review

**19.4.5.1** **Public Authority Language Review** shall be required for any claim, report, deck, website, press release, public-stage material, Nexus Universe material, National Model summary, Regional Cluster Program Plan summary, AEP Passport reference, Nexus Rail reference, Docket or Grid summary, handoff record, sponsor material, provider material, investor material, media material, or public-safe communication that references a public authority, public official, government, regulator, municipality, public finance body, public infrastructure body, emergency authority, public health body, Indigenous or Tribal public-governance body where applicable, or other public-law actor.

**19.4.5.2** The review shall determine whether the language accurately states capacity, role, jurisdiction, authority, participation status, public-safe listing permission, confidentiality obligations, publication class, and permitted references.

**19.4.5.3** The review shall prohibit language that implies public authority approval, government endorsement, regulatory comfort, policy adoption, procurement status, public finance allocation, data authorization, emergency action, public warning, infrastructure approval, environmental approval, project authorization, or execution unless separately and lawfully recorded.

**19.4.5.4** Public authority names, logos, seals, titles, photographs, quotations, public email domains, meeting attendance, or room participation shall not be used without permission and shall not imply endorsement.

**19.4.5.5** Public authority language shall distinguish learning, observation, dependency mapping, public-safe discussion, consultation where lawful, official process, official decision, and execution.

**19.4.5.6** Where ambiguity remains, the language shall be narrowed or withheld.

**19.4.5.7** Public Authority Language Review records shall be correctionable. If reviewed language later proves inaccurate, unsafe, overbroad, or misleading, it shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.4.6 Finance-Readiness Language Review

**19.4.6.1** **Finance-Readiness Language Review** shall be required for any claim, report, deck, website, press release, public-stage material, Nexus Universe material, National Model summary, Regional Cluster Program Plan summary, AEP Passport reference, Nexus Rail reference, Docket or Grid summary, handoff record, sponsor material, provider material, investor material, donor material, insurance material, public finance material, media material, or public-safe communication that references finance-readiness, capital-readability, insurance-readiness, donor relevance, development-readiness, public finance relevance, disaster-risk finance, diligence-gap, SPV-readiness, financeability, bankability, insurability, or transaction readiness.

**19.4.6.2** The review shall determine whether the language is no-reliance, non-advisory, non-solicitation, non-placement, non-underwriting, non-rating, non-guarantee, non-transactional, non-fiduciary, and non-executing.

**19.4.6.3** The review shall prohibit language that implies investment interest, financeability, bankability, insurability, underwriting appetite, insurance approval, donor approval, development finance approval, public finance allocation, transaction readiness, capital commitment, project approval, or execution unless separately and lawfully recorded by competent actors.

**19.4.6.4** Capital-reader participation, National Investors Council participation, insurance-readiness room participation, donor room participation, GRA-aligned finance-readiness work, AEP Passport finance-layer input, Nexus Rail finance-readiness input, Docket item, Grid input, or handoff-readiness shall not be described as finance approval.

**19.4.6.5** Finance-readiness language shall preserve unresolved dependencies, including public authority, procurement, technical, safeguard, provider, environmental, social, data, cyber, governance, and legal dependencies.

**19.4.6.6** Where ambiguity remains, the language shall be narrowed, no-reliance language shall be added, or the claim shall be withheld.

**19.4.6.7** Finance-Readiness Language Review records shall be correctionable. If reviewed language later creates reliance, finance signaling, insurance overclaim, donor overclaim, public finance overclaim, or transaction implication, it shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.4.7 Provider and Sponsor Language Review

**19.4.7.1** **Provider and Sponsor Language Review** shall be required for any claim, report, deck, website, press release, public-stage material, Nexus Universe material, National Model summary, Regional Cluster Program Plan summary, AEP Passport reference, Nexus Rail reference, Docket or Grid summary, handoff record, sponsor material, provider material, procurement material, media material, or public-safe communication that references a sponsor, partner, host, anchor, technical partner, provider candidate, public-good software contributor, enterprise participant, platform, operator, manufacturer, integrator, consultant, professional firm, infrastructure actor, or downstream handoff recipient.

**19.4.7.2** The review shall determine whether the language preserves support-without-control, provider-neutrality, procurement-neutrality, conflict disclosure, sponsor restrictions, mark-use permissions, contribution scope, public-safe listing permission, and permitted references.

**19.4.7.3** The review shall prohibit language that implies sponsor control, provider approval, preferred-provider status, procurement status, technical certification, financeability, public authority approval, community consent, Indigenous consent, project authorization, Nexus-ready status, AEP Passport status, Nexus Node status, or execution unless separately and lawfully recorded.

**19.4.7.4** Sponsor references shall distinguish funding or support from endorsement, control, authority, approval, and execution. Provider references shall distinguish contribution, candidate status, capability mapping, or demonstration from validation, selection, approval, and procurement.

**19.4.7.5** Heightened review shall apply where a sponsor is also a provider, capital actor, public authority participant, media actor, host, National Consortium Company participant, Project SPV participant, or downstream handoff recipient.

**19.4.7.6** Where ambiguity remains, sponsor and provider references shall be narrowed, marked as contribution-only, or withheld.

**19.4.7.7** Provider and Sponsor Language Review records shall be correctionable. If reviewed language later creates sponsor capture, provider validation, procurement advantage, finance signaling, public authority confusion, consent overclaim, or execution implication, it shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.4.8 Community and Indigenous Language Review

**19.4.8.1** **Community and Indigenous Language Review** shall be required for any claim, report, deck, website, press release, public-stage material, Nexus Universe material, National Model summary, Regional Cluster Program Plan summary, AEP Passport reference, Nexus Rail reference, Docket or Grid summary, handoff record, sponsor material, provider material, investor material, media material, or public-safe communication that references communities, Indigenous peoples, Tribal actors, rights-holders, protected knowledge holders, diaspora groups, youth, accessibility advocates, civil society, local institutions, traditional authorities, affected stakeholders, place-based legitimacy, social license, FPIC, consent, consultation, accommodation, land, culture, heritage, environmental justice, protected knowledge, or public-interest safeguards.

**19.4.8.2** The review shall determine whether the language accurately states capacity, represented scope if any, contribution type, confidentiality obligations, protected knowledge restrictions, publication permissions, safeguard conditions, consent-boundary language, data and privacy obligations, claims permissions, correction rights, and withdrawal rights.

**19.4.8.3** The review shall prohibit language that implies community consent, Indigenous consent, FPIC satisfaction, consultation completion, accommodation completion, social license, protected knowledge authorization, land access, site approval, cultural approval, environmental approval, rights-holder approval, local authorization, project approval, or execution unless separately and lawfully recorded.

**19.4.8.4** Community or Indigenous participation shall not be described as representative authority unless the relevant lawful record supports that exact capacity.

**19.4.8.5** Protected knowledge shall not be disclosed, summarized, translated, publicized, or routed beyond permission.

**19.4.8.6** Where ambiguity remains, the language shall be narrowed, consent-boundary language shall be added, or the claim shall be withheld.

**19.4.8.7** Community and Indigenous Language Review records shall be correctionable. If reviewed language later proves extractive, tokenistic, unsafe, consent-implying, protected-knowledge-exposing, misrepresentative, or execution-implying, it shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.4.9 No Public Warning by Reporting

**19.4.9.1** **No Public Warning by Reporting** shall mean that public-safe reporting by the Nexus Consortium Federation, including global, regional, national, Nexus Universe, National Model, Regional Cluster Program Plan, AEP Passport, Nexus Rail, Docket, Grid, safeguard, finance-readiness, public authority learning, correction, and handoff reporting, shall not constitute a public warning, emergency alert, public health warning, disaster warning, safety order, evacuation notice, regulatory notice, consumer warning, market warning, infrastructure warning, or other official warning unless issued by a competent public authority through separate lawful process.

**19.4.9.2** Public-safe reporting may describe risks, dependencies, learning themes, readiness questions, evidence limits, safeguard issues, correction items, and unresolved matters, but shall not instruct the public, command action, issue emergency guidance, substitute for public authority communications, or create official warning duties.

**19.4.9.3** Reports involving hazards, disasters, public health, infrastructure, cyber, security, environmental risk, humanitarian settings, conflict settings, or public safety shall include additional public-safe review to prevent warning confusion.

**19.4.9.4** Public-safe reports shall distinguish analysis, learning, observability, evidence, readiness, and dependency mapping from public warning or emergency command.

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

**19.4.9.6** Media and public-stage materials shall not use alarmist or directive language that could be mistaken for official public warning.

**19.4.9.7** Public-warning overclaims shall be corrected. If a report is interpreted as a public warning, emergency instruction, regulatory notice, or public authority communication without lawful authority, the report shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 19.4.10 Public-Safe Correction

**19.4.10.1** **Public-Safe Correction** shall be the process through which public-facing or externally circulated claims, reports, summaries, public-stage materials, Nexus Universe materials, websites, decks, press releases, sponsor materials, provider materials, investor materials, media materials, public authority materials, AEP Passport references, Nexus Rail references, Docket summaries, Grid summaries, handoff materials, National Model summaries, Regional Cluster Program Plan summaries, and archive materials are corrected in a manner that prevents reliance while preserving confidentiality and sensitivity.

**19.4.10.2** Public-Safe Correction may be required where a public or external claim is inaccurate, overbroad, outdated, superseded, unauthorized, misclassified, unsafe, reliance-producing, public-authority-overclaiming, finance-signaling, provider-validating, certification-implying, consent-implying, protected-knowledge-exposing, public-warning-implying, project-authorizing, or execution-implying.

**19.4.10.3** Public-Safe Correction measures may include correction notice, revised report, public-safe clarification, withdrawal notice, supersession notice, public listing update, mark-use correction, website correction, deck correction, press correction, media clarification, sponsor or provider notice, public authority reference correction, investor-material correction, handoff-recipient notice, archive notation, or restricted correction where public disclosure would increase harm.

**19.4.10.4** Public-Safe Correction shall not disclose confidential, restricted, public authority-sensitive, finance-sensitive, provider-sensitive, sponsor-sensitive, community-sensitive, Indigenous-sensitive where applicable, protected-knowledge-sensitive, cyber-sensitive, infrastructure-sensitive, security-sensitive, health-sensitive, humanitarian-sensitive, or not-for-publication information merely to correct a public claim.

**19.4.10.5** Public-Safe Correction shall identify what is corrected, what remains valid if anything, what is withdrawn or superseded, what limitations apply, and what reliance is prohibited, without creating new overclaims.

**19.4.10.6** Public-Safe Correction shall be linked to the relevant Claims Register, Public-Safe Reporting Register, Correction Register, source record, and archive record.

**19.4.10.7** Public-Safe Correction records shall themselves be correctionable. If a correction is incomplete, inaccurate, unsafe, confusing, publicized beyond permission, or fails to prevent reliance, the correction 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/xix.-claims.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.