# XXI. INDEPENDENCE

### 21. Conflicts, Anti-Capture, and Independence

### 21.1 Federation Conflict Principles

#### 21.1.1 Actual Conflict

**21.1.1.1** An **Actual Conflict** shall exist where a person, institution, sponsor, provider, capital actor, public authority participant, media participant, community participant, Indigenous participant where applicable, National Consortium Company, Project SPV, founder, board member, council participant, helix participant, Working Group participant, Competence Cell participant, partner, host, anchor, contributor, adviser, or downstream recipient has a present interest, duty, relationship, role, expectation, financial interest, institutional interest, contractual interest, procurement interest, policy interest, project interest, provider interest, sponsor interest, public authority interest, community-representation interest, protected knowledge interest, or enterprise-stack interest that directly conflicts with the proper performance of a Nexus public-good role.

**21.1.1.2** An Actual Conflict shall include, without limitation, a situation in which a participant is positioned to influence a record, claim, room, agenda, public-safe report, AEP Passport candidate, Nexus Rail candidate, Docket item, Grid input, safeguard condition, handoff-readiness record, sponsor listing, provider listing, public authority reference, finance-readiness note, National Model, Regional Cluster Program Plan, Nexus Universe output, National Consortium Company interface, or Project SPV interface in a manner that may improperly benefit that participant or an affiliated interest.

**21.1.1.3** Actual Conflicts shall be treated as record conditions, not personal accusations. The existence of an Actual Conflict shall not by itself disqualify participation, but it shall require disclosure, classification, management, recusal, restriction, independent review, correction, suspension, or non-renewal where necessary to preserve public-good integrity.

**21.1.1.4** Actual Conflicts shall be assessed according to the role being performed and the record being affected. A person may participate in one capacity while being restricted from another capacity where the conflict affects only a specific pathway, decision, record, room, output, handoff, or claim.

**21.1.1.5** Actual Conflicts shall be subject to heightened review where they involve sponsor influence, provider validation, capital signaling, public authority approval, procurement advantage, community or Indigenous consent overclaim, protected knowledge use, public-safe reporting, enterprise handoff, National Consortium Company activity, Project SPV activity, or Nexus Universe visibility.

**21.1.1.6** A person or institution with an Actual Conflict shall not participate in the relevant decision, classification, public-safe claim, correction, handoff, or record approval unless the conflict has been expressly managed and recorded.

**21.1.1.7** Actual Conflict records shall be correctionable. If an Actual Conflict is undisclosed, misclassified, unmanaged, understated, used to distort a record, used to influence a pathway, or discovered after a claim or output has been made, the affected role, access, record, claim, report, handoff, or archive entry shall be corrected, restricted, suspended, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.1.2 Potential Conflict

**21.1.2.1** A **Potential Conflict** shall exist where a person, institution, sponsor, provider, capital actor, public authority participant, media participant, community participant, Indigenous participant where applicable, National Consortium Company, Project SPV, founder, board member, council participant, helix participant, Working Group participant, Competence Cell participant, partner, host, anchor, contributor, adviser, or downstream recipient has an interest, relationship, opportunity, dependency, future role, expected benefit, prospective contract, prospective finance relationship, prospective provider relationship, prospective public authority relationship, prospective handoff role, or other circumstance that may reasonably develop into an Actual Conflict.

**21.1.2.2** Potential Conflicts shall be disclosed and recorded before they become Actual Conflicts where they may affect public-good records, Nexus Universe participation, sponsor or partner roles, provider-neutrality, public authority learning, finance-readiness, safeguards, public-safe reporting, AEP Passport or Nexus Rail routing, Docket or Grid classification, handoff-readiness, National Consortium Company interface, or Project SPV interface.

**21.1.2.3** A Potential Conflict may arise where a participant expects to seek sponsorship, provider status, investment opportunity, insurance role, donor role, development finance role, public authority engagement, procurement role, Company role, SPV role, consulting role, advisory role, media advantage, data access, protected knowledge access, community legitimacy, or public-stage visibility from a Nexus-related pathway.

**21.1.2.4** Potential Conflicts shall be managed proportionately. Management may include monitoring, disclosure, access limits, recusal from future decisions, separation from certain records, sponsor or provider limitations, no-reliance notices, public authority capacity clarification, safeguard restrictions, or delayed participation in a pathway.

**21.1.2.5** Potential Conflicts shall not be ignored merely because no improper act has occurred. The Federation shall prevent foreseeable capture and role collapse before harm occurs.

**21.1.2.6** Potential Conflicts shall be reviewed at renewal, role change, sponsorship change, provider status change, public authority role change, finance-readiness escalation, handoff preparation, Nexus Universe participation, or enterprise-stack interface.

**21.1.2.7** Potential Conflict records shall be correctionable. If a Potential Conflict becomes actual, was understated, was omitted, or affects a prior record or claim, the relevant role, access, record, claim, report, handoff, or archive entry shall be corrected, restricted, suspended, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.1.3 Perceived Conflict

**21.1.3.1** A **Perceived Conflict** shall exist where a reasonable observer, acting with knowledge of the relevant facts and Nexus role-separation principles, could reasonably believe that a person, institution, sponsor, provider, capital actor, public authority participant, media participant, community participant, Indigenous participant where applicable, founder, board member, council participant, helix participant, Working Group participant, Competence Cell participant, partner, host, anchor, contributor, adviser, National Consortium Company, Project SPV, or downstream recipient may have compromised independence, neutrality, public-good purpose, safeguard integrity, claims discipline, or correctionability, even if no Actual Conflict is proven.

**21.1.3.2** Perceived Conflicts shall be managed because public-good legitimacy depends not only on the absence of improper influence but also on the visible preservation of independence, neutrality, role separation, non-execution, and anti-capture discipline.

**21.1.3.3** Perceived Conflicts may arise from sponsor prominence, provider prominence, public authority proximity, capital-reader visibility, founder influence, host control, media amplification, family or professional relationships, repeated role overlap, public-stage positioning, National Consortium Company involvement, Project SPV involvement, or public claims that imply endorsement, approval, financeability, provider validation, consent, or execution.

**21.1.3.4** The management of a Perceived Conflict may include controlled disclosure, claim narrowing, public-safe clarification, recusal, role separation, independent review, public listing adjustment, sponsor or provider limitation, room access restriction, handoff restriction, or correction of public materials.

**21.1.3.5** Perceived Conflicts shall receive heightened attention in public-facing contexts, including Nexus Universe stages, public-safe reports, sponsor materials, provider materials, investor materials, public authority materials, media materials, websites, decks, National Model summaries, Regional Cluster Program Plan summaries, AEP Passport references, Nexus Rail references, Docket or Grid summaries, and handoff materials.

**21.1.3.6** A Perceived Conflict shall not be dismissed solely because the participant acted in good faith. The question shall be whether the record, role, claim, or output can remain trusted without clarification, restriction, or correction.

**21.1.3.7** Perceived Conflict records shall be correctionable. If perception risk is underestimated, creates reliance, damages public-good trust, suggests capture, or affects claims discipline, the relevant role, access, record, claim, report, listing, handoff, or archive entry shall be corrected, restricted, clarified, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.1.4 Institutional Conflict

**21.1.4.1** An **Institutional Conflict** shall exist where an institution’s public-good role, enterprise role, sponsor role, provider role, public authority role, capital role, insurer role, donor role, development actor role, media role, community role, Indigenous role where applicable, host role, National Consortium Company role, Project SPV role, or downstream project role may conflict with its duties, limitations, neutrality, independence, or claims discipline within the Federation.

**21.1.4.2** Institutional Conflicts may arise where an institution participates simultaneously as sponsor and provider, host and decision-influencer, capital reader and project proponent, public authority learner and funder, university and certifier by implication, media contributor and sponsor, community-facing actor and project proponent, National Consortium Company participant and public-good record contributor, or Project SPV participant and handoff-readiness reviewer.

**21.1.4.3** Institutional Conflicts shall be recorded at the institutional level and shall not be treated as resolved merely because individual representatives change. The institutional interest, market position, public authority relationship, finance relationship, provider relationship, sponsor relationship, or downstream role shall remain relevant until corrected, restricted, expired, or superseded.

**21.1.4.4** Institutional Conflicts shall be managed through role separation, separate records, access restrictions, public claims limits, recusal of representatives, independent review, sponsor support-without-control conditions, provider-neutrality conditions, finance no-reliance conditions, public authority capacity notices, safeguard restrictions, and handoff limitations.

**21.1.4.5** Institutional Conflicts shall receive heightened review where the institution has significant market power, public authority influence, capital influence, media reach, technical platform control, host control, data access, protected knowledge access, or regional or national dominance.

**21.1.4.6** Institutional Conflicts shall not be used to exclude valuable participation where the conflict can be managed without compromising public-good integrity. However, where the conflict cannot be managed, participation shall be denied, restricted, suspended, non-renewed, terminated, or archived.

**21.1.4.7** Institutional Conflict records shall be correctionable. If an institution’s role is misclassified, undisclosed, unmanaged, used to influence public-good records, used to create procurement advantage, used to create finance signaling, used to imply public authority approval, used to imply provider validation, used to imply consent, or used to imply execution, the relevant role, record, claim, report, handoff, or archive entry shall be corrected, restricted, suspended, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.1.5 Sponsor Conflict

**21.1.5.1** A **Sponsor Conflict** shall exist where a sponsor, anchor, host, funder, in-kind supporter, program supporter, Nexus Universe supporter, council sponsor, helix sponsor, regional sponsor, national sponsor, global sponsor, or affiliated actor has an interest that may influence, appear to influence, or benefit from public-good agenda-setting, participant access, public authority visibility, capital-reader visibility, provider-neutrality, safeguards, public-safe reporting, AEP Passport or Nexus Rail routing, Docket or Grid classification, handoff-readiness, National Consortium Company interface, or Project SPV interface.

**21.1.5.2** Sponsor Conflicts shall be presumed heightened where the sponsor is also a provider, investor, insurer, donor, development actor, public finance actor, public authority participant, media actor, host, technical platform, National Consortium Company participant, Project SPV participant, project proponent, or downstream handoff recipient.

**21.1.5.3** Sponsor support shall never convert into control. A Sponsor Conflict shall be managed to prevent pay-to-approve, pay-to-certify, pay-to-rank, pay-to-access-public-authority, pay-to-access-capital-readers, pay-to-validate-provider, pay-to-influence-safeguards, pay-to-create-handoff, pay-to-enter-AEP-Passport, pay-to-enter-Nexus-Rail, pay-to-resolve-Docket, pay-to-pass-Grid, or pay-to-execute structures.

**21.1.5.4** Sponsor Conflicts shall be disclosed, recorded, and attached to sponsor records, public-safe listing records, Nexus Universe records, claims records, public-safe reporting records, and handoff records where relevant.

**21.1.5.5** A sponsor shall not control public-good records, public-safe reports, room access, program architecture, technical outputs, public authority learning, finance-readiness outputs, safeguard outcomes, provider-neutrality, correction, renewal, or archive.

**21.1.5.6** Sponsor communications shall be reviewed to prevent sponsor support from being represented as endorsement, approval, financeability, procurement status, provider validation, consent, project authorization, or execution authority.

**21.1.5.7** Sponsor Conflict records shall be correctionable. If sponsor influence becomes control, creates public authority confusion, creates finance signaling, creates procurement advantage, creates provider validation, weakens safeguards, captures media visibility, implies consent, or creates execution implication, the sponsor role, access, claim, support record, public-safe listing, and affected outputs shall be corrected, restricted, suspended, terminated, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.1.6 Provider Conflict

**21.1.6.1** A **Provider Conflict** shall exist where a provider, vendor, operator, host, platform, manufacturer, integrator, technology actor, infrastructure actor, consultant, professional firm, public-good software contributor, technical partner, provider candidate, or enterprise participant has an interest that may influence, appear to influence, or benefit from public-good records, technical outputs, provider-neutral capability mapping, procurement-neutrality, public authority learning, finance-readiness, safeguards, AEP Passport or Nexus Rail routing, Docket or Grid classification, handoff-readiness, National Consortium Company interface, Project SPV interface, or Nexus Universe visibility.

**21.1.6.2** Provider Conflicts shall be presumed heightened where the provider is also a sponsor, host, capital actor, public authority contractor, National Consortium Company participant, Project SPV participant, project proponent, downstream handoff recipient, or dominant market actor.

**21.1.6.3** Provider participation shall not become provider validation. A Provider Conflict shall be managed to prevent public-good participation from becoming preferred-provider status, procurement eligibility, procurement award, certification, technical approval, product approval, service approval, financeability, public authority approval, consent, project authorization, Nexus-ready status, AEP Passport status, Nexus Node status, or execution authority.

**21.1.6.4** Provider Conflicts shall be recorded with provider-neutrality conditions, procurement-neutrality conditions, sponsor relationships, public authority relationships, finance relationships, technical contribution scope, public-safe listing permissions, permitted claims, prohibited claims, and correction rights.

**21.1.6.5** A provider shall not influence provider-neutral mapping, technical comparison, public-safe reporting, AEP Passport or Nexus Rail candidate routing, Docket or Grid inputs, handoff-readiness records, or procurement-adjacent materials in a way that privileges its own offering.

**21.1.6.6** Provider demonstrations, technical contributions, Working Group participation, Competence Cell participation, public-good software contributions, or Nexus Universe participation shall be labeled contribution-only unless a separate lawful process creates a different status.

**21.1.6.7** Provider Conflict records shall be correctionable. If provider participation is used as validation, procurement status, financeability, certification, public authority approval, consent, project authorization, Nexus-ready status, AEP Passport status, Nexus Node status, or execution authority, the provider record, claim, listing, report, handoff, and affected downstream materials shall be corrected, restricted, suspended, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.1.7 Capital Conflict

**21.1.7.1** A **Capital Conflict** shall exist where an investor, lender, insurer, reinsurer, donor, development actor, public finance reader, philanthropic actor, infrastructure finance professional, risk-transfer expert, capital reader, National Investors Council participant, GRA-aligned finance-readiness contributor, or finance-adjacent participant has an interest that may influence, appear to influence, or benefit from finance-readiness outputs, capital-readability discussions, insurance-readiness discussions, donor relevance discussions, public finance relevance discussions, SPV-readiness inputs, AEP Passport finance layers, Nexus Rail finance-readiness inputs, Docket or Grid classification, handoff-readiness, National Consortium Company interface, Project SPV interface, or public-safe reporting.

**21.1.7.2** Capital Conflicts shall be presumed heightened where the capital actor is also a sponsor, provider, project proponent, National Consortium Company participant, Project SPV participant, public authority participant, donor decision-maker, public finance actor, insurer, broker, adviser, or downstream transaction participant.

**21.1.7.3** Capital participation shall not become capital control. Capital actors shall not control public-good agenda, records, technical evidence, safeguards, public authority learning, provider-neutrality, public-safe reporting, AEP Passport or Nexus Rail routing, Docket or Grid classification, handoff decisions, Nexus Universe programming, National Model content, or Regional Cluster Program Plan content.

**21.1.7.4** Capital Conflicts shall be managed under no-reliance, non-advisory, non-solicitation, non-placement, non-underwriting, non-rating, non-guarantee, non-transactional, non-fiduciary, and non-executing discipline.

**21.1.7.5** Finance-readiness outputs shall not be shaped to create investment signals, bankability claims, insurability claims, donor approval claims, public finance allocation claims, transaction readiness claims, or project approval claims.

**21.1.7.6** Capital Conflict records shall be attached to relevant capital-reader rooms, National Investors Council records, finance-readiness notes, Nexus Universe records, AEP Passport finance layers, Nexus Rail finance-readiness inputs, Docket or Grid items, handoff records, and public-safe reports.

**21.1.7.7** Capital Conflict records shall be correctionable. If capital participation creates finance signaling, implies financeability, suppresses safeguards, influences provider selection, creates public authority confusion, implies insurance or donor approval, or creates execution implication, the finance-readiness record, claim, access, listing, report, handoff, and affected materials shall be corrected, restricted, suspended, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.1.8 Public Authority Role Conflict

**21.1.8.1** A **Public Authority Role Conflict** shall exist where a public authority, public official, former public official, public-sector employee, regulator, procurement learner, public finance reader, municipal or subnational actor, public enterprise, infrastructure authority, emergency management participant, public health participant, Indigenous or Tribal public-governance participant where applicable, or public authority-adjacent participant engages in Nexus in a way that may be confused with official action, endorsement, approval, regulatory comfort, procurement status, public finance allocation, public warning, project authorization, or execution.

**21.1.8.2** Public Authority Role Conflicts may arise where a participant simultaneously acts as a learner, policymaker, funder, regulator, procurement actor, public finance actor, sponsor, host, project proponent, National Consortium Company participant, Project SPV participant, or downstream approver.

**21.1.8.3** Public authority participation shall be capacity-classified. Each record shall identify whether the participant appears in personal capacity, observer capacity, learning capacity, institutional capacity, official capacity, advisory capacity, public authority decision capacity, or another recorded capacity.

**21.1.8.4** Public Authority Role Conflicts shall be managed to prevent public authority capture of the public-good stack and to prevent the public-good stack from appearing to substitute for public authority action.

**21.1.8.5** Public authority names, titles, logos, seals, photographs, quotations, official affiliations, attendance, email domains, meeting participation, Nexus Universe presence, public authority room participation, Government Portfolio showcase materials, AEP Passport public authority layers, Nexus Rail public authority dependencies, Docket inputs, Grid inputs, and public-safe reports shall not be used to imply official approval unless separately and lawfully recorded.

**21.1.8.6** Where a public authority participant has a role in a later approval, procurement, public finance, regulatory, permitting, emergency, public warning, or project process, Nexus participation shall be structured to avoid improper influence, premature reliance, or procedural unfairness.

**21.1.8.7** Public Authority Role Conflict records shall be correctionable. If public authority participation is used as endorsement, regulatory comfort, procurement status, public finance allocation, data authorization, public warning, project authorization, or execution authority, the relevant record, claim, report, public-safe listing, room record, handoff, and downstream materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.1.9 Community Representation Conflict

**21.1.9.1** A **Community Representation Conflict** shall exist where a person, institution, civil society actor, community actor, Indigenous actor where applicable, diaspora actor, youth actor, accessibility advocate, protected knowledge holder, local institution, public-interest contributor, traditional authority, project proponent, sponsor, provider, public authority participant, media actor, or intermediary is presented, or may be understood, as representing a community, Indigenous people, rights-holder group, diaspora group, youth group, vulnerable group, place, or public-interest constituency without a clear and lawful record of represented capacity.

**21.1.9.2** Community Representation Conflicts may arise where an individual participant is treated as speaking for all affected communities, where a civil society organization is treated as consent-granting, where an Indigenous participant is treated as satisfying FPIC or consultation, where a diaspora participant is treated as local authority, where a youth participant is treated as future-generation consent, or where a project proponent claims community legitimacy through participation.

**21.1.9.3** Community Representation Conflicts shall be managed with heightened care. Participation shall not be converted into representation, endorsement, consent, social license, protected knowledge authorization, land access, cultural approval, environmental approval, local authorization, project approval, or execution authority.

**21.1.9.4** A record involving community or Indigenous participation shall identify participant capacity, represented scope if any, limitations, confidentiality obligations, protected knowledge restrictions, public-safe listing permissions, consent-boundary language, withdrawal rights, correction rights, and handoff restrictions.

**21.1.9.5** Where represented authority is unclear, claims shall be narrowed to “participant,” “contributor,” “safeguard contributor,” “community input,” “public-interest input,” or other approved wording that does not imply representation or consent.

**21.1.9.6** Community Representation Conflicts shall be reviewed before public-safe reporting, Nexus Universe visibility, sponsor or provider materials, finance-readiness materials, public authority materials, handoff records, National Consortium Company materials, and Project SPV materials.

**21.1.9.7** Community Representation Conflict records shall be correctionable. If participation is misrepresented as representation, consent, approval, social license, protected knowledge authorization, or project authorization, the relevant record, claim, report, public-safe listing, handoff, and downstream materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.1.10 Regional and National Conflict

**21.1.10.1** A **Regional and National Conflict** shall exist where a regional pathway, Regional Headquarters Consortium, regional sponsor, regional partner, regional host, global participant, national participant, National Nexus Consortium, National Consortium Company, Project SPV, public authority participant, sponsor, provider, capital actor, community actor, Indigenous actor where applicable, or other participant has a role or interest that may create national bypass, regional supremacy, country misclassification, regional capture, national capture, cross-border overclaim, or improper routing of records.

**21.1.10.2** Regional and National Conflicts may arise where a Regional Headquarters Consortium attempts to speak for a country, where a regional sponsor influences country activation, where a country host is presented as regional sovereign lead, where a national pathway claims regional status without record, where a global claim overrides national conditions, where a National Consortium Company uses national records as public authority approval, or where a Project SPV treats public-good records as project authorization.

**21.1.10.3** Regional and National Conflicts shall be managed by preserving national gateway discipline, regional support without supremacy, global coordination without supremacy, country source records, cross-layer safeguard conditions, claims limits, and correctionability.

**21.1.10.4** Regional records shall not override national source records. Global records shall not override regional or national source records. National records shall not claim public authority approval or community consent unless separately and lawfully recorded.

**21.1.10.5** Country coverage, regional Top-Three status, G7 activation, G20 expansion, regional threshold status, global threshold status, and Nexus Universe participation shall not be used to create official country endorsement, regional authority, global authority, financeability, procurement status, certification, provider validation, consent, project authorization, or execution.

**21.1.10.6** Regional and National Conflicts shall be reviewed during Regional Cluster Program Plan preparation, National Model preparation, Nexus Universe delegation, public-safe reporting, AEP Passport and Nexus Rail routing, Docket and Grid classification, handoff-readiness, National Consortium Company interface, and Project SPV interface.

**21.1.10.7** Regional and National Conflict records shall be correctionable. If national gateways are bypassed, regional status is overstated, country activation is inflated, global synthesis erases national limits, public authority approval is implied, financeability is implied, provider validation is implied, consent is implied, or execution is suggested, the relevant records, claims, reports, handoffs, and archive entries shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

### 21.2 Anti-Capture Rules

#### 21.2.1 No Global Capture

**21.2.1.1** **No Global Capture** shall mean that the Global Nexus Consortium, global Federation agenda, common rail, Nexus Universe global architecture, Global Nexus Core, Global AEP Passport and Nexus Rail coordination, Global Docket and Grid comparability, Global Public-Safe Reporting, Global Claims Register, Global Correction Register, and global handoff-readiness pathways shall not be controlled, dominated, redirected, or materially distorted by any founder, sponsor, provider, public authority, capital actor, insurer, donor, development actor, media actor, region, country, host, platform, technical actor, National Consortium Company, Project SPV, community actor, Indigenous actor where applicable, or enterprise-stack participant.

**21.2.1.2** Global coordination shall remain public-good, role-separated, non-executing, record-based, safeguard-bound, correctionable, and resistant to private, institutional, public authority, capital, provider, sponsor, media, regional, or founder control.

**21.2.1.3** No person or institution shall use global visibility, global sponsorship, global hosting, global technical contribution, global capital-reader participation, global public authority participation, global public-stage presence, global media presence, or Global Nexus Universe participation to claim global authority, approval, endorsement, financeability, certification, provider validation, consent, project authorization, or execution.

**21.2.1.4** Global capture indicators shall include agenda dominance, sponsor-driven priorities, provider-driven technical outputs, capital-driven handoff pressure, public authority overclaim, media legitimacy capture, regional or country bypass, founder control, recurring conflicts, public-safe reporting distortion, claims register manipulation, correction suppression, or safeguard weakening.

**21.2.1.5** Global anti-capture controls may include role separation, board or stewardship independence, conflict disclosure, recusal, access limits, sponsor caps or restrictions where applicable, provider-neutrality controls, public authority capacity controls, no-reliance controls, safeguard review, independent review, claims review, correction authority, and non-renewal.

**21.2.1.6** Global public-good records shall not be edited, delayed, suppressed, elevated, or reclassified for improper sponsor, provider, capital, public authority, media, founder, regional, national, or enterprise-stack reasons.

**21.2.1.7** Global capture records shall be correctionable. If global capture is attempted, suspected, perceived, or actual, the relevant role, access, agenda item, record, claim, public-safe report, Nexus Universe material, sponsor or partner status, handoff, or archive entry shall be corrected, restricted, suspended, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.2.2 No Regional Capture

**21.2.2.1** **No Regional Capture** shall mean that a Regional Headquarters Consortium, Regional Cluster Program Plan, regional Nexus Universe pathway, regional country activation pipeline, regional public-safe reporting pathway, regional AEP Passport and Nexus Rail pathway, regional Docket and Grid pathway, regional sponsorship and partnership pathway, and regional handoff-readiness pathway shall not be controlled, dominated, redirected, or materially distorted by a host country, regional host, sponsor, provider, public authority, capital actor, media actor, founder, dominant market actor, regional institution, National Consortium Company, Project SPV, or other enterprise-stack participant.

**21.2.2.2** A Regional Headquarters Consortium shall be a support and translation layer, not a supremacy hub. No regional actor shall use regional status to override national gateways, speak for countries, bind public authorities, select providers, allocate finance, certify systems, grant consent, authorize projects, or execute.

**21.2.2.3** Regional capture indicators shall include host-country dominance, sponsor-driven country activation, provider-driven Regional Cluster Program Plan language, capital-driven handoff pressure, public authority overclaim, national bypass, Top-Three distortion, G7 or G20 overclaim, media narrative capture, safeguard weakening, protected knowledge exposure, and correction suppression.

**21.2.2.4** Regional anti-capture controls may include national gateway review, cross-country balance, cross-helix balance, conflict disclosure, recusal, sponsor restrictions, provider-neutrality controls, public authority capacity controls, finance no-reliance controls, safeguard review, independent review, claims review, correction authority, and non-renewal.

**21.2.2.5** Regional records shall preserve country source records, national limitations, safeguard conditions, public authority boundaries, finance boundaries, procurement-neutrality, provider-neutrality, sponsor restrictions, correction histories, and archive status.

**21.2.2.6** A regional host, sponsor, partner, or public authority participant shall not use regional infrastructure, funding, visibility, platform access, or public-stage presence to control country activation or regional outputs.

**21.2.2.7** Regional capture records shall be correctionable. If regional capture is attempted, suspected, perceived, or actual, the relevant role, access, country classification, Regional Cluster Program Plan element, Nexus Universe material, public-safe report, sponsor or partner status, handoff, or archive entry shall be corrected, restricted, suspended, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.2.3 No National Capture

**21.2.3.1** **No National Capture** shall mean that a National Nexus Consortium, forming national pathway, National Council, National Leadership Council, National Investors Council, Helix Council, National Working Group, Nexus Competence Cell, National Model, national Nexus Universe delegation, national public-safe reporting pathway, AEP Passport or Nexus Rail national candidate pathway, Docket or Grid national pathway, national handoff-readiness pathway, and National Consortium Company interface shall not be controlled, dominated, redirected, or materially distorted by any sponsor, provider, public authority, capital actor, media actor, host, founder, dominant institution, university, community actor, Indigenous actor where applicable, National Consortium Company, Project SPV, or downstream project proponent.

**21.2.3.2** National ownership shall not mean capture by a single national institution. National gateway discipline shall require balanced, recorded, role-separated, cross-helix, safeguard-aware, public-good participation rather than control by a ministry, company, fund, university, sponsor, provider, host, media actor, family office, city, or project proponent.

**21.2.3.3** National capture indicators shall include sponsor control of National Model language, provider control of technical outputs, capital control of finance-readiness outputs, public authority overclaim, government endorsement misuse, council stacking, helix imbalance, Working Group capture, safeguard tokenization, community or Indigenous consent overclaim, National Consortium Company role collapse, Project SPV pressure, and correction suppression.

**21.2.3.4** National anti-capture controls may include cross-helix balance, National Council and Helix Council separation, conflict disclosure, recusal, sponsor restrictions, provider-neutrality controls, public authority capacity controls, finance no-reliance controls, safeguard review, community and Indigenous protocol review where applicable, independent review, claims review, correction authority, and non-renewal.

**21.2.3.5** National records shall distinguish national formation from government approval, public authority learning from public authority action, finance-readiness from financeability, provider contribution from validation, safeguard input from consent, handoff-readiness from execution, and National Consortium Company interface from public-good authority.

**21.2.3.6** National capture controls shall apply especially during National Model drafting, Nexus Universe delegation selection, Government Portfolio showcase preparation, public-safe reporting, AEP Passport and Nexus Rail routing, Docket and Grid input formation, handoff-readiness, National Consortium Company interface, and Project SPV interface.

**21.2.3.7** National capture records shall be correctionable. If national capture is attempted, suspected, perceived, or actual, the relevant role, access, council or helix record, Working Group record, National Model element, Nexus Universe material, public-safe report, sponsor or partner status, handoff, Company interface, SPV interface, or archive entry shall be corrected, restricted, suspended, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.2.4 No Sponsor Capture

**21.2.4.1** **No Sponsor Capture** shall mean that sponsorship, anchoring, hosting, funding, in-kind support, convening support, infrastructure support, technical support, communications support, public-safe reporting support, Nexus Universe support, regional support, national support, council support, helix support, Working Group support, Competence Cell support, or handoff-readiness support shall not permit a sponsor to control public-good agenda, records, outputs, participants, rooms, claims, safeguards, correction, renewal, or handoff.

**21.2.4.2** Sponsor Capture shall be prohibited at global, regional, national, council, helix, Working Group, Competence Cell, Nexus Universe, AEP Passport, Nexus Rail, Docket, Grid, public-safe reporting, handoff, National Consortium Company interface, Project SPV interface, provider, public authority learning, capital-reader, media, and safeguard levels.

**21.2.4.3** Sponsor Capture indicators shall include sponsor-driven agenda setting, sponsor influence over public-safe reports, sponsor control of speaker selection, sponsor control of room access, sponsor influence over public authority or capital-reader access, sponsor influence over provider-neutral mapping, sponsor influence over safeguard treatment, sponsor influence over AEP Passport or Nexus Rail routing, sponsor influence over Docket or Grid classification, sponsor pressure for handoff, sponsor use of Nexus visibility as endorsement, and sponsor suppression of correction.

**21.2.4.4** Sponsor Capture shall be prevented through recorded support-without-control terms, conflict disclosure, influence restrictions, logo and mark-use controls, public-safe listing controls, sponsor-provider conflict review, public authority boundary review, finance no-reliance review, safeguard review, claims review, and correction rights.

**21.2.4.5** Sponsorship shall not buy authority, priority, validation, public authority access, capital-reader access, provider status, certification, AEP Passport status, Nexus Rail status, Docket resolution, Grid maturity approval, handoff approval, community legitimacy, Indigenous consent where applicable, or execution.

**21.2.4.6** Sponsor communications shall be limited to approved claims and shall not imply endorsement of sponsor products, services, projects, investments, technologies, public authority relationships, provider offerings, or downstream roles.

**21.2.4.7** Sponsor Capture records shall be correctionable. If sponsor capture is attempted, suspected, perceived, or actual, the sponsor role, sponsorship record, claims, public-safe listing, Nexus Universe materials, affected outputs, access rights, and handoff pathways shall be corrected, restricted, suspended, terminated, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.2.5 No Provider Capture

**21.2.5.1** **No Provider Capture** shall mean that a provider, vendor, operator, host, platform, manufacturer, integrator, technology actor, infrastructure actor, consultant, professional firm, public-good software contributor, technical partner, or enterprise participant shall not control, dominate, distort, or convert public-good participation into provider validation, provider preference, procurement advantage, technical certification, financeability, public authority approval, project authorization, or execution.

**21.2.5.2** Provider Capture shall be prohibited at global, regional, national, council, helix, Working Group, Competence Cell, Nexus Universe, AEP Passport, Nexus Rail, Docket, Grid, public-safe reporting, handoff, National Consortium Company interface, Project SPV interface, and public authority learning levels.

**21.2.5.3** Provider Capture indicators shall include provider-authored neutral records without review, provider-dominated Working Groups, provider-controlled technical rooms, provider-driven public-safe reporting, provider-sponsor leverage, provider influence over AEP Passport or Nexus Rail routing, provider influence over Docket or Grid classification, provider influence over handoff-readiness, provider visibility used as validation, and provider claims of Nexus approval.

**21.2.5.4** Provider Capture shall be prevented through provider-neutrality, procurement-neutrality, conflict disclosure, technical contribution classification, independent review, sponsor-provider conflict review, public authority boundary review, finance no-reliance review, safeguard review, claims review, correction rights, and downstream procurement separation.

**21.2.5.5** Provider participation shall not become provider qualification. Provider-neutral capability mapping may identify capabilities and dependencies but shall not rank, endorse, validate, recommend, select, approve, certify, or procure providers.

**21.2.5.6** Provider communications shall be limited to approved contribution-only claims unless a separate lawful provider qualification or procurement process creates a different status.

**21.2.5.7** Provider Capture records shall be correctionable. If provider capture is attempted, suspected, perceived, or actual, the provider role, access, technical record, public-safe listing, claim, Nexus Universe material, AEP Passport or Nexus Rail reference, Docket or Grid item, handoff record, and affected downstream materials shall be corrected, restricted, suspended, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.2.6 No Capital Capture

**21.2.6.1** **No Capital Capture** shall mean that capital readers, investors, lenders, insurers, reinsurers, donors, development actors, public finance readers, philanthropic actors, infrastructure finance professionals, risk-transfer experts, National Investors Council participants, GRA-aligned finance-readiness contributors, and finance-adjacent participants shall not control, dominate, distort, or convert public-good records into investment pipelines, financeability claims, insurance approval, donor approval, public finance allocation, transaction readiness, project approval, or execution.

**21.2.6.2** Capital Capture shall be prohibited at global, regional, national, council, helix, Working Group, Competence Cell, Nexus Universe, AEP Passport, Nexus Rail, Docket, Grid, public-safe reporting, handoff, National Consortium Company interface, Project SPV interface, and sponsor levels.

**21.2.6.3** Capital Capture indicators shall include capital-driven agenda setting, finance-readiness outputs shaped for promotion, capital-reader rooms used as transaction rooms, insurance-readiness rooms used as underwriting rooms, donor rooms used as commitment rooms, public finance rooms used as allocation rooms, handoff pressure driven by investment interest, safeguard suppression, provider preference driven by finance actors, and public-safe reports implying financeability.

**21.2.6.4** Capital Capture shall be prevented through no-reliance discipline, conflict disclosure, non-solicitation controls, market-conduct controls, access classification, independent review, public authority boundary review, provider-neutrality review, safeguard review, finance-readiness language review, claims review, and correction rights.

**21.2.6.5** Capital participation shall not create financeability, bankability, insurability, underwriting appetite, donor approval, development finance approval, public finance allocation, capital commitment, transaction readiness, project approval, or execution.

**21.2.6.6** Finance-readiness outputs shall preserve unresolved dependencies and shall not be used as investment materials unless separately and lawfully prepared outside the public-good stack by competent actors.

**21.2.6.7** Capital Capture records shall be correctionable. If capital capture is attempted, suspected, perceived, or actual, the capital-reader role, finance-readiness record, claims, access, room record, public-safe report, handoff record, National Consortium Company material, Project SPV material, and affected downstream materials shall be corrected, restricted, suspended, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.2.7 No Public Authority Capture

**21.2.7.1** **No Public Authority Capture** shall mean that public authorities, public-sector institutions, public officials, regulators, procurement actors, public finance bodies, municipal or subnational actors, infrastructure authorities, emergency management bodies, public health bodies, public enterprises, Indigenous or Tribal public-governance bodies where applicable, or other public-law actors shall not control, dominate, distort, or convert the public-good stack into a public authority, regulatory process, procurement process, public finance process, public warning channel, emergency command pathway, or project approval process.

**21.2.7.2** Public Authority Capture shall be prohibited while preserving lawful public authority learning, dependency mapping, public-safe dashboard review, Government Portfolio awareness, public authority rooms, AEP Passport public authority context layers, Nexus Rail public authority dependency routing, Docket and Grid public authority inputs, correction, and renewal.

**21.2.7.3** Public Authority Capture indicators shall include public authority claims of control over public-good records, public authority pressure to alter public-safe reports, public authority influence over provider-neutrality, public authority influence over finance-readiness outputs, public authority use of Nexus participation as official approval, procurement shortcuts, public finance signaling, public warning confusion, or project authorization implication.

**21.2.7.4** Public Authority Capture shall be prevented through capacity classification, public authority boundary notices, official-action separation, procurement-neutrality, public finance boundary discipline, public warning boundary discipline, conflict disclosure, independent review, claims review, safeguard review, and correction rights.

**21.2.7.5** Public authority participation shall not create government endorsement, regulatory comfort, policy adoption, procurement status, public finance allocation, data authorization, public warning, infrastructure approval, environmental approval, project authorization, or execution.

**21.2.7.6** Public-good bodies shall not act for public authorities unless separately and lawfully authorized, and even then only within the exact recorded authority.

**21.2.7.7** Public Authority Capture records shall be correctionable. If public authority capture is attempted, suspected, perceived, or actual, the public authority role, room record, claim, report, public-safe listing, Nexus Universe material, handoff record, and affected downstream materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.2.8 No Community Tokenization

**21.2.8.1** **No Community Tokenization** shall mean that communities, Indigenous actors where applicable, civil society, rights-aware organizations, diaspora actors, youth actors, accessibility advocates, protected knowledge holders, environmental and social safeguard contributors, humanitarian actors, local institutions, public-interest researchers, and place-based legitimacy contributors shall not be included, displayed, quoted, photographed, summarized, publicly listed, routed, or referenced merely to create apparent legitimacy, consent, diversity, inclusion, public-interest credibility, social license, sponsor credibility, provider credibility, finance credibility, public authority credibility, or project approval.

**21.2.8.2** Community and Indigenous participation shall be structured, non-extractive, permission-based, capacity-classified, safeguard-bound, correctionable, and protected against misuse.

**21.2.8.3** Community Tokenization indicators shall include symbolic participation without record, public-safe listing without permission, use of community presence as endorsement, use of Indigenous participation as consent where applicable, extraction of lived-risk knowledge without safeguards, protected knowledge exposure, sponsor or provider marketing using community imagery, finance materials using community presence as legitimacy, and handoff records implying social license.

**21.2.8.4** Community Tokenization shall be prevented through capacity classification, consent-boundary language, protected knowledge controls, public-safe listing permissions, representation review, safeguard review, public-safe reporting review, sponsor and provider restrictions, handoff restrictions, withdrawal rights, and correction rights.

**21.2.8.5** No person or institution shall be treated as speaking for all affected communities, Indigenous peoples, rights-holders, future generations, diaspora groups, or places unless a separate lawful and protocol-consistent record supports that representation.

**21.2.8.6** Community and Indigenous contributions shall not be used in public materials, AI systems, datasets, dashboards, digital twins, maps, sponsor materials, provider materials, investor materials, public authority materials, handoff packages, National Consortium Company materials, or Project SPV materials beyond the recorded scope.

**21.2.8.7** Community Tokenization records shall be correctionable. If tokenization is attempted, suspected, perceived, or actual, the participant record, public-safe listing, claim, report, media material, sponsor material, provider material, finance material, handoff record, Company material, SPV material, and archive entry shall be corrected, restricted, withdrawn, deleted where required, superseded, publicly clarified where necessary, or archived.

***

#### 21.2.9 No Founder Capture

**21.2.9.1** **No Founder Capture** shall mean that founders, founding institutions, founding sponsors, founding partners, founding board members, founding council members, founding hosts, founding technical contributors, founding capital readers, founding public authority participants, founding media participants, founding regional actors, founding national actors, or founding enterprise-stack participants shall not permanently control, dominate, override, privatize, or distort the Federation, its records, public-good mandate, claims discipline, safeguards, correctionability, Nexus Universe, AEP Passport, Nexus Rail, Docket, Grid, public-safe reporting, handoff pathways, National Consortium Company interfaces, or Project SPV interfaces.

**21.2.9.2** Founding role shall be historically meaningful but not sovereign. A founder may provide vision, continuity, institutional memory, early support, governance formation, technical leadership, legitimacy support, finance-readiness literacy, or convening capacity, but shall not own the public-good stack or convert founding status into unilateral authority.

**21.2.9.3** Founder Capture indicators shall include unilateral agenda control, correction suppression, founder-controlled appointments without checks, founder-controlled claims, founder-controlled sponsor or provider access, founder influence over public-safe reporting, founder control over handoff routing, founder use of Nexus names for private advantage, founder dominance over National Consortium Companies or Project SPVs through public-good status, and founder resistance to succession or renewal.

**21.2.9.4** Founder Capture shall be prevented through stewardship governance, role separation, conflict disclosure, recusal, term and renewal discipline where applicable, independent review, records discipline, claims discipline, safeguard review, correction authority, and institutional separation.

**21.2.9.5** A founder shall not use founding status to imply public authority approval, financeability, provider validation, certification, community consent, Indigenous consent where applicable, project authorization, Nexus-ready status, AEP Passport status, Nexus Node status, or execution authority.

**21.2.9.6** Founder-related communications shall distinguish founding role from current authority, advisory role from control, continuity from ownership, and vision from execution.

**21.2.9.7** Founder Capture records shall be correctionable. If founder capture is attempted, suspected, perceived, or actual, the founder role, governance record, access, claim, sponsor or partner relationship, public-safe report, handoff record, Company interface, SPV interface, and affected materials shall be corrected, restricted, suspended, restructured, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.2.10 No Enterprise-Stack Collapse

**21.2.10.1** **No Enterprise-Stack Collapse** shall mean that National Consortium Companies, Project SPVs, providers, hosts, operators, contractors, investors, insurers, donors, development actors, public finance actors, procurement bodies, public authorities acting in their own lawful capacities, community processes, Indigenous governance processes where applicable, environmental processes, data processes, cyber processes, and project implementers shall remain institutionally, legally, operationally, financially, and claims-separated from the public-good stack.

**21.2.10.2** Enterprise-stack participation shall not convert public-good records into execution records or public-good bodies into executing entities. A National Consortium Company or Project SPV may receive a handoff only within a lawful record and shall not inherit public-good legitimacy, approval, financeability, certification, provider validation, consent, public authority approval, Nexus-ready status, AEP Passport status, Nexus Node status, or execution authority by default.

**21.2.10.3** Enterprise-Stack Collapse indicators shall include Company claims of public-good authority, SPV claims of Nexus approval, provider claims of Nexus validation, sponsor influence over handoff, capital-reader pressure for transaction framing, public authority confusion over official status, public-safe reports used as investment materials, safeguard records stripped from enterprise documents, or handoff treated as project authorization.

**21.2.10.4** Enterprise-Stack Collapse shall be prevented through lawful handoff triggers, Handoff Readiness Records, source-record limitations, non-execution language, non-agency language, no-shared-liability language, finance boundary language, procurement-neutrality language, provider-neutrality language, public authority boundary language, safeguard attachment, correction rights, and archive linkage.

**21.2.10.5** Enterprise actors shall maintain their own governance, diligence, finance, procurement, provider, public authority, safeguard, data, cyber, contract, project, insurance, accounting, tax, correction, and archive records.

**21.2.10.6** Dual-role participants shall be conflict-managed, and no person shall use a public-good role to secure enterprise advantage or an enterprise role to control public-good records.

**21.2.10.7** Enterprise-Stack Collapse records shall be correctionable. If enterprise roles collapse into public-good roles, public-good records are used as approvals, safeguards are stripped, finance or procurement reliance is created, consent is implied, public authority approval is implied, or execution authority is suggested, the relevant records, claims, handoffs, Company materials, SPV materials, and archive entries shall be corrected, restricted, suspended, withdrawn, superseded, publicly clarified where necessary, or archived.

***

### 21.3 Conflict Management

#### 21.3.1 Disclosure

**21.3.1.1** **Disclosure** shall be the first mandatory step in conflict management. Each participant, sponsor, provider, partner, host, anchor, contributor, council member, helix member, Working Group participant, Competence Cell participant, public authority learner, capital reader, media contributor, community contributor, Indigenous contributor where applicable, National Consortium Company participant, Project SPV participant, founder, adviser, and downstream recipient shall disclose actual, potential, and perceived conflicts relevant to the role, record, room, claim, output, handoff, or pathway in which they participate.

**21.3.1.2** Disclosure shall include, as applicable, financial interests, institutional roles, employment or advisory roles, public authority roles, provider roles, sponsor roles, capital roles, insurance roles, donor roles, development roles, public finance roles, media roles, community representation claims, Indigenous representation claims where applicable, family or professional relationships, project interests, procurement interests, National Consortium Company roles, Project SPV roles, data interests, protected knowledge interests, and downstream handoff interests.

**21.3.1.3** Disclosure shall be made before participation where reasonably foreseeable, promptly upon learning of a new conflict, before entering a new role, before Nexus Universe participation where relevant, before public-safe reporting, before AEP Passport or Nexus Rail routing, before Docket or Grid classification, before handoff, and before renewal.

**21.3.1.4** Disclosure shall be recorded in the applicable conflict register, participation register, sponsor and partner register, council register, helix register, Working Group register, Nexus Universe register, public-safe reporting register, handoff record, Company interface record, or SPV interface record.

**21.3.1.5** Disclosure shall be sufficiently specific to allow classification and management. Generic statements of interest shall not be sufficient where a reasonable reviewer requires detail to determine role separation, access, recusal, restriction, public-safe language, or correction needs.

**21.3.1.6** Failure to disclose may result in restriction, recusal, suspension, termination, non-renewal, correction of affected records, withdrawal of claims, public-safe clarification where necessary, and archive notation.

**21.3.1.7** Disclosure records shall be correctionable. If a disclosure is incomplete, inaccurate, outdated, misleading, or later found insufficient, the disclosure and affected records shall be corrected, restricted, reclassified, suspended, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.3.2 Classification

**21.3.2.1** **Classification** shall mean the formal categorization of a disclosed or discovered conflict as actual, potential, perceived, institutional, sponsor-related, provider-related, capital-related, public authority-related, community representation-related, Indigenous representation-related where applicable, regional, national, enterprise-stack, data-related, protected knowledge-related, public-safe reporting-related, handoff-related, or other relevant conflict type.

**21.3.2.2** Classification shall identify the affected role, record, room, pathway, claim, output, decision, participant, geography, layer, term, sensitivity class, public-safe status, required controls, correction history, and renewal date.

**21.3.2.3** Classification shall also identify severity, including low, managed, heightened, restricted, unmanageable, urgent, or disqualifying, according to risk of capture, public authority confusion, finance reliance, procurement advantage, provider validation, certification drift, consent overclaim, protected knowledge exposure, public warning confusion, handoff misuse, role collapse, or execution implication.

**21.3.2.4** Classification shall be recorded before a participant with a known conflict influences affected records, rooms, public-safe claims, AEP Passport or Nexus Rail routing, Docket or Grid classification, handoff-readiness, National Consortium Company interface, or Project SPV interface.

**21.3.2.5** Conflict classification shall be reviewed at renewal, role change, sponsorship change, provider status change, public authority role change, finance-readiness escalation, public-safe publication, Nexus Universe participation, handoff preparation, or enterprise-stack interface.

**21.3.2.6** Where uncertainty exists, the conflict shall be classified at the more restrictive level pending review.

**21.3.2.7** Conflict Classification records shall be correctionable. If classification is incomplete, understated, overstated, wrong, outdated, or fails to manage risk, the classification and affected records shall be corrected, restricted, reclassified, suspended, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.3.3 Recusal

**21.3.3.1** **Recusal** shall mean the temporary or permanent exclusion of a conflicted person or institution from participating in a specific discussion, room, classification, decision, record drafting, claims approval, public-safe reporting review, safeguard review, AEP Passport or Nexus Rail routing, Docket or Grid classification, handoff-readiness determination, Company interface, SPV interface, correction decision, renewal decision, or archive decision.

**21.3.3.2** Recusal shall be required where participation by the conflicted person or institution could reasonably compromise independence, neutrality, public-good purpose, safeguard integrity, provider-neutrality, procurement-neutrality, finance no-reliance, public authority boundary discipline, claims discipline, correctionability, or non-execution.

**21.3.3.3** Recusal may be full, partial, topic-specific, role-specific, record-specific, room-specific, pathway-specific, time-limited, renewal-linked, or permanent.

**21.3.3.4** Recusal shall be recorded, including the conflict, affected matter, recusal scope, duration, substitute reviewer or decision pathway, access restrictions, permitted participation if any, and correction pathway.

**21.3.3.5** A recused person or institution shall not indirectly influence the affected matter through staff, affiliates, sponsors, providers, public authority contacts, capital contacts, media contacts, community contacts, Indigenous contacts where applicable, National Consortium Company contacts, Project SPV contacts, or informal communications.

**21.3.3.6** Recusal shall not be treated as wrongdoing. It shall be an integrity mechanism to preserve public-good trust.

**21.3.3.7** Recusal records shall be correctionable. If recusal is insufficient, breached, excessive, improperly omitted, or later found unnecessary, the recusal record and affected records shall be corrected, restricted, reclassified, suspended, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.3.4 Restriction

**21.3.4.1** **Restriction** shall mean the limitation of a participant’s access, role, claims, public-safe listing, room participation, record contribution, sponsor visibility, provider visibility, public authority reference, capital-reader participation, safeguard access, protected knowledge access, Nexus Universe access, AEP Passport or Nexus Rail access, Docket or Grid access, handoff access, Company interface access, SPV interface access, or publication rights due to conflict, capture risk, confidentiality risk, safeguard risk, public-safe risk, role-collapse risk, or execution implication.

**21.3.4.2** Restriction may be imposed where disclosure and recusal are insufficient to manage the conflict or where the risk requires preventive control before harm occurs.

**21.3.4.3** Restriction may include access limitation, document limitation, room exclusion, claim limitation, public listing limitation, sponsor visibility limitation, provider visibility limitation, finance-room limitation, public authority-room limitation, safeguard-room limitation, protected knowledge restriction, public-safe reporting restriction, handoff restriction, mark-use restriction, or non-renewal condition.

**21.3.4.4** Restriction shall be proportionate to risk, but shall err on the side of public-good integrity where ambiguity may create public authority confusion, finance reliance, procurement advantage, provider validation, consent overclaim, protected knowledge exposure, public warning confusion, or execution implication.

**21.3.4.5** Restricted participants shall not use restriction as evidence of approval, special access, confidential endorsement, financeability, provider status, public authority proximity, or handoff priority.

**21.3.4.6** Restriction shall be recorded with reasons, scope, duration, review date, correction pathway, renewal conditions, and archive status.

**21.3.4.7** Restriction records shall be correctionable. If restriction is insufficient, excessive, breached, misclassified, outdated, or used as a misleading claim, the restriction record and affected records shall be corrected, restricted further, relaxed where appropriate, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.3.5 Role Separation

**21.3.5.1** **Role Separation** shall be the conflict-management requirement that each person and institution act only within the role, capacity, layer, pathway, authority, and record under which they are participating, and that public-good roles, enterprise roles, public authority roles, finance roles, provider roles, sponsor roles, media roles, community roles, Indigenous roles where applicable, National Consortium Company roles, Project SPV roles, and downstream execution roles remain distinct.

**21.3.5.2** Role Separation shall apply even where the same person or institution lawfully holds multiple roles. A person may be a public-good participant in one context, an enterprise actor in another, a public authority participant in another, and a sponsor or provider in another, but shall not collapse those roles.

**21.3.5.3** Role Separation shall require separate records, separate claims, separate decision pathways, separate access controls, separate conflicts management, separate public-safe language, separate handoff conditions, and separate correction pathways.

**21.3.5.4** A person or institution shall not use a public-good role to secure enterprise advantage, a sponsor role to influence public-good outputs, a provider role to obtain validation, a capital role to influence handoff, a public authority role to imply approval, a community or Indigenous role to imply consent, a media role to create legitimacy capture, or a founder role to override governance.

**21.3.5.5** Role Separation shall be documented in participation records, sponsor and partner records, public authority learner records, capital-reader records, safeguard records, National Consortium Company interface records, Project SPV interface records, and handoff records where relevant.

**21.3.5.6** Public communications shall identify role distinctions where a reasonable reader could confuse them.

**21.3.5.7** Role Separation records shall be correctionable. If roles collapse, are ambiguously described, are used to create reliance, or are used to imply approval, financeability, provider validation, consent, public authority action, or execution, the relevant records, claims, access rights, reports, handoffs, and archive entries shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.3.6 Independent Review

**21.3.6.1** **Independent Review** shall mean review by a person, committee, board, steward, reviewer, counsel, technical reviewer, safeguard reviewer, public-safe reporting reviewer, finance-boundary reviewer, public authority boundary reviewer, or other competent reviewer who is sufficiently independent from the conflict, sponsor interest, provider interest, capital interest, public authority interest, community representation issue, Indigenous protocol issue where applicable, enterprise-stack interest, or handoff recipient to assess the matter fairly.

**21.3.6.2** Independent Review shall be required where a conflict is heightened, disputed, recurrent, public-facing, handoff-related, sponsor-related, provider-related, capital-related, public authority-related, community or Indigenous-related, protected knowledge-related, Nexus Universe-related, AEP Passport or Nexus Rail-related, Docket or Grid-related, National Consortium Company-related, Project SPV-related, or likely to affect public trust.

**21.3.6.3** Independent Review may assess disclosure sufficiency, classification, recusal, restriction, role separation, claims language, public-safe reporting, safeguard handling, data handling, public authority boundary language, finance no-reliance language, provider-neutrality, sponsor support-without-control, handoff readiness, correction adequacy, suspension, reinstatement, and archive treatment.

**21.3.6.4** Independent Review shall be recorded with reviewer capacity, independence basis, materials reviewed, limitations, findings, required controls, correction requirements, renewal conditions, and archive status.

**21.3.6.5** Independent Review shall not convert the reviewer into an approver beyond the scope of the review. Review of a conflict shall not create public authority approval, financeability, provider validation, certification, consent, project authorization, or execution.

**21.3.6.6** Where no sufficiently independent internal reviewer is available, the matter shall be restricted, deferred, externally reviewed where appropriate, or withheld from public-safe reporting or handoff until adequate review is available.

**21.3.6.7** Independent Review records shall be correctionable. If a review is incomplete, conflicted, outdated, unsafe, or fails to identify material risk, the review and affected records shall be corrected, restricted, superseded, publicly clarified where necessary, or archived.

***

#### 21.3.7 Public or Controlled Disclosure Where Appropriate

**21.3.7.1** **Public or Controlled Disclosure Where Appropriate** shall mean that a conflict, limitation, role distinction, sponsor relationship, provider relationship, capital relationship, public authority capacity, community representation limitation, Indigenous protocol limitation where applicable, enterprise-stack role, handoff limitation, or correction may be disclosed to the relevant audience where disclosure is necessary to prevent reliance, preserve trust, protect safeguards, manage conflicts, or correct public misunderstanding.

**21.3.7.2** Disclosure may be public, public-safe, controlled, restricted, confidential, recipient-specific, room-specific, record-specific, or internal depending on sensitivity, legal duties, public-safe reporting requirements, reliance risk, harm risk, protected knowledge risk, public authority sensitivity, finance sensitivity, provider sensitivity, sponsor sensitivity, community sensitivity, Indigenous sensitivity where applicable, and confidentiality obligations.

**21.3.7.3** Public or Controlled Disclosure shall not expose confidential or sensitive information merely to prove conflict management. Where disclosure of details would create harm, a public-safe limitation statement may be used.

**21.3.7.4** Disclosure shall identify what is relevant to the audience: the existence of a limitation, the role boundary, the recusal, the restriction, the non-endorsement condition, the no-reliance condition, the consent-boundary condition, the public authority capacity condition, or the handoff limitation.

**21.3.7.5** Disclosure shall not create new overclaims. A statement that a conflict has been managed shall not imply approval, certification, financeability, provider validation, public authority approval, consent, project authorization, or execution.

**21.3.7.6** Disclosure decisions shall be recorded with audience, content, sensitivity class, publication class, rationale, approval, correction pathway, and archive status.

**21.3.7.7** Public or Controlled Disclosure records shall be correctionable. If disclosure is incomplete, excessive, unsafe, misleading, or publicized beyond permission, the disclosure and affected materials shall be corrected, restricted, withdrawn, superseded, publicly clarified where necessary, or archived.

***

#### 21.3.8 Correction

**21.3.8.1** **Correction** shall be the mandatory response where a conflict, capture risk, role collapse, public-safe reporting error, claims error, sponsor influence, provider influence, capital influence, public authority overclaim, community representation error, Indigenous protocol error where applicable, protected knowledge issue, national-bypass issue, regional-supremacy issue, enterprise-stack collapse, or handoff misuse has affected or may affect a Nexus-related record, role, output, claim, report, room, pathway, handoff, Company interface, SPV interface, or archive entry.

**21.3.8.2** Correction may include disclosure amendment, classification change, recusal, access restriction, role separation, independent review, claim correction, public-safe clarification, public listing correction, sponsor restriction, provider restriction, capital-reader restriction, public authority reference correction, safeguard reattachment, protected knowledge containment, Nexus Universe material correction, AEP Passport or Nexus Rail reference correction, Docket or Grid correction, handoff correction, Company correction, SPV correction, withdrawal, supersession, non-renewal, or archive notation.

**21.3.8.3** Correction shall be urgent where the conflict creates public authority confusion, finance reliance, procurement advantage, provider validation, certification drift, sponsor capture, capital capture, consent overclaim, protected knowledge exposure, public warning confusion, national bypass, regional supremacy confusion, market confusion, reputational misuse, or execution implication.

**21.3.8.4** Correction may be private, controlled, restricted, public-safe, or public depending on sensitivity, reliance risk, harm risk, confidentiality, protected knowledge, public authority sensitivity, finance sensitivity, provider sensitivity, sponsor sensitivity, community sensitivity, Indigenous sensitivity where applicable, and public-safe reporting requirements.

**21.3.8.5** Correction shall not disclose sensitive information unnecessarily and shall not create new overclaims.

**21.3.8.6** Corrected records shall be linked to source records, claims registers, correction registers, public-safe reporting registers, handoff records, and archive entries as applicable.

**21.3.8.7** Correction records shall themselves be correctionable. If a correction is incomplete, inaccurate, unsafe, not implemented, publicized beyond permission, or fails to correct the underlying conflict or capture risk, the correction record shall be corrected, restricted, superseded, publicly clarified where necessary, or archived.

***

#### 21.3.9 Suspension

**21.3.9.1** **Suspension** shall mean the temporary removal, limitation, or freezing of a person’s or institution’s role, access, public-safe listing, sponsorship, partnership, provider-candidate status, council status, helix status, Working Group role, Competence Cell role, Nexus Universe access, public authority learner status, capital-reader status, media contributor status, safeguard contributor status, AEP Passport or Nexus Rail access, Docket or Grid access, handoff access, Company interface access, SPV interface access, claims permission, or mark-use permission while a conflict, capture risk, safeguard issue, protected knowledge issue, public-safe reporting issue, or role-collapse issue is reviewed or corrected.

**21.3.9.2** Suspension may be imposed where disclosure, classification, recusal, restriction, or role separation is insufficient or where urgent risk requires immediate control.

**21.3.9.3** Suspension triggers may include undisclosed conflict, unmanaged conflict, sponsor capture, provider capture, capital capture, public authority overclaim, community tokenization, Indigenous protocol breach where applicable, protected knowledge exposure, confidentiality breach, public-safe reporting misuse, finance signaling, procurement advantage, provider validation claim, consent overclaim, handoff misuse, repeated claims violations, correction refusal, or execution implication.

**21.3.9.4** Suspension may be full, partial, pathway-specific, record-specific, room-specific, claim-specific, public-safe listing-specific, handoff-specific, time-limited, pending review, or pending correction.

**21.3.9.5** Suspension shall be recorded with reason, scope, effective date, affected records, affected access, required corrective actions, review pathway, reinstatement conditions, public-safe communication decision, and archive status.

**21.3.9.6** Suspension shall not be described publicly as wrongdoing unless a public-safe and lawful basis supports that statement. Public-safe language may describe status as under review, restricted, suspended, withdrawn, corrected, or not currently active, as appropriate.

**21.3.9.7** Suspension records shall be correctionable. If suspension is improper, excessive, insufficient, breached, not implemented, or later superseded, the suspension record and affected materials shall be corrected, restricted, modified, lifted where appropriate, superseded, publicly clarified where necessary, or archived.

***

#### 21.3.10 Reinstatement

**21.3.10.1** **Reinstatement** shall mean the restoration of a previously suspended, restricted, withdrawn, or non-renewed role, access, public-safe listing, sponsorship, partnership, provider-candidate status, council status, helix status, Working Group role, Competence Cell role, Nexus Universe access, public authority learner status, capital-reader status, media contributor status, safeguard contributor status, AEP Passport or Nexus Rail access, Docket or Grid access, handoff access, Company interface access, SPV interface access, claims permission, or mark-use permission after the relevant conflict, capture risk, safeguard issue, protected knowledge issue, public-safe reporting issue, or role-collapse issue has been sufficiently addressed.

**21.3.10.2** Reinstatement shall not be automatic. It shall require a recorded determination that the underlying issue has been corrected, restricted, managed, resolved, superseded, expired, or reduced to an acceptable level, and that reinstatement will not compromise public-good integrity, safeguards, claims discipline, public authority boundaries, finance boundaries, provider-neutrality, sponsor support-without-control, protected knowledge, correctionability, or non-execution.

**21.3.10.3** Reinstatement may be full, partial, conditional, pathway-specific, record-specific, room-specific, claim-specific, public-safe listing-specific, handoff-specific, time-limited, probationary, or renewal-linked.

**21.3.10.4** Reinstatement conditions may include updated disclosure, corrected records, public-safe clarification, recusal, access limits, role separation, independent review, sponsor restrictions, provider-neutrality conditions, finance no-reliance conditions, public authority capacity notices, safeguard restrictions, protected knowledge controls, training or orientation, claims review, correction compliance, and renewal review.

**21.3.10.5** Reinstatement shall not validate past conduct or restore withdrawn claims unless the reinstatement record expressly supports the exact claim. A reinstated participant shall not claim that reinstatement means approval, endorsement, certification, financeability, provider validation, public authority approval, consent, project authorization, or execution.

**21.3.10.6** Public-safe reinstatement language, where needed, shall be limited and shall not disclose sensitive information or create new overclaims.

**21.3.10.7** Reinstatement records shall be correctionable. If reinstatement is premature, incomplete, unsafe, misused, publicized beyond permission, or later undermined by renewed conflict or capture risk, the reinstatement record and affected roles, access, claims, reports, handoffs, and archive entries shall be corrected, restricted, suspended again, withdrawn, superseded, publicly clarified where necessary, or archived.


---

# Agent Instructions: Querying This Documentation

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

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

```
GET https://docs.therisk.global/organization/cooperation/consortiums/charter/xxi.-independence.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.