# VI. PROCEDURE

The **National Investors Council** uses formal governance procedures to keep finance-readiness work disciplined, traceable, and bounded. This section explains how terms of reference, convening, room design, records, escalation, and correction operate across the [National Councils](/organization/cooperation/consortiums/gateways/national-councils.md), the [National Nexus Consortium](/organization/organization/architecture/ii.-definitions/xix.-national-nexus-consortium-nnc.md), and the national finance-readiness pathway.

These procedures protect [Nexus Rails](/organization/organization/architecture/ii.-definitions/xv.-nexus-rails.md), [Nexus Universe](/organization/cooperation/nexus-universe.md), and finance-facing records from drifting into solicitation, approval, brokerage, or execution.

## 6.1 Terms of Reference

### 6.1.1 Adoption of Terms of Reference

**6.1.1.1** The National Investors Council shall operate under written Terms of Reference adopted by the competent National Council, National Nexus Consortium authority, National Stewardship Board where formed, or other duly recorded governance authority.

**6.1.1.2** The Terms of Reference shall give practical operating effect to this Charter and shall specify the Council’s mandate, scope, membership or participation classes, eligibility requirements, convening rules, chairing structure, records discipline, confidentiality rules, no-reliance terms, non-advisory status, non-solicitation obligations, non-transaction controls, competition-compliance requirements, regulated-perimeter controls, safeguard rules, claims limits, escalation routes, correction procedures, annual review process, and archive requirements.

**6.1.1.3** No Terms of Reference shall enlarge the National Investors Council into an investment committee, fund, broker, dealer, lender, insurer, reinsurer, underwriter, guarantee facility, public finance authority, donor approval body, philanthropic grant-maker, securities platform, transaction arranger, procurement body, certification body, public authority, National Consortium Company, Project SPV, or execution vehicle unless a separate lawful instrument creates a distinct body outside this Council and clearly separates that body from the National Investors Council.

**6.1.1.4** The Terms of Reference shall be valid only to the extent consistent with this Charter, the National Council rules, the National Nexus Consortium instruments, applicable public-good stack controls, applicable national law, and the hard boundary that finance-readiness is not finance.

**6.1.1.5** The governing rule shall be:

**The Terms of Reference may operationalize the Council; they shall not transform the Council into a finance-execution body.**

***

### 6.1.2 Scope of Terms of Reference

**6.1.2.1** The Terms of Reference shall define the scope of Council activity with precision.

**6.1.2.2** Scope may include national finance-readiness review, capital-readability question formation, insurance-readiness question formation, reinsurance-readiness question formation, disaster-risk-finance question formation, public finance relevance mapping, donor and philanthropic relevance mapping, development-readiness mapping, diligence-gap mapping, risk-to-capital translation, Project SPV-readiness review, National Consortium Company finance-interface review, Nexus Rail finance-readiness pathway support, AEP Passport finance-readiness layer support, Nexus Universe capital-reader room support, and finance-readiness overclaim correction.

**6.1.2.3** Scope shall also identify what the Council shall not do, including investment approval, capital raising, securities offering, lending, underwriting, insurance placement, reinsurance placement, guarantee approval, donor allocation, public finance allocation, procurement, certification, provider selection, project approval, public authority action, community or Indigenous consent, SPV authorization, or execution.

**6.1.2.4** The Terms of Reference shall distinguish ordinary meetings, controlled meetings, no-reliance rooms, capital-reader rooms, insurance-readiness rooms, public finance relevance rooms, donor and philanthropic relevance rooms, Nexus Universe preparation sessions, Helix Council joint sessions, National Leadership Council joint sessions, and escalation sessions.

**6.1.2.5** The governing rule shall be:

**The Council’s scope shall be broad enough to make readiness legible and narrow enough to prevent reliance, solicitation, transaction, and execution.**

***

### 6.1.3 Authority Limits

**6.1.3.1** The Terms of Reference shall state the authority limits of the National Investors Council in express terms.

**6.1.3.2** The Council’s authority shall be limited to deliberating, reviewing, classifying, identifying questions, mapping relevance, recording gaps, preparing no-reliance notes, supporting capital-readability, supporting insurance-readiness, supporting donor and public finance relevance, supporting SPV-readiness awareness, supporting Nexus Rail finance-readiness pathways, supporting AEP Passport finance-readiness layers, supporting Nexus Universe capital-reader rooms, escalating issues, and correcting overclaims.

**6.1.3.3** The Council shall not have authority to approve investments, approve insurance, approve reinsurance, approve guarantees, approve public finance, approve donor or philanthropic support, approve procurement, approve providers, approve projects, approve SPVs, approve National Consortium Company action, approve public authority action, issue certification, issue ratings, issue standards-conformance conclusions, issue public warnings, issue public authority statements, or authorize execution.

**6.1.3.4** Authority limits shall apply to the Council, chairs, co-chairs, vice-chairs, rapporteurs, leads, participants, observers, guests, sponsors, providers, capital readers, public finance readers, donors, insurers, and any person communicating about the Council.

**6.1.3.5** The governing rule shall be:

**Every Council authority is a readiness authority unless a separate lawful record says otherwise.**

***

### 6.1.4 Reporting Lines

**6.1.4.1** The Terms of Reference shall define reporting lines from the National Investors Council to the National Council, National Nexus Consortium authority, National Secretariat or National Desk, National Stewardship Board where formed, and other competent receiving bodies.

**6.1.4.2** Reporting may include finance-readiness notes, capital-readability records, insurance-readiness records, donor relevance records, public finance relevance records, diligence-gap records, SPV-readiness records, Nexus Rail records, AEP Passport finance-layer records, Nexus Universe capital-room records, Docket items, correction records, and annual renewal notes.

**6.1.4.3** Reporting shall not convert Council outputs into final decisions. A report may be received, accepted, deferred, restricted, corrected, escalated, archived, or rejected by the competent receiving body.

**6.1.4.4** Reporting lines shall preserve confidentiality, publication class, no-reliance status, public authority capacity classification, finance-sensitive restrictions, safeguard restrictions, conflict conditions, and claims limits.

**6.1.4.5** The governing rule shall be:

**Reporting transmits readiness records; it does not transmit finance authority.**

***

### 6.1.5 Relationship to National Council Rules

**6.1.5.1** The National Investors Council shall operate within the National Council rules.

**6.1.5.2** National Council rules shall govern the Council’s position as a sub-gateway, its relationship to national ownership, its participation discipline, its public-good records, its escalation pathways, its cross-helix interfaces, its public authority boundaries, its Nexus Universe preparation role, its National Model role, its safeguard obligations, its claims discipline, and its correction process.

**6.1.5.3** Where National Investors Council Terms of Reference conflict with National Council rules, National Council rules shall prevail unless a competent instrument lawfully provides otherwise.

**6.1.5.4** The National Investors Council shall not use finance-readiness urgency, capital-reader interest, donor interest, public finance relevance, insurer inquiry, sponsor support, provider readiness, Nexus Universe timing, or SPV-readiness pressure to bypass National Council rules.

**6.1.5.5** The governing rule shall be:

**The Investors Council is inside the National Council architecture and cannot finance its way around national ownership.**

***

### 6.1.6 Relationship to National Leadership Council Rules

**6.1.6.1** The National Investors Council shall coordinate with the National Leadership Council according to recorded rules for joint agenda, shared inputs, leadership priorities, cross-helix alignment, Nexus Universe mobilization, National Working Group formation, National Model preparation, public-safe reporting, Docket matters, AEP Passport candidates, Nexus Rail candidates, and handoff awareness.

**6.1.6.2** National Leadership Council rules shall apply where leadership-pool matters, national agenda discipline, stewardship-pipeline matters, leadership eligibility, national delegation formation, cross-helix coordination, or public-good leadership records intersect with finance-readiness.

**6.1.6.3** The National Investors Council shall not influence leadership-pool status, board-candidate status, national leadership selection, National Council governance, or stewardship authority through capital-reader preference, donor preference, insurer preference, public finance relevance, or sponsor pressure.

**6.1.6.4** Joint rules shall preserve the distinction between leadership readiness and finance-readiness.

**6.1.6.5** The governing rule shall be:

**Leadership rules govern leadership; Investor Council rules govern capital-readiness questions; neither shall capture the other.**

***

### 6.1.7 Relationship to Capital / Insurance / Donor / Development Helix Council Rules

**6.1.7.1** The National Investors Council shall coordinate with the Capital / Insurance / Donor / Development Helix Council according to recorded rules for participation, referral, input classification, room design, conflict disclosure, no-reliance terms, claims limits, confidentiality, competition compliance, regulated-perimeter control, and correction.

**6.1.7.2** The Helix Council may provide broad participation and sector intelligence. The National Investors Council shall provide structured finance-readiness processing, capital-readability discipline, insurance-readiness question formation, donor relevance mapping, public finance relevance mapping, diligence-gap mapping, SPV-readiness review, and handoff-condition formulation.

**6.1.7.3** The Helix Council shall not become an investment committee by referral to the National Investors Council. The National Investors Council shall not become a capital allocation body by receiving Helix inputs.

**6.1.7.4** Helix inputs shall be source-labelled, role-classified, conflict-reviewed, claims-limited, no-reliance, and correctionable.

**6.1.7.5** The governing rule shall be:

**The Helix supplies finance-relevant participation; the Investors Council disciplines that participation into readiness records.**

***

### 6.1.8 Relationship to Stewardship Board Rules Where Formed

**6.1.8.1** Where a National Nexus Consortium Stewardship Board is formed, the National Investors Council shall operate under the Stewardship Board’s rules where applicable.

**6.1.8.2** Stewardship Board rules may govern approval of Terms of Reference, annual workplan, chair appointments, controlled-room permissions, public-safe release, escalation of Docket issues, conflict management, safeguard controls, correction measures, archive, and renewal.

**6.1.8.3** Stewardship Board oversight shall not convert the National Investors Council into an investment committee, finance authority, public finance authority, donor approval body, insurer, broker, lender, underwriter, procurement body, certification body, National Consortium Company, Project SPV, or execution vehicle.

**6.1.8.4** The Council shall provide readiness inputs to the Board where authorized, and the Board may accept, reject, defer, restrict, correct, route, or archive them.

**6.1.8.5** The governing rule shall be:

**Board oversight may govern the Council’s public-good function; it shall not create finance-execution authority.**

***

### 6.1.9 Annual Review

**6.1.9.1** The Terms of Reference shall be reviewed at least annually and may be reviewed more frequently where material changes occur.

**6.1.9.2** Annual review shall consider whether the Council’s mandate, composition, participation categories, room types, no-reliance terms, non-solicitation rules, non-transaction rules, competition-compliance controls, regulated-perimeter controls, confidentiality rules, claims rules, public authority boundaries, safeguard rules, Nexus Universe role, AEP Passport interface, Nexus Rail interface, Docket interface, handoff interface, and correction processes remain adequate.

**6.1.9.3** Annual review shall be informed by the prior cycle’s finance-readiness outputs, capital-reader room records, insurance-readiness records, donor relevance records, public finance relevance records, Docket issues, overclaim corrections, confidentiality issues, safeguard issues, public authority issues, market-conduct issues, and renewal needs.

**6.1.9.4** The Terms of Reference shall not renew automatically where serious finance-boundary, claims, safeguard, competition, confidentiality, or regulated-perimeter issues remain unresolved.

**6.1.9.5** The governing rule shall be:

**Terms governing finance-facing readiness must renew because finance-facing risk changes with each cycle.**

***

### 6.1.10 Correction of Terms

**6.1.10.1** The Terms of Reference shall be corrected where they are inaccurate, outdated, incomplete, unsafe, overbroad, inconsistent with this Charter, inconsistent with National Council rules, inconsistent with Stewardship Board rules where applicable, inconsistent with public-good stack controls, inconsistent with no-reliance discipline, or insufficient to manage finance-facing risk.

**6.1.10.2** Correction may include amendment, clarification, restriction, suspension of a room type, modification of participation criteria, revision of claims language, revision of no-reliance language, addition of regulated-perimeter controls, addition of competition-compliance controls, strengthening of confidentiality, strengthening of safeguard requirements, or revision of escalation pathways.

**6.1.10.3** Where flawed Terms of Reference have caused external reliance or overclaim, public or controlled clarification shall be considered.

**6.1.10.4** Corrected terms shall be recorded, dated, versioned, and distributed to affected participants.

**6.1.10.5** The governing rule shall be:

**If the operating terms permit finance drift, the terms themselves must be corrected.**

***

## 6.2 Convening

### 6.2.1 Convening Authority

**6.2.1.1** The National Investors Council may be convened by the competent National Council authority, National Nexus Consortium authority, National Secretariat or National Desk, National Stewardship Board where formed, or other recorded authority identified in the Terms of Reference.

**6.2.1.2** Convening authority shall specify the purpose, scope, agenda, participants, classification, no-reliance terms, confidentiality requirements, claims limits, conflict disclosure requirements, public authority capacity status, regulated-perimeter controls, competition-compliance controls, safeguard conditions, and records requirements for each meeting or room.

**6.2.1.3** No participant, sponsor, provider, investor, insurer, donor, public finance actor, public authority, National Consortium Company, Project SPV pathway actor, regional actor, or global actor shall convene a National Investors Council meeting or room by implication unless the convening authority is recorded.

**6.2.1.4** Informal capital-reader gatherings shall not be described as National Investors Council meetings unless convened through the competent record.

**6.2.1.5** The governing rule shall be:

**No convening record, no National Investors Council meeting.**

***

### 6.2.2 Chair and Co-Chair Structure

**6.2.2.1** The National Investors Council may have a Chair, Co-Chairs, Vice-Chair, or other leadership roles as authorized by the Terms of Reference.

**6.2.2.2** The chairing structure shall be designed to preserve national ownership, finance-boundary discipline, no-reliance status, competition compliance, public authority neutrality, safeguard protection, anti-capture balance, and correctionability.

**6.2.2.3** A Chair or Co-Chair shall not possess investment approval authority, finance authority, insurance authority, donor approval authority, public finance authority, procurement authority, certification authority, public authority status, Company authority, SPV authority, or execution authority by virtue of the role.

**6.2.2.4** Chair and Co-Chair roles shall be role-classified, conflict-reviewed, term-defined, claims-limited, and renewable or removable according to the Terms of Reference.

**6.2.2.5** The governing rule shall be:

**Chairing the Council means stewarding boundaries, not commanding capital.**

***

### 6.2.3 Secretariat Support

**6.2.3.1** The National Investors Council may receive Secretariat or National Desk support.

**6.2.3.2** Secretariat support may include agenda preparation, notices, participant classification, attendance records, conflict records, no-reliance acknowledgment records, confidentiality undertakings, records management, public-safe review routing, Docket capture, Nexus Universe preparation registers, AEP Passport finance-layer records, Nexus Rail records, correction tracking, archive, and annual renewal support.

**6.2.3.3** Secretariat support shall not create substantive finance authority. Administrative coordination shall not imply approval, endorsement, finance, insurance, donor commitment, public finance allocation, procurement, certification, SPV authorization, or execution.

**6.2.3.4** The Secretariat shall protect controlled materials, sensitive participant lists, capital-reader records, public authority-sensitive information, finance-sensitive information, donor-sensitive information, insurance-sensitive information, safeguard-sensitive information, and confidential room notes.

**6.2.3.5** The governing rule shall be:

**Secretariat support makes the Council governable by record, not authoritative by administration.**

***

### 6.2.4 Meeting Cadence

**6.2.4.1** The National Investors Council shall meet according to the cadence established in its Terms of Reference.

**6.2.4.2** Cadence may include regular meetings, annual-cycle meetings, quarterly readiness reviews, Nexus Universe preparation meetings, pre-live capital-reader room preparation, post-cycle debriefs, Docket review meetings, AEP Passport finance-layer review meetings, Nexus Rail finance-route meetings, and special meetings for urgent correction or safeguard matters.

**6.2.4.3** Meeting cadence shall be designed around public-good readiness and annual Nexus cycle needs, not around transaction pressure, investor urgency, donor cycles alone, sponsor deadlines, provider readiness, media timing, or external market pressure.

**6.2.4.4** A scheduled meeting shall be cancelled, deferred, restricted, or reclassified if the records, participants, confidentiality terms, public authority status, no-reliance terms, safeguards, or regulated-perimeter controls are not ready.

**6.2.4.5** The governing rule shall be:

**Meeting cadence serves readiness discipline; readiness discipline shall not be sacrificed to calendar pressure.**

***

### 6.2.5 Special Meetings

**6.2.5.1** Special meetings may be convened where a specific finance-readiness issue, insurance-readiness issue, donor relevance issue, public finance relevance issue, diligence gap, SPV-readiness matter, public authority dependency, safeguard matter, Docket issue, Nexus Universe preparation need, AEP Passport finance-layer issue, Nexus Rail finance-route issue, handoff issue, or overclaim correction requires focused attention.

**6.2.5.2** Special meetings shall state their purpose, authority, classification, participants, agenda, no-reliance terms, confidentiality requirements, competition-compliance limits, regulated-perimeter controls, safeguard requirements, and expected records.

**6.2.5.3** Special meetings shall not be used to bypass ordinary governance, create urgency-based overclaim, conduct transactions, solicit capital, secure donor commitments, obtain public finance commitments, arrange insurance, approve SPVs, approve projects, or advance provider selection.

**6.2.5.4** Outputs from special meetings shall be recorded and routed according to their status and limits.

**6.2.5.5** The governing rule shall be:

**A special meeting may accelerate review, but it shall not accelerate authority beyond the record.**

***

### 6.2.6 Controlled Meetings

**6.2.6.1** Controlled meetings shall be used where topics require restricted handling due to finance sensitivity, public authority sensitivity, insurance sensitivity, donor sensitivity, commercial sensitivity, provider sensitivity, sponsor sensitivity, community sensitivity, Indigenous or protected-knowledge sensitivity where applicable, cyber sensitivity, data sensitivity, infrastructure sensitivity, health sensitivity, biodiversity sensitivity, or public-safe reporting limits.

**6.2.6.2** Controlled meetings shall have defined participant lists, access controls, confidentiality undertakings, document controls, publication restrictions, note-taking rules, recording restrictions, AI-processing restrictions, external sharing limits, and correction pathways.

**6.2.6.3** Controlled meeting status shall not imply greater authority. A controlled room protects sensitive discussion; it does not approve finance, insurance, public finance, donor support, procurement, certification, SPV formation, or execution.

**6.2.6.4** Controlled meeting outputs shall be classified and may be summarized only in approved public-safe or controlled form.

**6.2.6.5** The governing rule shall be:

**Controlled meetings protect sensitive readiness work; they do not convert confidentiality into approval.**

***

### 6.2.7 No-Reliance Rooms

**6.2.7.1** No-reliance rooms may be convened where finance-facing, capital-reader, insurance-readiness, donor relevance, public finance relevance, SPV-readiness, AEP Passport finance-layer, Nexus Rail finance-route, Docket, or handoff matters require structured discussion.

**6.2.7.2** No-reliance rooms shall begin with express no-reliance terms stating that the room does not provide investment advice, financial advice, insurance advice, legal advice, tax advice, accounting advice, securities advice, procurement advice, public finance advice, donor advice, philanthropic advice, underwriting, guarantee approval, rating, public authority approval, certification, consent, SPV approval, project approval, or execution authorization.

**6.2.7.3** Participants shall acknowledge no-reliance terms before or at entry.

**6.2.7.4** No-reliance rooms may produce questions, observations, gaps, dependencies, routeability notes, Docket issues, or correction needs, but not commitments, approvals, investment indications, underwriting indications, donor commitments, public finance commitments, or transaction decisions.

**6.2.7.5** The governing rule shall be:

**A no-reliance room exists to prevent readiness dialogue from becoming reliance.**

***

### 6.2.8 Capital-Reader Rooms

**6.2.8.1** Capital-reader rooms may be convened to allow classified capital readers to understand national Nexus readiness questions under controlled no-reliance conditions.

**6.2.8.2** Capital-reader rooms may involve investors, banks, funds, family offices, insurers, reinsurers, donors, philanthropies, development finance actors, public finance readers, guarantee actors, risk-transfer actors, and other authorized participants.

**6.2.8.3** Capital-reader rooms shall not be fundraising rooms, securities rooms, investor roadshows, lender meetings, insurance placement rooms, underwriting rooms, donor commitment rooms, public finance allocation rooms, guarantee rooms, rating rooms, procurement rooms, or transaction rooms.

**6.2.8.4** Capital-reader room outputs shall be limited to capital-readability questions, diligence gaps, information needs, public authority dependencies, insurance questions, donor relevance, public finance relevance, safeguard issues, Docket items, and correction needs.

**6.2.8.5** The governing rule shall be:

**Capital-reader rooms let capital read readiness; they do not let capital commit, control, or transact.**

***

### 6.2.9 Insurance-Readiness Rooms

**6.2.9.1** Insurance-readiness rooms may be convened where national Nexus matters require risk, exposure, loss, control, underwriting information, reinsurance, disaster-risk finance, resilience, catastrophe, or risk-transfer discussion.

**6.2.9.2** Insurance-readiness rooms shall be no-reliance, non-advisory, non-soliciting, non-transactional, competition-compliant, confidentiality-aware, regulated-perimeter controlled, and claims-limited.

**6.2.9.3** Insurance-readiness rooms shall not approve coverage, bind insurance, place insurance, approve premiums, determine insurability, underwrite risk, approve reinsurance, approve guarantees, or provide insurance advice.

**6.2.9.4** Outputs shall be questions, gaps, dependencies, model needs, data needs, public authority interface issues, safeguard conditions, Docket items, or correction needs.

**6.2.9.5** The governing rule shall be:

**Insurance-readiness rooms organize insurance questions; they do not create insurance answers.**

***

### 6.2.10 Public Finance Relevance Rooms

**6.2.10.1** Public finance relevance rooms may be convened where national Nexus matters involve public finance relevance, public investment, public grants, public guarantees, subsidies, concessional finance, resilience finance, disaster-risk finance, climate finance, infrastructure finance, budget dependencies, or public authority funding questions.

**6.2.10.2** Public finance relevance rooms shall classify public authority and public finance participants by capacity and shall state no-public-finance-approval language.

**6.2.10.3** Such rooms shall not allocate public finance, approve budgets, approve grants, approve public guarantees, approve subsidies, approve procurement, issue official positions, or create government endorsement.

**6.2.10.4** Outputs shall identify public finance relevance, public authority dependencies, evidence needs, budget questions, public value questions, public finance gaps, Docket items, or escalation needs.

**6.2.10.5** The governing rule shall be:

**Public finance relevance rooms identify public finance questions; they do not spend or commit public money.**

***

### 6.2.11 Donor and Philanthropic Relevance Rooms

**6.2.11.1** Donor and philanthropic relevance rooms may be convened where national Nexus matters may align with donor, philanthropic, foundation, CSR, humanitarian, development, climate, resilience, disaster-risk, public-good, community, youth, accessibility, research, or capacity-building priorities.

**6.2.11.2** Donor and philanthropic relevance rooms shall be no-reliance, non-soliciting, non-transactional, claims-limited, confidentiality-aware, safeguard-aware, and public-safe where outputs are released.

**6.2.11.3** Such rooms shall not approve grants, create donor commitments, create philanthropic commitments, create pledges, allocate awards, approve CSR support, create sponsorship commitments, or create funding expectations.

**6.2.11.4** Outputs shall identify relevance questions, evidence needs, reporting needs, safeguard expectations, community conditions, public authority dependencies, Docket items, or correction needs.

**6.2.11.5** The governing rule shall be:

**Donor and philanthropic rooms test relevance; they do not make commitments.**

***

### 6.2.12 Nexus Universe Preparation Sessions

**6.2.12.1** The National Investors Council may convene Nexus Universe preparation sessions for national finance-readiness, capital-reader rooms, insurance-readiness rooms, donor relevance rooms, public finance relevance rooms, development-readiness rooms, SPV-readiness rooms, AEP Passport finance-layer preparation, Nexus Rail finance-route preparation, Docket capture, and post-cycle correction planning.

**6.2.12.2** Nexus Universe preparation sessions shall align with the annual Nexus Universe cycle, including one-year preparation, Nexus Core Build, live operation, post-cycle debrief, public-safe reporting, Docket review, Grid review where applicable, correction, archive, and renewal.

**6.2.12.3** Nexus Universe preparation shall not convert annual visibility into investment interest, insurance approval, donor commitment, public finance allocation, public authority approval, certification, procurement status, SPV approval, project approval, or execution authority.

**6.2.12.4** Nexus Universe preparation outputs shall be classified, no-reliance, claims-limited, safeguard-aware, and correctionable.

**6.2.12.5** The governing rule shall be:

**Nexus Universe preparation makes capital-facing readiness ready for public-good display without turning display into finance.**

***

### 6.2.13 Joint Sessions With Helix Councils

**6.2.13.1** The National Investors Council may convene joint sessions with Helix Councils where finance-readiness depends on cross-helix input.

**6.2.13.2** Joint sessions may involve the Capital / Insurance / Donor / Development Helix Council, Government / Public Authority Helix Council, Industry / Enterprise / Infrastructure / Technology Helix Council, Academia / Research / Science Helix Council, Media / Civic / Public-Interest Helix Council, Community / Indigenous / Diaspora / Place-Based Legitimacy Helix Council, or other authorized national helix structures.

**6.2.13.3** Joint sessions shall preserve role separation. Public authority input shall not become approval. Provider input shall not become validation. Community input shall not become consent. Capital input shall not become finance. Donor input shall not become commitment. Academic input shall not become certification.

**6.2.13.4** Joint session outputs shall identify source, role, classification, conflicts, safeguards, no-reliance status, claims limits, and correction pathway.

**6.2.13.5** The governing rule shall be:

**Joint sessions enrich finance-readiness only when each helix remains in its proper role.**

***

### 6.2.14 Joint Sessions With National Leadership Council

**6.2.14.1** The National Investors Council may convene joint sessions with the National Leadership Council where national priorities, leadership mobilization, Nexus Universe preparation, National Model preparation, National Working Groups, public-safe reporting, AEP Passport candidates, Nexus Rail candidates, Docket items, or lawful handoff require finance-readiness interpretation.

**6.2.14.2** Joint sessions shall preserve the distinction between leadership readiness and finance-readiness.

**6.2.14.3** Leadership Council participation shall not create finance approval. Investors Council participation shall not create leadership authority. Capital-reader presence shall not influence leadership-pool status, board-candidate status, or stewardship selection except through recorded and claims-limited public-good readiness inputs.

**6.2.14.4** Outputs shall identify which matters belong to leadership pathways, which belong to finance-readiness pathways, which require joint coordination, and which require escalation or correction.

**6.2.14.5** The governing rule shall be:

**Joint Leadership-Investors sessions align national readiness and capital-readiness without merging their powers.**

***

## 6.3 Chairing and Roles

### 6.3.1 Chair

**6.3.1.1** The Chair shall steward the National Investors Council’s mandate, agenda, procedures, boundary discipline, records discipline, no-reliance discipline, conflict controls, safeguard controls, and correctionability.

**6.3.1.2** The Chair shall ensure that meetings remain within the Council’s finance-readiness, capital-readability, insurance-readiness, donor relevance, public finance relevance, diligence-gap, SPV-readiness, Nexus Rail, AEP Passport, Nexus Universe, and lawful handoff mandate.

**6.3.1.3** The Chair shall have no investment approval power, insurance approval power, donor approval power, public finance approval power, transaction power, procurement power, certification power, public authority power, Company power, SPV power, or execution power by virtue of the role.

**6.3.1.4** The Chair shall intervene where discussion drifts toward advice, solicitation, transaction, market coordination, public authority overclaim, finance overclaim, insurance overclaim, donor overclaim, public finance overclaim, sponsor or provider capture, safeguard erosion, or execution implication.

**6.3.1.5** The governing rule shall be:

**The Chair’s first duty is to keep the Council inside readiness and outside finance execution.**

***

### 6.3.2 Co-Chair

**6.3.2.1** A Co-Chair may support the Chair in convening, agenda discipline, cross-helix coordination, capital-readiness structure, insurance-readiness structure, donor and public finance relevance, Nexus Universe preparation, Docket capture, and correction.

**6.3.2.2** Co-Chair structure may be used to balance national ownership, finance-boundary expertise, public-good discipline, capital-readiness expertise, insurance-readiness expertise, development-readiness expertise, and safeguard awareness.

**6.3.2.3** A Co-Chair shall not represent capital, insurers, donors, public finance actors, sponsors, providers, public authorities, GRA, GRF, GCRI, National Consortium Companies, or Project SPVs unless a separate record expressly classifies that role.

**6.3.2.4** Co-Chair authority shall remain scope-limited, claims-limited, conflict-reviewed, and correctionable.

**6.3.2.5** The governing rule shall be:

**A Co-Chair supports boundary-safe leadership, not capital influence.**

***

### 6.3.3 Vice-Chair

**6.3.3.1** A Vice-Chair may support continuity, meeting preparation, session leadership, record oversight, escalation tracking, annual review, and correction follow-up.

**6.3.3.2** The Vice-Chair may chair meetings where the Chair or Co-Chair is unavailable or recused, subject to role classification and conflict controls.

**6.3.3.3** The Vice-Chair shall carry the same no-reliance, non-advisory, non-solicitation, non-transaction, competition-compliance, regulated-perimeter, safeguard, and claims obligations as the Chair.

**6.3.3.4** Vice-Chair status shall not imply investment, finance, insurance, donor, public finance, procurement, certification, public authority, SPV, Company, or execution authority.

**6.3.3.5** The governing rule shall be:

**The Vice-Chair protects continuity without expanding authority.**

***

### 6.3.4 Rapporteur

**6.3.4.1** The Rapporteur shall support accurate, classified, no-reliance, claims-limited, and public-safe recording of Council meetings and outputs.

**6.3.4.2** Rapporteur records shall distinguish discussion, question, observation, dependency, gap, recommendation, routeability note, Docket item, correction item, and decision by competent body.

**6.3.4.3** The Rapporteur shall avoid language implying finance approval, insurance approval, donor commitment, public finance allocation, investment interest, guarantee support, transaction readiness, procurement status, certification, public authority approval, SPV approval, project authorization, consent, or execution.

**6.3.4.4** Rapporteur notes shall be reviewed for confidentiality, publication class, public authority sensitivity, finance sensitivity, safeguard sensitivity, and claims discipline before circulation.

**6.3.4.5** The governing rule shall be:

**The Rapporteur records readiness without creating approval by wording.**

***

### 6.3.5 Records Lead

**6.3.5.1** The Records Lead shall support the integrity of Council records.

**6.3.5.2** Records may include meeting records, attendance records, role classification records, conflict records, no-reliance acknowledgment records, finance-readiness records, capital-readability records, insurance-readiness records, public finance relevance records, donor and philanthropic relevance records, diligence-gap records, SPV-readiness records, Nexus Rail records, AEP Passport finance-layer records, correction records, and archive records.

**6.3.5.3** The Records Lead shall ensure that records identify source, date, role, classification, limitations, confidentiality status, public authority status, no-reliance status, claims limits, safeguard conditions, correction pathway, and archive status where applicable.

**6.3.5.4** The Records Lead shall not decide finance, insurance, donor, public finance, procurement, certification, public authority, Company, SPV, or execution matters by recording them.

**6.3.5.5** The governing rule shall be:

**Records make readiness traceable; they do not create finance authority.**

***

### 6.3.6 No-Reliance and Boundary Lead

**6.3.6.1** The No-Reliance and Boundary Lead shall monitor and support no-reliance discipline, non-advisory status, non-solicitation controls, non-transaction controls, competition compliance, regulated-perimeter control, and claims boundaries.

**6.3.6.2** The Lead shall review agendas, room terms, meeting scripts, participant notices, public-facing materials, investor-facing materials, insurer-facing materials, donor-facing materials, public finance-facing materials, Nexus Universe materials, AEP Passport finance-layer materials, Rail finance-route notes, and handoff notes for boundary risks.

**6.3.6.3** The Lead may recommend that a meeting be paused, restricted, reclassified, corrected, or escalated where reliance, advice, solicitation, transaction, securities, insurance, public finance, donor, procurement, public authority, competition, or execution risk arises.

**6.3.6.4** The Lead shall not provide legal, financial, investment, insurance, tax, accounting, procurement, public finance, or securities advice through the role.

**6.3.6.5** The governing rule shall be:

**The Boundary Lead protects the Council from becoming the regulated activity it is only meant to prepare for.**

***

### 6.3.7 Finance-Readiness Lead

**6.3.7.1** The Finance-Readiness Lead shall support national finance-readiness review and capital-readability question formation.

**6.3.7.2** The Lead may coordinate review of evidence needs, diligence gaps, risk-to-capital questions, revenue and cost assumptions, lifecycle questions, governance conditions, public authority dependencies, insurance dependencies, donor dependencies, public finance dependencies, and SPV-readiness conditions.

**6.3.7.3** The Lead shall not provide investment advice, financial advice, finance approval, lending approval, guarantee approval, capital commitment, bankability conclusion, financeability conclusion, rating, transaction arrangement, or capital solicitation.

**6.3.7.4** Finance-readiness outputs led by the Lead shall remain no-reliance, claims-limited, and correctionable.

**6.3.7.5** The governing rule shall be:

**The Finance-Readiness Lead organizes finance questions, not finance decisions.**

***

### 6.3.8 Insurance-Readiness Lead

**6.3.8.1** The Insurance-Readiness Lead shall support insurance-readiness, reinsurance-readiness, risk-transfer, disaster-risk-finance, catastrophe, resilience, protection-gap, and exposure-related question formation.

**6.3.8.2** The Lead may support identification of insurance gaps, reinsurance gaps, exposure data needs, model dependencies, risk controls, public authority insurance interfaces, infrastructure insurance questions, climate and disaster exposure questions, and insurance boundary corrections.

**6.3.8.3** The Lead shall not provide insurance advice, underwriting, coverage approval, premium indication, reinsurance approval, risk-transfer approval, guarantee approval, or insurance placement.

**6.3.8.4** Insurance-readiness outputs shall remain questions, gaps, dependencies, or no-reliance notes.

**6.3.8.5** The governing rule shall be:

**The Insurance-Readiness Lead identifies insurance questions without giving insurance answers.**

***

### 6.3.9 Public Finance Relevance Lead

**6.3.9.1** The Public Finance Relevance Lead shall support mapping of public finance relevance, budget dependencies, public investment questions, public guarantee questions, concessional finance questions, resilience finance, disaster-risk finance, climate finance, infrastructure finance, and public authority funding dependencies.

**6.3.9.2** The Lead shall ensure public authority capacity classification, no-public-finance-approval language, public-safe communication, and claims limits are applied.

**6.3.9.3** The Lead shall not approve public finance, allocate public funds, approve guarantees, approve grants, direct budgets, approve procurement, speak for public authorities, or create official positions.

**6.3.9.4** Public finance relevance outputs shall be relevance maps, dependency notes, Docket items, or escalation notes, not allocations.

**6.3.9.5** The governing rule shall be:

**The Public Finance Relevance Lead maps public finance questions without creating public finance.**

***

### 6.3.10 Donor and Philanthropic Relevance Lead

**6.3.10.1** The Donor and Philanthropic Relevance Lead shall support donor relevance, philanthropic relevance, foundation relevance, CSR relevance, development-support relevance, grant-readiness questions, and mission-fit mapping.

**6.3.10.2** The Lead may coordinate review of outcome logic, evidence needs, reporting requirements, safeguard expectations, community conditions, public authority dependencies, and capacity-building relevance.

**6.3.10.3** The Lead shall not approve grants, commit donors, commit philanthropies, issue pledges, allocate awards, create sponsorship commitments, or create funding expectations.

**6.3.10.4** Donor and philanthropic outputs shall distinguish relevance from commitment.

**6.3.10.5** The governing rule shall be:

**The Donor and Philanthropic Relevance Lead identifies possible mission fit, not funding commitments.**

***

### 6.3.11 SPV-Readiness Lead

**6.3.11.1** The SPV-Readiness Lead shall support review of Project SPV-readiness and National Consortium Company finance-interface questions.

**6.3.11.2** The Lead may identify legal structure questions, governance conditions, public authority dependencies, procurement dependencies, finance-readiness conditions, insurance-readiness conditions, donor relevance, public finance relevance, provider-neutrality requirements, safeguard conditions, data rights, land or asset rights, lifecycle obligations, operating responsibility, and handoff conditions.

**6.3.11.3** The Lead shall not approve SPV formation, project approval, company action, finance, insurance, procurement, provider selection, public authority approval, consent, or execution.

**6.3.11.4** SPV-readiness outputs shall remain questions, dependencies, restrictions, routeability notes, or handoff conditions.

**6.3.11.5** The governing rule shall be:

**The SPV-Readiness Lead identifies what an SPV pathway would require; the role does not create the SPV pathway.**

***

### 6.3.12 Nexus Rails Lead

**6.3.12.1** The Nexus Rails Lead shall support routing of finance-readiness matters through Nexus Rail pathways where authorized.

**6.3.12.2** The Lead may identify possible routes, receiving pathways, routeability conditions, finance-readiness dependencies, insurance-readiness dependencies, donor relevance, public finance relevance, safeguard restrictions, public authority dependencies, Docket issues, AEP Passport finance-layer needs, and handoff limitations.

**6.3.12.3** The Lead shall not execute Rails, approve routes as final, approve finance, approve insurance, approve public finance, approve donor support, approve procurement, approve SPVs, or authorize execution.

**6.3.12.4** Rail outputs shall be routeability notes and not execution instructions.

**6.3.12.5** The governing rule shall be:

**The Nexus Rails Lead supports routing discipline, not route execution.**

***

### 6.3.13 AEP Passport Finance Layer Lead

**6.3.13.1** The AEP Passport Finance Layer Lead shall support finance-readiness inputs to AEP Passport candidate pathways.

**6.3.13.2** The Lead may identify capital-readable evidence needs, finance-readiness gaps, insurance-readiness gaps, donor relevance, public finance relevance, risk allocation questions, safeguard conditions, public authority dependencies, SPV-readiness conditions, Docket issues, Rail routeability, and handoff limitations.

**6.3.13.3** The Lead shall not issue AEP Passports, approve AEP Passport status, certify candidates, declare Nexus-ready status, approve financeability, approve insurability, approve procurement, approve public authority status, consent, or execution readiness.

**6.3.13.4** Passport finance-layer outputs shall be candidate inputs only and shall remain subject to competent Passport process authority.

**6.3.13.5** The governing rule shall be:

**The AEP Passport Finance Layer Lead contributes finance-readiness inputs; the role does not issue or validate the Passport.**

***

### 6.3.14 Conflict and Correction Lead

**6.3.14.1** The Conflict and Correction Lead shall support identification, classification, management, and correction of conflicts, overclaims, role errors, participation errors, no-reliance failures, confidentiality breaches, safeguard omissions, public authority overclaims, finance overclaims, insurance overclaims, donor overclaims, public finance overclaims, SPV overclaims, Rail overclaims, AEP Passport overclaims, and handoff overclaims.

**6.3.14.2** The Lead may recommend disclosure, recusal, restriction, role reclassification, room exclusion, claim narrowing, public clarification, controlled clarification, publication reclassification, Docket entry, handoff restriction, suspension, withdrawal, supersession, archive, or reinstatement.

**6.3.14.3** The Lead shall preserve fairness, proportionality, public-good protection, confidentiality, public-safe communication, and correctionability.

**6.3.14.4** The Lead shall not use correction authority to suppress legitimate dissent, safeguard concerns, public-interest critique, technical truth, community concerns, or lawful caution.

**6.3.14.5** The governing rule shall be:

**The Conflict and Correction Lead protects the Council by correcting the record before reliance forms.**

***

## 6.4 Deliberation and Decision Support

### 6.4.1 Deliberative Character

**6.4.1.1** The National Investors Council shall be deliberative in character.

**6.4.1.2** Deliberation may include discussion, questioning, issue-spotting, evidence review, gap identification, routeability review, public authority dependency mapping, insurance-readiness review, donor relevance review, public finance relevance review, SPV-readiness review, and correction discussion.

**6.4.1.3** Deliberation shall not be treated as approval, commitment, advice, solicitation, transaction, underwriting, rating, public finance allocation, donor approval, procurement, certification, public authority action, consent, or execution.

**6.4.1.4** Deliberation shall be structured to prevent market reliance, public authority confusion, donor expectation, insurance expectation, sponsor advantage, provider advantage, and public overclaim.

**6.4.1.5** The governing rule shall be:

**Deliberation creates better questions and records; it does not create finance decisions.**

***

### 6.4.2 Recommendations, Not Final Decisions

**6.4.2.1** The National Investors Council may make recommendations to the National Council, National Leadership Council, Stewardship Board where formed, Helix Councils, National Working Groups, Nexus Universe preparation pathways, AEP Passport pathways, Nexus Rail pathways, Docket pathways, National Consortium Company interface pathways, Project SPV-readiness pathways, GRA-aligned pathways, or other competent receiving bodies.

**6.4.2.2** Recommendations may concern finance-readiness questions, capital-readability needs, insurance-readiness gaps, donor relevance, public finance relevance, diligence gaps, SPV-readiness questions, handoff conditions, boundary restrictions, correction needs, or escalation.

**6.4.2.3** Recommendations shall not be final decisions unless a separate competent body adopts them through proper record.

**6.4.2.4** A recommendation shall not be described as approval, adoption, commitment, finance, insurance, donor support, public finance allocation, procurement, certification, SPV approval, project approval, consent, or execution.

**6.4.2.5** The governing rule shall be:

**The Council recommends readiness treatment; competent bodies decide what, if anything, follows.**

***

### 6.4.3 Finance-Readiness Question Process

**6.4.3.1** The finance-readiness question process shall identify the finance-facing questions that must be answered or routed before a matter can be responsibly presented to capital readers or considered for lawful handoff.

**6.4.3.2** The process may consider evidence, technical status, public authority dependency, data and cyber status, safeguards, legal and regulatory issues, procurement dependency, revenue and cost assumptions, lifecycle obligations, risk allocation, insurance, donor relevance, public finance relevance, SPV-readiness, and handoff conditions.

**6.4.3.3** The process shall produce questions, dependencies, gaps, restrictions, or routeability notes, not approvals.

**6.4.3.4** The process shall apply no-reliance, claims limits, confidentiality classification, and correction pathways.

**6.4.3.5** The governing rule shall be:

**A finance-readiness question process is complete only when it identifies what is known, unknown, restricted, unresolved, and not approved.**

***

### 6.4.4 Capital-Readability Review Process

**6.4.4.1** The capital-readability review process shall assess whether a national Nexus matter can be understood by capital readers without creating false finance, investment, insurance, donor, public finance, or transaction meaning.

**6.4.4.2** The review may examine problem statement, evidence, maturity, risk, assumptions, safeguards, public authority dependencies, operating model, lifecycle, revenue or value logic, insurance questions, donor relevance, public finance relevance, SPV-readiness, and handoff conditions.

**6.4.4.3** Capital-readability review shall not approve market readiness, investment readiness, financeability, bankability, insurability, donor readiness, public finance readiness, or transaction readiness.

**6.4.4.4** Materials produced through review shall be labelled, no-reliance, claims-limited, and correctionable.

**6.4.4.5** The governing rule shall be:

**Capital-readability review improves intelligibility without creating market status.**

***

### 6.4.5 Insurance-Readiness Review Process

**6.4.5.1** The insurance-readiness review process shall identify insurance and reinsurance questions, gaps, and dependencies relevant to a national Nexus matter.

**6.4.5.2** The review may examine exposure, hazard, vulnerability, loss, controls, data quality, model dependency, operating responsibility, asset status, cyber risk, climate risk, infrastructure risk, public authority dependency, and safeguard conditions.

**6.4.5.3** Insurance-readiness review shall not approve insurance, provide insurance advice, determine insurability, bind coverage, approve premiums, approve underwriting, place insurance, approve reinsurance, or approve risk transfer.

**6.4.5.4** The review shall produce questions, gaps, dependencies, routeability notes, or Docket items.

**6.4.5.5** The governing rule shall be:

**Insurance-readiness review identifies what insurance actors would need to know; it does not act as an insurance actor.**

***

### 6.4.6 Public Finance Relevance Review Process

**6.4.6.1** The public finance relevance review process shall identify whether a national Nexus matter may be relevant to public finance, public investment, budget, grant, subsidy, public guarantee, concessional finance, resilience finance, disaster-risk finance, infrastructure finance, climate finance, or public authority funding pathways.

**6.4.6.2** The review may examine public-good value, public authority dependency, fiscal context, public investment logic, public guarantee questions, procurement dependencies, development relevance, and safeguard conditions.

**6.4.6.3** Public finance relevance review shall not approve public finance, allocate public funds, approve guarantees, direct budgets, approve grants, approve procurement, or create official positions.

**6.4.6.4** Outputs shall carry capacity classification and no-public-finance-approval language.

**6.4.6.5** The governing rule shall be:

**Public finance relevance review identifies possible public finance interface; it does not create public finance.**

***

### 6.4.7 Donor and Philanthropic Relevance Review Process

**6.4.7.1** The donor and philanthropic relevance review process shall identify whether a national Nexus matter may align with donor, philanthropic, foundation, CSR, humanitarian, development, climate, resilience, disaster-risk, research, community, capacity-building, or public-good support priorities.

**6.4.7.2** The review may examine mission fit, outcome logic, evidence needs, reporting needs, safeguard expectations, community conditions, public authority dependencies, implementation capacity, and public-safe communication.

**6.4.7.3** Donor and philanthropic relevance review shall not approve grants, create donor commitments, create philanthropic commitments, allocate funds, issue pledges, approve CSR support, or create funding expectations.

**6.4.7.4** Outputs shall distinguish relevance from commitment.

**6.4.7.5** The governing rule shall be:

**Donor and philanthropic review asks whether a matter is relevant; it does not make anyone responsible to fund it.**

***

### 6.4.8 Diligence-Gap Review Process

**6.4.8.1** The diligence-gap review process shall identify what is missing, unresolved, uncertain, restricted, conflicted, or unsuitable for capital-facing consideration.

**6.4.8.2** The review may include evidence gaps, legal gaps, regulatory gaps, public authority gaps, procurement gaps, finance gaps, insurance gaps, donor gaps, public finance gaps, technical gaps, data gaps, cyber gaps, safeguard gaps, community or Indigenous consent-boundary gaps where applicable, operating gaps, lifecycle gaps, risk allocation gaps, provider-neutrality gaps, governance gaps, and handoff gaps.

**6.4.8.3** Diligence-gap review shall not complete due diligence, provide legal clearance, provide financial clearance, provide insurance clearance, provide donor approval, provide public finance approval, provide safeguard clearance, or approve a project.

**6.4.8.4** Gaps shall be classified and routed to competent pathways or Docket where required.

**6.4.8.5** The governing rule shall be:

**A diligence-gap review is successful when it prevents unresolved gaps from being hidden by readiness language.**

***

### 6.4.9 Project SPV-Readiness Review Process

**6.4.9.1** The Project SPV-readiness review process shall identify whether a matter may require future Project SPV consideration and what conditions would need to be addressed before such consideration.

**6.4.9.2** The review may consider public authority approvals, procurement, permits, licences, finance-readiness, insurance-readiness, donor relevance, public finance relevance, governance, contracts, data rights, land rights, asset rights, provider-neutrality, safeguards, consent boundaries, lifecycle obligations, operator responsibility, risk allocation, National Consortium Company interface, and handoff conditions.

**6.4.9.3** Project SPV-readiness review shall not approve SPV formation, project approval, finance, insurance, procurement, provider selection, consent, Company action, or execution.

**6.4.9.4** Outputs shall be questions, conditions, restrictions, routeability notes, or handoff inputs, not approvals.

**6.4.9.5** The governing rule shall be:

**SPV-readiness review prepares a question set for lawful actors, not an authorization for a project vehicle.**

***

### 6.4.10 Escalation to National Council

**6.4.10.1** The National Investors Council shall escalate matters to the National Council where finance-readiness questions affect national priorities, public-good records, cross-helix balance, National Model content, Nexus Universe priorities, public authority learning, safeguards, claims discipline, or lawful handoff.

**6.4.10.2** Escalation may include finance-readiness notes, insurance-readiness notes, donor relevance notes, public finance relevance notes, diligence-gap records, SPV-readiness notes, Docket items, Nexus Rail routeability notes, AEP Passport finance-layer notes, correction records, or handoff restrictions.

**6.4.10.3** Escalation shall not imply adoption by the National Council.

**6.4.10.4** The National Council may accept, reject, defer, restrict, correct, route, renew, or archive escalated matters.

**6.4.10.5** The governing rule shall be:

**Escalation brings finance-readiness issues to national ownership; it does not decide them.**

***

### 6.4.11 Escalation to National Leadership Council

**6.4.11.1** The National Investors Council shall escalate matters to the National Leadership Council where finance-readiness issues affect national leadership priorities, leadership-pool considerations, cross-helix coordination, Nexus Universe mobilization, National Working Group formation, National Model priorities, public-safe reporting, or national renewal.

**6.4.11.2** Escalation may include capital-readiness concerns, finance-related leadership risks, donor or public finance overclaim, sponsor or provider capture risk, SPV-readiness concerns, public authority dependency, safeguard dependency, or Docket item.

**6.4.11.3** Escalation shall not imply that the National Leadership Council has approved finance or that the National Investors Council has approved leadership authority.

**6.4.11.4** Joint correction may be required where finance-readiness overclaim and leadership overclaim intersect.

**6.4.11.5** The governing rule shall be:

**Escalation to leadership aligns readiness with national stewardship; it shall not merge leadership authority with finance authority.**

***

### 6.4.12 Escalation to National Stewardship Board Where Formed

**6.4.12.1** Where a National Stewardship Board has been formed, the National Investors Council shall escalate matters requiring board-level public-good governance attention.

**6.4.12.2** Such matters may include major finance-readiness risks, public authority-sensitive issues, material donor or public finance implications, Nexus Universe capital-room risks, SPV-readiness concerns, National Consortium Company interface risks, safeguard dependencies, conflicts, competition concerns, public-safe reporting risks, Docket issues, and major overclaim corrections.

**6.4.12.3** Escalation to the Stewardship Board shall not imply Board approval unless the Board adopts or decides the matter by competent record.

**6.4.12.4** Board-level treatment shall preserve no-reliance, non-advisory, non-solicitation, non-transaction, competition-compliance, regulated-perimeter, and safeguard controls.

**6.4.12.5** The governing rule shall be:

**Board escalation seeks public-good governance treatment, not finance approval.**

***

### 6.4.13 Escalation to GRA-Aligned Pathways

**6.4.13.1** The National Investors Council may escalate matters to GRA-aligned pathways where finance-readiness, capital-readability, insurance-readiness, disaster-risk-finance, diligence-gap, public finance relevance, risk-to-capital, SPV-readiness, investor-council discipline, or lawful finance-boundary issues require broader GRA-aligned treatment.

**6.4.13.2** Escalation to GRA-aligned pathways shall not imply GRA membership, GRA appointment, GRA approval, GRA finance approval, GRA insurance approval, GRA donor approval, GRA public finance approval, GRA guarantee support, GRA transaction support, or GRA fiduciary role.

**6.4.13.3** Escalated matters shall carry national ownership records, no-reliance status, confidentiality class, public authority status, finance-readiness status, safeguard conditions, conflicts, claims limits, and correction pathway.

**6.4.13.4** A separate GRA record shall be required for any GRA action, status, pathway, or claim.

**6.4.13.5** The governing rule shall be:

**GRA-aligned escalation may deepen finance-boundary discipline; it does not create GRA authority or finance.**

***

### 6.4.14 Record of Non-Adoption, Deferral, Restriction, or Rejection

**6.4.14.1** The National Investors Council shall record non-adoption, deferral, restriction, or rejection of its recommendations, notes, routeability suggestions, Docket proposals, AEP Passport finance-layer inputs, Nexus Rail finance-route inputs, SPV-readiness notes, or handoff suggestions where a competent receiving body does not adopt or proceed with them.

**6.4.14.2** A non-adoption record shall state that the matter was not adopted and shall prevent external claims that it was approved or accepted.

**6.4.14.3** A deferral record shall identify why the matter was deferred, what conditions remain unresolved, and what future review may be required.

**6.4.14.4** A restriction or rejection record shall identify the restriction or rejection basis, affected claims, public-safe implications, Docket status, archive status, and correction requirements.

**6.4.14.5** The governing rule shall be:

**A matter that is not adopted must be recorded as not adopted before silence becomes false approval.**

***

## 6.5 Records

### 6.5.1 Meeting Records

**6.5.1.1** The National Investors Council shall keep meeting records for all ordinary meetings, special meetings, controlled meetings, no-reliance rooms, capital-reader rooms, insurance-readiness rooms, public finance relevance rooms, donor and philanthropic relevance rooms, Nexus Universe preparation sessions, Helix joint sessions, National Leadership Council joint sessions, Docket sessions, AEP Passport finance-layer sessions, Nexus Rail sessions, and handoff sessions.

**6.5.1.2** Meeting records shall identify date, convening authority, purpose, agenda, participants, roles, classification, no-reliance terms, confidentiality terms, conflicts disclosed, materials reviewed, questions identified, dependencies identified, outputs produced, restrictions, Docket issues, correction items, and next routing.

**6.5.1.3** Meeting records shall distinguish discussion from recommendation, recommendation from adoption, adoption from external approval, and readiness from finance.

**6.5.1.4** Meeting records shall not be drafted in language that implies investment approval, insurance approval, donor commitment, public finance allocation, public authority approval, procurement status, certification, SPV approval, project authorization, or execution.

**6.5.1.5** The governing rule shall be:

**A meeting record must record what happened without creating what did not happen.**

***

### 6.5.2 Attendance Records

**6.5.2.1** The National Investors Council shall maintain attendance records.

**6.5.2.2** Attendance records shall identify participant name, institution where applicable, role classification, capacity, attendance status, observer or guest status, room access, confidentiality status, no-reliance acknowledgment status, conflict status, and claims permissions where relevant.

**6.5.2.3** Attendance shall not imply approval, endorsement, contribution, finance interest, insurance interest, donor interest, public finance support, public authority position, or handoff role.

**6.5.2.4** Attendance records shall be classified where participant identity is sensitive.

**6.5.2.5** The governing rule shall be:

**Attendance proves presence only; it does not prove commitment, approval, or authority.**

***

### 6.5.3 Role Classification Records

**6.5.3.1** The National Investors Council shall maintain role classification records for all participants.

**6.5.3.2** Role classification records shall identify whether a participant acts as capital reader, finance-readiness contributor, insurance-readiness contributor, donor relevance contributor, public finance relevance contributor, development-readiness contributor, diligence-gap contributor, risk-to-capital contributor, SPV-readiness contributor, no-reliance room participant, observer, non-advisory expert, institutional representative, guest, public authority learner, sponsor-linked participant, provider-linked participant, National Consortium Company observer, Project SPV pathway observer, or other recorded role.

**6.5.3.3** Role classification records shall include authority limits, claims permissions, conflict status, confidentiality obligations, access rights, public-safe limits, and correction pathway.

**6.5.3.4** Role classification shall be reviewed when facts change.

**6.5.3.5** The governing rule shall be:

**Role records prevent participation from being mistaken for authority.**

***

### 6.5.4 Conflict Records

**6.5.4.1** The National Investors Council shall maintain conflict records.

**6.5.4.2** Conflict records shall identify actual, potential, perceived, financial, institutional, public authority, provider, sponsor, capital-reader, insurer, donor, public finance, advisory, legal, transaction, National Consortium Company, Project SPV, procurement, intellectual property, family, employment, and other relevant conflicts.

**6.5.4.3** Conflict records shall state whether a conflict is disclosed and monitored, disclosed and managed, recusal-required, access-restricted, unresolved, under review, disqualifying, corrected, or closed.

**6.5.4.4** Conflict records shall be linked to affected meetings, records, recommendations, outputs, Docket items, handoff notes, and corrections where relevant.

**6.5.4.5** The governing rule shall be:

**A finance-readiness record is incomplete if the conflicts behind it are invisible.**

***

### 6.5.5 No-Reliance Acknowledgment Records

**6.5.5.1** The National Investors Council shall maintain no-reliance acknowledgment records.

**6.5.5.2** Such records shall identify the participant, date, scope, room or activity covered, no-reliance terms accepted, non-advisory terms accepted, non-solicitation terms accepted, non-transaction terms accepted, regulated-perimeter terms accepted, and any renewal requirement.

**6.5.5.3** No participant shall participate in sensitive finance-facing rooms without appropriate no-reliance acknowledgment unless the competent convening authority expressly records a narrow exception.

**6.5.5.4** No-reliance acknowledgment records shall support correction where a participant later treats Council materials as reliance materials.

**6.5.5.5** The governing rule shall be:

**No-reliance is not merely language; it must be acknowledged and recorded.**

***

### 6.5.6 Finance-Readiness Records

**6.5.6.1** The National Investors Council shall maintain finance-readiness records.

**6.5.6.2** Finance-readiness records may include finance-readiness notes, question lists, evidence needs, public authority dependencies, technical dependencies, data and cyber dependencies, safeguard dependencies, revenue and cost assumptions, lifecycle questions, risk allocation questions, governance conditions, legal and regulatory dependencies, procurement dependencies, insurance dependencies, public finance dependencies, donor dependencies, Docket issues, routeability notes, and handoff conditions.

**6.5.6.3** Finance-readiness records shall not be treated as finance approval, investment advice, bankability, financeability, capital commitment, lending approval, guarantee approval, public finance approval, donor approval, or transaction readiness.

**6.5.6.4** Finance-readiness records shall carry no-reliance status, classification, limitations, and correction pathway.

**6.5.6.5** The governing rule shall be:

**Finance-readiness records record what must be understood before finance, not that finance exists.**

***

### 6.5.7 Capital-Readability Records

**6.5.7.1** The National Investors Council shall maintain capital-readability records.

**6.5.7.2** Capital-readability records may identify how a matter has been described for capital-reader understanding, what evidence is readable, what remains unclear, what risks are visible, what safeguards apply, what public authority dependencies exist, what assumptions require testing, and what limits apply.

**6.5.7.3** Capital-readability records shall not imply capital commitment, investment interest, bankability, financeability, securities offering, transaction readiness, or market status.

**6.5.7.4** Capital-readability records shall be reviewed before external circulation.

**6.5.7.5** The governing rule shall be:

**Capital-readability records help capital read the matter; they do not make capital act.**

***

### 6.5.8 Insurance-Readiness Records

**6.5.8.1** The National Investors Council shall maintain insurance-readiness records.

**6.5.8.2** Insurance-readiness records may identify exposure questions, hazard questions, vulnerability questions, loss questions, controls, resilience measures, data needs, model dependencies, risk-transfer questions, public authority insurance interfaces, infrastructure insurance questions, climate and disaster exposure questions, and insurance boundary corrections.

**6.5.8.3** Insurance-readiness records shall not imply insurance approval, underwriting, coverage, premium indication, insurability, reinsurance support, guarantee approval, insurance advice, or insurance placement.

**6.5.8.4** Insurance-readiness records shall be competition-compliant, confidentiality-aware, no-reliance, and claims-limited.

**6.5.8.5** The governing rule shall be:

**Insurance-readiness records preserve questions for insurers; they do not answer those questions as insurers.**

***

### 6.5.9 Public Finance Relevance Records

**6.5.9.1** The National Investors Council shall maintain public finance relevance records.

**6.5.9.2** Such records may identify public finance relevance, public authority dependencies, public investment logic, budget questions, public grant questions, public guarantee questions, concessional finance relevance, resilience finance relevance, disaster-risk finance relevance, climate finance relevance, infrastructure finance relevance, and public procurement dependencies.

**6.5.9.3** Public finance relevance records shall not imply public finance allocation, public funding approval, budget commitment, public guarantee, grant award, subsidy approval, procurement status, public authority endorsement, or official position.

**6.5.9.4** Public finance relevance records shall carry capacity classification and no-public-finance-approval language.

**6.5.9.5** The governing rule shall be:

**Public finance relevance records identify public finance questions, not public finance decisions.**

***

### 6.5.10 Donor and Philanthropic Relevance Records

**6.5.10.1** The National Investors Council shall maintain donor and philanthropic relevance records.

**6.5.10.2** Such records may identify donor relevance, philanthropic relevance, foundation relevance, CSR relevance, mission fit, outcome logic, evidence needs, reporting needs, safeguard expectations, community conditions, public authority dependencies, and capacity-building relevance.

**6.5.10.3** Donor and philanthropic relevance records shall not imply donor commitment, philanthropic commitment, foundation approval, grant award, pledge, allocation, CSR support, sponsorship, development assistance, or funding expectation.

**6.5.10.4** Donor and philanthropic records shall be claims-limited and public-safe where released.

**6.5.10.5** The governing rule shall be:

**Donor and philanthropic records map relevance without promising support.**

***

### 6.5.11 Diligence-Gap Records

**6.5.11.1** The National Investors Council shall maintain diligence-gap records.

**6.5.11.2** Diligence-gap records may identify legal, governance, finance, insurance, donor, public finance, technical, data, cyber, safeguard, public authority, procurement, environmental, social, community, Indigenous, land, asset, provider-neutrality, sponsor influence, operating model, lifecycle, revenue, risk allocation, and handoff gaps.

**6.5.11.3** Diligence-gap records shall not imply due diligence completion, legal clearance, financial clearance, insurance clearance, donor approval, public finance approval, procurement clearance, safeguard clearance, certification, or project approval.

**6.5.11.4** Diligence-gap records shall classify gaps as evidence-needed, technical-needed, legal-needed, public-authority-needed, finance-readiness-needed, insurance-readiness-needed, public-finance-needed, donor-needed, safeguard-needed, SPV-needed, Docketed, restricted, handoff-blocking, or correction-needed.

**6.5.11.5** The governing rule shall be:

**Diligence-gap records protect the system by recording what remains unresolved.**

***

### 6.5.12 SPV-Readiness Records

**6.5.12.1** The National Investors Council shall maintain Project SPV-readiness records.

**6.5.12.2** SPV-readiness records may identify legal structure questions, governance conditions, public authority approvals needed, procurement requirements, permits, licences, finance-readiness, insurance-readiness, donor relevance, public finance relevance, revenue or value logic, risk allocation, provider-neutral capability requirements, contracts, data rights, land or asset rights, community consent boundaries, Indigenous consent boundaries where applicable, environmental and social safeguards, cyber obligations, lifecycle responsibility, operator role, National Consortium Company interface, and handoff conditions.

**6.5.12.3** SPV-readiness records shall not imply SPV approval, project approval, SPV formation, financeability, bankability, insurability, procurement readiness, provider selection, public authority approval, consent, or execution authority.

**6.5.12.4** SPV-readiness records shall be conflict-reviewed where future enterprise actors may benefit.

**6.5.12.5** The governing rule shall be:

**SPV-readiness records identify conditions for future lawful consideration; they do not authorize the vehicle or project.**

***

### 6.5.13 Nexus Rails Records

**6.5.13.1** The National Investors Council shall maintain Nexus Rail finance-readiness records where matters are proposed, reviewed, routed, deferred, restricted, corrected, or archived through Rail pathways.

**6.5.13.2** Nexus Rail records shall identify source record, proposed route, receiving pathway, routeability status, finance-readiness status, insurance-readiness status, donor relevance, public finance relevance, safeguard conditions, public authority dependencies, unresolved gaps, claims limits, confidentiality class, no-reliance status, Docket status, handoff status, and correction pathway.

**6.5.13.3** Nexus Rail records shall not imply Rail execution, finance approval, insurance approval, donor approval, public finance approval, procurement status, certification, consent, handoff completion, or execution authority.

**6.5.13.4** Rail records shall identify whether a route is proposed, candidate, deferred, restricted, blocked, Docketed, corrected, superseded, archived, or renewed.

**6.5.13.5** The governing rule shall be:

**Rail records show possible routeability; they do not execute routes.**

***

### 6.5.14 AEP Passport Finance-Layer Records

**6.5.14.1** The National Investors Council shall maintain AEP Passport finance-layer records where finance-readiness inputs are contributed to AEP Passport candidate pathways.

**6.5.14.2** AEP Passport finance-layer records may include capital-readable evidence needs, finance-readiness dependencies, insurance-readiness questions, donor relevance, public finance relevance, diligence gaps, risk allocation questions, safeguard conditions, public authority dependencies, SPV-readiness conditions, Docket issues, Rail routeability, and handoff limitations.

**6.5.14.3** AEP Passport finance-layer records shall not imply AEP Passport issuance, certification, Nexus-ready status, financeability, bankability, insurability, public authority approval, procurement status, consent, project approval, or execution readiness.

**6.5.14.4** Such records shall be labelled as candidate finance-layer inputs and shall remain subject to competent AEP Passport process authority.

**6.5.14.5** The governing rule shall be:

**AEP Passport finance-layer records contribute readiness intelligence; they do not issue or validate Passport status.**

***

### 6.5.15 Correction Records

**6.5.15.1** The National Investors Council shall maintain correction records for all material corrections affecting participation, role classification, conflicts, no-reliance acknowledgments, finance-readiness records, capital-readability records, insurance-readiness records, public finance relevance records, donor and philanthropic relevance records, diligence-gap records, SPV-readiness records, Nexus Rail records, AEP Passport finance-layer records, public-safe communications, Nexus Universe materials, National Model materials, Docket items, handoff notes, and archive records.

**6.5.15.2** Correction records shall identify the original error, affected record, correction made, reason for correction, date, approving or correcting authority, affected participants, affected claims, publication implications, confidentiality implications, safeguard implications, public authority implications, finance implications, donor implications, insurance implications, public finance implications, and whether public or controlled clarification is required.

**6.5.15.3** Correction records may support claim narrowing, role reclassification, publication reclassification, public clarification, controlled clarification, withdrawal, restriction, suspension, supersession, archive, or reinstatement.

**6.5.15.4** Correction records shall preserve enough history to prevent the corrected error from re-emerging as current claim.

**6.5.15.5** The governing rule shall be:

**Correction records are the memory of the Council’s discipline; without them, finance-facing errors return as reliance.**

### Summary

Procedure turns Council functions into governed practice. It defines how the Council convenes, records, corrects, escalates, and protects no-reliance discipline across finance-readiness work.

These rules also protect boundaries between public-good record work, [Nexus Rails](/organization/organization/architecture/ii.-definitions/xv.-nexus-rails.md), [Nexus Universe](/organization/cooperation/nexus-universe.md), and any later enterprise, funding, or project pathway. Procedure keeps the Council inside governance, not execution.

### Next steps

1. [Continue to VII. READINESS](/organization/cooperation/consortiums/gateways/national-councils/investors/vii.-readiness.md)
2. [Review V. FUNCTIONS](/organization/cooperation/consortiums/gateways/national-councils/investors/v.-functions.md)
3. [Return to 0. Context](/organization/cooperation/consortiums/gateways/national-councils/investors/0.-context.md)


---

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