# VI. NATIONAL

### 6.1 National Nexus Consortium Defined

#### 6.1.1 National Nexus Consortium as Country Gateway

**6.1.1.1** A **National Nexus Consortium** shall be the ordinary country-level gateway of the Nexus Consortium Federation. It is the national public-good formation layer through which Nexus participation, National Council formation, Helix Council formation, National Working Group formation, Nexus Competence Cell formation, National Model preparation, public authority learning, finance-readiness translation, safeguard review, Nexus Universe national mobilization, AEP Passport and Nexus Rail candidate routing, Docket and Grid input formation, public-safe reporting, and lawful enterprise handoff are organized within a country.

**6.1.1.2** The National Nexus Consortium shall be the normal entry point for country-level Nexus activity because national ownership must precede local delivery. Global Nexus doctrine and regional support shall be localized through the national gateway before being used for country-specific public claims, Nexus Universe national participation, National Model publication, AEP Passport references, Nexus Rail routing, public authority learning, finance-readiness materials, provider-neutral capability mapping, sponsor participation, community safeguard review, Indigenous protocol review where applicable, or enterprise handoff.

**6.1.1.3** The National Nexus Consortium shall receive and localize the common Nexus rail within the country’s own legal, institutional, public authority, linguistic, cultural, economic, technical, infrastructure, community, Indigenous where applicable, environmental, data, cyber, finance, insurance, donor, development, public finance, and implementation context. Such localization shall preserve the Federation’s common doctrine while making national differences visible in the record.

**6.1.1.4** The National Nexus Consortium shall function as a gateway, not as a monopoly, government, regulator, procurement authority, financial authority, certification body, public warning body, consent body, project developer, operator, contractor, or execution vehicle. It shall organize the public-good pathway through which country-level Nexus participation becomes legible, bounded, recorded, public-safe, and correctionable; it shall not itself become the lawful actor that approves, finances, procures, certifies, consents, commands, or executes.

**6.1.1.5** The country gateway function shall include, as applicable:

1. receiving global and regional Nexus doctrine for national localization;
2. forming the National Council, National Leadership Council, and National Investors Council;
3. forming National Helix Councils;
4. forming National Working Groups and Nexus Competence Cells;
5. preparing the National Model;
6. organizing national Nexus Universe preparation and delegation pathways;
7. supporting public authority learning without public authority substitution;
8. supporting finance-readiness without finance execution;
9. supporting provider-neutral capability mapping without provider validation;
10. supporting community, Indigenous, diaspora, youth, accessibility, protected knowledge, and place-based safeguard review without consent overclaim;
11. routing AEP Passport, Proof Receipt where authorized, Nexus Rail, Docket, and Grid inputs;
12. preparing public-safe reports; and
13. recording lawful handoff conditions where appropriate.

**6.1.1.6** No participant shall bypass the National Nexus Consortium in order to claim national Nexus standing through global participation, regional participation, sponsorship, provider contribution, public authority attendance, capital-reader interest, media visibility, university participation, Nexus Universe visibility, AEP Passport reference, Nexus Rail reference, Docket item, Grid input, National Consortium Company activity, Project SPV activity, or local project activity. Where an exceptional pathway is required, it shall be separately recorded, narrowly bounded, public-safe, and correctionable.

**6.1.1.7** Any claim that country gateway participation creates government approval, public authority endorsement, procurement eligibility, financeability, bankability, insurability, insurance approval, donor approval, public finance allocation, provider validation, certification, standards conformance, community consent, Indigenous consent, Nexus-ready status, AEP Passport status, Nexus Node status, project authorization, or execution authority shall be corrected.

***

#### 6.1.2 National Nexus Consortium as National Ownership Layer

**6.1.2.1** A National Nexus Consortium shall serve as the **national ownership layer** of the Federation. National ownership shall mean that country-level Nexus formation is organized through national records, national participation, national public authority learning, national stakeholder formation, national safeguard review, national finance-readiness translation, national public-safe reporting, national Nexus Universe preparation, and national handoff conditions before any local delivery or project-facing pathway is treated as Nexus-aligned.

**6.1.2.2** National ownership shall not mean state ownership, governmental control, public authority delegation, exclusive national control, political endorsement, procurement control, or execution authority. It means that the country’s Nexus pathway is formed through a nationally anchored public-good structure that respects the country’s own institutions, laws, communities, public authorities, universities, enterprises, infrastructure systems, finance context, data and cyber conditions, and safeguards.

**6.1.2.3** The National Nexus Consortium shall preserve national ownership by ensuring that country-specific Nexus work is not imposed by global bodies, regional headquarters, sponsors, providers, capital actors, donors, public authorities acting outside recorded capacity, universities, media actors, National Consortium Companies, Project SPVs, or project proponents. The national layer shall be the place where country-level participation is classified, national records are formed, and national conditions are attached to any route, report, or handoff.

**6.1.2.4** National ownership shall include, without limitation:

1. national stakeholder mapping;
2. national council and helix formation;
3. national public authority capacity classification;
4. national research, evidence, and technical participation;
5. national industry, infrastructure, enterprise, and provider-neutral capability mapping;
6. national capital-readability and finance-readiness translation;
7. national media, civic, and public-safe communication discipline;
8. national community, Indigenous where applicable, diaspora, youth, accessibility, protected knowledge, and place-based safeguard review;
9. National Model preparation;
10. national Nexus Universe delegation formation;
11. national AEP Passport and Nexus Rail candidate routing;
12. national Docket and Grid input formation; and
13. national lawful handoff conditions.

**6.1.2.5** National ownership shall remain compatible with global coordination and regional support. The Global Nexus Consortium may provide common doctrine and the Regional Headquarters Consortium may provide regional translation and country support, but neither shall own the national record, speak for the country by default, override national gateway formation, or convert global or regional visibility into national authority.

**6.1.2.6** National ownership shall protect local and place-based legitimacy. Local delivery, site activity, host readiness, provider demonstration, public authority learning, capital-reader interest, community participation, Indigenous participation where applicable, public-safe reporting, National Consortium Company activity, Project SPV-readiness, or project discussion shall remain connected to national records and shall not become detached transactions carrying unsupported Nexus legitimacy.

**6.1.2.7** National ownership shall be correctionable. Where national records become inaccurate, captured, overclaimed, unsafe, inconsistent with public authority status, inconsistent with safeguards, inconsistent with finance boundaries, or misused for execution implication, the National Nexus Consortium shall correct, narrow, restrict, withdraw, supersede, publicly clarify where necessary, or archive the relevant record.

***

#### 6.1.3 National Nexus Consortium as Public-Good Mandate Layer

**6.1.3.1** A National Nexus Consortium shall serve as the **national public-good mandate layer** of the Federation. Its mandate is to organize national participation, evidence formation, readiness mapping, public authority learning, finance-readiness translation, safeguard review, public-safe reporting, Nexus Universe mobilization, AEP Passport and Nexus Rail routing, Docket and Grid input formation, correction, renewal, and lawful handoff in a manner that preserves the public-good character of Nexus.

**6.1.3.2** The National Nexus Consortium’s public-good mandate shall be grounded in the Federation’s core doctrines: participation before execution; evidence before claims; readiness before finance; national ownership before local delivery; safeguard review before deployment; public authority learning before public authority action; public-good discipline before enterprise handoff; records before implied authority; non-execution; role separation; anti-capture; public-safe reporting; and correctionability.

**6.1.3.3** The National Nexus Consortium shall not use its public-good mandate to claim public authority status, regulate markets, approve projects, select providers, allocate finance, certify technologies, issue public warnings, represent community consent, represent Indigenous consent, conduct procurement, act as an investment platform, or execute enterprise activity. Its public-good mandate shall be formation, learning, readiness, reporting, routing, safeguarding, and correction.

**6.1.3.4** The public-good mandate shall include the duty to maintain a national public-good firewall. The National Nexus Consortium shall prevent public-good legitimacy from being captured by sponsors, providers, capital actors, public authorities, founders, universities, media actors, National Consortium Companies, Project SPVs, or project proponents. Public-good records shall not be controlled by enterprise interests or converted into commercial claims without lawful handoff and proper boundary language.

**6.1.3.5** The public-good mandate shall allow engagement with powerful and necessary actors while preserving boundaries. The National Nexus Consortium may engage governments, regulators, public authorities, universities, enterprises, infrastructure actors, technology providers, capital readers, insurers, donors, development actors, sponsors, hosts, media, civil society, communities, Indigenous actors where applicable, diaspora contributors, youth actors, National Consortium Companies, and Project SPVs, provided each actor participates in recorded capacity and no actor converts participation into authority.

**6.1.3.6** The public-good mandate shall require the National Nexus Consortium to maintain records sufficient to show what has been formed, what remains unresolved, what is public-safe, what is restricted, what has been corrected, what has been withdrawn, what has been superseded, what has been archived, and what may be routed or handed off. The public-good mandate shall be valid only through records.

**6.1.3.7** Any use of the National Nexus Consortium’s public-good mandate to imply government endorsement, public authority approval, procurement status, financeability, provider validation, certification, community consent, Indigenous consent, project approval, public warning, emergency command, or execution shall be treated as a boundary incident and corrected.

***

#### 6.1.4 National Nexus Consortium as National Stakeholder Platform

**6.1.4.1** A National Nexus Consortium shall serve as the **national stakeholder platform** for Nexus participation in the country. It shall provide the structured public-good surface through which individual leaders, institutional actors, public authorities, universities, research bodies, enterprises, infrastructure actors, technology providers, capital readers, insurers, donors, development actors, media bodies, civic actors, civil society organizations, communities, Indigenous actors where applicable, diaspora contributors, youth, accessibility advocates, sponsors, hosts, partners, National Consortium Companies, Project SPVs, and other relevant actors may participate in country-level Nexus formation.

**6.1.4.2** The national stakeholder platform shall be organized through gateway discipline. Individual participation shall normally be routed through the National Council, including the National Leadership Council and National Investors Council. Institutional participation shall normally be routed through the Helix Councils. Task-specific work shall be routed through National Working Groups. Capability formation shall be routed through Nexus Competence Cells. Enterprise and project pathways shall be routed only through lawful handoff and separate enterprise-stack or project-vehicle processes.

**6.1.4.3** The National Nexus Consortium shall classify stakeholders by role and capacity. A participant may be recorded as a public authority learner, researcher, technical contributor, provider, sponsor, host, capital reader, insurer, donor, development actor, media contributor, civic actor, community participant, Indigenous participant where applicable, diaspora contributor, youth participant, accessibility contributor, National Consortium Company interface, Project SPV interface, or other lawful category. No participant shall be permitted to rely on unrecorded capacity.

**6.1.4.4** The national stakeholder platform shall be inclusive but not unbounded. Participation shall be open to relevant national actors according to the applicable gateway, but each participant shall be subject to conflict disclosure, claims discipline, public-safe reporting controls, data and confidentiality obligations, sponsor and provider boundary controls, finance no-reliance controls, public authority capacity classification, safeguard restrictions, and correction.

**6.1.4.5** The National Nexus Consortium shall use stakeholder participation to form better national records, not to manufacture endorsement. Participation by a ministry, agency, regulator, public official, investor, insurer, donor, company, university, media body, community representative, Indigenous actor, sponsor, provider, or project actor shall not be used to imply approval, commitment, financeability, procurement status, certification, consent, public authority action, or project authorization.

**6.1.4.6** The national stakeholder platform shall be protected against capture. No single stakeholder category, including public authorities, sponsors, providers, capital actors, founders, universities, media actors, communities, Indigenous actors, National Consortium Companies, or Project SPVs, shall dominate the National Nexus Consortium in a manner that distorts public-good records, suppresses safeguards, converts participation into endorsement, or collapses public-good and enterprise roles.

**6.1.4.7** Stakeholder platform records shall be correctionable. If a stakeholder is misclassified, overclaims status, misuses participation, creates conflict risk, misstates public authority or finance status, implies provider validation, implies community or Indigenous consent, misuses Nexus marks, or causes public-safe reporting risk, the National Nexus Consortium shall correct, restrict, suspend, reclassify, withdraw, publicly clarify where necessary, or archive the relevant record.

***

#### 6.1.5 National Nexus Consortium as National Model Formation Layer

**6.1.5.1** A National Nexus Consortium shall serve as the **National Model formation layer** for the country. The **National Model** shall be the country-level public-good record through which national Nexus participation, evidence, public authority context, finance-readiness, technical readiness, infrastructure readiness, community and Indigenous safeguards where applicable, public-safe reporting, Nexus Universe outputs, AEP Passport candidate layers, Nexus Rail candidates, Docket items, Grid inputs, and handoff conditions are organized into a coherent national formation record.

**6.1.5.2** The National Model shall be a readiness and learning record, not a national policy by implication, public authority decision, procurement plan, investment memorandum, donor plan, public finance allocation, certification, standards-conformance record, community consent instrument, Indigenous consent instrument, project approval, implementation plan by default, or execution mandate.

**6.1.5.3** National Model formation shall draw from the National Council, National Leadership Council, National Investors Council, Helix Councils, National Working Groups, Nexus Competence Cells, public authority learning rooms, finance-readiness rooms, technical and evidence records, provider-neutral capability maps, public-safe reporting records, community and safeguard records, Nexus Universe cycle records, AEP Passport and Nexus Rail candidate records, Docket and Grid records, and lawful handoff records where appropriate.

**6.1.5.4** The National Model may include, as applicable:

1. country context and national gateway status;
2. national stakeholder map;
3. national risk and resilience priorities;
4. public authority learning context;
5. technical, evidence, observability, data, AI, cyber, and infrastructure readiness records;
6. finance-readiness, insurance-readiness, donor relevance, development-readiness, and public finance relevance records;
7. provider-neutral capability maps;
8. sponsor, host, and partner boundary records;
9. community, Indigenous, diaspora, youth, accessibility, protected knowledge, and place-based safeguard records;
10. public-safe reporting classifications;
11. Nexus Universe national preparation and cycle records;
12. AEP Passport and Proof Receipt inputs where authorized;
13. Nexus Rail candidate routes;
14. Docket items and Grid inputs;
15. National Consortium Company and Project SPV interface conditions where applicable; and
16. correction, renewal, withdrawal, supersession, and archive records.

**6.1.5.5** National Model formation shall preserve unresolved issues. A public authority dependency shall remain a dependency; a finance-readiness gap shall remain a gap; a safeguard condition shall remain attached; a protected knowledge restriction shall remain restricted; a provider-neutral capability record shall not become provider selection; a community input shall not become consent; an Indigenous protocol note where applicable shall not become Indigenous consent; and a project concept shall not become project authorization.

**6.1.5.6** The National Model shall support Nexus Universe national participation by identifying what is ready for public presentation, what must remain controlled, what requires public authority room review, what requires finance-readiness room review, what requires safeguard room review, what can enter AEP Passport or Nexus Rail routing, what should become a Docket item, what can become a Grid input, what requires correction, and what may be considered for lawful handoff.

**6.1.5.7** The National Model shall be correctionable and renewable. If national conditions change, public authority status changes, finance-readiness is overstated, safeguards are incomplete, protected knowledge risks arise, provider-neutrality is compromised, public-safe reporting becomes unsafe, Nexus Universe outputs are overclaimed, or handoff conditions are misused, the National Model shall be corrected, narrowed, restricted, withdrawn, superseded, publicly clarified where necessary, renewed, or archived.

***

#### 6.1.6 National Nexus Consortium as Lawful Enterprise Handoff Layer

**6.1.6.1** A National Nexus Consortium shall serve as the national **lawful enterprise handoff layer** where eligible public-good records, readiness outputs, safeguard conditions, public authority dependency notes, finance-readiness notes, technical evidence records, Nexus Universe outputs, AEP Passport candidate layers, Proof Receipt inputs where authorized, Nexus Rail inputs, Docket items, Grid inputs, National Model elements, public-safe reports, or other national Nexus records may be transmitted to competent downstream actors under bounded, recorded, non-executing conditions.

**6.1.6.2** Lawful enterprise handoff shall not mean execution by the National Nexus Consortium. It shall mean the controlled transition of a public-good record into the consideration of a competent external actor, which may include a public authority, National Consortium Company, Project SPV, provider, host, operator, investor, insurer, donor, development finance actor, procurement body, community process, Indigenous governance process where applicable, research institution, technical body, or other lawful actor.

**6.1.6.3** The National Nexus Consortium shall remain on the public-good side of the handoff. It may create, classify, limit, route, publish public-safe summaries, attach safeguards, identify dependencies, correct records, and transmit handoff conditions. It shall not approve the downstream action, finance the project, underwrite insurance, allocate public finance, procure services, select vendors, issue public authority approval, certify systems, grant consent, authorize land access, execute contracts, operate infrastructure, or manage implementation.

**6.1.6.4** A lawful enterprise handoff record shall identify, at minimum:

1. originating National Nexus Consortium record;
2. record version, status, and correction history;
3. recipient and recipient capacity;
4. purpose of handoff;
5. evidence basis and limitations;
6. unresolved dependencies;
7. public authority dependencies;
8. finance, insurance, donor, development, and public finance dependencies;
9. procurement dependencies;
10. provider-neutrality and sponsor-boundary conditions;
11. community, Indigenous where applicable, diaspora, youth, accessibility, protected knowledge, and place-based safeguard conditions;
12. data, privacy, cyber, infrastructure, humanitarian, health, public authority-sensitive, and security-sensitive restrictions where applicable;
13. public-safe communication limits;
14. permitted and prohibited claims;
15. non-reliance or reliance limitations as applicable;
16. correction, withdrawal, and archive rights; and
17. express non-execution language.

**6.1.6.5** National Consortium Companies and Project SPVs shall be treated as separate enterprise-stack or project-vehicle recipients, not as extensions of the National Nexus Consortium. Their formation, governance, capitalization, contracts, procurement, finance, insurance, permits, safeguards, community processes, Indigenous protocols where applicable, data and cyber obligations, operations, liabilities, and execution responsibilities shall remain separate.

**6.1.6.6** Lawful enterprise handoff shall not create approval. A handoff record shall not by itself create public authority approval, regulatory comfort, procurement status, investment approval, financeability, bankability, insurability, insurance approval, donor approval, public finance allocation, development finance approval, provider validation, certification, standards conformance, community consent, Indigenous consent, protected knowledge authorization, land access, site approval, Nexus-ready status, AEP Passport status, Nexus Node status, project authorization, or execution authority.

**6.1.6.7** Lawful enterprise handoff shall remain correctionable after transmission. If a handoff recipient strips limitations, suppresses safeguards, overstates finance-readiness, implies public authority approval, misuses provider-neutral records, misstates community or Indigenous status, exposes protected knowledge, misuses Nexus Universe outputs, or implies National Nexus Consortium execution, the National Nexus Consortium shall correct, restrict, withdraw, supersede, publicly clarify where necessary, or archive the handoff record.

***

#### 6.1.7 National Nexus Consortium Identity Statement

**6.1.7.1** A **National Nexus Consortium** is the country gateway, national ownership layer, national public-good mandate layer, national stakeholder platform, National Model formation layer, Nexus Universe national mobilization layer, and lawful enterprise handoff layer of the Nexus Consortium Federation. It gives Nexus a nationally anchored public-good structure without becoming a government, regulator, procurement body, finance body, certification body, public warning body, consent body, project developer, operator, contractor, or execution vehicle.

**6.1.7.2** Its identity is national in ownership and federated in alignment. It receives global Nexus doctrine through the common rail, receives regional support through the Regional Headquarters Consortium, and localizes both into the country’s legal, institutional, public authority, finance, technical, infrastructure, community, Indigenous where applicable, data, cyber, environmental, linguistic, and cultural context.

**6.1.7.3** Its identity is public-good-rooted and non-executing. It organizes participation before execution, evidence before claims, readiness before finance, national ownership before local delivery, safeguard review before deployment, public authority learning before public authority action, public-good discipline before enterprise handoff, and records before implied authority.

**6.1.7.4** Its identity is stakeholder-facing but claims-limited. It may convene individual leaders, investors, public authorities, researchers, universities, enterprises, infrastructure actors, providers, sponsors, hosts, capital readers, insurers, donors, media, civic actors, communities, Indigenous actors where applicable, diaspora contributors, youth, accessibility advocates, National Consortium Companies, Project SPVs, and other lawful actors. Their participation shall create records and learning, not approval or authority by implication.

**6.1.7.5** Its identity is model-forming. It forms the National Model as the country-level public-good record that makes national Nexus participation, readiness, safeguards, public authority context, finance-readiness, Nexus Universe outputs, AEP Passport and Nexus Rail candidates, Docket and Grid items, public-safe reporting, correction, renewal, and handoff conditions legible.

**6.1.7.6** Its identity is handoff-aware but not executing. It may route mature and bounded public-good records to competent downstream actors, including National Consortium Companies and Project SPVs where lawfully formed, but it shall not become the actor that approves, finances, procures, certifies, consents, contracts, operates, or executes.

**6.1.7.7** Its identity is correctionable. It shall maintain the ability to correct national participation records, stakeholder classifications, council records, helix records, working-group outputs, competence-cell outputs, National Model elements, Nexus Universe materials, AEP Passport references, Nexus Rail references, Docket items, Grid inputs, public-safe reports, sponsor and provider references, public authority references, finance-readiness statements, safeguard records, and handoff records whenever they become inaccurate, unsafe, overbroad, superseded, misused, or inconsistent with Nexus doctrine.

**6.1.7.8** A National Nexus Consortium shall therefore be understood as a **public-good, non-executing, role-separated, anti-capture, record-based, correctionable national gateway that anchors Nexus in country ownership, organizes national stakeholders, forms the National Model, prepares national Nexus Universe participation, preserves safeguards, disciplines claims, routes AEP Passport and Nexus Rail candidates, maintains Docket and Grid inputs, and enables lawful handoff without becoming the authority that approves, finances, procures, certifies, regulates, consents, commands, or executes.**

### 6.2 National Mandate

#### 6.2.1 National Gateway Mandate

**6.2.1.1** Each **National Nexus Consortium** shall hold the **National Gateway Mandate** for its country. The National Gateway Mandate shall mean the authority, within the non-executing public-good architecture of the Nexus Consortium Federation, to receive, localize, organize, classify, record, route, safeguard, report in public-safe form, correct, renew, and hand off country-level Nexus participation, records, and readiness outputs through the national public-good gateway.

**6.2.1.2** The National Gateway Mandate shall ensure that Nexus does not enter a country as a purely global, regional, sponsor-led, provider-led, finance-led, event-led, public authority-adjacent, media-led, project-led, or enterprise-led activity without national formation. Country-level Nexus activity shall ordinarily be anchored through the National Nexus Consortium before being represented as national Nexus participation, National Model formation, Nexus Universe participation, AEP Passport candidate activity, Nexus Rail routing, public-safe reporting, finance-readiness, public authority learning, or lawful handoff.

**6.2.1.3** The National Gateway Mandate shall include, without limitation:

1. receiving global Nexus doctrine and regional translation materials;
2. localizing Nexus doctrine into the national legal, institutional, public authority, community, Indigenous where applicable, finance, data, cyber, environmental, linguistic, cultural, and implementation context;
3. maintaining national participation pathways;
4. forming National Councils and Helix Councils;
5. forming National Working Groups and Nexus Competence Cells;
6. preparing the National Model;
7. organizing national Nexus Universe participation;
8. forming national public-good records;
9. maintaining public-safe reporting discipline;
10. routing AEP Passport, Proof Receipt where authorized, Nexus Rail, Docket, and Grid inputs;
11. preparing lawful handoff conditions; and
12. correcting, renewing, restricting, withdrawing, superseding, or archiving national records.

**6.2.1.4** The National Gateway Mandate shall not create public authority status. The National Nexus Consortium shall not be treated as a government, ministry, agency, regulator, municipality, Indigenous or Tribal governance body, public finance authority, public procurement authority, emergency authority, public warning body, public health authority, infrastructure authority, data authority, legislature, court, or other public-law decision-maker.

**6.2.1.5** The National Gateway Mandate shall not create exclusive market control. The National Nexus Consortium shall not use gateway status to become a procurement gatekeeper, provider marketplace, investment platform, certification body, project developer, contractor, operator, public authority substitute, consent body, or execution vehicle.

**6.2.1.6** The National Gateway Mandate shall require national routing discipline. A sponsor, provider, host, public authority participant, capital reader, insurer, donor, development actor, university, media body, community actor, Indigenous actor where applicable, National Consortium Company, Project SPV, or project proponent shall not claim national Nexus standing unless the relevant national gateway record supports the claim.

**6.2.1.7** Any misuse of the National Gateway Mandate to imply governmental approval, public authority endorsement, procurement status, financeability, bankability, insurability, insurance approval, donor approval, public finance allocation, provider validation, certification, standards conformance, community consent, Indigenous consent, Nexus-ready status, AEP Passport status, Nexus Node status, project authorization, public warning, emergency command, or execution authority shall be corrected.

***

#### 6.2.2 National Public-Good Participation Mandate

**6.2.2.1** Each National Nexus Consortium shall hold the **National Public-Good Participation Mandate**. This mandate shall require the National Nexus Consortium to organize national participation as a public-good formation process, not as a procurement channel, investment pipeline, provider marketplace, political endorsement mechanism, public authority substitute, project approval process, or consent mechanism.

**6.2.2.2** National public-good participation shall be open to relevant national actors through proper gateway classification. Individual participation shall ordinarily be organized through the National Council, including the National Leadership Council and National Investors Council. Institutional participation shall ordinarily be organized through the Helix Councils. Task-specific work shall be organized through National Working Groups. Capability formation shall be organized through Nexus Competence Cells. Enterprise and project pathways shall be handled only through lawful handoff into separate competent processes.

**6.2.2.3** The National Public-Good Participation Mandate shall include participation by, as appropriate:

1. national leaders, experts, and public-good contributors;
2. individual capital readers and investment-literate participants;
3. public authorities in recorded learning or other lawful capacities;
4. universities, research institutions, laboratories, and scientific bodies;
5. enterprises, infrastructure actors, technology providers, hosts, operators, and industry bodies;
6. capital readers, investors, insurers, reinsurers, donors, development actors, philanthropic actors, and public finance readers;
7. media, civic, civil society, public-interest, accessibility, and information-integrity actors;
8. communities, Indigenous actors where applicable, diaspora contributors, youth, place-based actors, rights-aware participants, and protected knowledge holders where appropriate;
9. sponsors, hosts, partners, contributors, and public-good supporters;
10. National Consortium Companies and Project SPVs only as separate enterprise-stack or project-vehicle interfaces; and
11. other actors lawfully relevant to national Nexus formation.

**6.2.2.4** The National Public-Good Participation Mandate shall require that each participant be classified by role, capacity, gateway, level, contribution type, conflicts, publication permissions, claims permissions, data and confidentiality obligations, public authority status, finance status, provider or sponsor status, safeguard relevance, and correction pathway.

**6.2.2.5** Public-good participation shall create standing to contribute only within the recorded pathway. It shall not create board appointment, governance control, public authority status, procurement status, finance authority, investment opportunity, insurance approval, donor commitment, provider validation, certification, community consent, Indigenous consent, project authorization, Nexus-ready status, AEP Passport status, Nexus Node status, or execution rights.

**6.2.2.6** The National Nexus Consortium shall preserve inclusive participation without allowing tokenization, capture, or overclaim. Participation by communities, Indigenous actors where applicable, public authorities, capital readers, sponsors, providers, media, universities, or enterprises shall not be used decoratively or extractively, nor shall it be converted into implied approval, consent, legitimacy, financeability, or authority.

**6.2.2.7** National public-good participation shall remain correctionable. Participant classification, public listing, claims permission, room access, contribution status, sponsor status, provider status, public authority status, finance-readiness role, safeguard role, or handoff role may be corrected, restricted, suspended, withdrawn, superseded, or archived where inaccurate, unsafe, overclaimed, conflicted, captured, or misused.

***

#### 6.2.3 National Council Formation Mandate

**6.2.3.1** Each National Nexus Consortium shall hold the **National Council Formation Mandate**. This mandate shall require the National Nexus Consortium to form, maintain, classify, renew, and correct the National Council as the principal individual participation layer for national leadership, national public-good stewardship, capital-readability, investor literacy, Nexus Universe delegation readiness, National Model contribution, public-safe reporting input, and lawful handoff awareness.

**6.2.3.2** The National Council shall include, at minimum, two principal sub-councils:

1. the **National Leadership Council**, serving as the national individual leadership, stewardship, agenda-formation, public-good judgment, national systems insight, Nexus Universe mobilization, and leadership-pool layer; and
2. the **National Investors Council**, serving as the national individual capital-reader, investor-literacy, finance-readiness, insurance-readiness, donor-relevance, public finance relevance, diligence-gap, Project SPV-readiness, and no-reliance finance-readiness participation layer.

**6.2.3.3** National Council formation shall be governed by a recorded council mandate identifying the council’s purpose, composition, eligibility, participation levels, term, renewal rules, public listing status, claims rules, conflicts rules, meeting rules, records, Nexus Universe role, public-safe reporting role, Docket and Grid role, AEP Passport and Nexus Rail relevance, lawful handoff limits, and correction pathway.

**6.2.3.4** National Council participants shall participate in individual capacity unless the record expressly states another capacity. Institutional affiliation, public office, investor status, donor status, sponsor affiliation, provider affiliation, academic title, media visibility, community role, Indigenous role where applicable, or enterprise role shall be disclosed and classified, but shall not by itself convert the participant’s council status into institutional endorsement or authority.

**6.2.3.5** The National Leadership Council may support national agenda formation, leadership-pool identification, National Model input, Nexus Universe delegation preparation, public-safe reporting input, public authority learning awareness, national stakeholder formation, and working-group referrals. It shall not appoint public authorities, approve projects, select providers, allocate finance, certify systems, grant consent, or execute.

**6.2.3.6** The National Investors Council may support finance-readiness, capital-readability, insurance-readiness, donor relevance, public finance relevance, risk-to-capital translation, diligence-gap mapping, no-reliance capital-reader rooms, Project SPV-readiness questions, AEP Passport finance-layer input, Nexus Rail finance-readiness input, and Nexus Universe capital-reader preparation. It shall not provide investment advice, financial advice, insurance advice, securities offering, capital solicitation, underwriting, guarantee, donor approval, public finance allocation, financeability, bankability, insurability, or transaction readiness.

**6.2.3.7** National Council formation shall remain correctionable. If the National Council or either sub-council becomes captured, overclaims status, implies board authority, implies public authority approval, creates finance signaling, produces provider advantage, suppresses safeguards, misuses community or Indigenous participation, or becomes an execution proxy, the National Nexus Consortium shall correct, restrict, reconstitute, suspend, renew on corrected terms, or archive the relevant council records.

***

#### 6.2.4 National Helix Council Formation Mandate

**6.2.4.1** Each National Nexus Consortium shall hold the **National Helix Council Formation Mandate**. This mandate shall require the National Nexus Consortium to form, maintain, classify, renew, and correct institutional participation through Helix Councils that reflect the public authority, research, enterprise, capital, civic, media, community, Indigenous where applicable, diaspora, youth, accessibility, and place-based legitimacy dimensions of the national Nexus ecosystem.

**6.2.4.2** The National Helix Council architecture shall include the following gateway families:

1. **Government / Public Authority Helix Council**;
2. **Academia / Research / Science Helix Council**;
3. **Industry / Enterprise / Infrastructure / Technology Helix Council**;
4. **Capital / Insurance / Donor / Development Helix Council**;
5. **Media / Civic / Public-Interest Helix Council**; and
6. **Community / Indigenous / Diaspora / Place-Based Legitimacy Helix Council**.

**6.2.4.3** Each Helix Council shall operate under a recorded mandate identifying its purpose, composition, eligibility, participation categories, role classifications, conflicts rules, claims rules, public-safe reporting duties, Nexus Universe role, National Model role, Working Group referral role, Competence Cell interface, AEP Passport and Nexus Rail relevance, Docket and Grid relevance, safeguard obligations, publication class rules, lawful handoff limits, and correction pathway.

**6.2.4.4** The Government / Public Authority Helix Council shall support public authority learning, public authority capacity classification, public-safe dashboard review, Government Portfolio preparation, public finance relevance awareness, procurement-neutral learning, regulatory learning, and public authority dependency records. It shall not create public authority approval, delegation, endorsement, policy adoption, regulatory comfort, procurement status, public finance allocation, emergency command, public warning, or project authorization.

**6.2.4.5** The Academia / Research / Science Helix Council shall support evidence, methods, research integrity, scientific review, public-good software, open technical baselines, observability methods, Nexus Academy inputs, system cards, benchmark cards, National Model evidence, AEP Passport technical layers, Nexus Rail technical dependencies, and Docket or Grid evidence inputs. It shall not create certification, accreditation, standards conformance, technical approval, provider validation, or public authority approval.

**6.2.4.6** The Industry / Enterprise / Infrastructure / Technology Helix Council shall support provider-neutral capability mapping, infrastructure readiness, host and operator readiness, technical demonstration discipline, Nexus Core contribution, public-good software contribution, AEP Passport operational layers, Nexus Rail implementation-readiness inputs, National Consortium Company interface awareness, and Project SPV-readiness questions. It shall not create procurement status, provider selection, provider validation, product approval, certification, financeability, or execution authority.

**6.2.4.7** The Capital / Insurance / Donor / Development Helix Council shall support finance-readiness, capital-readability, insurance-readiness, reinsurance-readiness, donor relevance, development-readiness, public finance relevance, disaster-risk finance question formation, diligence-gap mapping, proof-pack readability, Project SPV-readiness, AEP Passport finance layers, Nexus Rail finance-readiness inputs, and no-reliance room discipline. It shall not create investment advice, financial advice, insurance advice, underwriting, guarantee, financeability, bankability, insurability, donor approval, development finance approval, public finance allocation, or transaction readiness.

**6.2.4.8** The Media / Civic / Public-Interest Helix Council shall support public meaning, public-safe reporting, civic trust, information integrity, accessibility, plain-language communication, public-interest review, claims discipline, media boundary discipline, public narrative safeguards, misinformation risk review, and public-safe Nexus Universe reporting. It shall not create public relations capture, public warning authority, government endorsement, certification, investment signaling, provider promotion, or project approval.

**6.2.4.9** The Community / Indigenous / Diaspora / Place-Based Legitimacy Helix Council shall support lived-risk knowledge, community safeguards, Indigenous protocol awareness where applicable, protected knowledge caution, diaspora contribution, youth and future-generation perspectives, accessibility, local implementation reality, place-based legitimacy, safeguard records, AEP Passport safeguard layers, Nexus Rail safeguard conditions, public-safe reporting limits, and handoff restrictions. It shall not create community consent, Indigenous consent, FPIC satisfaction, social license, protected knowledge authorization, land access, cultural approval, environmental approval, project approval, or execution authority.

**6.2.4.10** Helix Council formation shall remain correctionable. If a helix is misbalanced, captured, overclaimed, tokenistic, under-recorded, unsafe, used as approval, used as finance signal, used as provider validation, used as public authority endorsement, or used as consent evidence, the National Nexus Consortium shall correct, restrict, reconstitute, suspend, renew on corrected terms, or archive the relevant helix records.

***

#### 6.2.5 National Working Group Formation Mandate

**6.2.5.1** Each National Nexus Consortium shall hold the **National Working Group Formation Mandate**. This mandate shall permit and require the National Nexus Consortium to form task-specific, time-bound, role-classified National Working Groups where councils, helixes, public authority learning, finance-readiness, safeguard review, Nexus Universe preparation, National Model formation, AEP Passport routing, Nexus Rail routing, Docket items, Grid inputs, or lawful handoff questions require structured work.

**6.2.5.2** A National Working Group shall be formed only by recorded mandate. The mandate shall identify the Working Group’s name, purpose, scope, convening pathway, originating council or helix, participants, chairing or facilitation structure, records responsibilities, evidence basis, public authority boundaries, finance boundaries, provider-neutrality conditions, sponsor controls, safeguard requirements, data and confidentiality rules, publication class, expected outputs, Nexus Universe relevance, AEP Passport and Nexus Rail relevance, Docket and Grid relevance, lawful handoff limits, correction pathway, term, renewal rule, and closure conditions.

**6.2.5.3** National Working Groups may be formed around sectors, systems, risks, technologies, regions within the country, public authority issues, finance-readiness issues, community safeguard issues, National Model components, Nexus Universe deliverables, AEP Passport candidate layers, Nexus Rail candidates, Docket items, Grid inputs, or Project SPV-readiness questions.

**6.2.5.4** National Working Groups may address, as applicable, AI, AI-RAN, O-RAN, private wireless, cyber, compute, data, geospatial systems, Earth observation, digital twins, robotics, drones, sensing, blockchain-relevant infrastructure, quantum-relevant systems, advanced manufacturing, semiconductors, water, energy, food, health, biodiversity, climate, disaster risk, logistics, public finance relevance, insurance-readiness, protected knowledge, public-safe reporting, community safeguards, Indigenous protocols where applicable, and enterprise handoff pathways.

**6.2.5.5** National Working Groups shall produce records, not approvals. Their outputs may include evidence notes, method notes, readiness notes, dependency maps, safeguard records, community-risk notes, Indigenous protocol notes where applicable, public authority dependency notes, finance-readiness questions, provider-neutral capability maps, public-safe reporting inputs, Nexus Universe preparation records, AEP Passport inputs, Nexus Rail candidates, Docket items, Grid inputs, and handoff restriction notes.

**6.2.5.6** National Working Groups shall not become execution teams. They shall not procure, contract, select vendors, approve providers, approve projects, raise capital, underwrite insurance, issue public warnings, act as public authorities, certify systems, grant consent, authorize deployment, operate infrastructure, or manage implementation.

**6.2.5.7** National Working Group formation shall remain correctionable. A Working Group may be narrowed, suspended, reconstituted, renewed, closed, or archived where it exceeds mandate, becomes captured, produces unsafe outputs, omits safeguards, creates provider advantage, implies public authority approval, implies financeability, implies consent, or suggests execution authority.

***

#### 6.2.6 National Model Preparation Mandate

**6.2.6.1** Each National Nexus Consortium shall hold the **National Model Preparation Mandate**. This mandate shall require the National Nexus Consortium to prepare, maintain, classify, correct, renew, and archive the **National Model** as the principal country-level public-good record of Nexus participation, evidence, readiness, public authority context, finance-readiness, safeguard conditions, Nexus Universe outputs, AEP Passport and Nexus Rail candidates, Docket and Grid inputs, public-safe reporting, and lawful handoff conditions.

**6.2.6.2** The National Model shall be a national formation and readiness record. It shall not be a national law, public policy adoption, government plan, procurement plan, investment memorandum, donor plan, public finance allocation, certification record, standards-conformance record, community consent instrument, Indigenous consent instrument, environmental approval, project authorization, implementation plan by default, or execution mandate.

**6.2.6.3** The National Model shall be prepared from recorded inputs, including National Council records, Helix Council records, National Working Group records, Nexus Competence Cell records, public authority learning notes, finance-readiness notes, evidence and method records, provider-neutral capability maps, sponsor and partner records, safeguard records, public-safe reporting classifications, Nexus Universe cycle records, AEP Passport and Proof Receipt inputs where authorized, Nexus Rail records, Docket items, Grid inputs, and lawful handoff records.

**6.2.6.4** The National Model shall identify, as applicable:

1. national context and gateway status;
2. national institutional and stakeholder map;
3. national risk and resilience priorities;
4. technology and infrastructure readiness;
5. evidence, methods, observability, data, AI, cyber, and public-good software inputs;
6. public authority learning and public authority dependencies;
7. finance-readiness, insurance-readiness, donor relevance, development-readiness, public finance relevance, and capital-readability inputs;
8. provider-neutral capability and host-readiness inputs;
9. sponsor, host, partner, and provider boundary records;
10. community, Indigenous where applicable, diaspora, youth, accessibility, protected knowledge, and place-based safeguard records;
11. public-safe reporting classes;
12. Nexus Universe preparation and cycle records;
13. AEP Passport, Proof Receipt where authorized, Nexus Rail, Docket, and Grid inputs;
14. National Consortium Company and Project SPV interface conditions where applicable;
15. lawful handoff conditions; and
16. correction, renewal, withdrawal, supersession, and archive history.

**6.2.6.5** The National Model shall preserve unresolved issues. Dependencies, gaps, safeguards, limitations, restrictions, sensitivities, external authorities, finance limits, procurement limits, public authority limits, consent limits, data limits, cyber limits, and correction items shall remain visible and shall not be erased for narrative clarity, sponsor value, provider visibility, capital-reader interest, public authority comfort, media simplicity, or Nexus Universe presentation.

**6.2.6.6** The National Model shall support but not predetermine Nexus Universe participation and lawful handoff. It may identify what can be presented publicly, what must remain controlled, what may enter public authority rooms, what may enter finance-readiness rooms, what may enter safeguard rooms, what may become AEP Passport or Nexus Rail input, what should become Docket or Grid input, and what may be considered for handoff. It shall not itself approve any of those downstream outcomes.

**6.2.6.7** The National Model shall be correctionable and renewable at least annually and whenever material changes occur. If the National Model becomes inaccurate, overclaimed, outdated, unsafe, inconsistent with public authority status, inconsistent with safeguards, inconsistent with finance boundaries, inconsistent with provider-neutrality, inconsistent with data restrictions, or misused for execution implication, it shall be corrected, narrowed, restricted, withdrawn, superseded, publicly clarified where necessary, renewed, or archived.

***

#### 6.2.7 National Nexus Universe Mobilization Mandate

**6.2.7.1** Each National Nexus Consortium shall hold the **National Nexus Universe Mobilization Mandate**. This mandate shall require the National Nexus Consortium to prepare the country for participation in the annual Nexus Universe cycle through national records, national delegations, National Model inputs, public authority learning rooms, finance-readiness rooms, technical and evidence rooms, provider-neutral demonstration conditions, safeguard rooms, public-safe reporting pathways, AEP Passport and Nexus Rail candidates, Docket and Grid inputs, and post-cycle correction and renewal.

**6.2.7.2** National Nexus Universe mobilization shall operate across the full annual rhythm of the Federation, including year-long national preparation, one-month Nexus Core build support, one-week live operation participation, post-cycle public-safe reporting and correction, and next-cycle renewal.

**6.2.7.3** The National Nexus Consortium shall prepare, as applicable:

1. national annual priorities;
2. national delegation records;
3. National Council and Helix Council participation pathways;
4. National Working Group and Nexus Competence Cell outputs;
5. National Model presentation materials;
6. public authority learning room participation;
7. capital-reader, insurance-readiness, donor, development, and public finance relevance room participation;
8. technical, evidence, observability, data, AI, cyber, infrastructure, and public-good software room participation;
9. provider-neutral demonstration conditions;
10. community, Indigenous where applicable, diaspora, youth, accessibility, protected knowledge, and safeguard room participation;
11. media, civic, public-interest, and public-safe reporting participation;
12. AEP Passport and Proof Receipt input pathways where authorized;
13. Nexus Rail candidate routing;
14. Docket and Grid intake;
15. lawful handoff discussion controls; and
16. correction, withdrawal, archive, and renewal protocols.

**6.2.7.4** National Nexus Universe mobilization shall be record-led. No national output, project concept, provider demonstration, public authority reference, finance-readiness note, community statement, Indigenous statement where applicable, sponsor material, National Model element, AEP Passport input, Nexus Rail route, Docket item, Grid input, or handoff candidate shall enter Nexus Universe merely because it is visible, prestigious, politically attractive, sponsor-supported, media-friendly, investor-facing, or provider-promotional.

**6.2.7.5** National Nexus Universe participation shall preserve all boundaries. Public authorities shall participate in recorded capacity; capital readers shall participate under no-reliance discipline; providers shall demonstrate without validation; sponsors shall support without control; communities shall contribute without consent implication; Indigenous actors where applicable shall participate without Indigenous consent or FPIC implication; media shall follow public-safe reporting rules; and National Consortium Companies or Project SPVs shall remain separate enterprise-stack or project-vehicle actors.

**6.2.7.6** National Nexus Universe outputs may include national cycle records, public authority learning notes, finance-readiness notes, technical evidence notes, provider-neutral demonstration records, safeguard records, public-safe reports, AEP Passport candidate inputs, Proof Receipt inputs where authorized, Nexus Rail candidates, Docket items, Grid inputs, National Model updates, handoff candidates, correction items, and renewal items. They shall not be represented as approvals, certifications, finance commitments, procurement decisions, public authority actions, provider validations, community consents, Indigenous consents, public warnings, project authorizations, or execution commands.

**6.2.7.7** National Nexus Universe mobilization shall remain correctionable. Any national Nexus Universe material, session, delegate status, public-safe report, sponsor statement, provider statement, public authority reference, finance-readiness statement, community statement, Indigenous reference, AEP Passport reference, Nexus Rail reference, Docket item, Grid input, or handoff note that overclaims authority or readiness shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 6.2.8 National Safeguard and Public-Safe Reporting Mandate

**6.2.8.1** Each National Nexus Consortium shall hold the **National Safeguard and Public-Safe Reporting Mandate**. This mandate shall require the National Nexus Consortium to identify, record, localize, protect, route, correct, and publicly communicate in safe form the human, community, Indigenous where applicable, diaspora, youth, accessibility, environmental, biodiversity, land, water, ocean, food, health, humanitarian, data, cyber, privacy, protected knowledge, public authority, finance, provider, sponsor, media, and place-based safeguards relevant to national Nexus activity.

**6.2.8.2** National safeguards shall be treated as legitimacy infrastructure, not as reputational language. Safeguards shall create conditions, restrictions, cautions, dependencies, publication limits, handoff limits, and correction obligations that travel with National Model elements, Nexus Universe outputs, AEP Passport layers, Nexus Rail inputs, Docket items, Grid inputs, public-safe reports, and lawful handoff records.

**6.2.8.3** The National Safeguard Mandate shall include, as applicable:

1. community-risk and lived-risk review;
2. Indigenous protocol awareness, consultation-boundary discipline, and FPIC-boundary discipline where applicable;
3. protected knowledge and sensitive location controls;
4. community data, Indigenous data where applicable, privacy, cyber, and sovereign data controls;
5. youth and future-generation considerations;
6. accessibility and disability inclusion review;
7. diaspora role classification and boundary discipline;
8. environmental, biodiversity, land, water, ocean, food, health, livelihood, climate, and humanitarian safeguard review;
9. public authority-sensitive information review;
10. finance, provider, sponsor, and procurement safeguard review;
11. public-safe reporting and consent-language review;
12. Nexus Universe safeguard room preparation;
13. AEP Passport safeguard layer support;
14. Nexus Rail safeguard-condition routing; and
15. safeguard correction, withdrawal, and archive.

**6.2.8.4** The National Public-Safe Reporting Mandate shall require review of all public-facing national Nexus materials for factual accuracy, public authority language, finance no-reliance language, provider-neutrality language, sponsor influence, certification and standards-interface language, community consent language, Indigenous consent language where applicable, protected knowledge exposure, data and cyber risk, infrastructure and security sensitivity, humanitarian and health sensitivity, misinformation risk, accessibility, translation, localization, and correction pathway.

**6.2.8.5** Public-safe reporting may describe participation, themes, records formed, gaps identified, safeguards recorded, public authority learning areas, finance-readiness questions, Nexus Universe outputs, AEP Passport candidate references, Nexus Rail candidate references, Docket items, Grid inputs, correction items, and renewal priorities. It shall not imply approval, certification, public authority action, financeability, procurement status, provider validation, consent, project authorization, public warning, or execution.

**6.2.8.6** Safeguard records and public-safe reports shall not create consent. A community input is not community consent. An Indigenous protocol note is not Indigenous consent or FPIC satisfaction. A protected knowledge caution is not protected knowledge authorization. A public-safe report is not a public warning. A public authority-sensitive note is not public authority approval. A finance-readiness summary is not financeability.

**6.2.8.7** National safeguard and public-safe reporting records shall remain correctionable. If safeguards are incomplete, public-safe reports are misleading, protected knowledge is exposed, consent is overclaimed, public authority status is misstated, finance-readiness is overstated, provider-neutrality is compromised, or public communication creates unsafe reliance, the National Nexus Consortium shall correct, restrict, withdraw, supersede, publicly clarify where necessary, or archive the relevant record.

***

#### 6.2.9 National Enterprise Handoff Readiness Mandate

**6.2.9.1** Each National Nexus Consortium shall hold the **National Enterprise Handoff Readiness Mandate**. This mandate shall require the National Nexus Consortium to identify, prepare, classify, safeguard, limit, record, and correct the conditions under which eligible national public-good records may be handed off to competent downstream actors, including public authorities, National Consortium Companies, Project SPVs, providers, hosts, operators, investors, insurers, donors, development actors, procurement bodies, research institutions, technical bodies, community processes, Indigenous governance processes where applicable, or other lawful actors.

**6.2.9.2** Enterprise handoff readiness shall not be enterprise execution. It shall mean that the National Nexus Consortium has identified records, dependencies, safeguards, public authority conditions, finance-readiness conditions, provider-neutrality conditions, sponsor-boundary conditions, data and cyber conditions, community and Indigenous conditions where applicable, publication limits, claims limits, correction rights, and recipient capacity conditions that may support lawful downstream consideration.

**6.2.9.3** Handoff readiness may be supported by:

1. National Model elements;
2. evidence and method records;
3. technical-readiness records;
4. observability and systems-risk records;
5. public authority dependency notes;
6. finance-readiness and insurance-readiness notes;
7. donor relevance, development-readiness, and public finance relevance notes;
8. provider-neutral capability maps;
9. sponsor and partner boundary records;
10. safeguard and protected knowledge records;
11. public-safe reporting records;
12. Nexus Universe cycle outputs;
13. AEP Passport and Proof Receipt inputs where authorized;
14. Nexus Rail candidates;
15. Docket items and Grid inputs;
16. National Consortium Company interface records;
17. Project SPV-readiness records; and
18. correction and archive records.

**6.2.9.4** A handoff-readiness record shall identify the recipient capacity and the external processes that remain necessary. These may include public authority approval, procurement, finance, insurance, donor approval, development finance approval, public finance allocation, environmental review, community process, Indigenous process where applicable, data permission, cyber review, enterprise governance, Project SPV governance, contracting, permitting, operating readiness, safety review, and liability allocation.

**6.2.9.5** Handoff readiness shall not create public authority approval, procurement status, investment approval, financeability, bankability, insurability, insurance approval, donor approval, public finance allocation, development finance approval, provider validation, certification, standards conformance, community consent, Indigenous consent, protected knowledge authorization, land access, site approval, Nexus-ready status, AEP Passport status, Nexus Node status, project authorization, or execution authority.

**6.2.9.6** National Consortium Companies and Project SPVs shall remain separate from the National Nexus Consortium. The National Nexus Consortium may prepare handoff records for such vehicles where appropriate, but shall not become their shareholder, director, agent, fiduciary, lender, insurer, contractor, operator, guarantor, procurement body, or execution party unless a separate lawful instrument expressly creates a limited relationship outside the public-good role and the non-execution boundary remains clear.

**6.2.9.7** Enterprise handoff readiness shall be correctionable. If a handoff candidate is premature, unsafe, overclaimed, routed to the wrong actor, missing safeguards, missing public authority dependencies, finance-overclaimed, provider-skewed, sponsor-influenced, consent-overclaimed, data-sensitive, or used to imply execution, the National Nexus Consortium shall correct, restrict, suspend, withdraw, supersede, publicly clarify where necessary, or archive the handoff-readiness record.

***

#### 6.2.10 National Correction and Renewal Mandate

**6.2.10.1** Each National Nexus Consortium shall hold the **National Correction and Renewal Mandate**. This mandate shall require the National Nexus Consortium to maintain the continuing ability to correct, narrow, restrict, reclassify, suspend, withdraw, supersede, reinstate, renew, publicly clarify where necessary, and archive national participation records, council records, helix records, working-group outputs, competence-cell outputs, National Model elements, Nexus Universe materials, AEP Passport references, Nexus Rail references, Docket items, Grid inputs, public-safe reports, sponsor records, provider records, public authority references, finance-readiness statements, safeguard records, and handoff records.

**6.2.10.2** National correction shall apply whenever a national record or claim is inaccurate, incomplete, outdated, overbroad, overclaimed, unsafe, inconsistent with public authority status, inconsistent with finance boundaries, inconsistent with provider-neutrality, inconsistent with sponsor-boundary rules, inconsistent with community or Indigenous safeguards where applicable, inconsistent with protected knowledge restrictions, inconsistent with public-safe classification, or capable of creating unlawful reliance.

**6.2.10.3** National correction triggers shall include, without limitation:

1. national gateway overclaim;
2. public authority overclaim;
3. finance, insurance, donor, development, or public finance overclaim;
4. procurement or provider validation overclaim;
5. certification, standards-conformance, maturity, Nexus-ready, AEP Passport, Nexus Node, Docket, Grid, or Nexus Rail overclaim;
6. community consent, Indigenous consent, FPIC, protected knowledge, social license, land, cultural, site, or place-based legitimacy overclaim;
7. safeguard omission or mislocalization;
8. protected knowledge exposure;
9. public-safe reporting error;
10. sponsor, provider, capital, public authority, media, founder, national, enterprise, or project capture risk;
11. data, privacy, cyber, infrastructure, health, humanitarian, or security-sensitive publication risk;
12. role collapse between public-good stack and enterprise stack;
13. Working Group or Competence Cell mandate drift;
14. Nexus Universe overclaim;
15. handoff error or recipient misuse; and
16. execution implication.

**6.2.10.4** National correction measures may include record amendment, claim narrowing, controlled clarification, public-safe clarification, publication reclassification, participant reclassification, role reclassification, room restriction, name-use restriction, sponsor or provider reference restriction, removal of public materials, suspension of participation, withdrawal of handoff, supersession of records, archive notation, reinstatement on corrected terms, and renewal on corrected terms.

**6.2.10.5** National renewal shall occur at least annually and shall be aligned with the Nexus Universe cycle. Renewal shall review national gateway status, National Council status, Helix Council status, Working Group status, Competence Cell status, National Model status, public authority learning records, finance-readiness records, safeguard records, public-safe reports, sponsor and provider records, AEP Passport and Nexus Rail candidates, Docket and Grid items, handoff pathways, and archive records.

**6.2.10.6** Renewal shall not erase unresolved issues. Public authority dependencies, finance-readiness gaps, safeguard conditions, protected knowledge restrictions, data and cyber restrictions, community conditions, Indigenous protocol conditions where applicable, provider-neutrality issues, sponsor-boundary concerns, public-safe reporting limits, Docket items, Grid conditions, and handoff restrictions shall remain attached to renewed records unless separately resolved and recorded.

**6.2.10.7** The National Nexus Consortium shall produce an annual national renewal record. The renewal record shall identify the national gateway status, council and helix status, National Model status, Nexus Universe readiness, public-safe reporting status, finance-readiness status, safeguard status, partner and sponsor status, provider conditions, AEP Passport and Nexus Rail status, Docket and Grid updates, correction items, unresolved issues, restricted items, withdrawn items, superseded records, archive entries, and next-cycle conditions.

**6.2.10.8** The National Correction and Renewal Mandate shall be treated as a core national legitimacy function. The National Nexus Consortium shall not allow public authority sensitivity, sponsor sensitivity, provider importance, investor interest, media visibility, community politics, institutional embarrassment, Nexus Universe prominence, or enterprise pressure to prevent necessary correction.

### 6.3 National Functions

#### 6.3.1 National Priority Formation

**6.3.1.1** Each **National Nexus Consortium** shall perform the function of **National Priority Formation**. National Priority Formation shall mean the structured, record-based process through which the National Nexus Consortium identifies, classifies, sequences, localizes, safeguards, and renews the country’s Nexus priorities for participation, evidence formation, public authority learning, finance-readiness, National Model preparation, Nexus Universe mobilization, AEP Passport and Nexus Rail candidate routing, Docket and Grid input formation, public-safe reporting, and lawful handoff readiness.

**6.3.1.2** National priorities shall be public-good formation priorities, not public authority mandates, procurement programs, investment theses, donor plans, certification routes, provider pipelines, community consent pathways, Indigenous approval pathways, project approvals, or execution instructions. They shall organize attention, records, learning, readiness, safeguards, routing, and correction; they shall not authorize implementation.

**6.3.1.3** National Priority Formation may address, without limitation:

1. national systemic risk, resilience, disaster-risk reduction, adaptation, reconstruction, and recovery priorities;
2. water, energy, food, health, biodiversity, land, ocean, nature, climate, and livelihood systems;
3. AI, AI-RAN, O-RAN, private wireless, telecommunications, cyber, compute, data, geospatial systems, Earth observation, digital twins, sensing, robotics, drones, blockchain-relevant infrastructure, quantum-relevant systems, semiconductors, advanced manufacturing, critical infrastructure, and related exponential technologies;
4. public authority learning, Government Portfolio preparation, public finance relevance, procurement-neutral learning, and regulatory-learning priorities;
5. finance-readiness, insurance-readiness, reinsurance-readiness, donor relevance, development-readiness, public finance relevance, disaster-risk finance, diligence-gap, and capital-readability priorities;
6. public-safe reporting, information integrity, civic trust, media boundary, accessibility, plain-language communication, and public meaning priorities;
7. community, Indigenous where applicable, diaspora, youth, accessibility, protected knowledge, rights-aware, environmental, cultural, and place-based legitimacy priorities;
8. Nexus Universe national delegation, room, program, and annual-cycle priorities;
9. AEP Passport, Proof Receipt where authorized, Nexus Rail, Docket, and Grid priorities; and
10. correction, renewal, archive, and lawful handoff priorities.

**6.3.1.4** National Priority Formation shall be informed by records from National Councils, National Leadership Councils, National Investors Councils, Helix Councils, National Working Groups, Nexus Competence Cells, public authority learning rooms, finance-readiness rooms, technical and evidence records, safeguard records, National Model drafts, Nexus Universe cycle records, AEP Passport and Nexus Rail candidate records, Docket items, Grid inputs, public-safe reports, Regional Headquarters inputs, and Global Nexus Consortium common doctrine.

**6.3.1.5** National priorities shall distinguish between national relevance and national authority. A matter may be nationally important because it affects public risk, infrastructure, technology readiness, communities, public authority learning, finance-readiness, or Nexus Universe participation, but such importance shall not create approval, procurement status, financeability, certification, provider validation, consent, public warning, project authorization, or execution authority.

**6.3.1.6** National Priority Formation shall be recorded with scope, source records, affected sectors, affected communities, public authority relevance, finance-readiness relevance, technical relevance, safeguard relevance, Nexus Universe relevance, AEP Passport and Nexus Rail relevance, Docket or Grid relevance, public-safe status, claims limits, responsible review pathway, correction pathway, and renewal cycle.

**6.3.1.7** National priorities shall remain correctionable. If a priority becomes inaccurate, overbroad, politically misleading, unsafe, finance-overclaimed, public authority-overclaimed, provider-skewed, safeguard-incomplete, consent-overclaimed, or inconsistent with Nexus doctrine, it shall be corrected, narrowed, deferred, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 6.3.2 National Stakeholder Formation

**6.3.2.1** Each National Nexus Consortium shall perform the function of **National Stakeholder Formation**. National Stakeholder Formation shall mean the structured identification, classification, onboarding, role-recording, conflict-review, safeguard-review, claims-limiting, public-safe, and correctionable formation of the persons and institutions needed to support the national Nexus public-good pathway.

**6.3.2.2** National Stakeholder Formation shall organize participation across the country without converting participation into authority. The function shall ensure that public authorities, universities, research bodies, enterprises, infrastructure actors, technology providers, capital readers, insurers, donors, development actors, media bodies, civic actors, civil society organizations, communities, Indigenous actors where applicable, diaspora contributors, youth, accessibility advocates, sponsors, hosts, partners, National Consortium Companies, Project SPVs, and other lawful actors participate only within recorded capacity.

**6.3.2.3** Stakeholder formation may include, as applicable:

1. national stakeholder mapping;
2. sector and system mapping;
3. public authority capacity classification;
4. research and scientific capacity mapping;
5. enterprise, infrastructure, host, operator, and provider-neutral capability mapping;
6. capital, insurance, donor, development, and public finance relevance mapping;
7. media, civic, public-interest, accessibility, and information-integrity mapping;
8. community, Indigenous where applicable, diaspora, youth, protected knowledge, and place-based safeguard mapping;
9. sponsor, host, partner, and contributor mapping;
10. National Consortium Company and Project SPV interface mapping where applicable;
11. conflict, capture, and role-collapse review;
12. claims-permission classification;
13. public-safe listing classification; and
14. correction and renewal status.

**6.3.2.4** National Stakeholder Formation shall be gateway-based. Individuals shall ordinarily be formed through the National Council, including the National Leadership Council and National Investors Council. Institutions shall ordinarily be formed through the Helix Councils. Task-specific participants shall be formed through National Working Groups. Capability participants shall be formed through Nexus Competence Cells. Enterprise and project actors shall be classified separately and shall not be treated as public-good governance actors by implication.

**6.3.2.5** Stakeholder participation shall be recorded with role, capacity, affiliation, contribution type, public authority status if applicable, finance status if applicable, provider or sponsor status if applicable, community or Indigenous status where applicable, conflict status, publication status, claims permission, data and confidentiality obligations, safeguard obligations, Nexus Universe relevance, AEP Passport and Nexus Rail relevance, Docket and Grid relevance, handoff relevance, and correction pathway.

**6.3.2.6** Stakeholder formation shall be protected against capture and tokenization. No stakeholder category shall be used to manufacture legitimacy, imply approval, create finance signals, create provider preference, create public authority endorsement, or imply community or Indigenous consent. Participation shall be substantive, bounded, and record-based.

**6.3.2.7** National Stakeholder Formation shall be correctionable. If a stakeholder is misclassified, overclaims status, misuses name or marks, creates conflict risk, implies authority, distorts public-good records, exposes protected knowledge, creates public-safe reporting risk, or causes role collapse, the National Nexus Consortium shall correct, restrict, reclassify, suspend, withdraw, publicly clarify where necessary, or archive the relevant stakeholder record.

***

#### 6.3.3 National Council Activation

**6.3.3.1** Each National Nexus Consortium shall perform the function of **National Council Activation**. National Council Activation shall mean the formation, onboarding, role-classification, records setup, claims limitation, Nexus Universe preparation, public-safe reporting alignment, and renewal of the National Council, including the National Leadership Council and National Investors Council.

**6.3.3.2** National Council Activation shall create an individual participation layer for leadership, stewardship, national systems insight, investor literacy, capital-readability, public-good judgment, National Model contribution, Nexus Universe delegation readiness, Docket and Grid input, AEP Passport and Nexus Rail awareness, and lawful handoff literacy. It shall not create public office, board appointment, public authority approval, procurement authority, finance authority, investment advice, provider validation, certification, community consent, Indigenous consent, project authorization, or execution rights.

**6.3.3.3** National Council Activation shall include, as applicable:

1. adoption of council terms of reference;
2. formation of the National Leadership Council;
3. formation of the National Investors Council;
4. participant eligibility review;
5. role and capacity classification;
6. conflict and anti-capture review;
7. public listing and name-use controls;
8. claims permission controls;
9. meeting and records rules;
10. National Model contribution rules;
11. Nexus Universe delegation and room participation rules;
12. finance no-reliance rules for investor-related participation;
13. public authority boundary rules for public officials or former officials;
14. community and Indigenous consent-boundary rules where applicable;
15. Docket, Grid, AEP Passport, and Nexus Rail input rules; and
16. correction, renewal, suspension, and archive rules.

**6.3.3.4** The National Leadership Council shall support national agenda formation, leadership-pool development, public-good stewardship, public authority learning awareness, National Model input, Nexus Universe national delegation preparation, stakeholder formation, public-safe reporting input, working-group referrals, and correction awareness.

**6.3.3.5** The National Investors Council shall support no-reliance capital-reader participation, investor literacy, finance-readiness question formation, insurance-readiness question formation, donor and development relevance awareness, public finance relevance awareness, diligence-gap mapping, Project SPV-readiness questions, AEP Passport finance-layer inputs, Nexus Rail finance-readiness inputs, and Nexus Universe capital-reader room preparation.

**6.3.3.6** National Council Activation shall require claims discipline. A National Council member shall not claim to approve, endorse, finance, insure, certify, procure, regulate, consent, or authorize any Nexus pathway by reason of council participation. Institutional affiliation shall not be treated as institutional endorsement unless separately and lawfully recorded.

**6.3.3.7** National Council Activation shall remain correctionable. If a council member or council body overclaims authority, creates finance signaling, implies public authority approval, implies provider validation, suppresses safeguards, misuses community or Indigenous participation, or creates capture risk, the National Nexus Consortium shall correct, restrict, suspend, reclassify, remove public reference, renew on corrected terms, or archive the relevant record.

***

#### 6.3.4 National Helix Activation

**6.3.4.1** Each National Nexus Consortium shall perform the function of **National Helix Activation**. National Helix Activation shall mean the formation, onboarding, role-classification, mandate adoption, records setup, public-safe reporting alignment, Nexus Universe preparation, cross-helix coordination, claims limitation, and correction of the National Helix Councils.

**6.3.4.2** National Helix Activation shall organize institutional participation through the following helix gateways:

1. **Government / Public Authority Helix Council**;
2. **Academia / Research / Science Helix Council**;
3. **Industry / Enterprise / Infrastructure / Technology Helix Council**;
4. **Capital / Insurance / Donor / Development Helix Council**;
5. **Media / Civic / Public-Interest Helix Council**; and
6. **Community / Indigenous / Diaspora / Place-Based Legitimacy Helix Council**.

**6.3.4.3** National Helix Activation shall ensure that each helix has a recorded mandate, composition rules, eligibility rules, participation categories, role classifications, meeting rules, records responsibilities, National Model duties, Nexus Universe duties, Working Group referral duties, Competence Cell interface rules, AEP Passport and Nexus Rail relevance, Docket and Grid relevance, public-safe reporting duties, claims boundaries, conflict rules, safeguard duties, and correction pathway.

**6.3.4.4** Helix activation shall be cross-disciplinary and boundary-specific. The Government / Public Authority Helix shall support learning without public authority substitution. The Academia / Research / Science Helix shall support evidence without certification. The Industry / Enterprise / Infrastructure / Technology Helix shall support capability without provider validation. The Capital / Insurance / Donor / Development Helix shall support readiness without finance execution. The Media / Civic / Public-Interest Helix shall support public meaning without public relations capture. The Community / Indigenous / Diaspora / Place-Based Legitimacy Helix shall support safeguards without consent overclaim.

**6.3.4.5** National Helix Activation shall include anti-capture review. No helix shall be dominated by a sponsor, provider, public authority, capital actor, university, media actor, founder group, community actor, Indigenous actor, National Consortium Company, Project SPV, or other stakeholder category in a manner that distorts public-good records or weakens safeguards.

**6.3.4.6** Cross-helix coordination shall be required where outputs affect multiple domains. A National Model element, Nexus Universe output, AEP Passport candidate layer, Nexus Rail candidate, Docket item, Grid input, finance-readiness note, public authority learning record, safeguard record, or lawful handoff condition may require review by multiple helixes to prevent role collapse and overclaim.

**6.3.4.7** National Helix Activation shall remain correctionable. If a helix is misdescribed, captured, overclaimed, tokenistic, under-recorded, unsafe, used as approval, used as finance signal, used as provider validation, used as public authority endorsement, or used as consent evidence, the National Nexus Consortium shall correct, restrict, reconstitute, suspend, renew on corrected terms, or archive the relevant helix records.

***

#### 6.3.5 National Working Group Activation

**6.3.5.1** Each National Nexus Consortium shall perform the function of **National Working Group Activation**. National Working Group Activation shall mean the formation, mandate approval, participant classification, records setup, task management, output classification, claims control, public-safe reporting alignment, correction, renewal, closure, and archive of national task-specific Working Groups.

**6.3.5.2** National Working Groups shall be activated only where a defined national question, task, technology, system, risk, public authority learning need, finance-readiness question, safeguard issue, Nexus Universe deliverable, National Model component, AEP Passport candidate layer, Nexus Rail candidate, Docket item, Grid input, or lawful handoff question requires structured work beyond ordinary council or helix participation.

**6.3.5.3** National Working Group Activation shall require a mandate record identifying:

1. the Working Group name;
2. purpose and scope;
3. originating council, helix, or National Nexus Consortium pathway;
4. participants and capacity classifications;
5. chair, facilitator, or records lead;
6. term and renewal conditions;
7. evidence and method expectations;
8. public authority boundaries;
9. finance, insurance, donor, development, and public finance boundaries;
10. provider-neutrality and sponsor-boundary conditions;
11. community, Indigenous where applicable, diaspora, youth, accessibility, protected knowledge, and safeguard conditions;
12. data, privacy, cyber, confidentiality, and publication rules;
13. expected outputs;
14. National Model relevance;
15. Nexus Universe relevance;
16. AEP Passport, Proof Receipt where authorized, Nexus Rail, Docket, and Grid relevance;
17. lawful handoff limits; and
18. correction, suspension, closure, and archive rules.

**6.3.5.4** National Working Groups may generate evidence notes, method records, readiness notes, dependency maps, technical notes, observability notes, provider-neutral capability maps, public authority dependency notes, finance-readiness questions, safeguard records, public-safe reporting inputs, Nexus Universe preparation records, AEP Passport inputs, Nexus Rail candidates, Docket items, Grid inputs, and handoff restriction notes.

**6.3.5.5** National Working Groups shall not become execution teams. They shall not procure, contract, select vendors, approve providers, approve projects, raise capital, underwrite insurance, issue public warnings, act as public authorities, certify systems, grant consent, authorize deployment, operate infrastructure, manage implementation, or bind downstream actors.

**6.3.5.6** National Working Group Activation shall require output classification. Each output shall be classified as public, public-safe, controlled, restricted, confidential, 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.

**6.3.5.7** National Working Group Activation shall remain correctionable. If a Working Group exceeds mandate, becomes captured, omits safeguards, produces unsafe outputs, misclassifies records, creates provider advantage, implies public authority approval, implies financeability, implies consent, or suggests execution authority, it shall be corrected, restricted, suspended, reconstituted, closed, superseded, or archived.

***

#### 6.3.6 National Competence Cell Formation

**6.3.6.1** Each National Nexus Consortium shall perform the function of **National Competence Cell Formation**. National Competence Cell Formation shall mean the identification, creation, classification, mandate approval, records setup, training, documentation, capability development, public-safe reporting alignment, correction, renewal, and archive of focused national capability units that support the national Nexus pathway.

**6.3.6.2** A **Nexus Competence Cell** may be formed to build national capability in evidence, methods, observability, ontology, public-good software, AI, AI-RAN, O-RAN, private wireless, cyber, compute, data, geospatial systems, Earth observation, digital twins, sensing, robotics, drones, blockchain-relevant infrastructure, quantum-relevant systems, semiconductors, advanced manufacturing, WEFH-B systems, public authority learning, finance-readiness, insurance-readiness, public-safe reporting, community safeguards, protected knowledge handling, Nexus Universe preparation, AEP Passport candidate formation, Nexus Rail routing, Docket and Grid input formation, or lawful handoff readiness.

**6.3.6.3** National Competence Cell Formation shall require a competence mandate identifying:

1. capability domain;
2. host or formation pathway;
3. relationship to the National Nexus Consortium;
4. relationship to relevant councils, helixes, and Working Groups;
5. relationship to GCRI, GRF, GRA, Regional Headquarters Consortium, or Global Nexus Consortium where applicable;
6. participants and capacity classifications;
7. evidence, method, training, or technical expectations;
8. data, cyber, privacy, confidentiality, and security controls;
9. public authority boundaries;
10. finance and no-reliance boundaries;
11. provider-neutrality and sponsor-boundary conditions;
12. safeguard and protected knowledge conditions;
13. outputs and publication classes;
14. Nexus Universe relevance;
15. AEP Passport, Nexus Rail, Docket, and Grid relevance;
16. lawful handoff limits; and
17. correction, renewal, suspension, closure, and archive rules.

**6.3.6.4** Competence Cells may produce training materials, templates, methods, public-good software contributions, data dictionaries, ontology inputs, benchmark cards, system cards, evidence pack inputs, decision-pack inputs, dashboard methods, public-safe reporting tools, finance-readiness tools, safeguard tools, Nexus Universe build inputs, AEP Passport candidate supports, Nexus Rail dependency maps, and correction notes.

**6.3.6.5** Competence Cells shall build capability without conferring approval. A Competence Cell may teach, test, prototype, document, compare, prepare, and support, but it shall not certify, accredit, validate providers, approve technologies, issue standards conformance, approve public authority action, provide investment advice, allocate finance, grant insurance approval, authorize data use beyond permission, grant community consent, grant Indigenous consent, approve projects, or execute deployments.

**6.3.6.6** National Competence Cell Formation shall be protected against provider, sponsor, public authority, university, capital, founder, or enterprise capture. Contribution by a powerful actor shall not control the cell, suppress limitations, convert technical contribution into validation, convert training into certification, or convert capability formation into procurement advantage.

**6.3.6.7** National Competence Cells shall be correctionable. If a cell’s output becomes inaccurate, unsafe, outdated, overclaimed, captured, inconsistent with method, inconsistent with safeguards, inconsistent with data restrictions, or misused downstream as approval or execution authority, the National Nexus Consortium shall correct, restrict, withdraw, supersede, suspend, renew on corrected terms, or archive the relevant cell record or output.

***

#### 6.3.7 National Nexus Universe Preparation

**6.3.7.1** Each National Nexus Consortium shall perform the function of **National Nexus Universe Preparation**. National Nexus Universe Preparation shall mean the national process through which the country’s priorities, stakeholders, National Council inputs, Helix Council inputs, Working Group outputs, Competence Cell outputs, National Model elements, public authority learning records, finance-readiness records, safeguard records, public-safe reports, AEP Passport and Nexus Rail candidates, Docket items, Grid inputs, and lawful handoff questions are prepared for the annual Nexus Universe cycle.

**6.3.7.2** National Nexus Universe Preparation shall cover the full annual rhythm, including year-long national mobilization, one-month Nexus Core build support, one-week live operation participation, post-cycle public-safe reporting and correction, and next-cycle renewal.

**6.3.7.3** National Nexus Universe Preparation shall include, as applicable:

1. national annual priority setting;
2. national delegation formation;
3. National Model presentation preparation;
4. National Council and Helix Council session preparation;
5. Working Group and Competence Cell output preparation;
6. public authority learning room preparation;
7. capital-reader, insurance-readiness, donor, development, and public finance relevance room preparation;
8. technical, evidence, observability, AI, cyber, data, infrastructure, and public-good software room preparation;
9. provider-neutral demonstration preparation;
10. community, Indigenous where applicable, diaspora, youth, accessibility, protected knowledge, and safeguard room preparation;
11. media, civic, public-interest, and public-safe reporting preparation;
12. AEP Passport and Proof Receipt input preparation where authorized;
13. Nexus Rail candidate routing preparation;
14. Docket and Grid intake preparation;
15. lawful handoff discussion controls; and
16. correction, withdrawal, archive, and renewal procedures.

**6.3.7.4** National Nexus Universe Preparation shall be record-led and public-safe. No national item shall be presented publicly merely because it is sponsor-supported, provider-promotional, politically attractive, media-friendly, investor-facing, or institutionally prestigious. Each item shall be classified by record status, evidence basis, public-safe class, claims limits, authority boundaries, finance boundaries, provider-neutrality, safeguard conditions, unresolved dependencies, and correction pathway.

**6.3.7.5** National delegations shall be classified by role. A delegate may be a National Council participant, Helix Council participant, public authority learner, researcher, provider-neutral technical contributor, capital reader, insurer, donor, media actor, civic actor, community contributor, Indigenous participant where applicable, Competence Cell contributor, Working Group participant, National Consortium Company interface, Project SPV interface, or other recorded participant. Delegation status shall not create approval or authority.

**6.3.7.6** National Nexus Universe outputs shall not be represented as approvals, certifications, finance commitments, procurement decisions, public authority actions, provider validations, community consents, Indigenous consents, public warnings, project authorizations, AEP Passport statuses, Nexus Node approvals, or execution commands.

**6.3.7.7** National Nexus Universe Preparation shall be correctionable. If a session, room, delegate record, National Model element, presentation, public-safe report, sponsor material, provider material, public authority reference, capital-reader reference, community reference, Indigenous reference, AEP Passport reference, Nexus Rail reference, Docket item, Grid input, or handoff note overclaims authority or readiness, it shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 6.3.8 National AEP Passport and Rail Candidate Routing

**6.3.8.1** Each National Nexus Consortium shall perform the function of **National AEP Passport and Rail Candidate Routing**. This function shall identify, classify, prepare, limit, route, correct, renew, and archive national candidates, layers, inputs, dependencies, and safeguard conditions relevant to AEP Passport pathways, Proof Receipt inputs where authorized, and Nexus Rail routes.

**6.3.8.2** National AEP Passport routing shall organize candidate layers across technical evidence, methods, observability, public authority context, finance-readiness, insurance-readiness, donor relevance, public finance relevance, provider-neutrality, sponsor boundaries, host readiness, operational readiness, community safeguards, Indigenous protocol awareness where applicable, protected knowledge restrictions, public-safe reporting, Nexus Universe cycle records, Nexus Rail routeability, unresolved dependencies, and correction history.

**6.3.8.3** National Nexus Rail candidate routing shall identify routeability for national capabilities, systems, project concepts, node candidates, corridor candidates, public-good software inputs, observability pathways, National Model elements, Nexus Universe outputs, public authority learning inputs, finance-readiness questions, safeguard conditions, Docket items, Grid inputs, and lawful handoff candidates. Routeability shall mean a recorded pathway for further review or handoff consideration, not approval or execution.

**6.3.8.4** A national AEP Passport or Nexus Rail routing record shall identify, as applicable:

1. originating national record;
2. candidate subject, pathway, project concept, system, node, portfolio, capability, or output;
3. evidence basis and limitations;
4. technical and observability relevance;
5. public authority dependencies;
6. finance, insurance, donor, development, and public finance dependencies;
7. procurement dependencies;
8. provider-neutrality and sponsor-boundary conditions;
9. host, operator, infrastructure, and operational readiness conditions;
10. community, Indigenous where applicable, diaspora, youth, accessibility, protected knowledge, and place-based safeguard conditions;
11. data, cyber, infrastructure, health, humanitarian, public authority-sensitive, and security-sensitive restrictions;
12. public-safe reporting status;
13. Nexus Universe relevance;
14. Docket and Grid relevance;
15. lawful handoff conditions;
16. permitted and prohibited claims; and
17. correction, renewal, withdrawal, and archive rules.

**6.3.8.5** National AEP Passport and Rail Candidate Routing shall not create AEP Passport status, Nexus Rail approval, Nexus-ready status, Nexus Node approval, certification, standards conformance, public authority approval, procurement eligibility, financeability, insurance approval, donor approval, public finance allocation, provider validation, community consent, Indigenous consent, protected knowledge authorization, project authorization, or execution authority.

**6.3.8.6** Candidate routing shall preserve source conditions. National records routed to regional or global levels shall retain national source, public authority boundaries, finance boundaries, safeguard conditions, protected knowledge restrictions, data and cyber restrictions, publication class, claims limits, correction history, and lawful handoff limitations.

**6.3.8.7** National AEP Passport and Rail Candidate Routing shall be correctionable. If a candidate is overclaimed, incomplete, unsafe, misrouted, inconsistent with national records, stripped of safeguards, or used to imply approval, financeability, consent, certification, procurement status, provider validation, or execution, the National Nexus Consortium shall correct, restrict, suspend, withdraw, supersede, publicly clarify where necessary, or archive the routing record.

***

#### 6.3.9 National Public-Safe Reporting

**6.3.9.1** Each National Nexus Consortium shall perform the function of **National Public-Safe Reporting**. National Public-Safe Reporting shall mean the preparation, review, classification, publication, correction, withdrawal, renewal, and archive of national public-facing or public-safe materials arising from National Model formation, National Council activity, Helix Council activity, Working Group outputs, Competence Cell outputs, public authority learning, finance-readiness translation, safeguard records, Nexus Universe participation, AEP Passport and Nexus Rail routing, Docket and Grid items, and lawful handoff records.

**6.3.9.2** National Public-Safe Reporting shall support transparency, public meaning, civic trust, public authority literacy, finance-readiness literacy, technical understanding, safeguard visibility, Nexus Universe continuity, and correction. It shall not operate as public relations, sponsor promotion, provider marketing, investment promotion, public warning, emergency communication, certification, procurement communication, government endorsement, finance approval, community consent, Indigenous consent, or project approval.

**6.3.9.3** National public-safe reports may describe, as applicable:

1. national participation and gateway formation;
2. National Council and Helix Council formation;
3. National Model themes;
4. national risk and resilience priorities;
5. public authority learning areas;
6. finance-readiness and capital-readability questions;
7. technical, evidence, observability, data, AI, cyber, infrastructure, and public-good software themes;
8. provider-neutral capability themes;
9. community, Indigenous where applicable, diaspora, youth, accessibility, protected knowledge, and safeguard themes;
10. Nexus Universe national outputs;
11. AEP Passport and Nexus Rail candidate references within permitted limits;
12. Docket and Grid themes;
13. correction and renewal items; and
14. lawful handoff themes where public-safe.

**6.3.9.4** National Public-Safe Reporting shall require review 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, misinformation risk, misleading visualization risk, accessibility, translation, localization, and correction needs.

**6.3.9.5** Public-safe reporting shall distinguish between what has been formed, what has been learned, what is under review, what remains unresolved, what is restricted, what has been corrected, what has been withdrawn, what is being renewed, and what may be handed off. It shall not erase limitations for public narrative convenience.

**6.3.9.6** No national public-safe report shall imply public authority approval, regulatory finding, procurement status, financeability, insurance approval, donor approval, public finance allocation, provider validation, certification, standards conformance, community consent, Indigenous consent, project approval, public warning, Nexus-ready status, AEP Passport status, Nexus Node status, or execution authority.

**6.3.9.7** National Public-Safe Reporting shall be correctionable. If a public-safe report becomes inaccurate, unsafe, overbroad, incomplete, misleading, outdated, superseded, or misused, the National Nexus Consortium shall issue correction, narrowing, withdrawal, reclassification, supersession, archive notation, or public-safe update as appropriate.

***

#### 6.3.10 National Handoff Record Preparation

**6.3.10.1** Each National Nexus Consortium shall perform the function of **National Handoff Record Preparation**. This function shall prepare the bounded records through which eligible public-good outputs may be transmitted to competent downstream actors for lawful consideration without converting the National Nexus Consortium into an executing, approving, financing, procuring, certifying, consenting, regulating, or operating body.

**6.3.10.2** A National Handoff Record may relate to a National Model element, evidence record, technical-readiness note, observability record, public authority dependency note, finance-readiness note, insurance-readiness note, donor relevance note, development-readiness note, public finance relevance note, provider-neutral capability map, safeguard record, protected knowledge caution, public-safe report, Nexus Universe output, AEP Passport candidate layer, Proof Receipt input where authorized, Nexus Rail candidate, Docket item, Grid input, National Consortium Company interface, Project SPV-readiness record, or other lawful national Nexus output.

**6.3.10.3** National Handoff Record Preparation shall identify, at minimum:

1. originating National Nexus Consortium record;
2. originating council, helix, Working Group, Competence Cell, or National Model source where applicable;
3. record version, status, and correction history;
4. recipient and recipient capacity;
5. purpose and scope of handoff;
6. evidence basis and limitations;
7. unresolved dependencies;
8. public authority dependencies;
9. finance, insurance, donor, development, and public finance dependencies;
10. procurement dependencies;
11. provider-neutrality and sponsor-boundary conditions;
12. community, Indigenous where applicable, diaspora, youth, accessibility, protected knowledge, and place-based safeguard conditions;
13. data, privacy, cyber, infrastructure, humanitarian, health, public authority-sensitive, and security-sensitive restrictions;
14. publication and public-safe communication limits;
15. permitted and prohibited claims;
16. non-reliance or reliance limitations as applicable;
17. correction, withdrawal, supersession, renewal, and archive rights; and
18. express non-execution language.

**6.3.10.4** Handoff recipients may include, where appropriate, public authorities, National Consortium Companies, Project SPVs, providers, hosts, operators, investors, insurers, donors, development finance actors, procurement bodies, research institutions, technical bodies, community processes, Indigenous governance processes where applicable, or other competent lawful actors. Each recipient shall be classified according to actual capacity and shall remain responsible for its own legal process.

**6.3.10.5** National Handoff Record Preparation shall not create approval. A handoff record shall not create public authority approval, regulatory comfort, policy adoption, procurement status, investment approval, financeability, bankability, insurability, insurance approval, donor approval, public finance allocation, development finance approval, provider validation, certification, standards conformance, community consent, Indigenous consent, protected knowledge authorization, land access, site approval, Nexus-ready status, AEP Passport status, Nexus Node status, project authorization, or execution authority.

**6.3.10.6** Handoff records shall travel with safeguards and limitations. A downstream actor shall not strip the record of unresolved dependencies, public authority conditions, finance limits, procurement limits, provider-neutrality conditions, sponsor restrictions, safeguard conditions, protected knowledge restrictions, data controls, public-safe limits, claims prohibitions, or correction history.

**6.3.10.7** National Handoff Record Preparation shall remain correctionable after transmission. If a handoff is premature, misdirected, incomplete, overclaimed, unsafe, stripped of safeguards, misused by a recipient, used to imply public authority approval, used to imply financeability, used to imply provider validation, used to imply consent, or used to imply execution by the National Nexus Consortium, the National Nexus Consortium shall correct, restrict, suspend, withdraw, supersede, publicly clarify where necessary, or archive the handoff record.

### 6.4 National Limits

#### 6.4.1 No Public Authority Substitution

**6.4.1.1** A **National Nexus Consortium** shall not substitute for any public authority. It shall not replace, impersonate, bind, direct, pre-empt, simulate, or act on behalf of any national, federal, provincial, state, territorial, municipal, local, Indigenous, Tribal, public finance, public procurement, regulatory, emergency management, public health, infrastructure, data, court, legislative, administrative, or other public-law authority.

**6.4.1.2** The National Nexus Consortium may support public authority learning, public-sector readiness, Government Portfolio preparation, public-safe dashboard review, public authority dependency mapping, public authority room participation, public finance relevance discussion, procurement-neutral education, regulatory-learning records, and National Model public authority context. These functions shall support public-good learning and readiness only and shall not constitute public authority action.

**6.4.1.3** Public authority participation in the National Nexus Consortium, National Council, Helix Council, Working Group, Competence Cell, Nexus Universe delegation, National Model process, AEP Passport pathway, Nexus Rail pathway, Docket item, Grid input, public-safe report, or handoff discussion shall be classified by recorded capacity. Attendance, contribution, observation, participation, or receipt of information shall not imply official approval, delegation, endorsement, policy adoption, regulatory comfort, procurement status, public finance allocation, data authorization, emergency action, public warning, or project authorization.

**6.4.1.4** Public authority functions shall remain with the competent public authority. The National Nexus Consortium may provide records, context, evidence, readiness notes, dependency maps, public-safe summaries, safeguard conditions, and handoff inputs, but it shall not make the public authority decision or cause such decision to be made by implication.

**6.4.1.5** National public authority learning records shall state their limits. A public authority room note is not a public authority decision. A dashboard review is not an official warning. A Government Portfolio input is not government adoption. A public finance relevance note is not public finance allocation. A procurement-neutral learning record is not procurement approval. A regulatory-learning record is not regulatory comfort.

**6.4.1.6** The National Nexus Consortium shall not use public authority names, symbols, logos, titles, quotations, participation status, room attendance, or official affiliations in a manner that implies public authority approval unless separately and lawfully authorized by the competent public authority and recorded with scope, limitation, permission, and correction conditions.

**6.4.1.7** Any public authority substitution claim or implication shall be corrected. The National Nexus Consortium shall correct, narrow, withdraw, supersede, publicly clarify where necessary, or archive any record or communication implying that it exercises public authority or creates public authority approval.

***

#### 6.4.2 No Government Endorsement by Participation

**6.4.2.1** Participation by a government, ministry, agency, regulator, municipality, public official, public university, public enterprise, public finance actor, public procurement actor, public infrastructure body, emergency authority, or other public-sector participant in a National Nexus Consortium pathway shall not create government endorsement by implication.

**6.4.2.2** Government or public-sector attendance at meetings, workshops, rooms, Nexus Universe sessions, public authority learning rooms, National Council sessions, Helix Council sessions, Working Groups, Competence Cells, National Model reviews, AEP Passport discussions, Nexus Rail discussions, Docket reviews, Grid reviews, sponsor events, provider-neutral demonstrations, capital-reader rooms, or public-safe reporting reviews shall not be represented as endorsement, approval, adoption, sponsorship, delegation, procurement interest, public finance support, or official policy position unless separately and lawfully recorded.

**6.4.2.3** The National Nexus Consortium may record public-sector participation only in the capacity actually authorized. Where participation is informal, exploratory, learning-based, technical, observer-based, non-committal, or subject to internal government process, the record shall state that limitation.

**6.4.2.4** No participant shall use a public official’s name, ministry name, agency name, public authority logo, public institution title, public-sector email domain, meeting attendance, quotation, photograph, panel appearance, or Nexus Universe presence to imply government endorsement unless the competent public authority has expressly authorized the claim and the claim is recorded within scope.

**6.4.2.5** Government-related language shall be especially controlled in public-safe reporting, sponsor materials, provider materials, investor materials, donor materials, media materials, National Model summaries, Regional Cluster references, AEP Passport references, Nexus Rail references, and handoff records.

**6.4.2.6** Government participation shall not cure other missing authority. It shall not create procurement status, financeability, certification, provider validation, community consent, Indigenous consent, project authorization, data authorization, environmental approval, land access, public warning, or execution authority.

**6.4.2.7** Any government endorsement overclaim shall be treated as a serious claims incident and corrected, narrowed, withdrawn, reclassified, publicly clarified where necessary, or archived.

***

#### 6.4.3 No Procurement Authority

**6.4.3.1** A National Nexus Consortium shall not possess procurement authority. It shall not run tenders, issue procurement notices, award contracts, select vendors, rank bidders, approve suppliers, create preferred-provider lists, grant procurement eligibility, allocate purchasing opportunities, direct public or private procurement, provide bid advice as a procurement authority, or create procurement shortcuts.

**6.4.3.2** The National Nexus Consortium may support procurement-neutral learning, provider-neutral capability mapping, infrastructure-readiness review, technical demonstration preparation, host-readiness inquiry, operator-readiness inquiry, public authority learning, Nexus Core build support, AEP Passport technical layer interpretation, Nexus Rail implementation-readiness routing, National Model readiness mapping, and public-safe reporting. These activities shall remain public-good readiness and learning activities and shall not be represented as procurement activity.

**6.4.3.3** Provider participation in a National Helix Council, Working Group, Competence Cell, Nexus Universe program, technical room, provider-neutral demonstration, public-safe report, AEP Passport input, Nexus Rail input, Docket item, Grid input, National Model reference, or handoff discussion shall not create preferred-provider status, bid advantage, procurement status, procurement eligibility, product approval, service approval, technical approval, or vendor validation.

**6.4.3.4** Public authorities, enterprises, National Consortium Companies, Project SPVs, hosts, operators, development actors, and other lawful procuring or contracting bodies shall remain solely responsible for their own procurement, contracting, competition, fairness, bid evaluation, vendor selection, technical evaluation, financial evaluation, conflict management, market conduct, due diligence, and legal compliance processes.

**6.4.3.5** Procurement-neutrality controls shall include provider-neutral language, conflict disclosure, no-selection language, competition safeguards, confidentiality protections, no bid coordination, no market allocation, no price coordination, no tender substitution, no procurement preference, no technical approval by implication, and correction of procurement overclaims.

**6.4.3.6** The National Nexus Consortium shall not permit sponsors, hosts, providers, technical contributors, public authorities, capital readers, or National Consortium Companies to use national Nexus activity as a procurement signal or market preference unless a competent procuring body separately and lawfully makes a procurement decision outside the national public-good stack.

**6.4.3.7** Any procurement overclaim shall be corrected, including any claim that a provider, technology, platform, service, host, National Consortium Company, Project SPV, Nexus Universe participant, AEP Passport candidate, Nexus Rail candidate, Docket item, Grid input, National Model element, or handoff record has procurement status, procurement advantage, or provider approval by reason of National Nexus Consortium activity.

***

#### 6.4.4 No Finance or Insurance Authority

**6.4.4.1** A National Nexus Consortium shall not have finance, insurance, donor, development finance, or public finance authority. It shall not act as an investment adviser, financial adviser, insurance adviser, broker, dealer, lender, underwriter, insurer, reinsurer, donor, philanthropic grant-maker, public finance authority, development finance authority, rating agency, guarantee facility, fund, securities platform, capital-raising platform, transaction arranger, public finance allocator, or fiduciary to any finance participant by reason of its national public-good role.

**6.4.4.2** The National Nexus Consortium may support finance-readiness, capital-readability, insurance-readiness, reinsurance-readiness, disaster-risk finance question formation, donor relevance, development-readiness, public finance relevance, diligence-gap mapping, proof-pack readability, Project SPV-readiness, no-reliance capital-reader rooms, insurance-readiness rooms, donor and development rooms, public finance relevance rooms, and GRA-aligned finance-readiness translation. These activities shall be non-advisory, non-transactional, non-solicitation, non-placement, non-underwriting, non-rating, non-guarantee, and no-reliance unless separately handled by competent regulated actors outside the National Nexus Consortium.

**6.4.4.3** A national finance-readiness note, capital-readability record, insurance-readiness note, donor relevance note, public finance relevance note, disaster-risk finance note, Project SPV-readiness input, AEP Passport finance layer, Nexus Rail finance-readiness input, Nexus Universe capital-reader room output, National Model finance note, Docket item, Grid input, or public-safe report shall not constitute financeability, bankability, insurability, investment approval, insurance approval, underwriting, guarantee, donor approval, public finance allocation, development finance approval, or transaction readiness.

**6.4.4.4** Capital readers, investors, insurers, reinsurers, donors, philanthropic institutions, development finance actors, public finance actors, banks, funds, and financial institutions participating at national level shall participate only within recorded capacity and subject to no-reliance language, non-solicitation controls, regulated-perimeter discipline, confidentiality obligations, conflict disclosure, market-conduct controls, publication controls, and claims limits.

**6.4.4.5** The National Nexus Consortium shall not publish, permit, or support any statement implying that a country, project, portfolio, company, provider, sponsor, host, National Consortium Company, Project SPV, Nexus Rail, AEP Passport candidate, Nexus Universe output, Docket item, Grid input, National Model element, public-safe report, or handoff candidate is financeable, bankable, insurable, investment-ready, underwritten, guaranteed, donor-approved, public-finance-approved, development-finance-approved, or transaction-ready by reason of national participation.

**6.4.4.6** The National Nexus Consortium shall coordinate finance-readiness translation with GRA-aligned discipline where appropriate while preserving that GRA-aligned readiness does not create regulated financial activity, investment advice, insurance approval, public finance allocation, donor commitment, or transaction execution.

**6.4.4.7** Any finance, insurance, donor, development, or public finance overclaim shall be corrected, narrowed, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 6.4.5 No Certification or Standards Authority by Default

**6.4.5.1** A National Nexus Consortium shall not be a certification body, accreditation body, conformity assessment body, inspection authority, testing authority, standards-setting authority by default, standards-conformance authority, technical approval body, safety approval body, product approval body, compliance body, maturity approval body, or Nexus-ready approval body.

**6.4.5.2** The National Nexus Consortium may support standards localization and standards-interface discipline. It may translate, compare, localize, and explain standards-relevant materials, controlled vocabulary, evidence records, methods, benchmark references, system cards, maturity concepts, public-good technical baselines, interoperability questions, AEP Passport candidate layers, Nexus Grid inputs, Nexus Rail records, public-safe technical summaries, National Model elements, and Nexus Universe technical outputs. Such activity shall support learning, comparability, and readiness, not certification or conformance.

**6.4.5.3** A national technical note, benchmark note, system card, model card, evidence record, method record, public-good software record, Nexus Core input, Nexus Observatory input, AEP Passport layer, Proof Receipt input where authorized, Nexus Rail input, Grid input, Docket item, public-safe report, National Model element, or Nexus Universe technical output shall not be represented as certification, accreditation, standards conformance, maturity approval, safety approval, legal compliance, product approval, system approval, or Nexus-ready status unless separately and lawfully issued by a competent authorized body.

**6.4.5.4** Participation by standards experts, laboratories, technical institutions, universities, public authorities, GCRI-aligned contributors, providers, sponsors, or Nexus Competence Cells shall not create national standards authority or conformance status. Technical seriousness shall be expressed through evidence, methods, documentation, limitations, public-safe reporting, safeguards, and correctionability.

**6.4.5.5** The National Nexus Consortium shall maintain standards-interface language discipline. Terms such as “aligned,” “mapped,” “referenced,” “reviewed,” “benchmarked,” “candidate,” “input,” “layer,” “route,” “record,” “readiness,” “maturity input,” “localization,” and “review” shall not be used in a manner that implies certification, conformance, approval, compliance, or formal standards authority.

**6.4.5.6** National standards localization shall identify, where known, the competent external bodies or processes responsible for formal standards, certification, accreditation, regulatory compliance, procurement compliance, technical approvals, safety approvals, or conformity assessment. The National Nexus Consortium shall not appropriate those roles.

**6.4.5.7** Any national certification or standards overclaim shall be corrected, including claims that a provider, technology, system, National Consortium Company, Project SPV, Nexus Universe output, AEP Passport candidate, Nexus Rail candidate, Docket item, Grid input, National Model element, or public-safe report is certified, standards-compliant, accredited, approved, mature, safe, or Nexus-ready by reason of National Nexus Consortium activity.

***

#### 6.4.6 No Community or Indigenous Consent

**6.4.6.1** A National Nexus Consortium shall not grant, certify, imply, substitute for, aggregate, or evidence community consent, Indigenous consent, FPIC satisfaction where applicable, social license, protected knowledge authorization, land access, site approval, cultural approval, environmental approval, rights-holder approval, local authorization, or place-based consent.

**6.4.6.2** Community participation, Indigenous participation where applicable, diaspora contribution, youth participation, accessibility contribution, lived-risk knowledge, protected knowledge caution, safeguard review, place-based legitimacy input, public-safe reporting, Nexus Universe safeguard room participation, AEP Passport safeguard layer input, Nexus Rail safeguard condition, Docket item, Grid input, National Model safeguard statement, or handoff safeguard condition shall not imply consent, approval, authorization, social license, land access, site access, cultural permission, environmental approval, public authority approval, procurement status, financeability, project authorization, or execution authority.

**6.4.6.3** Indigenous participation shall be subject to heightened boundary discipline where applicable. Participation by Indigenous actors, Tribal actors, traditional authorities, Indigenous organizations, Indigenous researchers, Indigenous knowledge holders, or rights-holders shall not imply Indigenous consent, FPIC satisfaction, consultation completion, accommodation completion, rights waiver, protected knowledge permission, Indigenous data authorization, land approval, cultural approval, project approval, or authority to speak for all relevant Indigenous peoples unless separately and lawfully recorded through the applicable Indigenous governance and legal processes.

**6.4.6.4** Diaspora participation shall not substitute for local authorization. Diaspora actors may contribute knowledge, networks, investment literacy, philanthropic relevance, technical expertise, cultural context, or public-good support, but they shall not authorize local action, speak for local communities without record, approve projects, grant consent, grant land access, or replace local community or Indigenous processes.

**6.4.6.5** National safeguard records shall state their non-consent character. A safeguard record may identify lived-risk concerns, vulnerability, implementation realities, accessibility needs, protected knowledge restrictions, community benefits and harms, environmental concerns, trust conditions, grievance pathways, public-safe language requirements, and handoff restrictions. It shall not authorize deployment, procurement, finance, public authority action, or project execution.

**6.4.6.6** The National Nexus Consortium shall maintain consent-language discipline in all national materials. Terms implying “approved by communities,” “community-endorsed,” “Indigenous-approved,” “FPIC-complete,” “socially licensed,” “locally authorized,” “protected knowledge authorized,” or equivalent language shall not be used unless supported by separate lawful records from the competent process and expressly limited to their scope.

**6.4.6.7** Any consent overclaim shall be treated as a serious boundary incident and corrected, narrowed, withdrawn, reclassified, publicly clarified where necessary, or archived.

***

#### 6.4.7 No Project Authorization

**6.4.7.1** A National Nexus Consortium shall not authorize projects. It shall not approve, license, permit, finance, insure, procure, select, certify, validate, construct, operate, command, implement, manage, or deliver any project, asset, infrastructure, technology deployment, platform, public authority program, National Consortium Company activity, Project SPV activity, provider engagement, local implementation pathway, or enterprise activity.

**6.4.7.2** The National Nexus Consortium may support project-related readiness through public-good records, including evidence notes, technical-readiness notes, observability notes, public authority dependency notes, finance-readiness notes, insurance-readiness notes, donor relevance notes, development-readiness notes, public finance relevance notes, provider-neutral capability maps, safeguard records, protected knowledge cautions, Nexus Universe outputs, AEP Passport candidate layers, Proof Receipt inputs where authorized, Nexus Rail candidates, Docket items, Grid inputs, National Model elements, and lawful handoff conditions. These records shall not authorize the project.

**6.4.7.3** Project authorization may occur only through competent external actors and lawful processes, including, where applicable, public authority approvals, permits, licenses, procurement processes, finance processes, insurance processes, donor or development finance approvals, public finance allocations, enterprise governance, National Consortium Company governance, Project SPV governance, community processes, Indigenous protocols where applicable, environmental and social review, data permissions, cyber approvals, host agreements, operator agreements, provider contracts, and project-specific legal instruments.

**6.4.7.4** Inclusion of a project, candidate, pathway, corridor, node, system, technology, host, provider, National Consortium Company, Project SPV, or portfolio in a national priority, National Model, Nexus Universe program, public-safe report, AEP Passport pathway, Nexus Rail pathway, Docket, Grid, or handoff discussion shall not be treated as project approval or execution authorization.

**6.4.7.5** Project-related language shall distinguish among concept, candidate, input, record, readiness note, dependency, route, handoff condition, and authorized project. Only a competent actor outside the National Nexus Consortium may create project authorization, and only through a separate lawful process.

**6.4.7.6** The National Nexus Consortium shall not become an operator, contractor, developer, project manager, project sponsor, implementation partner, procurement agent, lender, insurer, public authority, consent body, or technical certifier by supporting readiness, convening national rooms, preparing National Model elements, or issuing handoff records.

**6.4.7.7** Any claim that the National Nexus Consortium has approved, authorized, financed, guaranteed, procured, certified, selected, insured, launched, deployed, operated, managed, delivered, or executed a project shall be corrected unless supported by a separate lawful record from a competent actor and unless the National Nexus Consortium’s non-executing role remains expressly preserved.

***

#### 6.4.8 No Provider Selection

**6.4.8.1** A National Nexus Consortium shall not select providers. It shall not choose vendors, approve suppliers, validate technologies, rank providers, establish preferred-provider status, award provider opportunities, grant provider qualification, grant procurement eligibility, issue provider endorsements, or confer provider advantage.

**6.4.8.2** The National Nexus Consortium may support provider-neutral contribution, provider-neutral capability mapping, technical demonstration rooms, infrastructure-readiness review, public-good software contribution, Nexus Core build support, evidence formation, observability input, AEP Passport technical layer support, Nexus Rail implementation-readiness support, public-safe technical summaries, and Working Group or Competence Cell participation. Such support shall not be represented as provider selection.

**6.4.8.3** Provider participation, sponsor participation, host participation, technical demonstration, public-good software contribution, Nexus Universe visibility, public-safe report reference, AEP Passport input, Nexus Rail input, Docket item, Grid input, National Model reference, or handoff discussion shall not create preferred-provider status, provider validation, technical approval, product approval, service approval, standards conformance, Nexus-ready status, procurement eligibility, or commercial entitlement.

**6.4.8.4** Provider-neutrality shall require that national materials avoid statements implying that one provider is selected, recommended, preferred, certified, approved, procurement-ready, or uniquely authorized unless a competent external actor has separately and lawfully made such determination outside the national public-good stack.

**6.4.8.5** Providers shall disclose conflicts and shall not use national participation to influence public-good records for commercial advantage, suppress competitor information, obtain procurement intelligence improperly, misrepresent technical status, create market allocation, coordinate pricing, or convert Nexus Universe visibility into provider approval.

**6.4.8.6** If a separate qualified-provider pathway is ever authorized by a competent body, such pathway shall require separate rules, eligibility criteria, conflicts review, claims controls, procurement-neutrality controls, public-good firewall controls, correction mechanisms, and express limitation language. No such pathway shall be implied from general national participation.

**6.4.8.7** Any provider-selection or provider-validation overclaim shall be corrected, including claims that a provider, technology, platform, service, host, operator, National Consortium Company, Project SPV, AEP Passport candidate, Nexus Rail candidate, Nexus Universe output, Docket item, Grid input, or National Model element has been selected, approved, validated, preferred, or procurement-enabled by the National Nexus Consortium.

***

#### 6.4.9 No Enterprise Execution Unless Through Separate Lawful Vehicle

**6.4.9.1** A National Nexus Consortium shall not engage in enterprise execution except through a separate lawful vehicle that is legally distinct from the National Nexus Consortium and expressly constituted for enterprise, project, operational, contractual, financial, procurement, implementation, or delivery activity. The National Nexus Consortium itself shall remain a non-executing public-good gateway and shall not become an enterprise actor by implication.

**6.4.9.2** Enterprise execution may occur only through competent external or separate lawful actors, including National Consortium Companies, Project SPVs, providers, operators, hosts, contractors, public authorities, investors, insurers, donors, development finance actors, procurement bodies, enterprises, or other lawful actors acting under their own governance, contracts, authority, liability, insurance, finance, tax, data, cyber, environmental, social, community, Indigenous where applicable, employment, procurement, and operational obligations.

**6.4.9.3** The National Consortium Company, where lawfully formed, shall be separate from the National Nexus Consortium. It shall have its own legal form, governance, capitalization, accounts, liabilities, contracts, duties, conflicts, tax position, employment obligations, data obligations, cyber obligations, finance arrangements, procurement obligations where applicable, insurance, safeguards, public authority dependencies, community processes, Indigenous protocols where applicable, and project responsibilities.

**6.4.9.4** A Project SPV, where lawfully formed, shall be separate from both the National Nexus Consortium and, unless otherwise lawfully structured, the National Consortium Company. It shall be responsible for its own project-specific governance, ownership, capitalization, finance, insurance, procurement, permits, contracts, environmental and social obligations, community processes, Indigenous protocols where applicable, data and cyber controls, operations, reporting, liabilities, and decommissioning.

**6.4.9.5** Lawful handoff from the National Nexus Consortium to a National Consortium Company, Project SPV, provider, host, operator, public authority, finance actor, insurer, donor, or other external actor shall not convert the National Nexus Consortium into a shareholder, director, officer, fiduciary, agent, guarantor, lender, insurer, contractor, operator, project sponsor, procurement body, or execution party unless a separate lawful instrument expressly creates a limited relationship outside the public-good role and the non-execution boundary remains clear.

**6.4.9.6** Public-good records shall not be used as disguised enterprise mandates. A National Model element, Nexus Universe output, AEP Passport input, Nexus Rail route, Docket item, Grid input, finance-readiness note, public authority dependency note, provider-neutral capability map, safeguard record, or handoff record shall not authorize a National Consortium Company, Project SPV, provider, sponsor, host, or operator to claim National Nexus Consortium approval, execution backing, finance support, public authority endorsement, procurement status, certification, or consent.

**6.4.9.7** Any enterprise-execution implication shall be corrected. Where a public statement, contract reference, sponsor material, provider material, media reference, Nexus Universe presentation, public authority reference, finance-readiness note, handoff note, National Consortium Company reference, or Project SPV reference implies that the National Nexus Consortium is executing, operating, managing, delivering, financing, procuring, insuring, building, or contracting, the statement or record shall be narrowed, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 6.4.10 National Claims Correction

**6.4.10.1** Each National Nexus Consortium shall maintain a mandatory **National Claims Correction** function. This function shall identify, review, correct, narrow, restrict, withdraw, supersede, publicly clarify where necessary, and archive claims made by or about the National Nexus Consortium, National Council, National Leadership Council, National Investors Council, Helix Councils, Working Groups, Competence Cells, Nexus Universe national participants, sponsors, providers, hosts, partners, public authorities, capital readers, insurers, donors, media actors, communities, Indigenous actors where applicable, National Consortium Companies, Project SPVs, AEP Passport candidates, Nexus Rail candidates, Docket items, Grid inputs, National Model elements, public-safe reports, and lawful handoff pathways.

**6.4.10.2** National Claims Correction shall apply to any claim that is inaccurate, unsupported, incomplete, misleading, outdated, unsafe, overbroad, overreliant, overpublicized, inconsistent with the record, inconsistent with public-safe classification, inconsistent with role separation, inconsistent with national ownership, inconsistent with safeguard conditions, or capable of creating unlawful reliance.

**6.4.10.3** Claims requiring correction may include, without limitation, claims of:

1. public authority status or government endorsement;
2. regulatory approval, public authority approval, public finance approval, or compliance determination;
3. procurement status, preferred-provider status, or vendor selection;
4. provider validation, technical approval, product approval, or system approval;
5. certification, accreditation, standards conformance, maturity approval, Nexus-ready status, AEP Passport status, Nexus Node status, Grid maturity status, or Nexus Rail approval;
6. financeability, bankability, insurability, investment approval, insurance approval, underwriting, guarantee, donor approval, public finance allocation, development finance approval, or transaction readiness;
7. community consent, community approval, social license, Indigenous consent, FPIC satisfaction where applicable, protected knowledge authorization, land access, site approval, cultural approval, environmental approval, or place-based approval;
8. public warning, emergency command, public safety order, or official risk notice;
9. project authorization, deployment approval, operational authority, enterprise execution, National Consortium Company approval, or Project SPV approval;
10. GCRI, GRF, GRA, Global Nexus Consortium, or Regional Headquarters Consortium endorsement, authority, or approval without separate record; and
11. lawful handoff meaning execution.

**6.4.10.4** National Claims Correction may be triggered by internal review, Regional Headquarters Consortium review, Global Nexus Consortium review, public authority concern, community concern, Indigenous concern where applicable, media misstatement, sponsor material, provider material, capital-reader material, public-safe reporting review, Nexus Universe monitoring, AEP Passport review, Nexus Rail review, Docket review, Grid review, handoff review, or post-cycle audit.

**6.4.10.5** Correction measures may include private notice, controlled clarification, public-safe clarification, record amendment, claim narrowing, name-use restriction, mark-use restriction, publication reclassification, removal of public listing, withdrawal of sponsor or provider communication, correction of Nexus Universe materials, correction of public-safe reports, correction of National Model language, correction of AEP Passport or Nexus Rail references, correction of Docket or Grid references, suspension of participation, restriction of room access, withdrawal of handoff, supersession of records, archive notation, or public statement where necessary to prevent misunderstanding.

**6.4.10.6** The National Nexus Consortium shall not allow public authority sensitivity, sponsor sensitivity, provider importance, investor interest, donor sensitivity, media attention, national politics, community politics, Nexus Universe prominence, partner pressure, enterprise pressure, or institutional embarrassment to prevent necessary correction.

**6.4.10.7** National Claims Correction shall be continuous and retroactive. A claim may be corrected after publication, presentation, media circulation, sponsor use, provider use, handoff, archive, or downstream reference. No claim shall become valid by repetition, visibility, reliance, passage of time, or failure to correct at first instance.

**6.4.10.8** The National Nexus Consortium shall treat claims correction as a core legitimacy function. The national layer’s credibility rests not on avoiding every error in a complex multi-actor architecture, but on maintaining the capacity to detect, acknowledge, narrow, correct, withdraw, supersede, and archive errors before they become institutional overclaim, public confusion, safeguard harm, unlawful reliance, or execution drift.


---

# 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/vi.-national.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.