IV. BOUNDARIES
4.1 Constitutional Non-Execution Clause
4.1.1 Non-Execution as a Constitutional Invariant of GCRI Canada. 4.1.1(a) Non-execution shall be a constitutional invariant of The Global Centre for Risk and Innovation - Canada. GCRI Canada shall exist and operate as a Canadian public-benefit, nonprofit, non-share, non-distributing, non-charitable unless and until lawfully changed, upstream truth, evidence, methods, observability, ontology, public-good R&D, public-good software, open technical-baseline, Nexus Truth Engine methods, Nexus Observatory methods, public authority learning, public-safe publication, and correctionability institution, and not as an execution body by default.
4.1.1(b) Non-execution means that GCRI Canada shall not, by default, own, operate, finance, manage, control, direct, dispatch, deploy, approve, procure, certify, recognize, finance-ready, insure, underwrite, rate, guarantee, regulate, warn, command, enforce, broker, lend, invest, place, clear, settle, or execute any downstream project, transaction, public authority decision, infrastructure deployment, market activity, emergency action, provider implementation, public finance action, securities activity, insurance activity, procurement process, protocol entitlement, or asset-level operation.
4.1.1(c) GCRI Canada may produce and steward evidence, methods, observability logic, ontologies, controlled vocabulary, technical baselines, public-good software, research outputs, public-safe reports, public authority learning materials, Academy materials, Nexus Truth Engine methods, Nexus Observatory methods, correction records, Docket inputs, Grid inputs, proof inputs, technical notes, controlled annexes, dashboards, maps, and other public-good technical materials, but those outputs shall remain upstream support unless a competent external authority lawfully attaches downstream effect through its own process and record.
4.1.1(d) Non-execution shall apply regardless of technical sophistication, public visibility, sponsor support, provider participation, public authority attendance, public authority interest, emergency context, capital-reader interest, media attention, Nexus proximity, repository control, dashboard visibility, AI output, proof receipt, blockchain anchor, DePIN record, digital twin output, public-safe report, or repeated use by downstream actors.
4.1.1(e) No artifact, record, model output, dashboard, map, proof receipt, technical baseline, software release, publication, event, Academy session, observatory signal, public authority learning material, sponsor acknowledgment, provider participation, or Nexus diagram shall be interpreted to create execution authority unless such authority is lawfully created by a competent actor outside GCRI Canada’s default role and recorded in a proper instrument.
4.1.1(f) Non-execution shall bind all directors, officers, members where applicable, committees, councils, staff, contractors, fellows, advisors, researchers, students, contributors, participants, sponsors, providers, vendors, hosts, public authority participants, universities, civil society participants, media participants, Nexus actors, and all persons using, describing, relying on, or referencing GCRI Canada outputs.
4.1.1(g) Any provision, policy, program, contract, public claim, technical system, repository label, dashboard state, AI output, proof receipt, public authority communication, finance-facing material, sponsor material, provider material, or Nexus interface that appears to confer execution authority on GCRI Canada shall be read down, corrected, restricted, suspended, superseded, withdrawn, or referred for legal and governance review.
4.1.1(h) The non-execution invariant shall not be waived by convenience, urgency, funding opportunity, public authority interest, sponsor expectation, provider readiness, public visibility, technical centrality, media narrative, national momentum, regional coordination, public-good need, or downstream demand.
4.1.2 Non-Execution as a Condition of Public-Benefit Legitimacy. 4.1.2(a) Non-execution shall be a condition of GCRI Canada’s public-benefit legitimacy. GCRI Canada’s legitimacy shall rest on its capacity to steward evidence, methods, observability, ontology, public-good R&D, public-good software, technical baselines, public authority learning, public-safe publication, and correctionability without converting those functions into downstream power.
4.1.2(b) GCRI Canada shall maintain public-benefit legitimacy by remaining structurally upstream of execution decisions, commercial decisions, financing decisions, procurement decisions, regulatory decisions, emergency decisions, public warning decisions, recognition decisions, finance-readiness decisions, certification decisions, protocol-effect decisions, and operational decisions.
4.1.2(c) Public-benefit legitimacy requires that GCRI Canada be trusted as an evidence and methods steward rather than as a market participant, transaction actor, public authority substitute, sponsor-controlled platform, provider-selection body, or execution vehicle.
4.1.2(d) GCRI Canada may support downstream action by others through high-integrity inputs, but it shall not convert public-good evidence into institutional command, public-safe reporting into public warning, technical baselines into certification, observability into emergency authority, public authority learning into delegated authority, GRA-relevant evidence into finance-readiness, GRF-relevant evidence into recognition, or protocol-supporting logic into protocol entitlement.
4.1.2(e) The public-benefit character of GCRI Canada shall be impaired if its outputs are used to create unsupported reliance, market advantage, procurement preference, public authority confusion, finance signaling, provider endorsement, sponsor influence, emergency command implication, public warning implication, or execution consequence.
4.1.2(f) GCRI Canada shall therefore design all public-facing and controlled outputs with clear issuer labels, status labels, scope limits, limitation statements, public-safe classifications, reliance boundaries, correction pathways, and role-separation language where material.
4.1.2(g) Where public-benefit legitimacy is threatened by execution drift or execution perception, GCRI Canada shall clarify, narrow, reclassify, correct, withdraw, suspend, route, or terminate the relevant activity, communication, relationship, technical asset, or output.
4.1.2(h) Public-benefit legitimacy shall be measured by integrity, restraint, accuracy, correctionability, independence, public-safe usefulness, and trust, not by transaction volume, capital mobilization, provider adoption, sponsor value, public authority proximity, media visibility, market share, or execution scale.
4.1.3 Non-Execution as a Condition of Public-Good Stack Integrity. 4.1.3(a) Non-execution shall be a condition of public-good stack integrity. GCRI Canada shall remain within the public-good stack as an upstream evidence, methods, observability, ontology, public-good R&D, public-good software, technical-baseline, public authority learning, public-safe publication, and correctionability institution.
4.1.3(b) The public-good stack shall remain distinct from enterprise-stack execution, investible vehicles, National Consortium Companies, Project SPVs, providers, vendors, sponsors, capital actors, procurement actors, public authority actors, regulated actors, infrastructure operators, and market actors.
4.1.3(c) GCRI Canada may generate public-good assets that support enterprise-stack actors, but such support shall not convert GCRI Canada into an enterprise-stack actor. Evidence support shall not become investment recommendation. Technical-baseline support shall not become asset ownership. Observatory-methods support shall not become infrastructure operation. Public-good compatibility support shall not become procurement steering. Public authority learning support shall not become delegated authority.
4.1.3(d) Public-good stack integrity requires role separation between GCRI Canada, GRF, GRA, Protocol Authority, Nexus Network, Nexus Universe, Nexus Observatory, Regional Nexus Consortiums, National Nexus Consortiums, National Consortium Companies, Project SPVs, providers, sponsors, public authorities, and capital readers.
4.1.3(e) GCRI Canada shall not allow public-good methods, software, schemas, ontologies, baselines, dashboards, reports, Academy materials, proof inputs, or correction records to become hidden execution rails, exclusive commercial assets, private governance mechanisms, provider chokepoints, sponsor-controlled instruments, or unrecorded downstream authority.
4.1.3(f) Public-good stack integrity shall require open where appropriate, controlled where required, secure always, public-safe before release, and correctable at all stages.
4.1.3(g) Where a public-good asset is used by enterprise-stack actors, the record shall preserve ownership or stewardship status, license, permitted use, prohibited use, support level, public-safe status, limitation, correction path, and non-execution boundary.
4.1.3(h) Where public-good stack integrity is threatened by execution drift, enclosure, sponsor control, provider preference, finance overclaim, public authority confusion, protocol implication, certification implication, or procurement implication, GCRI Canada shall restrict, relabel, relicense, fork, replace, withdraw, correct, or escalate the affected asset or relationship.
4.1.4 Non-Execution as a Condition of Legal Separateness From Enterprise Stack Actors. 4.1.4(a) Non-execution shall be a condition of GCRI Canada’s legal separateness from enterprise stack actors, including National Consortium Companies, Project SPVs, providers, vendors, contractors, sponsors, donors, hosts, capital actors, insurers, lenders, underwriters, investors, public finance bodies, procurement actors, implementation actors, infrastructure operators, and execution vehicles.
4.1.4(b) GCRI Canada shall not own, operate, finance, manage, control, guarantee, insure, underwrite, rate, lend to, broker for, arrange capital for, procure for, select providers for, supervise, direct, dispatch, deploy, or execute any enterprise-stack actor by default.
4.1.4(c) Legal separateness shall not be defeated by shared mission, shared records, shared public-good software, shared technical baselines, shared public authority learning, shared sponsors, shared providers, shared platforms, shared personnel, shared repositories, shared public-safe reports, shared events, shared public claims, shared Nexus diagrams, or shared technical assets.
4.1.4(d) Where GCRI Canada provides evidence, methods, technical baselines, public-good software, observability methods, public-safe reports, Academy materials, Docket inputs, Grid inputs, proof inputs, diligence gap maps, host-readiness evidence, node evidence, or correction records to enterprise-stack actors, such inputs shall be bounded, non-advisory, non-financial, non-procurement, non-certification, non-recognition, non-protocol, non-operational, and non-executing unless a competent external actor separately creates downstream effect.
4.1.4(e) Enterprise-stack actors shall remain responsible for their own governance, ownership, financing, procurement, contracting, insurance, operations, employment, tax, accounting, safety, cybersecurity, data handling, public authority relationships, public claims, delivery, performance, warranties, and liabilities.
4.1.4(f) GCRI Canada shall not allow its name, marks, reports, dashboards, technical baselines, evidence records, Academy materials, public authority references, or Nexus-compatible materials to be used as marketing authority for SPVs, securities, debt, insurance, public finance, procurement opportunities, provider services, project investments, or execution opportunities.
4.1.4(g) Where enterprise-stack materials imply that GCRI Canada controls, approves, finances, procures, guarantees, insures, underwrites, rates, certifies, recognizes, protocol-authorizes, public-authority-approves, or executes the enterprise-stack actor, GCRI Canada shall require correction, restriction, withdrawal, supersession, clarification, termination, or legal review.
4.1.4(h) Legal separateness from enterprise-stack actors shall be maintained through written agreements, public claims controls, name-use rules, cost-allocation records, data and IP boundaries, publication boundaries, correction rights, and role labels.
4.1.5 Non-Execution as a Condition of Public Authority Boundary Safety. 4.1.5(a) Non-execution shall be a condition of public authority boundary safety. GCRI Canada shall support public authorities through evidence, methods, observability interpretation, technical baselines, public-good software, public authority learning, public-safe reports, Academy materials, and correction records, but shall not become a public authority by default.
4.1.5(b) GCRI Canada shall not issue public authority decisions, official public warnings, emergency orders, evacuation instructions, public health orders, regulatory approvals, permits, enforcement actions, procurement awards, funding approvals, public finance approvals, official guidance, sovereign obligations, public-private partnership status, or public-sector determinations.
4.1.5(c) Public authority participation in GCRI Canada activities shall be capacity-classified where material. Attendance, comments, data contribution, funding, hosting, public authority learning, dashboard review, public-safe report review, Academy participation, or Nexus participation shall not create endorsement, adoption, procurement approval, funding approval, public finance approval, regulatory approval, public warning, emergency command, public-private partnership, joint venture, or sovereign obligation by default.
4.1.5(d) GCRI Canada outputs used in public authority contexts shall identify issuer, scope, status, limitations, public-safe classification, non-decision status, non-delegation status, data restrictions, confidence where appropriate, review status, and correction path.
4.1.5(e) Dashboards, maps, AI outputs, digital twins, observability signals, risk indicators, degraded-mode indicators, geospatial layers, proof receipts, public-safe reports, and Academy materials shall not be designed or described as official public warnings, emergency commands, evacuation instructions, regulatory notices, public health orders, public safety orders, or official government guidance unless a competent public authority has lawfully issued them as such.
4.1.5(f) Where GCRI Canada identifies evidence that may be relevant to public safety or public authority action, it may route or hand off the evidence to competent public authorities or responsible actors through records-valid, public-safe, privacy-preserving, cybersecurity-compatible, and protected-knowledge-aware procedures, but shall not itself make the public authority decision.
4.1.5(g) Public authority names, logos, quotes, titles, photographs, attendance, agency names, jurisdictions, and data references shall be used only with appropriate approval, capacity classification, public-safe review, and public claims controls.
4.1.5(h) Where public authority boundary safety is threatened by overclaim, public-warning implication, emergency-command implication, procurement implication, funding implication, regulatory implication, sovereign implication, or public-private partnership implication, GCRI Canada shall clarify, restrict, withdraw, correct, supersede, notify affected authorities where appropriate, or suspend the activity.
4.1.6 Non-Execution as a Condition of Finance-Readiness Boundary Safety. 4.1.6(a) Non-execution shall be a condition of finance-readiness boundary safety. GCRI Canada may provide evidence, methods, public-safe reports, technical baselines, diligence gap maps, host-readiness evidence, node evidence, observability summaries, proof-pack component inputs, and correction records that may be useful to GRA, capital readers, insurers, lenders, investors, public finance actors, National Consortium Companies, Project SPVs, or other competent actors, but GCRI Canada shall not issue finance-readiness by default.
4.1.6(b) GCRI Canada shall not provide investment advice, securities recommendations, securities offerings, brokerage, finder activity, placement activity, lending, underwriting, insurance, insurance advice, ratings, guarantees, public finance approval, capital commitments, transaction recommendations, fund management, clearing, settlement, payment intermediation, or regulated financial services.
4.1.6(c) Evidence usefulness to finance actors shall not convert GCRI Canada into a finance actor. Risk evidence shall not become underwriting. Diligence gaps shall not become investment advice. Proof-pack inputs shall not become proof-pack completion. Public-safe reports shall not become bankability. Observability summaries shall not become insurance approval. Technical baselines shall not become creditworthiness. Host-readiness evidence shall not become capital commitment.
4.1.6(d) Finance-facing or capital-reader access to GCRI Canada materials shall be controlled reading, evidence literacy, technical understanding, or diligence-supporting review, not financial advice, investment advice, insurance advice, underwriting guidance, rating, credit opinion, public finance approval, capital recommendation, transaction invitation, or capital commitment.
4.1.6(e) GCRI Canada shall not allow terms such as “finance-ready,” “capital-ready,” “investment-ready,” “bankable,” “investor-suitable,” “insurance-ready,” “underwritable,” “rated,” “guaranteed,” “public-finance-approved,” “routeable,” “proof-pack complete,” “capital-readable,” or equivalent finance-facing terms unless accurately referencing an external competent record and used in a non-advisory, finance-safe, records-valid manner.
4.1.6(f) Materials with finance-facing relevance shall include no-advice, no-offer where appropriate, no-underwriting, no-rating, no-guarantee, no-capital-commitment, no-public-finance-approval, issuer, limitation, public-safe status, finance-boundary, and correction language where material.
4.1.6(g) Sponsor support, public authority interest, capital-reader attendance, insurer review, lender review, investor review, public finance reader access, or GRA interface shall not create finance-readiness, investment suitability, insurance-readiness, underwriting, rating, guarantee, public finance approval, or capital commitment.
4.1.6(h) Where finance-readiness boundary safety is threatened, GCRI Canada shall restrict materials, correct claims, withdraw name use, suspend access, notify affected actors where appropriate, seek legal review, or terminate the relevant interface.
4.1.7 Non-Execution as a Condition of Provider Neutrality and Competition Safety. 4.1.7(a) Non-execution shall be a condition of provider neutrality and competition safety. GCRI Canada shall not select, rank, endorse, prefer, certify, procure, approve, award, exclude, allocate markets to, or provide procurement advantage to any provider by default.
4.1.7(b) Providers may participate in evidence review, technical-baseline discussion, testing, benchmarking, method review, public-good software contribution, observability-methods development, Academy learning, public authority learning contexts, or Nexus-compatible technical discussions, but such participation shall not create preferred status, certification, recognition, procurement approval, public authority approval, finance-readiness, protocol entitlement, market ranking, technical superiority, or GCRI Canada endorsement.
4.1.7(c) GCRI Canada may identify whether evidence relevant to a technical baseline, method, public-good software interface, cybersecurity expectation, privacy expectation, AI-governance expectation, public-safe release expectation, or public-good compatibility requirement is present, absent, incomplete, disputed, stale, restricted, or correction-requiring, but shall not convert such evidence review into provider selection.
4.1.7(d) Testing, benchmarking, demonstrations, interoperability checks, compatibility reviews, repository contributions, or public-good software integrations shall be described with precise limitations and shall not be used as procurement rankings, product certifications, vendor endorsements, or market-allocation instruments.
4.1.7(e) GCRI Canada shall not use provider-specific public claims, sponsor materials, public authority materials, technical baselines, dashboards, maps, reports, Academy materials, events, or Nexus documents to create provider preference unless a competent actor with lawful authority makes an external decision and GCRI Canada’s role is accurately bounded.
4.1.7(f) Provider neutrality shall apply across all technologies and sectors, including AI, AI-RAN, O-RAN, private wireless, telecommunications, cyber, compute, cloud, DePIN, blockchain, DLT, digital twins, geospatial systems, sensors, Earth observation, robotics, drones, energy, water, food, health, climate, advanced manufacturing, semiconductors, and related mission-critical infrastructure.
4.1.7(g) Where provider participation creates competition risk, procurement implication, endorsement implication, sponsor-shaped preference, public authority confusion, finance signaling, certification implication, protocol implication, or market-conduct concern, GCRI Canada shall correct, restrict, relabel, withdraw, suspend, or terminate the relevant activity or claim.
4.1.7(h) Provider neutrality and competition safety shall preserve public trust that GCRI Canada’s evidence and methods are not vendor marketing, hidden procurement, sponsor preference, or market steering.
4.1.8 Non-Execution as a Condition of Sponsor Non-Control. 4.1.8(a) Non-execution shall be a condition of sponsor non-control. Sponsors, donors, funders, supporters, in-kind contributors, cloud providers, software providers, AI model providers, facility hosts, technical supporters, corporate supporters, philanthropic supporters, and public-sector supporters shall support GCRI Canada only within mission-bounded, non-controlling, records-valid, public-benefit limits.
4.1.8(b) No sponsor or donor shall acquire control over GCRI Canada governance, Board decisions, officer decisions, evidence selection, method selection, technical baselines, ontology, public-good software, repository governance, data access, AI workflows, public authority access, provider participation, publication timing, public-safe release, correction decisions, public claims, Academy content, Nexus role, or institutional doctrine.
4.1.8(c) Sponsor support shall not purchase legitimacy, recognition, finance-readiness, certification, protocol effect, public authority approval, procurement advantage, provider preference, publication influence, correction veto, public-good asset control, or execution opportunity.
4.1.8(d) Sponsor visibility shall be factual, proportionate, public-safe, non-misleading, records-supported, and subject to public claims review. Sponsor logos, sponsor categories, sponsor levels, acknowledgments, event materials, dashboards, reports, Academy materials, and Nexus documents shall not imply endorsement, control, preferred status, public authority access, finance-readiness influence, or publication control.
4.1.8(e) Restricted funding or sponsored support may be accepted only where the restriction is lawful, public-benefit aligned, non-controlling, non-extractive, non-enclosing, non-distribution-compliant, privacy-compatible, cybersecurity-compatible, public-safe, and consistent with mission lock, non-execution, provider neutrality, public authority boundaries, finance boundaries, and correctionability.
4.1.8(f) GCRI Canada shall preserve publication independence and correction independence. No sponsorship may prohibit, delay, condition, punish, or financially penalize correction, limitation disclosure, supersession, withdrawal, public-safe clarification, or public claims correction.
4.1.8(g) Where sponsor support creates capture risk, finance signaling, provider preference, public authority confusion, publication-control risk, public claims risk, data risk, technical dependency risk, or mission-drift risk, GCRI Canada shall refuse, narrow, condition, disclose where appropriate, suspend, return, terminate, correct, or escalate the support relationship.
4.1.8(h) Sponsor non-control shall preserve the principle that public-good evidence, methods, observability, ontology, software, technical baselines, publications, corrections, and institutional meaning cannot be bought, owned, suppressed, inflated, delayed, or redirected by supporters.
4.1.9 Non-Execution as a Condition of Research Independence, Evidence Integrity, and Public-Safe Publication. 4.1.9(a) Non-execution shall be a condition of research independence, evidence integrity, and public-safe publication. GCRI Canada shall preserve the independence of its research, methods, evidence records, public-safe reports, technical baselines, public-good software, Academy materials, and correction records from downstream execution pressures.
4.1.9(b) Research independence requires that GCRI Canada’s evidence and methods not be shaped by a desired financing outcome, procurement outcome, provider outcome, sponsor outcome, public authority outcome, recognition outcome, finance-readiness outcome, certification outcome, protocol outcome, media outcome, or execution outcome.
4.1.9(c) Evidence integrity requires evidence before assertion, source before claim, record before effect, method before conclusion, limitation before reliance, review before publication, public-safe release before public exposure, and correction after error, challenge, supersession, or changed conditions.
4.1.9(d) Public-safe publication requires that GCRI Canada evaluate whether outputs may expose personal information, rights-bearing data, sovereign data, public authority restricted information, Indigenous knowledge, local knowledge, community-sensitive information, protected knowledge, cyber-sensitive information, sensitive infrastructure information, health-sensitive data, controlled technology, public safety risk, finance overclaim, public authority confusion, provider preference, sponsor control, or execution implication.
4.1.9(e) GCRI Canada shall not publish, release, display, map, dashboard, anchor, hash, tokenize, proof-record, or otherwise expose information merely because it is technically available, analytically interesting, publicly visible, sponsor-supported, provider-enabled, finance-useful, media-attractive, or Nexus-relevant.
4.1.9(f) AI outputs, model summaries, retrieval results, automated classifications, digital twin outputs, sensor signals, DePIN records, blockchain anchors, proof receipts, and dashboard states shall be treated as inputs or records within defined scope, not as authority, truth, public warning, finance-readiness, recognition, certification, procurement approval, protocol effect, or execution instruction by default.
4.1.9(g) Where research independence, evidence integrity, or public-safe publication is threatened by execution pressure, public authority expectation, sponsor influence, provider narrative, finance narrative, media timing, event timing, emergency pressure, or internal ambition, GCRI Canada shall apply review, limitation, delay, redaction, controlled release, correction, withdrawal, or refusal.
4.1.9(h) Research independence, evidence integrity, and public-safe publication shall be protected as core public-benefit duties and shall not be subordinated to speed, revenue, visibility, sponsorship, provider value, capital-reader usefulness, public authority convenience, or Nexus momentum.
4.1.10 Non-Execution as a Board-Level Duty, Officer-Level Constraint, Program-Level Design Rule, Publication-Level Disclaimer, and Participant-Level Obligation. 4.1.10(a) Non-execution shall operate at every level of GCRI Canada as a Board-level duty, officer-level constraint, program-level design rule, publication-level disclaimer where appropriate, and participant-level obligation.
4.1.10(b) The Board shall oversee non-execution as a constitutional duty. Board oversight shall include approving or requiring policies, controls, risk reviews, boundary reviews, public claims rules, sponsor rules, provider rules, public authority protocols, finance-boundary controls, data safeguards, AI controls, cybersecurity controls, publication controls, correction systems, and escalation pathways sufficient to preserve non-execution.
4.1.10(c) Officers shall operate within non-execution as an authority constraint. No officer shall approve, sign, publish, communicate, contract, convene, release, route, fund, accept support, authorize access, or manage a program in a manner that converts GCRI Canada into an execution actor, public authority, finance actor, procurement actor, certifier, recognizer, protocol authority, provider selector, sponsor-controlled platform, infrastructure operator, public warning authority, or emergency command body.
4.1.10(d) Programs shall be designed with non-execution embedded from inception. Program charters, budgets, public materials, data flows, AI workflows, public authority interfaces, sponsor arrangements, provider participation, technical systems, dashboards, repositories, Academy materials, outputs, handoff records, and correction pathways shall identify what GCRI Canada does, what it does not do, who downstream actors are, what authority remains external, and how boundary risk will be controlled.
4.1.10(e) Publications shall include non-execution disclaimers, limitation language, issuer labels, status labels, public-safe classifications, no-advice language, no-public-authority-action language, no-finance-readiness language, no-certification language, no-recognition language, no-protocol-effect language, no-procurement language, no-public-warning language, no-execution language, and correction pathways where appropriate to context and reliance risk.
4.1.10(f) Participants shall respect non-execution. Directors, officers, staff, contractors, fellows, advisors, researchers, students, contributors, sponsors, providers, vendors, hosts, public authority participants, universities, civil society participants, media actors, capital readers, Nexus actors, and partners shall not describe, use, market, cite, rely on, or repurpose GCRI Canada outputs as execution authority, public authority action, finance-readiness, investment advice, insurance approval, certification, recognition, procurement approval, protocol effect, public warning, emergency command, provider endorsement, sponsor control, or project approval.
4.1.10(g) Any person who becomes aware that GCRI Canada materials, systems, relationships, public claims, or outputs are being used in an execution-implying manner shall have a duty appropriate to role to report, correct, restrict, escalate, or seek clarification.
4.1.10(h) Non-execution controls shall be implemented through records, forms, templates, public claims reviews, boundary reviews, contracts, data agreements, sponsor terms, provider terms, repository labels, dashboard labels, access controls, publication reviews, incident response, correction mechanisms, and training.
4.1.10(i) Breach or threatened breach of non-execution may require correction, retraction, withdrawal, supersession, access restriction, program suspension, relationship termination, public-safe clarification, controlled clarification, legal review, Board review, or other remedial action.
4.1.10(j) The controlling rule shall be that GCRI Canada may be rigorous, useful, technical, visible, connected, global, and consequential, but its consequence shall arise through evidence, methods, public-good technical stewardship, learning, publication, handoff, and correction—not through execution authority by default.
4.2 Permitted Non-Executing Functions
4.2.1 Research, Public-Benefit R&D, and Technical Investigation. 4.2.1(a) GCRI Canada may conduct, support, coordinate, document, publish where public-safe, restrict where required, and correct research, public-benefit research and development, technical investigation, systems-risk inquiry, resilience inquiry, technology inquiry, evidence inquiry, methods inquiry, observability inquiry, ontology inquiry, public-good software inquiry, open technical-baseline inquiry, public authority learning inquiry, and Nexus-compatible technical investigation within its mission.
4.2.1(b) Permitted research may concern AI, AI-RAN, O-RAN, private wireless, telecommunications, cyber, cloud, sovereign compute, high-performance computing, verifiable compute, verifiable intelligence, blockchain, DLT, Web3, DePIN, digital twins, geospatial systems, Earth observation, sensors, drones, robotics, quantum-relevant systems, advanced manufacturing, semiconductors, climate, disaster risk, energy, water, food, health, biodiversity, biosecurity, infrastructure, public authority capacity, community safeguards, Indigenous and protected knowledge safeguards, and other exponential or mission-critical technologies.
4.2.1(c) Public-benefit R&D may include developing methods, prototypes, reference architectures, evaluation harnesses, test harnesses, dashboards, data tools, APIs, schemas, ontologies, model records, dataset records, benchmark records, public-good software, public-safe publication workflows, correction systems, evidence records, observability methods, and Academy materials, provided that such R&D remains non-executing and does not become provider delivery, public authority action, regulated advice, finance activity, procurement activity, certification, recognition, protocol effect, infrastructure operation, or project execution by default.
4.2.1(d) Technical investigation may identify evidence gaps, method gaps, data gaps, cyber risks, AI risks, public-safe publication risks, infrastructure dependencies, model limitations, digital twin assumptions, sensor limitations, DePIN signal risks, blockchain anchoring limits, public authority boundary issues, finance-boundary issues, provider-neutrality issues, sponsor-non-control issues, and correction needs.
4.2.1(e) Research and technical investigation shall be source-aware, method-bounded, limitation-aware, confidence-aware where appropriate, public-safe, privacy-preserving, cybersecurity-compatible, protected-knowledge-aware, sovereignty-compatible, records-valid, and correctionable.
4.2.1(f) Research outputs shall not create public authority decisions, official public warnings, emergency commands, procurement decisions, finance-readiness, investment advice, insurance approval, underwriting, rating, guarantee, GRF recognition, GRA finance-readiness, certification, protocol entitlement, provider endorsement, sponsor approval, operational command, or execution authority by default.
4.2.1(g) Where research involves public authority data, personal information, rights-bearing data, Indigenous knowledge, local knowledge, protected knowledge, community-sensitive information, health-sensitive data, cyber-sensitive information, sensitive infrastructure information, controlled technology, cross-border participation, AI processing, or public-safe mapping, heightened legal, ethics, data, cybersecurity, public-safe, and correction controls shall apply.
4.2.1(h) The permitted research function shall be understood as a public-good truth and methods function, not a downstream implementation, market, finance, procurement, regulatory, or command function.
4.2.2 Evidence Collection, Evidence Structuring, Evidence Stewardship, Evidence Review, and Evidence Correction. 4.2.2(a) GCRI Canada may collect, receive, classify, structure, source-line, preserve, review, steward, compare, challenge, correct, supersede, withdraw, archive, and publish where public-safe evidence within its mission.
4.2.2(b) Evidence may include technical evidence, risk evidence, resilience evidence, observability evidence, public authority context evidence, host-readiness evidence, node evidence, community-safeguard evidence, Indigenous and protected knowledge restrictions, data-governance evidence, AI-governance evidence, cybersecurity evidence, infrastructure evidence, climate and disaster evidence, energy and water evidence, food and health systems evidence, biodiversity evidence, telecommunications evidence, compute evidence, model evidence, dataset evidence, benchmark evidence, system evidence, inference evidence, and correction evidence.
4.2.2(c) Evidence collection shall identify source, provenance, custody, contributor authority, lawful basis where applicable, classification, sensitivity, permitted use, prohibited use, review status, public-safe status, confidence where appropriate, limitations, data restrictions, public authority restrictions, finance-boundary restrictions, protected knowledge restrictions, AI-use restrictions, cybersecurity restrictions, retention, transfer limits, publication limits, and correction path where material.
4.2.2(d) Evidence structuring may include evidence records, source-lineage records, dataset cards, model cards, benchmark cards, system cards, inference records, observability records, Docket inputs, Grid inputs, proof inputs, controlled annexes, public-safe summaries, technical notes, risk registers, diligence gap maps, and correction logs.
4.2.2(e) Evidence stewardship may include maintaining repositories, evidence libraries, classification systems, metadata, provenance chains, version histories, custody records, access controls, review queues, challenge pathways, correction records, supersession records, withdrawal records, and archival records.
4.2.2(f) Evidence review may identify whether evidence is sufficient, insufficient, incomplete, disputed, contradicted, preliminary, stale, restricted, public-safe, low-confidence, AI-assisted, method-limited, context-limited, jurisdiction-limited, or correction-requiring.
4.2.2(g) Evidence correction may include correcting source references, metadata, classifications, limitations, public-safe status, confidence treatment, dataset records, model records, dashboard labels, maps, public-safe reports, public authority materials, finance-boundary materials, repository entries, and public claims.
4.2.2(h) Evidence work shall not itself create recognition, maturity, finance-readiness, certification, protocol effect, procurement approval, public authority action, public warning, emergency command, investment advice, insurance approval, provider endorsement, sponsor approval, operational control, or execution authority.
4.2.2(i) The controlling rule shall be that GCRI Canada may steward evidence rigorously and consequentially, but evidence remains evidence until a competent external authority lawfully attaches a downstream effect through its own process and record.
4.2.3 Methods Development, Methods Stewardship, Methods Versioning, and Methods Publication. 4.2.3(a) GCRI Canada may develop, test, refine, document, steward, version, publish where public-safe, restrict where required, supersede, withdraw, and correct methods within its mission.
4.2.3(b) Methods may include evidence-quality methods, source-lineage methods, confidence methods, corroboration methods, dispute methods, observability methods, public-safe publication methods, AI-use review methods, cyber review methods, data classification methods, public authority capacity-classification methods, finance-boundary language methods, provider-neutrality methods, sponsor-non-control methods, community-safeguard methods, Indigenous and protected knowledge safeguard methods, technical-baseline methods, benchmark methods, evaluation methods, test methods, correction methods, and after-action methods.
4.2.3(c) Methods development shall identify purpose, scope, assumptions, evidence requirements, data requirements, limitations, prohibited uses, public-safe status, review status, maintainer, version, dependencies, maintenance status, validation-supporting evidence where applicable, challenge pathway, correction pathway, supersession pathway, and withdrawal pathway.
4.2.3(d) Methods stewardship may include maintaining method libraries, method profiles, method notes, method comparison records, controlled vocabulary, implementation guidance, examples, known limitations, misuse warnings, public-safe release conditions, training materials, and correction records.
4.2.3(e) Methods versioning shall preserve effective dates, supersession records, change logs, rationale, review status, affected outputs, downstream notice needs, repository tags, archival copies, and correction pathways.
4.2.3(f) Methods publication may occur through public-safe reports, method notes, technical notes, Academy materials, controlled annexes, repository documentation, open technical baselines, APIs, schemas, software documentation, and public-good learning materials.
4.2.3(g) A GCRI Canada method shall not become a mandatory standard, certification scheme, regulatory requirement, procurement requirement, protocol rule, finance-readiness rule, recognition rule, professional opinion, public authority guidance, or execution instruction by default.
4.2.3(h) Where a method is adopted by GRF, GRA, Protocol Authority, a public authority, a National Consortium Company, a Project SPV, a provider, or another competent actor, the downstream effect shall arise from that actor’s lawful adoption and record, not from GCRI Canada authorship alone.
4.2.3(i) Methods shall remain challengeable, reviewable, limitation-aware, public-safe, correctionable, and protected against sponsor control, provider preference, public authority confusion, finance overclaim, certification implication, protocol implication, procurement implication, and execution drift.
4.2.4 Observability Methods, Nexus Observatory Methods, Sensor Evidence Methods, AI-RAN Evidence Methods, DePIN Evidence Methods, Digital Twin Assumption Methods, and Public-Safe Dashboard Methods. 4.2.4(a) GCRI Canada may develop, steward, document, review, publish where public-safe, restrict where required, and correct observability methods, Nexus Observatory methods, sensor evidence methods, AI-RAN evidence methods, O-RAN evidence methods, private wireless evidence methods, DePIN evidence methods, digital twin assumption methods, geospatial methods, dashboard methods, degraded-mode awareness methods, resilience indicator methods, and public-safe evidence-output methods.
4.2.4(b) Observability methods may support the interpretation of signals, evidence, sources, sensors, edge systems, compute systems, AI-RAN systems, DePIN systems, digital twins, dashboards, geospatial layers, APIs, model outputs, dataset records, benchmark records, infrastructure states, cyber indicators, climate indicators, disaster indicators, energy indicators, water indicators, telecommunications indicators, public authority context, and community-safeguard context.
4.2.4(c) Sensor evidence methods may address sensor provenance, calibration, custody, placement, coverage, latency, failure modes, spoofing risk, tampering risk, drift, false positives, false negatives, environmental context, data quality, cyber exposure, public-safe mapping, and correction.
4.2.4(d) AI-RAN, O-RAN, and private wireless evidence methods may address network context, signal integrity, edge inference, compute workload records, latency, throughput, coverage, spectrum context where applicable, data flows, security posture, AI-model assumptions, public authority boundary issues, telecom operator boundaries, and public-safe release restrictions.
4.2.4(e) DePIN evidence methods may address node identity, node contribution, signal authenticity, incentive distortion, proof limitations, validator or oracle risk, device custody, spoofing, sybil risk, token or incentive influence where applicable, data quality, public claims, and correction.
4.2.4(f) Digital twin assumption methods may address model scope, assumptions, calibration, data sources, update frequency, uncertainty, simplification, scenario limits, visualization limits, inferred states, sensitivity, public-safe mapping, and distinction between modeled representation and reality.
4.2.4(g) Public-safe dashboard methods may address status labels, issuer labels, confidence display, limitation display, public authority boundary language, public warning boundary language, finance-boundary language, provider-neutrality language, sponsor-non-control language, sensitive infrastructure controls, protected knowledge controls, geospatial redaction, accessibility, versioning, and correction.
4.2.4(h) Observability work shall not make GCRI Canada a sensor operator, telecom operator, AI-RAN operator, DePIN operator, digital twin operator, dashboard operator, cyber operations centre, public warning authority, emergency command body, public authority, infrastructure operator, procurement body, finance actor, provider, or execution actor by default.
4.2.4(i) Dashboards, maps, indicators, digital twins, alerts, scores, AI summaries, proof receipts, blockchain anchors, DePIN records, and sensor outputs shall be treated as evidence-supporting or learning-supporting artifacts, not as public warnings, official guidance, finance-readiness, recognition, certification, procurement approval, protocol effect, operational command, or execution instruction by default.
4.2.5 Ontology, Taxonomy, Schema, Data Dictionary, Controlled Vocabulary, and Semantic Interoperability Work. 4.2.5(a) GCRI Canada may develop, steward, maintain, publish where public-safe, restrict where required, localize, map, version, supersede, withdraw, and correct ontologies, taxonomies, schemas, data dictionaries, controlled vocabularies, semantic mappings, interoperability profiles, classification systems, and naming disciplines within its mission.
4.2.5(b) Ontology and semantic work may define and align terms concerning risk, resilience, evidence, confidence, limitation, observability, technical baselines, public-good software, public authority learning, public-safe publication, AI governance, cyber governance, data classification, public authority capacity, finance-boundary states, GRF recognition, GRA finance-readiness, protocol effect, provider participation, sponsor support, maturity, readiness, public-safe status, correction, supersession, withdrawal, and Nexus role separation.
4.2.5(c) Controlled vocabulary shall protect public meaning by distinguishing evidence from recognition, evidence support from finance-readiness, technical baseline from certification, conformance support from protocol effect, public authority learning from public authority action, dashboard display from public warning, proof receipt from truth, AI output from authority, public-good stewardship from ownership, and support from execution.
4.2.5(d) Schemas and data dictionaries may support machine-readable records, APIs, dashboards, repositories, model cards, dataset cards, benchmark cards, system cards, inference records, proof inputs, proof-receipt logic, public-safe reports, controlled annexes, Academy materials, and Nexus-compatible data exchange.
4.2.5(e) Semantic interoperability work may support localization without fragmentation and federation without centralization by enabling local, national, regional, Indigenous, community, public authority, technical, and legal context to be mapped without erasing local truth or transferring authority.
4.2.5(f) Ontology work shall identify source, scope, steward, version, status, public-safe status, adoption status, jurisdictional assumptions, language assumptions, translation status, equivalence notes, divergence notes, limitations, prohibited uses, and correction path where material.
4.2.5(g) Ontology, taxonomy, schema, or controlled-vocabulary authorship shall not create protocol authority, certification authority, recognition authority, finance-readiness authority, regulatory authority, procurement authority, public authority approval, provider endorsement, sponsor control, or execution authority by default.
4.2.5(h) Where semantic assets are adopted by another competent actor, the external effect shall arise from that actor’s lawful adoption and record, not from GCRI Canada authorship alone.
4.2.5(i) Where terminology creates overclaim, ambiguity, public authority confusion, finance signaling, certification implication, recognition implication, protocol implication, provider preference, sponsor control, or execution implication, GCRI Canada shall correct, restrict, relabel, supersede, withdraw, or clarify the relevant term or record.
4.2.6 Public-Good Software, Reference Architectures, APIs, Open Technical Baselines, Evaluation Harnesses, Test Harnesses, and Conformance-Supporting Tools. 4.2.6(a) GCRI Canada may design, develop, maintain, steward, publish where public-safe, restrict where required, license, document, test, evaluate, secure, release, deprecate, supersede, withdraw, and correct public-good software, reference architectures, APIs, open technical baselines, evaluation harnesses, test harnesses, conformance-supporting tools, data tools, dashboards, repository structures, documentation, and reference implementations.
4.2.6(b) Public-good software may support evidence collection, evidence structuring, source-lineage tracking, observability, controlled vocabulary, public-safe publication, model governance, dataset governance, benchmark management, inference records, correction records, public authority learning, Academy programs, technical baselines, Docket inputs, Grid inputs, proof inputs, and Nexus-compatible interoperability.
4.2.6(c) Reference architectures and open technical baselines may describe public-good expectations, evidence requirements, interoperability expectations, security practices, privacy practices, AI-governance expectations, data-governance expectations, repository practices, public-safe release expectations, documentation expectations, accessibility expectations, maintenance expectations, and correction pathways.
4.2.6(d) Evaluation harnesses and test harnesses may assist in reviewing technical behavior, evidence quality, dataset properties, model behavior, system behavior, interoperability, security posture, public-safe status, and baseline alignment, but passing a test or evaluation shall not constitute certification, recognition, finance-readiness, protocol conformance, procurement approval, public authority approval, provider endorsement, warranty, guarantee, or execution authorization by default.
4.2.6(e) Conformance-supporting tools may help competent actors organize evidence for conformance review, but such tools shall not create externally effective conformance states, role keys, smart licenses, protocol entitlements, certification status, procurement status, or public authority approval unless a competent authority lawfully attaches such effect through its own record.
4.2.6(f) Public-good technical assets shall identify version, steward, maintainer, license, source, dependencies, security status where material, public-safe status, support level, intended use, prohibited use, warranty limits, non-certification status, non-protocol-authority status, non-procurement status, non-finance status, correction path, supersession path, deprecation path, and withdrawal path.
4.2.6(g) Software and technical assets shall be protected against dependency capture, public-good enclosure, hidden control, vendor chokepoints, sponsor veto, provider preference, insecure dependencies, data leakage, AI misuse, and uncorrectable public reliance.
4.2.6(h) GCRI Canada shall not become a provider, vendor, managed-service operator, infrastructure operator, certification body, protocol authority, procurement actor, or execution actor merely because its software, APIs, baselines, test harnesses, or reference architectures are used by others.
4.2.6(i) Where technical assets are misused to imply authority or downstream effect, GCRI Canada shall correct documentation, restrict use, change labels, withdraw releases, supersede assets, issue public-safe clarification, notify affected actors where appropriate, or terminate the relevant interface.
4.2.7 Nexus Truth Engine Methods, Confidence Logic, Corroboration Methods, Disputed Evidence Handling, Spoof Signal Handling, and Correction Triggers. 4.2.7(a) GCRI Canada may develop, steward, document, test, publish where public-safe, restrict where required, and correct Nexus Truth Engine methods, confidence logic, corroboration methods, contradiction handling, disputed evidence handling, spoof signal handling, anomaly review, correction triggers, supersession triggers, withdrawal triggers, and public-safe clarification triggers.
4.2.7(b) Nexus Truth Engine methods may support the organization of evidence, comparison of sources, detection of inconsistency, confidence treatment, limitation disclosure, source-lineage preservation, dispute labeling, stale evidence identification, spoof signal risk identification, model-output limitation, dashboard-status review, and correction pathways.
4.2.7(c) Confidence logic may describe levels, ranges, categories, or qualitative treatment of uncertainty, but shall not convert uncertainty into guarantee, rating, underwriting, investment suitability, public authority approval, public warning, certification, recognition, protocol effect, procurement approval, or execution instruction.
4.2.7(d) Corroboration methods may identify whether independent sources, sensor records, documents, public authority records, model records, dataset records, benchmark records, field observations, repository records, or controlled records support, contradict, limit, or fail to support a claim.
4.2.7(e) Disputed evidence handling may include dispute labels, challenge records, review queues, controlled notes, public-safe summaries, limitation statements, temporary holds, restricted use, reclassification, correction, supersession, or withdrawal.
4.2.7(f) Spoof signal handling may address AI-generated deception, sensor spoofing, DePIN sybil risks, blockchain anchoring misuse, forged records, altered metadata, manipulated dashboards, adversarial inputs, synthetic media, false public authority references, false sponsor claims, false provider claims, false finance claims, and other misleading signals.
4.2.7(g) Correction triggers may arise from error, new evidence, challenge, stale evidence, changed conditions, method failure, data restriction, public-safe concern, public authority clarification, finance-boundary concern, provider overclaim, sponsor overclaim, protocol misdescription, certification implication, recognition overclaim, procurement implication, public warning implication, or execution implication.
4.2.7(h) Nexus Truth Engine methods shall not create a singular authority of truth, public authority decision, finance-readiness determination, recognition record, certification, protocol effect, procurement decision, public warning, emergency command, provider endorsement, sponsor approval, or execution action by default.
4.2.7(i) The permitted function is to improve truth discipline, confidence discipline, dispute discipline, and correctionability, not to convert GCRI Canada into an arbiter with downstream legal, market, public authority, financial, protocol, or execution effect.
4.2.8 Verifiable Compute, Verifiable Intelligence, Model Governance, Dataset Governance, Model Cards, System Cards, Benchmark Cards, Inference Records, and Compute Workload Records. 4.2.8(a) GCRI Canada may develop, steward, document, review, publish where public-safe, restrict where required, and correct methods and records concerning verifiable compute, verifiable intelligence, model governance, dataset governance, model cards, system cards, benchmark cards, inference records, compute workload records, evaluation records, AI-use records, and related technical accountability instruments.
4.2.8(b) Verifiable compute methods may address workload identity, compute environment, hardware or cloud context, workload provenance, execution records, integrity checks, logs, attestations, resource use, security posture, privacy posture, jurisdictional context, access control, and correction path, without converting workload evidence into certification, public authority approval, finance-readiness, protocol effect, or execution authority by default.
4.2.8(c) Verifiable intelligence methods may address model identity, model provenance, dataset provenance, prompt or input restrictions, retrieval sources, inference context, output review, human review, confidence treatment, limitations, hallucination risk, bias or error risk where material, public-safe status, and correction.
4.2.8(d) Model governance may include model registers, model cards, system cards, evaluation records, use-case restrictions, training restrictions, access restrictions, retention rules, safety reviews, cybersecurity reviews, public-safe publication reviews, inference records, human review requirements, and correction processes.
4.2.8(e) Dataset governance may include dataset cards, source lineage, lawful basis, consent or authority where applicable, permitted uses, prohibited uses, data quality, representativeness, bias concerns where material, privacy restrictions, Indigenous and community safeguards, public authority restrictions, sovereign data restrictions, cybersecurity restrictions, AI-use restrictions, retention, publication controls, and correction.
4.2.8(f) Benchmark cards and evaluation records may describe benchmark purpose, scope, dataset, method, assumptions, limitations, results, version, reproducibility conditions, review status, public-safe status, and correction path, but shall not create ranking, certification, procurement preference, finance-readiness, public authority approval, provider endorsement, or protocol conformance by default.
4.2.8(g) Inference records may preserve prompt context, source context, model context, retrieval context, output context, human review, limitation, public-safe status, publication decision, correction path, and downstream use restrictions where material.
4.2.8(h) Compute workload records may preserve workload purpose, source, data inputs, compute environment, security controls, access controls, logs, output status, public-safe status, review status, and correction path.
4.2.8(i) GCRI Canada shall not treat AI outputs, model cards, system cards, benchmark cards, inference records, compute records, attestations, hashes, proof receipts, or verification artifacts as authority beyond their recorded scope.
4.2.8(j) The permitted function is to make compute and intelligence more reviewable, accountable, auditable, and correctionable, not to create public authority action, financial advice, certification, recognition, protocol effect, procurement approval, operational command, or execution authority by default.
4.2.9 Public Authority Learning, Evidence Literacy, Technical Literacy, AI Literacy, Cyber Literacy, Scenario Learning, and Public-Safe Interpretation Support. 4.2.9(a) GCRI Canada may support public authority learning, evidence literacy, technical literacy, AI literacy, cyber literacy, scenario learning, observability interpretation, public-safe interpretation, systems-risk learning, resilience learning, controlled vocabulary learning, public-good software orientation, technical-baseline understanding, and correctionability learning.
4.2.9(b) Learning support may be provided to public authorities, universities, laboratories, civil society organizations, communities, Indigenous institutions, hosts, sponsors, providers, National Consortium Companies, Project SPVs, capital readers, media actors, Nexus actors, and other participants, provided that the learning remains non-executing, non-delegated, non-advisory where regulated advice would be implicated, public-benefit, role-bounded, public-safe, and correctionable.
4.2.9(c) Public authority learning may include explanation of evidence records, methods, observability outputs, dashboards, maps, digital twins, AI outputs, cyber indicators, technical baselines, public-good software, data governance, public-safe publication, limitations, confidence, correction, and Nexus role separation.
4.2.9(d) Scenario learning may include tabletop exercises, simulations, after-action reviews, evidence walkthroughs, dashboard walkthroughs, digital twin interpretation, risk scenario interpretation, degraded-mode scenario review, and public authority learning exercises, provided that such activities are not emergency command, public warning, operational direction, regulatory instruction, procurement decision, public finance approval, or execution control.
4.2.9(e) GCRI Canada may explain technology and evidence, but shall not issue official legal advice, regulatory guidance, public authority instructions, emergency orders, public warnings, public health orders, enforcement directions, procurement requirements, public finance approvals, investment advice, insurance advice, underwriting advice, ratings, certifications, recognition, protocol entitlements, or execution instructions.
4.2.9(f) Learning materials shall identify issuer, purpose, scope, audience, status, limitations, public-safe classification, non-delegation status, non-decision status, no-advice status where appropriate, review status, data restrictions, and correction path where material.
4.2.9(g) Attendance, completion, participation, fellowship, Academy enrollment, workshop participation, scenario participation, or technical literacy training shall not create regulated certification, public authority qualification, procurement eligibility, finance-readiness, provider endorsement, protocol entitlement, or execution authority by default.
4.2.9(h) Where learning support is misdescribed as authority, certification, public authority approval, finance-readiness, procurement approval, provider endorsement, public warning, emergency command, or execution approval, GCRI Canada shall correct, restrict, relabel, withdraw, supersede, or clarify the relevant materials or claims.
4.2.10 Academy Programs, Fellowships, Training, Competence Formation, Public-Good Learning Materials, and Workforce Pathways Without Regulated Certification by Default. 4.2.10(a) GCRI Canada may develop, operate, support, publish where public-safe, restrict where required, and correct Academy programs, fellowships, residencies, training, competence-formation activities, public-good learning materials, workforce pathways, technical literacy tracks, evidence literacy tracks, AI literacy tracks, cyber literacy tracks, public authority learning tracks, research training, and Nexus-compatible learning activities within its mission.
4.2.10(b) Academy programs may address evidence, methods, observability, ontology, controlled vocabulary, public-safe publication, data governance, AI governance, cybersecurity, technical baselines, public-good software, verifiable compute, verifiable intelligence, Nexus Truth Engine methods, Nexus Observatory methods, community safeguards, Indigenous and protected knowledge safeguards, public authority learning, public-good economics, correctionability, and role separation.
4.2.10(c) Fellowships, residencies, and training programs may support research capacity, technical competence, public authority learning, public-good software contribution, methods development, observability interpretation, Academy teaching, public-safe publication, and correction records, provided that participants remain role-bounded and do not acquire authority beyond the record.
4.2.10(d) GCRI Canada may issue attendance records, participation records, completion records, learning records, contribution records, fellowship appointment records, residency records, and competence-formation records where accurate, records-valid, and public-safe.
4.2.10(e) Such records shall not constitute regulated certification, professional licensure, legal qualification, engineering qualification, clinical qualification, accounting qualification, insurance qualification, investment qualification, public authority qualification, procurement qualification, provider certification, GRF recognition, GRA finance-readiness, protocol entitlement, role key, smart license, or externally effective conformance state by default.
4.2.10(f) Training materials shall not be used to imply that GCRI Canada authorizes participants to advise, regulate, procure, finance, insure, underwrite, rate, certify, recognize, publicly warn, command, operate, or execute.
4.2.10(g) Workforce pathways may support learning, readiness, technical literacy, public-benefit competence, and public-good participation, but shall not create employment promises, procurement preference, provider preference, public authority appointment, regulated credential, finance role, or execution role by default.
4.2.10(h) Academy and fellowship records shall identify participant status, scope, term, supervision, contribution, confidentiality, conflicts, data access, AI-use limits, cybersecurity obligations, IP treatment, public claims limits, publication rules, public-safe review requirements, and correction obligations where material.
4.2.10(i) Where Academy, fellowship, training, competence, or workforce materials create certification, qualification, employment, public authority, procurement, finance, protocol, provider, sponsor, or execution ambiguity, GCRI Canada shall correct, restrict, relabel, withdraw, supersede, or clarify the materials.
4.2.11 Public-Safe Publications, Technical Notes, Whitepapers, Controlled Annexes, Dashboards, Maps, Briefings, and Reports Within Records-Valid Limits. 4.2.11(a) GCRI Canada may prepare, maintain, publish where public-safe, restrict where required, correct, supersede, withdraw, archive, and issue public-safe publications, technical notes, whitepapers, research outputs, controlled annexes, dashboards, maps, briefings, reports, Academy materials, public authority learning materials, method notes, technical baselines, software documentation, correction notices, and public-safe clarifications.
4.2.11(b) Publications and outputs shall be records-valid. They shall be grounded in identified sources, methods, evidence status, review status, public-safe classification, limitations, scope, issuer authority, version, date, steward, correction path, and restrictions on use where material.
4.2.11(c) Controlled annexes may be used where public release would expose personal information, public authority restricted information, Indigenous knowledge, protected knowledge, community-sensitive information, cyber-sensitive information, sensitive infrastructure information, health-sensitive data, controlled technology, finance-sensitive information, or other material risk.
4.2.11(d) Dashboards and maps may support learning, observability, public-safe interpretation, technical literacy, evidence review, and correction, but shall not be designed or described as public warnings, official guidance, emergency commands, public authority decisions, finance-readiness determinations, procurement tools, provider rankings, certification tools, recognition tools, protocol effect surfaces, or execution systems by default.
4.2.11(e) Briefings may be provided to public authorities, GRF, GRA, Protocol Authority, Nexus entities, universities, hosts, sponsors, providers, capital readers, civil society, media, National Consortium Companies, Project SPVs, and other lawful actors, provided that the briefing is role-bounded, public-safe or controlled as appropriate, non-executing, non-advisory where regulated advice would be implicated, and correctionable.
4.2.11(f) Public materials shall use controlled vocabulary and shall distinguish evidence, method, observation, inference, public-safe summary, technical baseline, learning support, Docket input, Grid input, proof input, correction, GRF recognition, GRA finance-readiness, protocol effect, public authority action, procurement, certification, provider implementation, sponsor support, and execution.
4.2.11(g) Publications shall not overstate maturity, supportability, operational status, public authority adoption, national mandate, finance-readiness, recognition, certification, protocol effect, procurement status, provider approval, sponsor control, public warning authority, emergency command, or execution effect.
4.2.11(h) Where publication risk exists, GCRI Canada shall apply public-safe review, legal review where material, privacy review, cybersecurity review, protected knowledge review, public authority reference review, finance-boundary review, sponsor and provider review, and correction planning.
4.2.11(i) Where a publication, dashboard, map, briefing, or report becomes inaccurate, misleading, stale, overbroad, unsafe, restricted, misused, or authority-implying, GCRI Canada shall correct, supersede, withdraw, restrict, clarify, or notify affected actors where appropriate.
4.2.12 Interface Support to GRF, GRA, Nexus Standards / Protocol Authority, Nexus Network, Nexus Universe, Nexus Observatory, Nexus Rails, Nexus Grid, Nexus Academy, Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, National Consortium Companies, Project SPVs, Qualified Providers, Universities, Hosts, Sponsors, and Public Authorities Within Non-Execution Boundaries. 4.2.12(a) GCRI Canada may provide interface support to The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards or Protocol Authority, Nexus Network, Nexus Universe, Nexus Observatory, Nexus Rails, Nexus Grid, Nexus Academy, Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, National Consortium Companies, Project SPVs, qualified providers, universities, laboratories, research bodies, hosts, sponsors, donors, public authorities, civil society organizations, communities, Indigenous institutions, media actors, and other Nexus-compatible actors within non-execution boundaries.
4.2.12(b) Interface support may include evidence inputs, method inputs, observability inputs, ontology inputs, controlled vocabulary, technical baselines, public-good software, APIs, data tools, public-safe reports, controlled annexes, Academy materials, Docket inputs, Grid inputs, proof inputs, diligence gap maps, host-readiness evidence, node evidence, public authority learning materials, correction records, technical after-action records, repository interfaces, data interfaces, AI-use interfaces, cybersecurity interfaces, publication interfaces, and public claims controls.
4.2.12(c) Interface support to GRF may support registry, recognition, standing, maturity-record, claims-discipline, stakeholder-formation, public-safe reporting, and public-facing legitimacy processes, but GCRI Canada shall not issue GRF recognition, standing, maturity, claims approval, registry status, stakeholder-formation status, or public-facing legitimacy by default.
4.2.12(d) Interface support to GRA may support finance-readiness, capital-readability, proof-pack, insurance-readiness, capital-reader room, diligence gap, RNFD, NFD, UNFSD, or regulated-perimeter processes, but GCRI Canada shall not issue finance-readiness, investment advice, insurance approval, underwriting, ratings, guarantees, public finance approval, capital commitments, or transaction recommendations.
4.2.12(e) Interface support to Nexus Standards or Protocol Authority may support technical baselines, schemas, controlled vocabulary, evidence requirements, method profiles, conformance-supporting tools, proof-receipt logic, role-key logic, and smart-license logic, but GCRI Canada shall not issue protocol entitlements, role keys, smart-license rights, proof-receipt legal effect, or externally effective conformance states by default.
4.2.12(f) Interface support to Nexus Network, Nexus Universe, Nexus Observatory, Nexus Rails, Nexus Grid, and Nexus Academy may support public-good rail coherence, learning, observability, Docket discipline, Grid discipline, Academy learning, public-safe reporting, technical after-action, and correctionability, but GCRI Canada shall not become the owner, operator, event company, infrastructure operator, public warning authority, emergency command body, provider, public authority, procurement body, finance actor, or execution actor by default.
4.2.12(g) Interface support to Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, and Nexus Competence Cells may support localization, regional hazard evidence, national readiness, host readiness, community safeguards, public authority learning, technical baselines, and correctionability, but GCRI Canada shall not acquire national mandate authority, regional mandate authority, public authority delegation, public finance authority, procurement authority, or consortium governance by default.
4.2.12(h) Interface support to National Consortium Companies and Project SPVs may support public-good compatibility, evidence, methods, technical baselines, observability methods, public-safe reports, proof inputs, diligence gap maps, and correctionability, but GCRI Canada shall not own, operate, finance, manage, control, guarantee, insure, underwrite, rate, procure for, select providers for, direct, or execute those entities by default.
4.2.12(i) Interface support to qualified providers, universities, hosts, sponsors, and public authorities shall preserve provider neutrality, academic independence, host non-ownership, sponsor non-control, public authority non-delegation, data safeguards, cybersecurity, public-safe publication, public claims discipline, and correctionability.
4.2.12(j) All interface support shall be governed by records-valid instruments where material, including role, authority, scope, data, IP, confidentiality, cybersecurity, AI use, public-safe status, public claims limits, finance boundaries, public authority boundaries, provider-neutrality boundaries, sponsor-non-control boundaries, correction responsibility, liability allocation where appropriate, and termination.
4.2.12(k) No interface support shall be described, marketed, relied upon, or technically encoded as downstream authority unless a competent external actor lawfully creates that effect through its own process and record.
4.2.12(l) The controlling rule shall be that GCRI Canada may support many actors across the Nexus architecture through high-integrity public-good evidence, methods, observability, ontology, technical baselines, software, learning, publication, and correction, but all such support shall remain non-executing, role-bounded, records-valid, public-safe, and correctionable.
4.3 General Prohibited-Function Rule
4.3.1 No Prohibited Function by Charter Interpretation. 4.3.1(a) No provision of this Charter shall be interpreted to authorize GCRI Canada to perform a prohibited function. All Charter language shall be read subject to GCRI Canada’s constitutional identity as a Canadian public-benefit, nonprofit, non-share, non-distributing, non-charitable unless lawfully changed, non-executing evidence, methods, observability, ontology, public-good R&D, public-good software, open technical-baseline, public authority learning, public-safe publication, and correctionability institution.
4.3.1(b) A prohibited function includes any function that would convert GCRI Canada, by default or implication, into an emergency command body, public warning authority, public authority, regulator, enforcement body, procurement body, public finance authority, investment adviser, securities adviser, broker, finder, placement agent, lender, insurer, underwriter, rating agency, guarantor, fund, bank, clearing system, settlement system, payment intermediary, market infrastructure provider, certification body by default, recognition authority, protocol authority by default, provider selector, infrastructure operator, National Consortium Company, Project SPV, asset owner, execution manager, operational controller, or sovereign substitute.
4.3.1(c) Charter provisions authorizing research, evidence stewardship, methods development, observability support, ontology, public-good software, technical baselines, public authority learning, Academy programs, public-safe publications, Nexus Truth Engine methods, Nexus Observatory methods, interface support, data systems, AI systems, repositories, dashboards, maps, controlled annexes, briefings, or correction records shall not be interpreted as authorization to perform prohibited downstream functions.
4.3.1(d) Where a Charter provision could be read either as authorizing a permitted non-executing function or as authorizing a prohibited function, the permitted non-executing interpretation shall prevail.
4.3.1(e) No interpretive rule, definition, preamble, purpose clause, power clause, program clause, interface clause, or technical clause shall be used to enlarge GCRI Canada’s authority beyond its lawful, records-valid, public-benefit, non-executing, role-bounded mandate.
4.3.1(f) References to support, stewardship, evidence, methods, observability, technical baselines, public-good software, public authority learning, interface, handoff, Docket input, Grid input, proof input, public-safe report, dashboard, map, or technical contribution shall not be interpreted as approval, authorization, certification, recognition, finance-readiness, public authority action, procurement decision, protocol effect, public warning, emergency command, operational control, or execution.
4.3.1(g) Any Charter ambiguity that may create prohibited-function risk shall be resolved in favour of non-execution, legal separateness, role separation, public-safe publication, validity-by-record, correctionability, public authority boundary safety, finance-boundary safety, provider neutrality, sponsor non-control, privacy, cybersecurity, sovereignty compatibility, anti-capture, anti-enclosure, and institutional trust.
4.3.1(h) The Charter shall be construed as a boundary instrument as well as a mission instrument: it empowers GCRI Canada to steward upstream public-good truth and methods, and simultaneously prohibits GCRI Canada from becoming the downstream actor by interpretation.
4.3.2 No Prohibited Function by Bylaw, Policy, Program Charter, Council Terms, Technical Procedure, Publication, Dashboard, Map, Event, Contract, Sponsorship, Funding Agreement, or Informal Practice. 4.3.2(a) No Bylaw provision, policy, procedure, schedule, annex, program charter, council term of reference, committee mandate, technical procedure, repository rule, software release, publication, dashboard, map, digital twin, briefing, report, Academy material, public authority learning material, event material, contract, sponsorship agreement, funding agreement, donor condition, provider arrangement, host arrangement, public authority protocol, interface agreement, or informal practice shall authorize a prohibited function unless GCRI Canada has been lawfully restructured and the governing instruments have been lawfully amended to permit such role.
4.3.2(b) Implementing instruments shall remain subordinate to applicable law, the articles, the Bylaw, this Charter, mission lock, non-execution, role separation, public authority boundaries, finance boundaries, provider neutrality, sponsor non-control, public-safe publication, privacy, cybersecurity, protected knowledge safeguards, anti-capture, anti-enclosure, and correctionability.
4.3.2(c) A program charter may authorize evidence support, methods support, public authority learning, research, technical-baseline development, observability-methods support, public-good software, Academy activity, public-safe publication, or correction, but shall not authorize execution, emergency command, public warning, public authority decision-making, procurement, finance-readiness, investment advice, insurance approval, underwriting, rating, guarantee, certification by default, recognition, protocol entitlement, provider selection, infrastructure operation, or project control.
4.3.2(d) A council term of reference may authorize advice, review, learning, evidence challenge, method development, public-safe review, correction recommendations, or technical contribution, but shall not authorize a council to bind GCRI Canada, issue public authority decisions, make finance determinations, issue certification, grant recognition, create protocol effect, select providers, award procurement, approve investments, or execute projects unless a lawful and Charter-consistent authority record expressly provides and the function is not otherwise prohibited.
4.3.2(e) A technical procedure may govern how evidence, models, datasets, software, APIs, dashboards, maps, proof receipts, digital twins, or repositories operate, but shall not convert technical functionality into legal authority, public authority action, finance-readiness, certification, recognition, procurement approval, protocol effect, public warning, emergency command, or execution control.
4.3.2(f) A contract, sponsorship, funding agreement, or donor condition shall not grant a sponsor, donor, provider, vendor, host, public authority, capital reader, National Consortium Company, Project SPV, university, or other actor the ability to require GCRI Canada to perform a prohibited function.
4.3.2(g) Informal practice shall not create authority. Emails, chats, slides, meeting notes, public statements, media descriptions, repeated workflows, event language, repository usage, dashboard usage, public authority expectations, sponsor expectations, or provider expectations shall not authorize prohibited functions.
4.3.2(h) Where any implementing instrument or informal practice appears to authorize a prohibited function, GCRI Canada shall hold the activity, read down the instrument, correct the language, restrict reliance, supersede the instrument, terminate the practice, or refer the matter for legal, governance, and Board-level review where appropriate.
4.3.3 No Prohibited Function by Repeated Conduct. 4.3.3(a) Repeated conduct shall not create a prohibited function. GCRI Canada shall not acquire execution authority, public authority, finance authority, procurement authority, certification authority, recognition authority, protocol authority, provider-selection authority, public warning authority, emergency command authority, infrastructure-operation authority, market authority, or regulated professional authority merely because similar conduct has occurred more than once.
4.3.3(b) Repeated evidence support shall not become recognition. Repeated diligence support shall not become finance-readiness. Repeated technical-baseline support shall not become certification. Repeated dashboard review shall not become public warning. Repeated public authority learning shall not become delegated authority. Repeated provider testing shall not become procurement ranking. Repeated proof inputs shall not become proof-pack completion. Repeated repository releases shall not become protocol authority. Repeated public briefings shall not become official guidance. Repeated project support shall not become execution.
4.3.3(c) Repetition may increase reliance risk, but it shall not cure boundary defects. Where repeated conduct creates public meaning beyond the record, the proper response shall be correction, clarification, records discipline, public claims control, re-scoping, formalization within permitted limits, or termination, not recognition of unauthorized authority.
4.3.3(d) GCRI Canada shall monitor repeated practices that may create execution drift, public authority confusion, finance overclaim, provider preference, sponsor control, certification implication, recognition implication, protocol implication, procurement implication, public warning implication, emergency command implication, data overreach, AI overreliance, public-good enclosure, or uncorrectable reliance.
4.3.3(e) Where repeated conduct is lawful and mission-aligned but insufficiently documented, GCRI Canada shall document it through appropriate records, controls, role labels, public claims limits, and correction pathways.
4.3.3(f) Where repeated conduct is outside permitted non-executing functions, GCRI Canada shall cease, suspend, narrow, quarantine, route, or terminate the conduct and assess whether corrective notice, public-safe clarification, Board review, or legal review is required.
4.3.3(g) No person may rely on historical informality, prior tolerance, prior silence, prior technical practice, prior public claim, prior sponsor arrangement, prior provider participation, prior public authority attendance, or prior Nexus language to justify continuation of a prohibited function.
4.3.3(h) Repeated conduct shall be evidence requiring review, not authority creating power.
4.3.4 No Prohibited Function by Public Authority Attendance, Provider Participation, Sponsor Support, Host Support, Public Visibility, Media Description, Capital-Reader Interest, or Nexus Branding. 4.3.4(a) Public authority attendance, provider participation, sponsor support, host support, public visibility, media description, capital-reader interest, or Nexus branding shall not create a prohibited function.
4.3.4(b) Public authority attendance shall not create endorsement, adoption, procurement approval, funding approval, public finance approval, regulatory approval, official guidance, public warning, emergency command, public-private partnership, joint venture, sovereign obligation, or delegated public authority.
4.3.4(c) Provider participation shall not create preferred-provider status, endorsement, certification, procurement approval, public authority approval, finance-readiness, insurance-readiness, protocol entitlement, technical superiority, market ranking, operational approval, or GCRI Canada control.
4.3.4(d) Sponsor or donor support shall not create sponsor control, publication control, correction veto, provider preference, public authority access, finance-readiness influence, recognition purchase, certification purchase, protocol influence, public-good asset ownership, or execution opportunity.
4.3.4(e) Host support shall not create ownership of GCRI Canada outputs, public authority approval, institutional endorsement, legal control, publication control, correction control, provider preference, finance-readiness, recognition, certification, protocol effect, or execution authority.
4.3.4(f) Public visibility and media description shall not create authority. A headline, quote, interview, event program, documentary, social post, press release, public map, public dashboard, public-safe report, or media shorthand shall not convert GCRI Canada into a public authority, finance actor, certifier, recognizer, protocol authority, procurement body, emergency command body, public warning authority, provider selector, or execution actor.
4.3.4(g) Capital-reader interest shall not create investment advice, finance-readiness, insurance-readiness, underwriting, rating, guarantee, public finance approval, capital commitment, routeability, investor suitability, or transaction recommendation.
4.3.4(h) Nexus branding, Nexus diagrams, Nexus rail language, Nexus Universe participation, Nexus Network participation, Nexus Observatory participation, Nexus Rails, Nexus Grid, Nexus Academy, Docket, Grid, proof inputs, or public-good stack references shall not create downstream authority, legal merger, protocol effect, public authority effect, finance effect, recognition, certification, procurement approval, or execution consequence by default.
4.3.4(i) Where any such association creates prohibited-function implication, GCRI Canada shall correct, restrict, relabel, withdraw, supersede, clarify, notify affected actors where appropriate, or terminate the relevant use or relationship.
4.3.5 No Prohibited Function by Technical Capability, Data Access, Repository Control, AI Output, Dashboard Operation, Digital Twin Simulation, Proof Receipt, Blockchain Anchor, DePIN Record, or Observatory Signal. 4.3.5(a) Technical capability shall not create prohibited authority. GCRI Canada’s ability to collect evidence, structure data, run models, maintain repositories, operate dashboards, create maps, develop software, generate AI outputs, maintain digital twins, produce proof receipts, anchor records, analyze DePIN signals, or interpret observatory signals shall not authorize prohibited functions.
4.3.5(b) Data access shall not create decision authority. Access to public authority data, provider data, sponsor data, sensor data, geospatial data, infrastructure data, AI data, cyber data, finance-sensitive data, protected knowledge, community data, Indigenous knowledge, or public records shall not authorize GCRI Canada to issue decisions, warnings, approvals, certifications, recognition, finance-readiness, procurement outcomes, protocol effect, or execution instructions.
4.3.5(c) Repository control shall not create protocol authority, certification authority, recognition authority, public authority, finance authority, provider-selection authority, procurement authority, or execution authority. A repository tag, release, signature, hash, package, badge, issue status, pull-request approval, or version number shall not create downstream effect by default.
4.3.5(d) AI outputs shall not create authority. No AI-generated summary, classification, score, inference, translation, retrieval result, recommendation, anomaly flag, confidence estimate, or draft shall create public authority action, finance-readiness, investment advice, insurance approval, underwriting, rating, recognition, certification, procurement approval, protocol effect, public warning, emergency command, provider endorsement, sponsor control, operational command, or execution instruction.
4.3.5(e) Dashboard operation shall not create public warning, emergency command, public authority action, finance-readiness, certification, recognition, protocol effect, procurement approval, provider ranking, operational control, or execution authority. Dashboard colors, scores, maps, bands, alerts, layers, filters, and status states shall be treated as evidence or learning artifacts within recorded scope.
4.3.5(f) Digital twin simulation shall not create reality, command, approval, certification, finance-readiness, public warning, public authority decision, procurement outcome, protocol effect, or execution instruction. Digital twins shall be governed by assumptions, data limitations, model limits, scenario boundaries, public-safe controls, and correction paths.
4.3.5(g) Proof receipts, blockchain anchors, hashes, signatures, timestamps, DePIN records, attestations, and tamper-evident records may evidence record existence, timing, custody, process state, or technical event within defined scope, but shall not by themselves create truth, legal entitlement, public authority approval, finance-readiness, recognition, certification, procurement approval, protocol effect, public warning, emergency command, or execution authority.
4.3.5(h) Observatory signals may support learning, evidence review, risk interpretation, resilience understanding, public-safe reporting, and handoff to competent actors, but shall not create public warning, emergency command, public authority action, infrastructure operation, provider selection, finance-readiness, certification, recognition, protocol effect, procurement decision, or execution consequence by default.
4.3.5(i) Where technical artifacts are likely to be misunderstood as authority, GCRI Canada shall apply issuer labels, status labels, limitation statements, no-authority language, public-safe controls, access controls, metadata controls, visual design controls, correction paths, and public claims review.
4.3.6 No Prohibited Function by Emergency, Urgency, Crisis, Opportunity, Funding Pressure, Partner Expectation, Public Demand, or Strategic Importance. 4.3.6(a) Emergency, urgency, crisis, opportunity, funding pressure, partner expectation, public demand, public authority interest, sponsor expectation, provider readiness, media attention, capital-reader interest, national momentum, regional coordination, or strategic importance shall not authorize GCRI Canada to perform a prohibited function.
4.3.6(b) GCRI Canada may respond to urgent contexts by preserving evidence, clarifying methods, creating public-safe summaries, correcting records, routing evidence to competent public authorities, supporting public authority learning, restricting unsafe release, applying cybersecurity controls, protecting data, and documenting limitations, but it shall not issue emergency commands, public warnings, evacuation instructions, public health orders, regulatory directives, procurement decisions, funding approvals, finance-readiness determinations, investment recommendations, insurance approvals, certification, recognition, protocol entitlements, operational orders, or execution commands.
4.3.6(c) Public-benefit urgency shall not defeat role separation. The more urgent the context, the greater the need for issuer clarity, lawful authority, public-safe controls, public authority boundaries, finance boundaries, data protection, cybersecurity, protected knowledge safeguards, correctionability, and competent handoff.
4.3.6(d) Funding pressure shall not justify sponsor control, publication control, provider preference, public authority overclaim, finance signaling, certification implication, recognition implication, protocol implication, procurement implication, or execution drift.
4.3.6(e) Partner expectation shall not create GCRI Canada authority. A public authority request, provider request, sponsor request, capital-reader request, university request, host request, National Consortium Company request, Project SPV request, Nexus actor request, or media request shall not require GCRI Canada to act beyond its mandate.
4.3.6(f) Strategic importance shall not create power. A project may be nationally important, regionally important, financially important, technically important, climate-important, disaster-relevant, health-relevant, cyber-relevant, public authority-relevant, or Nexus-relevant, but GCRI Canada shall still remain non-executing.
4.3.6(g) Where urgent circumstances create pressure to exceed non-execution, GCRI Canada shall use refusal, re-scoping, quarantine, controlled release, handoff, escalation, Board review, legal review, or public authority routing rather than prohibited action.
4.3.6(h) The controlling principle shall be that urgency may accelerate lawful evidence support, but it shall not convert GCRI Canada into the actor legally responsible for downstream decisions.
4.3.7 No Prohibited Function by Implication, Estoppel, Apparent Authority, Reliance, Silence, or Failure to Correct. 4.3.7(a) No prohibited function shall arise by implication, estoppel, apparent authority, reliance, silence, inaction, delay, informal tolerance, failure to correct, repeated public description, technical integration, platform access, public presence, sponsor acknowledgement, provider participation, public authority attendance, or Nexus association.
4.3.7(b) Apparent reliance by public authorities, sponsors, providers, capital readers, investors, lenders, insurers, public finance bodies, universities, media actors, National Consortium Companies, Project SPVs, Nexus actors, communities, or the public shall not create authority where GCRI Canada has not lawfully and records-validly assumed a permitted role.
4.3.7(c) Silence shall not be consent to prohibited-function meaning. Failure to immediately correct an overclaim shall not authorize the overclaim. Delay in correction shall not make a misdescription true. Public repetition shall not convert unauthorized meaning into valid authority.
4.3.7(d) Apparent authority shall be actively prevented through written authority records, role labels, capacity classifications, controlled vocabulary, approved public claims, signature controls, access controls, repository labels, dashboard labels, public authority protocols, finance-boundary language, sponsor terms, provider terms, and correction mechanisms.
4.3.7(e) Where GCRI Canada becomes aware that any person is relying on GCRI Canada materials as if they create a prohibited function, GCRI Canada shall assess the reliance risk and take proportionate corrective action.
4.3.7(f) Corrective action may include internal correction, public-safe clarification, controlled clarification, withdrawal, supersession, access restriction, name-use restriction, dashboard relabeling, repository correction, API metadata correction, notice to affected actors, contract enforcement, suspension, termination, legal review, or Board review.
4.3.7(g) No person shall claim that GCRI Canada is estopped from enforcing non-execution merely because GCRI Canada previously provided evidence, attended meetings, appeared in materials, accepted support, reviewed dashboards, participated in public authority learning, allowed provider participation, issued public-safe reports, or failed to immediately object to an overbroad description.
4.3.7(h) The rule against prohibited functions by implication shall protect GCRI Canada’s legal form, public-benefit purpose, institutional trust, and public-good role from being silently transformed by reliance narratives.
4.3.8 Mandatory Correction Where GCRI Canada Is Described as Performing a Prohibited Function. 4.3.8(a) GCRI Canada shall require correction where it is described, depicted, cited, marketed, encoded, displayed, or relied upon as performing a prohibited function.
4.3.8(b) Correction shall be required where GCRI Canada is described as issuing public warnings, emergency commands, public authority decisions, regulatory approvals, permits, enforcement actions, procurement awards, funding approvals, public finance approvals, investment advice, securities recommendations, brokerage, lending, insurance approval, underwriting, ratings, guarantees, capital commitments, GRF recognition, GRA finance-readiness, certification, protocol entitlements, role keys, smart-license rights, conformance states with external force, provider endorsements, sponsor approvals, infrastructure operations, asset ownership decisions, project execution decisions, or operational commands.
4.3.8(c) Correction shall apply to websites, reports, whitepapers, technical notes, dashboards, maps, APIs, repositories, model cards, dataset cards, benchmark cards, system cards, inference records, proof receipts, blockchain anchors, DePIN records, public authority materials, sponsor materials, provider materials, investor materials, lender materials, insurance materials, public finance materials, procurement materials, media materials, Academy materials, event materials, Nexus documents, contracts, funding agreements, and public statements.
4.3.8(d) Correction shall identify the accurate role of GCRI Canada, including whether the relevant material is evidence support, methods support, observability support, technical-baseline support, public-good software support, public authority learning, Academy material, public-safe publication, controlled annex, Docket input, Grid input, proof input, correction record, or other non-executing function.
4.3.8(e) Correction shall be proportionate to reliance risk. Internal misdescription may require internal correction, training, and template revision. Public misdescription may require public-safe clarification. Finance-facing misdescription may require withdrawal and legal review. Public authority-confusing misdescription may require notice to affected public authorities. Emergency-command or public-warning misdescription may require urgent correction. Technical-system misdescription may require metadata, API, dashboard, repository, proof-receipt, or interface correction.
4.3.8(f) Where the misdescription was made by a sponsor, provider, host, public authority participant, university, contractor, media actor, National Consortium Company, Project SPV, Nexus actor, or other third party, GCRI Canada may require revision, restrict name use, suspend access, terminate participation, notify affected audiences, or seek legal remedies where appropriate.
4.3.8(g) Material corrections shall be recorded, including source, affected materials, public meaning, reliance risk, corrective action, notice decision, responsible actor, closeout, repeat pattern, and prevention measures.
4.3.8(h) Correction shall preserve the controlling message that GCRI Canada supports downstream actors through evidence and methods but does not itself perform prohibited downstream functions.
4.3.9 Mandatory Escalation Where Proposed Activity Is Ambiguous. 4.3.9(a) Where a proposed activity is ambiguous as to whether it is a permitted non-executing function or a prohibited function, GCRI Canada shall escalate the activity before material reliance, public release, contract execution, data transfer, AI processing, public authority engagement, finance-facing use, sponsor visibility, provider participation, technical deployment, or Nexus interface activation.
4.3.9(b) Ambiguity requiring escalation includes uncertainty about public authority status, public warning status, emergency command status, procurement effect, public finance effect, investment advice, insurance advice, underwriting, rating, guarantee, capital commitment, finance-readiness, recognition, certification, protocol effect, provider preference, sponsor control, data rights, AI authority, cybersecurity risk, protected knowledge, infrastructure operation, project execution, or authority to bind GCRI Canada.
4.3.9(c) Escalation may involve officer review, Board review, legal review, regulated-perimeter review, finance-boundary review, public authority capacity review, privacy review, cybersecurity review, AI governance review, research ethics review, protected knowledge review, export-control review, sanctions review, tax review, public claims review, technical review, or public-safe publication review, as appropriate.
4.3.9(d) Pending escalation, GCRI Canada shall apply interim controls proportionate to risk, including hold, data quarantine, access restriction, publication pause, AI-use pause, finance-language freeze, public authority reference hold, sponsor visibility hold, provider participation hold, repository hold, dashboard hold, contract hold, or controlled status.
4.3.9(e) Escalation records shall identify the proposed activity, actors, affected materials, jurisdictions, data categories, technical systems, public authority interfaces, finance interfaces, sponsor or provider involvement, ambiguity, risk assessment, interim controls, reviewer, decision, conditions, residual risk, correction path, and re-review trigger.
4.3.9(f) Ambiguity shall not be resolved by enthusiasm, opportunity, funding, speed, public authority interest, partner reassurance, sponsor pressure, provider readiness, media value, capital-reader interest, technical feasibility, or Nexus importance.
4.3.9(g) Where ambiguity remains after review, the narrower non-executing interpretation shall apply, or the activity shall be refused, re-scoped, quarantined, routed to a competent actor, or submitted to Board review.
4.3.9(h) Mandatory escalation shall be a core control for preventing mission drift, public authority confusion, finance overclaim, provider preference, sponsor control, certification implication, recognition implication, protocol overclaim, procurement implication, public-warning implication, and execution drift.
4.3.10 Mandatory Refusal, Re-Scoping, Quarantine, Handoff, or Board Review Where Prohibited-Function Risk Cannot Be Safely Resolved. 4.3.10(a) Where prohibited-function risk cannot be safely resolved through interpretation, limitation language, role labeling, data controls, public claims controls, contract controls, technical controls, publication controls, correction mechanisms, or competent review, GCRI Canada shall refuse, re-scope, quarantine, hand off, suspend, terminate, or submit the activity to Board review.
4.3.10(b) Refusal shall be required where an activity would require GCRI Canada to perform or appear to perform a prohibited function, including public authority decision-making, emergency command, public warning, finance-readiness, investment advice, insurance approval, underwriting, rating, guarantee, public finance approval, procurement decision, certification, recognition, protocol entitlement, provider selection, infrastructure operation, asset ownership, or project execution.
4.3.10(c) Re-scoping may be used where GCRI Canada can preserve lawful public-benefit value by limiting the activity to evidence support, methods support, observability support, technical-baseline support, public-good software support, public authority learning, Academy material, public-safe publication, controlled annex, Docket input, Grid input, proof input, correction record, or handoff.
4.3.10(d) Quarantine may be used where records, data, AI outputs, dashboards, maps, digital twins, proof receipts, repository releases, technical baselines, public claims, sponsor materials, provider materials, finance-facing materials, public authority materials, or Nexus interfaces cannot yet be classified safely.
4.3.10(e) Handoff may be used where a competent actor outside GCRI Canada is the appropriate body to decide, approve, warn, command, procure, finance, insure, underwrite, rate, certify, recognize, protocol-authorize, operate, or execute. Handoff shall be records-valid and shall preserve source, scope, limitation, public-safe status, data restrictions, public authority restrictions, finance-boundary restrictions, correction path, and non-execution status.
4.3.10(f) Board review shall be required where the risk is constitutional, material, repeated, public-facing, finance-facing, public authority-facing, emergency-adjacent, protocol-adjacent, certification-adjacent, recognition-adjacent, procurement-adjacent, sponsor-sensitive, provider-sensitive, data-sensitive, cyber-sensitive, protected-knowledge-sensitive, cross-border-sensitive, or capable of altering GCRI Canada’s public meaning.
4.3.10(g) GCRI Canada shall not proceed on the basis that prohibited-function risk is acceptable merely because the activity is high-value, funded, urgent, requested by a respected partner, supported by a public authority, technically feasible, media-visible, nationally important, regionally important, capital-relevant, or Nexus-aligned.
4.3.10(h) Refusal, re-scoping, quarantine, handoff, suspension, termination, or Board review shall be recorded where material, including issue, risk, affected actors, affected records, interim controls, decision, authority, conditions for reopening, correction needs, notice decision, and re-review trigger.
4.3.10(i) Where prohibited-function risk has already produced public reliance, GCRI Canada shall assess whether correction, public-safe clarification, controlled clarification, withdrawal, notice, access restriction, data restriction, repository correction, dashboard correction, public authority notification, finance-facing notification, or legal review is required.
4.3.10(j) The controlling rule shall be that GCRI Canada shall lose an opportunity rather than lose its constitutional boundary; it shall narrow or decline work rather than become an execution, public authority, finance, procurement, certification, recognition, protocol, provider-selection, public-warning, emergency-command, or market actor by implication.
4.4 No Emergency Command
4.4.1 GCRI Canada Does Not Command Emergencies. 4.4.1(a) GCRI Canada shall not command emergencies. GCRI Canada shall not act as an emergency command body, incident command body, emergency operations centre, public safety command body, public health command body, disaster response authority, evacuation authority, rescue authority, shelter authority, logistics command body, field response authority, emergency communications authority, public warning authority, or sovereign emergency actor by default.
4.4.1(b) GCRI Canada’s role in emergency, disaster, public safety, public health, cyber incident, infrastructure failure, climate hazard, energy disruption, water disruption, food system disruption, telecommunications disruption, AI system incident, DePIN incident, digital twin incident, sensor incident, or other crisis-related contexts shall be limited to permitted non-executing functions, including evidence support, methods support, observability-methods support, technical-baseline support, public authority learning, public-safe interpretation, Academy learning, controlled briefings, technical after-action support, correction records, and records-valid handoff to competent actors.
4.4.1(c) GCRI Canada shall not become an emergency commander by reason of public-benefit purpose, technical expertise, observability capability, dashboard visibility, AI output, sensor access, public authority attendance, public authority request, community concern, media attention, sponsor support, provider participation, Nexus Observatory involvement, Nexus Universe exercise, Nexus Network participation, or urgent public need.
4.4.1(d) Emergency command authority belongs to competent public authorities, emergency management bodies, public safety agencies, public health authorities, infrastructure operators, utilities, community authorities where applicable, Indigenous authorities where applicable, and other lawful emergency actors acting through their own legal authority and records.
4.4.1(e) GCRI Canada may help competent actors understand evidence, methods, limitations, assumptions, confidence, public-safe status, data restrictions, cybersecurity risks, protected knowledge risks, and correction pathways, but it shall not decide what emergency action must be taken.
4.4.1(f) No GCRI Canada record, report, dashboard, map, digital twin, AI output, observability signal, proof receipt, technical note, controlled annex, public authority briefing, Academy material, table-top exercise material, Nexus Universe exercise material, or Nexus Observatory output shall be treated as emergency command unless a competent emergency authority has separately and lawfully issued its own command.
4.4.1(g) Where emergency-command ambiguity arises, the matter shall be held, clarified, restricted, relabeled, corrected, withdrawn, superseded, or routed to the competent authority before reliance is permitted.
4.4.2 No Operational Control Over Emergency Responders, Public Safety Actors, Public Health Actors, Utilities, Infrastructure Operators, Public Authorities, Community Authorities, Hosts, Providers, National Companies, Project SPVs, or Field Teams. 4.4.2(a) GCRI Canada shall not exercise operational control over emergency responders, public safety actors, public health actors, utilities, infrastructure operators, telecommunications operators, cyber incident responders, public authorities, community authorities, Indigenous authorities, hosts, providers, National Consortium Companies, Project SPVs, contractors, field teams, volunteers, logistics actors, shelter actors, rescue actors, or any other response actor by default.
4.4.2(b) Operational control includes authority to direct personnel, deploy resources, assign tasks, approve operations, command field teams, manage incident objectives, control infrastructure, control communications, operate emergency systems, allocate supplies, direct utilities, prioritize restoration, control shelters, direct evacuations, manage rescue, issue operational orders, or determine public safety actions.
4.4.2(c) GCRI Canada may observe, learn, document, structure evidence, support after-action review, maintain public-safe evidence records, provide methods, support technical interpretation, and route evidence to competent actors, but such activities shall not constitute operational control.
4.4.2(d) Where GCRI Canada supports a public authority, emergency actor, host, provider, National Consortium Company, Project SPV, or field team, that actor shall remain responsible for its own authority, operations, safety, staffing, command, field decisions, communications, public warnings, legal compliance, equipment, infrastructure, data handling, cybersecurity, insurance, liabilities, and corrections.
4.4.2(e) GCRI Canada shall not use access to dashboards, maps, observability systems, sensor feeds, AI systems, repositories, public authority rooms, radio systems, communications platforms, incident data, field reports, or technical tools to direct emergency operations.
4.4.2(f) GCRI Canada shall not be described as the controller, operator, dispatcher, incident commander, emergency manager, public safety lead, public health lead, infrastructure operator, utilities coordinator, field response lead, or command authority for any emergency response unless GCRI Canada has been lawfully restructured and expressly authorized through competent legal authority, which is not its default role under this Charter.
4.4.2(g) Where operational-control confusion arises, GCRI Canada shall clarify roles, restrict access, revise public materials, correct labels, route the matter to the competent operator or authority, and record the correction.
4.4.3 No Dispatch, Tasking, Deployment, Evacuation, Rescue, Shelter, Supply, Logistics, Field Response, or Incident-Command Authority. 4.4.3(a) GCRI Canada shall not have dispatch, tasking, deployment, evacuation, rescue, shelter, supply, logistics, field response, incident-command, public safety directive, public health directive, or emergency communications authority by default.
4.4.3(b) GCRI Canada shall not dispatch responders, assign personnel, direct field teams, deploy equipment, activate shelters, allocate supplies, determine evacuation routes, issue rescue instructions, direct logistics, activate emergency resources, command utilities, order shutdowns, direct restoration, or control emergency operations.
4.4.3(c) GCRI Canada shall not issue instructions to communities, households, businesses, public authorities, first responders, public health actors, utilities, infrastructure operators, providers, hosts, National Consortium Companies, Project SPVs, or field teams concerning emergency action.
4.4.3(d) GCRI Canada may identify evidence that appears relevant to emergency response and may route that evidence to competent actors through a records-valid, public-safe, privacy-preserving, cybersecurity-compatible, protected-knowledge-aware handoff.
4.4.3(e) Any handoff shall identify source, scope, limitations, confidence where appropriate, public-safe status, data restrictions, public authority restrictions, cybersecurity restrictions, protected knowledge restrictions, timestamp, recipient, correction path, and the fact that GCRI Canada is not issuing emergency command.
4.4.3(f) GCRI Canada may support scenario learning, exercise design, after-action review, evidence reconstruction, dashboard interpretation, sensor-evidence analysis, and technical learning, but it shall not convert those learning functions into live command authority.
4.4.3(g) Where any person requests GCRI Canada to dispatch, task, deploy, evacuate, rescue, shelter, supply, direct logistics, command field response, or control an incident, GCRI Canada shall refuse the command role and route the matter to the competent emergency or public authority actor where appropriate.
4.4.4 No Emergency Operating Order, Command Instruction, Public Safety Directive, or Incident-Control Determination. 4.4.4(a) GCRI Canada shall not issue emergency operating orders, command instructions, public safety directives, public health directives, incident-control determinations, emergency operating procedures for live response actors, evacuation orders, shelter-in-place directions, rescue commands, infrastructure shutdown orders, utility restoration priorities, enforcement directions, or emergency public communications by default.
4.4.4(b) GCRI Canada materials shall not be written, formatted, displayed, distributed, or visually designed to mimic official emergency orders, public warning notices, public safety directives, public health orders, evacuation instructions, incident command forms, regulatory notices, enforcement notices, or emergency operations communications unless a competent public authority issues such materials in its own capacity.
4.4.4(c) Technical notes, public-safe reports, dashboards, maps, digital twin outputs, AI summaries, observability records, sensor records, DePIN records, proof receipts, and Academy materials may support learning or evidence interpretation, but shall not be treated as emergency operating orders.
4.4.4(d) GCRI Canada may develop methods for classifying evidence, displaying risk indicators, protecting public-safe information, structuring handoffs, or supporting after-action learning, but such methods shall not command emergency operations.
4.4.4(e) Where materials are intended for competent emergency authorities, they shall be labeled as evidence support, methods support, public authority learning, technical interpretation, controlled briefing, public-safe report, after-action material, or handoff record, as applicable.
4.4.4(f) Where a public authority uses GCRI Canada materials to inform its own emergency operating order, command instruction, public safety directive, or incident-control determination, the public authority shall be responsible for the order, authority, adoption, communication, implementation, correction, and legal effect.
4.4.4(g) Where GCRI Canada materials are misused as emergency orders or command instructions, GCRI Canada shall require correction, restrict distribution, notify competent actors where appropriate, withdraw or supersede materials, and preserve correction records.
4.4.5 Emergency-Management Participation as Learning, Evidence, Simulation, Observability, or Technical Support Only. 4.4.5(a) GCRI Canada participation in emergency-management contexts shall be limited to learning, evidence, simulation, observability-methods support, technical interpretation, public-safe reporting, Academy support, after-action review, correction support, and records-valid handoff.
4.4.5(b) Emergency-management participation may include scenario learning, evidence review, dashboard walkthroughs, digital twin interpretation, sensor-evidence methods, degraded-mode awareness, resilience indicator review, public-safe mapping methods, cyber incident learning, AI incident learning, infrastructure risk learning, public authority capacity learning, community safeguard review, and technical after-action analysis.
4.4.5(c) Such participation shall not create command authority, public warning authority, official guidance, emergency response authority, regulatory authority, procurement authority, finance authority, insurance authority, provider-selection authority, infrastructure-operation authority, or execution authority.
4.4.5(d) Emergency-management materials shall identify issuer, purpose, scope, scenario status if applicable, live-status if applicable, public-safe classification, limitations, non-command status, non-warning status, data restrictions, public authority restrictions, review status, and correction path.
4.4.5(e) Where emergency-management learning is conducted with public authorities, public authority capacity shall be classified and recorded. Participation as learner, observer, technical reviewer, data contributor, host, funder, or scenario participant shall not imply official action unless the competent public authority separately records official action.
4.4.5(f) Where emergency-management participation involves communities, Indigenous institutions, vulnerable groups, health-sensitive data, public safety information, sensitive infrastructure, or cyber-sensitive information, GCRI Canada shall apply heightened privacy, cybersecurity, public-safe, protected knowledge, and do-no-harm controls.
4.4.5(g) Where emergency-management participation is likely to be misunderstood as command, GCRI Canada shall re-scope, relabel, restrict, defer, route to competent authorities, or decline participation.
4.4.6 Emergency Simulations, Drills, Tabletop Exercises, Nexus Universe Exercises, and Observatory Tests as Non-Command Activities. 4.4.6(a) Emergency simulations, drills, tabletop exercises, Nexus Universe exercises, Nexus Observatory tests, digital twin exercises, dashboard exercises, AI incident exercises, cyber exercises, infrastructure exercises, public authority learning exercises, and scenario-based learning activities involving GCRI Canada shall be non-command activities.
4.4.6(b) Exercises may be designed to improve evidence literacy, technical literacy, public authority learning, observability interpretation, data governance, AI governance, cyber literacy, public-safe publication, correctionability, inter-institutional coordination, community safeguards, and after-action learning.
4.4.6(c) Exercise materials shall distinguish simulated conditions from live conditions, training assumptions from operational facts, scenario outputs from public warnings, simulated alerts from official alerts, learning roles from command roles, and after-action insights from binding public authority decisions.
4.4.6(d) No exercise shall authorize GCRI Canada to command real responders, dispatch resources, issue public warnings, direct public authorities, approve emergency plans, determine evacuation, instruct communities, control infrastructure, procure services, select providers, approve funding, or execute operational response.
4.4.6(e) Nexus Universe exercises and Nexus Observatory tests shall not be described as official emergency drills unless a competent public authority has lawfully designated them as such through its own record. Even where public authorities participate, GCRI Canada’s role shall remain learning, evidence, methods, observability, technical support, public-safe interpretation, and correction.
4.4.6(f) Exercise outputs may include after-action notes, evidence gap maps, method gaps, dashboard limitation notes, public-safe reports, technical recommendations, correction records, Academy materials, and controlled annexes, but shall not constitute emergency orders, official guidance, regulatory requirements, procurement requirements, public authority adoption, certification, recognition, protocol effect, finance-readiness, or execution instruction.
4.4.6(g) Where an exercise creates public confusion, GCRI Canada shall restrict public materials, clarify exercise status, revise labels, remove emergency-command language, correct public claims, and notify affected actors where appropriate.
4.4.7 Public Authority and Emergency Management Capacity Classification. 4.4.7(a) Public authority and emergency management participation in GCRI Canada emergency-related activities shall require capacity classification where participation is material, public-facing, data-bearing, observability-related, exercise-related, emergency-adjacent, public-warning-adjacent, public authority-facing, or capable of creating public reliance.
4.4.7(b) Capacity classification shall identify whether a public authority or emergency actor participates as observer, learner, technical participant, evidence contributor, data contributor, scenario participant, exercise controller in its own capacity, host, funder, public safety learner, emergency management learner, public health learner, infrastructure-context contributor, regulator attending in non-regulatory capacity, public finance reader, procurement observer, or official decision-maker in its own separate capacity.
4.4.7(c) Capacity classification shall identify what the public authority or emergency actor is not doing, including whether the actor is not endorsing, adopting, procuring, funding, regulating, issuing guidance, issuing warnings, commanding, enforcing, approving public finance, delegating authority, forming a public-private partnership, entering a joint venture, or creating sovereign obligations.
4.4.7(d) Public authority or emergency management capacity shall not be inferred from title, uniform, agency name, logo, meeting attendance, data contribution, questions, comments, dashboard review, participation in exercises, photographs, quotations, or public visibility.
4.4.7(e) Capacity classification shall be recorded in meeting records, exercise records, public authority protocols, data contribution records, public-safe report records, public communications, dashboard labels, Academy materials, Nexus Universe materials, Nexus Observatory materials, and correction records where material.
4.4.7(f) Where capacity is uncertain, GCRI Canada shall apply the narrowest accurate classification and shall avoid public claims that imply official action.
4.4.7(g) Where capacity is misclassified, GCRI Canada shall correct the record, revise materials, clarify with the affected public authority or emergency actor where appropriate, restrict reliance, and preserve correction records.
4.4.8 Separation Between Decision-Support Materials and Emergency Command Decisions. 4.4.8(a) GCRI Canada shall maintain strict separation between decision-support materials and emergency command decisions.
4.4.8(b) Decision-support materials may include evidence records, technical notes, public-safe reports, controlled annexes, observability summaries, dashboards, maps, digital twins, AI-assisted summaries, sensor records, cyber indicators, degraded-mode indicators, resilience indicators, scenario notes, after-action reports, public authority learning materials, and correction records.
4.4.8(c) Emergency command decisions include decisions to warn, evacuate, shelter, rescue, deploy, dispatch, direct field teams, allocate supplies, activate emergency plans, close roads, shut down infrastructure, restore utilities, issue public health orders, issue public safety directions, communicate official alerts, enforce restrictions, or command response operations.
4.4.8(d) GCRI Canada may prepare, explain, update, correct, or hand off decision-support materials, but shall not make emergency command decisions.
4.4.8(e) Decision-support materials shall identify their source, scope, status, assumptions, limitations, confidence where appropriate, public-safe classification, data restrictions, public authority restrictions, non-command status, non-warning status, review status, responsible steward, version, and correction path.
4.4.8(f) Where decision-support materials are used by a competent emergency authority, the emergency authority shall remain responsible for its own decision, legal authority, adoption, communication, implementation, correction, and public accountability.
4.4.8(g) GCRI Canada shall avoid design choices that blur decision support and command, including official-warning colors, emergency alert formats, imperative public instructions, command-form layouts, unsupported “go/no-go” language, public authority seals without approval, evacuation-style mapping, or operational directive wording.
4.4.8(h) Where separation between decision support and emergency command becomes unclear, GCRI Canada shall relabel, restrict, redesign, correct, withdraw, supersede, or route the material to competent authority before further reliance.
4.4.9 Public-Safe Language for Emergency Contexts. 4.4.9(a) GCRI Canada shall use public-safe language in emergency-related contexts to preserve non-command status, prevent public warning confusion, protect public safety, and maintain trust.
4.4.9(b) Emergency-related GCRI Canada materials shall use language such as “evidence support,” “technical interpretation,” “observability summary,” “scenario learning,” “after-action learning,” “public authority learning,” “method note,” “controlled briefing,” “public-safe report,” “non-command material,” “non-warning material,” “for competent authority review,” “limitations apply,” “not an emergency instruction,” or equivalent role-bounded language where appropriate.
4.4.9(c) GCRI Canada shall avoid language such as “evacuate now,” “shelter now,” “official warning,” “emergency order,” “command instruction,” “public safety directive,” “public health order,” “incident command,” “dispatch,” “deployment order,” “go/no-go,” “all clear,” “unsafe,” “safe,” “mandatory,” “authorized,” “approved,” or equivalent emergency-command language unless quoting or referencing a competent public authority record with appropriate attribution and context.
4.4.9(d) Public-safe language shall identify issuer and role. A statement made by GCRI Canada shall not be framed as a public authority statement. A statement made by a public authority shall not be framed as GCRI Canada command.
4.4.9(e) Emergency-related public materials shall include limitations sufficient to prevent inappropriate reliance by the public, public authorities, media actors, providers, sponsors, National Consortium Companies, Project SPVs, capital readers, or communities.
4.4.9(f) Where public release may cause panic, expose sensitive infrastructure, reveal protected knowledge, disclose personal information, compromise cyber safety, imply public warning, misdirect public behavior, or interfere with competent authorities, GCRI Canada shall restrict, delay, redact, aggregate, route, or decline publication.
4.4.9(g) Media statements, social posts, dashboards, maps, briefings, slides, event materials, Academy materials, and Nexus materials in emergency contexts shall undergo public claims review and public-safe review proportionate to risk.
4.4.9(h) Where emergency language is inaccurate, overbroad, command-implying, public-warning-implying, public authority-confusing, or unsafe, GCRI Canada shall correct, withdraw, supersede, restrict, or issue public-safe clarification.
4.4.10 Correction of Any Statement Implying GCRI Canada Emergency Command Authority. 4.4.10(a) GCRI Canada shall correct any statement, depiction, dashboard state, map, AI output, digital twin display, proof receipt, public-safe report, briefing, event material, media description, sponsor material, provider material, public authority material, Nexus document, repository entry, API field, contract, email, social post, or public communication implying that GCRI Canada has emergency command authority.
4.4.10(b) Emergency command overclaim includes any implication that GCRI Canada commands emergencies, directs responders, dispatches teams, orders evacuations, instructs the public, controls utilities, operates emergency infrastructure, manages incident command, issues public warnings, issues public health orders, issues public safety directives, determines emergency status, authorizes rescue, controls shelter, allocates supplies, or determines official response actions.
4.4.10(c) Correction shall identify the accurate role of GCRI Canada as evidence support, methods support, observability support, technical interpretation, public authority learning, scenario learning, public-safe reporting, after-action support, correction support, or records-valid handoff, as applicable.
4.4.10(d) Correction shall be proportionate to risk. Internal misdescription may require template correction and training. Public misdescription may require public-safe clarification. Public authority-confusing misdescription may require notice to affected public authorities. Media-amplified misdescription may require media correction request. Dashboard or map misdescription may require interface redesign. Emergency-command or public-warning misdescription may require urgent withdrawal or restriction.
4.4.10(e) Where a third party refuses to correct emergency-command overclaim, GCRI Canada may restrict name use, suspend access, terminate participation, withdraw materials, notify competent authorities, notify affected audiences, or seek legal remedies where appropriate.
4.4.10(f) Material corrections shall be recorded, including the source, affected material, public meaning, reliance risk, corrective action, notice decision, responsible actor, closeout, repeat pattern, and prevention measures.
4.4.10(g) Repeated emergency-command overclaim shall not normalize command authority. It shall create a stronger duty to revise emergency-context language, dashboard labels, map design, public authority protocols, exercise materials, sponsor terms, provider terms, media protocols, Nexus Observatory materials, and public-safe publication controls.
4.4.10(h) The controlling rule shall be that GCRI Canada may support emergency-related learning and evidence integrity, but emergency command remains with competent emergency and public authority actors.
4.5 No Official Public Warning
4.5.1 GCRI Canada Does Not Issue Official Public Warnings. 4.5.1(a) GCRI Canada shall not issue official public warnings. GCRI Canada shall not act as a public warning authority, emergency alerting authority, public safety notification authority, public health warning authority, disaster warning authority, wildfire warning authority, flood warning authority, climate hazard warning authority, infrastructure safety warning authority, cyber emergency warning authority, telecommunications emergency authority, evacuation authority, shelter authority, road closure authority, utility instruction authority, or emergency communications authority by default.
4.5.1(b) GCRI Canada’s role in warning-adjacent contexts shall be limited to permitted non-executing functions, including evidence support, methods support, observability-methods support, technical interpretation, public authority learning, public-safe reporting, scenario learning, Academy materials, controlled briefings, after-action learning, correction support, and records-valid handoff to competent public authorities or other responsible actors.
4.5.1(c) Official public warnings shall remain the responsibility of competent public authorities, emergency management bodies, public safety agencies, public health authorities, Indigenous authorities where applicable, local authorities, infrastructure operators where lawfully responsible, utilities where lawfully responsible, cyber authorities where lawfully responsible, and other competent actors acting under their own legal authority and records.
4.5.1(d) GCRI Canada shall not become a public warning authority by reason of observability capability, dashboard visibility, map publication, digital twin simulation, AI output, sensor access, DePIN signal interpretation, AI-RAN signal interpretation, blockchain anchoring, proof receipts, public authority attendance, emergency-management participation, public concern, media attention, sponsor support, provider participation, Nexus Observatory involvement, Nexus Universe activity, or urgent public-benefit need.
4.5.1(e) No GCRI Canada report, dashboard, map, briefing, public-safe publication, controlled annex, technical note, Academy material, AI output, digital twin display, observability signal, sensor record, proof receipt, blockchain anchor, DePIN record, AI-RAN signal, confidence score, repository entry, API field, or public statement shall be treated as an official public warning unless a competent public authority has separately and lawfully issued such warning through its own process and record.
4.5.1(f) GCRI Canada may identify, classify, interpret, summarize, and route evidence that may be relevant to public safety, but it shall not instruct the public, declare official danger, issue emergency alerts, direct protective action, or substitute for public authority warning processes.
4.5.1(g) Where public-warning ambiguity arises, GCRI Canada shall apply the narrowest non-warning interpretation, restrict release where necessary, clarify issuer and role, relabel materials, route evidence to competent authorities, correct public claims, withdraw or supersede materials where required, and preserve correction records.
4.5.1(h) The controlling rule shall be that GCRI Canada may strengthen public-safe evidence and public authority learning, but official public warning authority remains with competent public and emergency actors.
4.5.2 No Evacuation Instructions, Emergency Alerts, Public Health Orders, Safety Commands, Infrastructure-Use Directives, Shelter Directives, Curfew Instructions, Road Closure Instructions, Utility Instructions, or Public Emergency Directives. 4.5.2(a) GCRI Canada shall not issue evacuation instructions, emergency alerts, public health orders, public safety commands, infrastructure-use directives, shelter directives, curfew instructions, road closure instructions, utility instructions, boil-water advisories, power-use directives, telecommunications-use directives, cyber emergency directives, transport directives, school closure directives, community movement instructions, or public emergency directives.
4.5.2(b) GCRI Canada shall not direct individuals, communities, businesses, public authorities, public safety actors, public health actors, utilities, infrastructure operators, schools, hospitals, care facilities, transportation operators, telecommunications operators, cyber operators, hosts, providers, National Consortium Companies, Project SPVs, or field teams to take or refrain from emergency action.
4.5.2(c) GCRI Canada shall not use imperative language that could reasonably be understood as official emergency instruction, including commands to evacuate, shelter, avoid roads, close facilities, shut down infrastructure, use or not use utilities, follow curfews, take medical action, deploy resources, activate field response, or change public behavior during emergencies.
4.5.2(d) GCRI Canada may prepare evidence summaries, hazard-context notes, technical interpretations, public-safe learning materials, controlled briefings, observability summaries, scenario materials, and after-action reports for competent authorities or responsible actors, provided that such materials are clearly labeled as non-warning, non-command, and decision-supporting.
4.5.2(e) Where GCRI Canada materials refer to official warnings, orders, instructions, advisories, closures, curfews, evacuation zones, shelter directions, public health orders, or infrastructure-use directives issued by competent authorities, the materials shall identify the issuing authority, source record, date, scope, limitations, and GCRI Canada’s non-issuer role.
4.5.2(f) GCRI Canada shall not paraphrase, restate, visualize, map, summarize, or distribute public authority warnings in a manner that changes their meaning, expands their scope, creates new instructions, obscures the issuing authority, or causes reliance on GCRI Canada rather than the competent authority.
4.5.2(g) Where urgent evidence suggests a need for official warning or emergency instruction, GCRI Canada may hand off evidence to competent authorities through records-valid procedures, but shall not issue the warning or instruction itself.
4.5.2(h) Where any GCRI Canada material is understood or likely to be understood as an evacuation instruction, emergency alert, public health order, safety command, infrastructure-use directive, shelter directive, curfew instruction, road closure instruction, utility instruction, or public emergency directive, GCRI Canada shall restrict, correct, withdraw, supersede, or clarify the material immediately where material risk exists.
4.5.3 Observability Outputs Do Not Become Official Alerts by Default. 4.5.3(a) Observability outputs produced, supported, displayed, analyzed, routed, or interpreted by GCRI Canada shall not become official alerts by default.
4.5.3(b) Observability outputs may include signals, indicators, sensor readings, geospatial layers, dashboard states, degradation indicators, anomaly flags, model outputs, digital twin outputs, DePIN signals, AI-RAN signals, cyber indicators, infrastructure indicators, climate indicators, flood indicators, wildfire indicators, health indicators, energy indicators, water indicators, telecommunications indicators, compute indicators, public authority context records, and public-safe summaries.
4.5.3(c) Observability outputs may support evidence review, public authority learning, technical interpretation, public-safe reporting, scenario analysis, after-action review, correction, and handoff to competent actors, but shall not constitute official warning, public alert, emergency notice, public authority directive, operational instruction, or public safety command.
4.5.3(d) GCRI Canada shall ensure that observability outputs identify issuer, source, method, status, scope, public-safe classification, limitations, uncertainty, data restrictions, update frequency where material, non-warning status, non-command status, responsible steward, and correction path.
4.5.3(e) Automated generation, real-time display, high-confidence status, map visibility, red or urgent color use, public dashboard access, public authority room access, public-sector participation, sponsor support, provider integration, or repeated operational use shall not transform observability outputs into official alerts.
4.5.3(f) GCRI Canada shall not design observability outputs to resemble official emergency alerts, public warning systems, public health notices, public safety advisories, cyber emergency notifications, evacuation maps, or public authority command dashboards unless the competent public authority issues or controls the warning function in its own capacity.
4.5.3(g) Where observability outputs are routed to public authorities or emergency actors, the handoff shall preserve source, limitations, public-safe status, confidence where appropriate, data restrictions, and the fact that GCRI Canada is not issuing an official alert.
4.5.3(h) Where observability outputs create official-alert confusion, GCRI Canada shall relabel, restrict, redesign, withdraw, supersede, correct, or route the output to competent authority before further reliance.
4.5.4 Dashboards Do Not Become Public Warning Systems by Default. 4.5.4(a) Dashboards produced, maintained, supported, designed, interpreted, or displayed by GCRI Canada shall not become public warning systems by default.
4.5.4(b) Dashboards may support public authority learning, evidence review, observability interpretation, public-safe reporting, research, Academy learning, scenario exercises, technical after-action review, data literacy, AI literacy, cyber literacy, risk interpretation, resilience understanding, and correctionability.
4.5.4(c) Dashboard colors, indicators, alerts, filters, layers, status bands, confidence scores, event flags, trend lines, maps, model outputs, anomaly labels, degraded-mode states, digital twin displays, API fields, or notification features shall not constitute official public warnings, emergency alerts, evacuation instructions, public health orders, safety commands, public authority decisions, procurement decisions, finance-readiness, certification, recognition, protocol effect, or execution instructions.
4.5.4(d) Public-facing or public authority-facing dashboards shall include role-bounded labels, issuer identification, status labels, scope limits, limitations, public-safe classification, non-warning language, non-command language, data restrictions, refresh or latency notes where material, correction pathways, and source references where appropriate.
4.5.4(e) GCRI Canada shall avoid dashboard designs that mimic official emergency alert systems, public safety command boards, public health order systems, evacuation-zone tools, road-closure systems, utility command systems, cyber incident command boards, or government warning platforms unless the competent public authority operates the warning function in its own legal capacity.
4.5.4(f) If a dashboard is used by a competent public authority to inform official warnings, the public authority shall remain responsible for warning issuance, legal authority, communications, implementation, updates, correction, and public accountability.
4.5.4(g) GCRI Canada shall not allow sponsors, providers, media actors, public authorities, hosts, National Consortium Companies, Project SPVs, or Nexus actors to describe a GCRI Canada dashboard as an official public warning system unless a competent public authority has lawfully established such status and GCRI Canada’s role is accurately limited.
4.5.4(h) Where dashboard use creates public warning confusion, GCRI Canada shall restrict access, redesign visual language, revise labels, add limitation statements, suspend publication, withdraw the dashboard, correct public claims, or notify competent actors where appropriate.
4.5.5 Maps Do Not Become Official Hazard Notices by Default. 4.5.5(a) Maps produced, supported, interpreted, displayed, or published by GCRI Canada shall not become official hazard notices by default.
4.5.5(b) Maps may support research, public-safe interpretation, public authority learning, technical literacy, observability methods, hazard evidence review, climate and disaster learning, infrastructure context, community safeguards, Indigenous and protected knowledge safeguards, scenario learning, after-action learning, and correctionability.
4.5.5(c) A GCRI Canada map shall not constitute an official hazard notice, evacuation map, emergency alert map, public health notice, safety order, regulatory map, infrastructure-use directive, road-closure map, utility instruction, public warning map, insurance map, finance-readiness map, procurement map, certification map, recognition map, protocol map, or execution map by default.
4.5.5(d) Maps shall identify source, method, date, version, scope, public-safe status, scale, resolution, limitations, uncertainty, data gaps, jurisdictional context, sensitive infrastructure controls, protected knowledge controls, community safeguard controls, non-warning status, non-command status, and correction path where material.
4.5.5(e) GCRI Canada shall not publish maps that expose sensitive infrastructure, protected knowledge, Indigenous knowledge, community-sensitive information, personal information, health-sensitive information, cyber-sensitive information, or security-sensitive locations beyond authorized and public-safe scope.
4.5.5(f) Where maps use or reference public authority boundaries, hazard zones, evacuation zones, flood zones, wildfire zones, public health regions, critical infrastructure layers, or emergency management layers, the maps shall distinguish public authority source layers from GCRI Canada evidence or interpretive layers.
4.5.5(g) GCRI Canada shall not alter, simplify, recolor, reclassify, overlay, or summarize public authority maps in a way that creates new official meaning, expands official warning scope, obscures competent authority, or causes public reliance on GCRI Canada as issuer.
4.5.5(h) Where a map could reasonably be mistaken for an official hazard notice, GCRI Canada shall restrict release, use controlled annexes, add clear labels, redesign the map, route to competent authority, delay publication, withdraw the map, or issue correction.
4.5.6 AI Outputs, Digital Twins, Sensors, DePIN Signals, AI-RAN Signals, Blockchain Anchors, Proof Receipts, or Confidence Scores Do Not Become Official Warnings by Default. 4.5.6(a) AI outputs, digital twins, sensor readings, DePIN signals, AI-RAN signals, O-RAN signals, private wireless signals, blockchain anchors, hashes, signatures, timestamps, proof receipts, confidence scores, anomaly scores, model scores, benchmark scores, geospatial scores, risk scores, resilience scores, and observability indicators shall not become official warnings by default.
4.5.6(b) AI outputs may assist with summarization, classification, translation, retrieval, anomaly identification, scenario analysis, evidence organization, limitation identification, or drafting, but shall not issue public warnings, emergency instructions, public authority decisions, public health orders, evacuation instructions, safety commands, finance-readiness, certification, recognition, procurement approval, protocol effect, or execution instructions.
4.5.6(c) Digital twins may model conditions, simulate scenarios, visualize assumptions, support learning, identify possible dependencies, and assist after-action review, but shall not determine reality, official hazard status, public warning status, evacuation need, operational command, infrastructure instruction, public authority decision, or execution action.
4.5.6(d) Sensor, DePIN, AI-RAN, O-RAN, and private wireless signals may support evidence and observability, but shall not become official public alerts merely because they are real-time, high-confidence, geographically specific, machine-readable, provider-integrated, public authority-viewed, or dashboard-displayed.
4.5.6(e) Blockchain anchors, hashes, signatures, timestamps, attestations, and proof receipts may evidence record existence, timing, custody, integrity, process state, or technical event within defined scope, but shall not create truth, official warning, legal entitlement, public authority approval, finance-readiness, recognition, certification, procurement approval, protocol effect, emergency command, or execution authority.
4.5.6(f) Confidence scores may express evidence confidence within a defined method, but shall not become public safety instruction, emergency status, guarantee, rating, insurance opinion, investment conclusion, regulatory finding, procurement finding, provider ranking, certification, recognition, or protocol conformance.
4.5.6(g) Where automated or technical outputs are displayed in public, public authority, emergency-management, infrastructure, cyber, health, climate, wildfire, flood, disaster, or safety contexts, GCRI Canada shall ensure human review, limitation statements, public-safe controls, non-warning language, non-command language, and correction pathways proportionate to risk.
4.5.6(h) Where automated or technical outputs create official-warning confusion, GCRI Canada shall pause publication, restrict access, revise labels, add human review, route to competent authority, correct metadata, withdraw outputs, supersede records, or issue public-safe clarification.
4.5.7 Public Authority Review Required Before Any Public-Warning-Like Output Is Released in a Public Authority Context. 4.5.7(a) Any GCRI Canada output that could reasonably be perceived as public-warning-like in a public authority context shall require public authority review, public-safe review, and role-boundary review before release, unless the output is withheld, restricted, or clearly confined to internal non-warning use.
4.5.7(b) Public-warning-like outputs may include hazard maps, risk dashboards, emergency-context briefings, infrastructure risk summaries, wildfire indicators, flood indicators, disaster indicators, public health risk summaries, cyber incident summaries, critical infrastructure summaries, AI incident summaries, DePIN or AI-RAN incident summaries, digital twin scenario displays, sensor alert displays, public safety briefings, or urgent public-safe reports.
4.5.7(c) Public authority review shall identify whether the competent authority has approved use of its name, data, symbols, warning references, maps, quotes, emergency classifications, public health classifications, public safety classifications, official boundaries, official instructions, or official warning context.
4.5.7(d) Public authority review shall not convert GCRI Canada into a public authority. Review by a public authority shall be capacity-classified and shall not imply adoption, endorsement, public warning issuance, regulatory approval, procurement approval, funding approval, public finance approval, public-private partnership, emergency command, or sovereign obligation unless the public authority separately and lawfully records such act.
4.5.7(e) Where public authority review is unavailable, incomplete, unclear, time-constrained, or insufficient, GCRI Canada shall restrict public release, remove public-warning-like elements, generalize or aggregate content, use controlled annexes, add limitation language, route evidence to competent authorities, or delay publication.
4.5.7(f) Public-warning-like outputs shall be designed to avoid official-warning confusion, including through issuer labels, non-warning labels, non-command labels, purpose statements, public-safe classifications, audience restrictions, limitations, data-source labels, public authority capacity labels, versioning, and correction paths.
4.5.7(g) If a competent public authority elects to issue a public warning based in part on GCRI Canada evidence, the public authority shall issue the warning in its own name, under its own authority, through its own communications channels, and with its own legal responsibility.
4.5.7(h) Public authority review records shall identify reviewer, capacity, materials reviewed, conditions, approvals or non-approvals, restrictions, public-safe treatment, required labels, publication decision, correction path, and re-review triggers where material.
4.5.8 Public-Safe Disclaimers for Hazard, Risk, Emergency, Health, Cyber, Infrastructure, Climate, Wildfire, Flood, Disaster, or Safety Materials. 4.5.8(a) GCRI Canada shall use public-safe disclaimers, limitation statements, issuer labels, role labels, and correction-path language for hazard, risk, emergency, health, cyber, infrastructure, climate, wildfire, flood, disaster, safety, public authority, public health, public safety, or public-warning-adjacent materials where necessary to prevent improper reliance.
4.5.8(b) Public-safe disclaimers shall state, where appropriate, that the material is evidence support, methods support, observability summary, technical interpretation, scenario learning, public authority learning, public-safe report, controlled briefing, or after-action material, and not an official public warning, emergency command, public health order, public safety directive, evacuation instruction, infrastructure-use directive, regulatory approval, procurement decision, finance-readiness determination, certification, recognition, protocol effect, or execution instruction.
4.5.8(c) Disclaimers shall be prominent enough for the risk. A high-risk dashboard, map, emergency-context briefing, public authority-facing material, media-facing material, or public-facing hazard report shall not rely on hidden, legalistic, or inaccessible disclaimers where public misunderstanding is foreseeable.
4.5.8(d) Disclaimers shall not be used to excuse unsafe publication. Where material remains likely to cause harmful reliance, panic, public authority confusion, infrastructure exposure, protected knowledge exposure, cyber risk, privacy harm, or official-warning confusion despite disclaimers, GCRI Canada shall restrict, redesign, delay, route, or decline publication.
4.5.8(e) Public-safe disclaimers shall be paired with public-safe design, including clear issuer labels, visual distinction from official alert systems, accessible language, controlled vocabulary, source labels, update status, limitation display, public authority source attribution where applicable, and correction path.
4.5.8(f) Materials that are translated, summarized, visualized, converted into dashboards, excerpted into media materials, embedded into websites, shared in public authority rooms, or reused by third parties shall preserve disclaimer meaning and role-boundary language.
4.5.8(g) GCRI Canada shall correct or withdraw materials where disclaimers are removed, weakened, contradicted, hidden, mistranslated, visually undermined, or overridden by public claims.
4.5.8(h) The purpose of public-safe disclaimers shall be public protection, role clarity, and trust—not liability avoidance alone.
4.5.9 Escalation Where GCRI Canada Materials Could Be Mistaken for Official Public Warnings. 4.5.9(a) Where GCRI Canada materials could reasonably be mistaken for official public warnings, emergency alerts, evacuation instructions, public health orders, safety commands, infrastructure-use directives, road closure instructions, utility instructions, cyber emergency notices, or public emergency directives, the matter shall be escalated before public release or continued reliance.
4.5.9(b) Escalation shall be required for materials involving urgent hazard information, public-facing maps, dashboards with alert-like signals, real-time observability feeds, public authority data, public health data, sensitive infrastructure information, wildfire or flood indicators, cyber incident indicators, digital twin emergency scenarios, AI-generated hazard summaries, DePIN or AI-RAN signals, public safety briefings, or media-ready safety language.
4.5.9(c) Escalation may involve public-safe publication review, public authority capacity review, legal review, privacy review, cybersecurity review, protected knowledge review, research review, public claims review, technical review, communications review, officer review, or Board review depending on risk.
4.5.9(d) Pending escalation, GCRI Canada shall apply interim controls, including publication hold, access restriction, public authority routing, data quarantine, map restriction, dashboard restriction, AI-output hold, visual redesign, language revision, disclaimer strengthening, media hold, sponsor or provider materials hold, and public claims freeze.
4.5.9(e) Escalation records shall identify the material, risk, audience, likely public meaning, data sources, public authority involvement, public-safe classification, interim controls, reviewer, decision, conditions, publication status, correction path, and re-review trigger.
4.5.9(f) Materials shall not be released on the basis of urgency, public interest, media timing, sponsor pressure, provider readiness, public authority informal interest, public visibility, technical capability, or Nexus importance if official-warning confusion remains unresolved.
4.5.9(g) Where escalation confirms public-warning risk that cannot be safely mitigated, GCRI Canada shall refuse publication, restrict to controlled circulation, route to competent public authorities, remove warning-like elements, or withdraw the material.
4.5.9(h) Escalation shall preserve the distinction between public-safe evidence support and official public warning.
4.5.10 Correction, Withdrawal, or Public Clarification Where Public Warning Confusion Occurs. 4.5.10(a) Where public warning confusion occurs, GCRI Canada shall correct, withdraw, supersede, restrict, relabel, redesign, publicly clarify, issue controlled clarification, notify competent authorities, notify affected audiences, or take other appropriate remedial action proportionate to the risk.
4.5.10(b) Public warning confusion includes any situation in which GCRI Canada materials are described, interpreted, displayed, circulated, cited, embedded, reposted, summarized, visualized, or relied upon as official public warnings, emergency alerts, evacuation instructions, public health orders, safety commands, infrastructure-use directives, road closure instructions, utility instructions, cyber emergency notices, or public emergency directives.
4.5.10(c) Public warning confusion may arise from text, maps, dashboards, digital twins, AI outputs, observability signals, sensor feeds, DePIN records, AI-RAN signals, blockchain anchors, proof receipts, confidence scores, red or alert-like visuals, public authority logos, public authority attendance, public authority data references, media headlines, sponsor materials, provider materials, public authority materials, Nexus documents, Academy materials, briefings, websites, repositories, APIs, or social posts.
4.5.10(d) Correction shall identify the accurate role of GCRI Canada, the non-warning status of the material, the competent authority for official warnings where known, the limits of the material, the source and date of the material, and the correction path.
4.5.10(e) Withdrawal shall be required where continued availability creates material risk of public harm, public authority confusion, emergency confusion, cyber risk, sensitive infrastructure exposure, protected knowledge exposure, privacy harm, or reliance on GCRI Canada as warning authority.
4.5.10(f) Public clarification shall be used where public reliance or public misunderstanding is likely or has occurred. Controlled clarification may be used where the affected audience is limited, confidential, public authority-restricted, data-sensitive, cyber-sensitive, or protected-knowledge-sensitive.
4.5.10(g) Where third parties have caused or amplified public warning confusion, GCRI Canada may require correction, restrict name use, suspend access, terminate participation, withdraw materials, notify competent authorities, notify affected audiences, seek media correction, or pursue legal remedies where appropriate.
4.5.10(h) GCRI Canada shall preserve records of material public warning confusion, including source, affected materials, public meaning, reliance risk, corrective action, notice decision, responsible actor, closeout, repeat pattern, and prevention measures.
4.5.10(i) Repeated public warning confusion shall not normalize warning authority. It shall require strengthened public-safe publication controls, dashboard labels, map design rules, AI-output controls, public authority protocols, media protocols, sponsor terms, provider terms, Nexus Observatory language, and emergency-context training.
4.5.10(j) The controlling rule shall be that GCRI Canada may produce and steward public-safe evidence, but it shall not issue official public warnings; where confusion occurs, correction shall be mandatory and public safety shall prevail.
4.6 No Regulation or Enforcement Authority
4.6.1 GCRI Canada Does Not Regulate. 4.6.1(a) GCRI Canada shall not regulate. GCRI Canada shall not act as a regulator, supervisory authority, enforcement authority, licensing authority, permitting authority, compliance authority, inspection authority, audit authority with public-law effect, sanctioning authority, adjudicative authority, administrative tribunal, public standards-enforcement body, public order issuer, or public duty enforcer by default.
4.6.1(b) GCRI Canada may support regulatory understanding only through permitted non-executing functions, including evidence support, methods support, observability interpretation, technical literacy, AI literacy, cyber literacy, public authority learning, technical-baseline support, public-safe reporting, controlled vocabulary, public-good software, research outputs, Academy materials, correction records, and records-valid handoff to competent public authorities or other responsible actors.
4.6.1(c) GCRI Canada shall not determine whether any person, project, provider, technology, public authority, host, sponsor, National Consortium Company, Project SPV, dataset, model, system, infrastructure, facility, product, service, or program complies with law, regulation, permit, license, public standard, public order, procurement rule, public finance condition, public safety obligation, public health obligation, telecommunications obligation, cyber obligation, environmental obligation, AI governance obligation, or other public-law requirement.
4.6.1(d) GCRI Canada shall not become a regulator by reason of technical expertise, public-benefit purpose, public authority attendance, public authority data access, public authority learning role, public authority funding, public-safe publication, observability capability, dashboard visibility, AI output, map publication, technical-baseline authorship, software release, repository stewardship, Nexus proximity, sponsor support, provider participation, media description, or repeated reliance by public authorities.
4.6.1(e) Public authorities, regulators, permitting bodies, enforcement bodies, courts, tribunals, inspection bodies, procurement authorities, public finance authorities, and other competent actors shall retain their own legal authority, decision processes, duties, discretion, records, public accountability, and correction obligations.
4.6.1(f) Where GCRI Canada materials are used by a regulator or public authority, the competent regulator or public authority shall remain responsible for any regulatory act, compliance position, enforcement position, permit decision, license decision, public standard adoption, official guidance, public order, or public-law consequence.
4.6.1(g) No GCRI Canada output shall be described as regulatory approval, compliance determination, official guidance, safe harbor, enforcement position, public standard, licensing decision, permit decision, inspection result, legal compliance opinion, or public-law determination unless a competent public authority or regulator has separately and lawfully issued that act through its own record.
4.6.1(h) Where regulatory ambiguity arises, GCRI Canada shall apply the narrowest non-regulatory interpretation, clarify its role, restrict public claims, revise labels, route the matter to competent authority, correct overclaims, and preserve correction records.
4.6.2 No Enforcement of Law, Regulation, Permit, License, Compliance Obligation, Public Standard, Public Order, or Public Duty. 4.6.2(a) GCRI Canada shall not enforce law, regulation, permit, license, compliance obligation, public standard, public order, public duty, public authority condition, enforcement undertaking, regulatory settlement, public health order, public safety order, environmental order, cyber order, telecommunications order, infrastructure order, procurement condition, public finance condition, or other legally binding public-law requirement.
4.6.2(b) GCRI Canada shall not investigate for enforcement, issue notices of violation, impose penalties, issue administrative monetary penalties, suspend licenses, revoke permits, order remediation, compel production, compel testimony, seize property, issue subpoenas, conduct inspections with legal force, issue enforcement letters, enter consent orders, require compliance plans, or determine public-law liability.
4.6.2(c) GCRI Canada may identify evidence gaps, method gaps, data gaps, technical risks, public-safe concerns, cyber risks, AI risks, observability concerns, documentation weaknesses, control deficiencies, or correction needs, but such identification shall not be enforcement.
4.6.2(d) GCRI Canada may support a competent public authority through evidence, methods, technical literacy, public-safe reporting, controlled annexes, or public authority learning, but the public authority shall remain responsible for any enforcement action, compliance position, official request, public order, sanction, remedy, or legal consequence.
4.6.2(e) GCRI Canada shall not use enforcement-like language such as “violation,” “non-compliant,” “illegal,” “penalty,” “sanctioned,” “ordered,” “required by GCRI Canada,” “enforcement action,” “regulatory breach,” “permit breach,” “license revoked,” “compliance failed,” or equivalent language unless accurately referencing a competent authority record or clearly labeling a non-regulatory evidence observation.
4.6.2(f) Evidence records, dashboards, maps, risk indicators, model outputs, benchmark results, technical notes, public-safe reports, proof receipts, blockchain anchors, repository labels, or AI-generated outputs shall not be used by GCRI Canada as enforcement instruments.
4.6.2(g) Where GCRI Canada identifies facts that may be relevant to lawful enforcement by another actor, it may route or hand off evidence to the competent authority through records-valid, public-safe, privacy-preserving, cybersecurity-compatible, and protected-knowledge-aware procedures, but shall not itself enforce.
4.6.2(h) Where GCRI Canada materials are misused as enforcement instruments, GCRI Canada shall correct, restrict, withdraw, supersede, notify affected actors where appropriate, and preserve correction records.
4.6.3 No Granting, Denial, Suspension, Revocation, or Approval of Public Permits, Licenses, Regulatory Status, Safe Harbors, Compliance Determinations, or Enforcement Positions. 4.6.3(a) GCRI Canada shall not grant, deny, suspend, revoke, amend, condition, approve, reject, validate, invalidate, certify, recognize, or determine public permits, licenses, approvals, regulatory statuses, safe harbors, compliance determinations, inspection outcomes, public-law authorizations, enforcement positions, public standards compliance, regulatory exemptions, public finance approvals, procurement approvals, or public authority permissions.
4.6.3(b) GCRI Canada shall not issue any document, dashboard state, map label, technical baseline, report, certificate, badge, score, API status, proof receipt, repository label, model card, dataset card, system card, benchmark card, inference record, or public statement that could reasonably be understood as granting or denying public-law status.
4.6.3(c) GCRI Canada may produce technical evidence, methods, baseline alignment notes, documentation status, public-safe reports, gap maps, confidence notes, observability summaries, and correction records, but such outputs shall remain non-regulatory and shall not determine compliance status by default.
4.6.3(d) A GCRI Canada statement that evidence is present, absent, incomplete, stale, disputed, restricted, public-safe, method-limited, or correction-requiring shall not mean that a permit should be granted, a license should be issued, a compliance obligation is satisfied, a safe harbor applies, an enforcement position is warranted, or a public standard is met.
4.6.3(e) Where a competent public authority or regulator chooses to consider GCRI Canada materials in its own process, the competent authority shall be responsible for any permit, license, regulatory status, safe harbor, compliance determination, enforcement position, public standard, approval, denial, suspension, revocation, condition, or public-law consequence.
4.6.3(f) GCRI Canada shall not allow its name, marks, evidence records, technical baselines, public-safe reports, dashboards, maps, Academy materials, software, or Nexus materials to be used to imply regulatory approval, license status, permit status, safe harbor, compliance determination, or enforcement position.
4.6.3(g) Where materials risk being interpreted as public-law status determinations, GCRI Canada shall add non-regulatory language, restrict use, seek public authority clarification, route to competent authority, revise labels, withdraw materials, or refuse publication.
4.6.3(h) Where a public-law status overclaim has occurred, GCRI Canada shall correct the overclaim, notify affected actors where appropriate, and preserve correction records.
4.6.4 No Regulatory Guidance by GCRI Canada by Default. 4.6.4(a) GCRI Canada shall not issue regulatory guidance by default. GCRI Canada technical notes, public-safe reports, whitepapers, Academy materials, learning materials, method notes, observability summaries, technical baselines, software documentation, dashboards, maps, datasets, model cards, system cards, benchmark cards, inference records, or public statements shall not be treated as official regulatory guidance unless a competent regulator has separately and lawfully adopted or issued them as such.
4.6.4(b) GCRI Canada may explain technical concepts, evidence categories, methods, risk concepts, AI governance concepts, cybersecurity concepts, data governance concepts, observability concepts, public-safe publication concepts, controlled vocabulary, public authority boundary concepts, finance-boundary concepts, and Nexus role-separation concepts in a non-regulatory learning capacity.
4.6.4(c) GCRI Canada may summarize or quote regulatory materials issued by competent authorities where accurate, source-labeled, limitation-aware, non-advisory, and not misleading, but such summaries shall not replace the official source or create legal advice.
4.6.4(d) GCRI Canada shall not state what law requires as an institutional legal determination unless the statement is limited to source-referenced educational explanation, reviewed where appropriate, and clearly distinguished from official regulatory guidance or legal advice.
4.6.4(e) GCRI Canada shall avoid terms such as “must comply,” “required by regulation,” “regulator-approved,” “safe harbor,” “official guidance,” “compliance pathway,” “approved standard,” “permit-ready,” “license-ready,” “lawful by GCRI determination,” or equivalent regulatory language unless accurately referencing a competent authority record and preserving GCRI Canada’s non-regulatory role.
4.6.4(f) Technical literacy and regulatory-adjacent learning materials shall include limitation language where appropriate, including that the materials are not legal advice, not regulatory guidance, not compliance approval, not a safe harbor, not a permit decision, not a license decision, not enforcement guidance, and not a substitute for competent authority review.
4.6.4(g) Where a public authority adopts or adapts GCRI Canada materials for regulatory guidance, the public authority shall be responsible for legal authority, adoption process, publication, interpretation, enforcement, correction, and public accountability.
4.6.4(h) Where GCRI Canada materials are misread as regulatory guidance, GCRI Canada shall correct, qualify, restrict, withdraw, supersede, or clarify the materials and, where appropriate, notify affected public authorities.
4.6.5 Regulator-Listening Participation Does Not Create Regulatory Approval, Compliance Guidance, Safe Harbor, Permit, Enforcement Position, or Public Endorsement. 4.6.5(a) Regulator-listening participation shall not create regulatory approval, compliance guidance, safe harbor, permit, license, enforcement position, public endorsement, public-law status, procurement approval, public finance approval, certification, recognition, protocol effect, or execution authority.
4.6.5(b) A regulator, public authority, enforcement body, permitting authority, licensing authority, public finance body, procurement body, public safety body, public health body, cyber authority, telecommunications authority, environmental authority, infrastructure authority, or other competent actor may attend, observe, listen, ask questions, contribute comments, review materials, provide data, fund learning, host a session, or participate in public authority learning without approving any GCRI Canada output.
4.6.5(c) Regulator-listening capacity shall be classified where material. The record shall identify whether the regulator is attending as observer, learner, technical participant, data contributor, host, funder, regulator in non-regulatory capacity, consultation participant, official decision-maker in its own separate process, or another defined capacity.
4.6.5(d) Regulator attendance, questions, silence, comments, suggestions, data contribution, correspondence, dashboard access, technical review, public-safe report review, participation in a public authority room, or presence in Nexus activities shall not create official guidance, approval, safe harbor, enforcement position, permit status, license status, compliance determination, or public endorsement.
4.6.5(e) Public materials referencing regulator participation shall use accurate, approved, capacity-classified, non-misleading, public-safe language and shall not use regulator names, logos, titles, photographs, quotes, or agency names to imply official approval unless expressly authorized by the competent authority.
4.6.5(f) Sponsors, providers, hosts, universities, National Consortium Companies, Project SPVs, capital readers, media actors, Nexus actors, and other participants shall not market regulator attendance as regulatory endorsement or compliance approval.
4.6.5(g) Where regulator-listening participation is likely to be misunderstood as approval or guidance, GCRI Canada shall restrict public claims, revise materials, seek capacity clarification, add limitation language, withhold publication, or route the matter to the competent authority.
4.6.5(h) Where regulator-listening participation is misdescribed, GCRI Canada shall correct the record, notify the affected authority where appropriate, withdraw or revise materials, and preserve correction records.
4.6.6 Technical Methods and Standards Support Do Not Become Law by Default. 4.6.6(a) Technical methods, standards support, reference architectures, open technical baselines, schemas, APIs, data dictionaries, ontologies, controlled vocabulary, public-good software, test harnesses, evaluation harnesses, conformance-supporting tools, benchmark methods, dashboard methods, and observability methods developed or supported by GCRI Canada shall not become law by default.
4.6.6(b) GCRI Canada may support technical discipline, interoperability, public-good software, evidence quality, public-safe publication, verifiable compute, verifiable intelligence, AI governance, cyber governance, data governance, public authority learning, and Nexus-compatible standards support, but such support shall not create legal obligations unless a competent public authority, legislature, regulator, court, tribunal, standards body, protocol authority, contract party, or other competent actor lawfully adopts or gives effect to the relevant material through its own process and record.
4.6.6(c) A GCRI Canada technical baseline may be useful, referenceable, persuasive, educational, conformance-supporting, or adoption-ready, but it shall not by default be mandatory, regulatory, certified, public-law binding, procurement-binding, protocol-effective, finance-ready, recognition-conferring, or enforcement-supporting with legal effect.
4.6.6(d) Standards support shall not make GCRI Canada a standards-setting authority with external legal force by default. Where GCRI Canada supports a separate Nexus Standards or Protocol Authority, the protocol or standards effect shall arise only through that authority’s lawful process and record.
4.6.6(e) Public authorities may lawfully adopt technical materials, but public authority adoption shall be the act of the public authority, not GCRI Canada, unless GCRI Canada has a distinct lawful role recorded within its Charter boundaries.
4.6.6(f) GCRI Canada shall not describe its technical materials as law, regulation, official standard, legal compliance pathway, mandatory requirement, safe harbor, permit condition, license condition, procurement requirement, or public-law rule unless a competent authority has lawfully established such status.
4.6.6(g) Where technical materials are likely to be cited in regulatory, procurement, public finance, certification, recognition, protocol, or public authority contexts, GCRI Canada shall include boundary language identifying non-regulatory, non-certification, non-protocol-effect, non-procurement, and correction status where appropriate.
4.6.6(h) Where GCRI Canada technical methods or standards support are misrepresented as law, GCRI Canada shall correct, restrict, withdraw, supersede, notify affected actors where appropriate, and preserve correction records.
4.6.7 Evidence Outputs Do Not Become Regulatory Findings by Default. 4.6.7(a) Evidence outputs produced, supported, stewarded, reviewed, published, or corrected by GCRI Canada shall not become regulatory findings by default.
4.6.7(b) Evidence outputs may include evidence records, public-safe reports, observability summaries, technical notes, controlled annexes, dashboards, maps, model cards, dataset cards, benchmark cards, system cards, inference records, proof inputs, diligence gap maps, risk indicators, resilience indicators, public authority learning materials, and correction records.
4.6.7(c) GCRI Canada may identify source status, evidence quality, limitation, confidence where appropriate, gap, inconsistency, dispute, stale record, missing data, cyber risk, AI risk, documentation deficiency, public-safe concern, protected knowledge concern, public authority ambiguity, finance-boundary concern, provider overclaim, sponsor overclaim, or correction need, but such identification shall not be a regulatory finding.
4.6.7(d) Evidence outputs shall not determine compliance, non-compliance, violation, breach, negligence, legality, permit status, license status, safe harbor, regulatory approval, enforcement priority, public standard satisfaction, public finance eligibility, procurement eligibility, or public-law liability.
4.6.7(e) Where a competent regulator or public authority uses GCRI Canada evidence outputs in its own process, the competent actor shall remain responsible for any regulatory finding, evidentiary weight, legal conclusion, procedural fairness, notice, appeal, enforcement action, public statement, or correction.
4.6.7(f) GCRI Canada shall design evidence outputs to prevent regulatory overclaim, including through issuer labels, evidence status labels, limitation statements, non-regulatory language, source references, review status, public-safe classification, public authority capacity labels, and correction paths where material.
4.6.7(g) Evidence outputs shall not be used by sponsors, providers, public authorities, hosts, media actors, National Consortium Companies, Project SPVs, capital readers, or Nexus actors to imply regulatory approval, compliance status, safe harbor, enforcement position, or public endorsement.
4.6.7(h) Where evidence outputs are misrepresented as regulatory findings, GCRI Canada shall correct, restrict, relabel, withdraw, supersede, notify affected actors where appropriate, and preserve correction records.
4.6.8 Public Authority Participants Retain Their Own Legal Authority and Decision Processes. 4.6.8(a) Public authority participants shall retain their own legal authority and decision processes in all interactions with GCRI Canada.
4.6.8(b) A public authority participant’s attendance, data contribution, technical review, question, comment, request, funding, hosting, dashboard access, Academy participation, public authority learning participation, Nexus participation, or controlled-room participation shall not transfer the public authority’s legal authority to GCRI Canada.
4.6.8(c) GCRI Canada shall not transfer its own authority to a public authority participant by participation, nor shall a public authority participant become a GCRI Canada director, officer, committee member, agent, sponsor, provider, controller, or issuer by default.
4.6.8(d) Public authority participants shall make regulatory decisions, enforcement decisions, permit decisions, license decisions, procurement decisions, public finance decisions, public warning decisions, emergency command decisions, public health decisions, public safety decisions, and official guidance decisions through their own lawful processes and records.
4.6.8(e) GCRI Canada shall support public authority learning only through non-executing evidence, methods, technical interpretation, public-safe publication, Academy materials, and correction records, and shall not substitute for public authority procedure, statutory duty, discretion, consultation, evidence rules, procedural fairness, notice, reasons, appeal, or accountability.
4.6.8(f) Public authority participants shall not be described as approving GCRI Canada materials, adopting GCRI Canada methods, endorsing GCRI Canada outputs, or issuing public-law effect unless their own competent record supports such description.
4.6.8(g) GCRI Canada shall use capacity classification, meeting records, public authority protocols, data contribution records, public claims controls, and correction mechanisms to preserve this distinction.
4.6.8(h) Where public authority legal authority or decision-process ambiguity arises, GCRI Canada shall clarify capacity, restrict public claims, correct materials, notify affected authorities where appropriate, and preserve correction records.
4.6.9 Public-Safe Regulatory Boundary Language. 4.6.9(a) GCRI Canada shall use public-safe regulatory boundary language in regulatory-adjacent, compliance-adjacent, enforcement-adjacent, permitting-adjacent, licensing-adjacent, standards-adjacent, public authority-facing, provider-facing, sponsor-facing, procurement-facing, finance-facing, media-facing, or public-facing materials where necessary to prevent improper reliance.
4.6.9(b) Regulatory boundary language may state, where appropriate, that the material is evidence support, methods support, technical interpretation, public authority learning, public-safe report, controlled briefing, research output, Academy material, technical baseline, software documentation, or correction record, and not regulatory guidance, legal advice, compliance approval, safe harbor, permit decision, license decision, enforcement position, official standard, public-law determination, procurement approval, public finance approval, certification, recognition, protocol effect, public warning, emergency command, or execution instruction.
4.6.9(c) Regulatory boundary language shall be clear, accessible, and proportionate to reliance risk. High-risk regulatory-adjacent dashboards, maps, technical baselines, provider materials, public authority materials, finance-facing materials, public-safe reports, and media materials shall not rely on hidden or inaccessible limitation language.
4.6.9(d) Regulatory boundary language shall identify the competent authority where known and shall not obscure that GCRI Canada is not the regulator or enforcement actor.
4.6.9(e) Where GCRI Canada summarizes public-law materials, it shall use source labels, date labels, jurisdiction labels, limitation language, and non-advice language where appropriate.
4.6.9(f) Boundary language shall be preserved when materials are translated, excerpted, visualized, turned into dashboards, embedded into websites, shared with public authorities, used by providers, used by sponsors, included in finance-facing materials, or reused in Nexus contexts.
4.6.9(g) Boundary language shall not be used to excuse materials that remain misleading. Where the overall presentation implies regulatory authority despite disclaimers, GCRI Canada shall redesign, restrict, withdraw, or decline publication.
4.6.9(h) Where boundary language is removed, weakened, contradicted, mistranslated, hidden, or overridden by public claims, GCRI Canada shall correct, restrict, withdraw, supersede, or issue clarification.
4.6.10 Correction Where GCRI Canada Outputs Are Misrepresented as Regulatory Acts. 4.6.10(a) GCRI Canada shall correct any statement, depiction, dashboard state, map, report, technical note, AI output, proof receipt, repository label, public authority material, sponsor material, provider material, media material, Nexus document, contract, public claim, or other communication that misrepresents GCRI Canada outputs as regulatory acts.
4.6.10(b) Regulatory-act misrepresentation includes any implication that GCRI Canada regulates, enforces law, grants permits, issues licenses, approves compliance, creates safe harbors, determines violations, establishes enforcement positions, issues official guidance, adopts public standards with legal force, approves public finance, makes procurement determinations, authorizes market activity, certifies legal compliance, or acts as a public authority.
4.6.10(c) Correction shall identify the accurate role of the relevant GCRI Canada output as evidence support, methods support, technical interpretation, public authority learning, technical baseline, software documentation, public-safe report, controlled annex, dashboard, map, briefing, Academy material, correction record, Docket input, Grid input, proof input, or other non-regulatory function.
4.6.10(d) Correction shall be proportionate to reliance risk. Internal misdescription may require template revision and training. Public misdescription may require public-safe clarification. Public authority-confusing misdescription may require notice to affected authorities. Provider or sponsor misuse may require name-use restriction or access suspension. Finance-facing or procurement-facing misdescription may require immediate withdrawal and legal review. Technical-system misdescription may require metadata, API, dashboard, repository, or proof-record correction.
4.6.10(e) Where a third party refuses to correct regulatory-act misrepresentation, GCRI Canada may restrict name use, restrict access, suspend participation, terminate the relationship, withdraw materials, notify competent authorities, notify affected audiences, seek media correction, or pursue legal remedies where appropriate.
4.6.10(f) Material corrections shall be recorded, including source, affected materials, public meaning, reliance risk, corrective action, notice decision, responsible actor, closeout, repeat pattern, and prevention measures.
4.6.10(g) Repeated regulatory-act misrepresentation shall not normalize regulatory authority. It shall require strengthened public authority protocols, regulatory boundary language, technical-baseline labels, dashboard labels, provider terms, sponsor terms, publication controls, repository controls, Academy materials, media protocols, and Nexus communication controls.
4.6.10(h) The controlling rule shall be that GCRI Canada may support regulatory understanding through evidence, methods, technical literacy, public-safe publication, and correction, but regulation and enforcement remain with competent lawful authorities.
4.7 No Procurement Authority or Vendor Selection Authority
4.7.1 GCRI Canada Does Not Conduct Public Procurement. 4.7.1(a) GCRI Canada shall not conduct public procurement. GCRI Canada shall not act as a public procurement authority, tendering authority, purchasing body, public buyer, bid evaluator, contracting authority, procurement board, vendor-selection body, prequalification body, public tender administrator, market-allocation body, or public purchasing decision-maker by default.
4.7.1(b) Public procurement shall remain the responsibility of competent public authorities, public-sector buyers, procurement bodies, public institutions, infrastructure owners, National Consortium Companies, Project SPVs, or other lawful purchasing or contracting actors acting through their own legal authority, procurement rules, governance records, conflict rules, competition requirements, budgets, approvals, contracts, and accountability procedures.
4.7.1(c) GCRI Canada may support procurement-adjacent understanding only through permitted non-executing functions, including evidence support, methods support, technical-baseline support, public-good software, observability-methods support, public authority learning, public-safe reports, controlled vocabulary, Academy materials, provider-neutral technical literacy, and correction records.
4.7.1(d) GCRI Canada shall not become a procurement authority by reason of technical expertise, public authority attendance, provider participation, sponsor support, technical-baseline authorship, public-good software release, benchmarking, testing, dashboard inclusion, observability work, public-safe reporting, Nexus participation, media description, public visibility, or repeated use of its materials by procurement actors.
4.7.1(e) GCRI Canada shall not design, issue, score, rank, administer, award, cancel, approve, supervise, or enforce public tenders, requests for proposals, requests for qualifications, procurement competitions, vendor lists, framework agreements, purchasing programs, or public buying processes by default.
4.7.1(f) Where a public authority, public buyer, National Consortium Company, Project SPV, or other competent actor uses GCRI Canada evidence, methods, public-good software, technical baselines, dashboards, reports, or Academy materials in a procurement process, that actor shall remain responsible for the procurement design, legal authority, competition rules, evaluation, award, contract, conflict management, protests, debriefings, records, and corrections.
4.7.1(g) GCRI Canada materials shall not be described as procurement approval, tender approval, vendor selection, purchasing recommendation, public contract award, bid prequalification, preferred vendor status, public buyer endorsement, public authority purchasing decision, or market allocation unless a competent procurement actor has separately and lawfully issued such determination through its own record.
4.7.1(h) Where procurement-authority ambiguity arises, GCRI Canada shall apply the narrowest non-procurement interpretation, clarify its role, restrict public claims, revise language, route the matter to the competent procurement actor, correct overclaims, and preserve correction records.
4.7.2 No Award of Public Contracts, Public Tenders, Vendor Selection, Preferred Vendor Status, Procurement Ranking, Public Purchasing Recommendation, or Tender Prequalification by Default. 4.7.2(a) GCRI Canada shall not award public contracts, award public tenders, select vendors, approve vendors, prequalify bidders, create preferred vendor status, rank vendors for procurement, recommend public purchases, determine tender eligibility, determine tender compliance, allocate markets, approve purchasing frameworks, or issue procurement outcomes by default.
4.7.2(b) GCRI Canada shall not issue any certificate, report, dashboard status, benchmark result, test result, technical-baseline alignment note, compatibility note, public-safe report, repository badge, API flag, proof receipt, Academy record, public authority learning record, or public statement that could reasonably be understood as procurement approval or vendor selection.
4.7.2(c) GCRI Canada may identify whether evidence relevant to a technical method, public-good baseline, interoperability expectation, privacy expectation, cybersecurity expectation, AI-governance expectation, public-safe release expectation, or documentation expectation is present, absent, incomplete, disputed, stale, restricted, or correction-requiring, but such identification shall not be a purchasing recommendation.
4.7.2(d) GCRI Canada shall not use terms such as “approved vendor,” “preferred vendor,” “selected vendor,” “procurement-ready,” “tender-ready,” “prequalified,” “shortlisted,” “recommended supplier,” “public buyer approved,” “government procurement approved,” “Nexus-approved provider,” “GCRI-approved provider,” or equivalent procurement-signaling terms unless accurately referencing a competent procurement actor’s separate record and preserving GCRI Canada’s non-procurement role.
4.7.2(e) Provider participation in GCRI Canada programs shall not grant any advantage in public tenders, private procurements, National Consortium Company procurements, Project SPV procurements, public authority procurements, sponsor procurements, or Nexus-related purchasing unless a competent procurement actor lawfully determines eligibility within its own process.
4.7.2(f) Where GCRI Canada supports a public authority or procurement actor with learning materials, technical baselines, evidence structures, or public-good software, GCRI Canada shall not determine which provider, product, system, platform, consultant, contractor, integrator, operator, insurer, lender, or service provider should be selected.
4.7.2(g) Procurement-facing use of GCRI Canada materials shall require public claims controls sufficient to prevent false implication of award, selection, recommendation, prequalification, ranking, endorsement, or public purchasing approval.
4.7.2(h) Where GCRI Canada materials are used or cited as procurement determinations, GCRI Canada shall require correction, restrict use, withdraw permission where appropriate, notify affected actors where appropriate, and preserve correction records.
4.7.3 No Provider Preference by Testing, Benchmarking, Participation, Sponsorship, Technical Contribution, Publication, Event Presence, Dashboard Inclusion, or Public Authority Learning. 4.7.3(a) Testing, benchmarking, participation, sponsorship, technical contribution, publication, event presence, dashboard inclusion, public authority learning, Academy participation, repository contribution, observability involvement, or Nexus proximity shall not create provider preference by default.
4.7.3(b) Provider testing may evaluate technical behavior, evidence quality, documentation completeness, interoperability, cybersecurity posture, AI governance, data handling, benchmark performance, public-safe compatibility, or method alignment within a defined scope, but testing shall not constitute endorsement, certification, public procurement approval, preferred vendor status, finance-readiness, insurance-readiness, protocol entitlement, or market ranking.
4.7.3(c) Benchmarking shall be method-bounded, limitation-aware, versioned, context-specific, and correctionable. A benchmark result shall not be generalized into overall provider superiority, procurement preference, public buyer recommendation, public authority approval, certification, recognition, finance-readiness, or protocol effect.
4.7.3(d) Provider participation in workshops, public authority learning, Academy sessions, Nexus Universe activities, Nexus Observatory activities, technical reviews, public-good software development, standards-support discussions, or evidence review shall not imply that GCRI Canada endorses, prefers, selects, certifies, recognizes, recommends, procures, or approves the provider.
4.7.3(e) Sponsorship shall not create provider preference. A sponsor that is also a provider shall not receive favorable testing, favorable publication, favorable dashboard presentation, preferred access to public authorities, preferred participation in Academy materials, preferred technical-baseline influence, or procurement-signaling treatment by reason of support.
4.7.3(f) Technical contribution shall not create technical supremacy or provider preference. A provider contributing code, data, models, infrastructure, cloud resources, AI tools, documentation, funding, facilities, or expert time shall not acquire control over methods, baselines, public-good software, publication, correction, repository governance, or provider-neutral public meaning.
4.7.3(g) Dashboard inclusion, map inclusion, registry-like display, repository listing, public-safe report reference, event attendance, or public authority room participation shall be labeled and designed to prevent preferred-status implication.
4.7.3(h) Where provider participation creates preference, endorsement, procurement, competition, sponsor-control, public authority, finance, certification, recognition, protocol, or market-conduct risk, GCRI Canada shall correct, restrict, relabel, withdraw, suspend, terminate, or redesign the relevant activity, material, or relationship.
4.7.4 No Procurement Steering Through Evidence Packs, Technical Baselines, Observatory Methods, Public-Good Software, Docket Inputs, Grid Inputs, or Public-Safe Reports. 4.7.4(a) GCRI Canada shall not steer procurement through evidence packs, technical baselines, observatory methods, public-good software, Docket inputs, Grid inputs, proof inputs, public-safe reports, controlled annexes, dashboards, maps, Academy materials, method libraries, benchmark records, test harnesses, evaluation harnesses, public authority learning materials, or Nexus-compatible records.
4.7.4(b) Evidence packs may organize evidence, sources, gaps, limitations, confidence, public-safe status, technical context, host readiness, node evidence, observability records, data governance, AI governance, cybersecurity, community safeguards, and correction needs, but shall not identify who should be awarded a contract or procured.
4.7.4(c) Technical baselines may describe public-good expectations, interoperability expectations, cybersecurity expectations, privacy expectations, AI-governance expectations, documentation expectations, public-safe release expectations, and correction pathways, but shall not be written to favor a provider, lock in a vendor, exclude lawful alternatives, create hidden specifications, or create procurement advantage by default.
4.7.4(d) Observatory methods may support understanding of sensor evidence, AI-RAN evidence, DePIN evidence, digital twin assumptions, dashboard limitations, geospatial evidence, and public-safe observability outputs, but shall not identify a preferred observability operator, system integrator, platform, telecommunications provider, cloud provider, AI provider, sensor provider, or infrastructure provider.
4.7.4(e) Public-good software and APIs may support interoperability, evidence structuring, public-safe publication, model governance, dataset governance, benchmark records, correction records, and technical learning, but shall not be used as hidden procurement channels or vendor lock-in mechanisms.
4.7.4(f) Docket inputs, Grid inputs, proof inputs, public-safe reports, and diligence gap maps may inform downstream actors, but shall not direct procurement, require purchase, recommend vendors, prequalify bidders, or create provider preference by default.
4.7.4(g) Where GCRI Canada materials are likely to be used in procurement-adjacent contexts, they shall include non-procurement language, provider-neutral language, no-endorsement language, limitation statements, scope labels, and correction pathways where material.
4.7.4(h) Where procurement steering occurs or is foreseeable, GCRI Canada shall re-scope the material, remove provider-preferential language, redesign technical specifications, restrict use, add boundary language, route procurement questions to competent procurement actors, or withdraw the material.
4.7.5 No Exclusive Access to Public Authority Buyers Through GCRI Canada. 4.7.5(a) GCRI Canada shall not provide exclusive access to public authority buyers through its programs, events, Academy activities, public authority learning rooms, Nexus interfaces, observability activities, public-safe reports, dashboards, provider demonstrations, sponsor arrangements, technical-baseline discussions, or public-good software activities.
4.7.5(b) No provider, vendor, sponsor, donor, host, university, National Consortium Company, Project SPV, capital actor, or other participant shall receive exclusive or preferential access to public authority buyers by reason of supporting, funding, sponsoring, hosting, contributing to, or participating in GCRI Canada.
4.7.5(c) Public authority participation in GCRI Canada activities shall be for public-benefit learning, evidence understanding, technical literacy, public-safe interpretation, research, correctionability, or other lawful capacity-classified purposes, and not as a private procurement channel.
4.7.5(d) GCRI Canada shall not arrange closed procurement access, buyer meetings, sales pipelines, tender influence, privileged public authority introductions, vendor lobbying channels, or sponsor-controlled public authority access by default.
4.7.5(e) GCRI Canada may convene multi-stakeholder learning environments where public authorities, providers, sponsors, universities, civil society actors, and other participants are present, provided that access rules are transparent where appropriate, role-bounded, provider-neutral, sponsor-non-controlled, public-benefit aligned, and not structured as procurement access.
4.7.5(f) Public authority rooms, workshops, controlled briefings, dashboards, and technical sessions shall use role labels and capacity classification to distinguish learning from procurement, market development, vendor pitching, sponsorship influence, and public authority endorsement.
4.7.5(g) If a public authority wishes to procure, it shall do so through its own procurement channels, rules, notices, procedures, competition requirements, and records, not through GCRI Canada unless GCRI Canada is lawfully and separately engaged in a permitted non-procurement support role.
4.7.5(h) Where exclusive-access risk arises, GCRI Canada shall modify access rules, broaden or neutralize participation where appropriate, restrict sales conduct, separate learning from procurement, correct claims, or terminate the access arrangement.
4.7.6 No Pay-to-Access Procurement Channels. 4.7.6(a) GCRI Canada shall not create, sell, imply, or facilitate pay-to-access procurement channels.
4.7.6(b) No sponsorship, donation, membership, program fee, Academy fee, event fee, subscription, in-kind contribution, technical contribution, cloud credit, software access, AI model access, facilities support, or other support shall purchase access to public authority buyers, procurement officials, tender opportunities, public finance readers, National Consortium Company procurement pathways, Project SPV procurement pathways, provider shortlists, public purchasing programs, or procurement influence.
4.7.6(c) Support levels, sponsor categories, donor tiers, provider participation levels, event packages, Academy packages, technical contribution status, or Nexus visibility shall not be structured to provide procurement access, public authority buyer access, preferred introductions, sales opportunities, or tender influence.
4.7.6(d) GCRI Canada shall not describe sponsor or provider benefits in terms of procurement access, buyer access, public authority purchasing opportunities, government sales pipeline, tender influence, project pipeline access, exclusive deal flow, preferred vendor exposure, or procurement readiness.
4.7.6(e) Fees may be charged for lawful mission-aligned programs, training, events, materials, subscriptions, or cost recovery, but such fees shall not be linked to procurement outcomes, public authority purchasing access, provider preference, finance-readiness, recognition, certification, protocol effect, or execution opportunities.
4.7.6(f) Where public authorities participate in fee-supported activities, GCRI Canada shall ensure that fee arrangements do not create improper access, pay-to-play perception, procurement preference, public authority endorsement, conflict of interest, or public trust risk.
4.7.6(g) Where any offering, sponsorship, or support arrangement creates pay-to-access procurement risk, GCRI Canada shall refuse, re-scope, reprice, redesign, disclose where appropriate, restrict benefits, or terminate the arrangement.
4.7.6(h) The controlling rule shall be that financial support may sustain public-good work, but it shall not purchase procurement access or market advantage.
4.7.7 No Sponsor or Provider Purchase of Preferential Treatment. 4.7.7(a) No sponsor, donor, funder, provider, vendor, contractor, host, university, public authority participant, National Consortium Company, Project SPV, capital actor, or other person may purchase preferential treatment from GCRI Canada.
4.7.7(b) Preferential treatment includes favorable evidence treatment, favorable method treatment, favorable benchmark framing, favorable dashboard placement, favorable report language, favorable public-safe publication timing, favorable correction treatment, preferred access to public authorities, preferred provider visibility, favorable Academy inclusion, preferred technical-baseline influence, repository privilege, public claims privilege, finance-signaling advantage, procurement implication, certification implication, recognition implication, protocol implication, or execution opportunity.
4.7.7(c) GCRI Canada shall not accept support conditioned on favorable treatment, suppressed unfavorable evidence, delayed correction, altered methods, altered benchmarks, provider preference, procurement signaling, public authority access, finance-facing advantage, sponsor visibility beyond approved terms, or public-good asset control.
4.7.7(d) If a sponsor or provider is also a technical contributor, participant, host, vendor, or subject of evidence review, GCRI Canada shall apply conflicts review, role separation, public claims controls, provider-neutrality controls, sponsor-non-control controls, data controls, and correction independence.
4.7.7(e) A provider’s technical quality, public-benefit contribution, or mission alignment may be discussed only within evidence-supported, method-bounded, provider-neutral, non-procurement, non-certification, non-endorsement limits.
4.7.7(f) Sponsorship acknowledgments shall not be designed to resemble provider approval, procurement preference, public authority endorsement, finance-readiness, certification, recognition, protocol entitlement, or official selection.
4.7.7(g) Where preferential-treatment risk arises, GCRI Canada shall refuse support, narrow benefits, separate roles, recuse conflicted persons, restrict public claims, revise materials, correct records, suspend participation, or terminate the relationship.
4.7.7(h) The controlling rule shall be that GCRI Canada’s evidence, methods, baselines, publications, corrections, public authority learning, and technical stewardship cannot be bought.
4.7.8 Competition-Safe Benchmarking and Market Baseline Libraries. 4.7.8(a) GCRI Canada may maintain competition-safe benchmarking and market baseline libraries for public-benefit evidence, technical literacy, interoperability learning, public authority learning, research, public-safe reporting, technical-baseline development, public-good software evaluation, and correctionability, provided that such libraries do not become procurement rankings or provider-selection tools by default.
4.7.8(b) Benchmarking shall be scoped, method-bounded, documented, versioned, reproducible where appropriate, limitation-aware, conflict-reviewed where material, public-safe, provider-neutral, sponsor-non-controlled, correctionable, and separated from procurement decisions.
4.7.8(c) Market baseline libraries may document technical categories, capabilities, architectures, evidence expectations, implementation patterns, interoperability issues, cybersecurity considerations, privacy considerations, AI-governance considerations, data-governance considerations, public-safe considerations, known limitations, dependency risks, and correction history without recommending vendors.
4.7.8(d) Benchmarking and baseline libraries shall not use ranking language, league tables, preferred-provider labels, award-like visuals, certification badges, procurement-ready labels, public authority approval labels, finance-ready labels, protocol-entitled labels, recognition labels, or other market-signaling devices unless such language is strictly necessary, records-supported, non-procurement, non-endorsement, public-safe, and legally reviewed where material.
4.7.8(e) Provider-specific information may be included only where lawful, evidence-supported, method-bounded, fair, current, public-safe, non-misleading, conflicts-reviewed where material, and accompanied by limitations and correction pathways.
4.7.8(f) GCRI Canada shall avoid anticompetitive information exchange, improper market signaling, exclusionary design, sponsor-shaped benchmarking, provider-favoring criteria, discriminatory access, or hidden procurement specifications.
4.7.8(g) Where benchmarking or baseline libraries are used by a competent procurement actor, that actor shall remain responsible for procurement process, legal compliance, evaluation criteria, competition obligations, vendor selection, award, debriefing, and remedies.
4.7.8(h) Where benchmarking or market baseline materials create competition, procurement, provider-preference, sponsor-control, finance-signaling, certification, recognition, protocol, or public authority risk, GCRI Canada shall restrict, revise, relabel, withdraw, supersede, or seek review before further use.
4.7.9 Public Authority Procurement Boundaries and Non-Endorsement Language. 4.7.9(a) GCRI Canada shall use public authority procurement boundary language and non-endorsement language in procurement-adjacent, public authority-facing, provider-facing, sponsor-facing, finance-facing, media-facing, or public-facing materials where necessary to prevent improper reliance.
4.7.9(b) Procurement boundary language may state, where appropriate, that the material is evidence support, methods support, technical interpretation, public authority learning, technical baseline, public-safe report, controlled briefing, Academy material, software documentation, observability summary, Docket input, Grid input, proof input, or correction record, and not a procurement decision, tender recommendation, vendor selection, preferred-provider status, public purchasing recommendation, tender prequalification, public contract award, public authority endorsement, certification, recognition, finance-readiness, protocol effect, public warning, emergency command, or execution instruction.
4.7.9(c) Non-endorsement language shall be used where providers, vendors, sponsors, hosts, or technical contributors are named, displayed, tested, benchmarked, included in dashboards, referenced in reports, present at events, or participating in public authority learning in a manner that may imply endorsement.
4.7.9(d) Public authority procurement boundary language shall identify that public authorities retain their own procurement rules, competition obligations, conflicts obligations, evaluation criteria, award decisions, contract management, records, and accountability.
4.7.9(e) Boundary language shall be clear, prominent, accessible, and proportionate to reliance risk. High-risk procurement-adjacent materials shall not rely on hidden, vague, or inaccessible disclaimers.
4.7.9(f) Boundary language shall be preserved when materials are excerpted, translated, visualized, embedded, presented in dashboards, included in procurement-adjacent discussions, used in public authority rooms, included in provider materials, included in sponsor materials, or reused in Nexus contexts.
4.7.9(g) Boundary language shall not be used to excuse materials that remain procurement-steering in substance. Where the overall presentation creates provider preference or procurement implication despite disclaimers, GCRI Canada shall redesign, restrict, withdraw, or decline publication.
4.7.9(h) Where boundary language is removed, weakened, contradicted, hidden, mistranslated, or overridden by public claims, GCRI Canada shall correct, restrict, withdraw, supersede, or issue clarification.
4.7.10 Correction Where GCRI Canada Proximity Is Used to Claim Procurement Advantage. 4.7.10(a) GCRI Canada shall correct any statement, depiction, marketing material, dashboard state, report, benchmark, public authority material, sponsor material, provider material, media material, Nexus document, contract, proposal, investor material, procurement material, website, repository entry, API field, event material, or public claim that uses GCRI Canada proximity to claim procurement advantage.
4.7.10(b) Procurement-advantage overclaim includes any implication that participation with GCRI Canada improves tender prospects, creates public buyer access, grants preferred vendor status, constitutes prequalification, signals public authority approval, creates provider endorsement, confirms procurement readiness, creates public purchasing recommendation, gives access to decision-makers, satisfies procurement requirements, or places a provider on a preferred list.
4.7.10(c) Procurement-advantage overclaim may arise from phrases such as “GCRI Canada approved,” “GCRI Canada preferred,” “selected through GCRI Canada,” “procurement-ready through GCRI,” “public authority access through GCRI Canada,” “Nexus-approved vendor,” “government-ready through Nexus,” “prequalified by GCRI Canada,” “endorsed for public buyers,” or equivalent statements.
4.7.10(d) Correction shall identify the accurate role of GCRI Canada, including whether the relevant interaction was evidence support, methods support, testing, benchmarking, public authority learning, Academy participation, technical contribution, sponsorship, hosting, public-safe publication, dashboard inclusion, repository contribution, Docket input, Grid input, proof input, or other non-procurement function.
4.7.10(e) Correction shall be proportionate to reliance risk. Internal overclaim may require template revision and training. Provider marketing overclaim may require name-use restriction. Public authority-confusing overclaim may require notice to affected public authorities. Procurement-facing overclaim may require immediate withdrawal and legal review. Public overclaim may require public-safe clarification. Repeated overclaim may require suspension or termination.
4.7.10(f) Where a provider, sponsor, host, National Consortium Company, Project SPV, media actor, public authority participant, university, contractor, or Nexus actor refuses to correct procurement-advantage overclaim, GCRI Canada may restrict name use, suspend access, terminate participation, withdraw materials, notify affected actors, seek media correction, or pursue legal remedies where appropriate.
4.7.10(g) Material corrections shall be recorded, including source, affected materials, public meaning, reliance risk, corrective action, notice decision, responsible actor, closeout, repeat pattern, and prevention measures.
4.7.10(h) Repeated procurement-advantage overclaim shall not normalize procurement authority. It shall require strengthened provider terms, sponsor terms, event rules, benchmark labels, dashboard labels, public authority protocols, name-use controls, non-endorsement language, procurement boundary language, and Nexus communication controls.
4.7.10(i) The controlling rule shall be that GCRI Canada may support public-good evidence, methods, technical baselines, public authority learning, and provider-neutral technical understanding, but it shall not conduct procurement, select vendors, endorse providers, or confer procurement advantage.
4.8 No Certification by Default
4.8.1 GCRI Canada Does Not Certify by Default. 4.8.1(a) GCRI Canada shall not certify by default. GCRI Canada shall not act as a certification body, conformity-assessment body, accreditation body, credentialing authority, approval authority, audit authority with external certification effect, product-certification body, provider-certification body, technology-certification body, system-certification body, node-certification body, resilience-certification body, public authority readiness-certification body, finance-readiness-certification body, or Nexus compatibility-certification body unless a separate lawful, authorized, records-valid, scope-defined certification program is expressly adopted.
4.8.1(b) GCRI Canada’s default role shall remain upstream, non-executing, public-benefit, evidence-based, methods-based, observability-based, ontology-based, public-good R&D-based, public-good software-based, technical-baseline-based, public authority learning-based, public-safe publication-based, and correctionable. That role may support future certification by a competent actor, but it shall not itself create certification.
4.8.1(c) No report, evidence record, method note, test result, benchmark result, technical-baseline alignment note, public-good software release, dashboard status, map layer, model card, dataset card, benchmark card, system card, inference record, proof receipt, blockchain anchor, DePIN record, AI output, Academy record, program participation, council participation, lab participation, Nexus Universe activity, observatory exercise, validation sprint, or public-safe publication shall constitute certification by default.
4.8.1(d) Certification shall not arise by implication, reliance, public visibility, provider participation, sponsor support, public authority attendance, media description, capital-reader interest, technical sophistication, repeated use, repository status, dashboard inclusion, GCRI Canada proximity, Nexus branding, or public-good importance.
4.8.1(e) Where a GCRI Canada output may be useful to a competent certification body, public authority, protocol authority, GRF, GRA, procurement actor, National Consortium Company, Project SPV, provider, sponsor, or other downstream actor, such usefulness shall not convert the output into certification.
4.8.1(f) GCRI Canada shall use controlled vocabulary to distinguish evidence, review, testing, benchmarking, baseline alignment, participation, completion, contribution, technical support, public-safe reporting, and correction from certification.
4.8.1(g) Where certification ambiguity arises, the non-certification interpretation shall prevail unless a separate authorized certification program has been lawfully established and the specific certification act is records-valid within its scope.
4.8.1(h) Any statement implying that GCRI Canada certifies by default shall be corrected, restricted, withdrawn, superseded, or publicly clarified where reliance risk exists.
4.8.2 No Certification of Technologies, Providers, Nodes, AI Systems, Cyber Systems, AI-RAN Systems, DePIN Systems, Digital Twins, Sensors, Dashboards, Software, Technical Baselines, Standards Compliance, Resilience Outcomes, Maturity States, Finance-Readiness, Public Authority Readiness, or Nexus Compatibility by Default. 4.8.2(a) GCRI Canada shall not certify technologies, providers, vendors, contractors, hosts, sponsors, National Consortium Companies, Project SPVs, nodes, hubs, clusters, observatory sites, AI systems, cyber systems, AI-RAN systems, O-RAN systems, private wireless systems, DePIN systems, blockchain systems, digital twins, sensors, dashboards, software, APIs, datasets, models, compute systems, public-good software, technical baselines, reference architectures, standards compliance, resilience outcomes, maturity states, finance-readiness, public authority readiness, host readiness, node readiness, insurance-readiness, procurement-readiness, public-safe status, protocol compatibility, or Nexus compatibility by default.
4.8.2(b) GCRI Canada may describe evidence relating to any such technology, provider, system, node, asset, method, or readiness condition, provided that the description remains evidence-based, method-bounded, non-certifying, non-procurement, non-financial, non-regulatory, non-recognition, non-protocol-effect, non-executing, and correctionable.
4.8.2(c) GCRI Canada may state that evidence was received, reviewed, structured, incomplete, disputed, stale, public-safe, controlled, limited, source-lined, method-bounded, benchmarked, tested, or aligned to a stated draft or reference baseline, but such statements shall not mean certified, approved, validated for market use, certified for public use, procurement-approved, finance-ready, insurance-ready, public-authority-ready, protocol-entitled, operationally safe, legally compliant, or Nexus-certified.
4.8.2(d) No provider shall claim that GCRI Canada evidence review, testing, benchmarking, technical contribution, dashboard inclusion, public-safe report reference, Academy participation, observatory exercise participation, public authority learning participation, or Nexus proximity certifies the provider or its products.
4.8.2(e) No public authority, sponsor, host, National Consortium Company, Project SPV, capital reader, media actor, or Nexus actor shall describe GCRI Canada participation as certification of a technology, provider, system, node, project, maturity state, readiness state, or compatibility state unless a separate authorized certification program has records-validly issued such certification.
4.8.2(f) Where another competent actor certifies a technology, provider, system, project, maturity state, readiness state, or compatibility state using GCRI Canada evidence as an input, the certification shall be that actor’s act, not GCRI Canada’s act, unless GCRI Canada has expressly and lawfully assumed a defined certification role.
4.8.2(g) GCRI Canada materials shall avoid certification-like visuals, badges, seals, rankings, pass/fail labels, approved-state labels, certified-state labels, gold/silver/bronze labels, readiness labels, or compliance labels unless they are non-certification labels with clear limitations or part of an authorized certification program.
4.8.2(h) Where certification-like misdescription occurs, GCRI Canada shall correct, restrict, relabel, withdraw, supersede, notify affected actors where appropriate, and preserve correction records.
4.8.3 Testing Is Not Certification. 4.8.3(a) Testing by, with, or in reference to GCRI Canada shall not constitute certification by default.
4.8.3(b) Testing may include technical testing, software testing, interoperability testing, cybersecurity testing, AI evaluation, data-quality testing, sensor testing, dashboard testing, API testing, observability testing, DePIN signal testing, AI-RAN evidence testing, digital twin assumption testing, model testing, benchmark testing, public-good software testing, reference-architecture testing, public-safe publication testing, and test-harness operation.
4.8.3(c) A test may identify behavior, evidence, performance, failure modes, interoperability issues, assumptions, vulnerabilities, limitations, gaps, or correction needs within a defined scope, method, time, version, dataset, environment, configuration, and review status.
4.8.3(d) A test result shall not certify overall safety, legal compliance, public authority readiness, finance-readiness, insurance-readiness, operational readiness, procurement readiness, resilience outcome, maturity state, provider quality, protocol conformance, Nexus compatibility, or public-good legitimacy.
4.8.3(e) Passing a GCRI Canada test shall not mean that a system, provider, product, node, project, dataset, model, benchmark, dashboard, public-good software component, AI-RAN system, DePIN system, digital twin, sensor, or technical baseline is certified.
4.8.3(f) Failing, partially passing, or not participating in a test shall not by itself create legal non-compliance, procurement disqualification, public authority rejection, finance rejection, insurance rejection, provider exclusion, recognition denial, protocol denial, or public-facing adverse status.
4.8.3(g) Test records shall identify purpose, scope, method, version, date, test environment, assumptions, data used, limitations, reviewer, result, public-safe status, prohibited interpretations, correction path, and non-certification status where material.
4.8.3(h) Where testing is misrepresented as certification, GCRI Canada shall correct the claim, revise labels, restrict use of test outputs, require removal of certification-like language, withdraw materials where necessary, and preserve correction records.
4.8.4 Benchmarking Is Not Certification. 4.8.4(a) Benchmarking by, with, or in reference to GCRI Canada shall not constitute certification by default.
4.8.4(b) Benchmarking may support technical learning, evidence comparison, method development, public authority learning, public-good software evaluation, model evaluation, dataset evaluation, system evaluation, cybersecurity learning, AI governance learning, interoperability learning, observability learning, and public-safe reporting.
4.8.4(c) Benchmark results shall be method-bounded, context-specific, version-specific, dataset-specific, configuration-specific, assumption-aware, limitation-aware, review-status-aware, public-safe where released, and correctionable.
4.8.4(d) Benchmarking shall not certify provider quality, technology safety, legal compliance, public authority readiness, finance-readiness, insurance-readiness, operational readiness, procurement readiness, resilience outcomes, maturity states, standards compliance, protocol conformance, Nexus compatibility, or public-good legitimacy.
4.8.4(e) Benchmark tables, scores, bands, comparisons, dashboards, charts, model cards, benchmark cards, test harness outputs, evaluation harness outputs, and public-safe reports shall not be designed or described as certification rankings, approved-provider lists, procurement rankings, public authority approvals, finance-readiness scores, insurance-readiness scores, or protocol conformance states by default.
4.8.4(f) Benchmarking shall not be used to create hidden procurement steering, market allocation, provider preference, sponsor advantage, public authority overclaim, finance signaling, certification implication, recognition implication, protocol implication, or execution implication.
4.8.4(g) Benchmark records shall identify benchmark purpose, scope, method, version, data, assumptions, limitations, result, review status, public-safe status, conflict review where material, sponsor or provider involvement where material, correction path, and non-certification status.
4.8.4(h) Where benchmarking is misrepresented as certification, GCRI Canada shall correct, restrict, relabel, withdraw, supersede, notify affected actors where appropriate, and preserve correction records.
4.8.5 Evidence Review Is Not Certification. 4.8.5(a) Evidence review by, with, or in reference to GCRI Canada shall not constitute certification by default.
4.8.5(b) Evidence review may determine whether evidence is present, absent, incomplete, inconsistent, disputed, stale, source-lined, classified, public-safe, restricted, method-limited, confidence-bounded, or correction-requiring, but shall not certify the underlying actor, system, project, technology, provider, readiness state, compliance state, maturity state, resilience outcome, finance-readiness, insurance-readiness, public authority readiness, or Nexus compatibility.
4.8.5(c) Evidence sufficiency for one purpose shall not be treated as certification for another purpose. Evidence sufficient for research may be insufficient for public authority action. Evidence sufficient for technical learning may be insufficient for procurement. Evidence sufficient for GRA review may not be finance-readiness. Evidence useful to GRF may not be recognition. Evidence relevant to Protocol Authority may not be protocol effect.
4.8.5(d) Evidence review shall not imply that GCRI Canada has independently verified every fact, audited every system, inspected every site, validated every claim, approved every method, certified every output, or guaranteed every result.
4.8.5(e) Evidence review records shall identify source, scope, method, review status, limitations, assumptions, confidence where appropriate, public-safe status, data restrictions, public authority restrictions, finance-boundary restrictions, provider-neutrality limits, sponsor-non-control limits, correction path, and non-certification status where material.
4.8.5(f) No person shall market a GCRI Canada evidence review as certification, validation, approval, public authority endorsement, finance-readiness, insurance-readiness, procurement readiness, maturity status, protocol conformance, public-good legitimacy, or Nexus certification.
4.8.5(g) Where evidence review is relied upon by a competent downstream actor, that actor remains responsible for any certification, recognition, finance-readiness, procurement, public authority, protocol, insurance, investment, or execution determination.
4.8.5(h) Where evidence review is misrepresented as certification, GCRI Canada shall correct, restrict, relabel, withdraw, supersede, notify affected actors where appropriate, and preserve correction records.
4.8.6 Technical Baseline Alignment Is Not Certification. 4.8.6(a) Technical baseline alignment by, with, or in reference to GCRI Canada shall not constitute certification by default.
4.8.6(b) Technical baseline alignment may indicate that a system, method, dataset, model, API, dashboard, software component, node, provider implementation, or project documentation appears to correspond in some defined respect to a stated reference architecture, schema, controlled vocabulary, interoperability expectation, cybersecurity expectation, privacy expectation, AI-governance expectation, data-governance expectation, public-safe publication expectation, documentation expectation, or open technical baseline.
4.8.6(c) Alignment shall be limited to the scope, version, method, evidence, assumptions, data, review status, and date recorded. Alignment to one baseline shall not mean alignment to all baselines. Alignment in documentation shall not mean implemented alignment. Alignment in a test environment shall not mean operational alignment. Alignment in one jurisdiction shall not mean lawful alignment in another.
4.8.6(d) Technical baseline alignment shall not certify legal compliance, public authority approval, procurement readiness, finance-readiness, insurance-readiness, resilience outcome, maturity state, provider quality, system safety, cybersecurity adequacy, operational readiness, protocol conformance, recognition, or Nexus compatibility by default.
4.8.6(e) GCRI Canada shall not allow baseline-alignment labels to be designed or used as certification badges, approved marks, provider endorsements, procurement qualifiers, regulatory approvals, finance labels, maturity labels, protocol states, or external conformance states unless part of a separately authorized certification or protocol program.
4.8.6(f) Technical baseline alignment records shall identify baseline, version, scope, method, evidence reviewed, assumptions, limitations, review status, public-safe status, maintainer, date, prohibited interpretations, correction path, and non-certification status.
4.8.6(g) Where a competent external actor adopts baseline alignment as part of its own certification, procurement, public authority, protocol, recognition, or finance-readiness process, that external effect shall arise from the external actor’s record and not from GCRI Canada alignment alone.
4.8.6(h) Where technical baseline alignment is misrepresented as certification, GCRI Canada shall correct, restrict, relabel, withdraw, supersede, notify affected actors where appropriate, and preserve correction records.
4.8.7 Public-Good Software Use Is Not Certification. 4.8.7(a) Use, implementation, integration, installation, deployment, forking, contribution to, reference to, or compatibility with GCRI Canada public-good software shall not constitute certification by default.
4.8.7(b) Public-good software may support evidence structuring, observability, ontology, controlled vocabulary, public-safe publication, data governance, model governance, benchmark records, system records, inference records, technical baselines, correction records, Academy learning, public authority learning, Docket inputs, Grid inputs, proof inputs, and Nexus-compatible interoperability.
4.8.7(c) Use of public-good software shall not certify that the user, provider, system, project, node, dashboard, dataset, model, API, infrastructure, or implementation is safe, secure, lawful, compliant, procurement-ready, finance-ready, insurance-ready, mature, recognized, protocol-conformant, public-authority-ready, or Nexus-compatible.
4.8.7(d) Software functioning as intended shall not certify the correctness of inputs, quality of data, validity of evidence, reliability of models, adequacy of cybersecurity, legality of processing, public-safe status of outputs, competence of users, compliance of downstream actors, or authority of any decision.
4.8.7(e) Contributions to public-good software shall not certify contributors, providers, vendors, sponsors, hosts, universities, public authorities, National Consortium Companies, Project SPVs, or any associated products or services.
4.8.7(f) Software documentation, repository badges, release notes, package labels, API states, compatibility flags, test results, continuous integration status, issue status, pull-request status, proof receipts, or version numbers shall not be represented as certification marks.
4.8.7(g) Public-good software records shall identify license, version, maintainer, intended use, prohibited use, dependencies, security status where material, support level, limitation, non-warranty language, non-certification status, public-safe status, correction path, deprecation path, and withdrawal path.
4.8.7(h) Where public-good software use is misrepresented as certification, GCRI Canada shall correct documentation, restrict name use, revise repository labels, withdraw or supersede releases where necessary, notify affected actors where appropriate, and preserve correction records.
4.8.8 Participation in a Program, Lab, Council, Nexus Universe Activity, Observatory Exercise, Academy Track, or Validation Sprint Is Not Certification. 4.8.8(a) Participation in any GCRI Canada program, lab, council, committee, working group, review session, Nexus Universe activity, Nexus Observatory exercise, Academy track, fellowship, residency, training program, validation sprint, technical review, benchmark activity, test activity, public authority learning activity, or public-safe reporting process shall not constitute certification by default.
4.8.8(b) Participation may evidence attendance, contribution, learning, review, discussion, testing, demonstration, observation, collaboration, research, technical contribution, or evidence submission within a defined scope, but shall not certify the participant, provider, technology, system, project, node, maturity state, readiness state, public authority status, finance-readiness, insurance-readiness, procurement status, protocol status, or Nexus compatibility.
4.8.8(c) Completion of an Academy track, fellowship, training program, validation sprint, exercise, lab activity, council participation, or program milestone may be recorded where accurate, but shall not constitute regulated certification, professional qualification, public authority qualification, procurement prequalification, provider certification, finance-readiness, protocol entitlement, recognition, or execution authority by default.
4.8.8(d) Participation records shall identify participant, role, scope, activity, date, contribution, attendance or completion status where applicable, limitations, public-safe status, confidentiality restrictions, data restrictions, public claims limits, correction path, and non-certification status.
4.8.8(e) No participant shall use participation to claim certified status, preferred provider status, public authority approval, procurement advantage, finance-readiness, insurance-readiness, protocol entitlement, recognition, Nexus approval, operational validation, or public-good legitimacy beyond the record.