V. NEXUS
5.1 Nexus Public-Good Stack Alignment
5.1.1 GCRI Canada as an Institution Within the Nexus Public-Good Stack. 5.1.1(a) The Global Centre for Risk and Innovation - Canada shall be understood as an institution within the Nexus public-good stack. Its place within that stack shall be defined by its Canadian public-benefit, nonprofit, non-share, non-distributing, non-executing role as steward of evidence, methods, observability, ontology, technical truth, public-good research and development, public-good software, open technical baselines, Nexus Truth Engine methods, Nexus Observatory methods, public authority learning, public-safe publication, validity-by-record, and correctionability.
5.1.1(b) GCRI Canada’s participation in the Nexus public-good stack shall be constitutional, doctrinal, functional, and records-valid. It shall not be merely branding, affiliation, event participation, technical contribution, publication alignment, or public-facing narrative. GCRI Canada shall participate by preserving upstream technical truth and public-good technical infrastructure in a manner compatible with the broader Nexus architecture and bounded by Canadian law, its articles, its Bylaw, this Charter, and its own corporate records.
5.1.1(c) GCRI Canada shall not be the whole Nexus system. It shall not be presumed to own, control, operate, govern, finance, execute, certify, recognize, regulate, command, procure, or speak for the whole Nexus architecture by reason of its participation in the public-good stack.
5.1.1(d) GCRI Canada’s public-good stack role shall be read together with the distinct roles of The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards / Protocol Authority, Nexus Network, Nexus Universe, Nexus Observatory, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Regional Nexus Consortiums, National Nexus Consortiums, National Consortium Companies, Project SPVs, qualified providers, sponsors, hosts, public authorities, universities, communities, capital readers, and other lawful actors.
5.1.1(e) GCRI Canada shall support the Nexus public-good stack by producing, stewarding, reviewing, maintaining, correcting, and handing off upstream evidence and technical meaning. It shall not convert public-good stack participation into downstream execution, public authority action, finance-readiness, recognition, protocol effect, procurement advantage, certification, provider preference, sponsor control, or market operation.
5.1.1(f) The public-good stack shall be interpreted as a disciplined architecture of separated functions, not as an undifferentiated institutional brand. GCRI Canada’s identity within that architecture shall remain evidence-first, methods-first, observability-first, ontology-first, records-first, public-safe, non-executing, and correctionable.
5.1.1(g) Where any public or internal reference states that GCRI Canada is “within Nexus,” “part of Nexus,” “aligned with Nexus,” “supporting Nexus,” “a Nexus institution,” or equivalent language, such reference shall be read as public-good stack alignment only and not as merger, agency, public authority status, protocol authority, finance authority, recognition authority, procurement authority, or execution authority.
5.1.1(h) The controlling rule shall be that GCRI Canada is a Nexus-aligned public-good technical truth institution, not the Nexus system as a whole.
5.1.2 Public-Good Stack Alignment Without Corporate Merger. 5.1.2(a) Public-good stack alignment shall not create corporate merger. GCRI Canada’s alignment with Nexus doctrines, instruments, vocabulary, technical baselines, evidence practices, public-good software, observability methods, Nexus Truth Engine methods, Nexus Observatory methods, GRF inputs, GRA inputs, Protocol Authority inputs, Nexus Network interfaces, Nexus Universe activities, Nexus Grid structures, Nexus Rails processes, or Nexus Academy materials shall not merge GCRI Canada with any other person or institution.
5.1.2(b) GCRI Canada shall remain a distinct Canadian legal person with its own articles, Bylaw, Charter, Board, officers, corporate records, assets, obligations, liabilities, policies, legal duties, tax status, governance procedures, records, and correction obligations.
5.1.2(c) Shared mission, shared public-good purpose, shared vocabulary, shared records, shared repositories, shared events, shared public materials, shared technical baselines, shared public-good software, shared data tools, shared standards-support work, shared Nexus Universe participation, shared Nexus Observatory methods, or shared institutional doctrine shall not create a single legal entity.
5.1.2(d) GCRI Canada shall not be treated as merged with GCRI US, GRF, GRA, Nexus Standards / Protocol Authority, Nexus Network, Nexus Universe, Nexus Observatory, Regional Nexus Consortiums, National Nexus Consortiums, National Consortium Companies, Project SPVs, qualified providers, sponsors, hosts, public authorities, universities, capital actors, or any other Nexus-aligned body by reason of public-good stack alignment.
5.1.2(e) Any shared services, shared marks, shared repositories, shared data, shared platforms, shared staff support, shared costs, shared publications, shared technical assets, shared public authority interfaces, shared sponsor relationships, shared provider relationships, or shared Nexus interfaces shall require records-valid governance, interface agreements, role definitions, authority mapping, liability boundaries, data controls, IP controls, public claims controls, and correction paths.
5.1.2(f) Public materials shall not describe GCRI Canada as a branch, subsidiary, operating arm, implementation arm, executive office, legal representative, national chapter with automatic authority, or controlling entity of any other Nexus institution unless the governing record lawfully supports that description and the description is consistent with Canadian law, the articles, the Bylaw, and this Charter.
5.1.2(g) Where corporate merger ambiguity arises, GCRI Canada shall correct the language, clarify legal separateness, revise public materials, update interface records, restrict name use, and preserve correction records.
5.1.2(h) The controlling rule shall be that alignment may be deep, but legal personality remains separate.
5.1.3 Public-Good Stack Alignment Without Agency, Partnership, Joint Venture, Parent-Subsidiary Status, Shared Treasury, Shared Liability, or Apparent Authority. 5.1.3(a) Public-good stack alignment shall not create agency, partnership, joint venture, parent-subsidiary status, shared treasury, shared liability, joint employer status, alter ego status, apparent authority, authority transfer, public-private partnership, or common control by default.
5.1.3(b) GCRI Canada shall not bind GRF, GRA, Protocol Authority, Nexus Network, Nexus Universe, Nexus Observatory, Regional Nexus Consortiums, National Nexus Consortiums, National Consortium Companies, Project SPVs, qualified providers, sponsors, hosts, public authorities, universities, capital actors, or other Nexus-aligned actors unless expressly authorized by a lawful records-valid instrument and acting within that instrument’s scope.
5.1.3(c) No other Nexus-aligned actor shall bind GCRI Canada by public-good stack alignment, shared doctrine, shared vocabulary, shared event presence, shared repository work, shared public authority engagement, shared sponsor support, shared provider participation, shared public materials, shared public-good software, shared technical baselines, or shared public-facing narrative.
5.1.3(d) GCRI Canada shall not share treasury, debts, liabilities, revenues, assets, obligations, employment responsibility, tax responsibility, fiduciary responsibility, public authority obligations, finance obligations, procurement obligations, insurance obligations, or execution obligations with another Nexus-aligned actor unless expressly and lawfully recorded.
5.1.3(e) Apparent authority shall not arise by title, proximity, logo placement, website listing, event role, speaking role, council role, dashboard access, repository access, shared email domain, public authority attendance, sponsor acknowledgment, provider contribution, technical centrality, media description, Nexus branding, or repeated cooperation.
5.1.3(f) Interface agreements, MoUs, cooperation records, shared-services agreements, technical contribution records, public authority records, sponsor agreements, provider agreements, data agreements, IP agreements, and Nexus coordination instruments shall state role separation, non-agency, non-partnership, non-joint-venture, non-shared-liability, non-shared-treasury, non-apparent-authority, and correction provisions where material.
5.1.3(g) Where a third party relies on public-good stack alignment to claim agency, partnership, joint venture, shared liability, shared treasury, parent-subsidiary status, public-private partnership, or authority transfer, GCRI Canada shall correct the claim, restrict name use where appropriate, notify affected institutions where appropriate, and preserve correction records.
5.1.3(h) The controlling rule shall be that Nexus alignment coordinates public-good meaning; it does not merge legal responsibility.
5.1.4 Public-Good Stack Alignment as Mission, Doctrine, Vocabulary, Records, Evidence, Methods, Standards-Support, and Interoperability Alignment. 5.1.4(a) Public-good stack alignment shall consist of mission alignment, doctrine alignment, controlled-vocabulary alignment, records alignment, evidence alignment, methods alignment, standards-support alignment, technical-baseline alignment, public-good software alignment, observability alignment, ontology alignment, Nexus Truth Engine method alignment, Nexus Observatory method alignment, public-safe publication alignment, and interoperability alignment.
5.1.4(b) Mission alignment means that GCRI Canada’s Canadian public-benefit purpose shall be carried out in a manner consistent with Nexus public-good objectives, including systemic risk reduction, resilience, technical truth, public authority learning, evidence integrity, safe innovation, public-good technical capacity, and long-horizon institutional memory.
5.1.4(c) Doctrine alignment means that GCRI Canada shall apply, as relevant to its role, the Nexus Constitutional Framework, the Public-Good Stack Framework, the Validity-by-Record Doctrine, the Correctionability Doctrine, the Non-Execution Doctrine, the One Rail / Two Stacks Doctrine, and the Verifiable Compute / Verifiable Intelligence Doctrine.
5.1.4(d) Vocabulary alignment means that GCRI Canada shall use controlled terms consistently across evidence, methods, observability, ontology, public-good software, technical baselines, dashboards, maps, public-safe reports, Academy materials, public authority learning, GRF inputs, GRA inputs, Protocol Authority inputs, Nexus interfaces, and public communications.
5.1.4(e) Records alignment means that GCRI Canada shall maintain records capable of being routed, reviewed, corrected, superseded, restricted, handed off, and understood across the Nexus public-good stack without creating unauthorized downstream effect.
5.1.4(f) Evidence and methods alignment means that GCRI Canada shall structure evidence and methods so they can support GRF recognition processes, GRA finance-readiness processes, Protocol Authority technical validity processes, public authority learning, Nexus Observatory interpretation, Nexus Grid maturity discipline, Nexus Rails routing, and Nexus Academy literacy without collapsing those distinct roles.
5.1.4(g) Standards-support and interoperability alignment mean that GCRI Canada may develop schemas, APIs, reference architectures, technical baselines, conformance-supporting tools, and public-good software that assist interoperability and standards work, but such support shall not create protocol authority, certification, procurement specification, provider preference, or external conformance effect by default.
5.1.4(h) The controlling rule shall be that public-good stack alignment makes GCRI Canada’s truth function interoperable with Nexus, while preserving institutional separateness and downstream role boundaries.
5.1.5 Public-Good Stack Alignment as Distinct From Enterprise Delivery, Asset Ownership, Capital Formation, Regulated Execution, and Market Operation. 5.1.5(a) Public-good stack alignment shall be distinct from enterprise delivery, asset ownership, capital formation, regulated execution, market operation, provider delivery, procurement implementation, infrastructure operation, project management, financing, revenue generation, underwriting, insurance placement, investment activity, and downstream commercial operations.
5.1.5(b) GCRI Canada’s public-good stack role shall not authorize it to own assets, operate infrastructure, contract for delivery as an execution vehicle, raise capital for projects, market securities, manage Project SPVs, manage National Consortium Companies, select providers, allocate procurement opportunities, guarantee performance, underwrite risk, insure projects, provide ratings, broker transactions, or operate market infrastructure by default.
5.1.5(c) Enterprise-stack actors, including National Consortium Companies, Project SPVs, qualified providers, operators, contractors, delivery entities, financiers, insurers, lenders, underwriters, market actors, and other lawful execution bodies, shall remain responsible for their own enterprise activity, contracts, assets, revenues, liabilities, personnel, compliance, procurement, financing, delivery, operations, and corrections.
5.1.5(d) GCRI Canada may support enterprise-stack actors with public-good evidence, methods, technical baselines, public-good software, public-safe reports, diligence gap maps, observability methods, Academy materials, and handoff records, but such support shall not make GCRI Canada the enterprise actor.
5.1.5(e) GCRI Canada shall not permit public-good stack materials to be used as offering materials, investment recommendations, procurement determinations, provider endorsements, certification marks, recognition records, protocol entitlements, public authority approvals, or execution instructions by default.
5.1.5(f) Where enterprise-stack use of GCRI Canada materials is permitted, the record shall preserve non-execution, no-investment-advice, no-procurement, no-certification, no-recognition, no-protocol-effect, provider-neutrality, sponsor-non-control, public authority boundary, data, cybersecurity, public-safe release, and correction controls.
5.1.5(g) Where public-good stack alignment is misused to imply enterprise control, asset ownership, capital formation, regulated execution, market operation, or provider delivery by GCRI Canada, GCRI Canada shall correct, restrict, withdraw, notify affected actors where appropriate, and preserve correction records.
5.1.5(h) The controlling rule shall be that GCRI Canada supports the conditions for better downstream action, but it does not become the downstream enterprise actor.
5.1.6 GCRI Canada’s Place in the Public-Good Stack as Evidence, Methods, Observability, Ontology, Technical Truth, Public-Good R&D, Public-Good Software, Open Technical Baseline, Nexus Truth Engine Methods, and Nexus Observatory Methods Steward. 5.1.6(a) GCRI Canada’s place in the Nexus public-good stack shall be as steward of evidence, methods, observability, ontology, technical truth, public-good research and development, public-good software, open technical baselines, Nexus Truth Engine methods, Nexus Observatory methods, public authority learning, public-safe publication, and correctionability.
5.1.6(b) Evidence stewardship includes the creation, receipt, structuring, source-lining, classification, review, limitation, challenge, correction, supersession, withdrawal, archival, and handoff of evidence records relevant to systemic risks, resilience, exponential technologies, public authority learning, technical baselines, public-good software, observability, and Nexus public-good functions.
5.1.6(c) Methods stewardship includes the development, documentation, versioning, review, publication, limitation, challenge, correction, and retirement of scientific-operational methods, evidence methods, observability methods, benchmarking methods, public-safe publication methods, data governance methods, AI governance methods, cyber methods, and Nexus Truth Engine methods.
5.1.6(d) Observability stewardship includes methods for interpreting nodes, hubs, clusters, hotspots, national dense cores, regional clusters, sensors, AI-RAN, O-RAN, DePIN, digital twins, dashboards, maps, public-safe evidence outputs, degraded-mode awareness, resilience indicators, system signals, and correction triggers without converting observability into official warning or emergency command.
5.1.6(e) Ontology stewardship includes controlled vocabulary, taxonomies, schemas, semantic mappings, data dictionaries, risk categories, maturity concepts, evidence classifications, public-safe labels, confidence logic, and interoperability rules necessary for records-valid meaning across the Nexus public-good stack.
5.1.6(f) Technical truth stewardship includes maintaining evidence before assertion, record before effect, source-lineage discipline, confidence awareness, limitation awareness, public-safe status, human review where material, AI-use controls, verifiable compute methods, verifiable intelligence records, correctionability, and public trust.
5.1.6(g) Public-good software and open technical baseline stewardship includes developing, maintaining, securing, licensing, documenting, versioning, correcting, and releasing reusable assets that support public-good interoperability without creating vendor preference, certification, protocol effect, procurement advantage, sponsor control, or execution obligation by default.
5.1.6(h) The controlling rule shall be that GCRI Canada’s Nexus role is upstream technical stewardship, not downstream authority.
5.1.7 GCRI Canada’s Alignment With the Nexus Constitutional Framework, Public-Good Stack Framework, Validity-by-Record Doctrine, Correctionability Doctrine, Non-Execution Doctrine, One Rail / Two Stacks Doctrine, and Verifiable Compute / Verifiable Intelligence Doctrine. 5.1.7(a) GCRI Canada shall align its Nexus-facing work with the Nexus Constitutional Framework, the Public-Good Stack Framework, the Validity-by-Record Doctrine, the Correctionability Doctrine, the Non-Execution Doctrine, the One Rail / Two Stacks Doctrine, and the Verifiable Compute / Verifiable Intelligence Doctrine, subject always to applicable Canadian law, the articles, the Bylaw, and this Charter.
5.1.7(b) Alignment with the Nexus Constitutional Framework shall require GCRI Canada to preserve public-good purpose, role separation, records-validity, correctionability, legal separateness, public-safe publication, anti-capture, anti-enclosure, anti-drift, public authority boundaries, finance boundaries, and institutional trust.
5.1.7(c) Alignment with the Public-Good Stack Framework shall require GCRI Canada to remain in the public-good stack as a steward of evidence and technical truth, while preserving the distinction between public-good infrastructure and enterprise-stack execution.
5.1.7(d) Alignment with the Validity-by-Record Doctrine shall require GCRI Canada to treat institutional validity as dependent on proper record, authority, version, source, review, scope, classification, limitation, handoff, correction path, and competent actor, not informal assertion, status, proximity, title, technical display, or public repetition.
5.1.7(e) Alignment with the Correctionability Doctrine shall require GCRI Canada to ensure that evidence, methods, publications, dashboards, maps, datasets, software, technical baselines, AI outputs, proof receipts, and public claims remain challengeable, reviewable, correctable, supersedable, withdrawable, and capable of public-safe clarification.
5.1.7(f) Alignment with the Non-Execution Doctrine shall require GCRI Canada to prevent drift into execution, public authority substitution, finance activity, procurement, certification, recognition, protocol authority, professional regulated opinion, emergency command, official public warning, provider preference, sponsor control, market operation, or infrastructure operation.
5.1.7(g) Alignment with the One Rail / Two Stacks Doctrine shall require GCRI Canada to support a common public-good rail while preserving the distinction between the public-good stack and the enterprise stack, including the distinction between evidence and execution, recognition and adoption, finance-readiness and finance execution, protocol effect and implementation, public authority learning and public authority decision, and support and control.
5.1.7(h) Alignment with the Verifiable Compute / Verifiable Intelligence Doctrine shall require GCRI Canada to support verifiable compute methods, model governance, dataset governance, model cards, system cards, benchmark cards, inference records, compute workload records, source-lineage controls, proof inputs, and human review where material, without treating technical verification artifacts as authority by default.
5.1.8 Public-Good Stack Alignment as a Constraint on Funding, Sponsorship, Provider Participation, Public Authority Participation, Publications, Programs, Data, AI, Cybersecurity, and Technical Architecture. 5.1.8(a) Public-good stack alignment shall constrain funding, sponsorship, donor support, provider participation, public authority participation, publications, programs, data, AI, cybersecurity, technical architecture, dashboards, maps, datasets, software releases, technical baselines, repositories, events, labs, pilots, validation sprints, Academy materials, and Nexus coordination.
5.1.8(b) Funding and sponsorship shall be accepted, structured, acknowledged, restricted, reported, and corrected only in a manner consistent with mission lock, public-benefit purpose, non-execution, public-good asset independence, provider neutrality, sponsor non-control, anti-capture, anti-enclosure, publication independence, data protection, cybersecurity, and correctionability.
5.1.8(c) Provider participation shall be structured to prevent preferred status, procurement advantage, certification implication, recognition implication, finance-readiness implication, protocol implication, public authority approval implication, market allocation, vendor lock-in, technical chokepoints, and hidden control surfaces.
5.1.8(d) Public authority participation shall be capacity-classified and shall not create endorsement, adoption, delegation, public-private partnership, public finance approval, procurement approval, regulatory approval, official guidance, public warning, emergency command, sovereign obligation, or public authority decision by default.
5.1.8(e) Publications and programs shall use controlled vocabulary, stage truth, boundary language, public-safe classification, disclaimers, source labels, limitation statements, role separation, public claims review, correction paths, and public-safe release controls.
5.1.8(f) Data, AI, and cybersecurity systems shall be designed to preserve lawful basis, permitted use, privacy, rights-bearing data protection, sovereign data, public authority data controls, protected knowledge safeguards, AI-use limits, model governance, secure collaboration, incident response, access logs where appropriate, and correctionability.
5.1.8(g) Technical architecture shall preserve openness where appropriate, control where required, portability, interoperability, substitutability, anti-enclosure, anti-lock-in, dependency review, secure release, versioning, public-good licensing, repository discipline, and boundary-safe interfaces.
5.1.8(h) The controlling rule shall be that public-good stack alignment is a design constraint across the institution, not merely an aspirational affiliation.
5.1.9 Public-Good Stack Alignment as an Anti-Capture, Anti-Enclosure, Anti-Drift, and Anti-Substitution Rule. 5.1.9(a) Public-good stack alignment shall operate as an anti-capture, anti-enclosure, anti-drift, and anti-substitution rule.
5.1.9(b) As an anti-capture rule, public-good stack alignment shall prevent sponsors, donors, funders, providers, vendors, hosts, public authorities, capital readers, universities, media actors, National Consortium Companies, Project SPVs, Nexus actors, or influential individuals from controlling GCRI Canada’s evidence, methods, ontology, observability, public-good software, technical baselines, publications, corrections, public authority access, provider participation, Docket inputs, Grid inputs, or institutional meaning.
5.1.9(c) As an anti-enclosure rule, public-good stack alignment shall prevent public-good assets, core semantics, canonical methods, evidence logic, technical baselines, public-good software, schemas, APIs, reference architectures, observability methods, and technical truth infrastructure from being converted into private constitutional inventory, exclusive vendor control, sponsor-controlled assets, hidden dependencies, or proprietary chokepoints.
5.1.9(d) As an anti-drift rule, public-good stack alignment shall prevent GCRI Canada from moving by practice, funding, emergency pressure, public visibility, technical centrality, partner expectation, program naming, event success, sponsor narrative, provider demand, or media framing into execution, finance, procurement, certification, recognition, protocol authority, public authority substitution, professional regulated advice, market operation, or infrastructure operation.
5.1.9(e) As an anti-substitution rule, public-good stack alignment shall prevent GCRI Canada from substituting for GRF, GRA, Protocol Authority, public authorities, National Consortium Companies, Project SPVs, qualified providers, licensed professionals, procurement actors, finance actors, insurers, underwriters, rating bodies, regulators, or execution actors.
5.1.9(f) Where capture, enclosure, drift, or substitution risk arises, GCRI Canada shall apply conflict review, perimeter review, hold, stop-the-line, quarantine, re-scoping, reclassification, boundary-safe handoff, correction, withdrawal, termination, public-safe clarification, legal review, Board review, or other corrective action as appropriate.
5.1.9(g) Repeated capture, enclosure, drift, or substitution patterns shall trigger policy review, training updates, agreement revisions, technical architecture review, sponsor term revision, provider term revision, public authority protocol revision, repository control review, dashboard label review, and Board reporting.
5.1.9(h) The controlling rule shall be that Nexus alignment must protect the public-good stack from being captured, enclosed, diluted, or substituted by any actor or convenience.
5.1.10 Public-Good Stack Alignment Review for Major Programs, Public Materials, Interface Agreements, Technical Releases, and Nexus Coordination Instruments. 5.1.10(a) GCRI Canada shall conduct public-good stack alignment review for major programs, public materials, interface agreements, technical releases, public-good software releases, dashboards, maps, datasets, technical baselines, repository releases, public authority interfaces, GRA interfaces, GRF interfaces, Protocol Authority interfaces, sponsor arrangements, provider arrangements, Nexus Universe activities, Nexus Observatory activities, Nexus Academy materials, and Nexus coordination instruments.
5.1.10(b) Public-good stack alignment review shall determine whether the activity or instrument preserves GCRI Canada’s public-benefit purpose, non-execution, legal separateness, role separation, evidence integrity, methods integrity, observability discipline, ontology discipline, technical truth function, public-good software integrity, open technical baseline integrity, public authority boundaries, finance boundaries, provider neutrality, sponsor non-control, public-safe publication, validity-by-record, correctionability, anti-capture, anti-enclosure, anti-drift, and anti-substitution.
5.1.10(c) Review shall identify whether the activity affects GRF recognition functions, GRA finance-readiness functions, Protocol Authority protocol functions, public authority decisions, Nexus Network rails, Nexus Universe activities, Nexus Observatory methods, Nexus Grid maturity discipline, Nexus Rails routing, Nexus Academy learning, National Consortium Companies, Project SPVs, qualified providers, sponsors, hosts, public authorities, universities, communities, or capital readers.
5.1.10(d) Review shall identify whether the activity could be misread as corporate merger, agency, partnership, joint venture, shared treasury, shared liability, public authority delegation, public-private partnership, procurement pathway, finance pathway, certification pathway, recognition pathway, protocol pathway, provider endorsement, sponsor control, or execution pathway.
5.1.10(e) Review shall identify required boundary language, disclaimers, capacity classifications, data controls, AI-use controls, cybersecurity controls, public-safe classification, repository labels, dashboard labels, map labels, public claims controls, correction path, handoff records, and re-review triggers.
5.1.10(f) Major interface agreements and Nexus coordination instruments shall identify parties, roles, authority limits, records, source status, data treatment, IP treatment, public-good asset treatment, public claims limits, public authority boundaries, finance boundaries, provider neutrality, sponsor non-control, correction obligations, breach handling, termination, and legal separateness.
5.1.10(g) Where public-good stack alignment review identifies unresolved risk, GCRI Canada shall re-scope, revise, restrict, route, quarantine, obtain legal review, obtain Board or committee review, delay release, refuse the activity, or require correction before proceeding.
5.1.10(h) Public-good stack alignment review records shall preserve activity, instrument, reviewed materials, affected actors, risks, controls, approval authority, required revisions, public-safe classification, release conditions, correction path, closeout, and re-review trigger.
5.1.10(i) No major program, public material, interface agreement, technical release, or Nexus coordination instrument shall be treated as Nexus-compatible merely because it uses Nexus vocabulary, includes Nexus logos, references Nexus bodies, involves public authorities, includes sponsors, includes providers, or supports a public-good goal.
5.1.10(j) The controlling rule shall be that Nexus compatibility requires role-correct, records-valid, public-safe, non-executing, correctionable, anti-capture, anti-enclosure, and legally separate alignment.
5.2 One Rail Doctrine
5.2.1 The Common Rail as Shared Semantic, Evidence, Methods, Records, Ontology, Interoperability, Correction, and Public-Good Technical Substrate. 5.2.1(a) The Common Rail shall be understood as the shared semantic, evidence, methods, records, ontology, interoperability, correction, and public-good technical substrate that allows differentiated Nexus institutions, programs, records, technical systems, public-good assets, public authority learning environments, recognition pathways, finance-readiness pathways, protocol-support pathways, Academy materials, observability systems, and lawful downstream actors to understand one another without collapsing their distinct roles.
5.2.1(b) The Common Rail shall support shared meaning across the Nexus public-good stack by preserving common terms, evidence categories, method references, source-lineage expectations, review-status labels, confidence logic, public-safe classifications, correction paths, version histories, handoff records, technical-baseline references, public-good software references, observability concepts, and interoperability structures.
5.2.1(c) The Common Rail shall not be a single corporate entity, execution vehicle, finance vehicle, procurement system, public authority platform, market infrastructure, provider network, certification body, recognition body, or protocol authority by default. It shall be a shared public-good substrate for meaning, routing, records, and correction.
5.2.1(d) GCRI Canada’s relationship to the Common Rail shall be that of an upstream technical truth, evidence, methods, observability, ontology, public-good R&D, public-good software, open technical-baseline, Nexus Truth Engine methods, and Nexus Observatory methods steward, acting within Canadian law, its articles, its Bylaw, this Charter, and the non-execution discipline of Part IV.
5.2.1(e) The Common Rail shall enable differentiated records to travel between GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards / Protocol Authority, Nexus Network, Nexus Universe, Nexus Observatory, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, National Consortium Companies, Project SPVs, qualified providers, hosts, sponsors, universities, communities, public authorities, and capital readers without creating merger, agency, shared liability, shared treasury, authority transfer, or execution consequence by implication.
5.2.1(f) The Common Rail shall preserve the distinction between evidence and recognition, evidence and finance-readiness, evidence and protocol effect, evidence and public authority decision, evidence and procurement, evidence and certification, evidence and professional opinion, evidence and execution, and evidence and market consequence.
5.2.1(g) Where the Common Rail is referenced in public materials, technical materials, dashboards, repositories, public-safe reports, Academy materials, interface agreements, or Nexus coordination instruments, such reference shall be read as reference to a shared public-good meaning and records substrate, not as an assertion of centralized control or downstream authority.
5.2.1(h) The controlling rule shall be that the Common Rail exists to make public-good meaning interoperable, records-valid, correctionable, and usable across distinct institutions without making those institutions legally or functionally identical.
5.2.2 GCRI Canada’s Contribution to the Common Rail Through Evidence Doctrine, Methods, Observability Logic, Ontologies, Schemas, Technical Baselines, Public-Good Software, and Technical Memory. 5.2.2(a) GCRI Canada may contribute to the Common Rail through evidence doctrine, methods, observability logic, ontologies, controlled vocabulary, taxonomies, schemas, data dictionaries, semantic mappings, technical baselines, reference architectures, APIs, public-good software, test harnesses, evaluation harnesses, benchmark methods, verifiable compute methods, verifiable intelligence records, Nexus Truth Engine methods, Nexus Observatory methods, and technical memory.
5.2.2(b) Evidence-doctrine contributions may include source-lineage rules, evidence classifications, evidence sufficiency concepts, confidence logic, corroboration methods, disputed-evidence handling, limitation statements, provenance rules, custody concepts, public-safe evidence rules, correction triggers, and handoff-ready record structures.
5.2.2(c) Methods contributions may include method libraries, method profiles, method notes, review procedures, benchmarking methods, testing methods, observability methods, public-safe publication methods, AI-governance methods, cyber-governance methods, data-governance methods, ontology-maintenance methods, and correction methods.
5.2.2(d) Observability contributions may include logic for interpreting nodes, hubs, clusters, hotspots, national dense Nexus cores, regional clusters, sensors, AI-RAN, O-RAN, private wireless, DePIN, digital twins, dashboards, maps, degraded-mode signals, resilience indicators, signal uncertainty, public-safe visualization, and non-warning observability outputs.
5.2.2(e) Ontology and schema contributions may include controlled terms, definitions, taxonomies, data dictionaries, semantic mappings, public-safe labels, status labels, role labels, evidence categories, maturity concepts, proof-input categories, model-record categories, dataset-record categories, benchmark-record categories, and system-record categories.
5.2.2(f) Technical-baseline and public-good software contributions may include reference architectures, open technical profiles, conformance-supporting tools, APIs, schemas, data tools, dashboards, repositories, public-good software components, reference implementations, documentation, secure release records, vulnerability records, dependency records, and correction pathways.
5.2.2(g) Technical-memory contributions may include version histories, supersession records, withdrawal records, correction records, method histories, evidence histories, benchmark histories, public-safe publication histories, dashboard histories, software release histories, repository histories, and institutional learning records.
5.2.2(h) GCRI Canada’s contributions to the Common Rail shall remain public-good, records-valid, source-aware, limitation-aware, privacy-preserving, cybersecurity-compatible, sovereignty-compatible, protected-knowledge-aware, non-executing, provider-neutral, sponsor-non-controlled, and correctionable.
5.2.2(i) GCRI Canada’s contribution of any material to the Common Rail shall not by itself create GRF recognition, GRA finance-readiness, Protocol Authority effect, public authority decision, procurement approval, certification, provider endorsement, sponsor approval, professional opinion, public warning, emergency command, asset ownership, or execution consequence.
5.2.2(j) The controlling rule shall be that GCRI Canada may strengthen the Common Rail by stewarding technical truth, but the Common Rail shall not convert that stewardship into downstream authority.
5.2.3 Common Rail as Public-Good Infrastructure, Not GCRI Canada’s Proprietary Asset. 5.2.3(a) The Common Rail shall be treated as public-good infrastructure, not as GCRI Canada’s proprietary asset.
5.2.3(b) GCRI Canada may steward, develop, maintain, contribute to, document, secure, release, version, correct, and improve components of the Common Rail within its lawful role, but such stewardship shall not make the Common Rail the private property, exclusive inventory, commercial product, proprietary platform, or unilateral control surface of GCRI Canada.
5.2.3(c) Common Rail assets may include methods, ontologies, schemas, public-good software, technical baselines, records structures, evidence categories, public-safe labels, correction pathways, dashboards, APIs, reference architectures, and documentation, but their public-good character shall be protected against enclosure, extraction, hidden dependency, sponsor control, provider lock-in, or institutional capture.
5.2.3(d) GCRI Canada shall not pledge, assign, exclusively license, encumber, privatize, enclose, suppress, or convert mission-critical Common Rail assets into private constitutional inventory except through a lawful, mission-consistent, public-benefit-justified, Board-reviewed, records-valid, time-bounded, safety-justified, and correction-compatible arrangement where such exception is expressly permitted.
5.2.3(e) GCRI Canada shall preserve portability, substitutability, interoperability, documentation, open or governed reuse where appropriate, secure access controls where required, and correction pathways for Common Rail assets under its stewardship.
5.2.3(f) Sponsors, donors, funders, providers, hosts, public authorities, universities, capital readers, National Consortium Companies, Project SPVs, or Nexus actors shall not acquire ownership, veto rights, release control, correction control, method control, ontology control, repository control, or technical-baseline control over Common Rail assets by support, participation, hosting, funding, contribution, or public visibility.
5.2.3(g) Where a Common Rail component includes third-party IP, data, software, models, standards, controlled technology, public authority material, community knowledge, Indigenous knowledge, protected knowledge, or licensed material, GCRI Canada shall preserve lawful use, attribution, restrictions, custody, public-safe treatment, and correction pathways without converting the component into unrestricted proprietary control.
5.2.3(h) The controlling rule shall be that GCRI Canada may be a steward of Common Rail components, but stewardship is not ownership of public-good meaning.
5.2.4 Common Rail as Interoperability Architecture, Not Centralized Corporate Control. 5.2.4(a) The Common Rail shall be an interoperability architecture, not centralized corporate control.
5.2.4(b) The purpose of the Common Rail shall be to allow distinct institutions and actors to align evidence, methods, vocabulary, records, public-safe classifications, correction paths, technical baselines, and handoff structures, while preserving separate legal authority, institutional responsibility, local context, public authority competence, finance boundaries, protocol boundaries, enterprise execution boundaries, and correction obligations.
5.2.4(c) Interoperability shall not mean hierarchy. Use of a shared term, schema, method, API, technical baseline, proof input, public-good software component, dashboard convention, record structure, or correction pathway shall not place the user under GCRI Canada’s corporate control or make GCRI Canada responsible for the user’s downstream decisions.
5.2.4(d) The Common Rail shall not create a command chain, approval chain, public authority chain, finance chain, procurement chain, certification chain, recognition chain, protocol chain, provider-selection chain, emergency command chain, public warning chain, professional-opinion chain, or execution chain by default.
5.2.4(e) GCRI Canada shall not use Common Rail stewardship to centralize control over regional or national truth, public authority decisions, community safeguards, Indigenous or local knowledge, public-good software dependencies, provider ecosystems, technical baselines, public-facing legitimacy, finance-readiness, protocol effect, or enterprise execution.
5.2.4(f) The Common Rail shall support localization without fragmentation, federation without centralization, interoperability without uniformity, common vocabulary without erasure of context, public-good assets without private lock-in, and technical truth without institutional domination.
5.2.4(g) Where Common Rail use creates centralization risk, hidden dependency risk, control-surface risk, public authority confusion, provider lock-in, sponsor influence, or local-context erasure, GCRI Canada shall review, re-scope, decentralize, document, open, govern, restrict, or correct the affected rail component.
5.2.4(h) The controlling rule shall be that the Common Rail connects meaning; it does not centralize power.
5.2.5 Common Rail as Records-Valid, Correctionable, Versioned, and Public-Safe. 5.2.5(a) The Common Rail shall be records-valid, correctionable, versioned, and public-safe.
5.2.5(b) Records-validity shall require that Common Rail components identify their source, authority, issuer, steward, version, date, status, scope, intended use, limitations, public-safe classification, data classification where applicable, review status, permitted use, prohibited use, handoff status, correction path, supersession path, and withdrawal path where material.
5.2.5(c) Correctionability shall require that Common Rail components remain challengeable, reviewable, correctable, supersedable, withdrawable, retractable where necessary, and capable of public-safe clarification. No Common Rail component shall become uncorrectable because it is embedded in software, dashboards, APIs, proof receipts, blockchain anchors, public-safe reports, datasets, Academy materials, or Nexus materials.
5.2.5(d) Versioning shall require that Common Rail components preserve version history, change logs, adoption records, review records, release records, dependency records where material, public-safe status changes, supersession status, deprecation status, and archival status.
5.2.5(e) Public-safe treatment shall require that Common Rail components be classified and released in a manner that protects privacy, rights-bearing data, public authority data, sovereign data, Indigenous knowledge, local knowledge, protected knowledge, sensitive infrastructure, cyber-sensitive information, health-sensitive information, controlled technology, sanctions-sensitive information, export-controlled information, and community safeguards.
5.2.5(f) Common Rail components shall distinguish public, public-safe summary, controlled, restricted, confidential, privileged, draft, under review, quarantined, superseded, withdrawn, archived, and not-for-reliance states where material.
5.2.5(g) Where a Common Rail component is reused by GRF, GRA, Protocol Authority, Nexus bodies, public authorities, National Consortium Companies, Project SPVs, providers, universities, sponsors, hosts, communities, or capital readers, the records-valid status, limitations, correction path, and boundary language shall travel with the component where material.
5.2.5(h) The controlling rule shall be that the Common Rail shall carry not only shared meaning, but also shared discipline for records, versioning, correction, and public-safe use.
5.2.6 Common Rail as Distinct From Enterprise Execution Rails, Capital Rails, Public Authority Rails, and Market Infrastructure. 5.2.6(a) The Common Rail shall be distinct from enterprise execution rails, capital rails, public authority rails, regulated payment rails, securities rails, insurance rails, procurement rails, market infrastructure, operational control systems, emergency command systems, public warning systems, and professional services delivery rails.
5.2.6(b) Common Rail interoperability shall not create enterprise execution. Technical baselines, public-good software, schemas, APIs, dashboards, evidence packs, proof inputs, and methods may support downstream enterprise actors, but they shall not make GCRI Canada an owner, operator, manager, contractor, provider, employer, guarantor, insurer, lender, underwriter, project sponsor, or execution actor.
5.2.6(c) Common Rail interoperability shall not create capital activity. Evidence records, diligence gap maps, host-readiness evidence, node evidence, technical baselines, public-safe reports, dashboards, maps, and proof inputs shall not constitute investment advice, securities offerings, capital solicitation, brokerage, lending, insurance, underwriting, rating, public finance approval, finance-readiness, or capital commitment by default.
5.2.6(d) Common Rail interoperability shall not create public authority action. Public authority-facing records, dashboards, maps, public-safe reports, technical baselines, and public authority learning materials shall not create official guidance, public authority decisions, public warnings, emergency commands, regulation, enforcement, procurement approval, funding approval, or sovereign obligation by default.
5.2.6(e) Common Rail interoperability shall not create market infrastructure. APIs, proof receipts, blockchain anchors, tokens, smart contracts, data feeds, registries, dashboards, and confidence scores shall not become clearing, settlement, payment, trading, rating, insurance, underwriting, procurement, public finance, certification, recognition, or protocol-effect systems by default.
5.2.6(f) Where Common Rail components are used in enterprise, capital, public authority, procurement, professional, or market contexts, boundary language, handoff records, competent actor responsibility, public-safe classification, and correction pathways shall preserve GCRI Canada’s non-executing role.
5.2.6(g) Where Common Rail components are at risk of being repurposed as enterprise execution rails, capital rails, public authority rails, procurement rails, or market infrastructure, GCRI Canada shall restrict, relabel, re-scope, route, quarantine, correct, withdraw, or seek legal and Board review where material.
5.2.6(h) The controlling rule shall be that the Common Rail supports interoperable public-good meaning, not regulated execution or market operation.
5.2.7 Common Rail as Support for Differentiated Institutions Without Making Them Identical. 5.2.7(a) The Common Rail shall support differentiated institutions without making them identical.
5.2.7(b) GCRI Canada, GRF, GRA, Protocol Authority, Nexus Network, Nexus Universe, Nexus Observatory, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, National Consortium Companies, Project SPVs, qualified providers, hosts, sponsors, public authorities, universities, communities, capital readers, and other actors may use shared rail concepts, records, evidence structures, method references, schemas, APIs, dashboards, public-safe labels, and correction pathways while retaining distinct legal status, mission, authority, accountability, jurisdiction, and liability.
5.2.7(c) Shared vocabulary shall not erase functional distinction. A term used by GCRI Canada as evidence support may be used by GRF in recognition, by GRA in finance-readiness, by Protocol Authority in protocol discipline, by public authorities in public decisions, or by enterprise actors in execution only through the relevant actor’s own authority and record.
5.2.7(d) Shared evidence shall not create shared decision. A single evidence record may inform multiple actors, but each actor shall determine its own permitted use, authority, review, reliance, output, correction, and downstream effect.
5.2.7(e) Shared methods shall not create shared liability. Method alignment shall support comparability and interoperability, but shall not make GCRI Canada responsible for another actor’s adoption, implementation, modification, misuse, overclaim, public communication, or execution.
5.2.7(f) Shared technical baselines shall not create common control. Technical alignment shall support portability and public-good quality, but shall not merge governance, treasury, obligations, public authority status, finance role, procurement role, certification role, recognition role, protocol authority, provider status, or execution status.
5.2.7(g) Where differentiated institutional roles become blurred by shared rail use, GCRI Canada shall clarify the actor, role, authority, record, limitation, public-safe status, and correction path.
5.2.7(h) The controlling rule shall be that the Common Rail is common because it is interoperable, not because all actors become one actor.
5.2.8 Common Rail as Anti-Fragmentation Infrastructure. 5.2.8(a) The Common Rail shall operate as anti-fragmentation infrastructure for public-good meaning, evidence, methods, observability, ontology, technical baselines, public-good software, public-safe publication, correction, and institutional memory.
5.2.8(b) Anti-fragmentation infrastructure shall reduce unnecessary divergence in terminology, evidence categories, method references, record structures, source-lineage practices, dashboard labels, map legends, public-safe classifications, proof-input structures, dataset records, model records, benchmark records, system records, inference records, technical-baseline labels, and correction practices.
5.2.8(c) The purpose of anti-fragmentation shall be to make legitimate local, regional, national, sectoral, disciplinary, and technical variation interoperable, not to erase lawful local truth, sovereignty, public authority context, Indigenous and local knowledge, community safeguards, legal constraints, language differences, or domain-specific method differences.
5.2.8(d) GCRI Canada may support anti-fragmentation by maintaining controlled vocabularies, semantic mappings, method libraries, reference architectures, public-good software, technical baselines, evidence templates, public-safe publication templates, repository structures, and correction protocols that allow multiple actors to align without central domination.
5.2.8(e) Anti-fragmentation shall not be used as a reason to impose a single institutional view where evidence is disputed, local context differs, public authority mandates differ, legal systems differ, community safeguards require localization, or protected knowledge requires restricted treatment.
5.2.8(f) Where competing terms, methods, records, baselines, or public-good software components arise, GCRI Canada may support comparison, mapping, reconciliation, versioning, confidence treatment, and correction rather than suppressing variation by authority.
5.2.8(g) Where fragmentation creates public risk, public authority confusion, finance confusion, provider lock-in, sponsor capture, technical incompatibility, data misuse, public-safe publication risk, or correction failure, GCRI Canada shall support harmonization, mapping, reclassification, correction, or public-safe clarification within its role.
5.2.8(h) The controlling rule shall be that the Common Rail prevents harmful fragmentation while preserving lawful and meaningful pluralism.
5.2.9 Common Rail as Anti-Fork Discipline for Core Semantics, Evidence Categories, Technical Baselines, and Public-Good Records. 5.2.9(a) The Common Rail shall operate as anti-fork discipline for core semantics, evidence categories, technical baselines, public-good records, public-safe labels, correction pathways, and other mission-critical public-good meaning structures.
5.2.9(b) Anti-fork discipline shall not prohibit lawful experimentation, localization, translation, domain adaptation, research variation, controlled pilots, technical testing, or public-good innovation. It shall require that material divergences from core semantics, evidence categories, technical baselines, or records structures be recorded, labeled, justified, versioned, mapped, and correctionable.
5.2.9(c) A fork becomes boundary-relevant where it creates confusion about evidence meaning, recognition status, finance-readiness, certification, protocol effect, public authority meaning, procurement status, provider status, sponsor influence, public-safe classification, correction path, or institutional authority.
5.2.9(d) GCRI Canada shall discourage unrecorded, silent, sponsor-driven, provider-driven, finance-driven, public authority-confusing, procurement-driven, certification-implying, recognition-implying, protocol-implying, or market-driven forks of core Common Rail semantics and technical baselines.
5.2.9(e) Where forks are necessary for jurisdictional, linguistic, domain, public authority, Indigenous, community, data, cybersecurity, controlled technology, or public-safe reasons, such forks shall be documented with scope, rationale, authority, steward, version, relationship to the common baseline, limitations, public-safe status, and correction path.
5.2.9(f) GCRI Canada may maintain mappings among forks, variants, translations, localized profiles, regional profiles, national profiles, technical profiles, controlled annexes, and public-safe summaries to preserve interoperability without forcing false uniformity.
5.2.9(g) Where a fork is used to create provider lock-in, sponsor control, public authority confusion, finance overclaim, certification overclaim, recognition overclaim, protocol overclaim, procurement advantage, or public-good asset enclosure, GCRI Canada shall correct, reclassify, withdraw support, restrict use, notify affected actors where appropriate, or escalate for Board or legal review.
5.2.9(h) The controlling rule shall be that variation is permitted when recorded and bounded; silent divergence of core public-good meaning is not.
5.2.10 Common Rail Governance Requires Clear Ownership, Custody, Access, Versioning, Correction, Public-Safe Publication, and Interface Records. 5.2.10(a) Governance of Common Rail components under GCRI Canada stewardship shall require clear ownership, stewardship, custody, access, versioning, correction, public-safe publication, release, interface, and handoff records.
5.2.10(b) Ownership records shall identify legal ownership, public-good stewardship, licensing status, third-party rights, contribution rights, contributor obligations, sponsor restrictions, provider restrictions, public authority restrictions, Indigenous or local knowledge restrictions, protected knowledge restrictions, and anti-enclosure controls.
5.2.10(c) Custody records shall identify where the component is held, who maintains it, who may access it, who may modify it, who may approve release, who may correct it, who may withdraw it, and who is responsible for preserving records.
5.2.10(d) Access records shall identify users, roles, permissions, access conditions, confidentiality obligations, data restrictions, AI-use limits, cybersecurity requirements, public authority restrictions, finance restrictions, provider restrictions, sponsor restrictions, onward-sharing limits, and access logs where appropriate and lawful.
5.2.10(e) Versioning records shall identify version number or equivalent identifier, release date, steward, changes, dependency changes where material, superseded materials, compatibility status, public-safe status, security status where material, deprecation status, archival status, and re-review trigger.
5.2.10(f) Correction records shall identify error, ambiguity, dispute, limitation, affected materials, affected users, correction authority, correction action, supersession, withdrawal, retraction where applicable, public-safe clarification, notice decision, and closeout.
5.2.10(g) Public-safe publication records shall identify whether the component may be public, public-safe summary, controlled, restricted, confidential, privileged, draft, under review, quarantined, superseded, withdrawn, archived, or not for reliance, and shall preserve required boundary language.
5.2.10(h) Interface records shall identify how the Common Rail component interacts with GRF, GRA, Protocol Authority, Nexus bodies, public authorities, National Consortium Companies, Project SPVs, providers, hosts, sponsors, universities, communities, capital readers, or other actors, including permitted use, prohibited use, competent authority, handoff limits, data treatment, IP treatment, public claims limits, and correction obligations.
5.2.10(i) Where ownership, custody, access, versioning, correction, public-safe publication, or interface records are absent, stale, contradictory, incomplete, or unsafe, GCRI Canada shall hold, restrict, reclassify, correct, quarantine, delay release, or refuse use of the relevant Common Rail component until the record is adequate.
5.2.10(j) The controlling rule shall be that the Common Rail shall be governed through records-valid stewardship, not informal possession, technical control, institutional reputation, sponsor support, provider contribution, or public visibility.
5.3 Two Stacks Doctrine
5.3.1 Public-Good Stack and Enterprise Stack as Separate but Interoperable Systems. 5.3.1(a) The Nexus architecture shall be understood as operating through two separate but interoperable systems: the public-good stack and the enterprise stack. The public-good stack shall steward public-benefit evidence, methods, observability, ontology, public-good technical baselines, public-good software, public-safe reporting, recognition-support inputs, finance-readiness translation inputs, protocol-support inputs, correctable records, public authority learning, and institutional legitimacy functions. The enterprise stack shall conduct lawful downstream execution, asset ownership, commercial delivery, project contracting, financing, operations, revenue activity, provider delivery, and market-facing implementation through separate competent actors.
5.3.1(b) Separation of the two stacks shall be a constitutional safeguard. It shall preserve GCRI Canada’s upstream technical truth role while allowing downstream actors to use properly bounded evidence, methods, technical baselines, public-safe outputs, and handoff records in their own lawful processes.
5.3.1(c) Interoperability between the public-good stack and the enterprise stack shall not be interpreted as merger, agency, shared liability, shared treasury, joint venture, public-private partnership, public authority delegation, finance intermediation, procurement relationship, provider endorsement, professional engagement, or execution relationship by default.
5.3.1(d) The two stacks may share vocabulary, records, evidence inputs, technical baselines, public-good software, observability methods, proof inputs, correction records, Academy materials, and interface instruments, but each stack shall retain its own authority, responsibility, risk, liability, governance, and correction duties.
5.3.1(e) The public-good stack shall not become the enterprise stack because its records are useful to projects, providers, capital readers, insurers, public authorities, National Consortium Companies, Project SPVs, or market actors. The enterprise stack shall not become the public-good stack because it implements, finances, operates, hosts, or commercializes work informed by public-good materials.
5.3.1(f) Where an activity crosses from public-good support into enterprise execution, GCRI Canada shall identify the crossing, apply boundary review, record the interface, restrict public claims, preserve non-execution, and route responsibility to the competent enterprise-stack actor.
5.3.1(g) Where ambiguity exists, the interpretation preserving stack separation, public-good integrity, legal separateness, non-execution, provider neutrality, sponsor non-control, finance-boundary discipline, procurement neutrality, public-safe publication, and correctionability shall prevail.
5.3.1(h) The controlling rule shall be that the public-good stack and enterprise stack shall interoperate by record, not merge by proximity.
5.3.2 GCRI Canada’s Position in the Public-Good Stack. 5.3.2(a) GCRI Canada shall be positioned within the public-good stack as a Canadian public-benefit, nonprofit, non-share, non-distributing, non-executing steward of upstream technical truth, evidence, methods, observability, ontology, public-good research and development, public-good software, open technical baselines, Nexus Truth Engine methods, Nexus Observatory methods, public authority learning, public-safe publication, and correctionability.
5.3.2(b) GCRI Canada’s public-good stack position shall not include enterprise execution, project ownership, asset ownership, provider delivery, procurement, capital formation, regulated finance, insurance placement, underwriting, rating, market operation, public authority action, certification by default, recognition by default, protocol authority by default, infrastructure operation, field deployment, commercial sales, or downstream management.
5.3.2(c) GCRI Canada may produce or steward evidence records, method records, observability records, ontology records, technical baseline records, public-good software records, model records, dataset records, benchmark records, system records, inference records, proof-input records, public-safe reports, controlled annexes, Academy materials, correction records, and handoff records that support the wider Nexus architecture.
5.3.2(d) GCRI Canada may provide inputs to The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards / Protocol Authority, Nexus Network, Nexus Universe, Nexus Observatory, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, National Consortium Companies, Project SPVs, qualified providers, public authorities, universities, sponsors, hosts, communities, and capital readers, provided that each input remains properly scoped, records-valid, public-safe where required, and non-executing.
5.3.2(e) GCRI Canada shall not claim to be the execution arm, commercial arm, investment arm, procurement arm, public authority arm, certification arm, recognition arm, protocol arm, operating arm, or delivery arm of the Nexus architecture.
5.3.2(f) GCRI Canada’s outputs shall be described as public-good evidence, methods, observability, ontology, technical baselines, software, learning, public-safe publication, and correction outputs unless a competent external actor separately creates downstream effect through its own process and record.
5.3.2(g) GCRI Canada shall preserve its public-good stack position in all contracts, interface agreements, public materials, technical releases, program charters, public authority engagements, sponsor arrangements, provider engagements, GRA interfaces, GRF interfaces, Protocol Authority interfaces, and Nexus coordination instruments.
5.3.2(h) The controlling rule shall be that GCRI Canada belongs upstream in the public-good stack and shall not be converted into an enterprise-stack actor by usefulness, demand, funding, visibility, technical centrality, or Nexus proximity.
5.3.3 Enterprise Stack as the Home of National Consortium Companies, Project SPVs, Qualified Providers, Licensed Actors, Market Actors, Asset Owners, Operators, and Commercial Delivery. 5.3.3(a) The enterprise stack shall be the home of National Consortium Companies, Project SPVs, qualified providers, licensed actors, market actors, asset owners, operators, contractors, systems integrators, managed service providers, infrastructure operators, insurers, lenders, underwriters, financiers, commercial delivery bodies, and other lawful downstream execution actors.
5.3.3(b) Enterprise-stack actors shall be responsible for enterprise functions, including asset ownership, project contracting, procurement participation, financing, revenue generation, customer contracting, infrastructure delivery, technology deployment, field operations, managed services, lifecycle operations, employment, subcontracting, warranties, insurance procurement, compliance, taxation, accounting, risk allocation, incident response, operational safety, and commercial performance.
5.3.3(c) National Consortium Companies may serve as separate investible and enterprise-stack platforms where lawfully formed, governed, capitalized, and authorized. Project SPVs may serve as separate asset-level execution vehicles where lawfully formed, governed, capitalized, contracted, and authorized. Neither shall be treated as GCRI Canada by reason of Nexus alignment or use of GCRI Canada evidence.
5.3.3(d) Qualified providers may deliver technology, integration, managed services, deployment, field support, lifecycle operations, software implementation, telecommunications services, AI-RAN or O-RAN services, DePIN services, cybersecurity services, cloud services, data services, dashboard services, sensing services, or other delivery functions under their own contracts, liabilities, licenses, and professional or regulatory obligations.
5.3.3(e) Licensed actors and regulated professionals shall perform legal, engineering, clinical, accounting, audit, actuarial, insurance, investment, rating, cybersecurity assurance, environmental assurance, safety assurance, public authority, financial, or other regulated work through their own lawful mandates and professional responsibilities.
5.3.3(f) GCRI Canada shall not assume enterprise-stack liabilities, obligations, warranties, delivery duties, operational duties, financing duties, procurement duties, public authority obligations, professional duties, or commercial duties merely because its evidence, methods, technical baselines, public-good software, public-safe reports, or Academy materials support enterprise-stack readiness.
5.3.3(g) Where enterprise-stack actors use GCRI Canada materials, such use shall preserve non-execution, no-investment-advice, no-procurement, no-certification, no-recognition, no-protocol-effect, provider-neutrality, sponsor-non-control, public authority boundary, data, cybersecurity, public-safe release, and correction controls.
5.3.3(h) The controlling rule shall be that execution belongs to competent enterprise-stack actors, not to GCRI Canada.
5.3.4 Public-Good Stack as the Home of Evidence, Methods, Public-Good Technical Baselines, Recognition, Claims Discipline, Finance-Readiness Translation, Protocol Discipline, Public-Safe Reporting, and Correctable Records. 5.3.4(a) The public-good stack shall be the home of evidence, methods, public-good technical baselines, public-good software, ontology, observability logic, recognition-related legitimacy functions, claims discipline, finance-readiness translation, protocol discipline, public-safe reporting, public authority learning, Academy learning, maturity discipline, routeability logic, proof inputs, correctable records, and public-good institutional memory.
5.3.4(b) Within the public-good stack, GCRI Canada shall steward upstream technical truth, evidence, methods, observability, ontology, technical baselines, public-good R&D, public-good software, Nexus Truth Engine methods, Nexus Observatory methods, public authority learning, public-safe publication, and correctionability.
5.3.4(c) Within the public-good stack, The Global Risks Forum (GRF) shall remain distinct as the steward of public-facing legitimacy, registry, recognition, standing, maturity records, claims discipline, stakeholder formation, and public-safe reporting functions.
5.3.4(d) Within the public-good stack, The Global Risks Alliance (GRA) shall remain distinct as the steward of finance-readiness, capital readability, proof packs, insurance-readiness, capital-reader rooms, RNFD, NFD, UNFSD, and regulated-perimeter discipline.
5.3.4(e) Within the public-good stack, Nexus Standards / Protocol Authority shall remain distinct as the steward of protocol discipline, conformance logic, role keys, smart licenses, proof receipts, entitlement states, anchoring discipline, and technical validity surfaces.
5.3.4(f) Public-good stack records may support enterprise-stack action, but they shall not become enterprise action. Evidence shall not become adoption by default. Recognition inputs shall not become recognition by default. Finance-readiness inputs shall not become finance-readiness by default. Technical baselines shall not become certification by default. Proof inputs shall not become protocol effect by default. Public-safe reports shall not become public authority decisions by default.
5.3.4(g) Public-good stack outputs shall be recorded, versioned, source-lined, limitation-aware, public-safe where required, boundary-labeled, challengeable, correctable, supersedable, withdrawable, and capable of handoff to competent actors.
5.3.4(h) The controlling rule shall be that the public-good stack creates disciplined public-good meaning and records, not downstream execution by itself.
5.3.5 Public-Good Stack Does Not Execute Enterprise Stack Functions. 5.3.5(a) The public-good stack shall not execute enterprise-stack functions. GCRI Canada, in its public-good stack capacity, shall not own assets, operate projects, manage Project SPVs, control National Consortium Companies, direct providers, contract as an execution vehicle, raise capital for projects, sell securities, broker transactions, lend, insure, underwrite, rate, guarantee, collect project revenue, manage field deployment, operate infrastructure, or perform commercial delivery by default.
5.3.5(b) Public-good stack functions may include research, evidence structuring, methods development, observability methods, ontology, public-good software, technical baselines, public-safe publication, Academy learning, public authority learning, GRF inputs, GRA inputs, Protocol Authority inputs, Nexus Observatory methods, Nexus Grid inputs, Nexus Rails routing support, correction records, and boundary-safe handoffs.
5.3.5(c) A public-good stack output shall not become an enterprise-stack instruction merely because it identifies evidence gaps, technical readiness, method limitations, host-readiness factors, node evidence, resilience indicators, public-safe constraints, data controls, cyber controls, or implementation considerations.
5.3.5(d) A public-good stack handoff shall not make GCRI Canada responsible for enterprise-stack decisions made by National Consortium Companies, Project SPVs, qualified providers, public authorities, finance actors, insurers, underwriters, operators, contractors, or licensed professionals.
5.3.5(e) Public-good stack actors shall not accept transaction-based compensation, execution-based fees, procurement-award incentives, capital-closing incentives, insurance-placement incentives, underwriting incentives, rating outcome incentives, or other compensation that would convert public-good support into enterprise-stack execution.
5.3.5(f) Public-good stack interfaces with enterprise actors shall include non-execution language, scope limits, public claims restrictions, data restrictions, IP treatment, correction obligations, and downstream actor responsibility.
5.3.5(g) Where public-good stack activity begins to function as enterprise execution, GCRI Canada shall hold, stop, quarantine, re-scope, reclassify, hand off, correct, withdraw, or refuse the activity.
5.3.5(h) The controlling rule shall be that public-good support may enable better execution by others, but it shall not itself execute.
5.3.6 Enterprise Stack Does Not Own, Control, Mutate, Enclose, Purchase, or Override Public-Good Stack Truth. 5.3.6(a) The enterprise stack shall not own, control, mutate, enclose, purchase, suppress, distort, inflate, override, or privately capture public-good stack truth.
5.3.6(b) National Consortium Companies, Project SPVs, qualified providers, vendors, contractors, operators, asset owners, insurers, lenders, underwriters, investors, sponsors, hosts, public authorities, universities, capital readers, market actors, and other enterprise or downstream participants shall not acquire control over GCRI Canada evidence, methods, observability logic, ontology, public-good software, technical baselines, public-safe publications, correction records, Docket inputs, Grid inputs, proof inputs, or institutional meaning by support, implementation, funding, contracting, data contribution, technical contribution, or market relevance.
5.3.6(c) Enterprise actors shall not require GCRI Canada to alter evidence, suppress unfavorable findings, delay correction, select methods to favour a project, include or exclude data for commercial advantage, design baselines for vendor lock-in, publish favourable language, create finance-signaling statements, imply public authority approval, or transform public-good outputs into market endorsements.
5.3.6(d) Enterprise actors shall not use GCRI Canada materials in a manner that removes limitations, omits disclaimers, overstates maturity, implies certification, implies recognition, implies finance-readiness, implies procurement advantage, implies provider preference, implies public authority endorsement, implies protocol effect, or implies execution authority.
5.3.6(e) Enterprise-stack use of public-good stack records shall preserve source, version, scope, public-safe classification, limitations, public claims limits, boundary language, permitted use, prohibited use, and correction path.
5.3.6(f) Where enterprise actors discover error, limitation, changed context, unsafe reliance, or downstream misuse involving GCRI Canada materials, they shall be required, where applicable by agreement or participation terms, to report the issue and cooperate with correction.
5.3.6(g) Where enterprise-stack actors attempt to own, control, mutate, enclose, purchase, or override public-good stack truth, GCRI Canada shall refuse, restrict, correct, withdraw materials, terminate access, terminate agreements, notify affected actors where appropriate, and preserve correction records.
5.3.6(h) The controlling rule shall be that enterprise actors may use public-good truth under proper limits, but they shall not own the truth function.
5.3.7 GCRI Canada’s Evidence and Technical Inputs May Support Enterprise Stack Readiness Without Becoming Enterprise Stack Execution. 5.3.7(a) GCRI Canada’s evidence and technical inputs may support enterprise-stack readiness without becoming enterprise-stack execution.
5.3.7(b) Such inputs may include evidence records, methods records, observability summaries, technical baselines, public-good software documentation, reference architectures, schemas, APIs, dashboards, maps, data tools, test harnesses, evaluation harnesses, benchmark records, host-readiness evidence, node evidence, cyber-control records, AI-governance records, data-governance records, public-safe reports, controlled annexes, diligence gap maps, Academy materials, proof inputs, limitation records, and correction records.
5.3.7(c) Enterprise-stack readiness support may help downstream actors understand evidence gaps, technical requirements, interoperability needs, data responsibilities, AI governance duties, cybersecurity needs, public-safe conditions, documentation gaps, host readiness, node readiness, observability needs, resilience considerations, and correction paths.
5.3.7(d) Enterprise-stack readiness support shall not become certification, recognition, finance-readiness, investment advice, insurance-readiness, underwriting approval, rating, public finance approval, procurement approval, provider endorsement, public authority approval, protocol effect, deployment approval, operational clearance, asset ownership decision, or execution instruction by default.
5.3.7(e) Any reference to readiness in GCRI Canada materials shall be carefully bounded. Readiness may describe evidence readiness, method readiness, documentation readiness, data readiness, public-safe readiness, technical baseline readiness, or handoff readiness only within the defined scope, not financial readiness, procurement readiness, public authority readiness, insurance readiness, certification readiness, or deployment readiness unless a competent external actor has separately created such meaning.
5.3.7(f) Enterprise-stack actors receiving GCRI Canada inputs shall remain responsible for their own due diligence, professional advice, public authority approvals, procurement participation, financing, insurance, underwriting, operational safety, contracts, data handling, cybersecurity, delivery, liabilities, public claims, and corrections.
5.3.7(g) GCRI Canada shall require scope limits, non-reliance language, public claims controls, data restrictions, IP treatment, correction obligations, and downstream actor responsibility where its inputs are used in enterprise-stack readiness contexts.
5.3.7(h) The controlling rule shall be that GCRI Canada may make enterprise action more evidence-literate, but it shall not perform the enterprise action.
5.3.8 Public-Good Firewall Between GCRI Canada and Enterprise Stack Actors. 5.3.8(a) GCRI Canada shall maintain a public-good firewall between itself and enterprise-stack actors.
5.3.8(b) The public-good firewall shall preserve GCRI Canada’s mission lock, non-execution, evidence integrity, methods integrity, publication independence, public-safe release, provider neutrality, sponsor non-control, finance-boundary safety, procurement neutrality, data rights, cybersecurity, public-good asset independence, correctionability, and legal separateness.
5.3.8(c) The firewall shall prevent enterprise-stack actors from controlling GCRI Canada’s Board, officers, programs, councils, methods, evidence selection, data inclusion, benchmark design, public-safe publication, technical baselines, public-good software, repositories, dashboards, correction decisions, public authority access, GRF inputs, GRA inputs, Protocol Authority inputs, or public claims.
5.3.8(d) The firewall shall prevent GCRI Canada from assuming enterprise-stack roles, including owner, operator, manager, financier, guarantor, insurer, underwriter, lender, broker, dealer, finder, placement agent, provider, vendor selector, procurement actor, project sponsor, commercial partner, market operator, or execution vehicle by default.
5.3.8(e) Firewall controls may include role separation, separate agreements, conflict review, recusal, information barriers, data-access limits, public claims limits, provider-neutrality rules, sponsor non-control rules, finance-boundary rules, procurement-boundary rules, publication independence clauses, correction independence clauses, IP controls, repository permission controls, dashboard access controls, and Board review for high-risk interfaces.
5.3.8(f) Where persons serve in multiple capacities across public-good and enterprise-stack actors, GCRI Canada shall require role clarity, conflict disclosure, recusal where appropriate, authority mapping, public claims limits, confidentiality controls, data controls, and correction obligations.
5.3.8(g) Where firewall risk arises, GCRI Canada shall restrict access, revise agreements, separate teams, re-scope activity, quarantine materials, correct public claims, suspend participation, terminate relationships, or escalate to Board and legal review.
5.3.8(h) The controlling rule shall be that the public-good firewall allows constructive interface with enterprise execution while preventing capture, confusion, and role collapse.
5.3.9 Interface Instruments Required Where GCRI Canada Supports Enterprise Stack Actors. 5.3.9(a) Where GCRI Canada materially supports enterprise-stack actors, the relationship shall be governed by an interface instrument or equivalent records-valid arrangement proportionate to risk.
5.3.9(b) Interface instruments may include MoUs, cooperation agreements, data agreements, IP agreements, technical-baseline agreements, public-good software licenses, public authority protocols, GRA interface records, GRF interface records, Protocol Authority interface records, Project SPV interface records, National Consortium Company interface records, provider participation terms, sponsor terms, host terms, Academy terms, dashboard access terms, repository terms, or controlled annex terms.
5.3.9(c) An interface instrument shall identify the parties, roles, legal capacity, purpose, scope, permitted use, prohibited use, authority limits, non-execution status, non-agency status, non-partnership status, non-joint-venture status, no shared treasury, no shared liability, no apparent authority, data treatment, AI-use limits, cybersecurity obligations, IP treatment, publication rules, public claims limits, confidentiality, correction obligations, breach handling, termination, and re-review triggers.
5.3.9(d) Where enterprise-stack use is finance-adjacent, the instrument shall include no-investment-advice, no-offer, no-solicitation, no-brokerage, no-lending, no-insurance, no-underwriting, no-rating, no-public-finance-approval, no-capital-commitment, and no-finance-readiness language where material.
5.3.9(e) Where enterprise-stack use is procurement-adjacent, the instrument shall include no-procurement, no-provider-preference, no-vendor-selection, no-prequalification, no-public-purchasing-recommendation, no-public-authority-approval, provider-neutrality, and competition-safety language where material.
5.3.9(f) Where enterprise-stack use is technical, the instrument shall identify technical baseline status, software license, support limits, secure release status, vulnerability reporting, dependency responsibilities, data restrictions, API limits, proof receipt limits, correction path, and non-certification, non-protocol-effect, and non-execution language where material.
5.3.9(g) Where enterprise-stack support involves public authorities, protected knowledge, sovereign data, public-safe release, controlled technology, export-control sensitivity, sanctions sensitivity, health-sensitive data, cyber-sensitive information, or sensitive infrastructure, heightened review and controls shall apply before the interface proceeds.
5.3.9(h) Where no adequate interface instrument exists, GCRI Canada shall restrict, delay, re-scope, quarantine, or refuse enterprise-stack support until role boundaries and records are sufficient.
5.3.9(i) Interface records shall be preserved in the authoritative repository or other controlled record system and shall be available for boundary assurance, correction, and Board review where material.
5.3.9(j) The controlling rule shall be that support across the public-good firewall must be written, scoped, bounded, correctionable, and records-valid.
5.3.10 Two Stacks Doctrine as Anti-Capture, Anti-Procurement-Steering, Anti-Finance-Overclaim, and Anti-Provider-Preference Control. 5.3.10(a) The Two Stacks Doctrine shall operate as an anti-capture, anti-procurement-steering, anti-finance-overclaim, and anti-provider-preference control.
5.3.10(b) As an anti-capture control, the doctrine shall prevent enterprise-stack actors from controlling GCRI Canada’s public-good evidence, methods, observability, ontology, technical baselines, public-good software, publications, public authority learning, GRF inputs, GRA inputs, Protocol Authority inputs, correction decisions, public claims, or institutional meaning.
5.3.10(c) As an anti-procurement-steering control, the doctrine shall prevent GCRI Canada’s evidence records, methods, technical baselines, public-good software, benchmark libraries, dashboards, maps, validation sprints, labs, Nexus Universe activities, public authority learning, or provider demonstrations from being used as hidden procurement specifications, vendor rankings, tender prequalification, public purchasing recommendations, or preferred provider pathways by default.
5.3.10(d) As an anti-finance-overclaim control, the doctrine shall prevent GCRI Canada’s evidence records, diligence gap maps, host-readiness evidence, node evidence, public-safe reports, dashboards, maps, proof inputs, GRA-facing inputs, technical baselines, Academy materials, or Nexus materials from being used as investment advice, securities offerings, capital solicitation, finance-readiness, insurance-readiness, underwriting approval, rating, public finance approval, guarantee, or capital commitment by default.
5.3.10(e) As an anti-provider-preference control, the doctrine shall prevent provider participation, technical contribution, sponsorship, benchmarking, testing, dashboard inclusion, public authority learning participation, Academy participation, Nexus Universe participation, or public-good software compatibility from becoming provider endorsement, preferred status, market superiority, procurement advantage, certification, recognition, finance-readiness, protocol entitlement, or public authority approval by default.
5.3.10(f) The doctrine shall require conflicts review, influence review, provider-neutrality review, sponsor non-control review, procurement-boundary review, finance-boundary review, public claims review, interface records, and correction controls where enterprise-stack actors interact materially with GCRI Canada.
5.3.10(g) Where the Two Stacks Doctrine is breached or at risk of being breached, GCRI Canada shall apply hold, stop-the-line, quarantine, re-scoping, reclassification, handoff, correction, withdrawal, suspension, termination, legal review, Board review, or public-safe clarification as appropriate.
5.3.10(h) The controlling rule shall be that the two stacks may connect, but the enterprise stack shall not purchase public-good meaning, and the public-good stack shall not sell execution consequence.
5.4 Public-Good Firewall
5.4.1 Public-Good Firewall as Structural Boundary Between GCRI Canada’s Public-Good Function and Downstream Commercial, Financial, Procurement, Operational, and Execution Functions. 5.4.1(a) GCRI Canada shall maintain a Public-Good Firewall as a structural boundary between its public-good function and downstream commercial, financial, procurement, operational, infrastructure, market, professional, public authority, and execution functions. The Public-Good Firewall shall preserve GCRI Canada’s constitutional role as a Canadian public-benefit, nonprofit, non-share, non-distributing, non-executing steward of evidence, methods, observability, ontology, technical truth, public-good research and development, public-good software, open technical baselines, Nexus Truth Engine methods, Nexus Observatory methods, public authority learning, public-safe publication, validity-by-record, and correctionability.
5.4.1(b) The Public-Good Firewall shall separate GCRI Canada from enterprise-stack functions performed by National Consortium Companies, Project SPVs, qualified providers, licensed actors, operators, contractors, asset owners, financiers, insurers, underwriters, lenders, rating actors, procurement actors, market actors, public authorities, and other downstream decision-makers or execution actors.
5.4.1(c) The Public-Good Firewall shall not prevent lawful cooperation, evidence handoff, technical-baseline support, public-good software support, public authority learning, GRA interface support, GRF interface support, Protocol Authority interface support, Nexus Observatory methods support, Nexus Universe learning, Academy activity, or enterprise-stack readiness support. It shall require that such cooperation remain role-bounded, records-valid, public-safe, non-executing, provider-neutral, sponsor-non-controlled, correctionable, and governed by appropriate interface records.
5.4.1(d) The Public-Good Firewall shall prevent public-good evidence, methods, technical baselines, software, reports, dashboards, maps, datasets, proof inputs, correction records, and Nexus interfaces from being converted by implication into procurement decisions, financial recommendations, investment materials, public finance approvals, certification, recognition, protocol effect, provider endorsements, sponsor-controlled outputs, public authority decisions, public warnings, emergency commands, professional opinions, or execution instructions.
5.4.1(e) The Public-Good Firewall shall operate across governance, contracts, funding, sponsorship, public claims, programs, events, labs, validation sprints, Nexus Universe activities, public authority learning rooms, capital-reader rooms, provider demonstrations, software releases, repository permissions, dashboard access, map release, data access, AI use, cybersecurity, publications, handoffs, corrections, and public communications.
5.4.1(f) The Public-Good Firewall shall be enforced through role separation, authority mapping, conflict review, influence review, interface agreements, public claims controls, non-reliance language, data and cybersecurity controls, public-safe classification, sponsor non-control clauses, provider-neutrality controls, finance-boundary language, procurement-boundary language, correction obligations, escalation, hold, stop-the-line authority, quarantine, re-scoping, and Board or legal review where material.
5.4.1(g) No person shall treat the Public-Good Firewall as symbolic. It shall be a substantive constitutional control governing how GCRI Canada preserves its upstream public-good role while interfacing with powerful downstream systems.
5.4.1(h) The controlling rule shall be that GCRI Canada may support downstream action through evidence and methods, but the downstream action shall remain outside GCRI Canada unless separately and lawfully authorized in a manner consistent with this Charter.
5.4.2 Public-Good Firewall Protects Evidence Integrity. 5.4.2(a) The Public-Good Firewall shall protect evidence integrity by preventing downstream actors, sponsors, donors, providers, vendors, hosts, capital readers, public authorities, universities, National Consortium Companies, Project SPVs, media actors, Nexus actors, or influential individuals from controlling, purchasing, distorting, suppressing, inflating, delaying, selectively quoting, or repurposing GCRI Canada evidence.
5.4.2(b) Evidence integrity shall require that evidence records remain source-lined, provenance-bearing, limitation-aware, confidence-aware, classification-aware, review-status-bearing, public-safe where required, challengeable, correctionable, supersedable, withdrawable, and capable of handoff without false downstream effect.
5.4.2(c) Evidence shall not be selected, included, excluded, sequenced, weighted, summarized, scored, visualized, dashboarded, mapped, or published to favour a sponsor, donor, provider, host, project, public authority, capital reader, National Consortium Company, Project SPV, policy position, media narrative, finance pathway, procurement pathway, certification pathway, recognition pathway, or protocol pathway.
5.4.2(d) Evidence records may support GRF recognition processes, GRA finance-readiness processes, Protocol Authority technical validity processes, public authority learning, enterprise-stack readiness, public-safe reporting, and Academy learning, but such support shall not alter the evidence record’s original source, scope, limitation, confidence, review status, or correction path.
5.4.2(e) GCRI Canada shall not allow downstream urgency, emergency pressure, public authority interest, capital-reader interest, sponsor expectation, provider expectation, media pressure, funding opportunity, program visibility, or Nexus strategic importance to compromise evidence integrity.
5.4.2(f) Where evidence is contested, incomplete, stale, sensitive, disputed, source-limited, AI-assisted, model-derived, dashboard-generated, DePIN-derived, blockchain-anchored, public authority-derived, sponsor-provided, provider-provided, or finance-relevant, GCRI Canada shall apply appropriate review, labeling, limitation, public-safe classification, and correction controls.
5.4.2(g) Where evidence integrity is threatened or breached, GCRI Canada shall hold, quarantine, reclassify, correct, withdraw, supersede, restrict downstream use, notify affected actors where appropriate, and preserve correction records.
5.4.2(h) The controlling rule shall be that evidence may be useful to downstream actors, but downstream utility shall not control upstream truth.
5.4.3 Public-Good Firewall Protects Methods Integrity. 5.4.3(a) The Public-Good Firewall shall protect methods integrity by preventing GCRI Canada methods, method libraries, method notes, method profiles, observability methods, benchmarking methods, validation sprint methods, public-safe publication methods, data methods, AI methods, cyber methods, ontology methods, Nexus Truth Engine methods, Nexus Observatory methods, and correction methods from being altered, captured, or narrowed to serve downstream commercial, financial, procurement, political, public authority, sponsor, provider, or execution objectives.
5.4.3(b) Methods integrity shall require that methods be documented, versioned, source-aware, assumption-aware, limitation-aware, reviewable, challengeable, reproducible where appropriate, explainable where appropriate, public-safe where required, and correctionable.
5.4.3(c) GCRI Canada methods shall not be designed to predetermine favourable evidence treatment, provider advantage, sponsor benefit, finance-readiness implication, public authority adoption, procurement advantage, certification implication, recognition implication, protocol effect, or market superiority.
5.4.3(d) Benchmarking methods, validation methods, readiness methods, observability methods, dashboard methods, map methods, confidence methods, and technical-baseline methods shall include scope, assumptions, limitations, version, data conditions, configuration conditions, public-safe status, conflicts where material, permitted use, prohibited use, and correction path.
5.4.3(e) Methods may be reused by GRF, GRA, Protocol Authority, Nexus bodies, public authorities, National Consortium Companies, Project SPVs, providers, universities, communities, and other actors, but such reuse shall preserve method status, limitations, public-safe classification, attribution where appropriate, and role boundaries.
5.4.3(f) GCRI Canada shall prevent method drift caused by repeated informal practice, sponsor terms, provider tooling, technical dependency, public authority preference, capital-reader expectations, media framing, event success, or project convenience.
5.4.3(g) Where methods integrity is threatened or breached, GCRI Canada shall revise method records, disclose limitations where appropriate, restrict use, rerun affected review where necessary, correct outputs, supersede or withdraw methods, and preserve correction records.
5.4.3(h) The controlling rule shall be that methods shall serve truth, public benefit, and correctionability, not outcome purchase, provider preference, finance signaling, procurement steering, or institutional convenience.
5.4.4 Public-Good Firewall Protects Research Independence. 5.4.4(a) The Public-Good Firewall shall protect research independence by ensuring that GCRI Canada’s research agenda, evidence review, technical investigation, public-good R&D, public-good software development, observability methods, ontology work, public-safe publication, Academy materials, and technical-baseline work are not controlled by sponsors, donors, funders, providers, hosts, public authorities, capital readers, media actors, enterprise-stack actors, or Nexus-adjacent participants.
5.4.4(b) Research independence shall include independence in question formation, method selection, data selection, limitation disclosure, publication timing, public-safe classification, negative or inconclusive findings, correction, supersession, withdrawal, and refusal to make unsupported public claims.
5.4.4(c) GCRI Canada may accept lawful, mission-aligned, non-controlling, non-extractive, non-enclosing, records-valid support for research and public-good R&D, but such support shall not purchase conclusions, suppress results, prevent correction, require favourable provider treatment, create finance-signaling language, create public authority adoption claims, or determine publication outcome.
5.4.4(d) Research agreements, grants, sponsorships, in-kind contributions, university collaborations, public authority collaborations, provider collaborations, and Nexus collaborations shall include terms sufficient to preserve research independence, evidence integrity, methods integrity, data rights, public-safe publication, confidentiality, cybersecurity, IP treatment, conflict management, and correctionability.
5.4.4(e) GCRI Canada shall distinguish commissioned public-good work from controlled consultancy, research support from outcome purchase, technical contribution from authorship control, sponsor support from publication control, public authority learning from official guidance, and provider participation from provider validation.
5.4.4(f) Where research involves sensitive data, public authority data, Indigenous or local knowledge, protected knowledge, health-sensitive data, cyber-sensitive information, sensitive infrastructure, controlled technology, export-control sensitivity, sanctions sensitivity, or vulnerable communities, research independence shall be paired with heightened safeguards and public-safe release discipline.
5.4.4(g) Where research independence is threatened or breached, GCRI Canada shall disclose conflicts where appropriate, require recusal, revise terms, restrict funder or provider influence, re-review outputs, correct public claims, withdraw or supersede affected materials, terminate support where necessary, and preserve correction records.
5.4.4(h) The controlling rule shall be that research may be supported by many actors, but it shall not be controlled by the interests of those actors.
5.4.5 Public-Good Firewall Protects Public-Good Software and Open Technical Baselines From Enclosure. 5.4.5(a) The Public-Good Firewall shall protect public-good software, open technical baselines, schemas, APIs, reference architectures, test harnesses, evaluation harnesses, dashboards, data tools, ontologies, controlled vocabularies, method libraries, technical documentation, and other public-good technical assets from enclosure.
5.4.5(b) Enclosure includes conversion of public-good technical assets into proprietary control, exclusive dependency, vendor chokepoint, sponsor-controlled release, hidden control surface, private constitutional inventory, unavailable standard, unreviewable platform, uncorrectable system, or commercially gated meaning infrastructure.
5.4.5(c) GCRI Canada shall preserve openness where appropriate, governance where required, security where necessary, controlled release where required, portability, substitutability, interoperability, versioning, documentation, vulnerability reporting, license clarity, dependency review, public-safe publication, and correctionability for public-good technical assets.
5.4.5(d) No sponsor, donor, funder, provider, host, university, public authority, National Consortium Company, Project SPV, capital reader, or Nexus actor shall acquire exclusive control over mission-critical public-good software, technical baselines, semantics, methods, repositories, release channels, or correction paths by support, contribution, hosting, funding, tooling, infrastructure, cloud credits, AI model access, or technical centrality.
5.4.5(e) GCRI Canada shall review technical architecture for vendor lock-in, insecure dependency, proprietary chokepoint, unreviewable AI dependency, hidden data extraction, cloud dependency capture, repository capture, package-channel control, API control, license incompatibility, public-safe release risk, and correction constraints.
5.4.5(f) Public-good software and technical baselines shall not be structured to create procurement preference, provider endorsement, certification, recognition, finance-readiness, protocol effect, public authority approval, or execution obligation by default.
5.4.5(g) Where enclosure risk arises, GCRI Canada shall revise licensing, broaden stewardship, document dependencies, create exit plans, preserve mirrors or alternatives where appropriate, restrict sponsor or provider control, re-scope release, quarantine components, or seek Board review where material.
5.4.5(h) The controlling rule shall be that public-good technical assets may be governed and secured, but they shall not be enclosed.
5.4.6 Public-Good Firewall Protects Public Authority Learning From Public Authority Substitution. 5.4.6(a) The Public-Good Firewall shall protect public authority learning from public authority substitution. GCRI Canada may support public authorities through evidence literacy, technical literacy, AI literacy, cyber literacy, observability interpretation, scenario learning, public-safe reporting, dashboards, maps, technical baselines, Academy materials, and methods support, but shall not become a public authority by doing so.
5.4.6(b) Public authority learning shall remain distinct from official guidance, public authority decision-making, regulatory approval, enforcement position, procurement approval, public finance approval, public warning, emergency command, public health order, public safety directive, sovereign obligation, public-private partnership, or delegation.
5.4.6(c) Public authority participation shall be capacity-classified where material, including whether the public authority is acting as observer, learner, technical participant, evidence contributor, data contributor, host, funder, reviewer, public finance reader, procurement observer, regulator attending in non-regulatory capacity, public safety learner, emergency management learner, public health learner, official decision-maker in its own separate process, or another defined capacity.
5.4.6(d) GCRI Canada materials provided to public authorities shall identify issuer, scope, purpose, limitations, public-safe status, data restrictions, review status, non-decision status, non-delegation status, non-warning status, non-command status, and correction path where material.
5.4.6(e) GCRI Canada shall not use public authority names, logos, titles, photographs, quotes, agency names, jurisdiction references, official classifications, public authority data, attendance, funding, hosting, or review to imply endorsement, adoption, public authority approval, official guidance, procurement approval, public finance approval, public-private partnership, public warning, emergency command, or sovereign obligation.
5.4.6(f) Where public authority materials require official decision, warning, command, regulatory action, procurement action, funding action, public finance action, or public guidance, GCRI Canada shall hand off or route the matter to the competent public authority and preserve GCRI Canada’s support-only role.
5.4.6(g) Where public authority substitution risk arises, GCRI Canada shall reclassify capacity, revise materials, restrict public claims, remove official-looking design, route to competent authority, issue correction, or escalate to legal or Board review.
5.4.6(h) The controlling rule shall be that GCRI Canada may help public authorities learn, but public authorities must decide through their own lawful processes.
5.4.7 Public-Good Firewall Protects Finance-Readiness Inputs From Becoming Financial Execution. 5.4.7(a) The Public-Good Firewall shall protect finance-readiness inputs from becoming financial execution. GCRI Canada may produce and hand off evidence, methods, observability summaries, technical baselines, host-readiness evidence, node evidence, public-safe reports, diligence gap maps, proof inputs, Academy materials, data governance records, AI governance records, cybersecurity records, and correction records that may be useful to GRA, capital readers, insurers, lenders, public finance actors, Project SPVs, National Consortium Companies, or other downstream actors.
5.4.7(b) Such inputs shall not constitute finance-readiness, capital-readiness, capital readability, proof-pack completion, insurance-readiness, investment advice, securities advice, securities offering, capital solicitation, brokerage, finder activity, placement activity, lending approval, credit approval, guarantee, insurance advice, underwriting, rating, public finance approval, grant approval, MDB approval, DFI approval, sovereign finance approval, capital commitment, investor suitability, fundability, bankability, or transaction recommendation.
5.4.7(c) GCRI Canada shall not receive transaction-based compensation, success fees, placement fees, brokerage commissions, finder fees, closing incentives, lending approval incentives, insurance placement incentives, underwriting incentives, rating outcome incentives, public finance approval incentives, procurement award incentives, or equivalent outcome-based compensation.
5.4.7(d) Finance-facing materials shall include no-investment-advice, no-offer, no-solicitation, no-brokerage, no-finder, no-placement, no-lending, no-credit-approval, no-guarantee, no-insurance-advice, no-underwriting, no-rating, no-public-finance-approval, no-capital-commitment, and no-finance-readiness language where material.
5.4.7(e) Evidence packs, diligence gap maps, dashboards, public-safe reports, technical baselines, proof inputs, and Academy materials shall not be repurposed into offering materials, investor decks, lender approvals, insurance approvals, underwriting packages, rating packages, public finance approvals, or transaction materials by default.
5.4.7(f) Where finance-facing handoff is appropriate, GCRI Canada shall distinguish GCRI Canada evidence inputs from GRA finance-readiness processes and from decisions of investors, lenders, insurers, underwriters, rating actors, MDBs, DFIs, public finance actors, sponsors, Project SPVs, National Consortium Companies, and other downstream actors.
5.4.7(g) Where financial execution risk arises, GCRI Canada shall route to GRA or another competent actor, restrict finance-facing use, revise materials, remove finance-signaling language, seek regulated-perimeter review, correct overclaims, withdraw materials where necessary, and preserve correction records.
5.4.7(h) The controlling rule shall be that GCRI Canada may support finance-relevant evidence literacy, but it shall not perform finance.
5.4.8 Public-Good Firewall Protects Provider Neutrality and Competition Safety. 5.4.8(a) The Public-Good Firewall shall protect provider neutrality and competition safety by preventing GCRI Canada’s evidence, methods, public-good software, technical baselines, events, labs, validation sprints, Nexus Universe activities, dashboards, maps, public-safe reports, public authority learning activities, Academy materials, and Nexus interfaces from creating provider preference, procurement advantage, market allocation, hidden vendor selection, or competition distortion by default.
5.4.8(b) Provider participation, technical contribution, software contribution, data contribution, demonstration, testing, benchmarking, sponsorship, hosting, dashboard inclusion, repository contribution, Academy participation, public authority learning participation, validation sprint participation, Nexus Universe participation, or Nexus Observatory participation shall not create provider endorsement, preferred status, procurement approval, certification, recognition, finance-readiness, protocol entitlement, public authority approval, or market superiority.
5.4.8(c) GCRI Canada shall design benchmarks, tests, technical baselines, schemas, APIs, public-good software, dashboards, maps, and public-safe reports to be provider-neutral, method-bounded, evidence-bounded, public-safe, limitation-aware, correctionable, and competition-safe.
5.4.8(d) GCRI Canada shall not structure public authority learning rooms, provider demonstrations, technical showcases, event agendas, sponsor benefits, Academy materials, validation sprints, or Nexus Universe activities to provide paid or preferential access to public buyers, procurement actors, regulators, public finance actors, or public authority decision-makers.
5.4.8(e) Where providers are named, displayed, compared, benchmarked, or referenced, the record shall identify scope, method, limitations, conflicts where material, sponsor relationship where material, public-safe status, non-endorsement status, non-procurement status, non-certification status, non-recognition status, non-finance-readiness status, and correction path.
5.4.8(f) GCRI Canada shall review provider relationships for conflicts, provider lock-in, benchmark influence, technical dependency, data access control, repository control, dashboard control, sponsor-provider overlap, public claims overreach, and procurement-signaling risk.
5.4.8(g) Where provider neutrality or competition safety is threatened, GCRI Canada shall revise criteria, add boundary language, separate roles, restrict access, rerun or withdraw benchmarks where necessary, correct public claims, suspend participation, terminate relationships, notify affected actors where appropriate, and preserve correction records.
5.4.8(h) The controlling rule shall be that public-good technical truth shall remain provider-neutral and competition-safe.
5.4.9 Public-Good Firewall Protects Sponsor Support From Sponsor Control. 5.4.9(a) The Public-Good Firewall shall protect sponsor, donor, funder, host, and supporter support from becoming control. Support may sustain GCRI Canada’s public-good work, but it shall not control public-good meaning.
5.4.9(b) Sponsors, donors, funders, hosts, and supporters shall not control governance, Board decisions, officer decisions, program design, evidence selection, method selection, data inclusion, benchmark design, publication timing, public-safe classification, dashboard display, map design, technical-baseline outcomes, public-good software release, public authority access, provider participation, GRF inputs, GRA inputs, Protocol Authority inputs, correction decisions, public claims, or institutional doctrine.
5.4.9(c) Sponsor support shall not purchase outcomes, access, recognition, finance-readiness, certification, procurement advantage, provider preference, Docket status, Grid status, benchmark advantage, publication outcome, method selection, data inclusion, public authority proximity, capital-reader proximity, public authority endorsement, protocol implication, or execution opportunity.
5.4.9(d) Sponsor acknowledgments shall be factual, proportionate, approved where required, non-endorsement, non-recognition, non-finance-readiness, non-certification, non-procurement, non-public-authority-approval, non-protocol-effect, non-execution, and correctionable.
5.4.9(e) Sponsor and donor agreements shall include non-control language, public claims limits, mark-use controls, confidentiality, data restrictions, publication independence, correction independence, conflicts controls, sponsor visibility limits, termination rights, return or refusal rights where appropriate, and boundary language where material.
5.4.9(f) Where a sponsor is also a provider, vendor, host, capital actor, public authority contractor, Project SPV participant, National Consortium Company participant, or subject of evidence review, GCRI Canada shall apply heightened conflict review, influence review, sponsor-provider separation, public claims review, and Board review where material.
5.4.9(g) Where sponsor control risk arises, GCRI Canada shall refuse support, narrow support, revise terms, separate sponsor visibility from substantive activity, restrict public claims, disclose conflicts where appropriate, return support where appropriate, suspend benefits, terminate the relationship, correct public materials, or escalate to Board review.
5.4.9(h) The controlling rule shall be that GCRI Canada may be supported, but it shall not be steered.
5.4.10 Firewall Breach Indicators, Escalation, Quarantine, Correction, and Handoff. 5.4.10(a) GCRI Canada shall maintain firewall breach indicators, escalation pathways, quarantine powers, correction procedures, and boundary-safe handoff mechanisms to detect, prevent, contain, and remedy Public-Good Firewall breaches.
5.4.10(b) Firewall breach indicators include sponsor or donor attempts to influence evidence, methods, publication, data inclusion, benchmark design, public authority access, provider participation, correction, or technical-baseline outcomes; provider attempts to claim preference, endorsement, procurement advantage, certification, recognition, finance-readiness, or protocol effect; enterprise actors using GCRI Canada materials as offering materials, procurement recommendations, public authority approvals, or execution instructions; and public authorities or partners misdescribing GCRI Canada as a decision-maker.
5.4.10(c) Firewall breach indicators also include transaction-based compensation, success fees, closing incentives, sponsor veto rights, provider-controlled methods, hidden vendor dependencies, unrecorded technical forks, public authority capacity ambiguity, public-warning-like dashboards, emergency-command-like materials, finance-signaling evidence packs, certification-like badges, recognition-like language, protocol-effect language, proof-receipt overclaim, AI-as-authority overclaim, and removal of required disclaimers.
5.4.10(d) Any director, officer, staff member, contractor, fellow, advisor, council participant, working group participant, sponsor, provider, host, public authority participant, community participant, university participant, capital reader, Nexus actor, or affected person may escalate a suspected firewall breach.
5.4.10(e) Upon detection of a potential firewall breach, GCRI Canada may impose hold, stop-the-line action, quarantine, access restriction, publication hold, dashboard disablement, repository lock, data room restriction, public claims freeze, sponsor benefit suspension, provider participation suspension, finance-facing circulation hold, public authority reference hold, or other interim relief proportionate to risk.
5.4.10(f) Quarantine may apply to affected reports, datasets, dashboards, maps, software, technical baselines, APIs, evidence packs, proof receipts, AI outputs, model outputs, public claims, sponsor materials, provider materials, public authority materials, event materials, Nexus materials, contracts, interface instruments, or program records.
5.4.10(g) Correction may include revising language, adding disclaimers, removing logos, removing badges, relabeling dashboards, relabeling maps, correcting metadata, revising repository labels, revising public claims, issuing public-safe correction notices, issuing controlled correction notices, superseding materials, withdrawing materials, terminating access, terminating sponsorship, terminating provider participation, or taking contractual or legal action.
5.4.10(h) Where the matter properly belongs to GRF, GRA, Protocol Authority, a public authority, a licensed professional, a National Consortium Company, a Project SPV, a qualified provider, a regulator, a procurement actor, a finance actor, an insurer, an underwriter, a rating actor, or another competent actor, GCRI Canada shall use boundary-safe handoff rather than assume the downstream role.
5.4.10(i) Firewall breach records shall identify the breach indicator, actor, affected materials, affected systems, affected audiences, risk classification, interim controls, reviewer, decision authority, correction action, handoff where any, notice decision, closeout, residual risk, and prevention measures.
5.4.10(j) Repeated firewall breach patterns shall trigger review of agreements, sponsor terms, provider terms, public authority protocols, finance-boundary controls, procurement-boundary controls, public claims templates, dashboard design, map design, repository labels, proof-receipt labels, AI-use controls, technical architecture, training, and Board reporting.
5.4.10(k) The controlling rule shall be that the Public-Good Firewall shall be actively monitored, enforced, corrected, and strengthened; it shall not depend on informal trust, reputation, goodwill, or assumed understanding.
5.5 Six Institutional Families Reading Rule
5.5.1 GCRI Canada Within the Public-Good Protocol / Evidence / Methods Family. 5.5.1(a) GCRI Canada shall be read as an institution within the Nexus public-good protocol, evidence, and methods family. Its institutional function shall be upstream, public-benefit, non-executing, records-valid, public-safe, and correctionable, centered on evidence, methods, observability, ontology, technical truth, public-good research and development, public-good software, open technical baselines, Nexus Truth Engine methods, Nexus Observatory methods, public authority learning, and technical memory.
5.5.1(b) GCRI Canada’s placement within the public-good protocol, evidence, and methods family shall not make it the whole family. It shall not by default exercise every public-good stack function, and shall not be treated as identical to The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards / Protocol Authority, Nexus Network, Nexus Universe, Nexus Observatory, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, or any other Nexus public-good body.
5.5.1(c) Within the public-good protocol, evidence, and methods family, GCRI Canada’s primary constitutional role shall be the stewardship of upstream technical truth. It may support recognition, finance-readiness, protocol discipline, public authority learning, Nexus rail interoperability, Academy literacy, Observatory methods, and public-safe reporting through evidence and methods inputs, but it shall not become the body that issues the downstream effect unless separately and lawfully authorized within its Charter boundaries.
5.5.1(d) GCRI Canada shall preserve the governing formula that GCRI Canada produces and stewards upstream technical truth; GRF stewards public-facing legitimacy, registry, recognition, maturity records, standing, claims discipline, stakeholder formation, and public-safe reporting; GRA stewards finance-readiness, capital readability, proof packs, insurance-readiness, capital-reader rooms, RNFD, NFD, UNFSD, and regulated-perimeter discipline; and Nexus Standards / Protocol Authority stewards protocol discipline, conformance logic, role keys, smart licenses, proof receipts, entitlement states, anchoring discipline, and technical validity surfaces.
5.5.1(e) References to GCRI Canada as a Nexus public-good institution shall therefore be interpreted as references to its specific evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, and open technical-baseline role, not as references to general Nexus control, public authority status, finance authority, recognition authority, certification authority, procurement authority, protocol authority, enterprise authority, or execution authority.
5.5.1(f) GCRI Canada shall not permit its public-good protocol, evidence, and methods role to be misdescribed as a mandate to regulate, procure, finance, certify, recognize, command, warn, execute, own assets, operate infrastructure, provide professional regulated opinions, control providers, control sponsors, or bind public authorities.
5.5.1(g) Where a Nexus reference does not clearly identify which public-good institution is acting, GCRI Canada shall use the narrowest accurate reading and shall identify the proper actor, record, role, authority, and boundary before reliance.
5.5.1(h) The controlling rule shall be that GCRI Canada belongs within the public-good truth and methods family, and its authority shall be read through that role alone.
5.5.2 Distinction From Regional Governance Family. 5.5.2(a) GCRI Canada shall be distinguished from the regional governance family within the Nexus architecture. Regional governance bodies, including Regional Nexus Consortiums and related regional coordination structures, may support regional alignment, regional convening, regional public-good coordination, regional institutional participation, regional hazard interpretation, regional stakeholder formation, regional public authority learning surfaces, and cross-border interoperability within their own mandates.
5.5.2(b) GCRI Canada shall not be treated as a Regional Nexus Consortium, regional governance authority, regional coordinating body, regional political body, regional public authority substitute, regional mandate holder, or regional execution coordinator by reason of its Nexus alignment, Canadian seat, evidence support, methods support, public authority learning support, or participation in regional Nexus activities.
5.5.2(c) Regional governance family functions may involve regional prioritization, regional consortium alignment, regional public authority interfaces, regional participation architecture, regional knowledge translation, and regional coordination among national or local actors. GCRI Canada may contribute evidence, methods, observability logic, technical baselines, public-safe reports, Academy materials, and correction records to such functions, but shall not thereby assume regional governance authority.
5.5.2(d) GCRI Canada’s Canadian stewardship role may include Canada-to-global and global-to-Canada evidence translation, Canadian public authority learning, Canadian observability methods support, Canadian data and sovereignty compatibility, and Canadian technical memory. Such role shall not be interpreted as authority over regional Nexus bodies or as a regional mandate over other jurisdictions.
5.5.2(e) Regional governance bodies shall not use GCRI Canada outputs to claim regional approval, public authority adoption, procurement authority, finance-readiness, recognition, certification, protocol effect, public warning, emergency command, public-private partnership, or execution authority unless a competent actor separately creates that effect through proper record and authority.
5.5.2(f) Interface between GCRI Canada and regional governance family actors shall be records-valid and shall identify role, scope, evidence status, data treatment, public-safe classification, public authority boundaries, finance boundaries, provider neutrality, sponsor non-control, publication limits, and correction path.
5.5.2(g) Where GCRI Canada’s role is blurred with regional governance, GCRI Canada shall correct public materials, clarify institutional separateness, revise interface records, restrict public claims, and preserve correction records.
5.5.2(h) The controlling rule shall be that GCRI Canada may support regional governance with technical truth, but it does not become regional governance.
5.5.3 Distinction From Sovereign National Family. 5.5.3(a) GCRI Canada shall be distinguished from the sovereign national family within the Nexus architecture. Sovereign national family functions may include national public authority action, national legal mandates, national public finance, national procurement, national emergency management, national regulatory authority, national public infrastructure policy, national data governance, national security, national public health, national public safety, and national sovereign decision-making.
5.5.3(b) GCRI Canada shall not be treated as a sovereign national actor, public authority, government department, Crown agent, regulator, national procurement authority, national emergency command body, public warning authority, public finance authority, national security authority, national infrastructure operator, or sovereign representative by reason of its Canadian seat, public-benefit purpose, public authority learning work, public authority participation, or Nexus alignment.
5.5.3(c) GCRI Canada may support sovereign national family actors with evidence, methods, public-safe reports, controlled annexes, dashboards, maps, technical baselines, public-good software, observability methods, public authority learning, Academy materials, and correction records, but shall do so as a non-executing support institution and not as a delegate of sovereign authority by default.
5.5.3(d) Public authority participation in GCRI Canada activities shall be capacity-classified where material and shall not create endorsement, adoption, delegation, public-private partnership, procurement approval, public finance approval, regulatory approval, enforcement position, official guidance, public warning, emergency command, sovereign obligation, or public authority decision by default.
5.5.3(e) GCRI Canada shall respect federal, provincial, territorial, Indigenous, local, public authority, research, privacy, data, AI, cyber, employment, tax, accessibility, sanctions, export-control, corporate, and other applicable Canadian law contexts while preserving its own legal separateness and non-public-authority status.
5.5.3(f) Sovereign national family actors shall not use GCRI Canada evidence, dashboards, maps, proof receipts, reports, public-good software, or technical baselines as official public authority acts unless the competent public authority separately adopts, issues, or relies upon such materials through its own lawful process and record.
5.5.3(g) Where GCRI Canada materials are used in sovereign national contexts, the record shall distinguish GCRI Canada evidence support from public authority decision, public authority learning from official guidance, observability from official warning, dashboard display from public action, and handoff from delegation.
5.5.3(h) The controlling rule shall be that GCRI Canada may serve public authority learning within Canada and beyond, but public authority remains with public authorities.
5.5.4 Distinction From Enterprise Systems Family. 5.5.4(a) GCRI Canada shall be distinguished from the enterprise systems family within the Nexus architecture. Enterprise systems family actors may include National Consortium Companies, Project SPVs, delivery entities, systems integrators, qualified providers, operators, asset owners, contractors, managed service providers, technology vendors, platform operators, infrastructure operators, customer-facing delivery bodies, and other lawful execution actors.
5.5.4(b) GCRI Canada shall not be treated as an enterprise systems actor, National Consortium Company, Project SPV, provider, vendor, operator, contractor, managed service provider, delivery entity, implementation body, project manager, asset owner, infrastructure operator, employer of downstream field teams, customer-facing service provider, or commercial execution vehicle by reason of providing evidence, methods, technical baselines, public-good software, observability methods, public-safe reports, dashboards, maps, or Academy materials.
5.5.4(c) Enterprise systems family actors shall remain responsible for contracts, delivery, deployment, operations, infrastructure, service levels, warranties, personnel, subcontractors, cybersecurity, data processing, licensing, permits, insurance, safety, incident response, customer support, revenues, taxes, liabilities, public claims, and corrections.
5.5.4(d) GCRI Canada may support enterprise systems family actors by providing public-good evidence, methods, open technical baselines, public-good software documentation, reference architectures, schemas, APIs, test harnesses, evaluation harnesses, public-safe reports, controlled annexes, observability methods, and correction records, provided that such support is records-valid, non-executing, provider-neutral, sponsor-non-controlled, and boundary-safe.
5.5.4(e) GCRI Canada shall not select, prefer, certify, recognize, rank, procure, endorse, validate for market use, approve, finance, insure, underwrite, guarantee, manage, supervise, or control enterprise systems actors by default.
5.5.4(f) Enterprise systems family actors shall not use GCRI Canada materials to imply procurement advantage, provider preference, certification, recognition, finance-readiness, public authority approval, protocol effect, public warning, emergency command, professional opinion, or execution authority beyond the record.
5.5.4(g) Interface with enterprise systems family actors shall require appropriate participant terms, interface agreements, data agreements, IP terms, technical-baseline terms, software licenses, public claims controls, provider-neutrality controls, sponsor non-control controls, and correction obligations.
5.5.4(h) The controlling rule shall be that GCRI Canada may strengthen enterprise systems through public-good technical truth, but enterprise systems execution remains outside GCRI Canada.
5.5.5 Distinction From Capital and Funds Family. 5.5.5(a) GCRI Canada shall be distinguished from the capital and funds family within the Nexus architecture. Capital and funds family actors may include GRA-facing capital readers, investors, lenders, insurers, reinsurers, underwriters, rating actors, public finance actors, MDBs, DFIs, banks, funds, grantors, donors, sponsors, Project SPV finance actors, National Consortium Company finance actors, and other finance or capital-formation participants.
5.5.5(b) GCRI Canada shall not be treated as a capital actor, fund, investment adviser, securities offeror, issuer, broker, dealer, placement agent, finder, capital introducer, lender, credit approver, guarantor, insurer, reinsurer, underwriter, rating agency, public finance approver, grant approver, MDB approver, DFI approver, sovereign finance approver, fund manager, payment intermediary, clearing actor, settlement actor, or market operator by reason of producing finance-relevant evidence.
5.5.5(c) GCRI Canada may provide evidence inputs, methods inputs, observability summaries, host-readiness evidence, node evidence, technical-baseline records, public-good software documentation, public-safe reports, controlled annexes, diligence gap maps, proof inputs, Academy materials, and correction records that may support GRA or other competent finance-facing actors, but shall not issue finance-readiness or provide financial execution.
5.5.5(d) Capital and funds family actors shall remain responsible for their own investment decisions, finance-readiness determinations, credit decisions, underwriting decisions, insurance decisions, rating decisions, public finance decisions, capital commitments, securities compliance, offering documents, due diligence, risk acceptance, public claims, legal compliance, regulated permissions, and corrections.
5.5.5(e) GCRI Canada shall not receive transaction-based compensation, success fees, finder fees, placement fees, brokerage commissions, closing incentives, lending approval incentives, insurance placement incentives, underwriting incentives, rating outcome incentives, public finance approval incentives, procurement award incentives, or equivalent outcome-based compensation.
5.5.5(f) GCRI Canada materials shall not be used as offering materials, investment recommendations, lender approvals, insurance approvals, underwriting packages, ratings, guarantees, public finance approvals, grant approvals, capital commitments, finance-readiness determinations, insurance-readiness determinations, fundability determinations, bankability determinations, or investor suitability determinations by default.
5.5.5(g) Finance-facing interfaces shall include no-investment-advice, no-offer, no-solicitation, no-brokerage, no-lending, no-insurance, no-underwriting, no-rating, no-public-finance-approval, no-capital-commitment, no-finance-readiness, public claims limits, GRA distinction, and correction controls where material.
5.5.5(h) The controlling rule shall be that GCRI Canada may inform capital readability through evidence, but it shall not act as capital.
5.5.6 Distinction From Licensed Execution / Market Infrastructure Family. 5.5.6(a) GCRI Canada shall be distinguished from the licensed execution and market infrastructure family within the Nexus architecture. Licensed execution and market infrastructure family actors may include regulated utilities, telecommunications carriers, payment systems, exchanges, clearing systems, settlement systems, insurers, reinsurers, brokers, dealers, lenders, underwriters, rating agencies, regulated professionals, licensed engineers, legal professionals, clinical professionals, public health professionals, auditors, accountants, actuaries, cybersecurity assurance providers, infrastructure operators, market operators, and other regulated or licensed actors.
5.5.6(b) GCRI Canada shall not be treated as a licensed execution actor, market infrastructure operator, regulated financial actor, regulated professional body, utility, telecommunications operator, payment system, exchange, clearing system, settlement system, insurer, reinsurer, broker, dealer, lender, underwriter, rating agency, professional adviser, or regulated service provider by reason of technical expertise, evidence outputs, public-good software, technical baselines, dashboards, maps, AI tools, proof receipts, or Nexus proximity.
5.5.6(c) GCRI Canada may provide evidence, methods, technical baselines, public-good software, public-safe reports, controlled annexes, public authority learning materials, Academy materials, observability methods, and correction records to licensed execution and market infrastructure actors, but shall not perform their licensed or regulated functions by default.
5.5.6(d) Licensed execution and market infrastructure actors shall remain responsible for their own licenses, permissions, professional standards, compliance, public authority obligations, customer obligations, market obligations, operational duties, legal duties, safety duties, cybersecurity duties, data duties, insurance duties, capital duties, public claims, and corrections.
5.5.6(e) Technical interfaces, APIs, proof receipts, blockchain anchors, smart contracts, tokens, data feeds, dashboards, confidence scores, model outputs, or automated classifications maintained or supported by GCRI Canada shall not create clearing, settlement, payment, trading, insurance, underwriting, lending, rating, public warning, emergency command, professional assurance, or regulated market effect by default.
5.5.6(f) Where licensed execution or market infrastructure actors use GCRI Canada materials in regulated processes, they shall remain responsible for determining whether and how such materials may lawfully be used, relied upon, disclosed, corrected, or incorporated into their own records.
5.5.6(g) GCRI Canada shall apply legal, professional, data, AI, cyber, public-safe, and boundary review where materials may be mistaken for regulated professional opinions, market infrastructure outputs, public authority findings, financial determinations, public warning outputs, or execution instructions.
5.5.6(h) The controlling rule shall be that GCRI Canada may support licensed systems with public-good evidence and methods, but it does not become a licensed execution or market infrastructure actor.
5.5.7 Family Alignment Without Family Merger. 5.5.7(a) Institutional family alignment shall not create family merger. Alignment across public-good protocol, evidence, and methods; regional governance; sovereign national; enterprise systems; capital and funds; and licensed execution or market infrastructure families shall preserve separate legal status, mandate, authority, governance, treasury, liability, personnel, records, data obligations, public claims, and correction responsibilities.
5.5.7(b) Shared Nexus mission, shared doctrine, shared vocabulary, shared rail, shared evidence structures, shared events, shared dashboards, shared public-safe reports, shared technical baselines, shared public-good software, shared Academy materials, shared public authority interfaces, shared sponsor support, or shared provider participation shall not merge institutional families.
5.5.7(c) GCRI Canada shall not become a regional governance actor, sovereign national actor, enterprise systems actor, capital actor, fund actor, licensed execution actor, market infrastructure actor, public authority, provider, sponsor, host, public-private partnership body, or execution vehicle by family alignment.
5.5.7(d) Other institutional families shall not acquire control over GCRI Canada’s Board, officers, mission, evidence, methods, ontologies, technical baselines, public-good software, publications, public-safe release, correction, repositories, dashboards, public authority learning, or institutional meaning by family alignment.
5.5.7(e) Cross-family cooperation shall require role clarity, records-valid instruments, public claims controls, data and cybersecurity controls, IP treatment, public-safe classification, boundary language, correction obligations, and downstream responsibility mapping where material.
5.5.7(f) Where family alignment creates confusion, GCRI Canada shall identify the correct family, actor, role, record, authority, limitation, public-safe status, and correction path before proceeding or permitting public reliance.
5.5.7(g) Public materials shall avoid language suggesting that Nexus families are one entity, one chain of command, one treasury, one liability pool, one public authority, one finance platform, one provider network, one execution system, or one market infrastructure by default.
5.5.7(h) The controlling rule shall be that the six families align through Nexus architecture, but they do not merge into a single actor.
5.5.8 Family Interfaces Through Records, MoUs, Protocols, Public-Safe Summaries, and Role-Bound Instruments. 5.5.8(a) Interfaces among institutional families involving GCRI Canada shall be conducted through records, memoranda of understanding, cooperation agreements, interface agreements, data agreements, IP agreements, public authority protocols, sponsor terms, provider terms, public-safe summaries, technical contribution records, handoff records, public claims protocols, and other role-bound instruments proportionate to risk.
5.5.8(b) Interface instruments shall identify the families involved, entities involved, legal capacity, purpose, scope, authority, non-authority, permitted use, prohibited use, records exchanged, evidence status, method status, technical status, public-safe classification, data classification, confidentiality, AI-use limits, cybersecurity obligations, IP treatment, public claims limits, publication rules, correction obligations, breach handling, termination, and re-review triggers.
5.5.8(c) Interfaces with the public-good protocol, evidence, and methods family shall preserve distinctions among GCRI Canada, GRF, GRA, Protocol Authority, Nexus Network, Nexus Universe, Nexus Observatory, Nexus Grid, Nexus Rails, Nexus Academy, and related bodies.
5.5.8(d) Interfaces with the regional governance family shall preserve regional coordination boundaries, local truth, public authority capacity, non-delegation, non-merger, and non-execution.
5.5.8(e) Interfaces with the sovereign national family shall preserve public authority boundaries, jurisdictional authority, public law, privacy, sovereign data, public finance, procurement, emergency command, public warning, and official action boundaries.
5.5.8(f) Interfaces with the enterprise systems family shall preserve non-execution, provider neutrality, procurement neutrality, asset ownership boundaries, delivery responsibility, operational liability, technical-baseline limits, data controls, and correction obligations.
5.5.8(g) Interfaces with the capital and funds family shall preserve no-investment-advice, no-offer, no-solicitation, no-brokerage, no-lending, no-insurance, no-underwriting, no-rating, no-public-finance-approval, no-capital-commitment, no-finance-readiness, GRA distinction, and regulated-perimeter controls.
5.5.8(h) Interfaces with the licensed execution or market infrastructure family shall preserve professional boundaries, licensed actor responsibility, market infrastructure boundaries, regulated activity limits, public authority boundaries, data and cyber controls, professional review, and non-execution.
5.5.8(i) Public-safe summaries may be used to communicate cross-family work to public audiences, provided that such summaries do not imply merger, authority transfer, public authority adoption, finance-readiness, certification, recognition, protocol effect, procurement advantage, provider endorsement, sponsor control, or execution consequence beyond the record.
5.5.8(j) The controlling rule shall be that cross-family interface must be written, bounded, records-valid, public-safe, and correctionable.
5.5.9 No Institutional Family May Use GCRI Canada Outputs to Claim Another Family’s Authority Without Proper Records and Competent Authority. 5.5.9(a) No institutional family, actor, participant, sponsor, provider, public authority, capital reader, National Consortium Company, Project SPV, licensed actor, university, host, media actor, community participant, or Nexus actor may use GCRI Canada outputs to claim another institutional family’s authority without proper records and competent authority.
5.5.9(b) GCRI Canada evidence, methods, observability summaries, ontologies, technical baselines, public-good software, public-safe reports, dashboards, maps, datasets, proof inputs, proof receipts, Academy materials, public authority learning materials, correction records, or handoff materials shall not be used to claim GRF recognition, standing, maturity records, claims approval, public-facing legitimacy, or registry status unless GRF or another competent recognition actor has separately issued such effect through its own process and record.
5.5.9(c) GCRI Canada outputs shall not be used to claim GRA finance-readiness, capital readability, proof-pack completion, insurance-readiness, capital-reader approval, RNFD, NFD, UNFSD status, investment suitability, finance approval, public finance approval, underwriting approval, rating, guarantee, or capital commitment unless GRA or another competent finance or regulated actor has separately created such effect through its own process and record.
5.5.9(d) GCRI Canada outputs shall not be used to claim Protocol Authority effect, conformance status with external force, role key, smart-license right, proof-receipt legal effect, entitlement state, protocol approval, technical validity surface, or protocol enforcement unless Protocol Authority or another competent protocol actor has separately created such effect through its own process and record.
5.5.9(e) GCRI Canada outputs shall not be used to claim public authority approval, official guidance, regulatory approval, enforcement position, procurement approval, public finance approval, emergency command, public warning, sovereign obligation, public-private partnership, or public adoption unless a competent public authority has separately created such effect through its own lawful process and record.
5.5.9(f) GCRI Canada outputs shall not be used to claim enterprise execution, asset ownership, project delivery, deployment authority, provider selection, operational readiness, customer commitment, infrastructure operation, or Project SPV action unless the competent enterprise actor has separately taken that action through its own lawful process and record.
5.5.9(g) GCRI Canada outputs shall not be used to claim professional opinion, regulated assurance, legal advice, engineering approval, clinical advice, accounting opinion, audit opinion, actuarial opinion, insurance opinion, investment opinion, rating opinion, cybersecurity assurance, environmental assurance, or safety assurance unless a competent licensed or regulated professional has separately issued such output through proper engagement and record.
5.5.9(h) Where another family or actor uses GCRI Canada outputs to claim authority beyond the proper record, GCRI Canada shall correct, restrict use, withdraw permission, notify the competent actor where appropriate, require public-safe clarification, suspend access, terminate participation, or pursue legal remedies where appropriate.
5.5.9(i) The controlling rule shall be that GCRI Canada outputs may support other families, but they shall not impersonate those families’ authority.
5.5.10 Six-Family Reading Rule for All Nexus References in GCRI Canada Materials. 5.5.10(a) All references to Nexus in GCRI Canada materials shall be interpreted through the Six Institutional Families Reading Rule. Nexus references shall identify or preserve the distinction among the public-good protocol, evidence, and methods family; the regional governance family; the sovereign national family; the enterprise systems family; the capital and funds family; and the licensed execution or market infrastructure family.
5.5.10(b) Where a GCRI Canada material uses terms such as Nexus, Nexus Network, Nexus Universe, Nexus Observatory, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Standards, Protocol Authority, Regional Nexus Consortium, National Nexus Consortium, National Consortium Company, Project SPV, qualified provider, capital reader, public authority, or equivalent terms, the material shall not imply that all such actors share one authority, one legal person, one treasury, one liability, one Board, one public authority mandate, one finance function, one provider role, one protocol role, or one execution role.
5.5.10(c) Nexus references shall distinguish upstream truth from public-facing legitimacy, public-facing legitimacy from finance-readiness, finance-readiness from finance execution, protocol support from protocol effect, public authority learning from public authority decision, technical baseline from certification, provider participation from provider endorsement, public authority participation from public authority adoption, and enterprise readiness support from enterprise execution.
5.5.10(d) Public materials, interface agreements, program materials, Academy materials, reports, dashboards, maps, datasets, software documentation, technical baselines, sponsor materials, provider materials, public authority materials, finance-facing materials, and Nexus coordination instruments shall use the Six-Family Reading Rule to avoid role confusion.
5.5.10(e) Where a Nexus reference could be read in more than one family, GCRI Canada shall use the narrower non-executing reading until the proper family, actor, authority, record, and boundary are identified.
5.5.10(f) Where a Nexus reference concerns a downstream effect, the material shall identify the competent family and actor responsible for that effect and shall state that GCRI Canada does not create that effect by default.
5.5.10(g) Where a Nexus reference creates ambiguity about merger, agency, partnership, joint venture, parent-subsidiary status, shared liability, shared treasury, public authority status, finance status, provider status, sponsor control, protocol effect, certification, recognition, procurement, professional opinion, emergency command, public warning, or execution, GCRI Canada shall revise, re-scope, add boundary language, restrict release, or correct the material.
5.5.10(h) The controlling rule shall be that Nexus is an architecture of differentiated institutional families; GCRI Canada materials shall preserve that differentiation in every material reference.
5.6 GCRI Canada’s Core Nexus Role
5.6.1 Evidence Doctrine Steward. 5.6.1(a) GCRI Canada shall serve within the Nexus public-good architecture as an evidence doctrine steward. This role shall include the development, maintenance, review, publication, correction, and controlled handoff of evidence concepts, evidence classifications, evidence sufficiency principles, evidence-source expectations, evidence-quality indicators, evidence limitation rules, evidence confidence logic, evidence provenance requirements, evidence-custody expectations, evidence-dispute handling, evidence-correction triggers, and evidence-to-handoff structures for public-good use.
5.6.1(b) Evidence doctrine stewardship shall be upstream, non-executing, and public-benefit. It shall support public authority learning, GRF recognition-related processes, GRA finance-readiness-related processes, Protocol Authority technical-validity processes, Nexus Observatory interpretation, Nexus Grid maturity discipline, Nexus Rails routing, Nexus Academy literacy, regional and national Nexus learning, and enterprise-stack readiness only as evidence support, not as downstream determination.
5.6.1(c) GCRI Canada may define and steward evidence categories for systemic risk, resilience, exponential technologies, AI systems, AI-RAN, O-RAN, private wireless, DePIN, digital twins, cyber systems, compute systems, data systems, sensors, geospatial systems, climate and nature systems, WEFH systems, energy systems, infrastructure systems, biosecurity-relevant systems, advanced manufacturing systems, semiconductor-relevant systems, public authority learning environments, and other Nexus-relevant domains.
5.6.1(d) Evidence doctrine shall require evidence before assertion, source before conclusion, record before effect, limitation before reliance, public-safe classification before release, correction path before publication, and competent-actor action before downstream authority.
5.6.1(e) GCRI Canada shall distinguish evidence from recognition, evidence from finance-readiness, evidence from protocol effect, evidence from certification, evidence from procurement, evidence from public authority decision, evidence from official warning, evidence from emergency command, evidence from professional opinion, evidence from provider endorsement, evidence from sponsor approval, and evidence from execution.
5.6.1(f) Evidence doctrine shall preserve challengeability. Evidence records shall be capable of being questioned, supplemented, corrected, superseded, withdrawn, restricted, reclassified, or routed to competent actors where the record, source, method, confidence, public-safe status, or legal boundary requires.
5.6.1(g) GCRI Canada shall not permit evidence doctrine to be used as hidden certification, hidden recognition, hidden finance-readiness, hidden procurement specification, hidden provider ranking, hidden public authority guidance, hidden professional opinion, hidden protocol effect, or hidden execution instruction.
5.6.1(h) The controlling rule shall be that GCRI Canada stewards evidence doctrine so that truth can be structured, reviewed, routed, and corrected, but evidence doctrine shall not itself become downstream authority.
5.6.2 Methods Steward. 5.6.2(a) GCRI Canada shall serve as a methods steward for the Nexus public-good architecture. This role shall include the development, documentation, versioning, publication, review, challenge, correction, retirement, and controlled reuse of methods used to structure evidence, evaluate sources, interpret observability, compare systems, assess limitations, support public authority learning, support public-safe reporting, support Academy materials, support GRF, support GRA, support Protocol Authority, and support lawful downstream actors within records-valid boundaries.
5.6.2(b) Methods stewardship shall include method libraries, method notes, method profiles, public-safe publication methods, observability methods, benchmarking methods, validation sprint methods, data-governance methods, AI-governance methods, cyber-governance methods, ontology methods, controlled-vocabulary methods, model-governance methods, dataset-governance methods, verifiable compute methods, verifiable intelligence methods, correction methods, and handoff methods.
5.6.2(c) GCRI Canada methods shall be documented with purpose, scope, assumptions, required inputs, prohibited inputs, source expectations, limitations, confidence treatment, review status, public-safe status, version, steward, applicable domain, permitted use, prohibited use, correction path, supersession path, and withdrawal path where material.
5.6.2(d) Methods shall be designed to support comparability, interoperability, transparency where lawful, reproducibility where appropriate, reviewability, proportionality, public-safe publication, privacy protection, cybersecurity, sovereign data compatibility, protected knowledge safeguards, and correctionability.
5.6.2(e) GCRI Canada methods shall not be designed or applied to predetermine outcomes, favour providers, satisfy sponsors, produce finance-signaling claims, steer procurement, imply public authority approval, manufacture certification, manufacture recognition, create protocol effect, suppress inconvenient evidence, or convert technical work into execution.
5.6.2(f) Method reuse by GRF, GRA, Protocol Authority, Nexus bodies, public authorities, National Consortium Companies, Project SPVs, providers, universities, communities, licensed professionals, sponsors, hosts, capital readers, or other actors shall preserve method status, limitations, version, attribution where appropriate, public-safe classification, and downstream actor responsibility.
5.6.2(g) Where a method becomes stale, disputed, misused, overclaimed, technically unsafe, legally unsafe, privacy-risk-bearing, cybersecurity-risk-bearing, finance-overclaiming, provider-preferencing, sponsor-influenced, or public authority-confusing, GCRI Canada shall review, correct, re-scope, withdraw, supersede, or restrict the method.
5.6.2(h) The controlling rule shall be that methods are public-good instruments for disciplined inquiry and correction, not instruments for outcome purchase, authority creation, or execution.
5.6.3 Observability Methods Steward. 5.6.3(a) GCRI Canada shall serve as an observability methods steward within the Nexus architecture. This role shall include the development, review, versioning, documentation, public-safe publication, correction, and controlled handoff of methods for observing, interpreting, and explaining complex systems, infrastructures, hazards, technologies, networks, communities, and resilience conditions without becoming an official warning, emergency command, public authority, infrastructure operator, provider, or execution actor.
5.6.3(b) Observability methods may address nodes, hubs, clusters, hotspots, national dense Nexus cores, regional clusters, sensors, AI-RAN, O-RAN, private wireless, DePIN, digital twins, cyber telemetry, geospatial signals, Earth observation, environmental signals, climate signals, disaster signals, energy systems, water systems, food systems, health-sensitive systems, infrastructure systems, dashboards, maps, APIs, public-safe visualizations, degraded-mode awareness, and resilience indicators.
5.6.3(c) Observability methods shall distinguish signal from conclusion, observation from warning, dashboard from official alert, map from official hazard notice, simulation from reality, scenario from instruction, anomaly from finding, confidence score from rating, and decision-support from decision-making.
5.6.3(d) GCRI Canada may support Nexus Observatory methods and public authority learning through observability logic, signal classification, uncertainty treatment, source-lineage rules, data-quality indicators, sensitive-location controls, privacy-preserving methods, cyber-safe handling, public-safe visualization, and correction triggers.
5.6.3(e) Observability outputs shall not create official public warnings, emergency commands, public authority decisions, regulatory findings, procurement approvals, finance-readiness, certification, recognition, protocol effect, professional opinions, provider endorsements, sponsor approvals, infrastructure-use directives, or execution instructions by default.
5.6.3(f) Observability methods shall be designed with public-safe release controls, including least-exposure publication, sensitive infrastructure protection, protected knowledge protection, Indigenous and local knowledge safeguards, community do-no-harm controls, data minimization, aggregation where appropriate, redaction where appropriate, delayed release where appropriate, and competent authority routing where required.
5.6.3(g) Where observability methods or outputs create public warning confusion, emergency command implication, public authority confusion, finance implication, provider preference, sponsor control, data exposure, cybersecurity risk, protected knowledge exposure, or harmful reliance, GCRI Canada shall restrict, reclassify, correct, withdraw, route, or quarantine the affected method or output.
5.6.3(h) The controlling rule shall be that GCRI Canada may improve the ability to see systems clearly, but it shall not become the actor that commands, warns, regulates, procures, finances, certifies, recognizes, or executes based on that view.
5.6.4 Ontology and Controlled Vocabulary Steward. 5.6.4(a) GCRI Canada shall serve as an ontology and controlled vocabulary steward within the Nexus public-good architecture. This role shall include the development, maintenance, review, versioning, publication, translation, localization, correction, and controlled reuse of taxonomies, controlled terms, schemas, semantic mappings, data dictionaries, evidence categories, risk categories, maturity concepts, public-safe labels, role labels, method labels, proof-input labels, confidence labels, dataset-record labels, model-record labels, benchmark-record labels, system-record labels, and correction-status labels.
5.6.4(b) Ontology and controlled vocabulary stewardship shall preserve semantic precision across GCRI Canada outputs and across interfaces with GRF, GRA, Protocol Authority, Nexus Network, Nexus Universe, Nexus Observatory, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, National Consortium Companies, Project SPVs, public authorities, qualified providers, universities, communities, sponsors, hosts, and capital readers.
5.6.4(c) Controlled vocabulary shall distinguish evidence, method, observability, public-safe report, technical baseline, public-good software, recognition, standing, maturity record, finance-readiness, capital readability, proof pack, insurance-readiness, protocol effect, role key, smart license, proof receipt, public authority learning, public authority decision, certification, validation, verification, testing, benchmarking, public warning, emergency command, procurement, provider neutrality, sponsor non-control, handoff, and execution.
5.6.4(d) Ontology stewardship shall support localization without fragmentation. GCRI Canada may support translations, national profiles, regional profiles, domain profiles, public authority profiles, controlled annexes, and community-sensitive vocabularies, provided that divergences from core terms are recorded, mapped, versioned, limitation-aware, and correctionable.
5.6.4(e) GCRI Canada shall not permit uncontrolled vocabulary, promotional language, sponsor language, provider language, finance language, public authority language, media language, event language, dashboard labels, API fields, repository tags, proof-receipt labels, or Nexus references to create authority beyond record.
5.6.4(f) Ontology and controlled vocabulary shall protect against false maturity, narrative acceleration, role confusion, certification overclaim, recognition overclaim, finance overclaim, protocol overclaim, procurement overclaim, public authority overclaim, provider preference, sponsor control, public-warning confusion, emergency-command confusion, and execution drift.
5.6.4(g) Where vocabulary becomes misleading, stale, ambiguous, mistranslated, overbroad, captured, provider-preferential, sponsor-shaped, finance-signaling, certification-implying, recognition-implying, protocol-implying, procurement-implying, or public authority-confusing, GCRI Canada shall correct, reclassify, revise, supersede, withdraw, or restrict the term or its use.
5.6.4(h) The controlling rule shall be that language is a constitutional infrastructure of truth; GCRI Canada shall steward words as carefully as it stewards records, data, software, and methods.
5.6.5 Technical Truth and Decision-Grade Evidence Architecture Steward. 5.6.5(a) GCRI Canada shall serve as a steward of technical truth and decision-grade evidence architecture within the Nexus public-good stack. This role shall require GCRI Canada to design, maintain, and correct evidence structures capable of supporting serious learning, review, scrutiny, public-safe interpretation, and lawful downstream decision-making by competent actors without becoming the downstream decision-maker.
5.6.5(b) Technical truth shall mean evidence and methods that are source-lined, provenance-bearing, records-valid, confidence-aware, limitation-aware, context-aware, classification-aware, reviewable, challengeable, public-safe where required, correctionable, and resistant to sponsor control, provider preference, finance pressure, public authority confusion, narrative acceleration, technical hallucination, and institutional drift.
5.6.5(c) Decision-grade evidence architecture shall not mean that GCRI Canada makes decisions. It shall mean that GCRI Canada structures evidence in a form that competent external actors may examine, test, compare, challenge, adopt, reject, rely upon, or route through their own lawful processes and records.
5.6.5(d) Decision-grade evidence architecture may include evidence packs, source-lineage records, limitation matrices, confidence logic, corroboration structures, dispute records, uncertainty records, public-safe classifications, data governance records, AI governance records, cyber governance records, model records, dataset records, benchmark records, system records, inference records, proof inputs, technical baseline records, observability records, and correction records.
5.6.5(e) GCRI Canada shall distinguish decision-grade from decision-making. A record may be suitable for serious review by GRF, GRA, Protocol Authority, a public authority, a licensed professional, an enterprise actor, an insurer, a lender, an underwriter, a rating actor, a procurement actor, or another competent actor, but GCRI Canada shall not thereby create the outcome of that actor’s process.
5.6.5(f) Technical truth architecture shall avoid false precision, false certainty, false maturity, overclaim, unsupported extrapolation, unreviewed AI output, stale source reliance, missing limitations, unclassified sensitivity, uncorrectable public claims, and authority-implying display.
5.6.5(g) Where evidence architecture is used downstream, GCRI Canada shall preserve scope limits, non-reliance language where material, public claims controls, data restrictions, public-safe status, correction path, and competent actor responsibility.
5.6.5(h) The controlling rule shall be that GCRI Canada makes evidence fit for disciplined use, not decisions fit for GCRI Canada to impose.
5.6.6 Public-Good R&D Steward. 5.6.6(a) GCRI Canada shall serve as a public-good research and development steward for the Nexus architecture. Its public-good R&D role shall include research, experimentation, investigation, prototyping, testing, benchmarking, technical exploration, method development, observability logic, ontology development, public-good software development, open technical-baseline development, Academy learning support, public authority learning support, and correction-oriented institutional memory.
5.6.6(b) Public-good R&D shall be mission-bounded, non-executing, non-market, non-dealing, non-custodial, non-placement, non-underwriting, non-brokerage, non-advisory, non-clearing, non-settlement, non-insurance, non-bank, non-fund, non-payment-intermediation, non-political, non-sovereign, and separate from enterprise execution.
5.6.6(c) Public-good R&D may address exponential technologies and systemic risks, including AI, AI-RAN, O-RAN, private wireless, blockchain and DLT, DePIN, Web3-relevant systems, quantum-relevant systems, HPC and sovereign compute, cyber, robotics, drones, sensing, Earth observation, geospatial systems, digital twins, biosecurity, climate and nature, water, energy, food, health-related systems, advanced manufacturing, semiconductors, infrastructure resilience, and related technical domains.
5.6.6(d) Public-good R&D shall not be converted into proprietary consultancy, provider delivery, sponsor-controlled research, public authority outsourcing, investment diligence, securities promotion, insurance underwriting, procurement evaluation, certification, recognition, protocol authority, professional regulated opinion, public warning, emergency command, or execution.
5.6.6(e) Public-good R&D shall preserve research integrity, including question integrity, method integrity, data integrity, source integrity, negative or inconclusive result integrity, publication independence, correction independence, conflict management, public-safe release, protected knowledge safeguards, privacy, cybersecurity, and lawful cross-border controls.
5.6.6(f) R&D outputs may include prototypes, reference implementations, methods, technical notes, datasets, benchmark libraries, model records, software components, dashboards, maps, simulations, public-safe reports, controlled annexes, Academy materials, and correction records, but such outputs shall remain boundary-labeled and non-executing.
5.6.6(g) Where public-good R&D produces materials relevant to GRF, GRA, Protocol Authority, public authorities, enterprise-stack actors, providers, sponsors, universities, communities, or capital readers, GCRI Canada shall use records-valid handoff, scope limits, public-safe classification, and correction paths.
5.6.6(h) The controlling rule shall be that public-good R&D creates shared technical capacity and learning, not private control or downstream authority.
5.6.7 Public-Good Software and Open Technical Baseline Steward. 5.6.7(a) GCRI Canada shall serve as a steward of public-good software and open technical baselines within the Nexus public-good architecture. This role shall include developing, maintaining, documenting, licensing, securing, versioning, releasing, correcting, deprecating, and retiring reusable technical assets that support evidence, methods, observability, ontology, technical truth, public-safe publication, public authority learning, Nexus interoperability, and correctionability.
5.6.7(b) Public-good software may include APIs, dashboards, data tools, test harnesses, evaluation harnesses, reference implementations, schema libraries, ontology tools, evidence tools, model-governance tools, dataset-governance tools, benchmark tools, inference-record tools, proof-input tools, observability tools, public-safe visualization tools, repository tools, correction tools, and documentation.
5.6.7(c) Open technical baselines may include reference architectures, open technical profiles, schemas, API patterns, interoperability profiles, evidence requirements, data-governance patterns, AI-governance patterns, cyber-governance patterns, observability patterns, technical documentation, secure release practices, and conformance-supporting instruments.
5.6.7(d) GCRI Canada’s stewardship of public-good software and technical baselines shall not create certification, protocol effect, procurement specification, provider endorsement, public authority approval, finance-readiness, insurance-readiness, recognition, professional opinion, public warning, emergency command, operational approval, or execution authority by default.
5.6.7(e) Public-good software and open technical baselines shall be governed against enclosure, vendor lock-in, sponsor control, hidden dependencies, insecure dependencies, unreviewable AI dependencies, cloud capture, repository capture, package-channel capture, API control, license incompatibility, public-safe release failure, data leakage, cybersecurity weakness, and correction constraints.
5.6.7(f) Public-good software releases shall identify license, steward, version, intended use, prohibited use, support status, security status where material, data status, AI-use status, dependency status, non-warranty language, non-certification status, non-protocol-effect status, non-procurement status, non-finance status, public-safe classification, correction path, deprecation path, and withdrawal path where material.
5.6.7(g) Technical baseline reuse by public authorities, providers, National Consortium Companies, Project SPVs, GRF, GRA, Protocol Authority, Nexus bodies, universities, sponsors, hosts, or capital readers shall preserve role boundaries, source status, version status, limitations, public claims limits, and correction obligations.
5.6.7(h) The controlling rule shall be that public-good software and technical baselines shall support interoperable public-good capacity, not private capture, provider preference, procurement steering, certification, protocol effect, or execution.
5.6.8 Nexus Truth Engine Methods Steward. 5.6.8(a) GCRI Canada shall serve as a steward of Nexus Truth Engine methods within its own institutional perimeter and within the broader Nexus public-good architecture. This stewardship shall concern methods for evidence intake, source lining, provenance review, corroboration, confidence treatment, dispute handling, limitation identification, contradiction handling, uncertainty treatment, correction triggering, supersession, withdrawal, public-safe classification, and handoff-ready truth structuring.
5.6.8(b) Nexus Truth Engine methods shall not create a machine authority, AI authority, dashboard authority, public authority decision, finance-readiness determination, certification, recognition, protocol effect, public warning, emergency command, professional opinion, procurement decision, provider endorsement, sponsor approval, or execution consequence by default.
5.6.8(c) Nexus Truth Engine methods may be supported by AI tools, models, retrieval systems, knowledge graphs, ontologies, confidence logic, dashboards, proof receipts, tamper-evident records, dataset records, model records, benchmark records, system records, inference records, and human review workflows, but the presence of such tools shall not displace human review, competent authority, public-safe release, or correctionability where material.
5.6.8(d) GCRI Canada shall ensure that Nexus Truth Engine methods distinguish source record from conclusion, machine output from reviewed finding, evidence confidence from legal or financial rating, proof receipt from truth, dashboard state from authority, model inference from fact, and public-safe report from official action.
5.6.8(e) Truth Engine methods shall include controls for hallucination, stale source reliance, source conflict, model bias where material, missing context, adversarial input, spoof signals, synthetic data, DePIN signal distortion, blockchain overclaim, dashboard overclaim, public authority overclaim, finance overclaim, provider overclaim, sponsor overclaim, and correction latency.
5.6.8(f) Truth Engine method records shall identify method, source categories, review status, automation level, human review requirement, confidence treatment, limitation treatment, public-safe classification, data restrictions, AI-use restrictions, cybersecurity controls, correction path, supersession path, and prohibited interpretations.
5.6.8(g) Where Nexus Truth Engine methods or outputs are routed to GRF, GRA, Protocol Authority, public authorities, Nexus bodies, National Consortium Companies, Project SPVs, qualified providers, licensed professionals, sponsors, hosts, universities, communities, or capital readers, records shall preserve the distinction between truth support and downstream effect.
5.6.8(h) The controlling rule shall be that the Nexus Truth Engine supports disciplined truth construction and correction; it shall not become an authority engine.
5.6.9 Nexus Observatory Methods Steward. 5.6.9(a) GCRI Canada shall serve as a steward of Nexus Observatory methods within its own institutional perimeter and in support of the broader Nexus public-good architecture. This role shall include methods for observing, structuring, interpreting, displaying, reviewing, public-safe releasing, correcting, and handing off system signals, resilience indicators, risk signals, sensor signals, AI-RAN signals, DePIN signals, digital twin outputs, geospatial outputs, cyber indicators, infrastructure indicators, and community-relevant observability records.
5.6.9(b) Nexus Observatory methods may address nodes, hubs, clusters, hotspots, national dense Nexus cores, regional clusters, sensors, AI-RAN, O-RAN, private wireless, edge compute, sovereign compute, DePIN, digital twins, dashboards, maps, APIs, public authority learning rooms, public-safe reports, and controlled annexes.
5.6.9(c) GCRI Canada shall steward Observatory methods as non-warning, non-command, non-regulatory, non-procurement, non-finance, non-certification, non-recognition, non-protocol-effect, non-professional-opinion, non-provider-endorsement, non-sponsor-controlled, and non-executing unless a competent external actor separately creates its own lawful effect.
5.6.9(d) Observatory methods shall distinguish live signal from verified condition, signal confidence from official finding, map layer from official hazard notice, dashboard state from public warning, digital twin from actual system state, AI output from reviewed record, DePIN record from public authority evidence, and observability from operational control.
5.6.9(e) Observatory methods shall incorporate public-safe release, privacy, cybersecurity, sovereign data, Indigenous and local knowledge safeguards, protected knowledge safeguards, sensitive infrastructure controls, health-sensitive data controls, community do-no-harm controls, least-exposure publication, aggregation, redaction, access restriction, and competent authority routing where material.
5.6.9(f) GCRI Canada may support Nexus Observatory nodes, hubs, clusters, hotspots, national dense cores, regional clusters, sensors, AI-RAN, DePIN, digital twins, dashboards, and public-safe evidence outputs through methods, not by default through ownership, operation, emergency command, official public warning, infrastructure operation, or field execution.
5.6.9(g) Where Observatory methods or outputs create public warning confusion, emergency command confusion, public authority confusion, finance implication, procurement implication, certification implication, recognition implication, protocol implication, provider preference, sponsor control, data exposure, cybersecurity exposure, protected knowledge exposure, or harmful reliance, GCRI Canada shall restrict, relabel, reclassify, route, correct, withdraw, or quarantine.
5.6.9(h) The controlling rule shall be that GCRI Canada may steward how systems are observed and interpreted, but not become the authority that commands action based on those observations.
5.6.10 Verifiable Compute and Verifiable Intelligence Methods Steward. 5.6.10(a) GCRI Canada shall serve as a steward of verifiable compute and verifiable intelligence methods within its Nexus role. This stewardship shall include methods for documenting compute workloads, model use, dataset use, inference events, benchmark conditions, system configurations, provenance, custody, integrity, reproducibility where appropriate, tamper-evidence, source-lineage, public-safe classification, human review, and correction paths.
5.6.10(b) Verifiable compute methods may include compute workload records, environment records, configuration records, dependency records, model execution records, dataset access records, benchmark execution records, hardware or cloud context records where material, secure release records, vulnerability records, proof inputs, hashes, signatures, and audit-supporting records.
5.6.10(c) Verifiable intelligence methods may include model cards, dataset cards, system cards, benchmark cards, inference records, prompt or input records where appropriate and lawful, output records, confidence treatment, limitation statements, human review status, AI-use restrictions, public-safe classification, correction records, and supersession records.
5.6.10(d) Verifiable compute and verifiable intelligence records shall not create legal authority, public authority meaning, finance-readiness, investment advice, insurance approval, underwriting, rating, certification, recognition, protocol effect, procurement approval, provider endorsement, sponsor approval, professional opinion, public warning, emergency command, operational control, or execution consequence by default.
5.6.10(e) GCRI Canada shall distinguish verification of process, provenance, custody, configuration, timing, or integrity from verification of substantive truth, safety, legality, compliance, public authority approval, finance quality, provider quality, market readiness, certification status, recognition status, protocol status, or execution readiness.
5.6.10(f) Verifiable compute and intelligence methods shall include controls for privacy, rights-bearing data, public authority data, sovereign data, protected knowledge, sensitive infrastructure, cyber-sensitive information, export-control sensitivity, sanctions sensitivity, controlled technology, model-provider retention, training restrictions, prompt leakage, inference leakage, and public-safe release.
5.6.10(g) Where verifiable compute or intelligence artifacts are used in GRF, GRA, Protocol Authority, public authority, enterprise, provider, sponsor, finance, insurance, procurement, professional, or Nexus contexts, GCRI Canada shall preserve record limits, prohibited interpretations, boundary language, competent actor responsibility, and correction paths.
5.6.10(h) The controlling rule shall be that verifiability strengthens records and accountability, but it shall not itself create downstream authority.
5.6.11 Data / AI / Cyber Safeguards Steward Within Its Own Institutional Perimeter. 5.6.11(a) GCRI Canada shall serve as a steward of data, AI, and cybersecurity safeguards within its own institutional perimeter. This role shall include establishing, maintaining, reviewing, correcting, and enforcing safeguards for data access, data classification, lawful basis, permitted use, prohibited use, privacy, rights-bearing data, sovereign data, public authority data, Indigenous knowledge, local knowledge, protected knowledge, health-sensitive data, cyber-sensitive information, sensitive infrastructure information, controlled technology, AI tool use, model governance, secure collaboration, repository security, software security, dashboard security, and incident response.
5.6.11(b) GCRI Canada’s data, AI, and cyber safeguards role shall not make it a regulator, data protection authority, cybersecurity regulator, law enforcement actor, public authority, public warning authority, emergency command body, professional cybersecurity assurance provider, certification body, or infrastructure operator by default.
5.6.11(c) Data safeguards shall require classification, minimization, lawful basis, authority to contribute, purpose limitation, access control, retention control, cross-border review, sovereign data compatibility, compute-to-data where appropriate, publication review, correction path, and deletion or restriction where required.
5.6.11(d) AI safeguards shall require input controls, model-provider review where material, retention restrictions, training restrictions, retrieval-source controls, hallucination review, bias and limitation review where material, human review where material, inference records, output limits, public-safe review, and AI-as-authority controls.
5.6.11(e) Cyber safeguards shall require authentication, authorization, least privilege, logging where appropriate, secrets management, vulnerability management, dependency review, repository protection, secure release, incident escalation, evidence preservation, backup and recovery where appropriate, access review, and public-safe disclosure handling.
5.6.11(f) GCRI Canada shall apply heightened safeguards where materials involve public authorities, vulnerable communities, Indigenous or local knowledge, protected knowledge, sensitive infrastructure, cyber-sensitive systems, health-sensitive information, controlled technologies, export-control risk, sanctions-sensitive actors, cross-border transfer, or public-facing dashboards and maps.
5.6.11(g) Where data, AI, or cyber safeguard risk arises, GCRI Canada shall restrict access, pause processing, quarantine outputs, disable systems, reclassify materials, notify affected actors where appropriate, correct records, route to competent actors, seek legal or technical review, and preserve incident or correction records.
5.6.11(h) The controlling rule shall be that GCRI Canada safeguards the systems it stewards; it does not become the public regulator of all systems it studies.
5.6.12 Research Integrity, Public-Safe Publication, and Correctionability Steward. 5.6.12(a) GCRI Canada shall serve as a steward of research integrity, public-safe publication, and correctionability within its Nexus role. This stewardship shall apply to research outputs, methods, evidence records, observability outputs, ontologies, technical baselines, public-good software, dashboards, maps, datasets, model records, benchmark records, system records, inference records, proof inputs, public-safe reports, controlled annexes, Academy materials, public authority learning materials, GRA inputs, GRF inputs, Protocol Authority inputs, and Nexus materials.
5.6.12(b) Research integrity shall require independence of inquiry, method discipline, evidence discipline, limitation disclosure, conflict management, negative and inconclusive result integrity, sponsor non-control, provider neutrality, publication independence, correction independence, source-lineage integrity, data integrity, AI-use integrity, cybersecurity integrity, and protection against capture, enclosure, drift, and substitution.
5.6.12(c) Public-safe publication shall require that outputs be reviewed for lawful release, privacy, rights-bearing data protection, public authority data limits, sovereign data compatibility, Indigenous and local knowledge safeguards, protected knowledge, sensitive infrastructure, cyber-sensitive information, health-sensitive data, controlled technology, export-control and sanctions sensitivity, community do-no-harm, public warning confusion, emergency command confusion, finance overclaim, procurement implication, certification implication, recognition implication, protocol implication, provider preference, sponsor control, and execution implication.
5.6.12(d) Correctionability shall require that GCRI Canada outputs remain challengeable, reviewable, correctable, supersedable, withdrawable, retractable where necessary, and capable of public-safe clarification. Correctionability shall not be defeated by publication, dashboard display, repository release, proof receipt, blockchain anchor, hash, AI output, public authority circulation, sponsor reuse, provider reuse, finance-facing reuse, media reuse, or Nexus circulation.
5.6.12(e) GCRI Canada shall maintain correction records, supersession records, withdrawal records, retraction records, closeout records, downstream dependency reviews, public-safe correction notices, controlled correction notices, and prevention measures for material errors, overclaims, ambiguity, boundary confusion, public-safe issues, or technical defects.
5.6.12(f) Where research integrity, public-safe publication, or correctionability conflicts with speed, convenience, funding, sponsor expectation, provider expectation, public authority interest, capital-reader interest, media timing, event schedule, technical readiness, or Nexus visibility, research integrity, public-safe publication, and correctionability shall prevail.
5.6.12(g) GCRI Canada shall train directors, officers, staff, contractors, fellows, advisors, council participants, researchers, technical contributors, sponsors, providers, public authority participants, and other relevant actors in research integrity, public-safe publication, controlled vocabulary, boundary language, correction duties, and escalation.
5.6.12(h) The controlling rule shall be that GCRI Canada’s Nexus role is credible only if its research is independent, its publications are public-safe, and its records remain correctable.
5.7 What GCRI Canada Contributes to Nexus
5.7.1 Evidence Models, Evidence Categories, Evidence Records, Evidence Packs, and Evidence Quality Methods. 5.7.1(a) GCRI Canada may contribute to Nexus evidence models, evidence categories, evidence records, evidence packs, and evidence quality methods that enable evidence to be structured, source-lined, reviewed, challenged, corrected, routed, and understood across the Nexus public-good architecture.
5.7.1(b) Evidence models may include structures for identifying sources, provenance, custody, confidence, uncertainty, limitations, evidence gaps, corroboration status, dispute status, review status, public-safe classification, data classification, sensitivity, lawful-use conditions, downstream handoff status, correction path, supersession path, withdrawal path, and competent actor relevance.
5.7.1(c) Evidence categories may include technical evidence, scientific evidence, observational evidence, public authority evidence, community evidence, Indigenous and local knowledge-sensitive evidence, sensor evidence, AI-RAN evidence, DePIN evidence, digital twin evidence, cyber evidence, geospatial evidence, climate evidence, infrastructure evidence, resilience evidence, host-readiness evidence, node evidence, model evidence, dataset evidence, benchmark evidence, system evidence, and public-safe evidence.
5.7.1(d) Evidence records and evidence packs may be prepared for public authority learning, GRF inputs, GRA inputs, Protocol Authority inputs, Nexus Observatory interpretation, Nexus Grid maturity discipline, Nexus Rails routing, Nexus Academy learning, National Consortium Company readiness, Project SPV readiness, provider-neutral technical review, and public-safe publication, provided that such records remain non-executing, limitation-aware, and boundary-labeled.
5.7.1(e) Evidence quality methods may address source reliability, chain of custody, replication, triangulation, confidence treatment, dispute handling, stale-source treatment, model-derived evidence treatment, AI-assisted evidence treatment, adversarial evidence risk, synthetic evidence risk, spoof signal risk, incomplete evidence, conflicting evidence, and correction triggers.
5.7.1(f) GCRI Canada evidence contributions shall not constitute recognition, standing, maturity records, finance-readiness, investment advice, insurance-readiness, underwriting approval, rating, public finance approval, certification, procurement approval, protocol effect, professional opinion, public authority decision, public warning, emergency command, provider endorsement, sponsor approval, or execution instruction by default.
5.7.1(g) Evidence contributions shall preserve the distinction between evidence and effect. Any downstream effect shall require the proper actor, proper role, proper authority, proper review, proper legal basis, and proper record.
5.7.1(h) The controlling rule shall be that GCRI Canada contributes evidence architecture to Nexus so that truth may be used responsibly by others, not so that GCRI Canada becomes the decision-maker.
5.7.2 Methods, Method Libraries, Method Profiles, Validation Logic, Confidence Logic, and Uncertainty Logic. 5.7.2(a) GCRI Canada may contribute methods, method libraries, method profiles, validation logic, confidence logic, uncertainty logic, limitation logic, challenge logic, correction logic, and handoff logic to the Nexus public-good architecture.
5.7.2(b) Method libraries may include repeatable approaches for evidence intake, evidence review, source assessment, technical assessment, observability interpretation, dashboard interpretation, map interpretation, public-safe publication, AI governance, dataset governance, model governance, cyber review, benchmark design, validation sprint design, public authority learning, community safeguard review, and protected knowledge handling.
5.7.2(c) Method profiles shall identify purpose, scope, domain, assumptions, required inputs, prohibited inputs, source requirements, review requirements, automation level, human review requirements, data restrictions, public-safe classification, limitations, expected outputs, prohibited interpretations, correction path, supersession path, withdrawal path, and downstream handoff relevance.
5.7.2(d) Validation logic may support review of whether evidence, methods, datasets, models, systems, software, dashboards, technical baselines, or observability outputs meet defined internal evidence or method conditions within a stated scope, but shall not create certification, regulatory approval, procurement approval, finance-readiness, recognition, protocol effect, public authority approval, professional opinion, or deployment approval by default.
5.7.2(e) Confidence logic shall support disciplined expression of confidence, uncertainty, corroboration, limitation, dispute, unresolved gaps, and review status. Confidence logic shall not be used as a credit rating, investment rating, insurance rating, public warning level, certification status, public authority determination, procurement ranking, provider score, or execution signal by default.
5.7.2(f) Uncertainty logic shall require GCRI Canada to state what is known, what is not known, what is disputed, what is stale, what is model-dependent, what is source-limited, what is jurisdiction-specific, what is public-safe-limited, and what requires competent external review.
5.7.2(g) Methods shall be versioned, reviewable, challengeable, correctable, public-safe where required, and protected against sponsor influence, provider preference, finance pressure, procurement steering, public authority confusion, and technical drift.
5.7.2(h) The controlling rule shall be that GCRI Canada contributes methods to improve disciplined interpretation, not to predetermine outcomes or create authority.
5.7.3 Observability Architecture, Sensor Evidence Methods, AI-RAN Signal Methods, DePIN Evidence Methods, Digital Twin Assumption Methods, and Cyber Telemetry Methods. 5.7.3(a) GCRI Canada may contribute observability architecture, sensor evidence methods, AI-RAN signal methods, O-RAN and private wireless signal methods, DePIN evidence methods, digital twin assumption methods, cyber telemetry methods, geospatial interpretation methods, dashboard methods, map methods, degraded-mode awareness methods, and resilience indicator methods to Nexus.
5.7.3(b) Observability architecture may support the interpretation of nodes, hubs, clusters, hotspots, national dense Nexus cores, regional clusters, sensors, edge systems, AI-RAN, O-RAN, private wireless, DePIN, digital twins, cyber systems, energy systems, water systems, food systems, health-sensitive systems, climate systems, biodiversity systems, infrastructure systems, and public-safe dashboards.
5.7.3(c) Sensor evidence methods shall address source identity, calibration, custody, reliability, latency, coverage, resolution, missing data, spoof risk, tamper risk, drift, environmental context, public-safe status, privacy risk, sensitive infrastructure exposure, community risk, and correction path.
5.7.3(d) AI-RAN signal methods shall address signal source, network context, edge compute context, model use, inference status, signal confidence, latency, anomaly treatment, degraded-mode conditions, security posture, data minimization, public authority relevance, public-safe visualization, and non-warning boundary language.
5.7.3(e) DePIN evidence methods shall address decentralized source integrity, node identity, incentive distortion, spoof signals, device trust, chain anchoring, off-chain evidence, custody, aggregation, uncertainty, public-safe release, privacy, cybersecurity, and correctionability.
5.7.3(f) Digital twin assumption methods shall identify assumptions, model boundaries, data sources, calibration status, scenario status, uncertainty, sensitivity, update frequency, validation limits, public-safe status, and the distinction between simulation and actual condition.
5.7.3(g) Cyber telemetry methods shall address logs, events, vulnerabilities, anomalous behavior, dependency risk, access-control events, incident indicators, source reliability, severity where appropriate, disclosure restrictions, public-safe handling, and the distinction between cybersecurity observation and law enforcement or regulatory finding.
5.7.3(h) GCRI Canada observability contributions shall not become public warnings, emergency commands, public authority findings, regulatory determinations, procurement decisions, finance-readiness determinations, certification, recognition, protocol effect, professional opinions, provider endorsements, sponsor approvals, or execution instructions by default.
5.7.3(i) The controlling rule shall be that GCRI Canada may help Nexus see complex systems more clearly, but seeing shall not become commanding, warning, approving, financing, certifying, recognizing, procuring, or executing.
5.7.4 Ontologies, Taxonomies, Schemas, Data Dictionaries, Controlled Vocabularies, Semantic Mappings, and AI-Readable Knowledge Structures. 5.7.4(a) GCRI Canada may contribute ontologies, taxonomies, schemas, data dictionaries, controlled vocabularies, semantic mappings, AI-readable knowledge structures, graph structures, metadata models, classification rules, status labels, public-safe labels, and correction labels to Nexus.
5.7.4(b) Such contributions shall support shared meaning across GCRI Canada, GRF, GRA, Protocol Authority, Nexus Network, Nexus Universe, Nexus Observatory, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, National Consortium Companies, Project SPVs, public authorities, qualified providers, universities, communities, sponsors, hosts, and capital readers.
5.7.4(c) Controlled vocabularies shall define and distinguish core Nexus terms, including evidence, method, observability, ontology, technical baseline, public-good software, public-safe report, recognition, standing, maturity record, finance-readiness, capital readability, proof pack, insurance-readiness, protocol effect, role key, smart license, proof receipt, validation, verification, testing, benchmarking, certification, public authority learning, public authority decision, public warning, emergency command, procurement, provider neutrality, sponsor non-control, handoff, and execution.
5.7.4(d) Schemas and data dictionaries may define fields, statuses, classifications, evidence categories, source fields, limitation fields, confidence fields, public-safe fields, review-status fields, correction fields, access fields, role fields, handoff fields, and prohibited-interpretation fields necessary for interoperable records.
5.7.4(e) Semantic mappings may connect local, regional, national, sectoral, domain-specific, multilingual, public authority, Indigenous or local knowledge-sensitive, and technical terms to common Nexus vocabulary without erasing context, sovereignty, lawful variation, or protected knowledge restrictions.
5.7.4(f) AI-readable knowledge structures may support retrieval, classification, reasoning support, source linking, evidence comparison, confidence treatment, and correction triage, but shall not create AI authority, automated public authority meaning, automated certification, automated recognition, automated finance-readiness, automated procurement, or automated protocol effect by default.
5.7.4(g) Ontology and schema contributions shall be versioned, records-valid, public-safe where required, reviewed for bias and ambiguity where material, secured where necessary, and correctionable.
5.7.4(h) The controlling rule shall be that GCRI Canada contributes shared meaning to Nexus while preventing words, labels, fields, or machine-readable structures from silently creating authority.
5.7.5 Public-Good Software, APIs, Dashboards, Data Tools, Reference Implementations, Open Technical Baselines, and Evaluation Harnesses. 5.7.5(a) GCRI Canada may contribute public-good software, APIs, dashboards, data tools, reference implementations, open technical baselines, test harnesses, evaluation harnesses, reference architectures, documentation, package releases, repository structures, and conformance-supporting instruments to Nexus.
5.7.5(b) Public-good software contributions may support evidence intake, source lining, data classification, public-safe review, dashboard visualization, map generation, benchmark execution, model recordkeeping, dataset recordkeeping, system recordkeeping, inference recordkeeping, proof-input structuring, correction management, repository discipline, and secure collaboration.
5.7.5(c) APIs and data tools may support interoperability among Nexus actors by enabling structured records, permitted exchanges, classification-aware transfer, correction propagation, public-safe publication, and handoff workflows, but shall not create public authority action, finance action, procurement action, certification, recognition, protocol effect, or execution by default.
5.7.5(d) Dashboards contributed by GCRI Canada shall be designed as evidence, observability, learning, and interpretation tools, not as official warning systems, emergency command systems, public authority decision systems, procurement systems, finance approval systems, certification registries, recognition registries, protocol entitlement systems, provider ranking systems, or execution control systems by default.
5.7.5(e) Reference implementations shall demonstrate possible technical patterns, interoperability, data structures, security approaches, public-safe display, correction flows, or baseline implementation logic without becoming required vendor products, procurement specifications, deployment approvals, certification requirements, protocol entitlements, or operational instructions by default.
5.7.5(f) Open technical baselines and evaluation harnesses may support quality, comparability, interoperability, testing, benchmarking, and readiness understanding, but passing, aligning, integrating, or participating shall not create certification, recognition, finance-readiness, procurement approval, provider endorsement, public authority approval, protocol effect, or execution authorization by default.
5.7.5(g) Technical contributions shall include license status, version, maintainer, security status where material, dependency status, permitted use, prohibited use, public-safe classification, data restrictions, AI-use restrictions, non-warranty language, non-certification language, non-protocol-effect language, non-procurement language, non-finance language, correction path, deprecation path, and withdrawal path where material.
5.7.5(h) The controlling rule shall be that GCRI Canada contributes public-good technical capacity to Nexus, but technical capacity shall not become hidden control, private enclosure, vendor preference, or execution authority.
5.7.6 Research Outputs, Technical Notes, Public-Safe Reports, Controlled Annexes, Academy Materials, and Technical Training Materials. 5.7.6(a) GCRI Canada may contribute research outputs, technical notes, public-safe reports, controlled annexes, Academy materials, technical training materials, evidence literacy materials, public authority learning materials, cyber literacy materials, AI literacy materials, data literacy materials, observability literacy materials, and technical-baseline learning materials to Nexus.
5.7.6(b) Research outputs may include findings, hypotheses, methods, evidence summaries, literature syntheses, technical analyses, gap maps, benchmark notes, validation sprint notes, observability reviews, ontology notes, software notes, public-safe summaries, and correction records.
5.7.6(c) Technical notes may explain methods, assumptions, limitations, technical baselines, software releases, data structures, AI-use controls, cyber controls, observability signals, dashboards, maps, public-safe release logic, and correction procedures.
5.7.6(d) Public-safe reports shall present information in a manner suitable for the intended audience while protecting privacy, rights-bearing data, sovereign data, public authority data, Indigenous knowledge, local knowledge, protected knowledge, health-sensitive data, cyber-sensitive information, sensitive infrastructure, controlled technology, export-control sensitivity, sanctions sensitivity, community safeguards, and public trust.
5.7.6(e) Controlled annexes may contain sensitive, restricted, confidential, privileged, public authority-restricted, finance-sensitive, cyber-sensitive, protected-knowledge-sensitive, or technical materials whose release requires access controls, permitted-use limits, onward-sharing limits, and correction paths.
5.7.6(f) Academy materials and technical training materials may support public authority learning, workforce development, evidence literacy, technical literacy, public-good software literacy, AI literacy, cyber literacy, data literacy, observability literacy, controlled vocabulary, and boundary literacy, but shall not constitute regulated certification, professional licensure, public authority guidance, provider endorsement, finance-readiness, or execution training by default.
5.7.6(g) All such materials shall identify issuer, scope, audience, review status, public-safe classification, limitations, required disclaimers, prohibited interpretations, correction path, supersession path, and withdrawal path where material.
5.7.6(h) The controlling rule shall be that GCRI Canada contributes learning and public-safe knowledge to Nexus, not official authority, professional advice, market approval, or execution consequence.
5.7.7 Dataset Cards, Model Cards, System Cards, Benchmark Cards, Model Registers, Compute Workload Records, Inference Records, and Verifiable Intelligence Records. 5.7.7(a) GCRI Canada may contribute dataset cards, model cards, system cards, benchmark cards, model registers, compute workload records, inference records, verifiable intelligence records, evaluation records, configuration records, dependency records, environment records, and AI-use records to Nexus.
5.7.7(b) Dataset cards may identify dataset source, provenance, lawful basis where applicable, permitted use, prohibited use, data subjects or affected communities where appropriate, sensitivity, rights-bearing data status, sovereign data status, public authority data status, protected knowledge status, collection method, coverage, limitations, bias risks where material, update status, access controls, retention, transfer limits, and correction path.
5.7.7(c) Model cards may identify model purpose, architecture where appropriate, source, provider, version, training data summary where available and lawful, intended use, prohibited use, limitations, risks, evaluation results, human review requirements, input restrictions, output limits, retention restrictions, public-safe status, and correction path.
5.7.7(d) System cards may identify system purpose, components, dependencies, data flows, user roles, authority limits, security controls, privacy controls, AI-use controls, public-safe controls, public authority boundaries, finance boundaries, procurement boundaries, certification boundaries, protocol boundaries, and correction paths.
5.7.7(e) Benchmark cards may identify benchmark purpose, method, dataset, configuration, assumptions, limitations, sponsor or provider involvement where material, reproducibility status, public-safe status, result interpretation limits, non-certification status, non-procurement status, non-finance status, and correction path.
5.7.7(f) Compute workload records and inference records may identify environment, workload, model, dataset, prompt or input category where appropriate and lawful, output category, time, configuration, access, human review status, confidence treatment, limitation treatment, retention, public-safe classification, and correction path.
5.7.7(g) Verifiable intelligence records shall support auditability, traceability, source lineage, custody, integrity, human review, limitation disclosure, and correction, but shall not create legal authority, public authority meaning, finance-readiness, investment advice, insurance approval, underwriting, rating, certification, recognition, protocol effect, procurement approval, provider endorsement, professional opinion, public warning, emergency command, or execution consequence by default.
5.7.7(h) The controlling rule shall be that GCRI Canada contributes verifiable intelligence records so that AI-supported work can be inspected and corrected, not so that AI outputs become authority.
5.7.8 Secure Release Practices, Repository Discipline, SBOM, Key Management, Vulnerability Management, and Technical Asset Correction. 5.7.8(a) GCRI Canada may contribute secure release practices, repository discipline, software bill of materials practices, key management practices, vulnerability management practices, dependency review practices, release-channel discipline, package-channel discipline, access-control practices, documentation practices, and technical asset correction methods to Nexus.
5.7.8(b) Secure release practices may include release authorization, code review, dependency review, vulnerability review, secrets scanning, SBOM preparation where appropriate, license review, data leakage review, model leakage review, public-safe review, versioning, changelog discipline, deprecation planning, rollback planning, and correction path documentation.
5.7.8(c) Repository discipline may include role-based access, branch protection where appropriate, maintainer rules, contribution rules, issue handling, pull-request review, release tagging, archive procedures, license labeling, security notices, public claims limits, documentation requirements, correction records, supersession records, and withdrawal records.
5.7.8(d) SBOM practices may identify software components, dependencies, versions, licenses, known vulnerabilities where material, provenance, maintainer responsibility, release scope, update requirements, and downstream user responsibilities.
5.7.8(e) Key management practices may address signing, verification, access credentials, secrets handling, rotation, revocation, custody, auditability where appropriate, incident response, and correction of compromised or stale credentials.
5.7.8(f) Vulnerability management may include intake, triage, severity assessment where appropriate, disclosure controls, affected-component review, remediation, release notes, public-safe notification, dependency updates, patching, withdrawal, supersession, and incident records.
5.7.8(g) Technical asset correction shall ensure that software, APIs, dashboards, maps, datasets, schemas, ontologies, technical baselines, proof receipts, model records, dataset records, benchmark records, and public-good tools remain correctable even after release, reuse, embedding, quotation, proofing, hashing, or downstream circulation.
5.7.8(h) Secure release, repository discipline, SBOM, key management, vulnerability management, and technical asset correction shall not constitute certification, cybersecurity assurance, public authority approval, procurement approval, finance-readiness, insurance approval, underwriting, rating, provider endorsement, protocol effect, or execution authorization by default.
5.7.8(i) The controlling rule shall be that GCRI Canada contributes trustworthy technical stewardship practices, not regulated assurance or execution authority.
5.7.9 Privacy, Data Rights, Sovereign Data, Compute-to-Data, Cross-Border Data, and Public-Safe Handling Methods. 5.7.9(a) GCRI Canada may contribute privacy, data rights, sovereign data, compute-to-data, cross-border data, public-safe handling, data minimization, access-control, retention, transfer, publication, and correction methods to Nexus.
5.7.9(b) Privacy and data rights methods shall address personal information, rights-bearing data, affected communities, consent where applicable, lawful basis, purpose limitation, minimization, access restriction, retention, accuracy, correction, deletion, portability where applicable, publication risk, AI-use limits, and onward-use restrictions.
5.7.9(c) Sovereign data methods shall address national, Indigenous, local, community, public authority, sensitive infrastructure, and jurisdictional data controls, including authority to contribute, custody, localization, permitted use, public-safe release, cross-border review, compute-to-data approaches, and data sovereignty compatibility.
5.7.9(d) Compute-to-data methods may support analysis without unnecessary transfer, exposure, extraction, or duplication of sensitive data, and may include controlled environments, role-based access, logging where appropriate, output review, public-safe release, and correction pathways.
5.7.9(e) Cross-border data methods shall address jurisdiction, lawful transfer basis, data classification, recipient capacity, public authority restrictions, export-control considerations, sanctions considerations, controlled technology, privacy obligations, cybersecurity obligations, sovereign data restrictions, protected knowledge safeguards, and public-safe publication limits.
5.7.9(f) Public-safe handling methods shall address classification, redaction, aggregation, generalization, delay, controlled annex treatment, restricted access, community safeguard review, Indigenous and protected knowledge review, sensitive infrastructure protection, cyber-sensitive handling, health-sensitive handling, and correction.
5.7.9(g) GCRI Canada’s data-handling methods shall not make it a public authority, data protection authority, cybersecurity regulator, law enforcement actor, public warning authority, emergency command body, professional adviser, provider, processor for all Nexus actors, or execution operator by default.
5.7.9(h) The controlling rule shall be that GCRI Canada contributes data safeguard methods to make Nexus safer and more trustworthy, not to expand its own authority over data or downstream decisions.
5.7.10 Public Authority Learning Materials, Evidence Literacy Materials, and Technical Literacy Materials. 5.7.10(a) GCRI Canada may contribute public authority learning materials, evidence literacy materials, technical literacy materials, AI literacy materials, cyber literacy materials, data literacy materials, observability literacy materials, public-safe publication materials, controlled vocabulary materials, and boundary literacy materials to Nexus.
5.7.10(b) Public authority learning materials may help public authorities, public institutions, public-sector participants, and public-serving actors understand evidence, methods, technical baselines, AI systems, cyber systems, observability systems, dashboards, maps, public-safe reports, data safeguards, public-good software, correctionability, and role separation.
5.7.10(c) Evidence literacy materials may explain source lineage, provenance, confidence, uncertainty, limitations, corroboration, evidence gaps, dispute handling, model-derived evidence, AI-assisted outputs, public-safe classification, and correction.
5.7.10(d) Technical literacy materials may explain reference architectures, schemas, APIs, dashboards, datasets, model records, benchmark records, system records, inference records, secure release practices, public-good software, observability methods, AI-RAN, DePIN, digital twins, cybersecurity, verifiable compute, and verifiable intelligence records.
5.7.10(e) Such materials shall distinguish learning from official guidance, interpretation support from public authority decision, public-safe report from public warning, dashboard from command system, technical baseline from certification, evidence input from finance-readiness, proof receipt from authority, and handoff from execution.
5.7.10(f) Public authority learning materials shall not create endorsement, adoption, delegation, public-private partnership, procurement approval, public finance approval, regulatory approval, enforcement position, official guidance, public warning, emergency command, sovereign obligation, or public authority decision by default.
5.7.10(g) Learning materials shall be reviewed for public-safe status, controlled vocabulary, boundary language, accessibility, localization, translation accuracy where applicable, correctionability, and required disclaimers.
5.7.10(h) The controlling rule shall be that GCRI Canada contributes literacy so that competent actors can understand evidence and systems better, not so that GCRI Canada replaces those actors.
5.7.11 Community Safeguard Methods, Protected Knowledge Handling, Public-Safe Mapping Logic, and Do-No-Harm Methods. 5.7.11(a) GCRI Canada may contribute community safeguard methods, protected knowledge handling, public-safe mapping logic, do-no-harm methods, accessibility methods, protected participation methods, grievance and correction methods, sensitive infrastructure handling, and vulnerable community protection methods to Nexus.
5.7.11(b) Community safeguard methods shall address how evidence, maps, dashboards, datasets, public-safe reports, technical baselines, Academy materials, observability outputs, and public communications may affect communities, vulnerable groups, Indigenous peoples, local knowledge holders, rights-bearing persons, public authority relationships, and public trust.
5.7.11(c) Protected knowledge handling shall address Indigenous knowledge, local knowledge, community-sensitive knowledge, cultural knowledge, ecological knowledge, health-sensitive information, security-sensitive knowledge, sensitive geographies, and other information that may require restricted use, consent or consultation protocols where applicable, confidentiality, non-extraction, non-enclosure, public-safe release limits, and correction paths.
5.7.11(d) Public-safe mapping logic shall address redaction, aggregation, generalization, scale, resolution, timing, layer visibility, sensitive location protection, infrastructure protection, cyber risk, community risk, public warning confusion, emergency command confusion, public authority confusion, and misuse risk.
5.7.11(e) Do-no-harm methods shall require proportionality, necessity, least-exposure publication, affected-community awareness, accessibility, dignity, non-retaliation, protected participation, privacy protection, cyber safety, and avoidance of stigmatizing, extracting, exposing, or endangering communities.
5.7.11(f) GCRI Canada shall not treat community participation, Indigenous or local knowledge contribution, public authority involvement, university involvement, sponsor support, provider participation, or Nexus visibility as permission to publish sensitive knowledge without proper safeguards.
5.7.11(g) Where community safeguard risk, protected knowledge risk, public-safe mapping risk, or do-no-harm risk arises, GCRI Canada shall restrict, reclassify, redact, aggregate, delay, route, consult where appropriate, correct, withdraw, or refuse release.
5.7.11(h) The controlling rule shall be that Nexus technical truth must remain safe for people, communities, and protected knowledge systems, not merely accurate in a technical sense.
5.7.12 Correction Records, Supersession Records, Withdrawal Records, Retraction Records, Downgrade Records, and Reinstatement Records. 5.7.12(a) GCRI Canada may contribute correction records, supersession records, withdrawal records, retraction records, downgrade records, reinstatement records, public-safe correction notices, controlled correction notices, downstream dependency reviews, challenge records, dispute records, and closeout records to Nexus.
5.7.12(b) Correction records shall identify error, ambiguity, overclaim, stale information, source issue, method issue, technical defect, public-safe issue, boundary confusion, data issue, AI issue, cybersecurity issue, protected knowledge issue, public authority issue, finance issue, procurement issue, certification issue, recognition issue, protocol issue, provider issue, sponsor issue, and the corrective action taken.
5.7.12(c) Supersession records shall identify the superseded material, superseding material, reason, effective date, scope, audience, version, affected interfaces, affected records, public-safe classification, continuing limitations, and correction chain.
5.7.12(d) Withdrawal records shall identify the withdrawn material, reason for withdrawal, withdrawal authority, affected audiences, access changes, repository changes, dashboard changes, API changes, data room changes, public authority notices, finance notices, sponsor or provider notices, replacement status, and residual risk.
5.7.12(e) Retraction records shall be used where a statement, record, output, dataset, model result, benchmark result, report, dashboard state, map layer, proof receipt, public claim, or technical release is materially inaccurate, unsupported, unsafe, unauthorized, misleading, or boundary-defective in a way requiring formal removal of reliance.
5.7.12(f) Downgrade records shall identify where a claim, status, readiness description, public-safe classification, maturity statement, confidence statement, evidence quality statement, technical-baseline status, release state, or public-facing description must be reduced because the record no longer supports the prior level of claim.
5.7.12(g) Reinstatement records shall identify where a withdrawn, downgraded, restricted, quarantined, superseded, or disputed material may be restored in whole or in part, including the basis for reinstatement, review completed, limitations, public-safe status, version, conditions, and correction path.
5.7.12(h) Correction-related records shall be versioned, source-linked, public-safe where required, access-controlled where necessary, preserved in institutional memory, and capable of being routed to GRF, GRA, Protocol Authority, Nexus bodies, public authorities, enterprise actors, providers, sponsors, communities, or other affected actors where appropriate.
5.7.12(i) Correction-related records shall not be treated as admission of downstream liability, certification denial, recognition denial, finance-readiness denial, public authority determination, procurement decision, professional opinion, protocol decision, public warning, emergency command, or execution instruction by default.
5.7.12(j) The controlling rule shall be that GCRI Canada contributes correction memory to Nexus so that public-good truth can improve over time and so that errors do not harden into authority.
5.8 What GCRI Canada Does Not Contribute as Nexus Authority
5.8.1 No GRF Recognition by GCRI Canada Contribution. 5.8.1(a) No contribution by GCRI Canada to Nexus shall constitute recognition, standing, maturity record, claims approval, registry status, public-facing legitimacy, stakeholder-formation status, or public-safe reporting effect within the institutional function of The Global Risks Forum (GRF).
5.8.1(b) GCRI Canada may contribute evidence records, methods, observability summaries, ontology, controlled vocabulary, technical baselines, public-good software records, public-safe reports, controlled annexes, Docket inputs, Grid inputs, challenge records, correction records, and source-lineage materials that may support GRF processes, but such contribution shall remain upstream technical truth support.
5.8.1(c) GRF recognition, standing, maturity records, claims discipline, stakeholder formation, registry treatment, public-facing legitimacy, and public-safe reporting determinations shall require GRF or another competent recognition actor to act through its own authority, process, review, record, and correction path.
5.8.1(d) GCRI Canada shall not represent that a person, provider, project, technology, node, host, National Consortium Company, Project SPV, public authority interface, public-good software asset, technical baseline, dataset, model, dashboard, method, or Nexus activity is recognized by GRF merely because GCRI Canada contributed evidence or methods.
5.8.1(e) Any GCRI Canada contribution routed to GRF shall identify its source status, scope, limitations, confidence where appropriate, public-safe status, review status, correction path, and GCRI Canada’s non-recognition role.
5.8.1(f) Where GCRI Canada materials are misused to imply GRF recognition, GCRI Canada shall correct, restrict, withdraw, notify GRF where appropriate, and preserve correction records.
5.8.1(g) The controlling rule shall be that GCRI Canada may support recognition-related truth, but GRF or another competent recognition actor must create recognition.
5.8.2 No GRA Finance-Readiness by GCRI Canada Contribution. 5.8.2(a) No contribution by GCRI Canada to Nexus shall constitute finance-readiness, capital readiness, capital readability, proof-pack completion, insurance-readiness, capital-reader approval, RNFD, NFD, UNFSD status, investor suitability, fundability, bankability, public finance approval, underwriting support, rating, guarantee, or capital commitment within the institutional function of The Global Risks Alliance (GRA).
5.8.2(b) GCRI Canada may contribute evidence records, technical baselines, observability summaries, host-readiness evidence, node evidence, data-governance records, AI-governance records, cybersecurity records, public-safe reports, diligence gap maps, proof inputs, controlled annexes, Academy materials, and correction records to GRA-facing processes, but such contribution shall not become a GCRI Canada finance determination.
5.8.2(c) GRA finance-readiness, capital readability, proof-pack, insurance-readiness, capital-reader room, RNFD, NFD, UNFSD, and regulated-perimeter outputs shall require GRA or another competent finance-facing actor to act through its own authority, process, record, review, and correction path.
5.8.2(d) GCRI Canada shall not represent that any project, SPV, National Consortium Company, provider, technology, host, node, public authority interface, public-good software asset, technical baseline, evidence pack, dashboard, map, or Nexus activity is finance-ready, capital-ready, insurable, underwritable, rated, fundable, bankable, investor-suitable, publicly financed, or capital-committed merely because GCRI Canada contributed evidence.
5.8.2(e) Any GCRI Canada contribution routed to GRA shall include no-investment-advice, no-offer, no-solicitation, no-brokerage, no-lending, no-insurance, no-underwriting, no-rating, no-public-finance-approval, no-capital-commitment, and no-finance-readiness language where material.
5.8.2(f) Where GCRI Canada materials are misused to imply GRA finance-readiness or financial approval, GCRI Canada shall correct, restrict, withdraw, notify GRA or affected actors where appropriate, seek regulated-perimeter review where material, and preserve correction records.
5.8.2(g) The controlling rule shall be that GCRI Canada may support finance-readable evidence, but it shall not issue finance-readiness.
5.8.3 No Nexus Standards / Protocol Authority Effect by GCRI Canada Contribution. 5.8.3(a) No contribution by GCRI Canada to Nexus shall constitute protocol effect, conformance status with external force, role key, smart-license right, proof-receipt legal effect, entitlement state, protocol approval, protocol enforcement, anchoring discipline with external effect, or technical validity surface within the institutional function of Nexus Standards / Protocol Authority.
5.8.3(b) GCRI Canada may contribute schemas, ontologies, controlled vocabulary, evidence requirements, method profiles, technical baselines, reference architectures, public-good software, APIs, proof-input structures, proof-receipt logic support, benchmark records, dataset records, model records, system records, inference records, and correction records to Protocol Authority-facing work.
5.8.3(c) Such contributions shall remain technical, evidentiary, methodological, semantic, public-good software, or conformance-supporting inputs unless Protocol Authority or another competent protocol actor separately creates protocol effect through proper authority, process, review, record, and correction path.
5.8.3(d) Technical authorship, repository stewardship, schema development, software release, proof-input preparation, public-good baseline development, or benchmark support by GCRI Canada shall not create protocol authority by default.
5.8.3(e) GCRI Canada shall not represent that any actor, node, provider, system, dataset, model, dashboard, public-good software component, technical baseline, proof receipt, blockchain anchor, role, license, entitlement, or Nexus interface has protocol effect merely because GCRI Canada contributed technical materials.
5.8.3(f) Where GCRI Canada materials are misused to imply protocol effect, GCRI Canada shall correct, restrict, withdraw, notify Protocol Authority where appropriate, and preserve correction records.
5.8.3(g) The controlling rule shall be that GCRI Canada may support protocol discipline, but Protocol Authority or another competent protocol actor must create protocol effect.
5.8.4 No Public Authority Act by GCRI Canada Contribution. 5.8.4(a) No contribution by GCRI Canada to Nexus shall constitute a public authority act, public law decision, regulatory approval, enforcement position, official guidance, permit, license, public finance approval, procurement approval, public-private partnership, sovereign obligation, public adoption, public funding decision, public safety directive, public health order, or emergency-management decision.
5.8.4(b) GCRI Canada may contribute public authority learning materials, evidence records, public-safe reports, controlled annexes, dashboards, maps, technical baselines, public-good software documentation, observability summaries, data-governance methods, AI-governance methods, cyber-governance methods, and correction records to public authorities.
5.8.4(c) Such contributions shall be decision-supporting only. Public authorities shall remain responsible for their own jurisdiction, authority, procedures, evidentiary weight, consultation, approvals, reasons, notices, adoption, implementation, publication, enforcement, procurement, public finance, public warnings, emergency commands, corrections, and accountability.
5.8.4(d) Public authority attendance, review, comments, silence, data contribution, dashboard access, funding, hosting, participation, or repeated involvement shall not transform a GCRI Canada contribution into public authority action.
5.8.4(e) GCRI Canada shall not use public authority names, logos, titles, photographs, quotes, agency names, jurisdiction references, maps, official classifications, attendance, funding, hosting, or data references to imply official approval unless the competent public authority has separately and lawfully created such meaning.
5.8.4(f) Where GCRI Canada materials are misused to imply public authority action, GCRI Canada shall correct, restrict, withdraw, notify affected public authorities where appropriate, and preserve correction records.
5.8.4(g) The controlling rule shall be that GCRI Canada may support public authority learning, but public authority acts belong to public authorities.
5.8.5 No Public Warning by GCRI Canada Contribution. 5.8.5(a) No contribution by GCRI Canada to Nexus shall constitute an official public warning, emergency alert, evacuation instruction, public health order, safety directive, infrastructure-use directive, shelter directive, curfew instruction, road closure instruction, utility instruction, cyber emergency notice, or public emergency directive.
5.8.5(b) GCRI Canada may contribute observability methods, dashboards, maps, public-safe visualizations, sensor evidence methods, AI-RAN signal methods, DePIN evidence methods, digital twin assumption methods, cyber telemetry methods, climate or hazard methods, public-safe reports, and learning materials, but such contributions shall not become official warning systems by default.
5.8.5(c) Public warning authority shall remain with competent public authorities or other lawful warning actors acting through their own processes, systems, records, and public accountability.
5.8.5(d) Observability outputs, dashboards, maps, AI outputs, model outputs, digital twins, sensors, DePIN signals, AI-RAN signals, blockchain anchors, proof receipts, confidence scores, anomaly flags, and public-safe reports shall not become public warnings merely because they are visible, timely, useful, technical, automated, or relied upon.
5.8.5(e) GCRI Canada contributions in hazard, emergency, public health, public safety, cyber, infrastructure, climate, wildfire, flood, disaster, or safety contexts shall carry public-safe boundary language where material and shall avoid official-warning design unless the competent public authority separately controls the official warning function.
5.8.5(f) Where public-warning confusion arises, GCRI Canada shall reclassify, relabel, restrict, correct, withdraw, notify competent actors where appropriate, and preserve correction records.
5.8.5(g) The controlling rule shall be that GCRI Canada may help clarify risk evidence, but it shall not warn the public as an official warning authority.
5.8.6 No Procurement Approval by GCRI Canada Contribution. 5.8.6(a) No contribution by GCRI Canada to Nexus shall constitute procurement approval, vendor selection, tender prequalification, public purchasing recommendation, procurement ranking, preferred vendor status, public buyer approval, market allocation, or provider endorsement.
5.8.6(b) GCRI Canada may contribute technical baselines, public-good software, benchmark methods, evaluation harnesses, evidence records, public-safe reports, observability methods, dashboards, maps, Academy materials, public authority learning materials, and provider-neutral technical materials, but such contributions shall not become procurement decisions.
5.8.6(c) Testing, benchmarking, technical contribution, sponsorship, dashboard inclusion, public authority learning participation, Academy participation, lab participation, validation sprint participation, Nexus Universe participation, public-good software compatibility, or repository contribution shall not create procurement advantage by default.
5.8.6(d) Procurement decisions shall remain with competent procurement actors acting through their own procurement laws, policies, evaluation criteria, competition duties, conflicts rules, records, remedies, and accountability.
5.8.6(e) GCRI Canada shall not structure evidence packs, technical baselines, public-good software, benchmark libraries, dashboards, maps, or public authority learning materials as hidden procurement specifications or preferred-provider channels by default.
5.8.6(f) Where GCRI Canada materials are misused to imply procurement approval or provider preference, GCRI Canada shall correct, restrict, withdraw, notify affected actors where appropriate, and preserve correction records.