# XIII. PARTNERS

This page defines how partners support Nexus Acceleration without gaining control.

It covers contributor programs, sponsor and provider boundaries, technical support, contribution records, benchmark controls, anti-capture safeguards, and partner exit.

It keeps partner capacity useful, traceable, and public-good aligned across Nexus Network, Nexus Universe, and National Nodes.

### Summary

* Contributor programs expand capacity without transferring authority.
* Sponsor support remains bounded and cannot shape agenda or outcomes.
* Provider participation stays neutral and cannot create procurement advantage.
* Records, benchmarks, and claims stay controlled, traceable, and correctable.
* Exit, teardown, and anti-capture rules protect continuity and independence.

### Related pages

* [XII. COUNCILS](/organization/acceleration/charter/xii.-councils.md)
* [XIV. FINANCE](/organization/acceleration/charter/xiv.-finance.md)
* [XV. AUTHORITIES](/organization/acceleration/charter/xv.-authorities.md)
* [XVI. SAFEGUARDS](/organization/acceleration/charter/xvi.-safeguards.md)
* [XIX. GOVERNANCE](/organization/acceleration/charter/xix.-governance.md)

### 13.1 Nexus Network Frontier Stack Contributor Program

#### 13.1.1 Primary Definition of the Nexus Network Frontier Stack Contributor Program

13.1.1.1 Nexus Network Frontier Stack Contributor Program means the structured public-good contribution pathway through which partners, sponsors, providers, manufacturers, hyperscalers, telecoms, cloud providers, cybersecurity firms, data platforms, universities, laboratories, infrastructure actors, software contributors, technical experts, build crews, National Nodes, public-interest technical actors, and other qualified contributors may support Nexus Network, Nexus Universe, Nexus Acceleration, National Working Groups, Nexus Competence Cells, Nexus Observatory interfaces, Nexus Rails, and related public-good technical pathways without acquiring control, preference, authority, validation, endorsement, procurement advantage, finance advantage, public authority standing, or execution rights.

13.1.1.2 The Contributor Program shall receive, classify, record, govern, and route contributions of capability, infrastructure, expertise, technical services, compute, cloud, networking, telecom, hardware, cybersecurity, data tooling, AI tooling, simulation tooling, digital twin tooling, observability tooling, secure-room support, data-room support, workflow support, repository support, public-good software support, training support, documentation support, research support, and live operations support.

13.1.1.3 The Contributor Program shall be a public-good stack support mechanism. It shall enable qualified contributors to support evidence production, research production, infrastructure-dependent research, observability, public-safe reporting, readiness translation support, national capacity formation, Nexus Universe temporary stack assembly, and permanent Nexus Network improvement while preserving neutrality, independence, role separation, public-safe claims discipline, anti-capture controls, teardown obligations, correctionability, and no-conversion boundaries.

13.1.1.4 The Contributor Program shall apply to contributions made for Nexus Universe annual cycles, Nexus Core Build, National Nexus Nodes, National Working Groups, Nexus Competence Cells, Nexus Observatory methods, Nexus Rails, public-good software, controlled repositories, public-safe reports, Docket pathways, Grid input pathways where applicable, National Continuation pathways, and post-cycle improvement pathways.

13.1.1.5 Contributor participation shall be conditioned on written or recorded contribution terms, contributor identity verification where appropriate, scope definition, access controls, confidentiality conditions, data boundaries, security conditions, recognition limits, sponsor/provider claims limits, public authority boundary limits, readiness boundary limits, procurement-neutrality terms, teardown obligations, and correction obligations.

13.1.1.6 The Contributor Program shall not be used to create contributor control over Nexus agenda, research selection, public authority learning, public-safe reporting, benchmark interpretation, readiness conclusions, community participation, Indigenous participation where applicable, National Node routing, lawful handoff dependency review, procurement outcomes, finance outcomes, insurance outcomes, donor outcomes, or execution pathways.

13.1.1.7 The Contributor Program exists to convert frontier-stack capability into public-good infrastructure support without converting contribution into authority.

***

#### 13.1.2 Contributor Program as Support Architecture, Not Sponsorship Marketplace

13.1.2.1 The Contributor Program shall be support architecture, not a sponsorship marketplace. It shall not be structured, described, operated, marketed, or interpreted as a conventional sponsorship package, advertising product, vendor showcase, sales channel, procurement pipeline, benchmark validation program, market ranking scheme, preferred-provider scheme, or pay-for-access influence pathway.

13.1.2.2 Contributor participation shall not be sold, granted, or represented as a right to control themes, select researchers, select National Nodes, influence Working Group outputs, influence Competence Cell review, shape public-safe claims, write readiness notes, control public authority rooms, control capital-reader rooms, access restricted data, secure procurement advantage, obtain validation, or influence lawful handoff routing.

13.1.2.3 Recognition of contributors shall be bounded, factual, contribution-specific, public-safe, non-promotional where required, and subject to claims discipline. Recognition may acknowledge that a contributor provided specified support within specified limits; it shall not imply endorsement, certification, preferred status, procurement qualification, market superiority, technical validation, financeability, insurability, public authority approval, community consent, Indigenous consent, deployment authorization, handoff authorization, or execution authority.

13.1.2.4 The Contributor Program shall distinguish support, sponsorship, partnership, technical contribution, infrastructure contribution, research support, public-good software contribution, build-crew support, and venue or host support from commercial promotion, procurement, sales, validation, endorsement, or transaction activity.

13.1.2.5 Contributors shall not use the Contributor Program to promote products, services, platforms, devices, models, infrastructure, funding products, insurance products, consulting services, or implementation offerings in a manner that creates market pressure, procurement implication, provider validation, public authority confusion, or public-good capture.

13.1.2.6 Contributor Program materials shall avoid package language that implies purchased influence, purchased access, purchased legitimacy, exclusive market position, official status, preferred-provider status, or priority over other contributors.

13.1.2.7 The Contributor Program may include contribution levels, contribution categories, technical roles, or recognition categories only where such classifications are factual, recorded, claims-bounded, non-authoritative, and not convertible into approval, preference, procurement, finance, insurance, endorsement, or execution.

13.1.2.8 The Contributor Program is legitimate only if contributors strengthen the public-good stack without being able to purchase control over it.

***

#### 13.1.3 Contributor Program Within Nexus Ecosystem

13.1.3.1 The Contributor Program shall operate within Nexus Ecosystem as a bounded public-good infrastructure support pathway serving Nexus Network, Nexus Universe, Nexus Acceleration, National Nexus Nodes, Regional Cluster Programs, National Working Groups, Nexus Competence Cells, GCRI technical and evidence pathways, The Global Risks Forum (GRF) public-safe and claims pathways, The Global Risks Alliance (GRA) readiness pathways, Nexus Observatory interfaces, Nexus Rails, Docket pathways, Grid input pathways where applicable, public-good repositories, and National Continuation pathways.

13.1.3.2 Within Nexus Network, the Contributor Program may support permanent network capacity, technical learning, contributor records, public-good software, observability interfaces, method improvements, repository improvements, security improvements, National Node capacity, and post-cycle improvements.

13.1.3.3 Within Nexus Universe, the Contributor Program may support the annual temporary frontier stack, Nexus Core Build, Live Week operations, secure rooms, controlled rooms, compute-to-data environments, data rooms, public authority learning rooms, readiness rooms, observability dashboards, technical desks, build crews, research workflows, public-safe reporting, and post-cycle teardown.

13.1.3.4 Within Nexus Acceleration, the Contributor Program may support the production, review, routing, correction, and continuation of Acceleration Objects, evidence records, public-safe reports, readiness notes, safeguard records, Docket items, National Continuation Records, and lawful handoff dependency records without controlling their outcomes.

13.1.3.5 Within National Nexus Nodes, contributor support shall respect national ownership, national routing, national safeguards, public authority boundaries, community safeguards, Indigenous safeguards where applicable, data sovereignty, national legal conditions, provider-neutrality, procurement neutrality, and National Continuation discipline.

13.1.3.6 Within National Working Groups and Nexus Competence Cells, contributor support may provide expertise, infrastructure, tools, data environments, technical mentoring, documentation, or review support, but shall not control mandates, outputs, review conclusions, public-safe language, readiness conclusions, routing, or continuation decisions.

13.1.3.7 Within the GCRI, GRF, and GRA triad, contributor interactions shall preserve role separation. GCRI may support evidence, methods, observability, public-good software, and technical baselines. GRF may support public-safe reporting, registry discipline, claims boundaries, stakeholder legitimacy, and public notice. GRA may support readiness readability, diligence-gap framing, no-reliance room discipline, and lawful handoff dependency mapping. Contributors shall not collapse these functions.

13.1.3.8 The Contributor Program is an interface across Nexus Ecosystem, but it shall not become a parallel authority over Nexus Ecosystem.

***

#### 13.1.4 Contributor Program and Annual Nexus Universe Build

13.1.4.1 The Contributor Program shall support the annual Nexus Universe build by helping assemble, test, operate, monitor, secure, document, and tear down the temporary Nexus Universe frontier stack, including compute, cloud, hardware, storage, high-performance networking, telecom, AI, simulation, digital twin, geospatial, cyber, data, observability, secure-room, controlled-room, public-safe reporting, readiness-room, research workflow, and build-crew support.

13.1.4.2 Contributor support may include cloud credits, compute allocations, GPU access, HPC access, edge devices, secure enclaves, confidential computing environments, storage, networking equipment, telecom environments, private wireless, AI-RAN or O-RAN test environments where appropriate, cybersecurity tooling, identity systems, monitoring systems, data platforms, simulation platforms, digital twin tools, Earth observation tools, observability dashboards, repository support, documentation, technical mentoring, and live operations personnel.

13.1.4.3 Each Nexus Universe contribution shall be recorded before use with contributor identity, contribution type, scope, duration, technical dependencies, access rights, data exposure, user permissions, security obligations, public-safe limits, recognition terms, support boundaries, teardown obligations, correction obligations, and prohibited claims.

13.1.4.4 Contributor-provided infrastructure shall be subject to technical review, security review, data boundary review, access control review, workload classification, public-safe classification, and safeguard review as appropriate before use in research workflows, public authority learning rooms, readiness rooms, or public-facing outputs.

13.1.4.5 Contributors shall not control researcher intake, researcher selection, access tiering, scarcity allocation, benchmark interpretation, public-safe reporting, readiness translation, public authority room participation, community participation, Indigenous participation where applicable, Docket routing, ARL status, Nexus Rail routing, National Continuation, or lawful handoff dependency review.

13.1.4.6 Contributor-provided infrastructure shall be used only within the recorded scope and shall be subject to acceptable-use rules, logging, monitoring, access closure, data retention limits, deletion or archive requirements, credential revocation, inventory controls, security incident procedures, and teardown confirmation.

13.1.4.7 Contributor support for Nexus Universe shall not imply that the contributor’s product, service, platform, infrastructure, model, hardware, dataset, or technical method has been validated, certified, approved, preferred, procured, financed, insured, endorsed, or authorized for deployment.

13.1.4.8 The Contributor Program enables Nexus Universe to assemble a serious frontier stack while preventing that stack from becoming a vendor-controlled environment.

***

#### 13.1.5 Contributor Program and Permanent Nexus Network

13.1.5.1 Contributions made through the Contributor Program may strengthen the permanent Nexus Network by generating records, technical lessons, methods, public-good software, observability interfaces, templates, infrastructure patterns, access-control patterns, secure-room patterns, compute-to-data patterns, benchmark boundaries, repository improvements, security improvements, National Node capacity, Competence Cell learning, Working Group learning, and post-cycle improvements.

13.1.5.2 Post-cycle contributor lessons shall be captured in contribution records, technical debriefs, infrastructure performance notes, security notes, access closure records, teardown records, public-safe reporting lessons, readiness-room lessons, National Node feedback, researcher feedback, partner debriefs, and correction logs.

13.1.5.3 Contributor-supported outputs may inform public-good technical baselines, open technical references, APIs, schemas, ontologies, proof objects, public-good repositories, observability methods, research workflow templates, secure-room templates, and Nexus Universe runbooks, subject to IP, licensing, security, data, confidentiality, protected knowledge, and public-safe controls.

13.1.5.4 Contributor-provided tools, methods, code, data, documentation, or infrastructure patterns shall not be incorporated into permanent Nexus Network resources unless rights, licenses, security review, contributor rights, attribution, confidentiality limits, public-good use conditions, non-enclosure principles, and correction obligations are recorded.

13.1.5.5 A contribution to permanent Nexus Network capacity shall not create contributor ownership over Nexus Network, contributor control over future cycles, preferred-provider status, procurement advantage, exclusive access, market status, standards conformance, certification, public authority approval, financeability, insurability, or execution authority.

13.1.5.6 Permanent Nexus Network improvements derived from contributor support shall be documented in a manner that distinguishes contributor contribution from Nexus adoption, evidence support from validation, technical lesson from endorsement, public-good baseline candidate from standard, and repository contribution from certification.

13.1.5.7 The permanent value of contribution is measured by the quality of records, methods, safeguards, software, lessons, and network capacity that remain after contribution-specific control is removed.

***

#### 13.1.6 Contributor Program and Public-Good Stack

13.1.6.1 The Contributor Program shall support the public-good stack by enabling qualified contributions that strengthen evidence, methods, observability, interoperability, public-safe reporting, readiness readability, national capacity, research production, secure infrastructure, public-good software, and lawful routing.

13.1.6.2 Contributor support for the public-good stack shall remain bounded from enterprise-stack entitlement. Contributor participation shall not create commercial entitlement, procurement preference, provider status, project award, National Consortium Company role, Project SPV role, implementation role, investment signal, insurance signal, public finance signal, donor status, public authority approval, or handoff authorization.

13.1.6.3 Contributors may support public-good infrastructure, research workflows, National Node capacity, Nexus Universe build, observability interfaces, public-good software, security controls, secure rooms, data rooms, public-safe reports, readiness-room logistics, and technical documentation, provided that support remains recorded, claims-bounded, non-controlling, public-safe, and correctionable.

13.1.6.4 Public-good stack contribution shall not authorize contributors to use Nexus public-good records for sales, procurement, investment marketing, insurance marketing, benchmark marketing, public authority lobbying, donor solicitation, community consent claims, Indigenous consent claims where applicable, or deployment claims.

13.1.6.5 Contributor support may be acknowledged only within contribution-specific recognition terms. Such acknowledgment shall not be represented as endorsement, certification, validation, approval, preferred status, public authority support, finance-readiness control, insurance approval, donor approval, public finance approval, procurement status, community consent, Indigenous consent, deployment authorization, handoff authorization, or execution authority.

13.1.6.6 Where contributor support may later be relevant to an enterprise-stack opportunity, procurement process, project vehicle, National Consortium Company pathway, Project SPV pathway, or lawful handoff pathway, provider-neutrality, procurement-neutrality, conflict disclosure, separation of records, no-preference language, and independent lawful review shall apply.

13.1.6.7 The public-good stack may receive contribution, but it shall not be captured by contributors.

***

#### 13.1.7 Contributor Program and Record Discipline

13.1.7.1 Every contribution shall be recorded before, during, and after its use through a Contribution Record or equivalent recorded instrument.

13.1.7.2 Each Contribution Record shall identify contributor identity, contributor type, contribution category, contribution description, scope, purpose, duration, location or pathway, supported Nexus body or process, technical dependencies, access rights, user permissions, data exposure, data handling conditions, security obligations, confidentiality conditions, IP and licensing conditions, contributor rights, public-good use terms, recognition terms, support limits, prohibited uses, teardown obligations, correction obligations, and claims boundaries.

13.1.7.3 Contribution categories may include compute, cloud, GPU, HPC, edge, sovereign compute, hardware, storage, networking, telecom, cybersecurity, identity and access management, data platform, AI platform, model tooling, simulation tooling, digital twin tooling, geospatial tooling, Earth observation tooling, observability dashboard, public-good software, repository support, secure room, data room, clean room, confidential computing, technical mentoring, documentation, training, venue or host support, public-safe reporting support, readiness-room support, and build-crew support.

13.1.7.4 Contribution Records shall identify whether the contribution supports Nexus Universe, Nexus Network, Nexus Acceleration, National Nexus Nodes, National Working Groups, Nexus Competence Cells, GCRI pathways, GRF pathways, GRA pathways, Nexus Observatory, Nexus Rails, public-good repositories, Docket processes, Grid input pathways where applicable, public authority learning, readiness rooms, community safeguard pathways, or archive.

13.1.7.5 Contribution Records shall include security classification, data classification, public-safe classification, access classification, risk classification, workload classification where applicable, safeguard status, public authority boundary status, readiness boundary status, and national routing status where applicable.

13.1.7.6 Contribution Records shall identify recognition terms, including permitted name use, logo use if any, factual acknowledgment language, public-safe limits, claim review requirements, prohibited promotional claims, and correction process.

13.1.7.7 Contribution Records shall identify teardown, access closure, credential revocation, data deletion or archive, equipment return, environment closure, log preservation, repository closure, license survival, confidentiality survival, and post-cycle debrief requirements.

13.1.7.8 A contribution without a sufficient Contribution Record shall not be used in controlled research, public authority learning, readiness rooms, sensitive data workflows, secure rooms, public-safe reports, Nexus Universe public materials, or lawful handoff dependency records except under a temporary emergency scoping record approved for limited, controlled, and non-public use.

13.1.7.9 Record Discipline ensures that contribution is traceable, bounded, secure, public-safe, and correctable.

***

#### 13.1.8 Contributor Program and Anti-Capture

13.1.8.1 The Contributor Program shall be governed by Anti-Capture Rules preventing contributors from controlling Nexus agenda, national priorities, research selection, researcher access, infrastructure allocation, benchmark interpretation, public-safe reporting, readiness conclusions, public authority learning, community participation, Indigenous participation where applicable, Working Group outputs, Competence Cell review, National Node routing, Docket status, ARL status, Nexus Rail routing, or lawful handoff dependency review.

13.1.8.2 Contributors shall not condition support on control over public-good outputs, favorable claims, exclusive recognition, provider preference, procurement advantage, benchmark language, public authority access, capital-reader access, community access, Indigenous access where applicable, Docket status, readiness status, National Continuation status, or handoff routing.

13.1.8.3 Sponsor support-without-control shall apply to any contributor providing financial support, in-kind support, venue support, infrastructure support, personnel support, technical support, or public-facing support. Sponsor status shall not create governance rights, agenda rights, research selection rights, public reporting rights, readiness influence, procurement preference, or execution role.

13.1.8.4 Provider contribution-without-validation shall apply to any contributor providing products, platforms, tools, services, models, infrastructure, data, hardware, software, or technical support. Provider contribution shall not validate the provider, validate the product, certify the technology, create market standing, create preferred status, or create procurement qualification.

13.1.8.5 Capital-reader, insurer-reader, donor-reader, and public-finance-reader participation shall not allow contributors to control readiness notes, diligence-gap records, public finance relevance notes, risk-to-capital translation, insurance-readiness question maps, donor-readiness notes, capital-reader room access, or lawful handoff dependency records.

13.1.8.6 Public authority participation or public-sector contribution shall not allow contributors to imply public authority approval, procurement status, funding support, official warning, policy decision, regulatory signal, public finance allocation, or legal authorization.

13.1.8.7 Community, Indigenous, youth, diaspora, accessibility, civil society, or public-interest participation shall not be used by contributors as consent, endorsement, social license, community validation, Indigenous consent, public-interest approval, or marketing legitimacy.

13.1.8.8 Anti-Capture concerns shall be recorded, escalated, reviewed, and corrected through conflict notes, boundary incident records, contribution restriction, claim correction, access limitation, recognition limitation, public-safe clarification, suspension of contribution, termination of contribution, withdrawal of materials, non-continuation, or archive.

13.1.8.9 Anti-Capture Rules ensure that contributor capacity supports Nexus rather than becoming Nexus.

***

#### 13.1.9 Contributor Program Boundary

13.1.9.1 Contributor status, contributor recognition, contribution level, contribution category, partner participation, sponsor participation, provider participation, technical contribution, infrastructure contribution, cloud contribution, compute contribution, telecom contribution, cybersecurity contribution, data contribution, AI contribution, university contribution, public authority-facing contribution, community-facing contribution, readiness-room support, Nexus Universe support, National Node support, Working Group support, Competence Cell support, or public-safe reporting support shall not create endorsement, certification, validation, procurement status, preferred-provider status, investment signal, financeability, insurability, insurance approval, donor commitment, public finance allocation, public authority approval, community consent, Indigenous consent, deployment authorization, project approval, handoff authorization, transaction, or execution authority.

13.1.9.2 A contributor shall not claim that its participation means that Nexus, GCRI, GRF, GRA, a National Nexus Node, a National Council, a Working Group, a Competence Cell, Nexus Universe, Nexus Network, Nexus Acceleration, a public authority, a community, Indigenous actors where applicable, capital readers, insurers, donors, or any other Nexus participant endorses, approves, validates, certifies, prefers, finances, insures, procures, authorizes, or adopts the contributor or its products, services, platforms, tools, methods, personnel, infrastructure, or projects.

13.1.9.3 Contributor-provided resources shall not be used to create unfair access, exclusive technical dependency, hidden vendor lock-in, procurement influence, data capture, public authority influence, benchmark advantage, research-selection influence, readiness influence, or public-safe narrative control.

13.1.9.4 Contributor claims shall be subject to public-safe review and may be restricted, corrected, withdrawn, superseded, clarified, or prohibited where they create overclaim, sponsor misuse, provider misuse, public authority confusion, finance overclaim, insurance overclaim, donor overclaim, procurement overclaim, community consent overclaim, Indigenous consent overclaim where applicable, protected knowledge risk, public-safe risk, or national bypass.

13.1.9.5 Any misuse of contributor status shall be treated as a Boundary Incident and may result in correction, recognition limitation, access restriction, contribution suspension, contribution termination, public clarification where required, restricted circulation, withdrawal, supersession, non-continuation, archive, or exclusion from future contribution pathways.

13.1.9.6 The Contributor Program Boundary preserves the difference between helping build the public-good stack and owning the meaning of what the public-good stack produces.

***

#### 13.1.10 Contributor Program Summary Clause

13.1.10.1 The Contributor Program converts partner capacity into public-good infrastructure support while preserving neutrality, independence, records, boundaries, anti-capture discipline, public-safe claims, national ownership, role separation, teardown discipline, and correctionability.

13.1.10.2 The Nexus Network Frontier Stack Contributor Program is the structured public-good pathway through which partners, sponsors, providers, manufacturers, hyperscalers, telecoms, cloud providers, cybersecurity firms, data platforms, universities, and technical contributors support Nexus Network and Nexus Universe without acquiring control. It is support architecture, not a conventional sponsorship marketplace, advertising package, vendor showcase, procurement channel, sales pipeline, benchmark validation program, or preferred-provider scheme. It operates within Nexus Ecosystem, Nexus Network, Nexus Universe, Nexus Acceleration, National Nexus Nodes, GCRI, GRF, GRA, National Working Groups, and Nexus Competence Cells. It helps assemble the annual temporary Nexus Universe stack, including compute, cloud, hardware, networking, telecom, cyber, data, AI, simulation, observability, secure-room, research workflow, and build-crew support. It may strengthen the permanent Nexus Network through records, technical lessons, methods, public-good software, observability interfaces, National Node capacity, and post-cycle improvements. It supports the public-good stack while remaining bounded from enterprise-stack entitlement, procurement advantage, finance-readiness control, or public authority approval. Every contribution must be recorded with contributor identity, contribution type, scope, duration, conditions, limits, technical dependencies, access rights, recognition terms, teardown obligations, and claims boundaries. Anti-capture rules prevent contributors from controlling agenda, research selection, public claims, benchmark interpretation, readiness conclusions, public authority learning, community participation, or lawful handoff routing. Contributor status does not create endorsement, certification, procurement status, preferred-provider status, investment signal, insurance approval, public authority approval, community consent, or execution authority.

13.1.10.3 No contributor, partner, sponsor, provider, manufacturer, hyperscaler, telecom, cloud provider, cybersecurity firm, data platform, university, technical contributor, infrastructure contributor, build-crew contributor, Contribution Record, contribution category, contribution level, recognition term, public acknowledgment, Nexus Universe support role, Nexus Network support role, National Node support role, Working Group support role, Competence Cell support role, readiness-room support role, public authority learning support role, public-safe reporting support role, Docket support role, Grid input support role where applicable, public-good software contribution, observability interface contribution, repository contribution, post-cycle lesson, debrief record, correction notice, or archive reference shall create certification, validation, recognition, maturity status, governance authority by default, public authority approval, procurement status, preferred-provider status, financeability, bankability, investability, insurability, underwriting acceptance, donor commitment, public finance allocation, official warning, emergency command, community consent, Indigenous consent, standards conformance, deployment authorization, project approval, handoff authorization, transaction, or execution authority by implication.

13.1.10.4 The controlling Contributor Program Formula is that contributors may provide capacity, infrastructure, tools, expertise, support, and lessons; Nexus records define the contribution, Nexus safeguards limit the contribution, Nexus claims discipline bounds recognition, Nexus public-good purpose controls use, Nexus teardown removes contributor control, and Nexus correction repairs misuse; but contribution is not control, support is not sponsorship power, recognition is not endorsement, infrastructure is not validation, benchmark use is not certification, partner presence is not procurement, capital support is not finance, public authority proximity is not approval, community visibility is not consent, and the public-good stack shall remain independent from the actors who help build it.

### 13.2 Partner Categories: Compute, Hardware, Cloud, Network, Telecom, Cyber, Data, AI, Simulation, Digital Twin, Observability, Research Workflow, Secure Room, Travel Support, and Build-Crew Support

#### 13.2.1 Compute and Accelerator Partners

13.2.1.1 Compute and Accelerator Partners mean contributors that provide or support CPUs, GPUs, accelerators, HPC capacity, inference capacity, training capacity, batch compute, edge compute, sovereign compute, secure enclave compute, confidential computing, partner-hosted compute, workload orchestration, runtime support, optimization support, and compute-use documentation for Nexus Network, Nexus Universe, Nexus Acceleration, National Working Groups, Nexus Competence Cells, National Nexus Nodes, research workflows, observability workflows, AI workflows, simulation workflows, and public-good technical pathways.

13.2.1.2 Compute and Accelerator Partner contributions may include cloud-based compute, dedicated hardware, temporary allocations, GPU clusters, accelerator access, edge devices, inference endpoints, research credits, controlled workloads, secure-room compute, compute-to-data environments, monitoring tools, performance logs, technical mentors, and workload support.

13.2.1.3 Each compute contribution shall be governed by recorded allocation, workload classification, user permissions, access duration, logging requirements, monitoring conditions, acceptable-use rules, security controls, data boundary rules, public-safe output controls, retention rules, teardown obligations, and correction pathways.

13.2.1.4 Compute and Accelerator Partners shall not control workload selection, researcher selection, scarcity allocation, benchmark framing, public claims, ARL status, Docket status, readiness translation, public authority learning, National Node routing, Nexus Rail routing, or lawful handoff dependency review.

13.2.1.5 Compute use shall be documented through Compute-Use Records identifying allocation, runtime, workload type, configuration, user access, data sensitivity, infrastructure dependencies, logs, limitations, reproducibility constraints, public-safe restrictions, and access closure.

13.2.1.6 Benchmark or performance outputs generated using contributed compute shall include environment, hardware, software, workload, configuration, data conditions, limitations, reproducibility constraints, and non-generalization language before any claim may be made.

13.2.1.7 Compute contribution shall not validate a model, certify a system, approve a workload, prove performance generally, confer procurement preference, imply financeability, imply insurability, imply public authority approval, or authorize deployment.

13.2.1.8 Compute and Accelerator Partners provide capacity for evidence-bearing work; they do not obtain authority over the evidence produced.

***

#### 13.2.2 Hardware and Infrastructure Partners

13.2.2.1 Hardware and Infrastructure Partners mean contributors that provide or support physical or technical infrastructure for Nexus Network, Nexus Universe, Nexus Acceleration, research production, observability, secure rooms, public-good software pathways, National Node capacity, and temporary frontier-stack operations.

13.2.2.2 Hardware and Infrastructure Partner contributions may include servers, storage systems, racks, edge devices, sensors, telemetry devices, networking hardware, telecom equipment, lab infrastructure, test equipment, power support, cooling support, cabling, device kits, accelerators, embedded systems, safety equipment, and integration support.

13.2.2.3 Hardware contributions shall be recorded with inventory details, ownership status, loan or donation terms, location, custody, access rules, safety conditions, installation requirements, integration dependencies, maintenance obligations, cybersecurity requirements, data exposure risks, insurance or liability conditions where applicable, teardown obligations, return obligations, and archive or disposal requirements.

13.2.2.4 Hardware and Infrastructure Partners shall comply with safety, access, electrical, environmental, security, operational, venue, and public-safe requirements applicable to the contribution.

13.2.2.5 Hardware integration shall not create vendor lock-in, exclusive dependency, hidden control, preferred-provider status, procurement advantage, benchmark advantage, or public authority implication.

13.2.2.6 Sensor, telemetry, edge, telecom, or cyber-physical contributions shall be subject to data classification, privacy, cyber, infrastructure sensitivity, sensitive geospatial, public authority boundary, protected knowledge, community safeguard, and public-safe output controls.

13.2.2.7 Hardware and Infrastructure Partner status shall not certify hardware, validate infrastructure, approve safety, establish standards conformance, create procurement qualification, imply deployment clearance, or authorize operational use.

13.2.2.8 Hardware and Infrastructure Partners contribute the physical substrate of public-good experimentation without acquiring control over Nexus outputs or downstream implementation.

***

#### 13.2.3 Cloud and Platform Partners

13.2.3.1 Cloud and Platform Partners mean contributors that provide cloud credits, managed services, AI platforms, secure cloud environments, data services, container platforms, developer environments, observability tools, workflow services, storage, databases, analytics platforms, monitoring services, identity services, and platform support for Nexus Network, Nexus Universe, Nexus Acceleration, National Nodes, Working Groups, Competence Cells, and research workflows.

13.2.3.2 Cloud and Platform Partner contributions may support compute, storage, AI, analytics, digital twins, simulation, geospatial processing, repository hosting, workflow orchestration, experiment tracking, telemetry, dashboards, secure data rooms, clean rooms, confidential computing, and public-good software development.

13.2.3.3 Cloud and platform contributions shall be recorded with account structure, tenancy model, service scope, access rights, user permissions, data residency, data transfer limits, security controls, logging, monitoring, cost controls, credit limits, usage constraints, API dependencies, retention rules, teardown obligations, and correction pathways.

13.2.3.4 Cloud and Platform Partners shall not receive exclusivity, preferred-provider status, procurement advantage, benchmark control, data ownership by implication, public authority approval by proximity, or public-good stack control.

13.2.3.5 Multi-cloud, hybrid, sovereign, edge, and partner-platform use shall be designed to preserve portability, interoperability, data boundary discipline, security, national ownership, and public-safe output control where practicable.

13.2.3.6 Platform-provided AI, analytics, observability, or workflow tools shall be subject to method documentation, provenance tracking, output review, data handling notes, model or system cards where relevant, and public-safe restrictions.

13.2.3.7 Cloud and Platform Partner contribution shall not certify a platform, validate service performance, create procurement status, approve compliance, establish security certification, or imply that the platform is Nexus-preferred.

13.2.3.8 Cloud and Platform Partners provide technical environments for public-good work without turning Nexus into a platform endorsement channel.

***

#### 13.2.4 Network and Telecom Partners

13.2.4.1 Network and Telecom Partners mean contributors that provide high-speed networking, research network support, routing, monitoring, private wireless, edge connectivity, AI-RAN, O-RAN, degraded-mode communications, emergency-connectivity learning environments, network security support, network operations support, and telecom testbed support for Nexus Network, Nexus Universe, Nexus Acceleration, National Nodes, observability pathways, research workflows, and temporary frontier-stack operations.

13.2.4.2 Network and Telecom Partner contributions may include fiber connectivity, peering support, research network access, Wi-Fi, private 5G, O-RAN test environments, AI-RAN research environments, edge nodes, routers, switches, network monitoring, packet visibility tools, traffic management, low-latency connections, emergency communication simulations, and telecom technical mentoring.

13.2.4.3 Network and telecom contributions shall be recorded with topology, service scope, access permissions, monitoring conditions, data exposure risk, traffic handling limits, security requirements, public authority sensitivity, telecom regulatory boundaries, public-safe limits, teardown obligations, and incident procedures.

13.2.4.4 AI-RAN, O-RAN, private wireless, edge, and degraded-mode communications work shall be treated as research, simulation, observability, resilience learning, or controlled testbed activity unless separately authorized by competent lawful actors.

13.2.4.5 Network and Telecom Partners shall not control research routing, public authority communications, emergency messages, public warning systems, operational telecom services, National Node decisions, public-safe reporting, or lawful handoff routing.

13.2.4.6 Telecom participation shall not create telecom approval, spectrum authorization, operational authorization, public authority approval, emergency communication authority, public safety authority, procurement status, provider validation, deployment clearance, or standards conformance.

13.2.4.7 Network and Telecom Partners strengthen connectivity and degraded-mode learning while preserving that research connectivity is not operational command or public authority infrastructure by default.

***

#### 13.2.5 Cybersecurity and Trust Partners

13.2.5.1 Cybersecurity and Trust Partners mean contributors that provide identity, access management, zero-trust architecture, monitoring, endpoint security, secrets management, vulnerability review, cyber ranges, threat modeling, logging, incident response support, repository security, secure development support, secure-room controls, data-room security, and trust infrastructure support.

13.2.5.2 Cybersecurity and Trust Partner contributions may include identity federation, MFA, privileged access management, secrets scanning, vulnerability scanning, container scanning, endpoint protection, SIEM or logging systems, network segmentation support, key management, cyber range environments, incident response playbooks, secure configuration support, and responsible disclosure workflows.

13.2.5.3 Cybersecurity contributions shall be recorded with scope, systems covered, access permissions, monitoring authority, log access, vulnerability handling terms, disclosure procedures, confidentiality obligations, data exposure risks, incident escalation paths, security limitations, and teardown obligations.

13.2.5.4 Cybersecurity and Trust Partners shall not receive unrestricted access to systems, data, logs, secrets, repositories, public authority-sensitive records, protected knowledge, or participant information except as expressly recorded and authorized.

13.2.5.5 Vulnerability review, cyber range work, penetration-testing support, or incident response support shall be performed only within approved scope, legal authority, access limits, safety controls, responsible disclosure rules, and public-safe reporting boundaries.

13.2.5.6 Cybersecurity and Trust Partner involvement shall not create security certification, compliance approval, risk acceptance, public authority authorization, vendor validation, procurement qualification, insurance approval, or operational clearance.

13.2.5.7 Cybersecurity contributions shall remain correctionable, including through patch records, access closure, credential rotation, vulnerability disclosure, public-safe notice where required, repository correction, release withdrawal, or archive.

13.2.5.8 Cybersecurity and Trust Partners help make Nexus technical work trustworthy without becoming the certifier of that trust.

***

#### 13.2.6 Data, AI, Simulation, Digital Twin, and Observability Partners

13.2.6.1 Data, AI, Simulation, Digital Twin, and Observability Partners mean contributors that provide data platforms, datasets, synthetic data environments, AI systems, model tooling, simulation environments, digital twin platforms, geospatial systems, Earth observation tools, telemetry systems, dashboards, sensor interfaces, analytics tools, signal processing, and observability support.

13.2.6.2 Such Partner contributions may support DRR, DRI, DRF readiness, WEFH-B systems, cascade modeling, infrastructure resilience, early signal learning, degraded-mode awareness, public authority learning, community safeguard review, National Models, Regional Cluster Programs, Nexus Universe research production, and public-safe reporting.

13.2.6.3 Data contributions shall be governed by data rights, permissions, provenance, sensitivity classification, data residency, transfer limits, retention limits, deletion rules, compute-to-data requirements, publication limits, protected knowledge controls, Indigenous data safeguards where applicable, privacy controls, cyber controls, and public-safe review.

13.2.6.4 AI contributions shall be governed by model or system cards where relevant, intended use limits, provenance, prompt or workflow logging where appropriate, human review, output classification, bias and risk review, public authority boundary controls, finance boundary controls, consent boundary controls, dual-use controls, and correction pathways.

13.2.6.5 Simulation and digital twin contributions shall identify assumptions, scope, model limits, input data, scenario conditions, uncertainty, validation limits, reproducibility limits, sensitive-location controls, and prohibited interpretations.

13.2.6.6 Observability contributions shall identify signal sources, telemetry conditions, dashboard limits, classification rules, update cadence, confidence limits where appropriate, public-safe limits, sensitive geospatial controls, and correction triggers.

13.2.6.7 Benchmark outputs or performance comparisons involving contributed data, AI, simulation, digital twin, or observability tools shall include benchmark boundaries and shall not be generalized beyond recorded conditions.

13.2.6.8 Data, AI, Simulation, Digital Twin, and Observability Partner status shall not create dataset endorsement, model approval, AI certification, benchmark validation, public warning authority, surveillance authority, public authority approval, financeability, insurability, procurement status, deployment authorization, or execution authority.

13.2.6.9 These Partners make systems more visible and testable while preserving that visibility, modeling, and intelligence are not approval, certainty, command, or execution.

***

#### 13.2.7 Research Workflow and Repository Partners

13.2.7.1 Research Workflow and Repository Partners mean contributors that provide notebooks, repositories, experiment tracking, artifact storage, model registries, dataset registries, workflow orchestration, collaboration tools, documentation systems, reproducibility tooling, CI/CD support, issue tracking, version control, release management, and research-production infrastructure.

13.2.7.2 Research Workflow and Repository Partner contributions may support research thesis records, experiment plans, method notes, evidence packs, benchmark records, model cards, system cards, compute-use records, data handling notes, reproducibility notes, public-good software releases, public-safe summaries, correction logs, Docket records, and archive records.

13.2.7.3 Workflow and repository contributions shall be recorded with repository scope, access permissions, contributor roles, branch protections, release controls, artifact retention, license terms, IP terms, documentation obligations, security scanning requirements, secrets controls, issue-handling rules, archive requirements, and correction pathways.

13.2.7.4 Public repositories, controlled repositories, restricted repositories, confidential repositories, and archive repositories shall be classified according to public-safe, data, cyber, protected knowledge, IP, public authority, community, Indigenous where applicable, and partner-confidentiality conditions.

13.2.7.5 Workflow tooling shall support provenance, versioning, reproducibility, experiment traceability, artifact custody, method discipline, correction, and archive, but shall not be represented as proof of scientific correctness, validation, certification, or readiness.

13.2.7.6 Repository Partners shall not control public-good software direction, release decisions, public-safe claims, license choices, contributor recognition, benchmark interpretation, or downstream handoff unless separately and lawfully recorded within a bounded role.

13.2.7.7 Research Workflow and Repository Partner status shall not create endorsement, certification, peer-review status, standards conformance, procurement status, provider validation, financeability, insurability, deployment authorization, or execution authority.

13.2.7.8 Research Workflow and Repository Partners strengthen the memory and reproducibility of Nexus work without owning the meaning of the records.

***

#### 13.2.8 Secure Room, Clean Room, and Compute-to-Data Partners

13.2.8.1 Secure Room, Clean Room, and Compute-to-Data Partners mean contributors that provide controlled rooms, secure rooms, clean rooms, confidential computing, no-download environments, data rooms, approved workload systems, controlled collaboration spaces, restricted-output workflows, access logging, output review workflows, and secure enclave support.

13.2.8.2 Such Partner contributions may support sensitive workloads involving public authority data, rights-bearing data, personal data, health-sensitive data, community-sensitive data, Indigenous knowledge where applicable, protected knowledge, cyber-sensitive information, infrastructure-sensitive information, sensitive geospatial information, partner-confidential information, or finance-sensitive information.

13.2.8.3 Secure-room contributions shall be recorded with room type, permitted users, access controls, identity verification, logging, monitoring, data ingress rules, data egress rules, no-download rules, approved workloads, prohibited workloads, output review procedures, retention rules, deletion or archive rules, incident procedures, teardown obligations, and correction pathways.

13.2.8.4 Compute-to-data environments shall be the preferred pathway for sensitive, restricted, sovereign, public authority, protected knowledge, health-sensitive, cyber-sensitive, or community-sensitive datasets where data export would create unacceptable risk.

13.2.8.5 Clean rooms shall apply information controls, audience limits, aggregation rules, output review, market-sensitive information boundaries, competition controls where relevant, and do-not-discuss rules where capital, insurance, donor, provider, public authority, or commercially sensitive information may be present.

13.2.8.6 Secure Room, Clean Room, and Compute-to-Data Partners shall not obtain ownership of data, access to raw data beyond recorded scope, rights to reuse outputs, authority over publication, authority over public authority learning, authority over readiness notes, or control over handoff routing.

13.2.8.7 Secure-room participation shall not create data approval, security certification, compliance approval, public authority approval, financeability, insurability, procurement status, consent, deployment authorization, handoff authorization, or execution authority.

13.2.8.8 Secure Room, Clean Room, and Compute-to-Data Partners make sensitive work possible by keeping the work controlled, logged, reviewed, bounded, and revocable.

***

#### 13.2.9 Travel, Access, Fellowship, and Build-Crew Support Partners

13.2.9.1 Travel, Access, Fellowship, and Build-Crew Support Partners mean contributors that assist with researcher access, participant access, travel support, accommodation support, fellowships, volunteer support, build crew, technical training, logistics, translation, interpretation, accessibility, documentation, onboarding, mentorship logistics, venue support, and participation support.

13.2.9.2 Support Partner contributions may help researchers, students, fellows, public-interest participants, community participants, Indigenous participants where applicable, accessibility participants, youth, diaspora participants, volunteers, technical builders, National Node representatives, Working Group participants, and Competence Cell contributors participate in Nexus Universe, Nexus Network, Nexus Acceleration, National Working Groups, or related public-good pathways.

13.2.9.3 Travel, access, fellowship, and participation support shall be recorded with beneficiary category, selection process, eligibility criteria, support type, amount or in-kind description where appropriate for internal records, duration, conditions, restrictions, conflict controls, safeguarding requirements, accessibility requirements, recognition limits, confidentiality conditions, and correction pathway.

13.2.9.4 Support Partners shall not influence researcher selection, participant selection, fellowship awards, access tiering, research topics, Working Group outputs, public-safe summaries, readiness notes, public authority learning, community participation, Indigenous participation where applicable, Docket status, Nexus Universe outcomes, or lawful handoff routing.

13.2.9.5 Fellowships and access support shall be administered through transparent, recorded, non-discriminatory, safeguard-aware, public-good criteria appropriate to the pathway, without sponsor or provider control over beneficiaries or outputs.

13.2.9.6 Build-crew support shall be assigned by recorded role, training, permissions, access limits, supervision, safety obligations, confidentiality obligations, data boundaries, acceptable-use rules, and teardown responsibilities.

13.2.9.7 Translation, interpretation, accessibility, and participation support shall preserve public-safe language, cultural context, disability access, consent boundaries, protected knowledge controls, and correction pathways.

13.2.9.8 Travel, Access, Fellowship, and Build-Crew Support Partner status shall not create endorsement, selection control, employment, agency, public authority status, procurement status, financeability, insurability, consent, deployment authorization, project approval, handoff authorization, or execution authority.

13.2.9.9 Support Partners expand access to public-good work without purchasing influence over who participates or what the work concludes.

***

#### 13.2.10 Partner Category Summary Clause

13.2.10.1 Partner categories describe capacity contributions, not authority categories. No partner category shall confer control, endorsement, certification, procurement advantage, provider validation, financeability, insurability, public authority approval, consent, deployment authorization, handoff authorization, transaction, or execution authority.

13.2.10.2 Compute and Accelerator Partners contribute GPUs, CPUs, HPC, accelerators, inference capacity, training capacity, edge compute, sovereign compute, secure enclaves, and workload support under access, logging, and no-validation controls. Hardware and Infrastructure Partners contribute servers, storage, racks, devices, edge systems, sensors, lab infrastructure, power or cooling support, hardware integration, inventory, safety, teardown, and return obligations. Cloud and Platform Partners contribute cloud credits, managed services, AI platforms, secure environments, data services, container platforms, observability tools, and developer environments without exclusivity or endorsement. Network and Telecom Partners contribute high-speed networking, private wireless, AI-RAN, O-RAN, edge connectivity, degraded-mode communications, research network support, routing, monitoring, and telecom boundary controls. Cybersecurity and Trust Partners contribute identity, zero trust, monitoring, secrets management, cyber ranges, vulnerability review, endpoint security, incident response support, and secure-room controls without creating security certification. Data, AI, Simulation, Digital Twin, and Observability Partners contribute data platforms, AI systems, simulation environments, digital twins, geospatial systems, Earth observation, telemetry, dashboards, and observability under data rights, public-safe, and benchmark-boundary rules. Research Workflow and Repository Partners contribute notebooks, repositories, experiment tracking, artifact storage, model registries, workflow orchestration, collaboration tools, documentation systems, and reproducibility tooling. Secure Room, Clean Room, and Compute-to-Data Partners contribute controlled rooms, clean rooms, confidential computing, no-download environments, data rooms, approved workload systems, output review workflows, and access logging. Travel, Access, Fellowship, and Build-Crew Support Partners support researcher access, travel, fellowships, volunteers, build crews, training, logistics, translation, accessibility, and participation without influencing selection or outputs.

13.2.10.3 No partner category, partner contribution, partner recognition, compute allocation, hardware provision, cloud credit, platform service, network service, telecom environment, cybersecurity support, data platform, AI system, simulation tool, digital twin environment, observability dashboard, repository system, secure room, clean room, compute-to-data environment, travel support, fellowship support, build-crew support, training support, logistics support, translation support, accessibility support, Contribution Record, public acknowledgment, Nexus Universe support role, Nexus Network support role, National Node support role, Working Group support role, Competence Cell support role, readiness-room support role, public authority learning support role, public-safe reporting support role, correction notice, or archive reference shall create certification, validation, recognition, maturity status, governance authority by default, public authority approval, procurement status, preferred-provider status, financeability, bankability, investability, insurability, underwriting acceptance, donor commitment, public finance allocation, official warning, emergency command, community consent, Indigenous consent, standards conformance, deployment authorization, project approval, handoff authorization, transaction, or execution authority by implication.

13.2.10.4 The controlling Partner Category Formula is that partners may contribute capacity, tools, infrastructure, expertise, access, logistics, and support; Contribution Records define the scope, safeguards define the limits, public-safe review controls the claims, teardown ends temporary control, and correction repairs misuse; but compute is not validation, hardware is not approval, cloud is not endorsement, telecom is not public authority infrastructure, cyber support is not security certification, data and AI are not truth by default, simulation is not prediction, digital twin output is not command, observability is not surveillance, workflow tooling is not peer review, secure rooms are not authorization, travel support is not selection control, build crews are not execution authority, and no partner category shall convert support into control.

### 13.3 Sponsor Support Without Sponsor Control

#### 13.3.1 Sponsor Support Principle

13.3.1.1 Sponsor Support Without Sponsor Control means the principle that sponsor support may strengthen Nexus Acceleration capacity, Nexus Universe operations, National Nexus Node preparation, research access, public-good records, public-safe reporting, accessibility, participation, infrastructure, technical readiness, and post-cycle learning, but shall not control institutional meaning, public-good agenda, research direction, public authority learning, community participation, Indigenous participation where applicable, public claims, readiness translation, routing, correction, or lawful handoff pathways.

13.3.1.2 Sponsor support shall be accepted only where the support is consistent with public-good purpose, role separation, anti-capture discipline, claims discipline, public-safe communication, provider neutrality, procurement neutrality, no-reliance readiness discipline, safeguard protection, national ownership, correctionability, and non-execution.

13.3.1.3 Sponsor support may increase capacity, but capacity shall not become control. Sponsor support may make activities possible, but possibility shall not become agenda ownership. Sponsor support may be acknowledged, but acknowledgment shall not become endorsement. Sponsor support may assist infrastructure, access, or operations, but assistance shall not become approval, validation, procurement advantage, finance signal, public authority status, community consent, Indigenous consent, handoff authorization, or execution authority.

13.3.1.4 Sponsor support shall be governed by written or recorded terms identifying the sponsor, support type, scope, duration, supported pathway, recognition terms, access limits, data limits, public-safe communication limits, conflicts, prohibited claims, teardown or closure obligations where applicable, correction obligations, and consequences of misuse.

13.3.1.5 Sponsorship shall be treated as a support relationship, not a governance relationship, agency relationship, partnership by implication, joint venture by implication, procurement relationship, finance relationship, public authority relationship, certification relationship, or execution relationship.

13.3.1.6 Sponsor support shall be subordinate to Nexus public-good records, Nexus safeguards, National Node routing, GCRI evidence discipline, The Global Risks Forum (GRF) public-safe and claims discipline, The Global Risks Alliance (GRA) readiness discipline, and lawful authority.

13.3.1.7 Sponsor support is legitimate only where the public-good stack remains independent from the sponsor supporting it.

***

#### 13.3.2 Permitted Sponsor Support

13.3.2.1 Permitted Sponsor Support may include funding, in-kind services, equipment, hardware, compute, cloud credits, software access, platform credits, technical mentors, training support, travel support, fellowship support, accessibility support, translation support, venue support, communications support, documentation support, build-crew support, logistics support, public-safe reporting support, secure-room support, data-room support, repository support, and post-cycle debrief support.

13.3.2.2 Funding support may be accepted for public-good operations, researcher access, travel, accessibility, translation, venue logistics, documentation, technical operations, secure rooms, public-safe reporting, National Node preparation, Working Group support, Competence Cell support, Nexus Universe preparation, Nexus Network capacity, or post-cycle learning, provided that the funding is recorded, bounded, conflict-reviewed, claims-reviewed, and non-controlling.

13.3.2.3 In-kind support may include equipment, cloud credits, compute allocations, cybersecurity tools, data platforms, AI tools, simulation environments, digital twin tools, observability dashboards, networking support, telecom support, repository tooling, documentation systems, training content, or technical mentoring, subject to technical review, security review, data review, public-safe review, contribution records, and teardown or access-closure obligations.

13.3.2.4 Travel, fellowship, access, accessibility, translation, and participation support may be used to broaden participation by researchers, students, fellows, public-interest participants, community participants, Indigenous participants where applicable, youth, diaspora, accessibility participants, National Node representatives, Working Group participants, and Competence Cell contributors, but shall not allow the sponsor to select beneficiaries, control participation, direct outputs, or influence research conclusions.

13.3.2.5 Venue, communications, documentation, and public-safe reporting support may be accepted only where editorial control, public claims, public authority references, sponsor references, provider references, community references, Indigenous references where applicable, readiness language, and public-safe summaries remain under the applicable Nexus claims and review processes.

13.3.2.6 Technical mentor, training, and build-crew support may be accepted where roles, permissions, access limits, confidentiality obligations, conflicts, security conditions, data boundaries, acceptable-use rules, and output boundaries are recorded.

13.3.2.7 Permitted Sponsor Support shall not include control over agenda, research selection, researcher access, public authority participation, community participation, Indigenous participation where applicable, technical findings, benchmark interpretation, public-safe reports, readiness notes, routing, correction, Docket status, ARL status, National Continuation, public authority learning, capital-reader rooms, lawful handoff pathways, procurement outcomes, finance outcomes, insurance outcomes, donor outcomes, or execution pathways.

13.3.2.8 Permitted Sponsor Support is support only because its limits are recorded before it is used.

***

#### 13.3.3 Sponsor Control Prohibition

13.3.3.1 Sponsor Control Prohibition means the rule that no sponsor shall control, direct, condition, veto, purchase, require, influence improperly, or dominate Nexus agenda, Nexus Universe themes, National Node priorities, National Council priorities, Helix Council inputs, National Working Group formation, research selection, researcher access, access allocation, technical findings, benchmark interpretation, public authority participation, public authority learning rooms, community participation, Indigenous participation where applicable, safeguard review, public-safe reports, readiness notes, Docket status, ARL status, Nexus Rail routing, correction, public notice, archive, National Continuation, or lawful handoff dependency review.

13.3.3.2 Sponsors shall not condition support on favorable public claims, logo placement beyond approved recognition terms, inclusion in public reports beyond factual acknowledgment, preferential speaking roles, preferred-provider language, benchmark advantage, access to restricted rooms, access to unpublished findings, influence over researcher selection, influence over public authority rooms, influence over community spaces, or influence over readiness translation.

13.3.3.3 Sponsors shall not use support to create procurement advantage, provider preference, market advantage, investment signal, insurance signal, donor signal, public finance signal, public authority implication, community consent implication, Indigenous consent implication where applicable, or project authorization implication.

13.3.3.4 Sponsors shall not direct GCRI evidence review, GRF public-safe review, GRA readiness review, Competence Cell review, National Node routing, Working Group outputs, Nexus Universe outputs, Docket Review, Grid input review where applicable, public authority learning records, safeguard records, readiness notes, or correction records.

13.3.3.5 Sponsors shall not control data access, public-safe release, publication timing, public narrative, media engagement, public authority attendance, capital-reader attendance, community-facing summaries, Indigenous-facing summaries where applicable, or public reports except as expressly permitted within recorded contribution or confidentiality terms and subject to Nexus public-safe review.

13.3.3.6 Sponsors shall not receive exclusivity, first look, right of refusal, preferred access, privileged procurement position, preferred finance position, preferred insurance position, preferred donor position, preferred public authority access, or preferred handoff position by reason of sponsorship.

13.3.3.7 Any attempted sponsor control shall be recorded as a Boundary Incident and may result in access limitation, recognition limitation, contribution restriction, suspension of sponsor status, termination of sponsor status, claim correction, public-safe clarification, withdrawal of acknowledgment, rerouting, archive, or exclusion from future support pathways.

13.3.3.8 Sponsor support may enable the work, but it shall never own the work.

***

#### 13.3.4 Sponsor Recognition Boundaries

13.3.4.1 Sponsor Recognition Boundaries mean the rules governing how sponsors may be acknowledged in public, controlled, internal, Nexus Universe, Nexus Network, National Node, Working Group, Competence Cell, public-safe report, research, repository, media, and post-cycle materials.

13.3.4.2 Sponsor recognition may include factual acknowledgment of the sponsor’s name, contribution category, contribution type, supported pathway, time period, and public-good support role, subject to approved language, contribution records, public-safe classification, claims review, logo-use rules, and correction rights.

13.3.4.3 Sponsor recognition shall not state or imply endorsement, certification, validation, maturity status, preferred-provider status, procurement qualification, procurement preference, investment signal, financeability, insurability, insurance approval, donor approval, public finance approval, public authority approval, official status, standards conformance, research validation, community consent, Indigenous consent where applicable, deployment authorization, handoff authorization, project approval, transaction, or execution authority.

13.3.4.4 Sponsor recognition shall distinguish sponsor support from partner contribution, provider contribution, technical review, public authority participation, research participation, capital-reader participation, community participation, Indigenous participation where applicable, and lawful handoff participation.

13.3.4.5 Sponsor logo use, name use, quotes, announcements, press references, web listings, social media references, event materials, reports, proceedings, repository references, public-safe summaries, and knowledge-base references shall be subject to approved use terms and may be limited, denied, corrected, withdrawn, or archived where overclaim risk exists.

13.3.4.6 Sponsor recognition shall be proportionate to the actual recorded support and shall not create artificial prominence, imply category leadership, suggest exclusivity, imply official status, imply national endorsement, imply Nexus-wide endorsement, or obscure other contributors, public-good actors, communities, or national ownership.

13.3.4.7 Sponsor recognition may be delayed, restricted, anonymized, aggregated, or withheld where recognition could create public-safe risk, procurement risk, market risk, public authority confusion, community harm, Indigenous safeguard concern where applicable, protected knowledge risk, conflict risk, or reputational misinterpretation.

13.3.4.8 Sponsor Recognition Boundaries allow gratitude without selling legitimacy.

***

#### 13.3.5 Sponsor Communications Discipline

13.3.5.1 Sponsor Communications Discipline means the requirement that all sponsor communications concerning Nexus, Nexus Universe, Nexus Network, Nexus Acceleration, National Nexus Nodes, National Councils, Working Groups, Competence Cells, GCRI, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), public authority learning, public-safe reports, readiness rooms, community participation, Indigenous participation where applicable, or supported outputs use approved public-safe language, contribution records, claims boundaries, no-control statements, benchmark limits, public authority disclaimers, readiness disclaimers, consent-boundary disclaimers, and correction obligations.

13.3.5.2 Sponsor communications may include press releases, website statements, social media posts, sponsor pages, public acknowledgments, internal announcements, annual reports, marketing references, case studies, event references, technical blogs, repository references, investor communications, donor communications, public authority-facing communications, and media statements.

13.3.5.3 Sponsor communications shall be reviewed before release where they refer to Nexus names, Nexus institutions, Nexus Universe, Nexus Network, Nexus Acceleration, GCRI, GRF, GRA, National Nodes, public authorities, communities, Indigenous actors where applicable, researchers, outputs, benchmarks, readiness, public-safe reports, public authority rooms, capital-reader rooms, sponsor recognition, or partner contributions.

13.3.5.4 Sponsor communications shall include contribution-specific language and shall not generalize support into endorsement, validation, certification, approval, procurement status, financeability, insurability, donor commitment, public finance allocation, public authority support, community consent, Indigenous consent where applicable, deployment authorization, handoff authorization, project approval, or execution authority.

13.3.5.5 Sponsor communications concerning benchmarks, performance, research outputs, infrastructure use, AI outputs, simulation outputs, digital twin outputs, observability outputs, or technical findings shall include benchmark boundaries, method limits, environment limits, workload limits, data limits, uncertainty, reproducibility constraints, and non-generalization language where relevant.

13.3.5.6 Sponsor communications concerning public authorities shall state that public authority participation is learning unless separately and lawfully recorded by the competent public authority. Sponsor communications concerning capital readers, insurers, donors, or public finance readers shall state that readiness discussion is no-reliance and non-transactional. Sponsor communications concerning communities or Indigenous actors where applicable shall state that participation is not consent.

13.3.5.7 Sponsors shall correct, withdraw, replace, restrict, or publicly clarify communications that are inaccurate, unsafe, overclaiming, misleading, inconsistent with contribution records, inconsistent with public-safe classifications, or inconsistent with no-conversion boundaries.

13.3.5.8 Sponsor Communications Discipline ensures that sponsorship does not convert public-good support into public-good misrepresentation.

***

#### 13.3.6 Sponsor Access Limits

13.3.6.1 Sponsor Access Limits mean the rules governing sponsor access to research rooms, data rooms, secure rooms, clean rooms, compute-to-data environments, public authority rooms, capital-reader rooms, readiness rooms, community spaces, Indigenous spaces where applicable, restricted records, unpublished outputs, public-safe drafts, Working Group materials, Competence Cell materials, Docket materials, Nexus Universe operational spaces, and National Node records.

13.3.6.2 Sponsors may receive access only where access is recorded, role-appropriate, necessary for the support provided, consistent with public-good purpose, compliant with confidentiality and security obligations, consistent with public-safe classification, and approved under applicable data, safeguard, public authority, readiness, national, and access-control rules.

13.3.6.3 Sponsors shall not receive default access to restricted records, raw data, sensitive datasets, protected knowledge, Indigenous knowledge where applicable, public authority-sensitive information, community-sensitive information, health-sensitive information, cyber-sensitive information, sensitive geospatial information, benchmark internals, unpublished findings, researcher deliberations, public-safe review drafts, readiness-room materials, or lawful handoff dependency materials.

13.3.6.4 Sponsors may be excluded from research rooms, data rooms, secure rooms, clean rooms, compute-to-data environments, public authority rooms, capital-reader rooms, community spaces, Indigenous spaces where applicable, or restricted sessions where sponsor presence could create influence risk, public authority confusion, procurement risk, finance overclaim, consent overclaim, protected knowledge risk, confidentiality risk, data risk, cyber risk, or public-safe risk.

13.3.6.5 Sponsor access to capital-reader rooms, insurer-reader rooms, donor-reader rooms, or public finance reader rooms shall be governed by no-reliance, non-advisory, non-soliciting, non-transactional, non-underwriting, non-commitment, non-allocation, competition-compliant, information-controlled, and regulated-perimeter rules.

13.3.6.6 Sponsor access to community or Indigenous spaces, where applicable, shall require heightened safeguard review, purpose limitation, participation protection, consent-boundary language, non-extraction conditions, protected knowledge controls, and correction pathways.

13.3.6.7 Sponsor access may be logged, monitored, limited, suspended, revoked, or conditioned on training, confidentiality, data handling, access acknowledgments, conflict disclosure, no-control acknowledgment, and public-safe communication obligations.

13.3.6.8 Sponsor Access Limits preserve the difference between supporting a space and entering, observing, shaping, or controlling it.

***

#### 13.3.7 Sponsor Conflict Disclosure

13.3.7.1 Sponsor Conflict Disclosure means the requirement that sponsors disclose commercial interests, public procurement interests, provider relationships, vendor interests, investor relationships, insurer relationships, donor relationships, public finance interests, policy interests, regulatory interests, public authority relationships, political interests, data interests, IP interests, research interests, media interests, community-facing interests, and other influence risks relevant to supported work.

13.3.7.2 Sponsor disclosures shall identify the sponsor’s business interests, products, services, platforms, relevant markets, supported pathways, intended contribution, affiliated providers, affiliated investors, affiliated insurers, affiliated donors, affiliated public finance actors, public authority relationships, procurement interests, policy or regulatory interests, funded research relationships, IP interests, and any relationships that could affect interpretation of support.

13.3.7.3 Sponsor disclosures shall be reviewed for agenda capture, provider validation, procurement advantage, benchmark influence, public authority implication, finance overclaim, insurance overclaim, donor overclaim, public finance overclaim, community consent overclaim, Indigenous consent overclaim where applicable, data capture, protected knowledge risk, national bypass, media influence, and public-safe communication risk.

13.3.7.4 Sponsor Conflict Disclosure may result in role limits, access limits, recognition limits, communications review, exclusion from certain rooms, exclusion from Working Group influence, exclusion from readiness-room participation, separation of technical support from review, independent review, recusal of affiliated experts, or decline of support.

13.3.7.5 Sponsors shall update disclosures where interests change, supported pathways change, products or services become relevant to Nexus outputs, procurement processes arise, public authority relationships arise, investment relationships arise, litigation or regulatory issues arise, media campaigns arise, or conflicts become material.

13.3.7.6 Failure to disclose material conflicts may result in correction, sponsor status suspension, sponsor status termination, restricted communications, withdrawal of acknowledgment, public clarification where required, access restriction, rerouting, non-continuation, archive, or exclusion from future support pathways.

13.3.7.7 Sponsor Conflict Disclosure makes influence visible before it becomes capture.

***

#### 13.3.8 Sponsor Misuse and Overclaim

13.3.8.1 Sponsor Misuse and Overclaim means any sponsor statement, omission, communication, logo use, public reference, marketing material, investor communication, public authority communication, donor communication, website entry, social media post, media statement, case study, presentation, sales material, procurement material, benchmark claim, research claim, readiness claim, community claim, Indigenous claim where applicable, or internal communication that misrepresents sponsor status, contribution, Nexus participation, public-good meaning, or supported outputs.

13.3.8.2 Sponsor Misuse may include improper use of Nexus names, unauthorized logo use, false validation claims, implied endorsement, implied certification, implied public authority approval, implied procurement advantage, implied preferred-provider status, implied financeability, implied insurability, implied donor commitment, implied public finance approval, implied community consent, implied Indigenous consent where applicable, benchmark marketing beyond recorded limits, research validation claims, Nexus-ready claims, Nexus-approved claims, public authority implication, readiness implication, or execution implication.

13.3.8.3 Sponsor Overclaim may occur through selective quotation, omission of limitations, removal of no-control language, omission of no-reliance language, omission of public authority disclaimers, omission of consent-boundary language, misuse of participant presence, misuse of public authority attendance, misuse of capital-reader attendance, misuse of community participation, misuse of Indigenous participation where applicable, or misuse of Nexus Universe visibility.

13.3.8.4 Sponsor Misuse may also include attempts to influence agenda, research selection, public-safe reports, readiness notes, public authority learning, community participation, Indigenous participation where applicable, benchmark interpretation, Docket status, ARL status, routing, correction, or handoff pathways in exchange for support.

13.3.8.5 Sponsor Misuse and Overclaim shall be recorded as a Boundary Incident where it creates risk of role collapse, public confusion, public authority confusion, procurement confusion, finance overclaim, insurance overclaim, donor overclaim, public finance overclaim, consent overclaim, protected knowledge risk, national bypass, or public-safe harm.

13.3.8.6 Sponsor Misuse and Overclaim shall not be excused by sponsor importance, contribution size, strategic value, public visibility, media convenience, donor relevance, capital relevance, public authority proximity, or institutional discomfort.

13.3.8.7 Sponsor Misuse and Overclaim shall trigger correction proportionate to risk, including revised language, withdrawal, public clarification, restricted communication, recognition limitation, sponsor suspension, termination, or archive.

13.3.8.8 Sponsor Misuse and Overclaim are integrity events, not branding disputes.

***

#### 13.3.9 Sponsor Correction and Withdrawal

13.3.9.1 Sponsor Correction and Withdrawal means the tools available to correct sponsor overclaim, sponsor misuse, inaccurate communications, unsafe public references, public authority confusion, finance implication, insurance implication, donor implication, procurement implication, consent implication, benchmark misuse, research validation overclaim, public-safe risk, or contribution-boundary breach.

13.3.9.2 Correction tools may include informal correction request, written notice, revised language, required disclaimer, removal of unauthorized logo use, revision of web or social media materials, correction of investor or public authority materials, correction of donor or public finance materials, correction of benchmark claims, correction of public-safe report references, restricted communications, withdrawal of acknowledgment, public clarification, controlled clarification, archive update, suspension of sponsor status, termination of sponsor status, or exclusion from future support pathways.

13.3.9.3 Sponsor correction shall identify the sponsor, communication or conduct at issue, affected records, affected claims, public-safe risk, boundary risk, reliance risk, required corrective action, deadline where applicable, notice audience, responsible steward, and archive status.

13.3.9.4 Withdrawal of acknowledgment may be used where sponsor recognition would continue to create public-safe risk, overclaim risk, procurement risk, public authority confusion, finance or insurance implication, donor or public finance implication, community harm, Indigenous safeguard concern where applicable, protected knowledge risk, or institutional capture risk.

13.3.9.5 Suspension of sponsor status may be used where the sponsor’s conduct requires investigation, correction, restricted access, claims review, conflict review, safeguard review, or boundary review before further participation may continue.

13.3.9.6 Termination of sponsor status may be used where misuse is material, repeated, uncorrected, intentional, unsafe, incompatible with public-good purpose, inconsistent with anti-capture discipline, or harmful to public trust, communities, Indigenous actors where applicable, public authorities, National Nodes, researchers, partners, or Nexus integrity.

13.3.9.7 Public correction shall be considered where sponsor overclaim has been publicly disseminated or could create reliance, public authority confusion, procurement confusion, finance or insurance confusion, community consent confusion, Indigenous consent confusion where applicable, or public-safe harm. Controlled correction may be used where public correction would amplify sensitive information or protected knowledge.

13.3.9.8 Sponsor correction shall not prevent additional remedies available under applicable agreements, policies, law, or institutional instruments.

13.3.9.9 Sponsor Correction and Withdrawal protects the Contributor Program by making sponsor support conditional on truthful, bounded, and correctable participation.

***

#### 13.3.10 Sponsor Support Summary Clause

13.3.10.1 Sponsor support is welcome only when it supports public-good capacity without control, capture, overclaim, procurement advantage, finance implication, public authority confusion, consent implication, or conversion into institutional authority.

13.3.10.2 The Sponsor Support Principle permits sponsor support to strengthen Nexus Acceleration capacity, Nexus Universe operations, National Node preparation, research access, public-good records, and public-safe reporting, but not to control institutional meaning. Permitted Sponsor Support may include funding, in-kind services, equipment, cloud credits, technical mentors, travel support, accessibility support, venue support, communications support, training support, and build-crew support. Sponsor Control Prohibition bars sponsor control over agenda, research selection, researcher access, public authority participation, community participation, technical findings, benchmark interpretation, public-safe reports, readiness notes, routing, correction, or handoff pathways. Sponsor Recognition Boundaries permit public-safe acknowledgment while preventing claims of endorsement, approval, certification, maturity, provider preference, procurement advantage, financeability, insurability, or public authority status. Sponsor Communications Discipline requires approved public-safe language, contribution records, claims boundaries, no-control statements, benchmark limits, public authority disclaimers, and correction obligations. Sponsor Access Limits govern research rooms, data rooms, secure rooms, capital-reader rooms, public authority rooms, community spaces, restricted records, and unpublished outputs. Sponsor Conflict Disclosure requires disclosure of commercial interests, public procurement interests, provider relationships, investor relationships, policy interests, and other influence risks. Sponsor Misuse and Overclaim includes improper use of Nexus names, false validation claims, implied endorsement, benchmark marketing, public authority implication, finance implication, or consent implication. Sponsor Correction and Withdrawal provide notice, revised language, withdrawal of acknowledgment, suspension of sponsor status, restricted communications, public correction, and archive.

13.3.10.3 No sponsor, sponsorship, sponsor recognition, sponsor contribution, sponsor support level, sponsor category, funding support, in-kind support, equipment support, cloud credit, technical mentor support, travel support, accessibility support, venue support, communications support, training support, build-crew support, sponsor statement, sponsor acknowledgment, sponsor access, sponsor room participation, sponsor-supported output, sponsor-supported Nexus Universe activity, sponsor-supported National Node activity, sponsor-supported Working Group activity, sponsor-supported Competence Cell activity, sponsor-supported readiness room, sponsor-supported public authority learning room, sponsor-supported public-safe report, correction notice, withdrawal notice, public clarification, or archive reference shall create certification, validation, recognition, maturity status, governance authority by default, public authority approval, procurement status, preferred-provider status, financeability, bankability, investability, insurability, underwriting acceptance, donor commitment, public finance allocation, official warning, emergency command, community consent, Indigenous consent, standards conformance, deployment authorization, project approval, handoff authorization, transaction, or execution authority by implication.

13.3.10.4 The controlling Sponsor Support Formula is that sponsors may support capacity, but not control meaning; may fund access, but not select outcomes; may provide infrastructure, but not validate themselves; may be recognized, but not endorsed; may support public authority learning, but not create public authority action; may support readiness rooms, but not create finance; may support community participation, but not create consent; may support Nexus Universe, but not own its agenda; and may remain welcome only while support remains bounded, transparent, public-safe, anti-capture, correctionable, and subordinate to the public-good stack.

### 13.4 Provider Contribution Without Provider Preference, Procurement Qualification, Bid Advantage, Validation, Certification, Market Claim, or Implied Eligibility

#### 13.4.1 Provider Contribution Principle

13.4.1.1 Provider Contribution Without Provider Preference means the principle that providers may contribute tools, systems, services, equipment, engineering support, technical mentors, software, infrastructure, data platforms, cloud environments, cybersecurity capabilities, telecom environments, AI tools, simulation systems, digital twin platforms, observability tools, repository systems, workflow tools, secure-room support, and related capacity to Nexus Network, Nexus Universe, Nexus Acceleration, National Nodes, Working Groups, and Competence Cells without gaining preference, validation, certification, procurement qualification, bid advantage, market legitimacy, public authority standing, financeability, insurability, or implied eligibility.

13.4.1.2 Provider contribution shall be accepted only where the contribution is consistent with public-good purpose, provider neutrality, procurement neutrality, role separation, anti-capture discipline, public-safe claims discipline, data and cyber safeguards, sponsor support-without-control where applicable, contribution records, teardown obligations, correctionability, and no-conversion boundaries.

13.4.1.3 Providers may contribute capacity to support evidence production, research workflows, infrastructure-dependent research, public-good software, observability, Nexus Universe temporary stack operations, National Node capability, Working Group production, Competence Cell review, public-safe reporting, readiness readability, and lawful handoff dependency mapping, provided that the provider shall not control the meaning, interpretation, routing, or downstream use of outputs.

13.4.1.4 Provider contribution shall be recorded before use through a Contribution Record or equivalent instrument identifying provider identity, product or service involved, contribution type, scope, duration, technical configuration, supported pathway, access rights, data exposure, IP and licensing conditions, security conditions, conflicts, recognition terms, claims limits, teardown or access-closure obligations, and correction obligations.

13.4.1.5 Provider contribution shall not be represented as Nexus adoption, Nexus endorsement, Nexus approval, GCRI validation, The Global Risks Forum (GRF) recognition, The Global Risks Alliance (GRA) finance-readiness conclusion, public authority acceptance, public procurement qualification, market approval, insurance approval, donor support, National Node approval, community consent, Indigenous consent where applicable, deployment authorization, handoff authorization, or execution authority.

13.4.1.6 Provider contribution may support the public-good stack, but the provider shall not acquire control over the public-good stack, the enterprise stack, the transition between the stacks, or any lawful handoff pathway.

13.4.1.7 The Provider Contribution Principle is that provider capacity may strengthen Nexus Acceleration only where contribution remains bounded, neutral, record-based, claims-safe, and non-authoritative.

***

#### 13.4.2 Provider Neutrality

13.4.2.1 Provider Neutrality means the rule that Nexus Acceleration shall remain neutral among providers, products, platforms, vendors, sponsors, manufacturers, hyperscalers, telecoms, infrastructure actors, software contributors, data platforms, cybersecurity firms, AI providers, cloud providers, hardware suppliers, engineering firms, operators, and other technical or enterprise contributors.

13.4.2.2 Provider Neutrality shall require that no provider be granted or implied to have preferred status, exclusive status, official status, approved status, procurement status, vendor status, Nexus-ready status, standards-conforming status, market-leading status, maturity status, public authority-accepted status, finance-ready status, insurance-ready status, or handoff-ready status by reason of participation or contribution.

13.4.2.3 Provider Neutrality shall apply across Nexus Universe, Nexus Network, Nexus Acceleration, National Nexus Nodes, National Councils, Working Groups, Competence Cells, public authority learning rooms, readiness rooms, capital-reader rooms, public-safe reports, Docket records, Grid input records where applicable, Nexus Rails, National Continuation pathways, and lawful handoff dependency review.

13.4.2.4 Provider Neutrality shall not prevent lawful contribution, technical participation, open collaboration, public-good software support, infrastructure support, research support, or evidence production. It shall prevent such contribution from being converted into preference, validation, procurement advantage, market signal, public authority implication, finance implication, insurance implication, donor implication, or execution implication.

13.4.2.5 Provider Neutrality shall require separation between provider support and review of provider-specific outputs. Where a provider’s tool, system, platform, device, model, service, or infrastructure is the subject of a record, appropriate conflict disclosure, independent review, limitation language, public-safe classification, benchmark controls, and claims restrictions shall apply.

13.4.2.6 Provider Neutrality shall require that public materials distinguish provider contribution from provider approval, provider participation from provider validation, provider-supported research from provider certification, provider infrastructure from procurement preference, and provider technical support from public authority acceptance.

13.4.2.7 Provider Neutrality may require rotation, multi-provider references, non-exclusive language, neutral descriptions, open technical alternatives, independent method notes, configuration disclosure, restricted publication, or public-safe review to prevent misleading provider advantage.

13.4.2.8 Provider Neutrality preserves the public-good character of Nexus Acceleration by preventing technical contribution from becoming market privilege.

***

#### 13.4.3 Procurement Qualification Prohibition

13.4.3.1 Procurement Qualification Prohibition means that provider participation, contribution, technical support, research involvement, Nexus Universe presence, National Node support, Working Group support, Competence Cell support, public authority room attendance, public-safe report mention, readiness-room participation, benchmark participation, repository contribution, or public acknowledgment shall not create procurement qualification, bid advantage, vendor status, eligibility, prequalification, preferred supplier status, purchasing recommendation, government supplier status, or implied procurement readiness.

13.4.3.2 No public authority, National Nexus Node, National Consortium Company, Project SPV, Working Group, Competence Cell, GCRI pathway, GRF pathway, GRA pathway, Nexus Universe pathway, or Nexus Network pathway shall treat provider participation as procurement eligibility unless a separate lawful procurement or contracting process independently establishes such status.

13.4.3.3 Provider participation in public authority learning rooms shall be treated as learning, technical context, or contribution only. It shall not create vendor access rights, procurement influence, procurement recommendation, public authority endorsement, procurement shortlisting, bid advantage, technical acceptance, or purchasing preference.

13.4.3.4 Provider support for National Nodes, Working Groups, Nexus Universe, secure rooms, data rooms, observability dashboards, research workflows, public-safe reports, or readiness rooms shall not be used in procurement materials unless the use is separately authorized, accurately described, public-safe, claims-reviewed, and clearly bounded against procurement implication.

13.4.3.5 Provider participation shall not create eligibility for National Consortium Company work, Project SPV work, public authority programs, public finance programs, donor-funded programs, grant programs, resilience programs, infrastructure programs, or implementation pathways.

13.4.3.6 Any reference to a provider in a procurement-sensitive context shall include appropriate language stating that the reference is not a procurement qualification, recommendation, endorsement, preference, eligibility determination, bid advantage, prequalification, or purchasing decision.

13.4.3.7 Procurement Qualification Prohibition shall be enforced through contribution records, communications review, public-safe review, conflict disclosure, provider-neutrality controls, correction, withdrawal, public clarification where required, restricted circulation, or archive.

13.4.3.8 Procurement Qualification Prohibition ensures that public-good contribution cannot be converted into a shortcut around lawful procurement.

***

#### 13.4.4 Validation and Certification Prohibition

13.4.4.1 Validation and Certification Prohibition means that provider contribution shall not validate, certify, approve, benchmark, rate, rank, endorse, verify, test-approve, safety-approve, security-approve, market-approve, standards-approve, or public-good-approve provider products, systems, services, tools, platforms, models, devices, infrastructure, data, software, methods, or personnel.

13.4.4.2 No provider contribution shall be described as validation unless a separate competent validation process has been lawfully established, completed, recorded, and accurately described. Nexus Acceleration review, GCRI technical review, Competence Cell review, Working Group use, Nexus Universe use, public-safe mention, or public authority learning shall not be represented as validation.

13.4.4.3 No provider contribution shall be described as certification unless a separate competent certification body or lawful process has issued certification within its authority and such certification is accurately identified as external or separate from Nexus Acceleration.

13.4.4.4 Benchmarking, testing, simulation, digital twin use, AI workflow use, cloud use, compute use, telecom use, cyber range use, repository use, or observability use involving provider tools shall not create general proof of performance, safety, compliance, reliability, security, superiority, public authority acceptance, financeability, insurability, or deployment readiness.

13.4.4.5 Nexus records may describe observed results within recorded conditions, but such records shall include method basis, configuration, environment, workload, data conditions, assumptions, limitations, conflicts, reproducibility constraints, public-safe classification, non-generalization language, and prohibited claims.

13.4.4.6 Provider-specific review shall not be performed by conflicted provider personnel as the sole basis for claims of quality, performance, safety, security, or readiness. Where provider personnel contribute technical context, such contribution shall be labeled, conflict-disclosed, and independently reviewed where required.

13.4.4.7 Validation and Certification Prohibition shall apply to all public communications, sponsor communications, provider communications, research outputs, public-safe reports, proceedings, readiness notes, National Node materials, public authority learning materials, and Nexus Universe materials.

13.4.4.8 Validation and Certification Prohibition protects Nexus Acceleration from becoming an implied testing laboratory, certifier, rating body, or endorsement platform.

***

#### 13.4.5 Market Claim Limits

13.4.5.1 Market Claim Limits mean the rules preventing providers from using Nexus participation, contribution, research outputs, public-safe reports, Working Group outputs, Competence Cell review, Nexus Universe presence, National Node support, public authority learning, readiness-room participation, benchmark records, or public acknowledgments as claims of superiority, safety, compliance, validation, public authority acceptance, bankability, insurability, deployment readiness, procurement readiness, preferred status, market approval, or Nexus approval.

13.4.5.2 Providers shall not claim that Nexus use, Nexus testing, Nexus Universe participation, public authority room attendance, research selection, benchmark inclusion, public-safe report mention, Docket entry, ARL status, Grid input, readiness note, or National Continuation pathway proves that a provider product, platform, service, tool, model, or system is superior, safe, compliant, validated, approved, certified, financeable, insurable, procured, deployable, or eligible.

13.4.5.3 Providers shall not use Nexus materials to make comparative marketing claims unless the specific comparative record has been approved for controlled reference, includes all required limitations, identifies test conditions, discloses conflicts, includes non-generalization language, and has passed public-safe and claims review.

13.4.5.4 Providers shall not omit limitations, uncertainty, configuration constraints, data limits, environment limits, reproducibility limits, benchmark boundaries, conflict disclosures, public authority disclaimers, readiness disclaimers, consent-boundary language, or no-conversion statements when referring to Nexus-related outputs.

13.4.5.5 Providers shall not use Nexus participation in investor materials, sales materials, procurement submissions, public authority pitches, insurance submissions, donor materials, public finance materials, media campaigns, or public websites in a manner that implies validation, endorsement, public authority acceptance, procurement advantage, financeability, insurability, donor support, public finance support, or deployment readiness.

13.4.5.6 Market Claim Limits shall apply equally to direct claims, implied claims, visual claims, logo placement, selective quotation, badge use, case studies, customer references, social media posts, conference presentations, technical blogs, benchmark tables, and sales decks.

13.4.5.7 Provider market claims that reference Nexus shall be subject to review, correction, withdrawal, public clarification where required, restricted circulation, suspension of recognition, termination of contribution status, or archive.

13.4.5.8 Market Claim Limits ensure that Nexus public-good work is not transformed into provider advertising.

***

#### 13.4.6 Implied Eligibility Prohibition

13.4.6.1 Implied Eligibility Prohibition means that no contributor, provider, sponsor, partner, manufacturer, hyperscaler, telecom, cloud provider, cybersecurity firm, data platform, AI provider, software contributor, infrastructure actor, university partner, technical contributor, or support partner may imply eligibility for public procurement, Project SPVs, National Consortium Company work, public authority programs, capital-reader interest, insurance approval, donor support, public finance support, implementation pathways, deployment pathways, or lawful handoff pathways by reason of Nexus participation.

13.4.6.2 Nexus participation shall not create eligibility for public authority contracts, grants, pilots, procurements, tenders, concessions, permits, approvals, regulatory programs, infrastructure programs, disaster-risk programs, resilience programs, public finance programs, donor programs, insurance programs, National Consortium Company opportunities, Project SPV opportunities, operator roles, or provider roles.

13.4.6.3 Docket entry, ARL status, Grid input review, Nexus Rail routing, Nexus Universe participation, National Node support, Working Group output, Competence Cell review, public-safe report mention, readiness note, or Handoff Dependency Note shall not be used to imply eligibility for any downstream opportunity.

13.4.6.4 Where a provider later participates in a separate lawful procurement, finance, insurance, donor, public finance, public authority, National Consortium Company, Project SPV, or implementation process, Nexus participation shall be disclosed where relevant and shall not substitute for the independent requirements of that process.

13.4.6.5 Any reference to Nexus participation in eligibility-sensitive materials shall be limited to factual contribution history and shall include clear language that participation does not create eligibility, prequalification, recommendation, approval, preference, financeability, insurability, or authorization.

13.4.6.6 Implied Eligibility Prohibition shall apply regardless of contribution size, sponsor level, technical importance, public visibility, public authority proximity, Nexus Universe prominence, or strategic relevance.

13.4.6.7 Implied Eligibility Prohibition prevents provider contribution from becoming an informal credential for downstream opportunities.

***

#### 13.4.7 Provider-Specific Output Controls

13.4.7.1 Provider-Specific Output Controls shall apply where a Nexus record, Working Group output, Competence Cell review, Nexus Universe output, benchmark record, public-safe report, readiness note, Docket item, ARL status, National Continuation Record, or Routing Note refers to a specific provider product, system, service, tool, platform, model, infrastructure, dataset, device, or method.

13.4.7.2 Provider-specific outputs shall identify the provider, contribution record, product or service involved, configuration, version, environment, workload, data conditions, access conditions, user conditions, test conditions, method basis, evidence basis, limitations, dependencies, conflicts, reviewer boundaries, public-safe classification, access classification, permitted references, prohibited claims, correction pathway, and archive status.

13.4.7.3 Provider-specific outputs shall state whether provider personnel supplied technical context, configuration assistance, engineering support, data support, interpretation support, or review support, and shall disclose the boundary between provider-supplied information and independent Nexus review.

13.4.7.4 Provider-specific outputs shall include non-generalization language stating that results apply only to the recorded conditions and shall not be generalized to other configurations, environments, workloads, datasets, users, jurisdictions, public authority contexts, deployment settings, procurement settings, finance settings, insurance settings, or safety contexts unless separately reviewed.

13.4.7.5 Provider-specific outputs shall not be publicly referenced unless public-safe review, claims review, conflict review, data review, benchmark-boundary review where applicable, provider-neutrality review, and sponsor/provider communications review have confirmed the permitted use.

13.4.7.6 Provider-specific outputs may be controlled, restricted, redacted, delayed, or no-publication where public release could create procurement implication, market advantage, benchmark misuse, public authority confusion, finance overclaim, insurance overclaim, donor overclaim, public finance overclaim, sensitive data exposure, cyber risk, or unfair provider comparison.

13.4.7.7 Provider-specific outputs shall be corrected, withdrawn, superseded, restricted, publicly clarified where required, or archived where configuration, data, method, result, limitation, public-safe status, conflict disclosure, or claims boundary is inaccurate or misleading.

13.4.7.8 Provider-Specific Output Controls allow technical specificity without allowing specificity to become endorsement.

***

#### 13.4.8 Comparative Benchmark Controls

13.4.8.1 Comparative Benchmark Controls shall apply to any Nexus-related benchmark, comparison, performance test, stress test, simulation result, workload comparison, AI evaluation, cloud comparison, compute comparison, telecom comparison, cybersecurity comparison, digital twin comparison, software comparison, or infrastructure comparison involving one or more providers, products, platforms, tools, systems, configurations, models, or services.

13.4.8.2 Comparative benchmarks shall be conducted only where the purpose, methodology, test conditions, workload, data, environment, configuration, version, comparator basis, measurement approach, limitations, uncertainty, reproducibility conditions, conflicts, public-safe classification, and permitted use are recorded before any claim is made.

13.4.8.3 Benchmark records shall identify hardware, software, network conditions, compute conditions, cloud conditions, data conditions, system configuration, model or tool version, run conditions, measurement method, evaluation criteria, failure conditions, excluded variables, reproducibility constraints, and non-generalization boundaries.

13.4.8.4 Benchmark records shall disclose conflicts, including provider involvement, sponsor involvement, contributor involvement, reviewer affiliation, infrastructure dependency, funding connection, technical support connection, data dependency, or other factor that may affect interpretation.

13.4.8.5 Comparative benchmarks shall not be used for unsupported marketing, ranking, ratings, superiority claims, procurement preference, public authority acceptance, financeability, insurability, market approval, safety approval, security certification, or deployment readiness.

13.4.8.6 Public release of comparative benchmark results shall require public-safe review, claims review, provider-neutrality review, conflict review, data review, cybersecurity review where relevant, public authority boundary review where relevant, and legal-interface review where required.

13.4.8.7 Where benchmark outputs are not fit for public use, they may be restricted to internal learning, method improvement, technical debugging, controlled research, Working Group review, Competence Cell review, or archive.

13.4.8.8 Comparative benchmarks shall include non-generalization language stating that results apply only to the recorded configuration, workload, dataset, environment, method, and time, and shall not establish general superiority, safety, reliability, compliance, procurement readiness, financeability, insurability, or deployment readiness.

13.4.8.9 Benchmark misuse shall require correction, withdrawal, public clarification where required, restricted circulation, provider communications correction, status downgrade, supersession, non-continuation, or archive.

13.4.8.10 Comparative Benchmark Controls preserve the value of testing by preventing testing from becoming marketing without discipline.

***

#### 13.4.9 Provider Boundary Incident

13.4.9.1 Provider Boundary Incident means any event, communication, claim, omission, conduct, record use, public statement, procurement reference, market reference, investor reference, insurance reference, donor reference, public finance reference, public authority reference, community reference, Indigenous reference where applicable, benchmark reference, or Nexus status reference that creates risk of provider preference, procurement overclaim, validation overclaim, certification overclaim, benchmark misuse, preferred-provider implication, public authority implication, finance implication, insurance implication, donor implication, public finance implication, consent implication, deployment implication, handoff implication, execution implication, or unauthorized Nexus status use.

13.4.9.2 Provider Boundary Incidents may include claims that a provider is Nexus-approved, Nexus-certified, Nexus-validated, Nexus-ready, preferred by Nexus, recommended by Nexus, selected by public authorities through Nexus, finance-ready through Nexus, insurable through Nexus, procurement-qualified through Nexus, or deployment-ready through Nexus.

13.4.9.3 Provider Boundary Incidents may include misuse of Nexus names, logos, public-safe reports, benchmarks, Working Group outputs, Competence Cell review records, Nexus Universe participation, National Node support, public authority attendance, community participation, Indigenous participation where applicable, readiness-room references, capital-reader presence, or Docket or ARL status.

13.4.9.4 Provider Boundary Incidents shall be recorded with provider identity, affected product or service, affected record, alleged claim or conduct, source, public-safe risk, procurement risk, public authority risk, readiness risk, benchmark risk, consent risk, market risk, national bypass risk, affected stakeholders, required correction, responsible steward, notice requirement, and archive status.

13.4.9.5 Provider Boundary Incidents may require immediate pause of public reference, correction request, revised language, removal of unauthorized materials, restricted communications, withdrawal of acknowledgment, benchmark withdrawal, public clarification where required, access limitation, contribution suspension, contribution termination, rerouting, non-continuation, archive, or exclusion from future provider pathways.

13.4.9.6 Where a Provider Boundary Incident affects public authority materials, procurement materials, investor materials, insurer materials, donor materials, public finance materials, community materials, Indigenous materials where applicable, or public reports, targeted notice or public-safe clarification shall be considered according to reliance risk and public-safe classification.

13.4.9.7 Provider Boundary Incidents shall not be minimized as branding disputes. They are institutional boundary events requiring correction to protect neutrality, public trust, procurement integrity, and Nexus legitimacy.

***

#### 13.4.10 Provider Neutrality Summary Clause

13.4.10.1 Providers may contribute capacity and expertise, but Nexus Acceleration does not convert contribution into preference, validation, procurement eligibility, market legitimacy, financeability, insurability, public authority approval, consent, deployment authorization, handoff authorization, or execution authority.

13.4.10.2 The Provider Contribution Principle allows providers to contribute tools, systems, services, equipment, engineering support, technical mentors, software, infrastructure, and data platforms without gaining preference or validation. Provider Neutrality keeps Nexus Acceleration neutral among providers, products, platforms, vendors, sponsors, manufacturers, hyperscalers, telecoms, and infrastructure actors. Procurement Qualification Prohibition confirms that provider participation, contribution, technical support, research involvement, or Nexus Universe presence does not create procurement qualification, bid advantage, vendor status, eligibility, or purchasing recommendation. Validation and Certification Prohibition confirms that provider contribution does not validate, certify, approve, benchmark, rate, rank, endorse, verify, or market-approve provider products, systems, services, tools, or platforms. Market Claim Limits prevent providers from using Nexus participation or research outputs as claims of superiority, safety, compliance, validation, public authority acceptance, bankability, insurability, or deployment readiness. Implied Eligibility Prohibition prevents contributors from implying eligibility for public procurement, Project SPVs, National Consortium Company work, public authority programs, capital-reader interest, insurance approval, or donor support by reason of participation. Provider-Specific Output Controls require configuration, context, method, limitations, dependencies, non-generalization, reviewer boundaries, and claims restrictions before any controlled reference. Comparative Benchmark Controls govern provider comparisons through test conditions, reproducibility limits, conflict disclosure, non-generalization, public-safe review, and prohibition on unsupported marketing. Provider Boundary Incidents include procurement overclaim, validation overclaim, benchmark misuse, preferred-provider implication, public authority implication, and unauthorized Nexus status use.

13.4.10.3 No provider, provider contribution, provider status, provider recognition, provider category, provider-specific output, provider-supported output, provider-supported benchmark, provider-supported Nexus Universe activity, provider-supported National Node activity, provider-supported Working Group activity, provider-supported Competence Cell activity, provider-supported public authority learning room, provider-supported readiness room, provider-supported public-safe report, contribution record, benchmark record, comparative benchmark, technical review, public acknowledgment, public-safe summary, Docket entry, ARL status, Grid input where applicable, Nexus Rail routing, National Continuation Record, Handoff Dependency Note, correction notice, withdrawal notice, public clarification, or archive reference shall create certification, validation, recognition, maturity status, standards conformance, governance authority by default, public authority approval, procurement status, preferred-provider status, financeability, bankability, investability, insurability, underwriting acceptance, donor commitment, public finance allocation, official warning, emergency command, community consent, Indigenous consent, deployment authorization, project approval, handoff authorization, transaction, or execution authority by implication.

13.4.10.4 The controlling Provider Neutrality Formula is that providers may contribute tools, but not validation; infrastructure, but not preference; expertise, but not authority; benchmarks, but not marketing claims; public-good support, but not procurement advantage; public authority proximity, but not public authority approval; readiness-room participation, but not financeability; community visibility, but not consent; and Nexus Acceleration shall remain credible only while every provider contribution is recorded, bounded, neutral, claims-safe, correctionable, and incapable of becoming an implied market credential.

### 13.5 Partner Contribution Valuation, Recognition, Public-Safe Acknowledgment, Contribution Records, Non-Influence Status, and Public Notice Controls

#### 13.5.1 Contribution Valuation Principle

13.5.1.1 Contribution Valuation means the transparent, record-based method for identifying, describing, classifying, and, where appropriate, estimating the nature, scope, approximate value, duration, restrictions, conditions, public-good relevance, and operational significance of partner, sponsor, provider, university, technical, infrastructure, research-access, secure-room, venue, travel, volunteer, and build-crew support provided to Nexus Network, Nexus Universe, Nexus Acceleration, National Nexus Nodes, National Working Groups, Nexus Competence Cells, GCRI pathways, The Global Risks Forum (GRF) pathways, The Global Risks Alliance (GRA) pathways, Nexus Observatory, Nexus Rails, public-good repositories, or National Continuation pathways.

13.5.1.2 Contribution Valuation shall be used to preserve transparency, accountability, auditability, fairness, public-good interpretation, anti-capture discipline, recognition accuracy, and correctionability. It shall not be used to price influence, sell legitimacy, rank contributors as institutional authorities, allocate agenda control, grant research access control, create public authority proximity, imply procurement advantage, create finance or insurance signals, or convert contribution into institutional endorsement.

13.5.1.3 Contribution Valuation may identify approximate monetary value, in-kind equivalent value, service value, access value, infrastructure value, support duration, cost avoided, capacity enabled, or public-good relevance where appropriate for internal records, donor records, audit records, partner debriefs, contribution summaries, or public-safe acknowledgments; provided that valuation shall not be represented as purchase price for authority, recognition, visibility, agenda influence, researcher access, public authority access, capital-reader access, readiness status, procurement status, or lawful handoff opportunity.

13.5.1.4 Contribution Valuation shall distinguish pledged support, committed support, received support, deployed support, used support, unused support, partially used support, withdrawn support, restricted support, corrected support, terminated support, and archived support.

13.5.1.5 Contribution Valuation shall identify restrictions, conditions, use limitations, access limitations, data limitations, confidentiality conditions, security conditions, public-safe conditions, public authority boundary conditions, community or Indigenous safeguard conditions where applicable, recognition limits, no-control conditions, teardown obligations, and correction obligations.

13.5.1.6 Contribution Valuation shall be proportionate to the contribution’s sensitivity, operational role, public visibility, public authority relevance, readiness relevance, procurement sensitivity, data exposure, cyber exposure, public-safe risk, sponsor/provider influence risk, and national routing relevance.

13.5.1.7 Contribution Valuation creates transparency about support; it shall not create influence over what Nexus means, produces, reviews, routes, publishes, or continues.

***

#### 13.5.2 Valuation Categories

13.5.2.1 Valuation Categories shall classify partner and sponsor support according to the nature of the contribution, the basis on which value is recorded, the pathway supported, the conditions attached, the public-safe status, and the recognition limits applicable to the contribution.

13.5.2.2 Cash Support includes monetary support for public-good operations, Nexus Universe preparation, National Node preparation, research access, accessibility, travel, translation, secure-room operations, public-safe reporting, documentation, training, logistics, Working Group support, Competence Cell support, Nexus Network capacity, or post-cycle learning, subject to funding records, restrictions, conflicts, recognition limits, and no-control conditions.

13.5.2.3 In-Kind Services include donated or discounted services, professional time, technical services, engineering services, cybersecurity services, platform support, documentation support, translation, accessibility support, legal-interface support where appropriate, logistics support, communications support, training, and operational support, subject to role boundaries and claims discipline.

13.5.2.4 Cloud Credits and Compute Support include cloud credits, GPU access, CPU access, HPC access, accelerator access, inference capacity, training capacity, edge compute, sovereign compute, secure enclave capacity, confidential computing, storage, managed services, and workload support, subject to access, logging, workload classification, data boundary, security, teardown, and no-validation controls.

13.5.2.5 Hardware Loans, Equipment Grants, and Infrastructure Support include servers, storage, racks, networking devices, telecom equipment, sensors, edge devices, lab infrastructure, power or cooling support, hardware integration, test equipment, inventory support, safety support, installation support, teardown support, return obligations, and archive obligations.

13.5.2.6 Software Access and Platform Support include software licenses, public-good software support, repository tooling, workflow systems, AI tools, simulation tools, digital twin tools, geospatial tools, Earth observation tools, observability dashboards, identity systems, security systems, documentation systems, and developer environments, subject to license, IP, security, data, and public-safe conditions.

13.5.2.7 Engineering Time and Technical Mentor Time include engineering support, architect support, technical mentoring, build-crew leadership, researcher support, infrastructure configuration, debugging, security assistance, workflow support, and technical training, subject to role assignment, conflict disclosure, access limits, contribution records, and output-boundary controls.

13.5.2.8 Travel, Fellowship, Access, Accessibility, Translation, Venue, Data-Room, Secure-Room, Clean-Room, and Volunteer Support include support for participation, researcher access, community participation, Indigenous participation where applicable, youth participation, diaspora participation, fellows, students, volunteers, venue access, controlled environments, data rooms, no-download environments, compute-to-data environments, interpretation, accessible materials, and logistical support, subject to selection non-influence, safeguard controls, public-safe limits, and correction pathways.

13.5.2.9 Valuation Categories shall be descriptive and administrative only. They shall not create contributor rank, endorsement rank, influence rank, procurement rank, provider rank, maturity rank, readiness rank, finance rank, insurance rank, or public authority rank.

13.5.2.10 Valuation Categories organize contribution records; they do not organize authority.

***

#### 13.5.3 Contribution Records

13.5.3.1 Contribution Records shall be required for each partner, sponsor, provider, university, technical, infrastructure, data, research-access, secure-room, travel, fellowship, accessibility, venue, communications, volunteer, or build-crew contribution accepted for use within Nexus Network, Nexus Universe, Nexus Acceleration, National Nexus Nodes, Working Groups, Competence Cells, public authority learning, readiness rooms, public-safe reporting, public-good software, or National Continuation.

13.5.3.2 Each Contribution Record shall capture contributor identity, contributor category, contribution type, contribution description, value basis, valuation category, estimated or recorded value where appropriate, timing, duration, supported pathway, restrictions, conditions, access rights, access limits, data exposure, data handling conditions, confidentiality obligations, IP and licensing conditions, cybersecurity obligations, public-safe classification, recognition class, permitted acknowledgment language, prohibited claims, teardown obligations, correction obligations, and archive status.

13.5.3.3 The value basis shall identify whether the contribution is cash, in-kind, discounted, donated, loaned, credited, time-based, access-based, infrastructure-based, service-based, cost-avoidance-based, or non-valued for public-safe or legal reasons.

13.5.3.4 Contribution Records shall identify whether the contribution has been pledged, accepted, received, deployed, partially deployed, unused, restricted, paused, corrected, withdrawn, terminated, superseded, retired, or archived.

13.5.3.5 Contribution Records shall identify any conflicts or influence risks, including sponsor interest, provider interest, procurement interest, investor interest, insurer interest, donor interest, public finance interest, public authority relationship, policy interest, research interest, IP interest, media interest, community-facing interest, Indigenous-facing interest where applicable, data interest, or market interest.

13.5.3.6 Contribution Records shall identify whether a contributor may access rooms, records, datasets, systems, meetings, public authority learning environments, readiness rooms, community spaces, Indigenous spaces where applicable, research outputs, unpublished outputs, public-safe drafts, logs, repositories, or other controlled materials, and under what conditions.

13.5.3.7 Contribution Records shall include a boundary statement confirming that the contribution does not create control, endorsement, certification, validation, procurement status, preferred-provider status, financeability, insurability, donor commitment, public finance allocation, public authority approval, community consent, Indigenous consent, deployment authorization, project approval, handoff authorization, transaction, or execution authority.

13.5.3.8 A contribution shall not be publicly acknowledged, used in controlled systems, used in sensitive workflows, used in public authority learning rooms, used in readiness rooms, or used in public-facing Nexus materials unless an adequate Contribution Record exists or a temporary controlled-use record has been approved for limited use.

13.5.3.9 Contribution Records make support legible and correctable before recognition or use creates public meaning.

***

#### 13.5.4 Recognition Classes

13.5.4.1 Recognition Classes mean the contribution-specific acknowledgment categories used to describe contributors accurately, proportionately, and publicly safely without ranking contributors as endorsed, preferred, validated, certified, procurement-qualified, finance-relevant, insurance-approved, public authority-approved, or institutionally superior.

13.5.4.2 Recognition Classes may include Contributor, Supporting Contributor, Technical Contributor, Infrastructure Contributor, Compute Contributor, Cloud Contributor, Hardware Contributor, Network Contributor, Telecom Contributor, Cybersecurity Contributor, Data Contributor, AI Contributor, Simulation Contributor, Digital Twin Contributor, Observability Contributor, Repository Contributor, Secure-Room Supporter, Clean-Room Supporter, Research Workflow Supporter, Build-Crew Supporter, Research Access Supporter, Travel Supporter, Accessibility Supporter, Venue Supporter, Training Supporter, Public-Safe Reporting Supporter, National Node Supporter, Nexus Universe Supporter, Nexus Network Supporter, or Public-Good Supporter.

13.5.4.3 Recognition Classes shall be based on the actual Contribution Record and shall describe the support provided, not the importance, authority, reliability, market quality, public authority status, finance status, insurance status, maturity status, or procurement status of the contributor.

13.5.4.4 Recognition Classes shall not be structured or described as tiers of influence, tiers of approval, sponsor hierarchy by authority, preferred provider rank, market leadership category, official partner status by implication, procurement tier, finance-readiness tier, insurance-readiness tier, donor tier by control, or public authority access tier.

13.5.4.5 Recognition Classes may be grouped for administrative or public-safe purposes, provided that grouping does not imply that higher visibility creates higher legitimacy, greater authority, better technical validation, procurement preference, financeability, insurability, or public authority approval.

13.5.4.6 Recognition Classes shall be revocable, correctable, revisable, restricted, downgradable, withdrawable, supersedable, and archivable where the Contribution Record changes, contribution status changes, public-safe risk arises, misuse occurs, conflict is discovered, or recognition would create overclaim.

13.5.4.7 Recognition Classes shall travel with claims boundaries in public materials where needed.

13.5.4.8 Recognition Classes are gratitude labels, not authority labels.

***

#### 13.5.5 Public-Safe Acknowledgment

13.5.5.1 Public-Safe Acknowledgment means the controlled, claims-safe, proportionate, accurate, public-facing or controlled-public recognition of partner names, sponsor names, provider names, contributor names, logos where permitted, contribution descriptions, technical roles, support categories, case notes, and public report references.

13.5.5.2 Public-Safe Acknowledgment may state that a contributor provided a specified type of support for a specified pathway, time period, activity, program, room, tool, infrastructure layer, access pathway, or public-good function, provided that the statement is supported by a Contribution Record and reviewed for public-safe language.

13.5.5.3 Public-Safe Acknowledgment shall not state or imply that the contributor is endorsed, certified, validated, approved, preferred, procurement-qualified, market-approved, standards-conforming, Nexus-ready, financeable, insurable, donor-approved, public-finance-approved, public-authority-approved, community-consented, Indigenous-consented where applicable, deployment-authorized, handoff-authorized, or execution-authorized.

13.5.5.4 Sponsor references shall include support-without-control discipline where needed. Provider references shall include provider-neutrality and no-validation language where needed. Public authority references shall include learning-without-approval language where needed. Readiness-related references shall include no-reliance and non-transactional language where needed. Community and Indigenous references where applicable shall include participation-without-consent language where needed.

13.5.5.5 Logos, badges, marks, seals, visual placements, case notes, website listings, report acknowledgments, proceedings references, public-safe summaries, presentations, social media posts, and media references shall be controlled to prevent visual implication of endorsement, ranking, preferred status, certification, public authority approval, or procurement preference.

13.5.5.6 Public-Safe Acknowledgment may be withheld, delayed, redacted, aggregated, anonymized, restricted, or controlled where naming the contributor could create procurement risk, public authority confusion, market sensitivity, public-safe risk, safeguard risk, community harm, Indigenous safeguard concern where applicable, protected knowledge risk, cyber risk, data risk, legal risk, conflict risk, or overclaim risk.

13.5.5.7 Public-Safe Acknowledgment shall be corrected or withdrawn where contribution descriptions are inaccurate, value is overstated, contribution status changes, logo use is improper, restrictions are omitted, sponsor overclaim occurs, provider overclaim occurs, public authority confusion arises, or contributor conduct breaches conditions.

13.5.5.8 Public-Safe Acknowledgment allows Nexus to be transparent and grateful without turning gratitude into validation.

***

#### 13.5.6 Non-Influence Status

13.5.6.1 Non-Influence Status means the mandatory rule that contribution, valuation, recognition, acknowledgment, support level, support category, public notice, in-kind value, cash value, technical value, infrastructure value, travel value, venue value, or volunteer value shall not influence research selection, researcher access, fellowship selection, participant selection, National Priority formation, Working Group formation, Competence Cell assignment, review outcomes, public-safe reporting, readiness translation, maturity input, Docket status, ARL status, Nexus Rail routing, National Continuation, correction, archive, or lawful handoff decisions.

13.5.6.2 Every Contribution Record and public or controlled acknowledgment shall include or incorporate Non-Influence Status language appropriate to the contribution and audience.

13.5.6.3 Contributors shall not receive influence over agenda, themes, research calls, challenge briefs, researcher selection, public authority learning rooms, capital-reader rooms, community spaces, Indigenous spaces where applicable, technical findings, benchmark interpretation, public claims, public-safe summaries, readiness notes, safeguard records, routing notes, continuation records, or handoff dependency records because of contribution value or visibility.

13.5.6.4 Contribution value shall not determine the credibility of an output, priority of a Docket item, ARL status, Nexus Universe selection, public-safe publication status, readiness status, National Node routing, or lawful continuation pathway.

13.5.6.5 Where a contribution creates risk that a contributor could influence outputs, access, review, routing, or public meaning, additional controls may include separation of contribution and review, independent review, conflict disclosure, access limitation, recognition limitation, communications review, room exclusion, restricted data access, provider-neutrality controls, public-safe review, or contribution decline.

13.5.6.6 Non-Influence Status shall apply to contributors of all sizes, including anchor supporters, major sponsors, technical partners, small contributors, universities, volunteers, public-interest contributors, public authorities, providers, capital readers, insurers, donors, and hosts.

13.5.6.7 Any attempt to convert contribution into influence shall be treated as a Boundary Incident.

13.5.6.8 Non-Influence Status is the firewall between support and capture.

***

#### 13.5.7 Public Notice Controls

13.5.7.1 Public Notice Controls mean the rules determining when partner contributions may be publicly noticed, when they must remain controlled or confidential, and when notices require GRF claims review, legal review, public-safe review, safeguard review, National Node review, contributor correction, or restriction.

13.5.7.2 Public notice of a contribution may be permitted where the Contribution Record is complete, contributor identity may be disclosed safely, contribution terms allow disclosure, public-safe review permits disclosure, recognition language is approved, conflicts are managed, data and security risks are controlled, and acknowledgment will not create overclaim, procurement risk, public authority confusion, finance implication, insurance implication, donor implication, public finance implication, consent implication, or national bypass.

13.5.7.3 Public notice shall be controlled or withheld where the contribution involves confidential terms, sensitive infrastructure, cyber-sensitive support, protected knowledge, Indigenous knowledge where applicable, sensitive geospatial data, public authority-sensitive support, market-sensitive support, capital-reader room support, insurer-reader room support, donor-reader room support, public finance-sensitive support, community-sensitive support, or legally restricted information.

13.5.7.4 GRF claims review shall be required where contribution notices include public-facing claims, recognition language, sponsor references, provider references, maturity-related language, public legitimacy references, public authority references, community references, Indigenous references where applicable, public-safe reports, media materials, or potential public misunderstanding.

13.5.7.5 Legal or legal-interface review shall be required where contribution notices involve contractual restrictions, regulated activities, public procurement sensitivity, securities or finance sensitivity, insurance sensitivity, donor restrictions, public finance sensitivity, IP or licensing terms, data protection, confidentiality, export controls, sanctions, public authority sensitivity, or other legal risk.

13.5.7.6 Partner correction shall be required where the contributor’s proposed notice, press release, website reference, public statement, logo use, case note, investor reference, procurement reference, donor reference, or public authority-facing material is inaccurate, overclaiming, unsupported, unsafe, or inconsistent with Contribution Records.

13.5.7.7 Public notices may be delayed, redacted, aggregated, anonymized, controlled, withdrawn, superseded, corrected, or archived according to public-safe classification, legal requirements, safeguard requirements, data conditions, contributor conditions, national conditions, or correction needs.

13.5.7.8 Public Notice Controls ensure that transparency about support does not create unsafe or misleading public meaning.

***

#### 13.5.8 Contribution Record Correction

13.5.8.1 Contribution Record Correction means the process for correcting inaccurate contribution descriptions, overstated value, understated restrictions, improper recognition class, improper logo use, sponsor overclaim, provider overclaim, omitted conflicts, omitted restrictions, omitted teardown obligations, omitted data boundaries, changed contribution status, incorrect public notice, or boundary issues in Contribution Records or related acknowledgments.

13.5.8.2 Contribution Record Correction may be initiated by the contributor, steward, National Nexus Node, National Council, Working Group, Competence Cell, GCRI, GRF, GRA, public authority learner, community participant, Indigenous participant where applicable, public-interest participant, researcher, partner, sponsor, provider, capital reader, donor, insurer, legal-interface reviewer, public-safe reviewer, or other affected party.

13.5.8.3 Correction records shall identify the affected Contribution Record, contributor, contribution category, incorrect or incomplete statement, corrected statement, reason for correction, value change where applicable, recognition change, restriction change, access change, public-safe impact, safeguard impact, data impact, security impact, public authority impact, readiness impact, national impact, notice requirement, and archive reference.

13.5.8.4 Corrections may include revising contribution description, adjusting value basis, correcting contribution status, revising recognition class, adding restrictions, adding conflicts, adding public-safe limits, adding no-control language, revising access rights, adding teardown obligations, revising logo permissions, restricting acknowledgment, withdrawing acknowledgment, correcting public notices, notifying affected audiences, or archiving superseded records.

13.5.8.5 Overstated value shall be corrected where value is inflated, unsupported, misleading, calculated on an improper basis, converted into influence implication, or used to claim hierarchy, entitlement, or authority.

13.5.8.6 Improper logo use or name use shall be corrected through removal, revised placement, revised caption, revised disclaimer, restricted use, public clarification where required, or withdrawal of recognition.

13.5.8.7 Changed contribution status shall be recorded where support is not delivered, partially delivered, delayed, withdrawn, terminated, restricted, repurposed, corrected, superseded, or archived.

13.5.8.8 Contribution Record Correction shall preserve traceability unless deletion is required by law, privacy, security, protected knowledge, confidentiality, or other valid control.

13.5.8.9 Contribution Record Correction keeps transparency honest after support changes, errors arise, or claims drift.

***

#### 13.5.9 Withdrawal or Suspension of Recognition

13.5.9.1 Withdrawal or Suspension of Recognition means the authority to suspend, withdraw, correct, downgrade, restrict, supersede, or archive contributor acknowledgment where recognition becomes inaccurate, unsafe, overclaiming, conflict-affected, misleading, inconsistent with Contribution Records, inconsistent with public-safe classification, inconsistent with national safeguards, or inconsistent with contribution conditions.

13.5.9.2 Recognition may be suspended where a potential misuse, overclaim, conflict, breach of condition, public-safe concern, procurement concern, public authority confusion, finance implication, insurance implication, donor implication, public finance implication, community concern, Indigenous safeguard concern where applicable, protected knowledge concern, data concern, cyber concern, or legal concern requires review before recognition continues.

13.5.9.3 Recognition may be withdrawn where the contributor materially misuses Nexus names, makes false validation claims, implies endorsement, implies procurement status, implies public authority approval, implies financeability, implies insurability, implies donor commitment, implies public finance approval, implies consent, breaches access limits, breaches confidentiality, breaches data rules, breaches security rules, refuses correction, or otherwise acts inconsistently with public-good purpose.

13.5.9.4 Recognition may be corrected where the contribution description, category, value, duration, supported pathway, public role, logo use, restrictions, or acknowledgment language is inaccurate or incomplete.

13.5.9.5 Recognition may be downgraded or reclassified where the contribution is reduced, partially delivered, not delivered, no longer active, restricted, corrected, or no longer suitable for a prior recognition class.

13.5.9.6 Recognition may be superseded where a later Contribution Record replaces the earlier record, or where recognition must reflect changed terms, revised public-safe language, corrected contribution description, or changed contribution status.

13.5.9.7 Recognition may be archived where the contribution has ended, been retired, been withdrawn, been superseded, been terminated, or is no longer current but should remain traceable.

13.5.9.8 Withdrawal or suspension of recognition shall not be treated as reputational punishment by default. It is a claims-safety, public-good integrity, and record-correction tool.

13.5.9.9 Recognition withdrawal or suspension may require public correction, controlled notice, contributor notice, National Node notice, public authority learning notice, readiness-room notice, partner notice, or archive update depending on prior exposure and reliance risk.

13.5.9.10 Recognition remains valid only while it remains accurate, bounded, public-safe, conflict-aware, and non-misleading.

***

#### 13.5.10 Valuation and Recognition Summary Clause

13.5.10.1 Contribution valuation and recognition create transparency and gratitude, not control, authority, validation, procurement advantage, financeability, insurability, public authority approval, community consent, Indigenous consent, deployment authorization, handoff authorization, institutional endorsement, or execution authority.

13.5.10.2 Contribution Valuation records the nature, scope, approximate value where appropriate, duration, restrictions, and public-good relevance of partner support without implying purchase of influence. Valuation Categories include cash support, in-kind services, cloud credits, hardware loans, equipment grants, software access, engineering time, technical mentor time, travel support, venue support, data-room support, secure-room support, clean-room support, and volunteer support. Contribution Records capture contributor identity, contribution type, value basis, timing, restrictions, access rights, recognition class, data exposure, confidentiality, teardown obligations, and boundary statements. Recognition Classes may include contributor, supporting contributor, technical contributor, infrastructure contributor, build-crew supporter, research access supporter, secure-room supporter, or public-good supporter without ranking as endorsement. Public-Safe Acknowledgment governs partner names, logos, contribution descriptions, sponsor references, technical roles, case notes, and public reports under claims-safe and no-control language. Non-Influence Status confirms that contribution does not influence research selection, review outcomes, public-safe reporting, readiness translation, routing, maturity input, or lawful handoff decisions. Public Notice Controls determine when partner contributions may be publicly noticed, when they must remain controlled or confidential, and when notices require GRF claims review, legal review, or partner correction. Contribution Record Correction repairs inaccurate contribution descriptions, overstated value, improper logo use, sponsor overclaim, omitted restrictions, or changed contribution status. Withdrawal or Suspension of Recognition applies where recognition must be suspended, withdrawn, corrected, downgraded, superseded, or archived due to misuse, overclaim, conflict, or breach of conditions.

13.5.10.3 No contribution valuation, valuation category, Contribution Record, Recognition Class, public-safe acknowledgment, public notice, partner name, logo use, contribution description, sponsor reference, technical role, case note, public report, contribution value, cash support, in-kind service, cloud credit, hardware loan, equipment grant, software access, engineering time, technical mentor time, travel support, venue support, data-room support, volunteer support, support category, recognition category, public acknowledgment, correction record, withdrawal of recognition, suspension of recognition, downgraded recognition, superseded recognition, archived recognition, or contribution archive reference shall create certification, validation, recognition standing, maturity status, governance authority by default, public authority approval, procurement status, preferred-provider status, financeability, bankability, investability, insurability, underwriting acceptance, donor commitment, public finance allocation, official warning, emergency command, community consent, Indigenous consent, standards conformance, deployment authorization, project approval, handoff authorization, transaction, or execution authority by implication.

13.5.10.4 The controlling Valuation and Recognition Formula is that contribution value may be recorded, contribution support may be acknowledged, contribution categories may be described, and contributor generosity may be recognized; but value is not influence, recognition is not endorsement, acknowledgment is not validation, logo use is not approval, contribution class is not rank, public notice is not authority, sponsor support is not control, provider support is not preference, technical support is not certification, public authority proximity is not approval, readiness support is not finance, community support is not consent, and contribution transparency remains legitimate only while it remains accurate, bounded, public-safe, non-influencing, correctionable, and subordinate to the public-good stack.

### 13.6 Technical Mentor and Partner Engineer Rules, Support Boundaries, Researcher Interaction, Confidentiality, Information Access, Conflict Controls, and Influence Controls

#### 13.6.1 Technical Mentor Role

13.6.1.1 Technical Mentors mean bounded support participants who assist researchers, National Working Groups, Nexus Competence Cells, Nexus Universe teams, National Nexus Nodes, build crews, public-good software teams, secure-room users, data-room users, and operations teams in understanding, configuring, using, documenting, troubleshooting, and safely operating contributed technologies, platforms, workflows, tools, systems, infrastructure, or methods.

13.6.1.2 Technical Mentors may be provided by partners, sponsors, providers, universities, laboratories, public-interest technical communities, open-source communities, National Nodes, GCRI pathways, Nexus Universe build teams, or other approved contributor pathways, subject to role definition, conflict disclosure, access controls, confidentiality, public-safe rules, and no-influence boundaries.

13.6.1.3 Technical Mentors may provide office hours, documentation guidance, workflow support, configuration explanations, safe-use guidance, troubleshooting assistance, training, onboarding, debugging support, reproducibility support, repository navigation, environment support, secure-room workflow support, compute-use support, and tool-specific explanations.

13.6.1.4 Technical Mentors shall not control research questions, research selection, researcher access, experimental design beyond technical support, benchmark framing, benchmark interpretation, findings, public-safe summaries, publications, readiness notes, public authority learning outputs, Docket status, ARL status, Nexus Rail routing, National Continuation, or lawful handoff dependency decisions.

13.6.1.5 Technical Mentor support shall be recorded where it materially affects a research workflow, technical output, benchmark condition, configuration, environment, method note, reproducibility note, compute-use record, data handling note, or public-good software release.

13.6.1.6 Technical Mentors shall operate under least-privilege access, need-to-know information access, confidentiality obligations, conflict controls, no-solicitation rules, no-pressure rules, and no-claim rules.

13.6.1.7 Technical Mentors strengthen the usability of the stack; they shall not shape the meaning of the outputs for sponsor, provider, commercial, institutional, public authority, finance, insurance, donor, procurement, or market advantage.

***

#### 13.6.2 Partner Engineer Role

13.6.2.1 Partner Engineers mean technical support contributors responsible for configuration, integration, troubleshooting, safe operation, monitoring support, documentation, teardown support, and technical support of contributed stack components within Nexus Network, Nexus Universe, Nexus Acceleration, National Nodes, Working Groups, Competence Cells, secure rooms, data rooms, clean rooms, compute-to-data environments, public-good repositories, observability interfaces, and temporary frontier-stack environments.

13.6.2.2 Partner Engineers may support compute, cloud, hardware, storage, networking, telecom, cybersecurity, identity, data platforms, AI platforms, simulation systems, digital twins, observability dashboards, repository systems, workflow tools, secure enclaves, clean rooms, confidential computing, developer environments, and other contributed components.

13.6.2.3 Partner Engineers may perform approved technical tasks, including setup, configuration, integration testing, access provisioning under authorized controls, monitoring support, logging support, vulnerability remediation, incident response support, environment stabilization, performance troubleshooting, documentation, teardown, access closure, and post-cycle debrief support.

13.6.2.4 Partner Engineers shall not alter research findings, manipulate benchmark results, suppress limitations, edit public-safe outputs for provider benefit, influence readiness conclusions, influence public authority summaries, influence researcher selection, control access allocation, or shape routing decisions for contributor advantage.

13.6.2.5 Partner Engineer activity shall be logged where it affects systems, access, data, workloads, configuration, security, benchmarks, outputs, public-good software releases, or technical records.

13.6.2.6 Partner Engineers shall follow approved change-control, access-control, incident-response, data-handling, confidentiality, secure-development, repository-security, and teardown procedures applicable to the relevant environment.

13.6.2.7 Partner Engineers keep contributed stack components usable and safe; they shall not become operators of Nexus meaning, institutional judgment, public authority learning, readiness conclusions, or execution pathways.

***

#### 13.6.3 Support Boundaries

13.6.3.1 Support Boundaries mean the limits governing Technical Mentor and Partner Engineer assistance so that technical support enables safe and effective use of contributed systems without controlling research outcomes, institutional records, public claims, or downstream interpretations.

13.6.3.2 Technical Mentors and Partner Engineers may support usage, configuration, documentation, troubleshooting, secure operation, workflow understanding, environment stability, reproducibility support, and technical learning within the assigned scope.

13.6.3.3 Technical Mentors and Partner Engineers shall not direct research conclusions, alter findings, suppress unfavorable results, control benchmarks, influence benchmark interpretation, influence publication decisions, approve outputs, draft conclusions for provider benefit, shape readiness conclusions, influence public authority learning summaries, or determine routing for contributor advantage.

13.6.3.4 Technical Mentors and Partner Engineers shall not pressure researchers, Working Groups, Competence Cells, National Nodes, public authority learners, community participants, Indigenous participants where applicable, public-interest participants, or build crews to use a contributor’s product, platform, system, dataset, model, or service beyond the recorded scope.

13.6.3.5 Technical Mentors and Partner Engineers shall not use access to promote sales, obtain procurement leads, collect market intelligence, solicit customers, obtain investor materials, obtain insurance or finance insights, influence public authority actors, or convert public-good participation into commercial pipeline activity.

13.6.3.6 Technical Mentors and Partner Engineers may explain technical limitations of contributed systems, but shall not convert those explanations into marketing claims, competitive comparisons, superiority claims, benchmark claims, certification claims, procurement claims, finance claims, insurance claims, or deployment-readiness claims.

13.6.3.7 Support Boundaries shall be included in mentor and engineer onboarding, contribution records, room rules, researcher guidance, meeting records where relevant, ticketing systems, public-safe communication rules, and correction procedures.

13.6.3.8 Support Boundaries ensure that the people who help operate the stack do not acquire control over the science, records, claims, readiness, routing, or lawful handoff pathways.

***

#### 13.6.4 Researcher Interaction Rules

13.6.4.1 Researcher Interaction Rules mean the rules governing how Technical Mentors and Partner Engineers interact with researchers, fellows, students, public-interest researchers, Working Groups, Competence Cells, build crews, National Nodes, and Nexus Universe participants.

13.6.4.2 Permitted interaction may include office hours, help desks, ticketing, documentation sessions, onboarding sessions, technical troubleshooting, configuration support, workflow support, reproducibility support, secure-room support, data-room support, environment support, and approved technical mentoring.

13.6.4.3 Researcher interactions shall be recorded where material to outputs, including through office-hour logs, ticket records, support notes, meeting records, configuration notes, issue trackers, repository comments, documentation updates, or compute-use records.

13.6.4.4 Technical Mentors and Partner Engineers shall disclose their contributor affiliation, provider affiliation, sponsor affiliation, employer affiliation, role, support scope, conflict status where relevant, and support boundaries before providing substantive support.

13.6.4.5 Technical Mentors and Partner Engineers shall respect researcher independence. They shall not pressure researchers to produce favorable results, omit limitations, use sponsor language, cite products, praise contributors, share unpublished findings, include contributor branding, provide testimonials, support marketing claims, or change conclusions.

13.6.4.6 Technical Mentors and Partner Engineers shall not solicit sales meetings, procurement discussions, employment discussions, investment discussions, consulting opportunities, proprietary collaborations, or commercial relationships through research support channels unless separately permitted by the applicable pathway and outside restricted support contexts.

13.6.4.7 Technical Mentors and Partner Engineers shall not request or retain unpublished research, raw data, credentials, logs, restricted outputs, public authority-sensitive information, protected knowledge, Indigenous knowledge where applicable, community-sensitive information, finance-sensitive information, or secure-room outputs except where access is expressly authorized and necessary for the assigned support role.

13.6.4.8 Researcher interactions involving sensitive matters shall follow confidentiality, access, data handling, public-safe, protected knowledge, secure-room, public authority, readiness, and safeguard rules.

13.6.4.9 Researcher Interaction Rules allow technical support to be useful, respectful, traceable, and non-coercive.

***

#### 13.6.5 Confidentiality and Restricted Information

13.6.5.1 Confidentiality and Restricted Information Rules shall govern Technical Mentor and Partner Engineer access to unpublished research, restricted data, contributor information, partner information, sponsor information, public authority context, community inputs, Indigenous inputs where applicable, protected knowledge, secure-room outputs, readiness-room records, public-safe drafts, Docket records, Working Group materials, Competence Cell materials, and controlled Nexus records.

13.6.5.2 Technical Mentors and Partner Engineers shall maintain confidentiality of all non-public, controlled, restricted, confidential, redacted, delayed, no-publication, protected knowledge, cyber-sensitive, public authority-sensitive, community-sensitive, Indigenous-sensitive where applicable, market-sensitive, finance-sensitive, or legally restricted information received through their support role.

13.6.5.3 Unpublished research shall not be copied, retained, shared, quoted, summarized publicly, used for commercial purposes, used for internal contributor marketing, used for product development, used for investor communications, used for procurement advantage, or used for public authority influence unless expressly authorized through the applicable record and permitted by law, policy, confidentiality terms, and public-safe review.

13.6.5.4 Restricted data shall be accessed only under recorded permission, least-privilege controls, approved workload rules, data handling notes, compute-to-data controls where applicable, no-download rules where applicable, retention limits, deletion rules, output review, and logging.

13.6.5.5 Public authority context shall be treated as learning-context information unless separately and lawfully public. Technical Mentors and Partner Engineers shall not represent public authority context as official position, approval, policy decision, procurement signal, funding signal, warning, command, regulatory action, or authorization.

13.6.5.6 Community inputs and Indigenous inputs where applicable shall be protected from extraction, marketing use, sponsor validation, provider validation, finance-readable social proof, public authority cover, media misuse, and consent overclaim.

13.6.5.7 Protected knowledge shall be handled under access restrictions, publication limits, cultural or community protocols where applicable, Indigenous protocols where applicable, data sovereignty considerations where applicable, sensitive-location controls, and correction pathways.

13.6.5.8 Confidentiality obligations shall survive the end of the support role, contribution, Nexus Universe cycle, Working Group, Competence Cell assignment, or access period.

13.6.5.9 Breach of confidentiality may require access revocation, incident response, correction, notification, withdrawal, public-safe clarification where required, suspension, termination, archive update, or exclusion from future support pathways.

13.6.5.10 Confidentiality protects the trust needed for technical support to operate in sensitive public-good environments.

***

#### 13.6.6 Information Access Controls

13.6.6.1 Information Access Controls shall ensure that Technical Mentors and Partner Engineers receive only the access necessary to perform assigned support tasks under least-privilege, need-to-know, purpose-limited, time-limited, logged, reviewable, and revocable conditions.

13.6.6.2 Access may include environment access, system access, repository access, ticket access, log access, documentation access, configuration access, monitoring access, limited data access, secure-room access, data-room access, clean-room access, or output-review access only where expressly authorized.

13.6.6.3 Access shall be classified by role, system, dataset, room, record class, public-safe class, safeguard status, data sensitivity, public authority sensitivity, cyber sensitivity, protected knowledge status, Indigenous sensitivity where applicable, community sensitivity, finance sensitivity, market sensitivity, and operational need.

13.6.6.4 Technical Mentors and Partner Engineers shall not receive default access to raw data, personal data, rights-bearing data, health-sensitive data, community-sensitive data, Indigenous knowledge where applicable, protected knowledge, public authority-sensitive records, cyber-sensitive records, sensitive geospatial information, confidential partner materials, unpublished research outputs, readiness-room materials, capital-reader room records, or lawful handoff dependency records.

13.6.6.5 Access shall be logged where practicable and appropriate. Logs may include user identity, role, time, system, action, dataset, repository, room, output accessed, change made, export attempted, credential used, ticket reference, and closure status.

13.6.6.6 Access shall be reviewed periodically and closed when no longer needed, when the assignment ends, when the support role changes, when a conflict arises, when a safeguard issue arises, when a boundary incident occurs, when the Nexus Universe cycle ends, when teardown occurs, or when correction requires restriction.

13.6.6.7 Access to secure rooms, clean rooms, no-download environments, compute-to-data environments, confidential computing environments, and controlled data rooms shall require heightened authorization, identity verification, training where appropriate, monitoring, no-download controls, output review, and closure procedures.

13.6.6.8 Technical Mentors and Partner Engineers shall not share credentials, bypass access controls, export restricted information, create unauthorized copies, access unrelated records, retain logs outside approved systems, or use support access for commercial, competitive, procurement, finance, insurance, donor, public authority, or marketing purposes.

13.6.6.9 Information Access Controls ensure that technical support receives enough access to help and not enough access to capture, misuse, or overreach.

***

#### 13.6.7 Conflict Controls

13.6.7.1 Conflict Controls shall require Technical Mentors and Partner Engineers to disclose commercial, provider, competitive, investment, insurance, donor, public finance, public authority, research, university, sponsor, institutional, founder, media, community, Indigenous where applicable, personal, IP, confidentiality, or other conflicts relevant to supported work.

13.6.7.2 Conflict disclosures shall identify employer affiliation, contributor affiliation, provider relationship, sponsor relationship, product interest, platform interest, competitive interest, procurement interest, investment interest, insurance interest, donor interest, public finance interest, public authority relationship, policy interest, research interest, university relationship, IP interest, publication interest, consulting relationship, and prior involvement in the supported output.

13.6.7.3 Conflict Controls may require role limitation, access limitation, separation from review, separation from benchmark interpretation, exclusion from publication discussions, exclusion from readiness note drafting, exclusion from public authority summaries, exclusion from community or Indigenous spaces where applicable, exclusion from competitor-sensitive materials, independent review, recusal, or removal from the support role.

13.6.7.4 A Technical Mentor or Partner Engineer affiliated with a provider whose system is being used may provide factual configuration and troubleshooting support, but shall not independently determine benchmark findings, performance conclusions, public-safe claims, readiness conclusions, procurement relevance, or provider comparison.

13.6.7.5 A Technical Mentor or Partner Engineer with capital, insurance, donor, public finance, or investment interests shall not access readiness-room materials, diligence-gap records, Handoff Dependency Notes, capital-reader room materials, insurer-reader materials, donor-reader materials, public finance-sensitive materials, or non-public finance-related outputs unless expressly authorized under no-reliance, information-control, conflict-management, and access-control rules.

13.6.7.6 A Technical Mentor or Partner Engineer with public authority roles shall not use support participation to create informal public authority decision-making, procurement implication, regulatory signal, policy signal, funding implication, official warning, command, or authorization.

13.6.7.7 Failure to disclose conflicts may result in correction, access restriction, recusal, support suspension, support termination, output re-review, public-safe clarification where required, withdrawal, supersession, non-continuation, archive, or exclusion from future support pathways.

13.6.7.8 Conflict Controls make technical support credible by preventing hidden interests from shaping public-good outputs.

***

#### 13.6.8 Influence Controls

13.6.8.1 Influence Controls shall prevent Technical Mentors and Partner Engineers from shaping selection, review, awards, public claims, benchmark interpretation, public authority summaries, readiness notes, routing decisions, National Continuation, Nexus Universe outcomes, Docket status, ARL status, Grid inputs where applicable, public-safe reporting, or lawful handoff dependency decisions for contributor, sponsor, provider, institutional, commercial, public authority, finance, insurance, donor, media, or personal advantage.

13.6.8.2 Technical Mentors and Partner Engineers shall not influence researcher selection, participant selection, fellowship selection, travel support selection, access tiering, compute allocation, dataset access, secure-room access, public authority room participation, community participation, Indigenous participation where applicable, awards, recognition, track selection, or Nexus Universe placement except through assigned operational input recorded within approved processes.

13.6.8.3 Technical Mentors and Partner Engineers shall not draft or edit public claims, public-safe summaries, readiness notes, benchmark conclusions, public authority learning summaries, community summaries, Indigenous summaries where applicable, media materials, investor materials, donor materials, insurance materials, public finance materials, procurement-sensitive materials, or handoff dependency records for contributor advantage.

13.6.8.4 Technical Mentors and Partner Engineers may provide factual corrections about tool configuration, environment conditions, version numbers, operational constraints, access limitations, or technical dependencies, provided that such corrections are recorded and do not become control over conclusions.

13.6.8.5 Technical Mentors and Partner Engineers shall not offer benefits, privileged support, faster access, improved access, private assistance, employment opportunities, commercial opportunities, investor access, procurement introductions, media visibility, or future opportunities to influence research outcomes, public statements, benchmark results, or participant conduct.

13.6.8.6 Technical Mentors and Partner Engineers shall not retaliate against researchers, Working Groups, Competence Cells, National Nodes, communities, Indigenous actors where applicable, public-interest participants, or reviewers for unfavorable findings, limitations, corrections, non-continuations, benchmark results, or public-safe restrictions.

13.6.8.7 Influence Controls shall be enforced through training, room rules, ticket records, meeting records, conflict disclosures, communications review, access logs, escalation pathways, correction procedures, and sanction or exclusion where required.

13.6.8.8 Influence Controls protect the independence of Nexus outputs by ensuring that technical support cannot become outcome control.

***

#### 13.6.9 Technical Mentor Misconduct or Boundary Incident

13.6.9.1 Technical Mentor or Partner Engineer Misconduct or Boundary Incident means any act, omission, communication, access event, support interaction, configuration action, data action, research interaction, benchmark interaction, public claim, confidentiality breach, solicitation, or influence attempt by a Technical Mentor or Partner Engineer that creates risk of unauthorized access, data misuse, benchmark manipulation, researcher pressure, claims overreach, confidentiality breach, public authority confusion, readiness overclaim, provider advantage, sponsor advantage, community harm, Indigenous safeguard concern where applicable, protected knowledge exposure, or public-safe harm.

13.6.9.2 Misconduct or Boundary Incidents may include unauthorized access, credential sharing, data export, retention of restricted information, access beyond need-to-know, use of restricted data for commercial purposes, pressure on researchers, solicitation, sales activity, benchmark manipulation, suppression of unfavorable findings, alteration of outputs, unauthorized editing of public-safe summaries, unauthorized readiness language, unauthorized public authority references, unauthorized sponsor or provider claims, and misuse of Nexus names.

13.6.9.3 Misconduct or Boundary Incidents may also include breach of confidentiality, disclosure of unpublished research, disclosure of public authority context, disclosure of community inputs, disclosure of Indigenous knowledge where applicable, disclosure of protected knowledge, disclosure of sensitive geospatial information, disclosure of cyber-sensitive information, disclosure of finance-sensitive information, or disclosure of secure-room outputs.

13.6.9.4 Each incident shall be recorded with the person or role involved, contributor affiliation, affected system, affected record, affected participant, affected data, affected output, conduct at issue, access logs where applicable, public-safe risk, safeguard risk, data risk, cyber risk, public authority risk, readiness risk, procurement risk, consent risk, market risk, national risk, required response, responsible steward, notice requirement, and archive status.

13.6.9.5 Responses may include immediate access suspension, room removal, credential revocation, support-role limitation, recusal, incident investigation, output freeze, benchmark freeze, data containment, public-safe hold, affected-party notice, contributor notice, public authority notice where required, community or Indigenous protocol notice where applicable, correction, withdrawal, supersession, public clarification where required, sponsor or provider status review, termination of support role, exclusion from future pathways, or legal escalation.

13.6.9.6 Where an incident affects research outputs, benchmark records, readiness notes, public-safe summaries, public authority learning records, community safeguard records, Indigenous safeguard records where applicable, or Handoff Dependency Notes, the affected records shall be reviewed for correction, withdrawal, restriction, supersession, archive, or re-review.

13.6.9.7 Misconduct or Boundary Incidents shall not be minimized as informal technical misunderstandings where they affect confidentiality, data, public-safe claims, safeguards, public authority boundaries, readiness boundaries, provider neutrality, or participant independence.

13.6.9.8 Technical Mentor and Partner Engineer misconduct controls protect the integrity of the stack by ensuring that support failures become correctable institutional events.

***

#### 13.6.10 Mentor and Engineer Summary Clause

13.6.10.1 Technical Mentors and Partner Engineers strengthen the stack only when their support is transparent, bounded, confidential, conflict-managed, access-controlled, non-soliciting, non-coercive, non-influencing, public-safe, and correctionable.

13.6.10.2 Technical Mentors are bounded support participants who assist researchers, Working Groups, or operations teams in using contributed technologies, platforms, workflows, or infrastructure without controlling research outcomes. Partner Engineers are technical support contributors responsible for configuration, troubleshooting, safe operation, integration, documentation, and support of contributed stack components. Support Boundaries permit mentors and engineers to support usage but prohibit them from directing research conclusions, altering findings, controlling benchmarks, influencing publication, approving outputs, or shaping readiness conclusions for provider benefit. Researcher Interaction Rules govern permitted support, office hours, ticketing, documentation, meeting records, conflict disclosure, confidentiality, no-solicitation, and no-pressure requirements. Confidentiality rules protect unpublished research, restricted data, partner information, public authority context, community inputs, protected knowledge, secure-room outputs, and controlled records. Information Access Controls ensure mentors and engineers receive only necessary access to environments, logs, data, outputs, and records under least-privilege and need-to-know principles. Conflict Controls require disclosure of commercial, provider, competitive, investment, public authority, research, personal, and other conflicts with recusal or limited-access rules where needed. Influence Controls prevent mentors and engineers from shaping selection, review, awards, public claims, benchmark interpretation, public authority summaries, readiness notes, or routing decisions for contributor advantage. Misconduct or Boundary Incidents include unauthorized access, pressure on researchers, data misuse, benchmark manipulation, solicitation, claims overreach, confidentiality breach, and influence attempts.

13.6.10.3 No Technical Mentor, Partner Engineer, technical mentor support record, partner engineer support record, office-hour record, ticketing record, documentation note, configuration note, troubleshooting note, environment support record, benchmark support record, researcher interaction, secure-room support, data-room support, access log, conflict disclosure, recusal record, influence-control record, misconduct record, boundary incident record, correction notice, withdrawal notice, public clarification, or archive reference shall create certification, validation, recognition, maturity status, governance authority by default, public authority approval, procurement status, preferred-provider status, financeability, bankability, investability, insurability, underwriting acceptance, donor commitment, public finance allocation, official warning, emergency command, community consent, Indigenous consent, standards conformance, deployment authorization, project approval, handoff authorization, transaction, or execution authority by implication.

13.6.10.4 The controlling Mentor and Engineer Formula is that mentors teach but do not decide, engineers configure but do not certify, support explains but does not influence, troubleshooting records conditions but does not shape conclusions, access enables assistance but does not permit capture, confidentiality protects trust, conflicts must be visible, influence must be blocked, misconduct must be corrected, and no technical support role shall convert contributed capacity into research control, provider validation, public authority action, readiness authority, procurement advantage, consent, handoff, or execution.

### 13.7 Pre-Production, Advanced Capability, Benchmark Use, Publication, Case-Study, Marketing, Researcher Feedback, and Non-Generalization Boundaries

#### 13.7.1 Pre-Production Technology Use

13.7.1.1 Pre-Production Technology Use means the controlled use within Nexus Network, Nexus Universe, Nexus Acceleration, National Nodes, Working Groups, Competence Cells, research pathways, secure rooms, data rooms, public-good software pathways, observability pathways, and temporary frontier-stack environments of technologies, systems, models, tools, platforms, devices, services, datasets, methods, or infrastructure that are pre-production, prototype, beta, alpha, experimental, confidential, restricted, advanced, unreleased, limited-access, early-stage, non-commercial, partner-confidential, research-only, or otherwise not generally available.

13.7.1.2 Pre-production technologies may be used only where the use is recorded, scoped, technically justified, legally permissible, security-reviewed, data-reviewed, public-safe reviewed where relevant, safeguard-reviewed where relevant, access-controlled, confidentiality-bound, benchmark-bounded, publication-bounded, claims-bounded, correctionable, and consistent with public-good purpose.

13.7.1.3 Each pre-production technology use shall be recorded in a Pre-Production Use Record or equivalent Contribution Record identifying the contributor, technology, version or build where available, development status, permitted use, prohibited use, environment, users, access period, data exposure, security controls, confidentiality conditions, benchmark limits, publication limits, public-safe status, known limitations, support contacts, incident procedures, teardown or access-closure obligations, and correction pathway.

13.7.1.4 Pre-production technologies shall not be used in ways that imply market readiness, deployment readiness, safety certification, security certification, compliance approval, standards conformance, public authority acceptance, procurement suitability, financeability, insurability, donor suitability, public finance eligibility, community consent, Indigenous consent where applicable, project approval, handoff authorization, or execution authority.

13.7.1.5 Pre-production technology use shall include heightened caution where the technology involves AI systems, agentic workflows, advanced compute, telecom, cyber tools, digital twins, simulation environments, sensitive data, critical infrastructure, geospatial intelligence, Earth observation, robotics, drones, sensors, public authority learning, protected knowledge, community-sensitive contexts, Indigenous knowledge where applicable, public health, security-sensitive systems, or regulated environments.

13.7.1.6 Pre-production technologies shall be subject to access restrictions, logging, monitoring, support boundaries, incident procedures, vulnerability disclosure rules, no-download rules where applicable, output review, public-safe classification, and withdrawal or suspension where safety, security, confidentiality, data, public-safe, safeguard, or boundary concerns arise.

13.7.1.7 Pre-production technology use shall not create a public claim that the contributor, provider, sponsor, product, system, model, platform, infrastructure, or method has been selected, validated, certified, approved, preferred, procured, adopted, financed, insured, or endorsed by Nexus, GCRI, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), a National Nexus Node, a public authority, a community, Indigenous actors where applicable, capital readers, donors, insurers, or any downstream actor.

13.7.1.8 Pre-production technologies may generate useful learning only when their experimental status, limits, risks, conditions, and prohibited interpretations remain visible.

***

#### 13.7.2 Advanced Capability Testing

13.7.2.1 Advanced Capability Testing means the controlled research use, assessment, simulation, observation, integration, stress-testing, workflow testing, or demonstration of advanced compute, AI, telecom, cyber, simulation, digital twin, hardware, data, geospatial, Earth observation, robotics, sensor, observability, secure-room, or infrastructure capabilities for public-good learning within recorded boundaries.

13.7.2.2 Advanced Capability Testing may support research production, Evidence Packs, Method Notes, Benchmark Records, Model Cards, System Cards, Compute-Use Records, Infrastructure Configuration Records, Data Handling Notes, Reproducibility Notes, Observability Records, public authority learning records, Nexus Universe outputs, Working Group outputs, Competence Cell reviews, public-good software pathways, and readiness question notes.

13.7.2.3 Advanced Capability Testing shall be conducted only under a recorded test purpose, defined environment, approved workload, known configuration, access controls, data boundaries, safety controls, cyber controls, dual-use controls, public-safe limits, safeguard requirements, reviewer boundaries, conflict disclosures, partner role descriptions, and correction pathway.

13.7.2.4 Advanced Capability Testing shall not imply that a technology is ready for market, deployment, public procurement, public authority use, operational use, emergency use, regulated use, commercial use, finance consideration, insurance consideration, donor funding, public finance support, community deployment, Indigenous context deployment where applicable, project implementation, or handoff.

13.7.2.5 Testing of advanced AI, agentic workflows, cyber tools, telecommunications systems, robotics, drones, digital twins, simulations, geospatial tools, and critical infrastructure testbeds shall include misuse review, safety controls, human review, sandboxing where appropriate, output classification, public authority boundary controls, sensitive-location controls, protected knowledge controls, and stop-the-line triggers.

13.7.2.6 Testing involving partner or provider systems shall distinguish technical support, partner-supplied information, independent review, benchmark conditions, observed outputs, unresolved limitations, and prohibited claims.

13.7.2.7 Advanced Capability Testing may produce learning, evidence, gaps, corrections, and routing recommendations; it shall not produce validation, certification, approval, endorsement, procurement qualification, financeability, insurability, public authority decision, consent, deployment authorization, handoff authorization, or execution authority.

13.7.2.8 Advanced capability is permitted in Nexus Acceleration only as bounded learning, not as market proof.

***

#### 13.7.3 Benchmark Use Conditions

13.7.3.1 Benchmark Use Conditions mean the required record conditions that must be satisfied before any benchmark, performance comparison, capability test, stress test, simulation result, model evaluation, AI evaluation, cloud comparison, compute comparison, telecom comparison, cyber comparison, digital twin comparison, software comparison, hardware comparison, data-platform comparison, workflow comparison, or infrastructure comparison may be cited, used, circulated, published, or referenced.

13.7.3.2 Each Benchmark Record shall specify the benchmark purpose, object tested, provider or contributor involvement, environment, workload, dataset, input conditions, configuration, hardware, software, network conditions, compute conditions, model or system version, tool versions, run date, test duration, measurement method, evaluator role, reviewer role, assumptions, limitations, uncertainty, failure conditions, reproducibility conditions, conflict disclosures, public-safe status, access class, publication class, permitted references, prohibited claims, and correction pathway.

13.7.3.3 Benchmark records shall identify the partner role, including whether a partner configured the system, supplied tools, provided data, provided engineering support, provided interpretation, observed testing, contributed infrastructure, or had any relationship to benchmark design, execution, review, publication, or communication.

13.7.3.4 Benchmark conditions shall identify whether the benchmark is exploratory, internal, research-only, controlled, public-safe publishable, restricted, confidential, partner-confidential, public authority-sensitive, procurement-sensitive, market-sensitive, cyber-sensitive, or no-publication.

13.7.3.5 Benchmark results shall include non-generalization language stating that the result applies only to the recorded configuration, workload, dataset, environment, assumptions, method, participants, time, and conditions, and shall not be generalized to other products, platforms, contexts, users, jurisdictions, workloads, deployment settings, procurement settings, public authority settings, finance settings, insurance settings, or safety contexts.

13.7.3.6 Benchmark results shall not be cited without limitations, conflict disclosures, reproducibility limits, data limits, environment limits, workload limits, reviewer boundaries, public-safe classification, and prohibited-use language.

13.7.3.7 Benchmark results shall not be used to create unsupported claims of superiority, safety, compliance, reliability, resilience, validation, certification, financeability, insurability, procurement eligibility, public authority acceptance, market readiness, deployment readiness, or Nexus approval.

13.7.3.8 Benchmark Use Conditions preserve the value of measurement by preventing measurement from becoming unbounded marketing, procurement influence, or false certainty.

***

#### 13.7.4 Publication Rules for Partner-Supported Results

13.7.4.1 Publication Rules for Partner-Supported Results mean the requirements governing public release, controlled release, technical report publication, public-safe summaries, proceedings, repository publication, case notes, research papers, post-cycle papers, media materials, knowledge-base entries, sponsor materials, provider materials, and public reports involving results produced with partner, sponsor, provider, contributor, university, infrastructure, data, cloud, compute, telecom, cybersecurity, AI, simulation, digital twin, observability, secure-room, or workflow support.

13.7.4.2 Partner-supported results shall not be published unless the underlying records identify the partner support used, contribution record, method basis, evidence basis, data basis, configuration, environment, workload, support role, conflicts, limitations, reproducibility constraints, public-safe classification, confidentiality conditions, claims boundaries, and correction pathway.

13.7.4.3 Public-safe review shall be required before publication where results include public-facing claims, partner names, sponsor names, provider names, public authority references, community references, Indigenous references where applicable, benchmark results, readiness language, public-good claims, recognition language, sensitive geospatial information, protected knowledge, public authority learning records, or media-facing summaries.

13.7.4.4 Technical review shall be required before publication where results include technical claims, methods, model outputs, AI outputs, simulation outputs, digital twin outputs, benchmark records, compute-use records, data handling notes, reproducibility claims, software artifacts, system cards, model cards, observability records, or infrastructure configuration records.

13.7.4.5 Partner confidentiality review may be required where publication could disclose confidential partner information, unreleased technology, pre-production systems, trade secrets, security information, system configurations, infrastructure vulnerabilities, controlled data, or restricted contribution terms; provided that confidentiality review shall not permit a partner to suppress accurate public-safe limitations, unfavorable findings, correction records, or necessary boundary language for improper commercial advantage.

13.7.4.6 Publication shall include benchmark boundary language where benchmarked results are referenced, including environment, workload, data, configuration, reproducibility, limitations, conflicts, partner role, non-generalization, and public-safe status.

13.7.4.7 Publication shall not include unsupported marketing claims, sponsor claims, provider claims, public authority approval claims, financeability claims, insurability claims, donor commitment claims, public finance allocation claims, procurement claims, community consent claims, Indigenous consent claims where applicable, deployment-readiness claims, project approval claims, handoff claims, or execution claims.

13.7.4.8 Publication may be public, controlled, restricted, redacted, delayed, withheld, withdrawn, superseded, corrected, or archived according to public-safe review, technical review, confidentiality review, safeguard review, legal-interface review, national review, and correction requirements.

13.7.4.9 Publication of partner-supported results shall make the public-good contribution visible where appropriate, but shall not transform public-good learning into partner endorsement.

***

#### 13.7.5 Case-Study Boundaries

13.7.5.1 Case-Study Boundaries mean the rules governing public-safe learning stories, technical case notes, partner contribution summaries, Nexus Universe cycle summaries, National Node stories, research workflow examples, infrastructure lessons, readiness-room lessons, public authority learning examples, community safeguard examples, and post-cycle learning narratives involving partners, sponsors, providers, contributors, researchers, public authorities, communities, Indigenous actors where applicable, National Nodes, Working Groups, or Competence Cells.

13.7.5.2 Case studies may describe what was attempted, what was learned, what records were produced, what methods were used, what infrastructure was required, what safeguards were applied, what limitations were identified, what corrections occurred, what routing followed, and what continuation questions remain.

13.7.5.3 Case studies shall not claim or imply certification, validation, superiority, provider preference, procurement advantage, public authority approval, financeability, insurability, donor commitment, public finance allocation, community consent, Indigenous consent where applicable, deployment readiness, project approval, handoff authorization, execution success, or market legitimacy.

13.7.5.4 Case studies involving partners or providers shall distinguish contribution from endorsement, infrastructure use from validation, technical support from certification, observed result from general performance, public authority learning from public authority action, readiness question from finance outcome, community participation from consent, and Nexus Universe participation from adoption.

13.7.5.5 Case studies shall be reviewed for public-safe language, sponsor and provider claims, benchmark boundaries, confidentiality, protected knowledge, community safeguards, Indigenous safeguards where applicable, public authority boundaries, readiness boundaries, procurement sensitivity, and non-generalization.

13.7.5.6 Case studies shall not include selective quotations, visuals, screenshots, benchmark tables, researcher feedback, public authority statements, community statements, Indigenous statements where applicable, partner names, logos, or contribution values unless permitted by the relevant record and reviewed for public-safe use.

13.7.5.7 Case studies may be corrected, withdrawn, restricted, superseded, clarified, or archived where they become inaccurate, overclaiming, outdated, unsafe, misleading, conflict-affected, or inconsistent with contribution records, publication rules, or public-safe classifications.

13.7.5.8 Case studies tell public-good learning stories; they do not convert stories into certification, procurement, finance, consent, or deployment claims.

***

#### 13.7.6 Marketing Boundaries

13.7.6.1 Marketing Boundaries mean the rules prohibiting partners, sponsors, providers, contributors, manufacturers, hyperscalers, telecoms, cloud providers, cybersecurity firms, data platforms, AI providers, software providers, infrastructure actors, and support partners from using Nexus participation, Nexus Universe participation, research results, public-safe reports, benchmark records, access, contribution status, public authority attendance, capital-reader observation, insurer-reader observation, donor-reader observation, community participation, Indigenous participation where applicable, or media visibility as market validation or endorsement.

13.7.6.2 Partners shall not use Nexus participation to state or imply that their products, services, platforms, systems, models, datasets, infrastructure, personnel, methods, or organizations are superior, safer, compliant, certified, validated, approved, preferred, procurement-qualified, financeable, insurable, donor-approved, public-finance-approved, public-authority-accepted, community-consented, Indigenous-consented where applicable, deployable, handoff-ready, or execution-ready.

13.7.6.3 Partners shall not use Nexus names, logos, marks, public reports, proceedings, screenshots, photographs, participant names, public authority attendance, researcher participation, benchmark outputs, readiness-room access, Docket status, ARL status, National Node materials, or Nexus Universe materials in marketing without prior approval under contribution, claims, public-safe, and logo-use rules.

13.7.6.4 Marketing materials shall not omit limitations, uncertainty, configuration constraints, benchmark conditions, method boundaries, data limits, public-safe restrictions, partner role disclosures, conflict disclosures, no-reliance statements, public authority disclaimers, procurement disclaimers, consent-boundary language, or no-conversion statements where required.

13.7.6.5 Marketing use of researcher feedback, public authority feedback, community feedback, Indigenous feedback where applicable, capital-reader observations, insurer-reader observations, donor observations, or public finance reader observations shall be prohibited unless specifically authorized, accurately quoted, non-coercive, non-selective, public-safe, and accompanied by required boundaries.

13.7.6.6 Partners shall not suggest that attendance at, access to, or support of Nexus Universe, a National Node, a Working Group, a Competence Cell, a public authority learning room, a readiness room, a community space, an Indigenous space where applicable, or a research room constitutes market validation, official participation status, public authority acceptance, capital interest, insurance interest, donor interest, public finance interest, or community acceptance.

13.7.6.7 Marketing violations may result in correction, withdrawal, public clarification where required, restricted communications, recognition suspension, recognition withdrawal, contribution suspension, contribution termination, exclusion from future pathways, or archive.

13.7.6.8 Marketing Boundaries preserve the public-good character of Nexus by preventing partners from turning controlled research into commercial proof.

***

#### 13.7.7 Researcher Feedback Controls

13.7.7.1 Researcher Feedback Controls mean the rules allowing structured feedback from researchers, fellows, students, Working Group participants, Competence Cell contributors, public-interest researchers, National Node participants, build crews, and Nexus Universe participants on tools, systems, platforms, workflows, infrastructure, documentation, mentorship, secure rooms, data rooms, compute environments, observability interfaces, and support quality while preventing testimonial overclaim, paid endorsement confusion, pressure, selective quotation, or unsupported public marketing.

13.7.7.2 Researcher feedback may be collected for internal learning, technical improvement, partner debrief, repository improvement, workflow correction, documentation improvement, public-good software improvement, secure-room improvement, Nexus Universe improvement, National Node capacity improvement, and post-cycle renewal.

13.7.7.3 Researcher feedback shall be voluntary, non-coercive, non-retaliatory, clearly scoped, and separate from research selection, awards, access allocation, travel support, fellowships, publication opportunity, compute allocation, grading, employment opportunity, commercial opportunity, or future Nexus participation.

13.7.7.4 Partners, sponsors, providers, Technical Mentors, and Partner Engineers shall not pressure researchers to provide favorable feedback, testimonials, endorsements, ratings, quotes, social media posts, case-study quotes, sales references, investor references, procurement references, or marketing statements.

13.7.7.5 Researcher feedback used externally shall require permission, public-safe review, quotation review, context review, conflict review, and boundary language. Selective quotation shall be prohibited where it would mislead readers, omit material limitations, imply endorsement, imply validation, imply procurement relevance, imply financeability, imply public authority acceptance, or misrepresent researcher independence.

13.7.7.6 Paid or benefit-linked feedback shall be clearly identified and shall not be used as endorsement unless permitted by applicable policy and accompanied by appropriate disclosure and public-safe review.

13.7.7.7 Researcher feedback about provider-specific tools shall not be used to claim superiority, general performance, certification, validation, safety, compliance, deployment readiness, procurement readiness, financeability, insurability, or Nexus endorsement.

13.7.7.8 Researcher feedback may be anonymized, aggregated, redacted, controlled, or withheld where public release would expose unpublished research, sensitive data, protected knowledge, community information, Indigenous knowledge where applicable, public authority context, confidential partner information, or public-safe risk.

13.7.7.9 Researcher Feedback Controls allow honest improvement while preventing researchers from being converted into marketing instruments.

***

#### 13.7.8 Non-Generalization Rule

13.7.8.1 Non-Generalization Rule means that results from a specific test, configuration, workload, dataset, team, time period, environment, partner-supported workflow, secure-room setting, compute allocation, cloud configuration, AI model version, simulation setup, digital twin scenario, telecom environment, cyber range, hardware stack, data platform, observability dashboard, or Nexus Universe cycle shall not be generalized beyond the recorded conditions.

13.7.8.2 Every test, benchmark, experiment, simulation, model evaluation, infrastructure run, secure-room workflow, AI-assisted output, digital twin output, observability output, public authority learning record, readiness question note, or partner-supported result shall state the conditions under which it was produced and the conditions under which it should not be interpreted.

13.7.8.3 Non-generalization language shall identify limits related to environment, hardware, software, model version, data, workload, user skill, configuration, time, access, security settings, network conditions, public authority context, national context, community context, Indigenous context where applicable, assumptions, method, reviewer scope, reproducibility, and public-safe classification.

13.7.8.4 A result observed in one Nexus Universe cycle, National Node, Working Group, Competence Cell review, research run, public authority learning context, readiness room, secure room, or partner-supported workflow shall not be represented as generally valid across other countries, sectors, public authorities, communities, Indigenous contexts where applicable, technologies, configurations, providers, markets, procurement processes, finance processes, insurance processes, donor processes, public finance processes, or deployment environments.

13.7.8.5 Non-generalization shall apply even where results are impressive, strategically useful, sponsor-supported, public authority-observed, capital-reader-observed, media-visible, technically advanced, or produced by prestigious researchers or institutions.

13.7.8.6 Non-generalization language shall accompany public-safe summaries, case studies, partner communications, benchmark records, technical reports, readiness notes, public authority learning notes, public reports, repository records, Nexus Universe materials, and public-facing knowledge-base entries where specific results may otherwise be overstated.

13.7.8.7 Violation of the Non-Generalization Rule shall be treated as a Boundary Incident requiring correction, withdrawal, restricted circulation, public clarification where required, revised benchmark language, revised case-study language, revised partner communications, supersession, non-continuation, or archive.

13.7.8.8 The Non-Generalization Rule preserves scientific honesty by ensuring that bounded results remain bounded.

***

#### 13.7.9 Advanced Capability Misuse and Correction

13.7.9.1 Advanced Capability Misuse means any use, communication, omission, publication, benchmark reference, case study, marketing claim, researcher quotation, public authority reference, readiness reference, sponsor reference, provider reference, public-safe report, investor reference, insurance reference, donor reference, public finance reference, procurement reference, community reference, Indigenous reference where applicable, or public material that misrepresents pre-production technology use, advanced capability testing, benchmark results, partner-supported results, case-study findings, researcher feedback, or Nexus participation.

13.7.9.2 Advanced Capability Misuse may include overstated benchmarks, pre-production marketing, selective results, omitted limitations, omitted confidentiality limits, omitted non-generalization language, omitted public-safe classification, omitted conflict disclosures, researcher quotation misuse, public authority implication, procurement implication, capital-reader implication, insurer-reader implication, donor implication, public finance implication, community consent implication, Indigenous consent implication where applicable, unsupported superiority claims, unsupported safety claims, unsupported compliance claims, or unsupported deployment-readiness claims.

13.7.9.3 Misuse may occur through direct claims, implied claims, visuals, diagrams, dashboards, screenshots, tables, benchmark charts, social media posts, press releases, sales decks, investor decks, public authority briefings, donor materials, public finance materials, insurance submissions, case studies, technical blogs, repository descriptions, or conference presentations.

13.7.9.4 Advanced Capability Misuse shall be recorded as a Boundary Incident where it creates risk of public confusion, market distortion, procurement distortion, public authority confusion, finance overclaim, insurance overclaim, donor overclaim, public finance overclaim, community harm, Indigenous safeguard concern where applicable, protected knowledge exposure, public-safe risk, national bypass, or loss of scientific integrity.

13.7.9.5 Correction measures may include correction notice, revised language, removal of unsupported claims, removal of unauthorized logo use, removal of benchmark claims, withdrawal of case study, withdrawal of researcher quotation, revised public-safe summary, revised benchmark record, revised publication, public clarification where required, controlled clarification, restriction of future communications, recognition suspension, contribution suspension, contribution termination, output freeze, Docket correction, ARL correction, Routing Note correction, non-continuation, or archive.

13.7.9.6 Where misuse involves pre-production or confidential technology, correction shall also consider confidentiality breach, security risk, vulnerability exposure, partner-confidential information, unreleased system information, legal obligations, and controlled notice rather than unnecessary public amplification.

13.7.9.7 Where misuse involves public authority implication, finance implication, insurance implication, donor implication, public finance implication, procurement implication, or consent implication, correction shall include appropriate no-conversion language and may require notice to affected readers.

13.7.9.8 Advanced Capability Misuse shall not be minimized as marketing enthusiasm where it distorts evidence, authority, readiness, public safety, consent, procurement, or market meaning.

13.7.9.9 Correction of misuse protects both the contributor and Nexus by restoring the boundary between controlled learning and public claim.

***

#### 13.7.10 Benchmark and Marketing Summary Clause

13.7.10.1 Nexus Acceleration may generate technical learning, pre-production learning, advanced capability learning, benchmark learning, infrastructure learning, researcher feedback, public-safe case studies, and partner-supported results, but it shall never permit partners to convert controlled research into unbounded marketing, validation, certification, procurement claims, finance claims, insurance claims, public authority claims, consent claims, deployment claims, handoff claims, or execution claims.

13.7.10.2 Pre-production technology use shall occur only under safety, security, confidentiality, benchmark, publication, claims, and correction boundaries. Advanced Capability Testing shall be controlled research use of advanced compute, AI, telecom, cyber, simulation, digital twin, hardware, data platforms, observability tools, or infrastructure without implying market readiness or validation. Benchmark Use Conditions shall specify environment, workload, data, configuration, limitations, reproducibility, conflicts, partner role, non-generalization, and public-safe status. Publication Rules for Partner-Supported Results shall require public-safe review, technical review, partner confidentiality review where appropriate, benchmark boundary language, and no unsupported marketing claims. Case-Study Boundaries shall permit public-safe learning stories while prohibiting claims of certification, superiority, provider preference, procurement advantage, public authority approval, financeability, insurability, or deployment readiness. Marketing Boundaries shall prohibit partners from using Nexus participation, research results, access, public authority attendance, capital-reader observation, or community participation as market validation or endorsement. Researcher Feedback Controls shall permit structured feedback on tools or infrastructure while preventing testimonial overclaim, paid endorsement confusion, pressure, selective quotation, or unsupported public marketing. The Non-Generalization Rule shall prohibit results from a specific test, configuration, workload, team, time, dataset, or environment from being generalized beyond recorded conditions. Advanced Capability Misuse shall include overstated benchmarks, pre-production marketing, selective results, researcher quotation misuse, public authority implication, or unsupported claims, and shall require correction or withdrawal.

13.7.10.3 No pre-production technology use, prototype use, experimental technology use, advanced capability test, benchmark, performance comparison, capability test, stress test, simulation result, model evaluation, AI evaluation, cloud comparison, compute comparison, telecom comparison, cyber comparison, digital twin comparison, software comparison, hardware comparison, data-platform comparison, workflow comparison, infrastructure comparison, partner-supported result, publication, case study, marketing material, researcher feedback, testimonial, quotation, public authority observation, capital-reader observation, insurer-reader observation, donor-reader observation, community participation, Indigenous participation where applicable, public-safe summary, public report, Nexus Universe material, National Node material, Working Group output, Competence Cell review, Docket entry, ARL status, Routing Note, correction notice, withdrawal notice, or archive reference shall create certification, validation, recognition, maturity status, standards conformance, governance authority by default, public authority approval, procurement status, preferred-provider status, financeability, bankability, investability, insurability, underwriting acceptance, donor commitment, public finance allocation, official warning, emergency command, community consent, Indigenous consent, deployment authorization, project approval, handoff authorization, transaction, or execution authority by implication.

13.7.10.4 The controlling Benchmark and Marketing Formula is that Nexus may test, learn, compare, document, publish, summarize, and correct; partners may support, observe where permitted, receive bounded feedback, and be acknowledged where appropriate; but pre-production use is not market readiness, advanced testing is not validation, benchmarks are not rankings, publication is not endorsement, case studies are not certification, researcher feedback is not a testimonial by default, public authority observation is not approval, capital-reader observation is not finance, community participation is not consent, Indigenous participation is not consent, and no controlled research result may be transformed into unbounded marketing, procurement advantage, public authority implication, readiness claim, deployment claim, or execution authority.

### 13.8 Sponsor and Provider Conflict Disclosure, Employer-Affiliation Disclosure, Influence Risk, Anti-Capture Controls, Boundary Incidents, Correction, and Withdrawal

#### 13.8.1 Sponsor and Provider Conflict Disclosure

13.8.1.1 Sponsor and Provider Conflict Disclosure means the mandatory disclosure discipline requiring sponsors, providers, partners, manufacturers, hyperscalers, telecoms, cloud providers, cybersecurity firms, data platforms, AI providers, software providers, infrastructure actors, universities, technical contributors, support partners, and their representatives to disclose conflicts, commercial interests, procurement interests, investment interests, insurance interests, donor interests, public finance interests, policy interests, public authority relationships, competitor relationships, data interests, intellectual-property interests, research interests, and other influence risks relevant to Nexus Network, Nexus Universe, Nexus Acceleration, National Nexus Nodes, National Councils, Helix Councils, National Working Groups, Nexus Competence Cells, public authority learning rooms, readiness rooms, public-safe reporting, Docket pathways, Grid input pathways where applicable, National Continuation, or lawful handoff dependency review.

13.8.1.2 Sponsors and providers shall disclose interests before contribution acceptance, room access, research support, technical mentoring, engineering support, benchmark participation, public authority learning participation, readiness-room participation, Working Group participation, Competence Cell support, public-safe report reference, public acknowledgment, Nexus Universe participation, National Node support, or any other role through which the sponsor or provider could influence records, claims, outputs, access, routing, correction, or public meaning.

13.8.1.3 Disclosures shall identify the sponsor’s or provider’s relevant products, services, platforms, tools, systems, infrastructure, markets, procurement interests, public authority relationships, public-sector sales interests, investment relationships, insurer relationships, donor relationships, public finance relationships, policy advocacy, regulatory interests, litigation or compliance sensitivities where material, competitor relationships, funded research relationships, university or laboratory relationships, consultant relationships, data interests, IP interests, and any intended public communications.

13.8.1.4 Sponsor and provider disclosures shall identify whether the contributor seeks or may later seek procurement, project, National Consortium Company, Project SPV, public authority, capital, insurance, donor, public finance, operator, implementation, or lawful handoff opportunities related to the supported workstream, national priority, Nexus Universe track, technology domain, or jurisdiction.

13.8.1.5 Disclosure shall include relationships between sponsor and provider roles where an entity is both a sponsor and provider, a provider and capital reader, a sponsor and public authority contractor, a university and vendor, a cloud provider and AI provider, a donor and implementation actor, or otherwise occupies multiple roles capable of creating role confusion.

13.8.1.6 Sponsor and provider conflict disclosures shall be updated when interests change, contribution scope changes, public authority relationships arise, procurement opportunities arise, investment relationships arise, insurance or donor relationships arise, public communications are proposed, new products become relevant, benchmark use changes, or potential influence risks become material.

13.8.1.7 Failure to disclose a material sponsor or provider conflict may result in restricted access, recognition limitation, recusal, independent review, correction of records, withdrawal of claims, suspension of participation, termination of participation, public-safe clarification where required, non-continuation, archive, or exclusion from future contribution pathways.

13.8.1.8 Sponsor and Provider Conflict Disclosure protects Nexus public-good work by making influence visible before it becomes control.

***

#### 13.8.2 Employer-Affiliation Disclosure

13.8.2.1 Employer-Affiliation Disclosure means the requirement that participants, reviewers, mentors, partner engineers, volunteers, council members, Working Group participants, Competence Cell contributors, technical leads, build-crew members, public authority learners, researchers, fellows, public-interest participants, media participants, readiness-room participants, and other Nexus participants disclose employer affiliations and relevant institutional roles where such affiliations may affect interpretation, access, conflict management, public-safe language, readiness discipline, procurement sensitivity, public authority boundaries, community safeguards, Indigenous safeguards where applicable, or routing.

13.8.2.2 Employer-Affiliation Disclosure shall identify current employer, sponsoring institution, contributing organization, client relationship where relevant, funded role where relevant, advisory role, board role, public authority role, university or laboratory role, provider role, sponsor role, investor role, insurer role, donor role, public finance role, media role, community representation role, Indigenous representation role where applicable, and any institutional relationship relevant to the matter being considered.

13.8.2.3 Employer affiliation shall be recorded for persons participating in National Councils, Helix Councils, National Leadership Council pathways, National Investors Council pathways, National Working Groups, Nexus Competence Cells, Nexus Universe tracks, research rooms, secure rooms, data rooms, clean rooms, public authority learning rooms, capital-reader rooms, readiness rooms, community spaces, Indigenous spaces where applicable, public-safe review, technical review, benchmark review, and lawful handoff dependency review.

13.8.2.4 Employer affiliation shall not disqualify participation by default. It shall enable appropriate interpretation, conflict review, role limitation, access limitation, recusal, independent review, provider-neutrality controls, procurement-neutrality controls, readiness-room controls, public authority boundary controls, and public-safe claims discipline.

13.8.2.5 Where a participant’s employer has a commercial, procurement, public authority, investment, insurance, donor, public finance, sponsor, provider, competitor, media, or policy interest in the workstream or output, the participant’s role shall be reviewed for influence risk and may be limited, separated from review, or recused where necessary.

13.8.2.6 Employer affiliations shall be handled with appropriate privacy, confidentiality, public-safe classification, and access controls. Public disclosure of employer affiliation shall occur only where necessary, permitted, and public-safe.

13.8.2.7 Failure to disclose a material employer affiliation or institutional role may require correction of meeting records, review records, contribution records, conflict records, public-safe summaries, readiness notes, benchmark records, routing records, or continuation records, and may result in access restriction, recusal, role limitation, suspension, or archive.

13.8.2.8 Employer-Affiliation Disclosure ensures that institutional context is visible without treating affiliation itself as authority, endorsement, or disqualification.

***

#### 13.8.3 Influence Risk Assessment

13.8.3.1 Influence Risk Assessment means the structured assessment of whether sponsors, providers, employers, capital readers, insurers, donors, public finance readers, public authority actors, universities, institutional partners, media actors, founders, technical contributors, or other participants could improperly influence Nexus agenda, records, claims, access, research selection, public authority learning, community participation, Indigenous participation where applicable, benchmark interpretation, public-safe reporting, readiness translation, Docket status, ARL status, routing, correction, National Continuation, or lawful handoff dependency review.

13.8.3.2 Influence Risk Assessment shall be conducted where support is material, visibility is high, public authority proximity exists, procurement sensitivity exists, finance or insurance sensitivity exists, donor or public finance sensitivity exists, provider-specific outputs exist, benchmark comparisons exist, pre-production technologies are used, sensitive data are accessed, community or Indigenous safeguards are implicated, public-safe reporting is planned, or lawful handoff dependency tracking is contemplated.

13.8.3.3 Influence risks may include agenda capture, research-selection influence, access allocation influence, provider validation, sponsor control, procurement advantage, public authority implication, financeability implication, insurability implication, donor commitment implication, public finance allocation implication, benchmark manipulation, selective publication, data capture, protected knowledge misuse, community consent overclaim, Indigenous consent overclaim where applicable, public narrative control, media distortion, or national bypass.

13.8.3.4 Influence Risk Assessment shall review contribution records, conflict disclosures, employer affiliations, room access requests, public communications, benchmark conditions, provider-specific outputs, public authority references, readiness-room design, National Node routing, Working Group mandates, Competence Cell assignments, public-safe summaries, and proposed recognition.

13.8.3.5 Influence risk may be classified as low, moderate, high, severe, restricted, or stop-the-line, according to the likelihood and consequence of improper influence, public confusion, data misuse, public authority overclaim, finance overclaim, procurement distortion, community harm, Indigenous safeguard harm where applicable, or loss of public-good independence.

13.8.3.6 Influence Risk Assessment may result in approval of support within limits, additional disclosure, limited access, separation from review, recusal, independent review, multi-party review, public-safe language restrictions, recognition limits, communications review, benchmark restrictions, public notice controls, contribution restriction, contribution decline, pause, correction, or termination.

13.8.3.7 Influence Risk Assessment shall be recorded where the risk is material, the contribution is significant, the pathway is public-facing, or the assessment affects access, recognition, review, routing, publication, or continuation.

13.8.3.8 Influence Risk Assessment prevents influence from becoming invisible infrastructure inside public-good work.

***

#### 13.8.4 Anti-Capture Controls

13.8.4.1 Anti-Capture Controls shall prevent sponsors, providers, employers, capital readers, insurers, donors, public finance readers, public authorities, universities, institutional partners, founders, elite networks, media actors, technical contributors, or any participant class from capturing Nexus agenda, research selection, national priorities, public-safe reporting, review conclusions, readiness translation, public authority learning, community participation, Indigenous participation where applicable, routing, correction, National Continuation, or lawful handoff dependency review.

13.8.4.2 Anti-Capture Controls shall include balanced participation, role separation, disclosure requirements, employer-affiliation records, conflict registers, contribution records, access limits, room rules, independent review, public-safe review, safeguard review, provider-neutrality controls, procurement-neutrality controls, no-reliance readiness controls, National Node routing, correction pathways, and stop-the-line authority.

13.8.4.3 Balanced participation shall ensure that no sponsor, provider, helix, capital reader, public authority actor, university, founder, media actor, donor, insurer, or institutional bloc dominates priority formation, Working Group formation, Competence Cell review, Nexus Universe selection, public-safe reporting, or readiness translation.

13.8.4.4 Recusal and limited access shall be used where conflicts could affect research selection, benchmark interpretation, provider-specific outputs, public claims, readiness notes, public authority learning records, procurement-sensitive matters, community safeguards, Indigenous safeguards where applicable, or handoff dependency records.

13.8.4.5 Independent review shall be required where provider-specific results, sponsor-supported outputs, benchmark claims, public authority-sensitive outputs, readiness-sensitive outputs, public-facing case studies, or high-risk public-safe outputs could be materially influenced by a conflicted actor.

13.8.4.6 Public-safe review shall ensure that contributor recognition, sponsor references, provider references, public authority references, community references, Indigenous references where applicable, readiness references, benchmark references, case studies, public reports, and public notices do not create false authority, false legitimacy, false finance signal, false procurement signal, or false consent signal.

13.8.4.7 Stop-the-line authority may be used to pause access, publication, public communication, benchmark release, readiness-room use, public authority room use, data access, Nexus Universe use, routing, or handoff dependency tracking where capture risk, conflict risk, public-safe risk, safeguard risk, or boundary risk is material.

13.8.4.8 Anti-Capture Controls shall be enforceable through correction, restriction, recusal, suspension, termination, public clarification where required, withdrawal of recognition, rerouting, non-continuation, and archive.

13.8.4.9 Anti-Capture Controls preserve the public-good stack by ensuring that support never becomes governance through influence.

***

#### 13.8.5 Recusal and Limited Participation

13.8.5.1 Recusal and Limited Participation means the process by which a sponsor, provider, employer-affiliated participant, technical mentor, partner engineer, reviewer, council member, Working Group participant, Competence Cell contributor, public authority actor, capital reader, insurer, donor, media actor, researcher, or other participant is excluded from, or limited within, a pathway, room, review, output, decision, or record because a conflict, affiliation, access risk, influence risk, public-safe risk, safeguard risk, procurement sensitivity, readiness sensitivity, or provider-specific interest exists.

13.8.5.2 Recusal may be required where a participant has a direct or material interest in research selection, benchmark review, provider-specific output, public claims, readiness translation, public authority outputs, procurement-sensitive matters, insurance-readiness records, donor-readiness records, public finance relevance records, community safeguard records, Indigenous safeguard records where applicable, protected knowledge records, sensitive data, or lawful handoff dependency records.

13.8.5.3 Limited Participation may allow a participant to provide factual, technical, contextual, operational, or scoping information while excluding the participant from conclusions, scoring, claims drafting, public-safe approval, benchmark interpretation, readiness language, public authority summaries, routing decisions, continuation decisions, correction decisions, or handoff dependency conclusions.

13.8.5.4 Recusal and Limited Participation records shall identify the participant, affiliation, conflict or sensitivity, affected pathway, permitted role, prohibited role, access limits, review limits, confidentiality conditions, public-safe restrictions, duration, steward, and correction pathway.

13.8.5.5 Provider personnel may provide configuration, troubleshooting, documentation, and technical context for provider systems, but shall not determine findings, benchmark conclusions, public-safe claims, procurement relevance, readiness conclusions, or comparative performance interpretations involving their own systems.

13.8.5.6 Sponsors may provide support context and contribution details, but shall not participate in decisions or records that determine agenda control, researcher selection, public authority learning content, community participation, Indigenous participation where applicable, readiness notes, benchmark conclusions, public-safe reports, routing, correction, or handoff dependencies where sponsor influence risk is present.

13.8.5.7 Public authority actors may participate in learning and problem-context roles, but shall not use Nexus participation to make informal public authority decisions, procurement decisions, funding decisions, regulatory signals, official warnings, emergency commands, or legal authorizations.

13.8.5.8 Recusal and Limited Participation shall not be treated as reputational discipline by default. They are integrity controls that allow participation to continue safely where full participation would create role confusion or capture risk.

13.8.5.9 Recusal and Limited Participation preserve the usefulness of expertise and support while preventing conflicts from controlling outputs.

***

#### 13.8.6 Boundary Incident Definition

13.8.6.1 Sponsor and Provider Boundary Incident means any sponsor or provider-related event, conduct, omission, access use, communication, claim, record use, public statement, marketing material, research interaction, benchmark interaction, room participation, public authority interaction, community interaction, Indigenous interaction where applicable, readiness-room interaction, or handoff-related interaction that creates risk of hidden control, agenda pressure, access misuse, data misuse, benchmark manipulation, overclaim, unauthorized status use, public-safe language violation, role collapse, public authority confusion, procurement confusion, finance confusion, insurance confusion, donor confusion, public finance confusion, consent confusion, national bypass, or execution implication.

13.8.6.2 Boundary Incidents may include hidden control over agenda, pressure on researchers, pressure on Working Groups, pressure on Competence Cells, pressure on National Nodes, attempts to control research selection, attempts to control public authority participation, attempts to control community or Indigenous participation where applicable, improper access to rooms or records, data misuse, confidential information misuse, protected knowledge exposure, benchmark manipulation, selective quotation, publication pressure, suppression of unfavorable findings, sponsor overclaim, provider overclaim, or unauthorized use of Nexus names or marks.

13.8.6.3 Boundary Incidents may include claims that a sponsor or provider is Nexus-approved, Nexus-certified, Nexus-validated, Nexus-recognized, Nexus-ready, preferred by Nexus, procurement-qualified through Nexus, publicly approved by a public authority through Nexus, finance-ready through Nexus, insurable through Nexus, donor-supported through Nexus, community-consented through Nexus, Indigenous-consented through Nexus where applicable, deployment-authorized through Nexus, or handoff-authorized through Nexus.

13.8.6.4 Boundary Incidents may occur through public materials, private materials, sales materials, investor materials, donor materials, public finance materials, insurance submissions, procurement submissions, public authority briefings, case studies, social media posts, technical blogs, press releases, internal reports, presentations, dashboards, logo use, visual placement, or oral statements.

13.8.6.5 Boundary Incidents may be actual, potential, perceived, attempted, prevented, ongoing, corrected, repeated, public, controlled, confidential, technical, public-safe, procurement-sensitive, finance-sensitive, public authority-sensitive, community-sensitive, Indigenous-sensitive where applicable, data-sensitive, or cyber-sensitive.

13.8.6.6 A Boundary Incident shall be treated as an institutional integrity event, not merely a communications issue, where it affects public meaning, institutional role separation, public authority boundaries, finance boundaries, procurement neutrality, provider neutrality, community safeguards, Indigenous safeguards where applicable, data protection, public-safe reporting, or lawful handoff discipline.

13.8.6.7 The purpose of defining Boundary Incidents is to ensure that capture, overclaim, and role collapse are correctable before they become institutional practice.

***

#### 13.8.7 Boundary Incident Review

13.8.7.1 Boundary Incident Review means the process for intake, recording, assessment, review, correction, communication control, notice, routing, and archive of sponsor or provider Boundary Incidents.

13.8.7.2 Boundary Incident Review may be initiated by a steward, National Nexus Node, National Council, Helix Council, National Working Group, Competence Cell, GCRI, GRF, GRA, public authority learner, researcher, community participant, Indigenous participant where applicable, public-interest participant, sponsor, provider, partner, capital reader, donor, insurer, media actor, reviewer, Technical Mentor, Partner Engineer, legal-interface reviewer, public-safe reviewer, or any person with a credible concern.

13.8.7.3 The incident intake record shall identify the alleged sponsor or provider conduct, affected contributor, affected records, affected outputs, affected pathways, affected participants, source of concern, date, public-safe classification, access class, immediate risk, and whether a temporary pause, access restriction, communications hold, publication hold, benchmark hold, readiness-room hold, public authority room hold, or data hold is required.

13.8.7.4 A fact record shall identify relevant communications, Contribution Records, conflict disclosures, employer-affiliation disclosures, access logs where applicable, room records, meeting records, benchmark records, public materials, private materials, public authority materials, readiness records, researcher interactions, technical mentor interactions, partner engineer interactions, and correction history.

13.8.7.5 Risk assessment shall consider public-safe risk, role-collapse risk, public authority confusion, procurement risk, finance risk, insurance risk, donor risk, public finance risk, community consent risk, Indigenous consent risk where applicable, data risk, cyber risk, protected knowledge risk, benchmark misuse risk, national bypass risk, market distortion risk, and reputational reliance risk.

13.8.7.6 Boundary Incident Review may require consultation with GCRI for technical or evidence issues, GRF for public-safe, claims, registry, or public notice issues, GRA for readiness, no-reliance, finance, insurance, donor, public finance, or handoff dependency issues, National Nodes for national ownership issues, safeguard reviewers for community, Indigenous, privacy, cyber, data, human research, geospatial, or public-interest issues, and legal-interface reviewers where required.

13.8.7.7 Communication controls may include internal hold, sponsor or provider communication hold, public statement hold, public-safe language restriction, logo-use suspension, case-study hold, benchmark hold, investor-material correction, procurement-material correction, media correction, public authority notice, or controlled clarification.

13.8.7.8 Boundary Incident Review shall produce an outcome record identifying no issue, issue corrected, correction required, access restricted, recognition limited, recusal required, independent review required, record corrected, public notice required, contribution suspended, participation terminated, output withdrawn, benchmark withdrawn, routing corrected, non-continuation, or archive.

13.8.7.9 Boundary Incident Review shall preserve records even where the incident is resolved informally, unless deletion is required by law, privacy, security, protected knowledge, confidentiality, or other valid control.

13.8.7.10 Boundary Incident Review ensures that boundary failures are investigated through records rather than managed through reputation alone.

***

#### 13.8.8 Correction Measures

13.8.8.1 Correction Measures mean the tools available to repair, limit, clarify, withdraw, restrict, supersede, suspend, terminate, reroute, or archive sponsor or provider conduct, records, communications, outputs, access, recognition, contribution status, or pathway participation where conflict, overclaim, misuse, influence risk, public-safe risk, data risk, procurement risk, readiness risk, safeguard risk, or anti-capture concern arises.

13.8.8.2 Correction Measures may include revised language, withdrawal of claim, correction notice, public-safe clarification, controlled clarification, restriction of public communications, removal of unauthorized logo use, revision of Contribution Records, revision of conflict disclosures, revision of employer-affiliation disclosures, addition of boundary language, addition of no-control language, addition of no-validation language, addition of no-procurement language, addition of no-reliance language, addition of consent-boundary language, and archive update.

13.8.8.3 Correction Measures may include restricted access, access revocation, room exclusion, recusal, limited participation, independent review, reassignment of review, benchmark restriction, benchmark withdrawal, public authority room restriction, readiness-room restriction, secure-room access suspension, data-room access suspension, repository access suspension, technical mentor restriction, partner engineer restriction, or contributor communication restriction.

13.8.8.4 Correction Measures may include correction of Working Group outputs, Competence Cell records, public-safe summaries, readiness notes, Docket entries, ARL references, Grid input references where applicable, Routing Notes, National Continuation Records, Nexus Universe materials, National Node materials, case studies, public reports, public notices, public authority learning materials, sponsor materials, provider materials, investor materials, insurer materials, donor materials, public finance materials, procurement materials, and media materials.

13.8.8.5 Correction Measures may include suspension of sponsor status, suspension of provider status, suspension of contributor recognition, withdrawal of recognition, downgrade of recognition class, contribution restriction, contribution termination, non-continuation of the affected pathway, exclusion from future contribution opportunities, or archive.

13.8.8.6 Public notice shall be used where prior public exposure, public reliance, public authority confusion, procurement reliance, finance or insurance reliance, donor or public finance reliance, community consent confusion, Indigenous consent confusion where applicable, or public-safe harm requires external clarification. Controlled notice may be used where public notice would amplify sensitive information.

13.8.8.7 Correction shall be proportionate to risk but shall not be avoided because a contributor is important, prestigious, strategically useful, financially significant, technically critical, publicly visible, politically sensitive, or institutionally close.

13.8.8.8 Correction Measures convert boundary problems into repairable institutional records.

***

#### 13.8.9 Withdrawal or Termination

13.8.9.1 Withdrawal or Termination means the suspension, withdrawal, termination, exclusion, or non-continuation of sponsor or provider participation where serious conflict, misuse, breach, overclaim, public-safe risk, data risk, cyber risk, protected knowledge risk, anti-capture concern, procurement risk, readiness risk, public authority confusion, community harm, Indigenous safeguard concern where applicable, or repeated boundary failure makes continued participation unsafe or inconsistent with public-good purpose.

13.8.9.2 Withdrawal or termination may be applied where a sponsor or provider materially misuses Nexus names, claims validation, claims certification, implies endorsement, implies procurement status, implies public authority approval, implies financeability, implies insurability, implies donor commitment, implies public finance allocation, implies community consent, implies Indigenous consent where applicable, misuses benchmarks, suppresses limitations, manipulates outputs, violates confidentiality, misuses data, breaches access rules, breaches secure-room rules, breaches public-safe language rules, or refuses correction.

13.8.9.3 Withdrawal or termination may also apply where a sponsor or provider attempts hidden control, conditions support on outcomes, pressures researchers, interferes with Working Groups, interferes with Competence Cells, interferes with National Nodes, attempts to control public authority participation, attempts to control readiness translation, attempts to control routing, or uses participation for procurement, finance, insurance, donor, public finance, or market advantage inconsistent with Nexus boundaries.

13.8.9.4 Withdrawal may be temporary or permanent, partial or complete, public or controlled, recognition-specific, access-specific, pathway-specific, contribution-specific, room-specific, output-specific, or Nexus-wide, according to the severity and scope of the issue.

13.8.9.5 Termination shall be considered where misuse is serious, repeated, intentional, uncorrected, harmful, unsafe, deceptive, capture-seeking, legally risky, or incompatible with continued trust.

13.8.9.6 A Withdrawal or Termination Record shall identify the sponsor or provider, affected contribution, affected pathway, basis for action, records reviewed, conflicts, boundary incidents, correction attempts, public-safe risks, data risks, safeguard risks, national implications, recognition implications, access implications, communication restrictions, notice requirements, archive requirements, and future participation conditions where any exist.

13.8.9.7 Withdrawal or termination shall not prevent additional remedies under applicable agreements, policies, laws, institutional instruments, data rules, confidentiality obligations, security rules, or public authority requirements.

13.8.9.8 Withdrawal or termination protects the Contributor Program by making participation conditional on integrity, not merely capacity.

***

#### 13.8.10 Conflict and Anti-Capture Summary Clause

13.8.10.1 Partner participation remains legitimate only when conflicts are disclosed, affiliations are recorded, influence is assessed, capture is controlled, boundaries are enforceable, correction is mandatory, and withdrawal or termination is available where support becomes incompatible with public-good integrity.

13.8.10.2 Sponsor and Provider Conflict Disclosure requires sponsors and providers to disclose conflicts, commercial interests, procurement interests, investment interests, policy interests, public authority relationships, competitor relationships, and influence risks. Employer-Affiliation Disclosure requires participants, reviewers, mentors, volunteers, council members, Working Group participants, Competence Cell contributors, and technical leads to disclose employer affiliations and relevant institutional roles. Influence Risk Assessment applies where sponsors, providers, employers, capital readers, public authority actors, or institutional partners could influence agenda, records, claims, routing, or decisions. Anti-Capture Controls include balanced participation, recusal, limited access, independent review, public-safe review, record transparency, and stop-the-line authority. Recusal and Limited Participation apply where conflicts affect research selection, benchmark review, public claims, readiness translation, public authority outputs, procurement-sensitive matters, or provider-specific work. Sponsor and Provider Boundary Incidents include hidden control, agenda pressure, access misuse, data misuse, benchmark manipulation, overclaim, unauthorized status use, and public-safe language violations. Boundary Incident Review includes intake, fact record, affected outputs, risk assessment, correction path, communication controls, and archive. Correction Measures include revised language, withdrawal of claim, restricted access, recusal, suspension, public notice, revised Contribution Record, and routing correction. Withdrawal or Termination applies where serious conflict, misuse, breach, overclaim, public-safe risk, data risk, or anti-capture concern makes continued participation unsafe or inconsistent with public-good purpose.

13.8.10.3 No sponsor conflict disclosure, provider conflict disclosure, employer-affiliation disclosure, influence risk assessment, anti-capture control, recusal record, limited-participation record, Boundary Incident record, Boundary Incident Review, correction measure, withdrawal, termination, revised Contribution Record, communication hold, public notice, controlled clarification, access restriction, recognition limitation, benchmark correction, readiness correction, public authority correction, National Node correction, routing correction, non-continuation, or archive reference shall create certification, validation, recognition standing, maturity status, governance authority by default, public authority approval, procurement status, preferred-provider status, financeability, bankability, investability, insurability, underwriting acceptance, donor commitment, public finance allocation, official warning, emergency command, community consent, Indigenous consent, standards conformance, deployment authorization, project approval, handoff authorization, transaction, or execution authority by implication.

13.8.10.4 The controlling Conflict and Anti-Capture Formula is that sponsors and providers may participate only where interests are disclosed, affiliations are visible, influence is assessed, access is limited, conflicts are managed, independent review is available, public-safe claims are controlled, boundary incidents are corrected, and withdrawal remains possible; support is not control, affiliation is not authority, contribution is not preference, expertise is not validation, public authority proximity is not approval, readiness proximity is not finance, community proximity is not consent, and Nexus remains legitimate only while the public-good stack can say no, pause, correct, restrict, withdraw, and archive.

### 13.9 Equipment, Software, Services, Cloud Credits, Data Access, Travel Support, Volunteer Support, Event Support, Build-Crew Support, and In-Kind Contribution Records

#### 13.9.1 Equipment Contribution Records

13.9.1.1 Equipment Contribution Records shall be required for all donated, loaned, leased, temporarily provided, trial, prototype, pre-production, partner-owned, sponsor-supported, provider-supported, university-supported, public authority-supported, venue-supported, or otherwise contributed equipment used in Nexus Network, Nexus Universe, Nexus Acceleration, National Nexus Nodes, National Working Groups, Nexus Competence Cells, secure rooms, data rooms, clean rooms, compute-to-data environments, public-good software pathways, observability pathways, research workflows, event operations, or build-crew operations.

13.9.1.2 Each Equipment Contribution Record shall identify the contributor, item description, manufacturer, model, serial number or asset identifier where appropriate, quantity, ownership status, custody chain, location, permitted use, prohibited use, contribution duration, installation requirements, configuration requirements, safety requirements, access limits, authorized users, supervision requirements, insurance or liability conditions where applicable, maintenance obligations, return obligations, teardown requirements, disposal requirements, and archive status.

13.9.1.3 Equipment records shall distinguish donated equipment, loaned equipment, leased equipment, temporary equipment, evaluation equipment, pre-production equipment, prototype equipment, demonstration equipment, operational support equipment, research-only equipment, and equipment provided for public-good use with restrictions.

13.9.1.4 Equipment records shall identify whether the equipment involves compute, GPUs, accelerators, servers, storage, racks, networking devices, telecom equipment, AI-RAN or O-RAN components, sensors, robotics, drones, edge devices, lab devices, safety systems, power systems, cooling systems, secure-room systems, monitoring systems, access-control systems, or other technical infrastructure.

13.9.1.5 Equipment records shall identify safety, cybersecurity, data, geospatial, public authority, community, Indigenous where applicable, protected knowledge, export-control, venue, logistics, electrical, environmental, operational, and public-safe requirements relevant to the equipment.

13.9.1.6 Equipment provided for Nexus use shall not create provider validation, product endorsement, procurement status, preferred-provider status, safety certification, security certification, public authority approval, financeability, insurability, donor commitment, public finance allocation, deployment authorization, handoff authorization, or execution authority.

13.9.1.7 Equipment records shall include teardown and return obligations, including removal date, responsible party, inventory check, condition check, credential removal, data removal, configuration wipe where applicable, log preservation where required, packaging, shipping, insurance where applicable, and confirmation of return or disposition.

13.9.1.8 Equipment Contribution Records protect both the contributor and Nexus by ensuring that physical and technical assets are traceable, safe, bounded, and removable.

***

#### 13.9.2 Software Contribution Records

13.9.2.1 Software Contribution Records shall be required for all contributed software, software licenses, platform access, APIs, repositories, developer tools, AI tools, simulation tools, digital twin tools, geospatial tools, Earth observation tools, observability tools, workflow tools, cybersecurity tools, documentation systems, model registries, artifact registries, experiment tracking tools, collaboration tools, or public-good software components used in Nexus Network, Nexus Universe, Nexus Acceleration, National Nodes, Working Groups, Competence Cells, research workflows, secure rooms, data rooms, or public-good repositories.

13.9.2.2 Each Software Contribution Record shall identify the contributor, software name, version or build where available, license terms, access terms, user limits, permitted users, permitted uses, prohibited uses, duration, support period, update policy, security obligations, data handling terms, telemetry terms, logging terms, API limits, integration dependencies, IP conditions, confidentiality conditions, open-source or proprietary status, public-good use conditions, post-cycle access closure, and correction pathway.

13.9.2.3 Software records shall distinguish open-source software, public-good software, proprietary software, restricted software, pre-production software, research-only software, partner-confidential software, SaaS access, API access, trial software, discounted software, donated software, and software used only in controlled environments.

13.9.2.4 Software contributions involving AI, agentic workflows, data processing, public authority learning, readiness translation, observability, cybersecurity, sensitive data, protected knowledge, Indigenous knowledge where applicable, geospatial information, or secure-room workflows shall require heightened documentation, access controls, model or system cards where relevant, logging, output review, public-safe review, and correction pathways.

13.9.2.5 Software Contribution Records shall identify whether the software may store, process, transmit, learn from, log, retain, export, or expose data, prompts, outputs, configuration details, telemetry, credentials, metadata, public authority context, community inputs, Indigenous inputs where applicable, or protected knowledge.

13.9.2.6 Software contributions shall not create certification, validation, compliance approval, security approval, public authority approval, procurement qualification, preferred-provider status, financeability, insurability, deployment authorization, handoff authorization, or execution authority.

13.9.2.7 Post-cycle access closure shall include user removal, token revocation, credential rotation where needed, repository access review, API key revocation, data deletion or archive where required, license expiration, log preservation where required, and confirmation of closure.

13.9.2.8 Software Contribution Records ensure that digital tools can support public-good work without silently capturing data, claims, access, or downstream dependency.

***

#### 13.9.3 Services Contribution Records

13.9.3.1 Services Contribution Records shall be required for contributed services, including technical support, consulting, training, engineering, cybersecurity support, cloud architecture, data services, observability support, telecom support, AI support, simulation support, digital twin support, geospatial support, secure-room support, public-safe reporting support, documentation support, translation support, accessibility support, logistics support, operational support, and post-cycle debrief support.

13.9.3.2 Each Services Contribution Record shall identify the contributor, service description, service category, assigned personnel or role categories, scope, duration, expected outputs, permitted interactions, prohibited interactions, access rights, data exposure, confidentiality obligations, conflict disclosures, employer affiliations, supervision requirements, quality controls, public-safe limits, support boundaries, deliverable boundaries, and correction pathway.

13.9.3.3 Services records shall distinguish advisory services, technical services, operational services, engineering services, mentoring services, training services, support-desk services, incident-response services, documentation services, logistics services, accessibility services, translation services, and public-safe reporting services.

13.9.3.4 Services contributed by providers or sponsors shall be governed by support-without-control, provider-neutrality, procurement-neutrality, no-solicitation, no-pressure, non-influence, confidentiality, conflict, access-control, and claims-boundary rules.

13.9.3.5 Services Contribution Records shall identify whether the service provider may interact with researchers, public authorities, capital readers, insurers, donors, public finance readers, communities, Indigenous actors where applicable, media actors, Working Groups, Competence Cells, National Nodes, Nexus Universe teams, or secure-room users, and under what conditions.

13.9.3.6 Contributed services shall not create endorsement, certification, validation, procurement qualification, preferred-provider status, public authority approval, financeability, insurability, donor commitment, public finance allocation, community consent, Indigenous consent, deployment authorization, handoff authorization, transaction, or execution authority.

13.9.3.7 Services records shall include closure obligations, including final support date, access closure, deliverable status, confidentiality survival, records delivered, unresolved issues, incident reports, correction needs, and archive status.

13.9.3.8 Services Contribution Records make human and professional support visible, bounded, and accountable.

***

#### 13.9.4 Cloud Credit Records

13.9.4.1 Cloud Credit Records shall be required for all cloud credits, compute credits, platform credits, storage credits, AI credits, database credits, managed service credits, developer credits, security service credits, observability credits, or other account-based contribution credits provided to Nexus Network, Nexus Universe, Nexus Acceleration, National Nodes, Working Groups, Competence Cells, research workflows, secure rooms, data rooms, or public-good software pathways.

13.9.4.2 Each Cloud Credit Record shall identify the contributor, credit amount or credit basis, account structure, billing owner, usage owner, permitted workloads, prohibited workloads, authorized users, account permissions, cost controls, billing alerts, overage responsibility, expiration date, service scope, region or residency limits, data controls, logging requirements, security controls, support contacts, teardown obligations, and access closure process.

13.9.4.3 Cloud Credit Records shall identify whether credits may be used for compute, GPUs, storage, databases, AI services, model training, inference, data processing, observability, cybersecurity, simulation, digital twins, geospatial processing, public authority learning, readiness rooms, secure rooms, or public-good repositories.

13.9.4.4 Cloud credits shall be subject to workload classification, data classification, public-safe classification, security review, access review, and cost monitoring before use for sensitive, restricted, public authority, community-sensitive, Indigenous-sensitive where applicable, cyber-sensitive, health-sensitive, infrastructure-sensitive, protected knowledge, or finance-sensitive workloads.

13.9.4.5 Cloud Credit Records shall identify responsibility for charges beyond the credit amount, unauthorized usage, unused credits, expired credits, suspended credits, transferred credits, and account closure.

13.9.4.6 Cloud credit support shall not create endorsement of the cloud provider, preferred-provider status, procurement qualification, platform validation, public authority approval, financeability, insurability, deployment authorization, handoff authorization, or execution authority.

13.9.4.7 Cloud Credit Records shall include no-endorsement, no-preference, no-validation, no-procurement, and no-control language where the contribution may be publicly acknowledged or used in partner communications.

13.9.4.8 Cloud Credit Records prevent donated capacity from becoming unmanaged spend, uncontrolled access, or implied platform endorsement.

***

#### 13.9.5 Data Access Records

13.9.5.1 Data Access Records shall be required for any dataset, data feed, data platform, data room, telemetry stream, sensor stream, Earth observation source, geospatial dataset, public dataset, partner dataset, protected dataset, synthetic dataset, derived dataset, restricted dataset, confidential dataset, public authority dataset, community dataset, Indigenous dataset where applicable, health-sensitive dataset, cyber-sensitive dataset, infrastructure-sensitive dataset, or finance-sensitive dataset used in Nexus Network, Nexus Universe, Nexus Acceleration, National Nodes, Working Groups, Competence Cells, research workflows, observability, public authority learning, readiness translation, or public-safe reporting.

13.9.5.2 Each Data Access Record shall identify dataset identity, source, provenance, rights, permissions, lawful basis where applicable, sensitivity classification, data residency, data sovereignty considerations, authorized users, permitted uses, prohibited uses, access method, compute-to-data requirements, clean-room requirements, no-download requirements, storage conditions, transfer restrictions, retention period, deletion requirements, output review, publication limits, audit logs, and correction pathway.

13.9.5.3 Data Access Records shall identify whether data involve personal information, rights-bearing data, health-sensitive data, community-sensitive data, Indigenous knowledge or Indigenous data where applicable, protected knowledge, sensitive ecological information, sensitive geospatial information, critical infrastructure information, cyber-sensitive information, public authority information, partner-confidential information, market-sensitive information, or finance-sensitive information.

13.9.5.4 Compute-to-data shall be the preferred pathway for sensitive, restricted, sovereign, public authority, protected knowledge, health-sensitive, cyber-sensitive, community-sensitive, Indigenous-sensitive where applicable, or infrastructure-sensitive datasets where data export would create unacceptable risk.

13.9.5.5 Data Access Records shall identify audit requirements, including access logs, query logs where appropriate, download attempts, export attempts, output approvals, user identity, purpose, date, system, incident events, deletion confirmation, and archive references.

13.9.5.6 Data outputs shall be subject to public-safe review, data rights review, privacy review, cyber review, protected knowledge review, Indigenous safeguard review where applicable, sensitive geospatial review, public authority boundary review, and publication review as applicable.

13.9.5.7 Data access shall not create ownership transfer, publication rights, reuse rights, public authority approval, community consent, Indigenous consent where applicable, research validation, benchmark validation, financeability, insurability, procurement status, deployment authorization, handoff authorization, or execution authority.

13.9.5.8 Data Access Records protect data subjects, communities, public authorities, contributors, researchers, and Nexus institutions by making data use lawful, limited, logged, and correctionable.

***

#### 13.9.6 Travel and Researcher Access Support Records

13.9.6.1 Travel and Researcher Access Support Records shall be required for all travel, accommodation, visa support, access support, fellowship support, stipend support, scholarship support, registration support, researcher access support, student support, fellow support, volunteer support, community participant support, Indigenous participant support where applicable, youth support, diaspora support, accessibility support, and participation support connected to Nexus Universe, Nexus Network, Nexus Acceleration, National Nodes, Working Groups, Competence Cells, public authority learning, research workflows, or public-good pathways.

13.9.6.2 Each Travel and Researcher Access Support Record shall identify the support provider, support type, beneficiary category, eligibility criteria, selection process, selection steward, selection independence controls, support amount or in-kind description where appropriate for internal records, duration, restrictions, reporting requirements, conflicts, confidentiality conditions, safeguarding requirements, accessibility requirements, public-safe classification, recognition limits, and correction pathway.

13.9.6.3 Support shall be administered through transparent, recorded, non-discriminatory, safeguard-aware, public-good criteria appropriate to the pathway, and shall not be controlled by sponsors, providers, donors, capital readers, insurers, public finance readers, public authorities, universities, media actors, or other contributors except through a recorded and non-controlling support role.

13.9.6.4 Travel, access, fellowship, stipend, or participation support shall not influence research selection, research outcomes, benchmark conclusions, publication outcomes, public-safe reporting, readiness notes, public authority learning, community participation content, Indigenous participation content where applicable, awards, routing, or lawful handoff dependency decisions.

13.9.6.5 Beneficiary selection shall be independent from contributor commercial interests, provider interests, sponsor interests, public authority interests, capital-reader interests, insurer interests, donor interests, public finance interests, media interests, and procurement interests.

13.9.6.6 Support records shall identify any conditions imposed on the beneficiary, including attendance, reporting, participation, confidentiality, conduct, public-safe communication, travel documentation, accessibility accommodation, safeguarding, and expense documentation conditions.

13.9.6.7 Travel and access support shall not create employment, agency, endorsement, sponsor control, provider preference, public authority status, financeability, insurability, community consent, Indigenous consent where applicable, deployment authorization, handoff authorization, or execution authority.

13.9.6.8 Travel and Researcher Access Support Records ensure that access support expands participation without purchasing influence over people or outputs.

***

#### 13.9.7 Volunteer Support Records

13.9.7.1 Volunteer Support Records shall be required for all volunteer roles supporting Nexus Network, Nexus Universe, Nexus Acceleration, National Nodes, Working Groups, Competence Cells, public authority learning, readiness rooms, secure rooms, data rooms, research workflows, public-safe reporting, translation, accessibility, logistics, documentation, build crews, public-good software, observability, or event operations.

13.9.7.2 Each Volunteer Support Record shall identify the volunteer, role, time commitment, affiliation disclosures, employer affiliation where relevant, sponsor or provider affiliation where relevant, conflict disclosures, assigned supervisor, permitted activities, prohibited activities, confidentiality obligations, conduct rules, safeguarding obligations, access permissions, data access limits, system access limits, public-safe restrictions, training requirements, boundary letter, and correction pathway.

13.9.7.3 Volunteer roles may include event support, documentation support, research support, translation support, accessibility support, logistics support, public-safe reporting support, technical support, build-crew support, repository support, data organization support, community support, and National Node support, subject to qualification, supervision, and safeguards.

13.9.7.4 Volunteers shall operate under role-specific access and shall not receive access to restricted data, public authority-sensitive information, protected knowledge, Indigenous knowledge where applicable, unpublished research, secure-room outputs, readiness-room records, capital-reader room materials, or confidential partner records unless expressly authorized and necessary for the assigned role.

13.9.7.5 Volunteers shall not use their role to claim authority, represent Nexus without authorization, solicit commercial relationships, influence researchers, influence public authority participants, influence community participants, influence Indigenous participants where applicable, control outputs, access restricted materials improperly, or make public claims.

13.9.7.6 Volunteer Support Records shall include conduct expectations, including non-harassment, non-discrimination, confidentiality, no-solicitation, no-pressure, no-unauthorized-communications, public-safe conduct, data protection, accessibility, safeguard respect, and correction cooperation.

13.9.7.7 Volunteer participation shall not create employment, agency, governance status, public authority status, certification authority, procurement authority, finance authority, consent authority, deployment authority, handoff authority, or execution authority.

13.9.7.8 Volunteer Support Records protect volunteers and Nexus by making informal support formal enough to be safe.

***

#### 13.9.8 Event and Build-Crew Support Records

13.9.8.1 Event and Build-Crew Support Records shall be required for all event operations, venue support, logistics support, production support, technical operations, build-crew roles, translation support, interpretation support, accessibility support, communications support, public-safe reporting support, secure-room operations, data-room operations, network operations, compute operations, stage operations, signage, media operations, registration, safety support, teardown support, and post-cycle operational support.

13.9.8.2 Each Event and Build-Crew Support Record shall identify the support provider, support category, assigned personnel or role classes, supported activity, location, time period, supervisor, access rights, restricted areas, systems access, equipment access, data exposure, public-facing role, confidentiality obligations, safety obligations, accessibility obligations, communications limits, emergency procedures, teardown obligations, and correction pathway.

13.9.8.3 Build-crew records shall identify technical stack responsibilities, including compute setup, cloud setup, networking, telecom, secure rooms, data rooms, clean rooms, observability dashboards, repository systems, AI workflows, simulation workflows, digital twin environments, cybersecurity controls, monitoring, logging, access provisioning, access closure, equipment inventory, and teardown.

13.9.8.4 Event support records shall distinguish public areas, controlled areas, restricted areas, secure rooms, public authority rooms, readiness rooms, research rooms, community spaces, Indigenous spaces where applicable, media spaces, technical operations spaces, and no-access areas.

13.9.8.5 Communications support shall be subject to public-safe language, sponsor/provider claims limits, public authority boundary language, readiness boundary language, consent-boundary language, approved statements, and correction obligations.

13.9.8.6 Translation, interpretation, and accessibility support shall preserve meaning, confidentiality, protected knowledge, Indigenous protocol limits where applicable, public-safe restrictions, accessibility requirements, and correction pathways.

13.9.8.7 Build-crew and event support shall not create authority to speak for Nexus, approve outputs, certify systems, validate providers, authorize access beyond assigned scope, control public authority rooms, control readiness rooms, control community spaces, control Indigenous spaces where applicable, control public-safe reporting, or execute projects.

13.9.8.8 Event and Build-Crew Support Records ensure that temporary operations are safe, bounded, accessible, public-safe, and removable.

***

#### 13.9.9 In-Kind Contribution Controls

13.9.9.1 In-Kind Contribution Controls shall govern non-cash contributions to ensure valuation transparency, no-control status, conflict disclosure, use limits, access limits, public-safe acknowledgment, recognition boundaries, correctionability, and archive.

13.9.9.2 In-kind contributions may include equipment, software, services, cloud credits, data access, compute, networking, telecom, cybersecurity, AI platforms, simulation tools, digital twin tools, observability dashboards, secure rooms, clean rooms, data rooms, travel support, volunteer time, event support, venue support, training, translation, accessibility, communications, documentation, and build-crew support.

13.9.9.3 Each in-kind contribution shall be recorded with contribution type, contributor identity, valuation basis where appropriate, conditions, restrictions, duration, access rights, ownership or license terms, data exposure, confidentiality, conflicts, permitted use, prohibited use, public-safe acknowledgment terms, no-control language, teardown or closure requirements, and correction pathway.

13.9.9.4 In-kind valuation shall be approximate where appropriate and shall identify the basis of valuation, including market value, replacement value, list value, discounted value, internal estimate, credit amount, time estimate, or non-valued status where valuation is inappropriate, confidential, misleading, or unnecessary.

13.9.9.5 In-kind contributions shall not be used to purchase agenda influence, public visibility, research selection, room access, provider preference, public authority proximity, readiness influence, benchmark interpretation, public-safe reporting influence, National Node routing, lawful handoff access, or procurement advantage.

13.9.9.6 Public-safe acknowledgment of in-kind contributions shall be accurate, proportionate, contribution-specific, non-promotional where required, and subject to approved claims language.

13.9.9.7 If a contribution description becomes inaccurate, incomplete, overstated, understated, misleading, conflict-affected, no longer current, or inconsistent with contribution conditions, the Contribution Record and any acknowledgment shall be corrected, restricted, withdrawn, superseded, downgraded, or archived.

13.9.9.8 In-Kind Contribution Controls ensure that non-cash support is treated with the same integrity discipline as cash support.

***

#### 13.9.10 Contribution Record Summary Clause

13.9.10.1 Contribution records protect contributors, Nexus institutions, researchers, public authorities, communities, Indigenous actors where applicable, participants, partners, sponsors, providers, volunteers, National Nodes, Working Groups, Competence Cells, and the public by making support transparent, bounded, secure, public-safe, conflict-aware, non-controlling, and correctionable.

13.9.10.2 Equipment Contribution Records govern donated, loaned, leased, or temporary equipment, including item description, ownership, custody, location, condition, safety requirements, access limits, return obligations, and teardown. Software Contribution Records govern license, access terms, user limits, data handling, security obligations, permitted uses, restrictions, support period, and post-cycle access closure. Services Contribution Records govern technical support, consulting, training, engineering, cybersecurity, data services, cloud architecture, observability support, and operational support. Cloud Credit Records govern credit amount, account structure, permitted workloads, billing controls, data controls, expiration, overage responsibility, access closure, and no-endorsement language. Data Access Records govern dataset identity, rights, permissions, sensitivity, authorized users, compute-to-data controls, retention, deletion, publication limits, and audit logs. Travel and Researcher Access Support Records govern travel, accommodation, access, fellowships, stipends, and participation support, including eligibility, selection independence, restrictions, reporting, and no-influence conditions. Volunteer Support Records govern roles, time commitments, affiliation disclosures, confidentiality obligations, conduct rules, supervision, access permissions, and boundary letters. Event and Build-Crew Support Records govern event operations, venue support, logistics, build crew, technical operations, translation, accessibility, communications, public-safe reporting, and teardown support. In-Kind Contribution Controls ensure valuation transparency, no-control status, conflict disclosure, use limits, public-safe acknowledgment, and correction if contribution descriptions become inaccurate.

13.9.10.3 No Equipment Contribution Record, Software Contribution Record, Services Contribution Record, Cloud Credit Record, Data Access Record, Travel and Researcher Access Support Record, Volunteer Support Record, Event and Build-Crew Support Record, In-Kind Contribution Record, contribution valuation, contribution acknowledgment, access record, support record, teardown record, closure record, correction record, withdrawal record, supersession record, public notice, controlled notice, or archive reference shall create certification, validation, recognition standing, maturity status, governance authority by default, public authority approval, procurement status, preferred-provider status, financeability, bankability, investability, insurability, underwriting acceptance, donor commitment, public finance allocation, official warning, emergency command, community consent, Indigenous consent, standards conformance, deployment authorization, project approval, handoff authorization, transaction, or execution authority by implication.

13.9.10.4 The controlling Contribution Record Formula is that every contributed asset, service, credit, dataset, access pathway, volunteer role, event role, and build-crew role must be described before use, limited during use, closed after use, corrected if misdescribed, and archived when complete; contribution records create transparency, not entitlement, support, not control, access, not ownership, acknowledgment, not endorsement, capacity, not authority, and public-good continuity, not execution.

### 13.10 Partner Exit, Teardown, Access Closure, Data Closure, Credential Closure, Equipment Return, Debrief, Lessons Learned, Contribution Archive, and Correction

#### 13.10.1 Partner Exit Conditions

13.10.1.1 Partner Exit Conditions mean the circumstances under which a partner, sponsor, provider, contributor, technical mentor, partner engineer, infrastructure supporter, cloud contributor, software contributor, data contributor, secure-room supporter, event supporter, build-crew supporter, travel supporter, volunteer supporter, or other contribution participant exits, completes, pauses, withdraws, is suspended, is terminated, or is otherwise closed out from Nexus Network, Nexus Universe, Nexus Acceleration, National Nexus Nodes, National Working Groups, Nexus Competence Cells, public authority learning rooms, readiness rooms, secure rooms, data rooms, public-good repositories, or related public-good pathways.

13.10.1.2 Partner exit may occur by planned completion, annual-cycle completion, post-cycle teardown, completion of contribution scope, expiration of access term, expiration of cloud credits or software licenses, completion of equipment loan, completion of support period, non-renewal, mutual termination, contributor withdrawal, contribution replacement, contribution supersession, workstream retirement, non-continuation, archive, breach, conflict concern, Boundary Incident, security issue, data issue, confidentiality issue, public-safe concern, anti-capture concern, legal constraint, safeguard issue, public authority boundary issue, procurement sensitivity, readiness boundary issue, or loss of fit with public-good purpose.

13.10.1.3 Every material partner exit shall be recorded through an Exit Record or equivalent closure record identifying the partner, contribution record, exit basis, affected systems, affected rooms, affected users, affected records, affected data, affected credentials, affected equipment, affected software, affected cloud accounts, affected public acknowledgments, affected claims, teardown requirements, access-closure requirements, data-closure requirements, credential-closure requirements, equipment-return requirements, debrief requirements, lessons-learned requirements, correction requirements, and archive status.

13.10.1.4 Planned exit shall be addressed at the time of contribution acceptance. Contribution Records shall identify expected end date or closure trigger, teardown duties, access closure, data closure, credential closure, equipment return, license survival or expiration, confidentiality survival, public acknowledgment status, archive class, and correction obligations.

13.10.1.5 Unplanned exit shall require risk review proportionate to the reason for exit. Where exit is caused by breach, conflict concern, Boundary Incident, security issue, data issue, public-safe risk, safeguard risk, sponsor overclaim, provider overclaim, procurement sensitivity, readiness misuse, or public authority confusion, the Exit Record shall identify immediate containment measures, communication controls, correction path, notice requirements, and archive treatment.

13.10.1.6 Partner exit shall not erase prior records unless deletion is required by law, privacy, security, protected knowledge, confidentiality, data rights, Indigenous protocol where applicable, or other valid control. Completed, withdrawn, terminated, or non-renewed contributions shall remain traceable according to their public-safe and access classifications.

13.10.1.7 Partner exit shall not imply disapproval, approval, certification, validation, procurement status, financeability, insurability, donor commitment, public finance allocation, public authority approval, community consent, Indigenous consent, deployment authorization, handoff authorization, transaction, or execution authority. It means the contribution relationship or access pathway has ended or changed under the recorded condition.

13.10.1.8 Partner exit is a governance event, not an administrative afterthought.

***

#### 13.10.2 Teardown Requirements

13.10.2.1 Teardown Requirements mean the mandatory closure, removal, deconfiguration, decommissioning, transfer, return, archival, or controlled continuation actions required for partner-provided equipment, cloud environments, software access, data platforms, secure rooms, clean rooms, data rooms, dashboards, integrations, APIs, network links, telecom environments, temporary accounts, live operations tools, public-good repositories, observability systems, workflow systems, and other contributed stack components.

13.10.2.2 Teardown shall be required at the end of the authorized period, contribution term, Nexus Universe cycle, research workflow, Working Group assignment, Competence Cell assignment, secure-room operation, data-room operation, cloud-credit period, software access period, event operation, build-crew operation, or partner support period, unless a separate continuation record lawfully authorizes continued use.

13.10.2.3 Each Teardown Record shall identify the component, contributor, supported pathway, responsible steward, teardown date or trigger, systems affected, users affected, data affected, credentials affected, integrations affected, dependencies affected, records to preserve, records to close, equipment to return, software access to close, accounts to deactivate, logs to preserve, data to retain, data to delete, data to return, public-safe considerations, security considerations, and completion confirmation.

13.10.2.4 Teardown of cloud environments shall address account closure, user removal, role removal, billing closure, credit expiration, workload termination, storage review, log preservation, snapshot handling, backup deletion or archive, key revocation, API deactivation, region or residency requirements, and cost overrun review.

13.10.2.5 Teardown of software and platform access shall address license expiration, user deprovisioning, token revocation, API key removal, repository access closure, model registry closure, artifact storage review, telemetry closure, data export restrictions, documentation survival, and post-cycle support obligations.

13.10.2.6 Teardown of data platforms, secure rooms, clean rooms, data rooms, and compute-to-data environments shall address approved workload closure, output review, no-download confirmation, access logs, data retention, data deletion, data return, restricted-output archive, user removal, room closure, audit record, and incident review where required.

13.10.2.7 Teardown of dashboards, observability tools, network links, telecom environments, APIs, integrations, and live operations tools shall address data feeds, credentials, endpoints, routing rules, monitoring rules, logs, alerting, telemetry, public-safe visibility, sensitive geospatial exposure, public authority-sensitive information, and continuity dependencies.

13.10.2.8 Teardown shall not be delayed because a contributor wishes to preserve market visibility, technical dependency, public authority proximity, researcher access, data access, readiness-room access, or future handoff advantage.

13.10.2.9 Teardown is complete only when the relevant systems, access, data, credentials, equipment, records, public acknowledgments, and correction obligations have been closed, continued under record, or archived.

***

#### 13.10.3 Access Closure

13.10.3.1 Access Closure means the process of closing, revoking, limiting, disabling, transferring, or reclassifying partner, mentor, engineer, researcher, volunteer, sponsor, provider, contributor, public authority learner, readiness-room participant, Working Group participant, Competence Cell contributor, build-crew member, and other authorized-user access to systems, rooms, records, repositories, dashboards, logs, datasets, secure environments, public-safe drafts, unpublished outputs, and restricted records after the authorized period ends or the access is no longer needed.

13.10.3.2 Access Closure shall apply to physical spaces, digital systems, cloud accounts, compute environments, secure rooms, clean rooms, data rooms, public authority rooms, readiness rooms, capital-reader rooms, insurer-reader rooms, donor-reader rooms, community spaces, Indigenous spaces where applicable, event spaces, repositories, documentation systems, ticketing systems, dashboards, logs, communication channels, data feeds, APIs, storage, and archives.

13.10.3.3 Each Access Closure Record shall identify the person, role, affiliation, access type, system or room, access basis, access start date, access end date, closure trigger, closure action, residual access if any, logs reviewed, credentials revoked, materials returned, confidentiality survival, data handling status, records affected, and steward confirmation.

13.10.3.4 Access shall be closed promptly upon expiration of authorization, completion of task, departure from role, end of Nexus Universe cycle, workstream retirement, non-continuation, contribution withdrawal, contribution termination, conflict concern, Boundary Incident, security issue, data issue, confidentiality concern, public-safe issue, or access no longer being necessary under least-privilege and need-to-know principles.

13.10.3.5 Access Closure shall verify that no user retains unauthorized access to raw data, restricted data, protected knowledge, Indigenous knowledge where applicable, public authority-sensitive information, community-sensitive information, health-sensitive information, cyber-sensitive information, sensitive geospatial information, finance-sensitive information, market-sensitive information, unpublished research, readiness notes, Docket materials, Handoff Dependency Notes, public-safe drafts, or confidential partner materials.

13.10.3.6 Access Closure shall include review of group memberships, repository permissions, room permissions, cloud roles, IAM roles, SSH keys, API keys, tokens, dashboards, shared drives, collaboration tools, mailing lists, communication channels, ticket queues, event credentials, physical badges, room keys, temporary passes, and delegated permissions.

13.10.3.7 Residual access shall be permitted only where separately recorded, justified, time-limited, classified, and subject to continued confidentiality, logging, and review.

13.10.3.8 Access Closure shall not be confused with deletion of institutional memory. Access may close while records remain archived, controlled, restricted, or preserved according to law, policy, public-safe classification, and safeguard requirements.

13.10.3.9 Access Closure restores the principle that contribution access is temporary, purpose-bound, revocable, and never a continuing entitlement.

***

#### 13.10.4 Data Closure

13.10.4.1 Data Closure means the process for resolving the status of data, datasets, data feeds, derived data, synthetic data, logs, outputs, secure-room records, clean-room outputs, compute-to-data outputs, public authority data, community data, Indigenous data where applicable, protected knowledge, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, geospatial data, partner data, and other controlled information after a contribution, workstream, room, environment, or access period ends.

13.10.4.2 Data Closure shall determine whether data must be retained, deleted, returned, archived, redacted, anonymized, aggregated, restricted, transferred to a lawful steward, preserved under legal hold, preserved for reproducibility, preserved for audit, preserved for public-safe reporting, or destroyed according to applicable rights, permissions, law, policy, contributor terms, data-sharing terms, community safeguards, Indigenous protocols where applicable, public authority conditions, and public-safe classifications.

13.10.4.3 Each Data Closure Record shall identify dataset identity, source, steward, permitted use, actual use, authorized users, access history, outputs produced, derived records, sensitivity class, public-safe class, retention basis, deletion basis, return basis, archive class, audit logs, output review status, publication limits, correction needs, and confirmation of closure.

13.10.4.4 Data Closure for clean rooms, secure rooms, no-download environments, confidential computing, compute-to-data environments, and data rooms shall include confirmation of approved workloads, output review, export review, query logs where appropriate, download attempt review, residual file review, temporary storage deletion, cache deletion where applicable, credential revocation, access log preservation, and closure of user sessions.

13.10.4.5 Data Closure shall ensure that partner data, contributor data, public authority data, community data, Indigenous data where applicable, protected knowledge, confidential information, and restricted datasets are not retained, copied, exported, reused, trained on, published, or archived beyond the recorded permissions.

13.10.4.6 Data Closure shall address derivative outputs, including summaries, embeddings, models, transformed datasets, benchmark outputs, dashboards, maps, screenshots, logs, simulations, digital twin outputs, AI outputs, public-safe summaries, readiness notes, and research artifacts, and shall classify whether each may be retained, redacted, restricted, published, returned, deleted, or archived.

13.10.4.7 Data Closure shall preserve audit logs where required for accountability, reproducibility, security, correction, public-safe review, legal obligations, data protection obligations, protected knowledge obligations, Indigenous protocol obligations where applicable, or incident response.

13.10.4.8 Data Closure shall not create new data rights, publication rights, reuse rights, public authority approval, community consent, Indigenous consent, financeability, insurability, procurement status, deployment authorization, handoff authorization, or execution authority.

13.10.4.9 Data Closure is the discipline by which sensitive information leaves active use without leaving uncontrolled residue.

***

#### 13.10.5 Credential Closure

13.10.5.1 Credential Closure means the revocation, rotation, invalidation, deactivation, expiry, transfer, audit, or closure of credentials, secrets, keys, tokens, passwords, certificates, API keys, SSH keys, service accounts, admin accounts, user accounts, federated identities, hardware tokens, physical badges, room keys, temporary passes, and other access mechanisms used in partner-supported Nexus environments.

13.10.5.2 Credential Closure shall occur when the authorized access period ends, when a user role ends, when a contribution ends, when teardown occurs, when a security event occurs, when a Boundary Incident occurs, when a conflict requires access restriction, when credentials are suspected of compromise, when least-privilege review requires reduction, or when the credential is no longer necessary.

13.10.5.3 Each Credential Closure Record shall identify the credential type, system, account, user or service identity, issuing authority, access scope, creation date, closure trigger, closure action, revocation date, rotation status, residual dependency, audit review, affected systems, responsible steward, and confirmation of least-privilege restoration.

13.10.5.4 Credential Closure shall include revocation of user accounts, service accounts, API keys, OAuth tokens, SSH keys, cloud keys, encryption keys where appropriate, temporary passwords, federated access, repository credentials, CI/CD credentials, dashboard access, database access, VPN access, remote-access tools, room badges, physical keys, and privileged access.

13.10.5.5 Secret rotation shall occur where credentials may have been exposed, where partner engineers or technical mentors had privileged access, where shared credentials were discovered, where access logs indicate unusual activity, where a breach or suspected breach occurs, where personnel change, or where closure cannot be confirmed by revocation alone.

13.10.5.6 Credential Closure shall include audit review of use, including last login, privileged actions, data exports, repository changes, configuration changes, storage access, log access, API use, failed attempts, unusual access, and access after expected closure.

13.10.5.7 Credential Closure shall confirm restoration of least privilege, removal of dormant accounts, removal of temporary roles, removal of emergency access, removal of contributor access, and closure of unauthorized privilege escalation pathways.

13.10.5.8 Credential Closure shall be documented before teardown is considered complete where credentials could affect systems, data, repositories, rooms, dashboards, cloud environments, secure environments, or public-safe records.

13.10.5.9 Credential Closure prevents temporary contribution access from becoming permanent hidden control.

***

#### 13.10.6 Equipment Return and Sanitization

13.10.6.1 Equipment Return and Sanitization means the process for returning, transferring, wiping, sanitizing, decommissioning, inventorying, transporting, repairing, disposing, or archiving donated, loaned, leased, temporarily provided, pre-production, prototype, or partner-owned equipment used in Nexus Network, Nexus Universe, Nexus Acceleration, National Nodes, Working Groups, Competence Cells, secure rooms, data rooms, clean rooms, events, or build operations.

13.10.6.2 Equipment Return and Sanitization shall apply to servers, storage devices, laptops, desktops, accelerators, GPUs, edge devices, sensors, telecom equipment, networking equipment, routers, switches, lab devices, robotics, drones, removable media, monitoring devices, access-control devices, badge systems, mobile devices, cameras, recording equipment, testing equipment, and other technical or operational equipment.

13.10.6.3 Each Equipment Return and Sanitization Record shall identify the equipment, asset identifier, contributor, custodian, location, ownership status, condition at receipt, condition at return, data-bearing status, configuration status, sanitization requirement, sanitization method, credential removal, log preservation where required, damage report, missing item report, secure transport method, custody transfer, return date, receiving party, and archive status.

13.10.6.4 Equipment containing or capable of containing data shall be reviewed for residual data, logs, credentials, cached data, configuration files, datasets, outputs, user accounts, access tokens, encryption keys, telemetry, screenshots, sensor records, public authority information, community information, Indigenous information where applicable, protected knowledge, cyber-sensitive information, or partner-confidential information before return, reuse, transfer, disposal, or archive.

13.10.6.5 Sanitization may include wiping, secure deletion, cryptographic erasure, factory reset, credential removal, key destruction, storage removal, drive destruction where required, configuration reset, log extraction and preservation where required, firmware review where appropriate, and confirmation of completion.

13.10.6.6 Equipment return shall include inventory reconciliation, custody chain confirmation, packing, labeling, transport security, insurance where applicable, export or import compliance where applicable, hazardous or battery handling where applicable, damage reporting, missing equipment reporting, and final receipt confirmation.

13.10.6.7 Equipment that cannot be returned safely, lawfully, securely, or according to contribution terms shall be escalated for legal, security, contributor, safeguard, and archive review.

13.10.6.8 Equipment Return and Sanitization shall not create certification, validation, procurement status, endorsement, financeability, insurability, public authority approval, deployment authorization, handoff authorization, or execution authority for the equipment, contributor, or downstream use.

13.10.6.9 Equipment Return and Sanitization ensures that the physical stack exits as safely as it entered.

***

#### 13.10.7 Partner Debrief

13.10.7.1 Partner Debrief means the structured post-contribution review with a partner, sponsor, provider, contributor, technical mentor group, partner engineer group, university, cloud provider, telecom provider, cybersecurity contributor, data contributor, software contributor, secure-room supporter, event supporter, build-crew supporter, or other support actor concerning contribution performance, support quality, access issues, data issues, security issues, operational issues, claims boundaries, researcher feedback, public-safe controls, teardown, lessons learned, correction needs, and future contribution opportunities.

13.10.7.2 A Partner Debrief shall be required for material contributions, high-risk contributions, Nexus Universe stack contributions, secure-room contributions, data contributions, public authority-sensitive contributions, readiness-room contributions, pre-production technology contributions, benchmark-related contributions, cloud or compute contributions, cyber-sensitive contributions, public-facing contributions, or contributions affected by incidents, corrections, conflicts, or boundary concerns.

13.10.7.3 Each Partner Debrief Record shall identify the contributor, contribution record, debrief participants, debrief date, contribution scope, actual use, technical performance, support quality, researcher feedback, Working Group feedback, Competence Cell feedback, public authority learning feedback where appropriate, access issues, data issues, security issues, safeguard issues, public-safe issues, readiness issues, benchmark issues, claims-boundary issues, teardown status, correction status, and future contribution recommendations.

13.10.7.4 Partner Debriefs may address what worked, what failed, what was underused, what created risk, what required correction, what created confusion, what created dependency, what improved research production, what improved secure operation, what improved public-safe reporting, and what should be changed for future cycles.

13.10.7.5 Partner Debriefs shall not become sales meetings, procurement discussions, investment discussions, insurance discussions, donor allocation discussions, public finance discussions, public authority approval discussions, or negotiation of handoff unless separately and lawfully routed through the appropriate non-Nexus or lawful pathway.

13.10.7.6 Partner Debriefs shall include claims-boundary review where the partner may wish to reference its contribution, researcher feedback, technical performance, public-safe summaries, Nexus Universe role, National Node role, Working Group support, Competence Cell support, public authority room support, readiness-room support, or post-cycle lessons.

13.10.7.7 Partner Debriefs may identify future contribution opportunities, but future support shall require new or renewed Contribution Records, conflict review, access review, public-safe review, anti-capture review, and boundary terms.

13.10.7.8 Partner Debriefs make contribution relationships learnable without turning debrief into approval, procurement, finance, or endorsement.

***

#### 13.10.8 Lessons Learned

13.10.8.1 Lessons Learned Records shall identify what worked, what failed, what created risk, what should be corrected, what should be renewed, what should be retired, what should be restricted, what should be archived, and what should inform next-cycle partner engagement, Nexus Universe build, Nexus Network improvement, National Node preparation, Working Group production, Competence Cell assignment, public-safe reporting, readiness-room design, secure-room design, data-room design, contribution records, access controls, and teardown.

13.10.8.2 Lessons Learned shall be produced after material contribution cycles, Nexus Universe cycles, temporary stack operations, secure-room operations, cloud or compute contributions, data contributions, public authority learning room operations, readiness room operations, event operations, build-crew operations, major partner support, boundary incidents, security incidents, public-safe incidents, or significant corrections.

13.10.8.3 Each Lessons Learned Record shall identify the source contribution, pathway, participants or participant classes where appropriate, operational lessons, technical lessons, evidence lessons, data lessons, security lessons, access lessons, safeguard lessons, public-safe lessons, readiness lessons, public authority boundary lessons, community safeguard lessons, Indigenous safeguard lessons where applicable, provider-neutrality lessons, sponsor-control lessons, procurement-neutrality lessons, claims lessons, teardown lessons, and archive lessons.

13.10.8.4 Lessons Learned shall identify whether templates, contribution terms, access controls, data rules, credential rules, teardown procedures, mentor rules, partner engineer rules, benchmark rules, publication rules, recognition rules, public notice controls, conflict disclosures, anti-capture controls, or correction procedures should be updated.

13.10.8.5 Lessons Learned shall preserve both positive and negative learning. It shall record contributions that strengthened capacity and contributions that created friction, risk, confusion, underuse, overclaim, dependency, conflict, safeguard difficulty, or closure burden.

13.10.8.6 Lessons Learned may be public, controlled, restricted, confidential, redacted, delayed, no-publication, or archived according to public-safe, confidentiality, data, cyber, protected knowledge, public authority, community, Indigenous where applicable, market-sensitive, and legal conditions.

13.10.8.7 Lessons Learned shall feed next-cycle partner engagement, contribution design, Nexus Universe preparation, Nexus Network improvement, National Node support, Working Group guidance, Competence Cell assignment, public-safe reporting, readiness-room design, and lawful handoff dependency discipline.

13.10.8.8 Lessons Learned turn partner contribution from one-time support into cumulative public-good capability.

***

#### 13.10.9 Contribution Archive and Correction

13.10.9.1 Contribution Archive and Correction means the process for preserving completed contribution records, correcting contribution descriptions, updating valuation records, correcting public acknowledgments, recording withdrawal, recording suspension, recording termination, archiving restricted contribution details, and preserving traceability after a partner exits or a contribution closes.

13.10.9.2 Contribution Archive shall preserve Contribution Records, Exit Records, Teardown Records, Access Closure Records, Data Closure Records, Credential Closure Records, Equipment Return and Sanitization Records, Partner Debrief Records, Lessons Learned Records, recognition records, public notice records, correction records, conflict records, Boundary Incident records, and relevant public-safe classification records.

13.10.9.3 Archive classes may include public archive, controlled archive, restricted archive, confidential archive, redacted archive, no-publication archive, cyber-sensitive archive, data-sensitive archive, protected knowledge archive, Indigenous-sensitive archive where applicable, public authority-sensitive archive, market-sensitive archive, partner-confidential archive, legal-hold archive, and internal institutional memory archive.

13.10.9.4 Contribution correction shall occur where contribution descriptions are inaccurate, public acknowledgments are outdated, value records are overstated or understated, contribution status changes, restrictions were omitted, access was misdescribed, sponsor overclaim occurred, provider overclaim occurred, public authority confusion arose, readiness implication arose, procurement implication arose, consent implication arose, or public-safe classification changes.

13.10.9.5 Correction may include revised contribution records, revised public acknowledgment, revised logo use, revised valuation, revised recognition class, revised support description, revised partner communications, restricted public notice, withdrawal of acknowledgment, public clarification where required, controlled clarification, supersession, downgrade, retirement, non-continuation, or archive.

13.10.9.6 Where contribution details remain confidential, restricted, market-sensitive, public authority-sensitive, cyber-sensitive, data-sensitive, protected, or Indigenous-sensitive where applicable, the archive shall preserve internal traceability without unsafe public disclosure.

13.10.9.7 Archive shall identify which claims remain permitted, which acknowledgments remain current, which materials must no longer be used, which public references have been superseded, which access has been closed, which data has been handled, which equipment has been returned or sanitized, and which lessons must inform future cycles.

13.10.9.8 Contribution Archive and Correction shall preserve institutional memory without preserving misleading status.

***

#### 13.10.10 Partner Exit Summary Clause

13.10.10.1 Partner contribution is complete only when access is closed, data is handled, credentials are revoked or rotated, equipment is returned or sanitized, systems are torn down or lawfully continued, records are archived, public acknowledgments are corrected where needed, claims are bounded, and lessons strengthen the next cycle.

13.10.10.2 Partner Exit Conditions include planned completion, post-cycle teardown, contribution expiration, breach, conflict concern, Boundary Incident, security issue, non-renewal, withdrawal, or mutual termination. Teardown Requirements apply to partner-provided equipment, cloud environments, software access, data platforms, secure rooms, dashboards, integrations, network links, temporary accounts, and live operations tools. Access Closure requires closure of partner, mentor, engineer, researcher, volunteer, sponsor, and provider access to systems, rooms, data, repositories, dashboards, logs, and restricted records after the authorized period ends. Data Closure governs data retention, deletion, return, archive, audit logs, clean-room closure, output review, partner data removal, and restricted data confirmation. Credential Closure requires credential revocation, secret rotation, account deactivation, token invalidation, key management closure, audit review, and confirmation of least-privilege restoration. Equipment Return and Sanitization covers wiping, sanitization, inventory reconciliation, damage reporting, secure transport, custody transfer, and residual data controls. Partner Debrief covers technical performance, support quality, access issues, data issues, security issues, claims boundaries, researcher feedback, and future contribution opportunities. Lessons Learned identify what worked, what failed, what created risk, what should be corrected, what should be renewed, and what should inform next-cycle partner engagement. Contribution Archive and Correction preserve completed contribution records, correct public acknowledgments, update value records, record withdrawal, and archive restricted contribution details.

13.10.10.3 No partner exit, teardown record, access closure record, data closure record, credential closure record, equipment return record, sanitization record, partner debrief, lessons learned record, contribution archive, contribution correction, public acknowledgment correction, value-record update, withdrawal record, suspension record, termination record, non-renewal record, post-cycle record, public notice, controlled notice, or archive reference shall create certification, validation, recognition standing, maturity status, governance authority by default, public authority approval, procurement status, preferred-provider status, financeability, bankability, investability, insurability, underwriting acceptance, donor commitment, public finance allocation, official warning, emergency command, community consent, Indigenous consent, standards conformance, deployment authorization, project approval, handoff authorization, transaction, or execution authority by implication.

13.10.10.4 The controlling Partner Exit Formula is that contribution begins with record, operates under limits, closes through teardown, restores least privilege through access and credential closure, protects rights through data closure, protects assets through equipment return and sanitization, protects truth through correction, protects memory through archive, and protects the next cycle through lessons learned; a partner has not fully exited until the contribution can no longer create hidden access, uncontrolled data, unresolved credentials, unreturned equipment, misleading recognition, uncorrected claims, or unrecorded learning.

<br>

### Next steps

* Review [XIV. FINANCE](/organization/acceleration/charter/xiv.-finance.md) for finance-readiness and reader boundaries.
* Review [XV. AUTHORITIES](/organization/acceleration/charter/xv.-authorities.md) and [XVI. SAFEGUARDS](/organization/acceleration/charter/xvi.-safeguards.md) for authority and safeguard controls.
* Review [XIX. GOVERNANCE](/organization/acceleration/charter/xix.-governance.md) for downstream governance and decision boundaries.


---

# 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/acceleration/charter/xiii.-partners.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.