ARTICLE III. ALIGNMENT

Section 64. Public-Good Stack Alignment

64.1 Nexus Public-Good Stack Context. The Corporation shall situate its purposes, powers, programs, records, technical assets, research activities, evidence functions, observability methods, ontology work, public-good software, open technical baselines, public authority learning activities, controlled-room activities, publications, and Nexus interfaces within the Nexus public-good stack, being the non-executing institutional layer through which shared evidence, methods, records, correction, observability, ontology, technical baselines, public-safe reporting inputs, standards-support inputs, maturity inputs, finance-readiness evidence inputs, public authority learning inputs, safeguards, and public-good technical memory are developed, stewarded, reviewed, corrected, and made interoperable.

For purposes of this Bylaw, the Nexus public-good stack shall be understood as a role-separated public-benefit architecture that supports systemic risk, resilience, public trust, and exponential technology governance without becoming a market actor, regulated intermediary, project developer, enterprise delivery platform, public authority, procurement authority, finance authority, emergency-command actor, or certification body by default. The Corporation’s participation in the Nexus public-good stack shall therefore be interpreted through the following controlling principles:

a) evidence shall remain evidence and shall not become recognition, finance-readiness, certification, procurement approval, public authority decision, or execution instruction;

b) methods shall remain methods and shall not become compulsory legal standards, regulatory approvals, procurement mandates, market recommendations, or professional advice unless separately and lawfully adopted by competent authority;

c) observability shall remain evidence infrastructure and public-safe intelligence support and shall not become official public warning, emergency command, public authority action, guarantee, or final truth;

d) ontology shall remain semantic infrastructure and shall not become legal hierarchy, institutional supremacy, public authority meaning, or private control of public-good terms;

e) public-good software and open technical baselines shall remain reference, interoperability, and conformance-supporting assets and shall not become certification, procurement preference, exclusive vendor pathway, or private enclosure;

f) public authority learning shall remain capacity formation and technical literacy support and shall not become public authority delegation, public warning, regulatory action, public finance approval, or sovereign commitment;

g) finance-readiness evidence support shall remain technical input and shall not become capital-readability determination, investment advice, routeability determination, insurance approval, underwriting, rating, guarantee, or public finance approval; and

h) Nexus compatibility shall remain record-based alignment within defined authority surfaces and shall not imply endorsement, certification, public legitimacy, procurement approval, provider preference, or enterprise-stack authority.

The Corporation shall maintain its public-good stack alignment as a constitutional operating posture, not as a branding statement. All internal policies, program charters, committee mandates, council mandates, public materials, controlled-room protocols, evidence packs, technical releases, sponsor materials, provider materials, public authority interfaces, and cross-entity agreements shall be drafted and administered consistently with this Section.

64.2 GCRI Canada Within the GCRI Function. The Corporation shall express, within Canada and within its lawful corporate remit, the GCRI function of evidence, methods, observability, ontology, technical truth, public-good research and development, public-good software, open technical baselines, and scientific-operational integrity. The Corporation shall not be interpreted as the whole of the GCRI function globally, nor as the parent, branch, agent, alter ego, controller, treasury, employer, guarantor, or liability center of any other GCRI entity unless a lawful instrument expressly provides otherwise and only to the extent permitted by applicable law.

The Corporation’s Canadian expression of the GCRI function shall include the capacity, subject to this Bylaw, to:

a) develop, steward, review, publish, restrict, correct, supersede, withdraw, or archive evidence doctrine, methods, observability frameworks, ontology systems, public-good software, open technical baselines, reference architectures, and public-safe technical materials;

b) support Canadian, regional, and global Nexus interfaces with evidence inputs, methods inputs, observability inputs, ontology inputs, technical baseline inputs, correction signals, public authority learning materials, and public-good R&D outputs;

c) localize public-good technical and institutional methods for Canadian legal, governance, public authority, community, Indigenous, data, privacy, cyber, AI, accessibility, sanctions, export-control, and safeguards contexts;

d) contribute to global Nexus coherence without surrendering Canadian corporate separateness, Canadian legal compliance, Board authority, records custody, role boundaries, or non-execution discipline;

e) support interoperability between GCRI Canada, GCRI US, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Grid, Nexus Rails, Nexus Academy, Nexus Competence Cells, Global Nexus Consortium, Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, National Consortium Companies, Project SPVs, Qualified Enterprise Providers, sponsors, hosts, public authorities, universities, communities, civil society, and other participants; and

f) correct, qualify, limit, or withdraw any claim that misstates the Corporation’s role within the GCRI function or the Nexus public-good stack.

The Corporation shall not use the GCRI function to claim authority over recognition, standing, maturity records, claims discipline outside its own outputs, finance-readiness determinations, protocol entitlements, procurement outcomes, public authority decisions, emergency warnings, regulated compliance, certification, or enterprise execution.

64.3 GCRI Canada as Canadian Public-Benefit Evidence and Methods Anchor. The Corporation shall operate as a Canadian public-benefit evidence and methods anchor within the Nexus public-good stack. This anchoring role shall mean that the Corporation may provide disciplined custody, review, localization, development, and correction of evidence and methods relevant to Canada, Canadian-linked activities, Canadian public authority learning, Canadian-hosted or Canadian-participating Nexus activities, Canadian public-good software and technical baselines, Canadian observability contexts, Canadian data governance contexts, Canadian safeguards contexts, and Canadian interfaces with regional and global Nexus structures.

The Canadian evidence and methods anchor role shall include, where lawful and authorized:

a) Canadian evidence doctrine development for systemic risk, resilience infrastructure, AI, agentic AI, AI-RAN, O-RAN, private wireless, sovereign compute, edge compute, high-performance compute, verifiable compute, verifiable intelligence, blockchain, distributed ledger technology, Web3-relevant systems, DePIN, cybersecurity, cyber-physical systems, robotics, drones, autonomous systems, sensing, Earth observation, satellite, geospatial, digital twins, climate, nature, biodiversity, disaster, wildfire, flood, water, energy, food, health, biosecurity, quantum-relevant systems, advanced manufacturing, semiconductors, industrial systems, ports, utilities, critical infrastructure, supply chains, and other mission-critical or exponential technologies;

b) Canadian methods development for source lineage, confidence, uncertainty, calibration, corroboration, dispute handling, spoof detection, stale data review, sensor fusion, AI output review, digital twin assumption review, cyber evidence, geospatial evidence, public-safe publication, evidence challenge, correction, and controlled-room handling;

c) Canadian observability methods for nodes, hubs, clusters, hotspots, national dense cores, regional clusters, sensors, AI-RAN, O-RAN, DePIN, cyber telemetry, geospatial systems, digital twins, dashboards, public-safe outputs, degraded-mode awareness, and mission-critical signals;

d) Canadian ontology and semantic interoperability work for controlled vocabulary, risk categories, evidence classifications, maturity concepts, public authority capacity terms, finance-boundary terms, recognition-boundary terms, certification-boundary terms, technology families, schemas, data dictionaries, and AI-readable knowledge structures;

e) Canadian public authority learning support that enables public authorities to understand evidence, methods, technical baselines, dashboards, observability outputs, public-safe limitations, and Nexus interfaces without converting the Corporation into a public authority or decision-maker; and

f) Canadian correction discipline for evidence, methods, publications, public authority references, sponsor references, provider claims, finance-facing implications, public-safe outputs, technical baselines, software releases, and Nexus-compatible claims.

The Corporation’s anchoring role shall not create territorial exclusivity, public authority mandate, sovereign delegation, public finance approval, procurement authority, or control over other Canadian or non-Canadian institutions. It shall be a public-benefit stewardship role, not a jurisdictional supremacy role.

64.4 Alignment With the Nexus Constitutional Framework. The Corporation shall align its internal governance, public-good activities, technical outputs, records discipline, public-safe communications, role-separation practices, and Nexus interfaces with the Nexus Constitutional Framework to the extent such alignment is consistent with applicable Canadian law, the Articles, this Bylaw, Board-adopted policies, and competent corporate authority.

The Nexus Constitutional Framework shall be treated as a mission-alignment, interoperability, role-separation, public-good architecture, and interpretive support instrument for the Corporation only to the extent lawfully adopted or incorporated by reference through appropriate corporate action. It shall not, by its own force alone, amend this Bylaw, override applicable law, change the Corporation’s legal status, alter Board authority, confer rights on third parties, create public authority powers, impose enterprise-stack duties, or authorize prohibited functions.

Alignment with the Nexus Constitutional Framework shall require the Corporation to preserve:

a) the public-good character of shared evidence, methods, observability, ontology, records, and technical baselines;

b) the distinction between public-good stack and enterprise stack;

c) the separation between evidence, recognition, finance-readiness, standards/protocol authority, execution, public authority action, provider delivery, national company functions, and Project SPV functions;

d) the doctrines of non-execution, validity-by-record, correctionability, one rail / two stacks, public-good firewall, support-without-control, public authority capacity classification, finance-readiness without regulated execution, procurement neutrality, and public-safe publication;

e) the requirement that automated outputs, AI outputs, dashboards, digital twins, DePIN records, AI-RAN signals, proof receipts, compute attestations, and ledger entries remain subject to record, review, context, classification, limitation, and correction; and

f) the requirement that institutional authority be traceable to lawful record, not reputation, proximity, technical centrality, sponsorship, public authority attendance, operational convenience, or repeated practice.

Where a conflict arises between a Nexus constitutional instrument and the Corporation’s Canadian legal obligations or this Bylaw, the Corporation shall apply the higher-order lawful instrument, document the conflict, create a divergence log or compatibility note where appropriate, and preserve the most protective lawful interpretation pending resolution.

64.5 Alignment With the Public-Good Stack Framework Charter. The Corporation shall align with the Public-Good Stack Framework Charter as a structural statement of the Nexus public-good stack, enterprise stack, institutional families, common rail, records discipline, role-separation logic, public-good technical stewardship, and support-without-control architecture, to the extent lawfully adopted and consistent with this Bylaw.

Such alignment shall require the Corporation to understand its place as an upstream public-benefit technical institution whose outputs may support, but shall not collapse into, the distinct functions of:

a) The Global Risks Forum (GRF), as public-good registry, recognition, maturity-records, standing, claims-discipline, stakeholder-formation, public-safe reporting, and public-facing legitimacy steward;

b) The Global Risks Alliance (GRA), as capital-readability, finance-readiness, investor-literacy, insurance-readiness, diligence-translation, and common-business-interest steward;

c) Nexus Standards or any separately constituted protocol authority, as standards-profile, conformance-logic, protocol-discipline, role-key, smart-license, proof-receipt, ledger-anchoring, entitlement-logic, and technical-validity-state authority where lawfully authorized;

d) Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, and related public-good systems, each within its defined role;

e) Global, regional, and national consortium structures as coordination, mandate, legitimacy, localization, and participation surfaces without control over the Corporation unless lawfully adopted;

f) National Consortium Companies and Project SPVs as enterprise-stack actors, investible platforms, project vehicles, operators, asset owners, contracting vehicles, and execution structures outside the Corporation’s public-good perimeter; and

g) Qualified Enterprise Providers as delivery actors whose participation does not create public-good authority, provider preference, certification, procurement advantage, or control over the Corporation.

The Corporation shall not interpret public-good stack alignment as requiring uniformity of legal form, shared treasury, common employer status, joint liability, automatic agency, or loss of Canadian corporate separateness. Alignment shall be achieved through interoperable records, compatible doctrine, lawful agreements, defined authority surfaces, boundary notes, controlled vocabulary, correction paths, and public-safe claims discipline.

64.6 Alignment With the Non-Execution Doctrine. The Corporation shall align all public-good stack participation with the Non-Execution Doctrine. This doctrine shall require that the Corporation remain outside regulated, commercial, sovereign, emergency, procurement, certification, finance, insurance, investment, lending, rating, and enterprise execution functions unless and only to the extent a lawful, Board-approved, separately authorized, non-conflicting, and bylaw-consistent function is created, and provided that no prohibited function is undertaken.

The Non-Execution Doctrine shall apply to every authority surface of the Corporation, including Board deliberations, officer delegations, committees, councils, working groups, competence cells, research programs, public authority rooms, capital-reader rooms, data rooms, controlled rooms, software repositories, public-good technical baselines, dashboards, public-safe reports, evidence packs, proof receipts, Nexus interfaces, sponsor materials, provider materials, public statements, and partnership instruments.

In applying the Non-Execution Doctrine, the Corporation shall ensure that:

a) evidence inputs to GRF shall not become recognition or standing by the Corporation;

b) evidence inputs to GRA shall not become finance-readiness, capital-readability, investment suitability, insurability, routeability, or bankability determinations by the Corporation;

c) technical baselines, conformance-supporting tools, and standards mappings shall not become certification, accreditation, compliance approval, legal equivalence, or procurement mandate by the Corporation;

d) public authority learning, public authority rooms, and public authority participation shall not become public authority delegation, public warning, funding approval, regulatory action, procurement approval, or sovereign act by the Corporation;

e) observability outputs, dashboards, maps, AI systems, digital twins, DePIN records, ledger entries, AI-RAN signals, sensor signals, and proof receipts shall not become public warnings, emergency commands, certifications, public authority decisions, or final authority;

f) Nexus Universe participation, Nexus Network support, Nexus Observatory support, Nexus Rails support, Nexus Grid inputs, Nexus Academy training, or Nexus Competence Cell formation shall not become execution by the Corporation; and

g) sponsor, donor, provider, host, investor, insurer, lender, National Consortium Company, or Project SPV participation shall not create control, private benefit, provider preference, procurement advantage, finance implication, or execution authority.

Any activity that cannot be safely classified as non-executing shall be held, quarantined, re-scoped, externalized to a lawful actor, or terminated.

64.7 Alignment With the Validity-by-Record Doctrine. The Corporation shall align with the Validity-by-Record Doctrine, under which institutional meaning, governance authority, evidence status, method status, public-safe publication status, public authority reference status, sponsor benefit status, provider claim status, technical release status, Nexus interface status, correction status, and any Nexus-compatible claim shall arise only from an authoritative record created, approved, classified, stored, and maintained through the Corporation’s lawful governance and records systems.

No claim of alignment, approval, adoption, recognition, finance-readiness support, standards support, public authority participation, technical validity, evidence status, public-good software release, controlled-room access, committee recommendation, council output, competence cell output, public-safe report, proof receipt, dashboard status, data access, AI-use permission, or cross-entity interface shall have institutional meaning merely because of circulation, attendance, reputation, authorship, technical access, sponsorship, funding, repeated practice, title, informal approval, email, chat, slide deck, public statement, website copy, meeting note, repository comment, or operational habit.

The Corporation shall maintain record-based validity through:

a) structured intake and Case IDs for material acts;

b) authority mapping and decision packs for governance-significant decisions;

c) official registers for corporate, governance, evidence, methods, ontology, model, dataset, software, technical asset, publication, correction, incident, sponsor, donor, public authority, provider, and third-party risk records;

d) versioning, change logs, supersession chains, errata, correction notices, withdrawal records, and archives;

e) classification of publication, access, handling, competition sensitivity, data sensitivity, security, public authority sensitivity, finance sensitivity, infrastructure sensitivity, cyber sensitivity, and protected knowledge sensitivity;

f) repository discipline, authenticity controls, signature controls, audit trails, hashes or integrity references where used, custody records, and tamper-evident references where appropriate; and

g) divergence logs, compatibility notes, interface records, and mismatch resolution records for cross-entity alignment.

The Corporation shall not allow the language of “Nexus,” “GCRI,” “public-good,” “verified,” “validated,” “recognized,” “finance-ready,” “insurance-ready,” “Nexus-compatible,” “conforming,” “certified,” “approved,” “authorized,” “public-safe,” “Docket,” “Grid,” “proof receipt,” or similar controlled vocabulary to be used without a proper record and authority surface.

64.8 Alignment With the Correctionability Doctrine. The Corporation shall align with the Correctionability Doctrine, under which all governance records, evidence artifacts, methods, technical baselines, public-good software, ontology terms, public-safe outputs, public claims, public authority references, sponsor references, provider references, Nexus-compatible statements, committee outputs, council outputs, controlled-room materials, dashboards, proof receipts, reports, maps, models, AI-assisted outputs, and cross-entity interface records shall remain capable of correction, clarification, supersession, withdrawal, retraction, downgrade, retirement, archival, or other appropriate lifecycle action.

Correctionability shall not be discretionary branding hygiene. It shall be a governance duty. The Corporation shall correct inaccurate, incomplete, misleading, unsupported, unsafe, stale, superseded, overbroad, unauthorized, sponsor-influenced, provider-influenced, public-authority-confusing, finance-overclaiming, certification-implying, procurement-implying, recognition-implying, maturity-implying, or role-confusing outputs.

The Correctionability Doctrine shall require that:

a) records include correction paths before they are used as evidence, methods, technical baselines, public-safe outputs, public authority references, Nexus interface inputs, or public claims;

b) public-safe correction notices, controlled correction notices, internal correction notices, stakeholder notifications, and downstream dependency reviews be used where appropriate;

c) correction preserve historical traceability and shall not conceal error, drift, misuse, overclaim, or boundary confusion;

d) correction respect confidentiality, privilege, data protection, cybersecurity, public authority sensitivity, finance sensitivity, infrastructure sensitivity, competition sensitivity, community safeguards, Indigenous knowledge protections, and protected knowledge restrictions;

e) correction signals be transmitted to GRF, GRA, GCRI US, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Grid, Nexus Rails, Nexus Academy, consortiums, National Consortium Companies, Project SPVs, providers, hosts, public authorities, sponsors, donors, funders, or affected stakeholders where relevant and lawful; and

f) failure to correct after detection be treated as a governance issue requiring escalation.

The Corporation’s willingness and capacity to correct shall be treated as a condition of public-good trust. No person shall characterize correction, supersession, withdrawal, or retraction as institutional weakness where such action is required to preserve truthfulness, safety, legality, public benefit, role separation, or public-good integrity.

64.9 Alignment With the One Rail / Two Stacks Doctrine. The Corporation shall align with the One Rail / Two Stacks Doctrine. The one rail shall mean the shared semantic, evidentiary, records, observability, correction, public-safe meaning, and interoperability rail through which public-good and enterprise-stack actors may communicate, compare, route, and understand information without collapsing their legal functions. The two stacks shall mean, respectively, the public-good stack and the enterprise stack.

The Corporation shall belong to the public-good stack and shall not be treated as an enterprise-stack actor by reason of its technical centrality, software development, public authority interfaces, controlled-room participation, Nexus Universe involvement, Nexus Observatory methods support, Nexus Network technical support, or evidence inputs to finance-readiness workflows.

The Corporation shall preserve the One Rail / Two Stacks Doctrine by ensuring that:

a) public-good stack outputs remain upstream inputs, not downstream execution decisions;

b) enterprise-stack demand does not create public-good authority;

c) enterprise-stack feedback may inform public-good improvement but shall not control research, evidence, methods, ontology, public-good software, technical baselines, publications, public authority access, Docket inputs, Grid inputs, GRF inputs, or GRA inputs;

d) National Consortium Companies and Project SPVs may receive evidence, methods, technical baseline, observability, or public-good compatibility support only within lawful non-execution boundaries;

e) Qualified Enterprise Providers may contribute tools, data, systems, compute, AI-RAN, sensors, dashboards, cybersecurity, integration support, or services without obtaining preferred provider status, certification, procurement advantage, public authority meaning, or control;

f) sponsors, donors, funders, and hosts may support public-good work without purchasing outcomes, access, influence, recognition, finance-readiness, public authority proximity, publication language, or technical conclusion; and

g) public authorities may participate in capacity-classified learning, observation, technical literacy, and controlled-room contexts without delegating sovereign, regulatory, public warning, procurement, funding, emergency, or public finance authority to the Corporation.

The Corporation shall maintain interface records, boundary notes, compatibility notes, divergence logs, public-safe limitation statements, and correction paths sufficient to preserve rail interoperability without role collapse.

64.10 Alignment With the Verifiable Compute and Verifiable Intelligence Doctrine. The Corporation shall align with the Verifiable Compute and Verifiable Intelligence Doctrine, under which compute workloads, inference records, model registers, dataset cards, model cards, system cards, benchmark cards, evaluation harnesses, confidential computing records, secure enclave records, compute-to-data records, air-gapped environment records, proof receipts, compute receipts, AI output records, agentic AI controls, and verifiable intelligence artifacts shall be treated as evidence-supporting and method-governed records rather than final authority.

The Corporation may steward, develop, review, test, document, publish, restrict, correct, or support methods for verifiable compute and verifiable intelligence, including methods concerning:

a) provenance of compute workloads, models, datasets, prompts, retrieval sources, embeddings, fine-tuning data, inference contexts, evaluation inputs, benchmark assumptions, and system configurations;

b) traceability of AI-assisted evidence classification, confidence scoring, source comparison, corroboration, contradiction handling, spoof detection, failed signal handling, missing data treatment, stale data treatment, and correction triggers;

c) secure computing environments, confidential computing, air-gapped environments, compute-to-data patterns, restricted data zones, sovereign data zones, controlled-room AI use, and public-safe output review;

d) human review requirements for material outputs, public-facing outputs, public authority-facing outputs, finance-facing outputs, safeguards-sensitive outputs, and high-risk technical outputs;

e) model governance, model retirement, dataset governance, system cards, benchmark governance, inference records, and AI incident handling; and

f) interoperability with Nexus Observatory, Nexus Standards, Nexus Grid, Nexus Docket, Nexus Rails, Nexus Network, GRF, GRA, GCRI US, consortiums, National Consortium Companies, Project SPVs, providers, and public authorities where lawful and non-executing.

No compute record, inference record, AI output, model output, benchmark result, proof receipt, compute receipt, digital twin output, DePIN record, ledger entry, AI-RAN signal, O-RAN signal, dashboard, map, automated classification, confidence score, or verifiable intelligence artifact shall constitute recognition, finance-readiness, certification, procurement approval, legal compliance approval, public authority decision, public warning, emergency command, guarantee, rating, or final truth by default.

64.11 Alignment With Nexus Network, Nexus Observatory, Nexus Standards, Nexus Risk Management, Nexus Rails, Nexus Universe, Nexus Grid, Nexus Academy, and Nexus Competence Cells. The Corporation may align, coordinate, interface, and exchange lawful non-executing inputs with Nexus Network, Nexus Observatory, Nexus Standards, Nexus Risk Management, Nexus Rails, Nexus Universe, Nexus Grid, Nexus Academy, and Nexus Competence Cells. Such alignment shall be role-specific, record-based, and boundary-controlled.

In relation to Nexus Network, the Corporation may support evidence doctrine, methods, observability logic, ontology, public-good software, reference implementations, and network evidence interfaces, but shall not be deemed to own, operate, control, commercialize, or provide the entire Nexus Network by default.

In relation to Nexus Observatory, the Corporation may support methods for observability, telemetry, sensing, evidence conversion, AI-RAN, O-RAN, DePIN, sensors, geospatial systems, cyber telemetry, digital twins, dashboards, degraded-mode awareness, public-safe outputs, traceability, correction, and verifiable intelligence, but shall not issue public warnings, emergency commands, certifications, finance-readiness determinations, or public authority decisions.

In relation to Nexus Standards or protocol authority, the Corporation may support technical baselines, evidence requirements, methods, schemas, public-good software, conformance-supporting tools, interoperability mappings, and proof-receipt logic, but shall not become a protocol authority, standards authority, certification body, entitlement issuer, role-key issuer, smart-license authority, or compliance approver by authorship or technical centrality.

In relation to Nexus Risk Management, the Corporation may support risk evidence methods, scenario methods, risk ontologies, data structures, digital twin methods, uncertainty methods, and public-safe risk outputs, but shall not issue emergency commands, public warnings, public authority decisions, insurance underwriting conclusions, investment advice, or regulated risk determinations.

In relation to Nexus Rails, the Corporation may provide technical evidence inputs, methods inputs, observability inputs, technical baseline inputs, and correction signals, but shall not determine routeability, capital-readability, finance-readiness, bankability, insurability, investment suitability, underwriting, guarantee status, or public finance approval.

In relation to Nexus Universe, the Corporation may support technical build review, evidence review, benchmarking, methods review, Academy labs, public authority learning, observatory inputs, Docket and Grid inputs, public-safe materials, sponsor claims discipline relating to technical outputs, and after-action correction, but shall not convert event participation into recognition, procurement, finance-readiness, public authority endorsement, or execution.

In relation to Nexus Grid, the Corporation may provide evidence inputs, methods inputs, observability inputs, research inputs, technical baseline inputs, and correction signals, but shall not issue maturity determinations, guarantees, certifications, public authority approvals, finance-readiness, insurance-readiness, procurement approvals, or performance warranties.

In relation to Nexus Academy and Nexus Competence Cells, the Corporation may support evidence literacy, research integrity training, AI, data, cyber, observatory, public authority, public-safe publication, safeguards, public-good software, and technical competence formation, but shall not issue professional certification, regulated credentials, public authority qualifications, provider preferences, procurement advantages, or certification by default.

Each interface shall be supported by records sufficient to identify the relevant entity, purpose, authority surface, role boundary, data classification, publication class, correction path, legal constraints, and public-safe limitation language.

64.12 Alignment Without Subordination to External Bodies Unless Lawfully Adopted. Alignment with Nexus instruments, Nexus entities, councils, consortiums, standards functions, protocol functions, public authority processes, global coordination bodies, regional coordination bodies, national consortium structures, National Consortium Companies, Project SPVs, sponsors, providers, hosts, universities, laboratories, community bodies, or other external bodies shall not subordinate the Corporation’s internal governance to any external body unless such subordination is required by applicable law or is lawfully adopted through the Corporation’s governing instruments, Board-approved agreements, or member approval where required.

No external doctrine, charter, protocol, standard, consortium decision, council output, working group note, sponsor condition, provider requirement, public authority expectation, grant term, partnership statement, technical integration, dashboard status, software dependency, public announcement, or operational custom shall override:

a) applicable Canadian law;

b) the Articles or constituting instrument of the Corporation;

c) this Bylaw;

d) Board reserved powers;

e) fiduciary duties of directors;

f) lawful member approval rights where applicable;

g) non-execution boundaries;

h) public-benefit and non-distribution requirements;

i) records, validity-by-record, and correctionability requirements;

j) data, AI, cyber, privacy, safeguards, accessibility, sanctions, export-control, competition, and research ethics requirements; or

k) Canadian corporate separateness and governance seat discipline.

The Corporation may adopt external instruments by reference only through a lawful recorded act that identifies the instrument, version, scope, authority surface, legal effect, conflicts rule, amendment mechanism, repository location, public or controlled access status, and correction path. Adoption of alignment language shall not be presumed to adopt all future versions of an external instrument unless expressly approved through an appropriate mechanism.

64.13 Alignment Without Merger, Agency, Shared Treasury, Shared Employer, Shared Liability, or Parent-Subsidiary Status. The Corporation’s alignment with the Nexus public-good stack, GCRI US, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, Global Nexus Consortium, Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, National Consortium Companies, Project SPVs, Qualified Enterprise Providers, sponsors, donors, funders, hosts, universities, laboratories, public authorities, communities, civil society, media, contractors, or other partners shall not create merger, agency, partnership, joint venture, alter ego status, parent-subsidiary status, branch status, division status, shared treasury, shared employer, joint employer, common control, fiduciary delegation, or shared liability.

Shared mission shall not create legal fusion. Shared doctrine shall not create shared liability. Shared ontology shall not create shared treasury. Shared records shall not create mutual authority. Shared personnel shall not create single employer status. Shared events shall not create partnership. Shared rooms shall not create agency. Shared technical baselines shall not create protocol authority. Shared public authority participation shall not create sovereign delegation. Shared finance-readiness evidence inputs shall not create investment, insurance, lending, underwriting, rating, guarantee, or public finance authority.

The Corporation shall maintain boundary discipline through:

a) separate corporate records;

b) separate financial records;

c) separate bank accounts and treasury controls;

d) separate employment and contractor records unless a lawful shared-service arrangement expressly provides otherwise;

e) written interface agreements, MoUs, data-sharing agreements, evidence-sharing agreements, controlled-room agreements, public-good technical asset agreements, service-level terms, or other instruments where appropriate;

f) non-merger, no-agency, no-partnership, no-joint-venture, no-shared-liability, no-mutual-authority, non-execution, and claims-discipline clauses in material agreements;

g) role-specific public descriptions;

h) controlled use of names, marks, logos, titles, public authority references, sponsor references, provider references, and Nexus references; and

i) correction, withdrawal, takedown, or public clarification where alignment has been misrepresented as control, authority, endorsement, guarantee, or legal fusion.

No person shall bind, represent, obligate, or expose the Corporation by claiming authority arising solely from Nexus alignment, shared participation, shared doctrine, shared personnel, shared documents, shared technical systems, shared public authority interface, sponsor relationship, or provider relationship.

64.14 Alignment Records, Compatibility Notes, and Divergence Logs. The Corporation shall maintain alignment records sufficient to evidence the nature, scope, limits, authority surface, classification, legal basis, public-benefit rationale, non-execution boundary, data / AI / cyber posture, public authority posture, finance-boundary posture, certification-boundary posture, procurement-neutrality posture, safeguards posture, and correction pathway for material Nexus public-good stack alignments.

Alignment records may include:

a) Board resolutions;

b) committee records;

c) officer delegations;

d) interface agreements;

e) MoUs;

f) public-good stack compatibility notes;

g) role-separation notes;

h) non-execution analyses;

i) public authority capacity notes;

j) finance-boundary notes;

k) certification-boundary notes;

l) procurement-neutrality notes;

m) data, AI, cyber, privacy, sanctions, export-control, competition, accessibility, safeguards, and protected knowledge reviews;

n) controlled vocabulary records;

o) technical baseline records;

p) public-good software release records;

q) evidence and methods records;

r) public-safe publication records;

s) sponsor, donor, provider, host, and partner records;

t) correction records;

u) supersession records;

v) public or controlled notices;

w) annual interface review records; and

x) closeout records.

Compatibility notes shall be used where the Corporation aligns with an external or Nexus instrument but must explain how such alignment operates within Canadian law, this Bylaw, the Corporation’s legal separateness, non-execution boundaries, public-good role, controlled vocabulary, records discipline, and correction paths.

Divergence logs shall be used where the Corporation departs from, localizes, narrows, delays, suspends, rejects, or differently implements a Nexus instrument, public-good stack practice, external standard, consortium practice, protocol reference, or cross-entity expectation. A divergence log shall identify the source of divergence, reason for divergence, legal basis, risk analysis, affected interfaces, interim handling rule, review date, responsible authority, and correction or reconciliation path.

Alignment records, compatibility notes, and divergence logs shall not themselves create public authority, recognition, finance-readiness, certification, procurement, provider preference, legal compliance approval, or execution effect unless separately and lawfully authorized. Their function is to preserve truthfulness, interoperability, auditability, role separation, public-good trust, and correctionability.

Section 65. Role Separation, Legal Separateness, and No Institutional Collapse

65.1 Mandatory Role Separation Within the Nexus Public-Good Stack. The Corporation shall preserve mandatory role separation among the institutions, bodies, programs, records, technical surfaces, public-facing designations, recognition pathways, finance-readiness interfaces, regional and national formations, and execution-adjacent actors that interact with or operate within the Nexus architecture. Role separation shall be treated as a foundational governance condition, not as a drafting preference, branding distinction, operational convenience, or optional internal protocol.

For purposes of this Bylaw, role separation means that each institution, body, program, vehicle, committee, registry, room, record, route, status, interface, and operating surface shall act only within its recorded authority, legal form, mandate, delegation, jurisdictional posture, risk classification, and approved institutional function. No person, officer, director, committee, member, participant, sponsor, host, vendor, public authority, capital reader, regional consortium, national consortium, project vehicle, service provider, or affiliated actor shall collapse, merge, imply, borrow, transfer, substitute, or overstate the role of one institution or surface through proximity, funding, public visibility, shared mission, shared personnel, shared terminology, shared technical assets, common doctrine, operational dependency, or market expectation.

65.1.1 The Corporation shall recognize that the Nexus architecture depends upon a disciplined allocation of roles among separate institutional families and operating surfaces, including, without limitation:

a) The Global Centre for Risk and Innovation (GCRI), in its applicable legally constituted form, as an upstream public-good evidence, methods, research, observability, ontology, scientific-operational discipline, safeguards, and technical-stewardship institution;

b) The Global Risks Forum (GRF), as the public-good registry, recognition, standing, maturity-records, claims-discipline, stakeholder-formation, public-safe reporting, and public-facing legitimacy steward;

c) The Global Risks Alliance (GRA), as the finance-readiness, resilience-finance translation, capital-architecture, proof-pack, insurance-readiness, and regulated-perimeter discipline institution;

d) any applicable protocol authority, standards authority, Nexus Standards body, Nexus Network authority, Nexus Observatory authority, or designated common-rail steward, only within the authority expressly recorded for such body;

e) regional Nexus consortiums, regional public-good consortiums, regional hubs, national public-good consortiums, national working groups, Nexus Competence Cells, and similar bodies, only within their admitted, recorded, localized, and maturity-bounded public-good or coordination functions;

f) national consortium companies, qualified enterprise providers, host-led commercial entities, implementation companies, service providers, and other second-stack actors, only within lawful commercial, enterprise, service, deployment, technical support, or market-facing functions recorded for them;

g) project SPVs, project companies, infrastructure vehicles, delivery vehicles, finance vehicles, and lawful execution actors, only within their own separately authorized downstream legal and commercial arrangements;

h) public authorities, regulators, agencies, cities, public institutions, multilateral actors, public finance actors, and public infrastructure operators, only in the capacity in which their participation is recorded and never by implication from attendance, consultation, observation, funding, speaking, or collaboration;

i) sponsors, donors, vendors, suppliers, technology providers, media partners, capital readers, universities, researchers, civil society participants, communities, and contributors, only within the permissions, restrictions, claims limits, safeguards, and records applicable to their respective participation.

65.1.2 The Corporation shall not treat shared public-good purpose, ecosystem affiliation, annual program participation, common vocabulary, common visual identity, common technical rail, shared doctrine, sponsor package, board awareness, executive coordination, or operational collaboration as evidence that two or more legally distinct institutions have become one legal person, one fiduciary body, one operator, one public authority, one standards body, one financial intermediary, one procurement platform, one commercial vehicle, one employer, one agent, one partnership, one joint venture, one alter ego, or one execution authority.

65.1.3 Each Nexus-related role shall remain bounded by the record that creates or recognizes it. A role may be coordinated, interoperable, federated, supportive, adjacent, or sequential without being merged. The Corporation shall therefore preserve the following distinctions at all times:

a) evidence shall be distinguished from recognition;

b) recognition shall be distinguished from certification unless a lawful certification program has been separately adopted and expressly scoped;

c) registry standing shall be distinguished from procurement approval;

d) public-safe reporting shall be distinguished from public warning, emergency command, or official public authority notice;

e) finance-readiness shall be distinguished from regulated financial advice, underwriting, brokerage, lending, insurance placement, rating, fund management, custody, payment, clearing, settlement, capital allocation, or securities distribution;

f) sponsor support shall be distinguished from sponsor control;

g) technical demonstration shall be distinguished from validation, warranty, official approval, or permanent Grid adoption;

h) Docket admission shall be distinguished from Grid integration, commercial readiness, procurement readiness, financeability, or public authority endorsement;

i) maturity status shall be distinguished from legal authorization, market permission, sovereign approval, or professional reliance;

j) public authority observation shall be distinguished from public authority adoption;

k) academic participation shall be distinguished from institutional endorsement, peer review, accreditation, or research approval unless separately recorded;

l) regional hub participation shall be distinguished from territorial exclusivity, franchise control, sovereign authority, or national implementation authority;

m) national consortium participation shall be distinguished from national public authority status, regulatory authority, or exclusive national mandate;

n) project-vehicle execution shall be distinguished from public-good governance;

o) enterprise delivery shall be distinguished from public-good stewardship.

65.2 Legal Separateness of Institutions and Vehicles. Each corporation, association, nonprofit entity, public-good institution, business league, consortium, company, project SPV, host entity, sponsor entity, public authority, university, research institution, vendor, qualified provider, capital actor, or other legal person participating in, supporting, interfacing with, or being referenced by the Nexus architecture shall remain legally separate unless a competent legal instrument expressly provides otherwise. Legal separateness shall not be weakened by common mission, common founders, common directors, overlapping officers, shared service arrangements, fiscal support, common brand architecture, common public communications, shared publications, common technical baselines, common software, common data environments, shared events, shared membership systems, shared sponsors, common board presentations, shared office resources, or coordinated strategy.

65.2.1 The Corporation shall maintain its own legal identity, governance records, board decisions, officer delegations, financial records, contracts, risk registers, policies, repositories, bank accounts, books, insurance arrangements, tax records, corporate filings, compliance posture, and authority chain in accordance with applicable law and this Bylaw.

65.2.2 No director, officer, committee member, employee, contractor, advisor, sponsor, participant, or affiliate shall represent that the Corporation is legally merged with, controlled by, controlling, guaranteeing, employing, underwriting, supervising, regulating, certifying, financing, insuring, operating, or acting as agent for any other Nexus institution, consortium, company, project vehicle, sponsor, host, public authority, vendor, provider, or participant unless an express written instrument, approved by the competent authority, truthfully establishes the specific relationship and its limits.

65.2.3 No relationship of affiliation, coordination, shared doctrine, common program participation, or ecosystem alignment shall be interpreted to create:

a) parent-subsidiary status;

b) branch-office status;

c) general partnership;

d) joint venture;

e) agency;

f) fiduciary agency;

g) alter-ego liability;

h) employer-of-record status;

i) consolidated debtor or guarantor status;

j) tax unity;

k) common treasury authority;

l) shared procurement authority;

m) shared regulated financial authority;

n) public authority delegation;

o) statutory authority;

p) standards authority with legal force;

q) certification authority;

r) insurance, underwriting, brokerage, investment, or lending authority;

s) emergency command authority;

t) public warning authority;

u) clinical, public health, or professional practice authority;

v) technology warranty or product-liability assumption;

w) data-controller, data-processor, custodian, fiduciary, or trustee status beyond the record.

65.2.4 Where the Corporation enters into a memorandum of understanding, cooperation agreement, affiliation agreement, grant agreement, sponsorship agreement, host agreement, service agreement, repository arrangement, data-sharing arrangement, licensing arrangement, joint publication arrangement, public authority engagement, regional hub arrangement, consortium arrangement, or other institutional interface with another actor, such instrument shall preserve legal separateness unless the Board expressly approves a different lawful structure after legal, tax, governance, regulatory, financial, conflict, data, and safeguards review.

65.2.5 The Corporation shall not permit legal separateness to be defeated by operational habit. Repeated coordination, shared meetings, shared staff support, shared documents, shared public language, shared technology, shared funder relationships, or shared annual programming shall not expand the Corporation’s legal responsibility or authority beyond the record. Where practice begins to create a reasonable risk of separateness confusion, management shall escalate the matter for correction, clarification, documentation, contract revision, public-claims adjustment, governance review, or legal advice.

65.3 No Role Substitution by Visibility, Funding, Expertise, or Urgency. No person or institution shall acquire the role of the Corporation, the Board, a committee, registry authority, recognition authority, maturity-record authority, public-safe reporting authority, claims authority, technical evidence authority, finance-readiness authority, regional hub authority, public authority, sponsor authority, or execution authority by reason of visibility, expertise, urgency, payment, sponsorship, philanthropy, political relevance, technical capacity, public attention, media presence, founder status, title, donor importance, vendor sophistication, capital access, or operational indispensability.

65.3.1 Role authority shall arise only through lawful constitution, recorded delegation, committee mandate, Board approval, officer appointment, adopted policy, written agreement, participant admission, room classification, registry record, Docket record, Grid record, maturity record, or other recognized institutional act sufficient for the specific authority claimed.

65.3.2 The Corporation shall reject any interpretation under which:

a) a sponsor becomes a governance authority because it funds a program;

b) a vendor becomes a technical authority because it provides equipment, software, compute, data, or expert staff;

c) a donor becomes a policy authority because it supports the public-good mission;

d) a host becomes a regional authority because it provides venue, local legitimacy, public authority access, or infrastructure;

e) a public authority becomes an adopting authority because it attends, observes, speaks, or participates in a controlled room;

f) a capital reader becomes a finance authority of the Corporation because it reviews proof packs or attends finance-readiness sessions;

g) a researcher becomes a certification authority because they review evidence, publish findings, or participate in a challenge;

h) a committee becomes the Board because it studies, recommends, or supervises a matter;

i) an officer becomes the institution because they lead operations or public communications;

j) a founder becomes a reserved-matter authority by historical role, reputation, or ecosystem memory;

k) an implementation provider becomes a public-good steward because it delivers downstream services;

l) a regional consortium becomes a global authority because it operates successfully in one jurisdiction;

m) a project SPV becomes the Nexus public-good stack because it executes a lawful project derived from upstream evidence or readiness work.

65.3.3 Urgency shall not create unrecorded authority. The Corporation may adopt emergency or expedited procedures where permitted by this Bylaw and applicable law, but urgency shall not authorize role collapse, sponsor control, public authority misrepresentation, unsafe publication, finance-perimeter breach, procurement implication, maturity overclaim, or execution by the wrong actor.

65.3.4 Expertise shall inform decisions but shall not itself constitute authority. Technical, legal, financial, public authority, community, scientific, engineering, cyber, AI, data, insurance, procurement, governance, and capital experts may advise, review, challenge, and recommend within recorded scope, but the legal effect of any institutional act shall depend upon the competent authority and record.

65.4 Public-Good Stack and Second-Stack Boundary. The Corporation shall maintain a clear distinction between the Nexus public-good stack and any second-stack, enterprise, commercial, implementation, deployment, finance, fund, infrastructure, market, or execution pathway. The public-good stack may create evidence, methods, records, recognition, maturity states, public-safe outputs, stakeholder formation, finance-readiness inputs, technical baselines, and governance-supporting artifacts. The second stack may include lawful enterprise services, implementation pathways, commercial offerings, project vehicles, infrastructure delivery, managed services, local deployment, financing, procurement, contracting, insurance, and regulated execution by appropriate actors outside the Corporation’s public-good role.

65.4.1 The Corporation shall not use public-good assets to obscure, subsidize, authorize, endorse, guarantee, or improperly advantage private commercial execution. Public-good assets may support lawful ecosystem development only where the relationship is recorded, role-bounded, fair, transparent, claims-controlled, conflict-reviewed, and consistent with public-benefit integrity.

65.4.2 No public-good record shall be converted into a commercial entitlement except through an approved route expressly contemplated by this Bylaw, applicable policy, written agreement, or competent authority record. Without limiting the foregoing:

a) a registry entry shall not create a right to sell;

b) a maturity record shall not create a right to procure;

c) a recognition shall not create a right to claim certification;

d) a Docket status shall not create a right to claim Grid adoption;

e) a Grid review shall not create a right to public authority adoption;

f) a public-safe report shall not create a right to regulated reliance;

g) a finance-readiness note shall not create a right to capital;

h) a sponsor acknowledgment shall not create a right to governance influence;

i) a host status shall not create a right to territorial exclusivity;

j) a regional hub status shall not create a right to alter global doctrine;

k) a Nexus affiliation shall not create a right to use public-good marks beyond approved use.

65.4.3 The Corporation may interface with second-stack actors where doing so advances its mission, improves evidence quality, supports public-safe reporting, tests real-world readiness, supports standards-aligned interoperability, enables lawful regionalization, improves finance-readiness, or strengthens public-good infrastructure. Such interface shall be governed by written scope, conflict controls, claims discipline, data protections, public authority boundaries, procurement neutrality, competition-law discipline, and non-execution perimeter controls.

65.4.4 The public-good stack shall not be weakened merely because second-stack pathways are commercially valuable. Commercial value may be a legitimate consequence of disciplined public-good architecture; it shall not be the source of public-good truth, recognition, standing, maturity, or authority.

65.5 Distinction Between Governance, Evidence, Recognition, Finance-Readiness, and Execution. The Corporation shall preserve a strict distinction among governance, evidence, recognition, finance-readiness, and execution. These functions may interact sequentially or through defined interfaces, but they shall not be merged into one uncontrolled pathway.

65.5.1 Governance means the lawful adoption, supervision, interpretation, correction, delegation, and control of the Corporation’s internal authority, institutional boundaries, public-good purpose, records, policies, programs, committees, officers, and public-facing role.

65.5.2 Evidence means the documented, reviewable, challengeable, source-aware, limitation-aware, methodologically bounded, and correctionable information, analysis, record, benchmark, observation, dataset, technical finding, safeguards finding, scenario result, or proof input produced, received, or maintained under approved procedures.

65.5.3 Recognition means a recorded public-good or institutional status, acknowledgment, maturity statement, designation, registry entry, badge, award, standing position, Docket position, public-safe acknowledgment, comparability statement, or other status-bearing act issued under approved recognition rules.

65.5.4 Finance-readiness means the preparation, translation, structuring, documentation, gap identification, and non-executing presentation of evidence in forms that may assist capital, insurance, public finance, sponsor, infrastructure, or development-finance actors to conduct their own lawful diligence, without the Corporation advising, offering, arranging, underwriting, insuring, brokering, rating, lending, investing, placing, managing, clearing, settling, guaranteeing, allocating, or executing capital.

65.5.5 Execution means the downstream legal, financial, procurement, engineering, operational, commercial, regulated, public authority, infrastructure, project, professional, or market act by which a decision is implemented, capital is committed, contracts are performed, systems are deployed, services are delivered, regulated rights arise, public authority consequences occur, or legal obligations are carried into effect by actors lawfully authorized to do so.

65.5.6 No sequence of governance, evidence, recognition, or finance-readiness shall be described as execution by the Corporation. No execution pathway shall claim to be public-good governance merely because it relies upon, references, supports, funds, implements, or benefits from public-good outputs.

65.5.7 Where a matter moves from one function to another, the transition shall require a record adequate to preserve meaning. In particular:

a) evidence may inform recognition only through an approved review and status record;

b) recognition may inform finance-readiness only where the reliance boundary and status limits are preserved;

c) finance-readiness may inform lawful execution only by separate downstream actors under their own authority;

d) execution may generate feedback to evidence only through documented after-action, monitoring, assurance, or correction channels;

e) public authority participation may inform learning only within recorded capacity and shall not become approval by inference;

f) sponsor participation may support activity only within support-without-control rules and shall not become a merits signal by inference.

65.6 Separateness of Boards, Committees, Officers, and Delegated Bodies. The Board of the Corporation shall remain the fiduciary oversight body of the Corporation and shall not be displaced by any committee, advisory council, working group, registry panel, recognition panel, sponsor council, public authority room, capital-reader room, technical panel, regional body, management office, founder group, staff team, external adviser, or affiliated institution. Delegation shall support governance; it shall not dissolve accountability.

65.6.1 Committees, panels, councils, working groups, and delegated bodies shall act only within their mandates. A recommendation, report, finding, review, score, draft recognition, maturity assessment, claims review, publication clearance, public authority note, sponsor note, finance-readiness note, Docket note, Grid note, or advisory conclusion shall not become a final institutional act unless the applicable authority and record requirements have been satisfied.

65.6.2 Officers and management may implement, coordinate, prepare, supervise, report, communicate, and administer within delegated authority, but shall not alter constitutional role separation, waive legal separateness, bind other institutions, represent unapproved authority, approve reserved matters, convert public-good outputs into commercial rights, approve regulated execution, or imply public authority endorsement unless expressly authorized.

65.6.3 Advisory bodies shall not be described as decision-making bodies unless the record supports that status. Public authority advisory participation, technical expert participation, sponsor advisory participation, community advisory participation, academic advisory participation, or capital-reader participation shall not be used to imply that such participants govern the Corporation or approve its outputs.

65.6.4 Where the same individual serves, advises, funds, or participates in more than one Nexus-related institution or surface, that person shall observe role-specific conduct, conflict, confidentiality, record, information-barrier, and authority rules. Multiple affiliations shall not permit information leakage, authority borrowing, unrecorded delegation, private benefit, sponsor influence, public authority confusion, finance-perimeter drift, or claims inflation.

65.7 No Cross-Entity Commitment Without Competent Authority. The Corporation shall not bind, commit, represent, guarantee, speak for, delegate on behalf of, accept obligations for, or create reliance concerning any other Nexus institution, consortium, company, project SPV, sponsor, host, vendor, public authority, university, funder, capital actor, community, or participant unless a competent authority has approved such act and the authority is recorded in a written instrument.

65.7.1 No director, officer, employee, contractor, committee, adviser, member, participant, or affiliate shall state or imply that another institution will fund, approve, certify, adopt, procure, host, deploy, insure, underwrite, finance, support, regulate, endorse, recognize, publish, or operate any matter unless the statement is supported by a current, authorized, and specific record.

65.7.2 The Corporation shall not allow documents, slide decks, public statements, sponsor packages, proposals, letters of support, concept notes, media materials, grant applications, public authority briefings, regional hub materials, finance-readiness materials, Docket materials, Grid materials, or technical papers to imply cross-entity commitment by listing logos, names, titles, participants, or institutional relationships without the required permission and claims review.

65.7.3 Where the Corporation participates in a joint initiative, the governing instrument shall specify, as applicable:

a) the parties;

b) the purpose;

c) the legal relationship;

d) what each party is and is not committing to do;

e) which party controls which records;

f) which party controls which public communications;

g) which party bears which costs;

h) which party bears which liabilities;

i) which party controls data and access;

j) whether any intellectual property, software, dataset, mark, method, report, or technical baseline is shared, licensed, or reserved;

k) whether public authority, sponsor, donor, or capital-reader participation is involved;

l) what claims are permitted;

m) what claims are prohibited;

n) how conflicts are handled;

o) how correction, withdrawal, closeout, and supersession are managed;

p) what happens upon termination.

65.7.4 No cross-entity commitment shall be inferred from silence, attendance, courtesy review, circulation, calendar invitation, informal email, meeting note, shared workspace access, draft document access, public announcement, sponsorship discussion, or prior collaboration.

65.8 Claims Discipline for Role Separation and Separateness. All public and institutional claims concerning the Corporation’s relationship to any Nexus institution, public authority, sponsor, host, vendor, consortium, project vehicle, university, capital actor, community, or participant shall match the record and preserve role separation. Claims discipline shall apply to written, oral, visual, digital, contractual, media, social media, dashboard, registry, report, slide, proposal, website, announcement, logo, badge, map, diagram, and event-stage communications.

65.8.1 The Corporation shall not make, approve, tolerate, or fail to correct claims that imply:

a) legal merger where there is coordination;

b) agency where there is cooperation;

c) control where there is alignment;

d) endorsement where there is participation;

e) public authority approval where there is observation;

f) procurement readiness where there is recognition;

g) financeability where there is finance-readiness;

h) certification where there is evidence review;

i) Grid adoption where there is Docket consideration;

j) execution authority where there is public-good governance;

k) territorial exclusivity where there is regional participation;

l) sponsor control where there is sponsorship;

m) technical validation where there is demonstration;

n) official standard where there is mapping, reference, or alignment;

o) regulated advice where there is educational or readiness material;

p) institutional guarantee where there is bounded reliance.

65.8.2 Any claim that describes the Corporation as “official,” “authorized,” “approved,” “certified,” “selected,” “endorsed,” “backed,” “validated,” “finance-ready,” “procurement-ready,” “government-adopted,” “public authority approved,” “Grid-integrated,” “standard-setting,” “regulatory,” “licensed,” “guaranteed,” “investment-grade,” “insured,” “underwritten,” “preferred,” “exclusive,” or any equivalent term shall be reviewed against the record before use.

65.8.3 Where a relationship is nuanced, the Corporation shall prefer a longer truthful statement over a shorter misleading statement. Institutional seriousness requires exactness. A communication may be elegant, compact, and market-facing, but it shall not be inaccurate.

65.8.4 Any misleading role or separateness claim shall be subject to correction, withdrawal, clarification, takedown, amendment, notice to affected parties, claims-library revision, participant discipline, sponsor remedy, contract cure, or escalation to the Board or applicable committee.

65.9 Records, Registers, and Evidence of Role Authority. The Corporation shall maintain records sufficient to establish, verify, audit, correct, and explain role authority, legal separateness, relationship status, delegation, participation capacity, recognition status, maturity status, Docket status, Grid status, sponsor status, public authority capacity, finance-readiness boundary, and claims permissions.

65.9.1 The Corporation’s records system shall be capable of distinguishing:

a) legal entity records;

b) governance authority records;

c) officer authority records;

d) committee mandate records;

e) delegation records;

f) member and participant records;

g) sponsor and donor records;

h) vendor and provider records;

i) host and hub records;

j) public authority capacity records;

k) capital-reader and finance-readiness room records;

l) registry and recognition records;

m) Docket and Grid records;

n) publication and public-safe reporting records;

o) data-sharing and access records;

p) intellectual property and licensing records;

q) conflict and recusal records;

r) correction and supersession records;

s) closeout and termination records.

65.9.2 A role shall not be treated as valid merely because it is widely understood, historically assumed, publicly repeated, visually displayed, commercially useful, or operationally convenient. Material role authority must be traceable to a competent record.

65.9.3 Where a role record is incomplete, ambiguous, stale, contradicted, superseded, contested, or inconsistent with public claims, the Corporation shall apply the most restrictive interpretation until the matter is clarified by competent authority.

65.9.4 Records shall be retained in a manner that permits later review of why a relationship was described in a particular way, why a participant was admitted to a particular room, why a public authority was named or not named, why a sponsor was permitted or restricted, why a recognition was granted or withheld, why a Docket or Grid status was recorded, and why a claim was approved or corrected.

65.10 Shared Personnel, Shared Services, and Information-Barriers. The Corporation may, where lawful and approved, share personnel, contractors, consultants, services, facilities, systems, software, repositories, administrative support, communications support, technical infrastructure, research support, fiscal services, or other resources with another institution or actor. Such sharing shall not alter legal separateness, role separation, fiduciary duties, confidentiality obligations, data rights, public-good boundaries, or authority records.

65.10.1 Any material shared-service arrangement shall be recorded and shall identify:

a) the parties;

b) the services or resources shared;

c) the authority under which the arrangement is approved;

d) the cost allocation or contribution structure;

e) the data and confidentiality rules;

f) the intellectual property rules;

g) the records custody rules;

h) the public communications rules;

i) the conflict controls;

j) the termination and closeout rules;

k) any information barriers required.

65.10.2 Where personnel serve multiple roles, they shall act in the capacity appropriate to the specific matter. A person acting for the Corporation shall not use information, authority, records, confidential materials, data access, sponsor knowledge, public authority access, finance-readiness records, or technical review materials for another institution or commercial actor unless permitted by law, agreement, policy, and the applicable record.

65.10.3 The Corporation shall maintain information barriers where required to protect:

a) confidential data;

b) personal information;

c) community-protected knowledge;

d) public authority materials;

e) sponsor-sensitive materials;

f) vendor-sensitive materials;

g) benchmark integrity;

h) Docket or Grid review integrity;

i) finance-readiness non-execution;

j) procurement neutrality;

k) legal privilege;

l) conflict-sensitive matters;

m) regulatory-perimeter discipline;

n) public-safe publication integrity.

65.10.4 Shared infrastructure shall not create shared authority. Shared email domains, shared cloud systems, shared repositories, shared file structures, shared meeting rooms, shared visual systems, shared databases, shared calendars, or shared program-management tools shall be configured and described so that the applicable legal entity, authority holder, custodian, data role, and access limits remain clear.

65.11 Public Authority Boundary and Non-Substitution Rule. The Corporation shall not permit its public-good role, Nexus affiliation, public-facing legitimacy, recognition records, public-safe reports, evidence outputs, stakeholder rooms, Nexus Universe participation, Nexus Observatory records, Docket records, Grid records, or finance-readiness materials to be represented as public authority action unless a competent public authority has separately and lawfully taken such action and the claim is expressly authorized.

65.11.1 Public authorities may participate in learning, observation, scenario work, controlled rooms, review, consultation, public-safe discussion, finance-readiness dialogue, technical demonstrations, Academy activity, regional hub activity, or stakeholder formation only within recorded capacity. Their participation shall not be used to imply:

a) procurement;

b) public tender;

c) endorsement;

d) adoption;

e) approval;

f) certification;

g) regulatory clearance;

h) official exercise;

i) emergency readiness;

j) public warning;

k) public finance commitment;

l) budget commitment;

m) policy adoption;

n) sovereign mandate;

o) delegated authority;

p) public infrastructure acceptance;

q) official public reliance.

65.11.2 The Corporation shall preserve the distinction between public-good legitimacy and public authority. Public-good legitimacy may support trust, participation, evidence quality, stakeholder formation, and public-safe reporting. It does not substitute for statute, regulation, public procurement, public finance approval, emergency command authority, public warning authority, regulator action, or governmental decision-making.

65.11.3 Any use of public authority name, title, seal, logo, flag, quote, photograph, participation status, meeting reference, room attendance, document review, or contribution shall be governed by prior classification, permission, claims review, and record control.

65.12 Finance-Readiness Boundary and No Capital-Execution Collapse. The Corporation shall preserve the boundary between public-good records, maturity records, recognition records, evidence records, public-safe reports, finance-readiness inputs, and regulated financial execution. Nothing in the Corporation’s Nexus role shall be interpreted to authorize the Corporation to act as a broker, dealer, investment adviser, underwriter, insurer, reinsurer, lender, bank, fund manager, rating agency, placement agent, custodian, payment processor, clearinghouse, exchange, capital allocator, guarantee provider, fiduciary financial adviser, or regulated financial intermediary unless separately and lawfully authorized, which shall not be presumed.

65.12.1 Finance-readiness records may describe evidence, gaps, maturity, conditions, dependencies, limitations, risk controls, lifecycle considerations, host readiness, public authority context, insurance-readiness concepts, infrastructure-continuity relevance, and diligence questions. They shall not state or imply that capital should be committed, securities should be purchased, insurance should be underwritten, a loan should be made, credit should be extended, a project is investable, a borrower is creditworthy, a public finance commitment exists, or a capital actor has approved a matter unless the statement is separately lawful, authorized, and recorded by the relevant actor.

65.12.2 A capital reader’s attendance, question, review, comment, participation, or receipt of materials shall not be treated as approval, endorsement, commitment, underwriting interest, investment signal, insurance signal, lending signal, rating signal, public finance signal, or diligence completion.

65.12.3 Where the Corporation works with The Global Risks Alliance (GRA), banks, insurers, development finance institutions, multilateral development banks, investors, infrastructure funds, foundations, public finance actors, sponsors, hosts, or project vehicles, the Corporation shall preserve its own role and shall not allow finance-readiness collaboration to become regulated financial execution by implication.

65.13 Sponsor, Vendor, Host, and Provider Boundary. Sponsors, vendors, hosts, qualified enterprise providers, service providers, technology providers, implementation partners, media partners, and commercial actors may support, participate in, fund, host, demonstrate, provide infrastructure, submit evidence, join rooms, contribute expertise, or pursue lawful downstream opportunities only within recorded scope. Their support or participation shall not create governance authority, recognition authority, public-good authority, Docket authority, Grid authority, public authority access rights, finance-readiness authority, Academy credential authority, or claims rights beyond the record.

65.13.1 Sponsor and vendor support shall be governed by support-without-control. The Corporation may accept money, in-kind support, equipment, cloud credits, software, technical staff, venue support, scholarships, challenge support, report support, Academy support, media support, or infrastructure support only where the support is bounded, recorded, conflict-reviewed, claims-controlled, and consistent with public-benefit integrity.

65.13.2 A sponsor, vendor, host, or provider shall not receive:

a) recognition by payment;

b) award advantage by sponsorship;

c) benchmark advantage by contribution;

d) Docket advancement by relationship;

e) Grid advancement by infrastructure support;

f) public authority access by commercial purchase;

g) public-safe report control by funding;

h) Academy credential control by sponsorship;

i) finance-readiness approval by room participation;

j) procurement preference by demonstration;

k) territorial exclusivity by hosting;

l) governance influence by strategic importance;

m) data access by contribution;

n) institutional endorsement by logo proximity.

65.13.3 Where sponsor, vendor, host, or provider materials describe their participation in the Corporation’s work, such materials shall be subject to approved claims language, review rights, correction rights, and termination rights where required.

65.14 Regional, National, and Local Separateness. Regional Nexus consortiums, national public-good consortiums, national working groups, Nexus Competence Cells, regional hubs, national consortium companies, host-led entities, project SPVs, and local operating bodies shall remain separately classified and separately bounded. The Corporation shall not permit local or regional ambition to rewrite global doctrine, public-good perimeter, role separation, legal separateness, claims discipline, finance-readiness limitations, public authority boundaries, data obligations, Docket discipline, Grid maturity discipline, or correctionability.

65.14.1 Regional and national bodies may adapt, translate, implement, coordinate, convene, localize, train, support, and generate evidence within approved scope. They shall not alter the Corporation’s legal identity, public-good purpose, recognition authority, registry authority, claims rules, public-safe publication authority, or maturity rules unless competent authority expressly authorizes the relevant act.

65.14.2 A regional hub, national consortium, local host, or implementation vehicle shall not claim that it represents the whole Nexus architecture, the Corporation, GRF, GRA, GCRI, a protocol authority, a public authority, or any other institution unless the record supports that claim.

65.14.3 Local law, language, custom, sponsor market, public authority structure, host condition, community need, or commercial opportunity may require localized procedures. Such localization shall be recorded as localization, not as amendment of the common rail or collapse of institutional roles.

65.15 Correction, Escalation, and Remedies for Role Collapse. Any actual, threatened, or reasonably perceived role collapse, legal separateness confusion, public authority misrepresentation, sponsor-control risk, finance-perimeter drift, procurement implication, certification implication, maturity overclaim, Docket overclaim, Grid overclaim, or cross-entity commitment risk shall be corrected promptly.

65.15.1 Corrective action may include, as applicable:

a) clarification of role records;

b) amendment of public language;

c) withdrawal of statements;

d) correction of website, media, slide, proposal, report, dashboard, registry, or marketing materials;

e) notice to affected parties;

f) sponsor, vendor, host, or participant instruction;

g) contract amendment;

h) conflict review;

i) information-barrier implementation;

j) committee escalation;

k) Board escalation;

l) legal review;

m) regulatory-perimeter review;

n) public authority capacity reclassification;

o) finance-readiness boundary clarification;

p) suspension of room access;

q) suspension of claims permission;

r) suspension, deferral, or correction of recognition, Docket, or Grid status;

s) termination or non-renewal of participation;

t) public correction where required to protect trust.

65.15.2 The Corporation shall not delay correction merely because the misleading statement benefits fundraising, sponsor relations, public relations, media coverage, partner confidence, recruitment, regional expansion, capital interest, or commercial opportunity.

65.15.3 Where role collapse has created reliance risk, the Corporation shall evaluate whether additional measures are required, including direct notice to affected persons, correction of controlled materials, withdrawal of reliance language, preservation of evidence, independent review, Board report, or legal advice.

65.15.4 Repeated or intentional role collapse, authority borrowing, public authority misrepresentation, sponsor-control conduct, finance-perimeter breach, procurement implication, or false maturity claim may constitute grounds for discipline, removal, termination, suspension, loss of status, refusal of renewal, or other remedy available under this Bylaw, applicable policy, or contract.

65.16 Controlling Interpretation. This Section shall be interpreted as a constitutional protection for the Corporation and the Nexus architecture. Where doubt exists, the interpretation that best preserves role separation, legal separateness, public-good integrity, non-execution, public authority boundary discipline, finance-readiness limitation, sponsor support-without-control, procurement neutrality, data and safeguards protection, claims truthfulness, Docket discipline, Grid maturity discipline, correctionability, and record-validity shall prevail.

65.16.1 No provision of this Bylaw, no committee mandate, no officer delegation, no sponsor agreement, no host agreement, no regional hub arrangement, no public authority participation, no finance-readiness room, no technical record, no recognition, no maturity record, no Docket status, no Grid status, no public-safe report, no visual map, no public statement, no annual program, no operational practice, and no course of dealing shall be read to override this Section unless a later amendment expressly identifies this Section and lawfully modifies it.

65.16.2 This Section shall apply continuously across all programs, registries, recognition systems, maturity records, public-safe reporting channels, Nexus Universe interfaces, Nexus Network interfaces, Nexus Observatory interfaces, Nexus Standards interfaces, Nexus Risk Management interfaces, regional and national formations, public authority rooms, sponsor relationships, finance-readiness pathways, Academy surfaces, publication processes, Docket records, Grid records, and closeout activities.

65.16.3 The Corporation’s credibility shall depend not only on the quality of its evidence or the importance of its mission, but on its ability to remain exactly what it is: a role-bounded public-good institution operating within a federated architecture of legally separate actors, recorded authorities, disciplined interfaces, and correctionable public trust.

Section 66. Public-Good Stack and Enterprise Stack Separation

66.1 Public-Good Stack Definition for Bylaw Purposes. For purposes of this Bylaw, the “Public-Good Stack” means the non-executing, public-benefit, evidence-bearing, methods-governed, observability-enabled, ontology-stewarded, safeguards-protected, correctionable, and records-valid institutional layer through which GCRI Canada and aligned public-good institutions create, maintain, review, preserve, publish, correct, and interoperate shared public-good infrastructure, knowledge infrastructure, technical baselines, evidence systems, public-safe outputs, and mission-aligned coordination instruments.

66.1.1 The Public-Good Stack shall include, without limitation, those functions, records, assets, systems, and institutional surfaces that relate to:

a) public-benefit research and public-good R&D;

b) evidence doctrine, evidence records, evidence classifications, evidence packs, assurance packs, and evidence lineage;

c) scientific-operational methods, validation methods, confidence methods, uncertainty methods, reproducibility methods, replication methods, benchmarking methods, source-lineage methods, and correction methods;

d) observability methods, Nexus Observatory methods, node methods, hub methods, cluster methods, hotspot methods, degraded-mode awareness methods, public-safe dashboard methods, and mission-critical signal interpretation methods;

e) ontologies, taxonomies, schemas, controlled vocabularies, data dictionaries, semantic interoperability structures, AI-readable knowledge structures, and public-safe vocabulary discipline;

f) public-good software, open technical baselines, reference architectures, APIs, SDKs, test harnesses, gold vectors, negative tests, public-safe visualization tools, and conformance-supporting technical assets without certification effect;

g) data governance methods, AI governance methods, cyber governance methods, privacy-preserving methods, compute-to-data methods, verifiable compute methods, verifiable intelligence methods, model governance methods, and secure release methods;

h) community safeguards, Indigenous knowledge safeguards, local and territorial knowledge safeguards, protected environmental knowledge safeguards, public-safe mapping controls, grievance pathways, non-retaliation, and protected participation mechanisms;

i) public authority learning, evidence literacy, technical literacy, public-safe reporting literacy, scenario methods, simulation methods, and controlled non-executing public authority participation;

j) technical evidence inputs to The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, Nexus Network, Nexus Observatory, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, regional consortiums, national consortiums, national working groups, national companies, Project SPVs, and qualified enterprise providers, only within GCRI Canada’s public-good and non-executing remit;

k) correctionability, supersession, withdrawal, retraction, archival, historical traceability, and official-record continuity;

l) validity-by-record, case IDs, official registers, gazette or notice-stream entries, controlled repositories, classification records, and authoritative governance records.

66.1.2 The Public-Good Stack shall not be interpreted as a holding company, commercial delivery channel, investment platform, procurement authority, public regulator, emergency command structure, public warning system, certification body, capital allocator, insurance intermediary, lender, underwriter, broker, fund, market operator, project developer, systems integrator, managed-services provider, public-private partnership vehicle, or enterprise execution platform.

66.1.3 The Public-Good Stack may be commercially valuable, strategically important, technically sophisticated, public authority relevant, finance-readable, sponsor-supported, and enterprise-useful. None of those qualities shall convert it into the Enterprise Stack or into regulated or execution-facing activity.

66.1.4 The Public-Good Stack shall be interpreted through the following controlling propositions:

a) public-good evidence may support downstream decision-making but shall not substitute for downstream decision authority;

b) public-good methods may support comparability but shall not constitute certification unless a lawful and separately authorized certification program exists;

c) public-good observability may support awareness but shall not constitute public warning, emergency command, public authority action, or operational instruction;

d) public-good ontologies may support interoperability but shall not create legal equivalence, procurement mandate, or regulated compliance status;

e) public-good software may support implementation but shall not create provider preference, procurement requirement, or commercial entitlement;

f) public-safe reporting may support public literacy but shall not create official public authority notice, regulated reliance, or market recommendation;

g) public-good records may support recognition, finance-readiness, standards alignment, or enterprise execution only through separate competent authority, role separation, and recorded interface.

66.2 Enterprise Stack Definition for Bylaw Purposes. For purposes of this Bylaw, the “Enterprise Stack” means the lawful, downstream, market-facing, project-facing, service-facing, finance-facing, procurement-facing, asset-facing, operational, commercial, or regulated execution layer through which actors other than GCRI Canada may own assets, contract, finance, insure, procure, deploy, operate, sell, maintain, integrate, deliver, license, underwrite, invest, lend, guarantee, manage, or execute systems, projects, services, infrastructure, products, or transactions.

66.2.1 The Enterprise Stack may include, without limitation:

a) national consortium companies;

b) regional or national implementation companies;

c) Project SPVs;

d) qualified enterprise providers;

e) commercial operators;

f) system integrators;

g) technology vendors;

h) infrastructure providers;

i) cloud, compute, AI, telecom, AI-RAN, O-RAN, cyber, sensing, robotics, geospatial, digital twin, and software providers;

j) banks, lenders, insurers, reinsurers, underwriters, guarantors, investors, funds, development finance institutions, multilateral development banks, leasing companies, public finance actors, and other capital actors acting within their own lawful mandates;

k) public procurement bodies and lawful purchasers;

l) host institutions acting in operational, commercial, facility, infrastructure, or asset-owner capacities;

m) contractors, subcontractors, suppliers, manufacturers, maintainers, managed-service providers, field-service providers, and implementation partners;

n) project developers, project sponsors, public-private partnership vehicles, concessionaires, operators, asset companies, and other lawful execution vehicles.

66.2.2 The Enterprise Stack may use, reference, interoperate with, support, fund, implement, test against, or derive benefit from Public-Good Stack outputs only where the applicable rights, licenses, contracts, records, role boundaries, claims restrictions, safeguards, data controls, non-execution boundaries, and correction obligations are satisfied.

66.2.3 Enterprise Stack actors shall not become Public-Good Stack authorities merely because they contribute resources, provide infrastructure, fund work, sponsor activities, implement outputs, host nodes, attend rooms, participate in working groups, submit evidence, operate projects, provide data, engage public authorities, participate in Nexus Universe, support Nexus Observatory, or use Nexus-compatible language.

66.2.4 The Enterprise Stack shall remain responsible for its own lawful execution, including, where applicable, contracts, procurement, permits, professional advice, engineering responsibility, cybersecurity controls, operational safety, insurance, financing, tax, regulatory compliance, data processing, privacy compliance, labour and employment obligations, public authority approvals, customer obligations, warranties, service levels, and liability.

66.3 Public-Good Stack Functions. GCRI Canada’s role within the Public-Good Stack shall be limited to public-benefit, non-executing, technical-stewardship functions, including evidence, methods, observability, ontology, research integrity, public-good software, open technical baselines, public-safe outputs, safeguards, standards-supporting materials, maturity inputs, readiness inputs, and correction.

66.3.1 GCRI Canada may perform Public-Good Stack functions that include:

a) developing, maintaining, reviewing, correcting, and publishing evidence methods;

b) developing and maintaining public-good technical baselines and reference architectures;

c) developing, stewarding, or supporting open technical assets and public-good software;

d) supporting interoperability through schemas, ontologies, APIs, technical profiles, semantic mappings, and conformance-supporting tools;

e) supporting observability through methods for nodes, hubs, clusters, sensors, AI-RAN, O-RAN, DePIN, digital twins, cyber telemetry, geospatial systems, sovereign compute, and public-safe dashboards;

f) creating evidence inputs for GRF-controlled registry, recognition, standing, Docket, Grid, maturity, claims-discipline, and public-safe reporting functions;

g) creating technical evidence inputs for GRA-controlled finance-readiness, capital-readability, insurance-readiness, proof-pack, and diligence-translation functions;

h) supporting Nexus Standards or Protocol Authority functions through evidence requirements, methods, schema support, test harnesses, reference implementations, and technical baseline support, without becoming the standards or protocol authority by default;

i) supporting public authority learning through non-executing technical literacy, evidence literacy, scenario methods, simulation methods, and public-safe explanation;

j) supporting Nexus Academy and Nexus Competence Cells through training materials, methods, labs, technical literacy, evidence literacy, and public-good capacity formation;

k) supporting regional and national consortiums through lawful localization materials, technical methods, evidence architecture, safeguards logic, and compatibility notes;

l) supporting national companies, Project SPVs, and qualified enterprise providers through public-good compatibility inputs, technical baselines, evidence methods, and correction signals, without assuming enterprise execution responsibility.

66.3.2 GCRI Canada may record, structure, and transmit Public-Good Stack inputs to other actors, but such inputs shall remain bounded by purpose, classification, reliance limits, and correction pathways. GCRI Canada shall not permit its inputs to be described as final recognition, finance-readiness determination, certification, procurement approval, public authority endorsement, public warning, investment advice, insurance approval, underwriting support, credit approval, rating, or execution instruction.

66.3.3 Where Public-Good Stack work creates outputs that may be valuable to enterprise actors, such outputs shall remain subject to:

a) public-benefit purpose;

b) non-distribution and no private inurement;

c) non-execution;

d) sponsor and provider non-control;

e) provider neutrality;

f) procurement neutrality;

g) public authority boundary discipline;

h) finance-readiness boundary discipline;

i) data, AI, cyber, privacy, and safeguards controls;

j) controlled vocabulary;

k) validity-by-record;

l) correctionability;

m) lawful licensing and intellectual property terms.

66.4 Enterprise Stack Functions. Enterprise Stack functions shall include project development, asset ownership, contracting, capital formation, operations, service delivery, technology supply, insurance placement, lending, procurement response, and commercial execution by lawful actors. Such functions shall remain outside GCRI Canada’s institutional role unless a particular activity is lawfully and expressly permitted within GCRI Canada’s non-executing public-benefit mandate and does not cross into prohibited execution.

66.4.1 Enterprise Stack functions may include, without limitation:

a) forming, capitalizing, financing, owning, leasing, operating, maintaining, insuring, or disposing of infrastructure assets;

b) responding to procurements, tenders, requests for proposals, grants, concessions, public-private partnership processes, or commercial opportunities;

c) entering into customer contracts, vendor contracts, service contracts, operating agreements, lease agreements, finance agreements, insurance agreements, project agreements, concession agreements, or implementation agreements;

d) raising capital, issuing securities, arranging loans, obtaining insurance, negotiating guarantees, structuring project finance, or securing public finance support through lawful actors;

e) providing professional, engineering, cybersecurity, financial, insurance, legal, technical, operating, installation, integration, managed-service, or field-service services;

f) deploying, operating, monitoring, maintaining, repairing, replacing, upgrading, and decommissioning systems;

g) assuming warranties, liabilities, service-level obligations, uptime obligations, performance obligations, customer obligations, and regulatory obligations;

h) making commercial decisions regarding pricing, customers, suppliers, markets, staffing, vendors, subcontractors, financing, and business strategy, subject to competition-law and other applicable legal controls;

i) conducting regulated activities only where the actor is properly authorized, licensed, exempt, or otherwise lawfully permitted to do so.

66.4.2 GCRI Canada shall not perform Enterprise Stack functions by implication, convenience, urgency, reputational pressure, funding pressure, public authority expectation, technical centrality, sponsor expectation, partner demand, or operational necessity.

66.4.3 Where Enterprise Stack actors rely on GCRI Canada outputs, the applicable interface shall preserve:

a) no agency;

b) no partnership;

c) no joint venture;

d) no shared treasury;

e) no shared employer;

f) no shared liability;

g) no GCRI Canada guarantee;

h) no public authority substitution;

i) no certification by default;

j) no procurement recommendation;

k) no finance, insurance, investment, lending, rating, or underwriting implication;

l) no sponsor or provider preference;

m) no public-good authority transfer.

66.5 GCRI Canada Not an Enterprise Stack Actor. GCRI Canada shall not be treated, described, governed, funded, marketed, contracted, or operated as an Enterprise Stack actor. Its public-benefit and public-good technical-stewardship role shall not be converted into commercial execution, project execution, asset ownership, regulated intermediation, procurement participation, provider selection, or operational control.

66.5.1 Without limiting the generality of the foregoing, GCRI Canada shall not act as:

a) a project developer;

b) a project sponsor in the commercial or securities sense;

c) a project SPV;

d) a national consortium company;

e) a regulated fund;

f) a lender;

g) a guarantor;

h) an insurer or reinsurer;

i) an underwriter;

j) a broker, dealer, placement agent, or finder;

k) a rating agency;

l) an investment adviser;

m) a procurement agent;

n) a public-private partnership bidder;

o) a systems integrator for commercial deployment;

p) a managed-services operator;

q) an infrastructure operator by default;

r) a commercial software vendor by default;

s) a preferred provider;

t) a public authority implementation body;

u) an emergency command or public warning authority.

66.5.2 GCRI Canada may own, license, maintain, or control technical assets, software, repositories, datasets, equipment, systems, records, publications, or infrastructure necessary for its public-benefit operations. Such ownership or control shall not convert GCRI Canada into an Enterprise Stack actor unless the activity crosses into commercial execution or another prohibited function.

66.5.3 GCRI Canada may charge lawful fees, accept sponsorships, receive grants, receive donations, recover costs, enter service agreements, license public-good assets, and maintain operational infrastructure where consistent with this Bylaw. Revenue generation or cost recovery shall not convert GCRI Canada into an enterprise execution vehicle.

66.5.4 Any proposed activity that could reasonably be interpreted as Enterprise Stack activity shall be subjected to perimeter review before commencement. Where doubt remains, the activity shall be narrowed, externalized, routed to a lawful Enterprise Stack actor, held, quarantined, or rejected.

66.6 Enterprise Stack Actors Not Public-Good Authorities by Participation. Enterprise Stack actors shall not acquire Public-Good Stack authority by participation in GCRI Canada activities. Participation, funding, contribution, hosting, technical support, data contribution, room attendance, research collaboration, challenge involvement, Nexus Universe participation, Nexus Observatory involvement, Nexus-compatible mapping, or public-good alignment shall not create authority over GCRI Canada’s research, evidence, methods, technical baselines, publications, public authority interfaces, Docket inputs, Grid inputs, GRF inputs, GRA inputs, or public claims.

66.6.1 Enterprise Stack actors shall not:

a) control evidence classifications;

b) control methods;

c) control research findings;

d) control technical baselines;

e) control public-good software release decisions;

f) control publication conclusions;

g) control public-safe reporting language;

h) control claims discipline;

i) control public authority access or references;

j) control finance-readiness inputs;

k) control standards-supporting outputs;

l) control Docket or Grid evidence inputs;

m) control correction decisions;

n) control ontology or controlled vocabulary meaning;

o) control community safeguards or protected knowledge treatment;

p) control data access or AI-use approval except in relation to their own lawful systems and data under written terms.

66.6.2 Enterprise Stack actors may provide factual input, technical information, operational context, implementation feedback, data, tools, equipment, staff support, test environments, funding, or review comments. Such contributions shall be received as contributions, not authority. GCRI Canada shall retain the ability to accept, reject, qualify, correct, restrict, or disregard such inputs according to its public-benefit mandate, evidence methods, safeguards, conflicts controls, and non-execution boundary.

66.6.3 No Enterprise Stack actor shall use its participation in GCRI Canada to claim that it is “approved,” “certified,” “preferred,” “selected,” “official,” “recognized,” “finance-ready,” “procurement-ready,” “Grid-integrated,” “Docket-approved,” “public authority endorsed,” “GCRI-backed,” “Nexus-certified,” or equivalent unless the exact claim is separately authorized by a competent record and is not misleading.

66.7 No Role Collapse Between GCRI Canada and National Consortium Companies. National consortium companies shall be treated as Enterprise Stack or second-stack investible national platforms where separately constituted. They may interface with GCRI Canada for technical evidence, methods, observability, public-good compatibility, open baseline, research, training, and correction purposes. They shall not be treated as GCRI Canada, as part of GCRI Canada, as controlling GCRI Canada, or as possessing GCRI Canada’s public-good authority.

66.7.1 GCRI Canada shall not become a national consortium company by supporting, advising, informing, collaborating with, or licensing public-good assets to such company.

66.7.2 A national consortium company shall not become a public-good steward by using GCRI Canada outputs, supporting GCRI Canada programs, participating in Nexus activities, hosting Observatory-related infrastructure, implementing public-good baselines, or contributing funding or technical support.

66.7.3 Any interface between GCRI Canada and a national consortium company shall preserve:

a) separate legal personality;

b) separate treasury;

c) separate governance;

d) separate records;

e) separate employer status;

f) separate liability;

g) separate public communications;

h) separate authority over commercial execution;

i) no automatic access to confidential Public-Good Stack materials;

j) no control over GCRI Canada research, evidence, methods, publications, technical baselines, or corrections;

k) no use of GCRI Canada name to market securities, investment interests, debt instruments, insurance products, procurement bids, commercial offerings, or project participation except as expressly authorized and accurately described.

66.7.4 Where GCRI Canada provides technical evidence or public-good compatibility support to a national consortium company, such support shall be documented in an interface agreement, contribution record, license, technical note, or other appropriate record identifying scope, limits, claims language, data controls, IP terms, confidentiality, correction pathways, and non-execution boundaries.

66.8 No Role Collapse Between GCRI Canada and Project SPVs. Project SPVs shall be treated as project-level Enterprise Stack execution vehicles where separately constituted. GCRI Canada may provide public-good evidence, methods, technical baseline, observability, data-governance, safeguards, or compatibility inputs to Project SPVs where lawful and mission-aligned, but shall not control, guarantee, finance, endorse, certify, own, operate, manage, underwrite, insure, rate, procure, or execute the project by default.

66.8.1 GCRI Canada shall not be treated as a Project SPV merely because a project uses GCRI Canada methods, evidence artifacts, public-good software, open baselines, technical notes, observability methods, public-safe reporting logic, or Nexus-compatible language.

66.8.2 A Project SPV shall not use GCRI Canada’s name, marks, records, outputs, technical baselines, public-good assets, publications, or Nexus relationship to imply:

a) investment recommendation;

b) credit approval;

c) insurance approval;

d) underwriting support;

e) performance guarantee;

f) procurement approval;

g) public authority approval;

h) certification;

i) Grid status;

j) Docket advancement;

k) public-good endorsement;

l) public finance approval;

m) sponsor-backed investment opportunity;

n) official Nexus project status beyond the record.

66.8.3 GCRI Canada shall not accept any role in a Project SPV that would compromise its public-benefit purpose, non-execution boundary, legal separateness, evidence independence, sponsor and provider neutrality, public authority boundary discipline, finance-readiness boundary, or correctionability.

66.8.4 Where a Project SPV uses GCRI Canada inputs, the relevant records shall specify whether the input is:

a) public material;

b) controlled material;

c) licensed technical asset;

d) evidence input;

e) methods input;

f) observability input;

g) public-safe reporting input;

h) standards-supporting input;

i) training input;

j) correction signal;

k) non-reliance-bound technical note.

66.9 No Role Collapse Between GCRI Canada and Qualified Enterprise Providers. Qualified enterprise providers may provide tools, services, systems, data, equipment, compute, AI capabilities, AI-RAN systems, O-RAN systems, sensors, dashboards, cyber capabilities, integration services, managed services, technical support, or implementation support to GCRI Canada or to other Nexus-related actors under lawful terms. Such participation shall not convert the provider into a Public-Good Stack authority, and shall not convert GCRI Canada into the provider’s commercial principal, reseller, guarantor, certifier, procurement agent, or preferred-provider sponsor.

66.9.1 Provider participation shall be governed by written terms addressing, as applicable:

a) scope of contribution or service;

b) ownership and custody of equipment or systems;

c) data access;

d) AI-use limits;

e) cybersecurity obligations;

f) confidentiality;

g) IP rights;

h) license terms;

i) support obligations;

j) export-control obligations;

k) sanctions compliance;

l) competition-law controls;

m) conflict disclosures;

n) public claims;

o) public authority contact;

p) benchmark integrity;

q) Docket or Grid relevance;

r) correction and closeout;

s) offboarding and access revocation.

66.9.2 No provider shall receive preferred status, required-provider status, procurement advantage, certification, recognition, finance-readiness implication, public authority endorsement, or technical conclusion advantage by reason of its contribution to GCRI Canada.

66.9.3 GCRI Canada shall preserve independence in all provider-related evidence, methods, benchmarks, publications, technical baselines, and public-safe outputs. Provider information may be used as evidence only after appropriate classification, source-lineage review, conflict review, reliability assessment, and correction-path assignment.

66.9.4 Where a provider supplies infrastructure used in evidence generation, testing, benchmarking, data processing, AI processing, controlled rooms, public-safe reporting, or technical publication, GCRI Canada shall disclose, record, or control the relationship to the extent required to preserve independence, transparency, reproducibility, and public trust.

66.10 No Role Collapse Between GCRI Canada and Sponsors, Hosts, Contractors, Investors, Insurers, Lenders, or Operators. Sponsors, hosts, contractors, investors, insurers, lenders, operators, and other supporting or participating actors shall remain distinct from GCRI Canada and from the Public-Good Stack authority exercised by GCRI Canada. Their participation shall be governed by support-without-control, public-benefit alignment, conflict discipline, and claims limits.

66.10.1 A sponsor may fund, support, contribute, underwrite costs, provide equipment, sponsor seats, support programs, support publications, support Academy or training activity, support technical environments, or support public-good access only under terms that prohibit sponsor control of evidence, methods, research conclusions, technical baselines, publications, public authority access, Docket inputs, Grid inputs, public-safe outputs, or correction decisions.

66.10.2 A host may provide venue, data context, facilities, infrastructure, local legitimacy, research access, technical environment, community connection, public authority interface, or operational support only under terms that preserve GCRI Canada’s legal separateness, non-execution role, data rights, public claims controls, safety obligations, and public authority boundary.