# IX. HANDOFF

This section defines how the National Leadership Council supports the **National Model**, **National Working Groups**, **National Consortium Company interfaces**, and **Project SPV interfaces**.

It explains how readiness is recorded, how structured work is formed, and how lawful handoff stays bounded. It also clarifies what the Council does **not** approve, authorize, finance, procure, certify, or execute.

### Summary

* The **National Model** records country-level readiness without creating approval or authority.
* **National Working Groups** structure evidence, learning, and safeguards without becoming decision-makers.
* **National Consortium Company** and **Project SPV** pathways stay separate from the public-good leadership role.

## **9.1 National Model Support**

### **9.1.1 National Model as Country-Level Readiness Record**

**9.1.1.1** The **National Model** shall be understood as the country-level readiness record of the Nexus Consortium architecture. It is the structured national instrument through which a country’s Nexus priorities, public authority interfaces, Helix Council inputs, National Working Group outputs, technical assets, finance-readiness gaps, safeguard conditions, Nexus Universe participation, Nexus Observatory pathways, Nexus Rail routes, AEP Passport candidates, public-safe reporting conditions, National Consortium Company interfaces, Project SPV-readiness questions, Docket items, Grid inputs where applicable, and lawful handoff conditions are recorded.

**9.1.1.2** The National Model shall not be treated as a government plan, investment memorandum, procurement document, certification report, public authority approval, public warning, project authorization, provider catalogue, sponsor narrative, or execution mandate unless a separate competent record gives a specific external document that status.

**9.1.1.3** The National Model’s principal function is to make national readiness legible without overstating readiness. It should clarify what exists, what is being prepared, what is only candidate status, what remains incomplete, what requires public authority action, what requires finance-readiness work, what requires safeguard review, what may be public-safe, what must remain controlled, and what may later be eligible for lawful handoff.

**9.1.1.4** The National Model shall preserve the distinction between public-good readiness and enterprise execution. It may identify implementation-facing pathways, but it does not itself execute, finance, insure, procure, approve, certify, consent, or authorize.

**9.1.1.5** The National Leadership Council shall support the National Model as a leadership, agenda, cross-helix, public-safe, and renewal input body, not as the sole owner or final approver of the National Model unless separate governance records provide otherwise.

**9.1.1.6** The governing rule shall be:

**The National Model records country-level Nexus readiness; it does not create national authority, finance, certification, procurement, consent, or execution by itself.**

***

### **9.1.2 Leadership Council Role in National Model Prioritization**

**9.1.2.1** The National Leadership Council shall support prioritization of National Model content by identifying which national matters require inclusion, update, restriction, correction, Docket handling, Nexus Universe mobilization, AEP Passport preparation, Nexus Rail routing, Observatory treatment, public authority learning, finance-readiness interpretation, safeguard review, National Working Group formation, or lawful handoff scoping.

**9.1.2.2** The Council’s prioritization role may include:

a) identifying national leadership priorities;\
b) reviewing National Council agenda inputs;\
c) reviewing Helix Council inputs;\
d) reviewing National Investors Council finance-readiness inputs;\
e) identifying National Working Group outputs relevant to the National Model;\
f) identifying Nexus Universe annual-cycle priorities;\
g) identifying public authority-sensitive matters;\
h) identifying safeguard-sensitive matters;\
i) identifying public-safe summary candidates;\
j) identifying matters requiring correction, withdrawal, restriction, or archive.

**9.1.2.3** Prioritization shall be based on national relevance, public-good value, evidence need, readiness status, public authority dependency, finance-readiness relevance, safeguard sensitivity, regional and global alignment, Nexus Universe relevance, and lawful handoff potential.

**9.1.2.4** Prioritization shall not be controlled by sponsor preference, provider marketing, capital-reader interest, media opportunity, public-stage visibility, founder preference, regional pressure, global pressure, or event deadlines.

**9.1.2.5** Prioritization by the National Leadership Council shall not constitute final National Model approval unless a competent governance record grants that authority.

**9.1.2.6** The governing rule shall be:

**The Council may prioritize National Model inputs; the record determines National Model status.**

***

### **9.1.3 National Model Inputs From Helix Councils**

**9.1.3.1** The National Leadership Council shall support structured integration of National Model inputs from Helix Councils.

**9.1.3.2** Helix Council inputs may include public authority learning needs, academic and research evidence, industry and infrastructure capability, capital and insurance-readiness observations, donor and development relevance, media and civic public-safe communication inputs, community and Indigenous safeguard concerns where applicable, diaspora perspectives, youth and accessibility insights, and other nationally relevant stakeholder intelligence.

**9.1.3.3** The National Leadership Council shall help ensure that Helix Council inputs are integrated without distorting their meaning or collapsing their role boundaries.

**9.1.3.4** Helix Council input shall be classified by source, role, public authority status, finance-readiness status, technical status, safeguard status, public-safe status, confidentiality class, conflict implications, and correction pathway.

**9.1.3.5** The Council shall not treat one helix’s input as controlling the National Model. Public authority input is not automatic approval. Industry input is not provider selection. Capital input is not finance. Academic input is not certification. Media input is not public-safe release. Community or Indigenous input is not consent.

**9.1.3.6** The governing rule shall be:

**Helix inputs enrich the National Model; they do not replace National Model discipline.**

***

### **9.1.4 National Model Public Authority Layer**

**9.1.4.1** The National Model shall include, where applicable, a public authority layer that identifies public authorities, public authority roles, public authority learning needs, public authority status classifications, regulatory dependencies, procurement boundaries, public finance relevance, emergency-management boundaries, public-warning limits, and lawful approval pathways relevant to national Nexus activity.

**9.1.4.2** The National Leadership Council may support the public authority layer by identifying where public authority learning is needed, where public authority status is ambiguous, where public authority-facing materials require review, and where public authority participation must be carefully described.

**9.1.4.3** The public authority layer shall distinguish between:

a) official public authority approval;\
b) official participation;\
c) observer participation;\
d) learning participation;\
e) technical contribution;\
f) public-safe review;\
g) data-stewardship role;\
h) regulator observation;\
i) public finance reading;\
j) no official position;\
k) status pending clarification.

**9.1.4.4** Public authority status shall be explicitly recorded. Where unclear, the default shall be no approval, no endorsement, no adoption, no procurement, no funding, no public finance commitment, no public warning, no emergency command, no delegation, and no official position.

**9.1.4.5** The public authority layer shall not be used to imply public authority support where no such support exists.

**9.1.4.6** The governing rule shall be:

**The National Model may record public authority context; it must not manufacture public authority approval.**

***

### **9.1.5 National Model Technical Layer**

**9.1.5.1** The National Model may include a technical layer that records technical assets, evidence needs, methods, data sources, Nexus Observatory candidates, Nexus Core candidates, digital public infrastructure, AI systems, cyber posture, compute resources, connectivity, sensing, geospatial systems, digital twins, public-good software, interoperability needs, standards-interface questions, and AEP Passport technical candidates.

**9.1.5.2** The National Leadership Council may support the technical layer by identifying technical priorities, routing technical issues to National Working Groups, connecting technical contributors to GCRI-aligned methods where appropriate, identifying evidence gaps, and ensuring that technical materials are not overclaimed.

**9.1.5.3** The technical layer shall distinguish between:

a) demonstrated capability;\
b) tested capability;\
c) evidence-supported capability;\
d) prototype capability;\
e) concept-stage capability;\
f) provider-provided claim;\
g) independently reviewed evidence;\
h) public-safe technical summary;\
i) controlled technical material;\
j) restricted or cyber-sensitive material.

**9.1.5.4** Technical inclusion in the National Model shall not imply technical validation, certification, provider endorsement, standards conformance, public authority approval, procurement readiness, finance-readiness, or deployment authorization.

**9.1.5.5** Technical limitations, uncertainty, data quality constraints, cyber conditions, interoperability issues, and safeguard concerns shall be recorded rather than hidden.

**9.1.5.6** The governing rule shall be:

**The technical layer records what is known, what is tested, what is claimed, and what remains uncertain; it does not certify technology by inclusion.**

***

### **9.1.6 National Model Finance-Readiness Layer**

**9.1.6.1** The National Model may include a finance-readiness layer that records capital-readability, insurance-readiness, disaster-risk-finance relevance, public finance relevance, donor relevance, philanthropic relevance, diligence gaps, SPV-readiness questions, National Consortium Company interface needs, and lawful handoff conditions.

**9.1.6.2** The National Leadership Council may support the finance-readiness layer in coordination with the National Investors Council and GRA-aligned discipline where applicable.

**9.1.6.3** The finance-readiness layer shall distinguish between:

a) finance-readiness question;\
b) capital-readable evidence need;\
c) insurance-readiness question;\
d) public finance relevance;\
e) donor relevance;\
f) philanthropic relevance;\
g) diligence gap;\
h) SPV-readiness condition;\
i) no-reliance capital-reader note;\
j) unresolved finance-boundary issue.

**9.1.6.4** Finance-readiness layer inclusion shall not imply investment interest, finance approval, bankability, financeability, insurance approval, underwriting, guarantee, rating, public finance approval, donor approval, philanthropic commitment, or transaction readiness.

**9.1.6.5** The finance-readiness layer shall be non-advisory, no-reliance, non-soliciting, non-transactional, confidentiality-aware, competition-compliant, and regulated-perimeter aware.

**9.1.6.6** The governing rule shall be:

**The finance-readiness layer makes readiness readable without making finance claims.**

***

### **9.1.7 National Model Safeguard Layer**

**9.1.7.1** The National Model shall include, where applicable, a safeguard layer identifying privacy, cybersecurity, sovereign data, public authority sensitivity, community protection, Indigenous safeguards where applicable, protected knowledge, accessibility, health data, biodiversity-sensitive information, critical infrastructure exposure, location-sensitive information, procurement neutrality, sponsor or provider conflict risks, public-safe reporting limits, and non-extractive participation requirements.

**9.1.7.2** The National Leadership Council may support the safeguard layer by identifying safeguard concerns, routing matters to safeguard processes, ensuring public-safe communication limits, and preventing premature public or enterprise use of sensitive materials.

**9.1.7.3** The safeguard layer shall identify:

a) affected persons, communities, systems, places, datasets, or knowledge categories where appropriate;\
b) sensitivity classification;\
c) consent or authorization requirements;\
d) publication limits;\
e) data-handling limits;\
f) cyber controls;\
g) public authority-sensitive controls;\
h) community and Indigenous safeguard controls;\
i) restricted-room requirements;\
j) correction pathway.

**9.1.7.4** Safeguard inclusion in the National Model shall not constitute consent, legal approval, public authority approval, community approval, Indigenous approval, data authorization, protected-knowledge permission, or permission to publish, commercialize, map, automate, operationalize, or hand off.

**9.1.7.5** Where safeguard readiness is incomplete, the National Model shall record the gap rather than present the matter as ready.

**9.1.7.6** The governing rule shall be:

**The safeguard layer protects national readiness from becoming harmful readiness.**

***

### **9.1.8 National Model Public-Safe Summary**

**9.1.8.1** The National Model may include a public-safe summary prepared for external understanding, Nexus Universe participation, national stakeholder communication, regional and global routing, and public-good reporting.

**9.1.8.2** The National Leadership Council may support preparation or review of the public-safe summary by identifying claims limits, public authority status language, finance-readiness disclaimers, technical limitations, sponsor and provider boundaries, community and Indigenous safeguard language, data restrictions, Nexus Universe status, and correction notes.

**9.1.8.3** A public-safe summary shall state only what may safely be communicated. It shall not include restricted data, protected knowledge, cyber-sensitive information, confidential public authority material, unreleased finance-readiness material, provider-sensitive technical information, or community-sensitive information unless approved for release through the proper process.

**9.1.8.4** The public-safe summary shall not imply that the National Model is government-approved, investment-ready, certified, procurement-ready, community-consented, Indigenous-approved, or execution-authorized.

**9.1.8.5** Public-safe summaries shall remain subject to correction, supersession, withdrawal, and archive.

**9.1.8.6** The governing rule shall be:

**The public-safe summary communicates national readiness carefully; it does not convert readiness into public authority or market claims.**

***

### **9.1.9 National Model Correction**

**9.1.9.1** The National Leadership Council shall support correction of the National Model where leadership records, agenda priorities, Helix inputs, public authority status, technical evidence, finance-readiness notes, safeguard conditions, public-safe summaries, Nexus Universe materials, AEP Passport candidates, Nexus Rail pathways, Docket items, Grid inputs, handoff references, or enterprise interface notes are inaccurate, incomplete, outdated, unsafe, overstated, or misleading.

**9.1.9.2** Correction may include:

a) clarification;\
b) amendment;\
c) reclassification;\
d) restriction;\
e) supersession;\
f) withdrawal;\
g) public-safe correction;\
h) Docket entry;\
i) referral to National Council, Stewardship Board, Helix Council, National Investors Council, National Working Group, GRF, GCRI, GRA, Regional Nexus Consortium, or competent public authority process;\
j) archive of superseded material.

**9.1.9.3** National Model correction shall be recorded with the reason, affected section, authority, date, replacement language where applicable, public-safe implications, and future prevention measures.

**9.1.9.4** Correction shall not be delayed to protect sponsor interests, provider interests, capital-reader expectations, public authority optics, media narrative, event materials, or institutional pride.

**9.1.9.5** The governing rule shall be:

**A National Model that cannot correct itself cannot safely guide national readiness.**

***

### **9.1.10 National Model Renewal**

**9.1.10.1** The National Leadership Council shall support periodic renewal of the National Model, preferably in connection with the Nexus Universe annual cycle, National Council renewal, Helix Council review, National Investors Council review, National Working Group review, public-safe reporting review, and post-cycle correction.

**9.1.10.2** Renewal shall review:

a) national priorities;\
b) leadership-pool inputs;\
c) Helix Council inputs;\
d) National Working Group outputs;\
e) public authority status;\
f) technical evidence;\
g) finance-readiness layer;\
h) safeguard layer;\
i) Nexus Universe outcomes;\
j) AEP Passport candidates;\
k) Nexus Rail pathways;\
l) Docket items;\
m) Grid inputs where applicable;\
n) National Consortium Company interface;\
o) Project SPV-readiness questions;\
p) public-safe summaries.

**9.1.10.3** Renewal may result in continuation, update, expansion, restriction, correction, withdrawal, consolidation, archiving, or escalation.

**9.1.10.4** The renewed National Model shall identify what changed, why it changed, what remains unresolved, what is public-safe, what is controlled, what is restricted, and what is eligible for further routeability.

**9.1.10.5** The governing rule shall be:

**The National Model must renew with the country’s learning, not freeze the country’s readiness in outdated form.**

***

## **9.2 National Working Groups**

### **9.2.1 Working Group Identification**

**9.2.1.1** The National Leadership Council shall identify where National Working Groups may be needed to convert national priorities into structured public-good work.

**9.2.1.2** A National Working Group may be needed where a matter requires sustained attention, technical review, policy development, public authority learning preparation, finance-readiness mapping, safeguard review, public-safe reporting, National Model preparation, Nexus Universe preparation, Nexus Observatory development, Nexus Rail routing, AEP Passport candidate preparation, Docket handling, or lawful handoff scoping.

**9.2.1.3** Working Group identification shall be based on national need, public-good value, evidence requirements, cross-helix input, public authority sensitivity, finance-readiness relevance, safeguard conditions, and Nexus Universe relevance.

**9.2.1.4** The Council shall not create working groups merely for prestige, visibility, sponsor satisfaction, provider positioning, public authority optics, capital-reader attention, media programming, or title creation.

**9.2.1.5** The governing rule shall be:

**A National Working Group should exist only where structured work is needed and recordable.**

***

### **9.2.2 Working Group Proposal**

**9.2.2.1** The National Leadership Council may prepare or recommend a Working Group Proposal for consideration by the National Council, National Nexus Consortium Stewardship Board where formed, National Secretariat, National Desk, or other competent body.

**9.2.2.2** A Working Group Proposal should identify:

a) proposed name;\
b) public-good rationale;\
c) national priority addressed;\
d) relationship to National Model;\
e) relationship to Nexus Universe;\
f) relevant Helix Councils;\
g) relationship to National Investors Council where finance-readiness is relevant;\
h) proposed scope;\
i) proposed outputs;\
j) proposed participants or participant classes;\
k) proposed lead or co-lead candidates;\
l) evidence needs;\
m) public authority status issues;\
n) finance-readiness boundaries;\
o) safeguard requirements;\
p) confidentiality and public-safe classification;\
q) reporting line;\
r) term or review cycle;\
s) correction pathway.

**9.2.2.3** A Working Group Proposal is not a working group. The working group exists only when constituted by competent record.

**9.2.2.4** A Working Group Proposal shall not be publicized as an active workstream unless approved for that purpose.

**9.2.2.5** The governing rule shall be:

**Proposal prepares formation; formation requires record.**

***

### **9.2.3 Working Group Terms of Reference**

**9.2.3.1** Every National Working Group should operate under written Terms of Reference adopted by the competent body.

**9.2.3.2** Working Group Terms of Reference shall identify purpose, scope, outputs, participants, leads, reporting line, authority limits, confidentiality, public-safe communication rules, data controls, public authority boundaries, finance-readiness boundaries, safeguard requirements, conflict controls, Nexus Universe relevance, National Model relevance, Docket relation, renewal process, and correction process.

**9.2.3.3** Terms of Reference shall expressly state that a working group does not approve projects, certify technology, select providers, procure goods or services, provide finance, provide insurance, issue public warnings, bind public authorities, grant community or Indigenous consent, or execute.

**9.2.3.4** Working Group Terms of Reference shall be reviewed periodically and corrected where necessary.

**9.2.3.5** The governing rule shall be:

**Working groups require Terms of Reference because structured work must remain bounded.**

***

### **9.2.4 Working Group Lead Candidate Pool**

**9.2.4.1** The National Leadership Council may maintain or contribute to a Working Group Lead Candidate Pool.

**9.2.4.2** Candidate-pool review shall consider expertise, contribution record, leadership discipline, conflict status, claims compliance, confidentiality reliability, safeguard competence, public authority boundary awareness, finance-readiness boundary awareness, and correction history.

**9.2.4.3** Working Group Lead candidacy shall be workstream-specific. A person suitable for one working group may not be suitable for another.

**9.2.4.4** Inclusion in the Working Group Lead Candidate Pool shall not create appointment as a Working Group Lead.

**9.2.4.5** The governing rule shall be:

**Lead candidacy identifies possible service; appointment requires the working-group record.**

***

### **9.2.5 Technical Working Groups**

**9.2.5.1** The National Leadership Council may recommend Technical Working Groups where national Nexus work requires technical evidence, methods, data, observability, AI, cyber, compute, connectivity, sensing, geospatial systems, digital twins, public-good software, standards-interface work, Nexus Core preparation, Nexus Observatory development, Nexus Rails, AEP Passport technical layers, or technical public-safe reporting.

**9.2.5.2** Technical Working Groups shall operate under evidence discipline, methods discipline, data protection, cybersecurity controls, public-safe communication rules, provider-neutrality rules, technical limitation reporting, and correctionability.

**9.2.5.3** Technical Working Groups shall not certify technologies, approve providers, determine procurement readiness, issue legal compliance findings, confirm public authority approval, confirm finance-readiness, or authorize deployment.

**9.2.5.4** Provider contributions to Technical Working Groups shall be classified and separated from public-good findings.

**9.2.5.5** The governing rule shall be:

**Technical Working Groups produce evidence and questions, not certification or procurement outcomes.**

***

### **9.2.6 Public Authority Learning Working Groups**

**9.2.6.1** The National Leadership Council may recommend Public Authority Learning Working Groups where national Nexus work requires safe public authority engagement, policy learning, regulatory learning, public finance learning, procurement-neutral learning, emergency-management learning, public utility learning, or official-status classification.

**9.2.6.2** Public Authority Learning Working Groups shall support learning, not official decision-making, unless a competent public authority separately establishes a lawful official process.

**9.2.6.3** Such working groups shall classify public authority participation as official, observer, learner, technical contributor, data steward, public-safe reviewer, personal capacity, or no official position, as applicable.

**9.2.6.4** Outputs shall not be described as government approval, regulatory approval, public finance approval, procurement status, official adoption, public warning, policy decision, or public authority delegation unless separately and lawfully recorded.

**9.2.6.5** The governing rule shall be:

**Public Authority Learning Working Groups make learning safe without replacing public authority.**

***

### **9.2.7 Finance-Readiness Working Groups**

**9.2.7.1** The National Leadership Council may recommend Finance-Readiness Working Groups in coordination with the National Investors Council and GRA-aligned discipline where finance-readiness, capital-readability, insurance-readiness, donor-readiness, public finance relevance, SPV-readiness, or lawful handoff requires structured work.

**9.2.7.2** Finance-Readiness Working Groups shall operate on a non-advisory, no-reliance, non-soliciting, non-transactional, confidentiality-aware, competition-compliant, and regulated-perimeter basis.

**9.2.7.3** Finance-Readiness Working Groups may identify evidence gaps, diligence gaps, capital-readability issues, insurance-readiness questions, public finance relevance, donor or philanthropic relevance, SPV-readiness conditions, and handoff dependencies.

**9.2.7.4** Such working groups shall not provide investment advice, raise capital, arrange finance, broker transactions, underwrite insurance, rate projects, guarantee outcomes, approve donors, approve public finance, or confirm financeability, bankability, or insurability.

**9.2.7.5** The governing rule shall be:

**Finance-Readiness Working Groups make risk more readable without becoming financial actors.**

***

### **9.2.8 Safeguard Working Groups**

**9.2.8.1** The National Leadership Council may recommend Safeguard Working Groups where national Nexus work requires structured treatment of privacy, cyber, sovereign data, public authority sensitivity, community protection, Indigenous safeguards where applicable, protected knowledge, accessibility, health data, biodiversity-sensitive information, critical infrastructure exposure, public-safe reporting, or non-extractive participation.

**9.2.8.2** Safeguard Working Groups shall identify risks, restrictions, required processes, consent boundaries, lawful authorization needs, public-safe communication limits, and escalation routes.

**9.2.8.3** Safeguard Working Groups shall not grant consent, waive rights, authorize publication, approve legal compliance, override public authority processes, or provide community or Indigenous approval unless separately and lawfully authorized by the appropriate rights-holder or competent process.

**9.2.8.4** Safeguard Working Group materials may require restricted handling and shall not be disclosed publicly without public-safe review.

**9.2.8.5** The governing rule shall be:

**Safeguard Working Groups protect readiness from causing harm.**

***

### **9.2.9 Nexus Universe Working Groups**

**9.2.9.1** The National Leadership Council may recommend Nexus Universe Working Groups where national participation in the annual cycle requires dedicated preparation.

**9.2.9.2** Nexus Universe Working Groups may support National Model preparation, delegation preparation, Government Portfolio Showcase preparation, Nexus Core candidates, Observatory candidates, Rail pathways, AEP Passport candidates, public authority rooms, capital-reader rooms, safeguard rooms, public-safe reporting, Docket capture, and post-cycle renewal.

**9.2.9.3** Nexus Universe Working Groups shall ensure that national participation is prepared through records, role classification, public-safe communication, finance-readiness boundaries, public authority status classification, safeguard readiness, and correction procedures.

**9.2.9.4** Participation in a Nexus Universe Working Group shall not guarantee public-stage visibility, official delegation status, public authority approval, finance-readiness, certification, procurement status, consent, or execution readiness.

**9.2.9.5** The governing rule shall be:

**Nexus Universe Working Groups prepare the annual surge; they do not create annual-stage entitlement.**

***

### **9.2.10 Working Group Review, Closure, or Renewal**

**9.2.10.1** The National Leadership Council shall support periodic review of National Working Groups within its mandate.

**9.2.10.2** Review may consider mandate relevance, output quality, evidence status, contribution, participation, conflicts, public-safe reporting, finance-readiness boundaries, public authority status, safeguard compliance, Nexus Universe relevance, National Model relevance, Docket items, Rail routing, AEP Passport relevance, and handoff conditions.

**9.2.10.3** Review may recommend continuation, renewal, re-scoping, merger, split, pause, closure, correction, restriction, archive, or escalation.

**9.2.10.4** Closure of a working group shall not erase its records. Records shall be archived, corrected, restricted, or superseded as appropriate.

**9.2.10.5** The governing rule shall be:

**Working groups must continue only where their work remains useful, bounded, and trustworthy.**

***

## **9.3 National Consortium Company Interface**

### **9.3.1 National Consortium Company as Separate Enterprise-Stack Vehicle**

**9.3.1.1** A **National Consortium Company** shall be understood as a separate enterprise-stack vehicle that may be formed under applicable law to receive lawful implementation-facing handoff, organize enterprise activity, support project-development pathways, contract where authorized, interface with providers, support National Nexus Consortium implementation interfaces, and prepare Project SPV pathways where appropriate.

**9.3.1.2** The National Consortium Company is not the National Leadership Council. It is not the National Council. It is not the National Nexus Consortium public-good body. It is not the National Model. It is not GRF, GCRI, or GRA. It is not a public authority by default.

**9.3.1.3** The National Consortium Company shall remain legally, operationally, financially, and governance-separated from the National Leadership Council unless a specific lawful interface is recorded.

**9.3.1.4** The National Leadership Council may identify when a National Consortium Company interface may become relevant, but it shall not create, own, govern, manage, finance, insure, procure for, contract for, or control the Company by implication.

**9.3.1.5** The governing rule shall be:

**The National Consortium Company is an enterprise-stack vehicle; the National Leadership Council remains a public-good leadership gateway.**

***

### **9.3.2 Leadership Council Handoff Awareness**

**9.3.2.1** The National Leadership Council may maintain handoff awareness concerning matters that may later require National Consortium Company involvement.

**9.3.2.2** Handoff awareness may include understanding national priorities, readiness gaps, public authority dependencies, finance-readiness questions, insurance-readiness questions, safeguard conditions, technical evidence, National Model references, Nexus Universe outputs, AEP Passport candidate status, Nexus Rail routing, Docket issues, and enterprise interface needs.

**9.3.2.3** Handoff awareness does not authorize handoff. It allows leadership to identify whether a matter appears to require later enterprise-stack consideration.

**9.3.2.4** Handoff awareness shall be recorded with limits, conditions, unresolved gaps, and routing requirements.

**9.3.2.5** The governing rule shall be:

**The Council may know when enterprise handoff may be needed; it cannot make handoff lawful by awareness alone.**

***

### **9.3.3 No Control of National Consortium Company by Leadership Council**

**9.3.3.1** The National Leadership Council shall not control any National Consortium Company unless a separate lawful instrument expressly creates a defined relationship, and even then only within the scope of that instrument.

**9.3.3.2** The Council shall not appoint directors, manage officers, approve budgets, sign contracts, control procurement, select providers, direct operations, allocate revenues, approve investments, approve insurance, authorize SPVs, or bind the National Consortium Company by default.

**9.3.3.3** A person participating in the National Leadership Council may separately serve in a National Consortium Company only where roles are separated, conflicts are disclosed, claims are bounded, and the applicable governance records permit.

**9.3.3.4** Leadership Council participation shall not create ownership rights, voting rights, board rights, profit rights, employment rights, contract rights, project rights, or commercial entitlements in the National Consortium Company.

**9.3.3.5** The governing rule shall be:

**Public-good leadership may not become hidden enterprise control.**

***

### **9.3.4 Handoff Candidate Identification**

**9.3.4.1** The National Leadership Council may identify potential handoff candidates for National Consortium Company consideration where public-good records suggest possible downstream enterprise relevance.

**9.3.4.2** Handoff candidates may arise from National Model priorities, National Working Group outputs, Nexus Universe outputs, Nexus Core work, Nexus Observatory candidates, Nexus Rail pathways, AEP Passport candidates, public authority learning records, finance-readiness notes, safeguard records, Docket items, or regional/global routing.

**9.3.4.3** A handoff candidate record should identify:

a) source record;\
b) public-good rationale;\
c) national priority;\
d) evidence status;\
e) technical readiness;\
f) public authority dependencies;\
g) finance-readiness status;\
h) insurance-readiness questions;\
i) safeguard conditions;\
j) data restrictions;\
k) provider-neutral capability needs;\
l) unresolved gaps;\
m) receiving body proposed;\
n) claims limits;\
o) correction pathway.

**9.3.4.4** Identification of a handoff candidate shall not mean the matter is approved, viable, financeable, insurable, procured, certified, consented, or ready for implementation.

**9.3.4.5** The governing rule shall be:

**Handoff candidate identification starts routing discipline; it does not complete handoff.**

***

### **9.3.5 Handoff Limits**

**9.3.5.1** Any National Consortium Company handoff supported by National Leadership Council input shall remain limited by the source records, public authority status, finance-readiness boundaries, safeguard conditions, data restrictions, technical limitations, procurement rules, consent requirements, and correction pathways.

**9.3.5.2** Handoff shall not erase unresolved gaps. The handoff record shall carry them forward.

**9.3.5.3** Handoff shall not transform public-good participation into commercial endorsement or enterprise rights.

**9.3.5.4** Handoff limits shall be expressly stated in any handoff-related record, including prohibited claims.

**9.3.5.5** The governing rule shall be:

**Handoff carries conditions; it does not remove them.**

***

### **9.3.6 Conflict Review**

**9.3.6.1** The National Leadership Council shall support conflict review where a National Consortium Company interface or handoff candidate implicates participants, sponsors, providers, investors, insurers, donors, public authorities, National Working Group leads, Helix Council members, or leadership-pool candidates.

**9.3.6.2** Conflict review shall identify whether any participant may benefit from, influence, or appear to influence handoff routing, enterprise interface, provider selection, procurement positioning, SPV formation, finance-readiness interpretation, public-safe reporting, or National Model framing.

**9.3.6.3** Conflict mitigation may include disclosure, recusal, independent review, role reclassification, claims restriction, access limitation, or referral to the competent body.

**9.3.6.4** Unresolved conflicts may require suspension or re-routing of handoff consideration.

**9.3.6.5** The governing rule shall be:

**Enterprise handoff must not be shaped by hidden enterprise interests.**

***

### **9.3.7 Claims Review**

**9.3.7.1** The National Leadership Council shall support claims review for any National Consortium Company interface or handoff-related communication.

**9.3.7.2** Claims review shall prevent unsupported statements implying:

a) National Consortium Company approval;\
b) project approval;\
c) provider selection;\
d) procurement status;\
e) investment readiness;\
f) insurance approval;\
g) public finance support;\
h) public authority approval;\
i) certification;\
j) community consent;\
k) Indigenous consent;\
l) Nexus Universe endorsement;\
m) AEP Passport status;\
n) Nexus Rail execution;\
o) GRF, GCRI, or GRA approval.

**9.3.7.3** Handoff-related claims shall state whether a matter is candidate, under review, routed, accepted for further review, deferred, restricted, rejected, corrected, or withdrawn.

**9.3.7.4** Claims review shall occur before public, investor-facing, public authority-facing, provider-facing, or sponsor-facing communication.

**9.3.7.5** The governing rule shall be:

**Enterprise-interface claims must be tighter than ordinary participation claims because reliance risk is higher.**

***

### **9.3.8 Enterprise-Stack Boundary**

**9.3.8.1** The National Leadership Council shall preserve the boundary between the public-good stack and the enterprise stack.

**9.3.8.2** The public-good stack prepares evidence, records, readiness, public authority learning, finance-readiness, safeguards, public-safe reporting, AEP Passport candidates, Nexus Rail pathways, Docket items, National Model inputs, and handoff conditions.

**9.3.8.3** The enterprise stack may lawfully execute through National Consortium Companies, Project SPVs, providers, operators, contractors, investors, insurers, donors, public finance actors, public authorities, licensed professionals, and other competent actors acting under separate authority.

**9.3.8.4** The National Leadership Council shall not collapse these stacks. Its work may inform enterprise readiness but shall not become enterprise activity.

**9.3.8.5** The governing rule shall be:

**Public-good preparation and enterprise execution must remain connected but not merged.**

***

### **9.3.9 Correction of Company Overclaim**

**9.3.9.1** The National Leadership Council shall support correction where any National Consortium Company-related claim overstates the relationship between the Company and the Council, National Council, National Nexus Consortium, GRF, GCRI, GRA, Nexus Universe, public authorities, sponsors, providers, capital readers, communities, or Project SPVs.

**9.3.9.2** Company overclaim may include unsupported statements implying that:

a) the Company is the public-good National Council;\
b) the Company is the National Leadership Council;\
c) the Company holds public authority;\
d) the Company is endorsed by public authorities;\
e) the Company is finance-approved;\
f) the Company is certified by Nexus;\
g) Company projects are procured or approved;\
h) Company activity is community-consented;\
i) Company activity is Indigenous-approved where applicable;\
j) the Company is controlled by GRF, GCRI, or GRA;\
k) the Company has automatic access to AEP Passport, Rail, or Nexus Universe status.

**9.3.9.3** Correction may include public clarification, revised materials, claim withdrawal, role reclassification, access restriction, handoff suspension, or referral to the competent legal or governance process.

**9.3.9.4** The governing rule shall be:

**Company overclaim must be corrected because enterprise reliance can create legal, public, and market risk.**

***

### **9.3.10 Re-Routing or Suspension of Handoff**

**9.3.10.1** The National Leadership Council may recommend re-routing or suspension of a National Consortium Company handoff candidate where the record indicates unresolved risks.

**9.3.10.2** Re-routing or suspension may be appropriate where:

a) public authority status is unclear;\
b) finance-readiness is overstated;\
c) provider neutrality is compromised;\
d) sponsor control risk exists;\
e) safeguards are incomplete;\
f) community or Indigenous consent boundaries are unresolved;\
g) technical evidence is insufficient;\
h) data or cyber risks are unresolved;\
i) conflicts are unmanaged;\
j) claims are inaccurate;\
k) National Model status is defective;\
l) Docket issues remain open.

**9.3.10.3** Re-routing may direct the matter to National Council, Stewardship Board, Helix Council, National Investors Council, National Working Group, safeguard process, public authority learning process, Nexus Observatory, Nexus Rails, AEP Passport pathway, Docket, GRF, GCRI, GRA, Regional Nexus Consortium, or another competent pathway.

**9.3.10.4** Suspension shall be recorded and shall identify the conditions for reconsideration.

**9.3.10.5** The governing rule shall be:

**Unsafe handoff should be paused before it becomes unsafe execution.**

***

## **9.4 Project SPV Interface**

### **9.4.1 Project SPV as Separate Lawful Project Vehicle**

**9.4.1.1** A **Project SPV** shall be understood as a separate lawful project vehicle established for a defined project, asset, program, infrastructure, service, finance, insurance, procurement, delivery, operating, or implementation purpose under applicable law and governing instruments.

**9.4.1.2** A Project SPV may hold project contracts, permits, assets, liabilities, revenues, financing, insurance, warranties, delivery obligations, operator relationships, provider contracts, public authority agreements, sponsor arrangements, and other lawful project-specific matters where properly formed.

**9.4.1.3** The Project SPV is not the National Leadership Council. It is not the National Council. It is not the National Nexus Consortium public-good body. It is not the National Model. It is not the National Consortium Company unless the lawful structure expressly provides a specific relationship. It is not GRF, GCRI, or GRA. It is not a public authority by default.

**9.4.1.4** The National Leadership Council shall not create, own, govern, manage, finance, insure, procure for, contract for, operate, or control a Project SPV by implication.

**9.4.1.5** The governing rule shall be:

**A Project SPV is a lawful execution vehicle; the National Leadership Council is a public-good leadership and readiness gateway.**

***

### **9.4.2 Leadership Council Role in SPV-Readiness Awareness**

**9.4.2.1** The National Leadership Council may support SPV-readiness awareness where national priorities, National Model records, National Working Group outputs, Nexus Universe outputs, AEP Passport candidates, Nexus Rail pathways, finance-readiness notes, public authority learning records, safeguard records, or handoff candidates suggest that a project-specific vehicle may later be relevant.

**9.4.2.2** SPV-readiness awareness may include identifying what questions must be answered before a Project SPV could responsibly be considered.

**9.4.2.3** Such questions may relate to public authority approval, procurement, permitting, finance, insurance, technical readiness, land or asset rights, data rights, community or Indigenous consent where applicable, operator capacity, provider neutrality, sponsor influence, environmental and social safeguards, cybersecurity, and lifecycle responsibilities.

**9.4.2.4** SPV-readiness awareness shall not be described as SPV approval, SPV formation, investment readiness, procurement readiness, public authority approval, project approval, or execution authorization.

**9.4.2.5** The governing rule shall be:

**The Council may help identify whether SPV questions exist; it does not answer them with execution authority.**

***

### **9.4.3 No SPV Approval by Leadership Council**

**9.4.3.1** The National Leadership Council shall have no authority to approve any Project SPV unless a separate lawful instrument expressly creates a specific approval role, and such role is compatible with the Council’s public-good character.

**9.4.3.2** The Council shall not approve SPV formation, SPV governance, SPV financing, SPV insurance, SPV procurement, SPV provider selection, SPV public authority agreements, SPV community or Indigenous consent, SPV commercial terms, SPV asset ownership, SPV operating model, or SPV project execution.

**9.4.3.3** The Council may recommend that SPV-readiness be studied, routed, paused, corrected, or referred to competent actors.

**9.4.3.4** Any public or private claim that the National Leadership Council approved an SPV shall be corrected unless supported by a separate lawful record.

**9.4.3.5** The governing rule shall be:

**SPV approval belongs to lawful project governance, not to the National Leadership Council.**

***

### **9.4.4 SPV-Readiness Questions**

**9.4.4.1** The National Leadership Council may identify SPV-readiness questions that should be addressed before any lawful Project SPV pathway is pursued.

**9.4.4.2** SPV-readiness questions may include:

a) What national priority does the proposed project address?\
b) What public-good record supports the project’s consideration?\
c) What evidence exists and what evidence is missing?\
d) What public authority approvals, permits, delegations, or decisions may be required?\
e) What procurement process may apply?\
f) What finance-readiness gaps exist?\
g) What insurance-readiness questions exist?\
h) What safeguards apply?\
i) What community, Indigenous, rights-holder, land, data, or protected-knowledge issues arise?\
j) What technical risks remain?\
k) What provider-neutral capability requirements apply?\
l) What sponsor or provider conflicts exist?\
m) What operating and lifecycle responsibilities would arise?\
n) What Docket issues remain open?\
o) What conditions must travel with any handoff?

**9.4.4.3** SPV-readiness questions shall be recorded and routed to competent actors.

**9.4.4.4** Identification of SPV-readiness questions shall not imply that an SPV should be formed.

**9.4.4.5** The governing rule shall be:

**SPV-readiness begins with questions, not assumptions.**

***

### **9.4.5 Public Authority Dependencies**

**9.4.5.1** The National Leadership Council may identify public authority dependencies relevant to SPV-readiness.

**9.4.5.2** Public authority dependencies may include permits, licences, approvals, procurement authority, public finance authority, environmental approval, land authority, public utility authority, public health authority, emergency-management authority, data-sharing authority, infrastructure authority, regulatory approval, or other lawful public decisions.

**9.4.5.3** The Council shall not resolve public authority dependencies. It may identify them, classify them, and route them to the appropriate public authority learning or lawful decision pathway.

**9.4.5.4** Public authority dependency identification shall not be represented as public authority approval, regulatory comfort, procurement readiness, public finance support, or official adoption.

**9.4.5.5** The governing rule shall be:

**Public authority dependencies must be named before execution, but only public authorities can decide public authority matters.**

***

### **9.4.6 Finance and Insurance Dependencies**

**9.4.6.1** The National Leadership Council may identify finance and insurance dependencies relevant to SPV-readiness in coordination with the National Investors Council and GRA-aligned discipline where applicable.

**9.4.6.2** Finance and insurance dependencies may include capital-readability, diligence gaps, revenue model questions, risk allocation, insurance coverage, underwriting questions, guarantees, public finance relevance, donor relevance, philanthropic relevance, concessionary finance relevance, sovereign support questions, blended finance issues, and lifecycle funding questions.

**9.4.6.3** The Council shall not resolve finance or insurance dependencies. It may identify questions and route them to competent finance-readiness, capital-reader, insurance-readiness, National Investors Council, GRA-aligned, or lawful external finance processes.

**9.4.6.4** Finance and insurance dependency identification shall not imply financeability, bankability, insurability, investment approval, underwriting, guarantee, public finance approval, donor approval, philanthropic commitment, or transaction readiness.

**9.4.6.5** The governing rule shall be:

**Finance and insurance dependencies may be mapped by readiness discipline; they are resolved only through lawful finance and insurance processes.**

***

### **9.4.7 Safeguard Dependencies**

**9.4.7.1** The National Leadership Council may identify safeguard dependencies relevant to SPV-readiness.

**9.4.7.2** Safeguard dependencies may include privacy, cybersecurity, sovereign data, community protection, Indigenous consent or data sovereignty where applicable, rights-holder issues, protected knowledge, environmental and social safeguards, accessibility, health data, biodiversity-sensitive information, critical infrastructure exposure, land and livelihood impacts, public-safe reporting limits, and non-extractive participation requirements.

**9.4.7.3** The Council shall not resolve safeguard dependencies by itself. It may identify, classify, and route them to the appropriate safeguard, consent, consultation, public authority, community, Indigenous, legal, technical, or public-safe process.

**9.4.7.4** Safeguard dependency identification shall not imply safeguard clearance, community consent, Indigenous consent, environmental approval, data authorization, protected-knowledge permission, or social license.

**9.4.7.5** The governing rule shall be:

**Safeguard dependencies are not obstacles to be bypassed; they are conditions for lawful readiness.**

***

### **9.4.8 Provider Neutrality**

**9.4.8.1** The National Leadership Council shall preserve provider neutrality in any SPV-readiness discussion.

**9.4.8.2** Provider neutrality means that the Council may identify capability requirements, interoperability needs, performance questions, technical evidence needs, data requirements, cyber requirements, operating requirements, and implementation constraints without selecting, endorsing, ranking, validating, or preferring any provider by default.

**9.4.8.3** Provider-linked participants shall disclose conflicts and may be recused from SPV-readiness discussions where their participation could create actual or perceived provider advantage.

**9.4.8.4** Provider participation in Nexus Universe, National Working Groups, Nexus Core, National Model preparation, AEP Passport candidacy, or Rail routing shall not create SPV provider status.

**9.4.8.5** The governing rule shall be:

**SPV-readiness may identify what capability is needed; procurement processes decide who provides it.**

***

### **9.4.9 Handoff Record Requirements**

**9.4.9.1** Any SPV-related handoff candidate supported by National Leadership Council input shall require a handoff record before being communicated as routed or under consideration by a downstream actor.

**9.4.9.2** The handoff record should identify:

a) source of the matter;\
b) national priority;\
c) public-good record basis;\
d) evidence status;\
e) technical status;\
f) public authority dependencies;\
g) procurement dependencies;\
h) finance-readiness and insurance-readiness dependencies;\
i) safeguard dependencies;\
j) data, cyber, privacy, and protected-knowledge conditions;\
k) provider-neutral requirements;\
l) sponsor or provider conflicts;\
m) National Model reference;\
n) Nexus Universe reference where applicable;\
o) AEP Passport candidate status where applicable;\
p) Nexus Rail pathway where applicable;\
q) Docket items;\
r) prohibited claims;\
s) receiving body;\
t) correction pathway.

**9.4.9.3** The handoff record shall state what the handoff does and does not mean.

**9.4.9.4** Handoff record existence shall not itself constitute SPV approval, project approval, finance approval, procurement approval, insurance approval, public authority authorization, consent, certification, or execution authority.

**9.4.9.5** The governing rule shall be:

**SPV-related handoff must be recorded with conditions before it is relied upon.**

***

### **9.4.10 Correction of SPV Overclaim**

**9.4.10.1** The National Leadership Council shall support correction where any Project SPV-related claim overstates the meaning of Council participation, National Model inclusion, Nexus Universe visibility, National Working Group output, public authority learning, finance-readiness, AEP Passport candidacy, Nexus Rail routing, National Consortium Company interface, or handoff record.

**9.4.10.2** SPV overclaim may include unsupported statements implying:

a) SPV approval by the National Leadership Council;\
b) SPV approval by the National Council;\
c) public authority approval;\
d) finance approval;\
e) insurance approval;\
f) procurement status;\
g) provider selection;\
h) certification;\
i) Nexus-ready status;\
j) AEP Passport status;\
k) community consent;\
l) Indigenous consent where applicable;\
m) public finance approval;\
n) donor or philanthropic commitment;\
o) execution authorization;\
p) GRF, GCRI, or GRA approval.

**9.4.10.3** Correction may include immediate claim withdrawal, revised language, participant notice, public-safe clarification, investor-facing correction, public authority-facing correction, provider-facing correction, sponsor-facing correction, reclassification, handoff suspension, Docket entry, or referral to the competent legal or governance process.

**9.4.10.4** Repeated SPV overclaim may justify suspension or restriction of leadership eligibility, working-group access, Nexus Universe participation, handoff support, or National Model reference.

**9.4.10.5** The governing rule shall be:

**SPV overclaim must be corrected before public-good readiness becomes false execution authority.**

***

### Related links

* [VIII. MOBILIZATION AND PARTICIPATION](broken://spaces/EQtittnb4JJQ2YOtd2tk/pages/pDY3vZ3ovX8fQYx3qV52)
* [VII. PIPELINE, PROJECTS, AND DISCLOSURE](broken://spaces/EQtittnb4JJQ2YOtd2tk/pages/FzaxWQJ4xQVRDeBqkzLw)
* [X. ACCOUNTABILITY, RECORDS, AND CONDUCT](broken://spaces/EQtittnb4JJQ2YOtd2tk/pages/RddGgW2Z5H5z0AqrsY0f)

### Next steps

Continue to:

1. Define accountability, correction, and record discipline in [X. ACCOUNTABILITY, RECORDS, AND CONDUCT](broken://spaces/EQtittnb4JJQ2YOtd2tk/pages/RddGgW2Z5H5z0AqrsY0f).
2. Review participation and representation rules in [VIII. MOBILIZATION AND PARTICIPATION](broken://spaces/EQtittnb4JJQ2YOtd2tk/pages/pDY3vZ3ovX8fQYx3qV52).
3. Connect handoff discipline to project routing in [VII. PIPELINE, PROJECTS, AND DISCLOSURE](broken://spaces/EQtittnb4JJQ2YOtd2tk/pages/FzaxWQJ4xQVRDeBqkzLw).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.therisk.global/organization/cooperation/consortiums/gateways/national-councils/leadership/ix.-handoff.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.