XX. ASSURANCE
20.1 Risk Management Purpose
20.1.1 Risk Management as Charter-Level Institutional Discipline. 20.1.1(a) Risk management shall be a Charter-level institutional discipline of GCRI Canada and shall govern the identification, assessment, ownership, control, monitoring, escalation, correction, renewal, and assurance of risks affecting GCRI Canada’s public-benefit mission, lawful authority, evidence integrity, methods integrity, public trust, legal separateness, non-execution, Public-Good Stack role separation, data rights, cybersecurity, protected knowledge, public authority boundaries, finance-readiness boundaries, and Nexus interoperability.
20.1.1(b) Risk management shall not be treated as an optional administrative process, insurance exercise, reputational exercise, or after-the-fact incident response. It shall be an embedded governance discipline through which GCRI Canada anticipates, prevents, detects, corrects, and learns from risk across all material institutional functions.
20.1.1(c) Risk management shall apply to strategic decisions, Board decisions, officer delegations, programs, research, evidence, methods, data, AI systems, compute environments, cybersecurity, public-good software, Open Technical Baselines, technical releases, publications, dashboards, maps, controlled rooms, clean rooms, public authority learning, sponsorships, grants, donations, provider participation, community interfaces, and Nexus interfaces.
20.1.1(d) Risk management shall be read with GCRI Canada’s legal compliance, records, correctionability, data governance, cybersecurity, finance-boundary, public authority-boundary, publication, participation, governance, and fiscal provisions.
20.1.1(e) The controlling rule shall be that risk management is a constitutional safeguard of lawful public-benefit work.
20.1.2 Risk Management as Identification, Assessment, Ownership, Control, Monitoring, Escalation, Correction, and Renewal. 20.1.2(a) Risk management shall include identification, assessment, ownership, custody, classification, scoring where used, treatment, control design, control operation, monitoring, escalation, correction, assurance, renewal, and closure where appropriate.
20.1.2(b) Identification shall determine the nature of the risk, affected activity, affected records, affected persons, affected communities, affected Public Authorities, affected systems, affected data, affected publications, affected interfaces, affected obligations, and affected trust surfaces.
20.1.2(c) Assessment shall consider likelihood, severity, legal consequence, public-benefit consequence, public trust consequence, data sensitivity, AI risk, cybersecurity risk, protected knowledge risk, Public Authority sensitivity, finance sensitivity, cross-border exposure, technical complexity, and downstream reliance.
20.1.2(d) Ownership shall identify the accountable risk owner, operational custodian, control owner, escalation path, review cycle, and Board or committee reporting threshold.
20.1.2(e) Control shall include preventive, detective, corrective, compensating, procedural, technical, legal, governance, training, access, publication, public-safe, and records controls as appropriate.
20.1.2(f) Monitoring and renewal shall ensure that risks remain current as law, technology, data, participants, funding, public authority relationships, public claims, Nexus interfaces, and institutional scale change.
20.1.2(g) The controlling rule shall be that unmanaged risk is not merely unidentified exposure; it is a failure of institutional stewardship.
20.1.3 Risk Management as Applicable to Governance, Research, Evidence, Methods, Data, AI, Cybersecurity, Public-Good Software, Technical Baselines, Public Authority Interfaces, Finance Boundaries, Publications, Community Safeguards, Participants, Sponsors, Providers, Hosts, and Nexus Interfaces. 20.1.3(a) Risk management shall apply to governance, fiduciary duties, Board authority, officer authority, delegations, committees, councils, Working Groups, research, evidence, methods, observability, ontology, technical truth, public-good software, Open Technical Baselines, data, AI, compute, cybersecurity, technical assets, publications, public claims, dashboards, maps, Academy materials, public authority learning materials, and public-safe outputs.
20.1.3(b) Risk management shall apply to Public Authority interfaces, including observer status, regulator-listening status, public finance reader status, emergency-management participation, data contributions, public authority learning, public authority references, public authority rooms, dashboards, maps, and public-safe communications.
20.1.3(c) Risk management shall apply to finance boundaries, including GRA interfaces, Proof Pack inputs, capital-reader rooms, RNFD / NFD / UNFSD support, finance-sensitive data, public finance readers, insurance-readiness references, token / blockchain / DLT / DePIN interfaces, proof receipts, and finance-sensitive public claims.
20.1.3(d) Risk management shall apply to sponsors, donors, funders, providers, hosts, universities, laboratories, contractors, fellows, advisors, participants, contributors, communities, Indigenous knowledge holders, civil society, media, National Companies, Project SPVs, and Nexus actors.
20.1.3(e) The controlling rule shall be that risk management follows institutional activity wherever authority, data, technology, money, public meaning, or trust may move.
20.1.4 Risk Management as Public-Benefit Protection, Not Risk Transfer, Insurance Underwriting, Rating, Guarantee, or Public Authority Determination. 20.1.4(a) Risk management by GCRI Canada shall be a public-benefit protection discipline and shall not be treated as risk transfer, insurance underwriting, credit rating, guarantee, certification, public finance approval, public authority determination, emergency command, public warning, procurement approval, provider endorsement, or regulated professional risk service by default.
20.1.4(b) GCRI Canada may identify, classify, assess, monitor, mitigate, and correct risks affecting its own mission, records, evidence, methods, public-safe outputs, public authority learning, technical baselines, and Nexus interfaces, but such work shall not create external approval, insurability, creditworthiness, investment readiness, finance-readiness, maturity recognition, regulatory compliance, procurement eligibility, or public authority adoption.
20.1.4(c) Risk reports, registers, dashboards, maps, heat maps, risk notes, assurance findings, technical risk summaries, and public-safe risk communications shall include boundary language where necessary to prevent reliance as insurance, rating, guarantee, public warning, public authority decision, finance-readiness determination, or certification.
20.1.4(d) Where risk materials are read by capital readers, Public Authorities, providers, sponsors, communities, or media, GCRI Canada shall preserve role clarity, source limits, uncertainty, public-safe status, and correction paths.
20.1.4(e) The controlling rule shall be that GCRI Canada manages institutional risk to protect public trust, not to sell or assign risk status to others.
20.1.5 Risk Management as Distinct From Regulated Enterprise Risk Services Unless Separately Authorized and Properly Controlled. 20.1.5(a) GCRI Canada’s risk management shall be distinct from regulated enterprise risk services, professional advisory services, insurance services, investment advisory services, credit assessment services, engineering certification, compliance certification, public authority determination, public warning, emergency command, procurement advisory, and execution services unless separately authorized by competent authority and properly controlled outside GCRI Canada’s prohibited functions.
20.1.5(b) GCRI Canada shall not present its risk management outputs as enterprise risk ratings, investment risk ratings, insurance ratings, credit ratings, bankability opinions, procurement evaluations, regulatory compliance opinions, engineering certifications, public safety determinations, or official hazard notices.
20.1.5(c) Where GCRI Canada contributes risk evidence to another competent actor, such contribution shall be bounded by source authority, purpose, classification, limitations, role separation, permitted use, prohibited use, and correction path.
20.1.5(d) Any activity that may be interpreted as regulated risk service shall require legal review, role classification, boundary language, records, and refusal where the activity would exceed GCRI Canada’s lawful role.
20.1.5(e) The controlling rule shall be that risk literacy and evidence stewardship shall not become unauthorized professional or regulated risk activity.
20.1.6 Risk Management as Integrated With Validity-by-Record, Correctionability, Non-Execution, Public-Safe Publication, and Legal Separateness. 20.1.6(a) Risk management shall be integrated with validity-by-record, correctionability, non-execution, public-safe publication, legal separateness, controlled vocabulary, authoritative repositories, Gazette discipline where applicable, and no-silent-effect discipline.
20.1.6(b) A material risk position shall not be treated as institutionally valid unless recorded with owner, authority, scope, classification, evidence basis, review status, limitations, controls, treatment, escalation path, and correction path.
20.1.6(c) Risk management shall support correctionability by identifying outdated risk assessments, incorrect risk ratings, unsupported assumptions, failed controls, stale evidence, unsafe public materials, uncorrected incidents, and downstream dependencies requiring correction.
20.1.6(d) Risk management shall preserve non-execution by ensuring that risk outputs do not become commands, approvals, public authority actions, financial determinations, provider preferences, certification, procurement steering, or operational execution instructions.
20.1.6(e) Risk management shall preserve legal separateness by distinguishing GCRI Canada’s risks, records, controls, liabilities, and decisions from those of GCRI US, GRF, GRA, Protocol Authority, Nexus entities, National Companies, Project SPVs, providers, sponsors, hosts, Public Authorities, universities, and capital actors.
20.1.6(f) The controlling rule shall be that risk management is valid only when it is recorded, bounded, correctable, non-executing, and entity-specific.
20.1.7 Risk Management as Preventive, Detective, Corrective, and Learning-Oriented. 20.1.7(a) Risk management shall be preventive, detective, corrective, and learning-oriented.
20.1.7(b) Preventive risk management shall include policy, training, access controls, legal review, ethics review, data minimization, AI-use controls, cybersecurity controls, public claims review, Public Authority capacity classification, finance-boundary review, protected knowledge safeguards, contract clauses, and role separation.
20.1.7(c) Detective risk management shall include monitoring, assurance, register review, access review, publication review, incident reporting, anomaly detection, dashboard review, repository review, audit trails, issue registers, and stakeholder challenge pathways.
20.1.7(d) Corrective risk management shall include holds, quarantines, access restrictions, corrections, reclassifications, downgrades, suspensions, withdrawals, retractions, takedowns, public-safe notices, controlled notices, legal review, remediation, and assurance follow-up.
20.1.7(e) Learning-oriented risk management shall convert incidents, near misses, assurance findings, public challenges, participant grievances, technical failures, publication corrections, and legal changes into updated controls, training, registers, policies, and Board oversight.
20.1.7(f) The controlling rule shall be that risk management shall improve institutional behavior, not merely document institutional exposure.
20.1.8 Risk Management as Board, Officer, Committee, Staff, Fellow, Advisor, Contributor, Sponsor, Provider, Host, Public Authority, Community, and Participant Responsibility Where Relevant. 20.1.8(a) Risk management shall be a responsibility of the Board, Officers, committees, staff, contractors, fellows, advisors, contributors, maintainers, Working Groups, councils, sponsors, donors, funders, providers, hosts, universities, Public Authorities, communities, capital readers, and participants where relevant to their roles, access, authority, and activities.
20.1.8(b) The Board shall oversee enterprise-level risk governance, risk appetite where adopted, prohibited risks, material risk escalation, control assurance, mission drift risk, non-execution risk, legal separateness risk, and public trust risk.
20.1.8(c) Officers shall implement risk management through policies, procedures, controls, registers, training, incident response, escalation, correction, and reporting.
20.1.8(d) Committees and councils shall identify and escalate risks within their mandates but shall not assume Board authority, public authority, finance authority, certification authority, procurement authority, or execution authority by risk discussion.
20.1.8(e) External participants shall comply with risk controls, room rules, confidentiality, data rules, AI-use limits, public claims limits, Public Authority boundary language, finance-boundary language, conflict disclosures, and correction obligations.
20.1.8(f) The controlling rule shall be that risk responsibility is distributed by role, while risk authority remains governed by proper records and lawful delegation.
20.1.9 Risk Management as Proportionate to Public-Benefit Consequence, Legal Risk, Data Sensitivity, Technical Complexity, Public Authority Sensitivity, Finance Sensitivity, Community Sensitivity, and Public Trust Risk. 20.1.9(a) Risk management shall be proportionate to public-benefit consequence, legal risk, data sensitivity, technical complexity, AI complexity, cybersecurity exposure, Public Authority sensitivity, finance sensitivity, community sensitivity, protected knowledge sensitivity, cross-border exposure, publication reach, and public trust risk.
20.1.9(b) Higher-risk activities shall require heightened review, stronger records, clearer owners, tighter access controls, more explicit boundary language, legal review where required, public-safe review, Board or committee visibility, and assurance follow-up.
20.1.9(c) Lower-risk activities may use proportionate controls, provided that non-execution, records validity, privacy, cybersecurity, Public Authority boundaries, finance boundaries, provider neutrality, sponsor non-control, protected knowledge, and correctionability remain preserved.
20.1.9(d) Proportionality shall not be used to waive prohibited-function boundaries, legal obligations, privacy obligations, data protection obligations, cybersecurity obligations, protected knowledge safeguards, sanctions controls, export-control controls, or anti-inurement controls.
20.1.9(e) The controlling rule shall be that risk controls may scale by risk, but constitutional boundaries do not disappear at lower scale.
20.1.10 Risk Management Records as Material Constitutional Records. 20.1.10(a) Risk management records shall be material constitutional records of GCRI Canada.
20.1.10(b) Such records shall include risk registers, issue registers, control registers, risk assessments, treatment plans, accepted risk records, prohibited risk records, escalation records, incident records, assurance findings, corrective action plans, risk appetite statements where adopted, risk tolerance decisions, Board reports, committee reports, control testing records, exception records, and lessons-learned records.
20.1.10(c) Risk records shall identify owner, custodian, authority, scope, affected Charter Part, risk domain, evidence basis, classification, severity, likelihood where used, treatment, controls, residual risk, review cycle, escalation threshold, dependencies, limitations, public-safe status where applicable, and correction path.
20.1.10(d) Risk records shall be retained, classified, access-controlled, versioned, protected from silent edit, linked to relevant registers, and subject to legal hold where required.
20.1.10(e) The controlling rule shall be that risk governance must be provable by record before it can be relied upon.
20.2 Institutional Risk Register
20.2.1 Requirement to Maintain an Institutional Risk Register. 20.2.1(a) GCRI Canada shall maintain an Institutional Risk Register covering material risks to its mission, governance, legal compliance, public-benefit status, evidence integrity, methods integrity, data rights, AI governance, cybersecurity, public-safe publication, public authority boundaries, finance boundaries, community safeguards, technical assets, participants, support relationships, Nexus interfaces, continuity, reputation, and public trust.
20.2.1(b) The Institutional Risk Register shall identify risk title, risk description, domain, owner, custodian, affected Charter Parts, affected policies, affected records, affected systems, affected participants, affected Public Authorities, affected data classes, affected public materials, likelihood where used, severity, inherent risk, controls, residual risk, treatment plan, review date, escalation threshold, related issues, related incidents, and Board or committee reporting status.
20.2.1(c) The Register shall include current risks, emerging risks, systemic risks, cross-cutting risks, unresolved risks, accepted risks, prohibited risks, and risks under treatment.
20.2.1(d) The Register shall not be used to normalize prohibited functions or accept risks that the Charter forbids.
20.2.1(e) The controlling rule shall be that material institutional risks must be visible, owned, controlled, reviewed, and correctable.
20.2.2 Governance Risk. 20.2.2(a) Governance Risk means risk affecting Board stewardship, fiduciary duty, officer delegation, committee function, council function, conflict management, related-party controls, mission lock, legal separateness, records validity, and lawful authority.
20.2.2(b) Governance Risk may arise from informal decision-making, founder control, sponsor influence, provider influence, committee overreach, council overreach, unclear delegations, missing records, conflicts, recusal failures, stale policies, defective meetings, or unclear public claims authority.
20.2.2(c) Governance Risk controls may include Board-reserved matters, delegation registers, conflict registers, recusal records, committee charters, council terms, governance training, meeting records, decision packs, legal review, and governance assurance.
20.2.2(d) Governance Risk shall be escalated where institutional authority, legal compliance, mission lock, Board oversight, or public trust may be affected.
20.2.2(e) The controlling rule shall be that governance risk is constitutional risk because governance determines institutional authority.
20.2.3 Fiduciary Risk. 20.2.3(a) Fiduciary Risk means risk that Directors, Officers, or other persons exercising authority fail to act with required duty, care, loyalty, prudence, independence, good faith, mission fidelity, conflict discipline, or lawful oversight.
20.2.3(b) Fiduciary Risk may arise from inadequate information, conflicts, related-party transactions, private benefit, inurement, sponsor capture, provider capture, unreviewed legal risk, weak financial controls, failure to oversee data and cybersecurity, failure to correct, or failure to preserve non-execution.
20.2.3(c) Controls shall include Board training, briefing materials, legal review, financial review, conflict disclosure, recusal, independent review, Board minutes, committee reporting, risk reporting, assurance findings, and corrective action tracking.
20.2.3(d) Fiduciary Risk shall be treated as heightened where Board action could affect corporate status, tax status, public trust, legal separateness, restricted funds, Public Authority interfaces, finance-sensitive interfaces, protected knowledge, or major technical assets.
20.2.3(e) The controlling rule shall be that fiduciary risk must be controlled before judgment becomes institutional harm.
20.2.4 Mission Drift Risk. 20.2.4(a) Mission Drift Risk means risk that GCRI Canada moves away from its public-benefit, nonprofit, non-share, non-distributing, non-executing, evidence-and-methods, public-good technical mandate.
20.2.4(b) Mission Drift Risk may arise from commercial revenue pressure, sponsor expectations, provider expectations, grant conditions, public authority demand, capital-reader interest, media visibility, founder preference, operational convenience, technical enthusiasm, or Nexus role confusion.
20.2.4(c) Mission Drift Risk includes drift toward consultancy, execution, certification sales, finance-readiness sales, procurement advice, provider marketplace, public authority substitute, emergency command, public warning system, data brokerage, proprietary enclosure, or regulated financial activity.
20.2.4(d) Controls shall include mission-lock review, Board oversight, legal review, revenue review, contract review, public claims review, support-without-control rules, provider neutrality, finance-boundary review, public authority-boundary review, and correctionability.
20.2.4(e) The controlling rule shall be that mission drift must be identified early because drift often begins as useful work without boundaries.
20.2.5 Non-Execution Boundary Risk. 20.2.5(a) Non-Execution Boundary Risk means risk that GCRI Canada is described, used, relied upon, or structured as executing downstream operational, market, public authority, emergency, procurement, finance, infrastructure, provider, or project activities.
20.2.5(b) Such risk may arise from dashboards, maps, public authority learning, technical baselines, public-good software, evidence packs, room participation, public claims, project support, provider demonstrations, National Company interfaces, Project SPV interfaces, or capital-reader contexts.
20.2.5(c) Controls shall include non-execution language, role classification, public claims review, contract clauses, Public Authority capacity records, GRA routing, GRF role separation, Protocol Authority separation, provider neutrality, and legal review where risk exists.
20.2.5(d) Non-Execution Boundary Risk shall be escalated where materials could be read as command, approval, public warning, procurement recommendation, finance determination, certification, or execution instruction.
20.2.5(e) The controlling rule shall be that GCRI Canada may inform action but shall not become the actor by implication.
20.2.6 Public-Good Stack Role-Separation Risk. 20.2.6(a) Public-Good Stack Role-Separation Risk means risk that GCRI Canada’s role is merged, confused, overstated, or collapsed with GRF, GRA, Protocol Authority, Nexus entities, Public Authorities, National Companies, Project SPVs, providers, sponsors, or capital actors.
20.2.6(b) Such risk may arise through shared records, shared events, shared doctrine, shared branding, shared rooms, shared technical baselines, shared public authority interfaces, shared capital-reader materials, shared public claims, or shared participants.
20.2.6(c) Controls shall include controlled vocabulary, role language, legal-separateness clauses, interface records, shared-record boundaries, divergence logs, equivalence notes, public claims review, and entity-boundary assurance.
20.2.6(d) This risk shall be heightened where public audiences, Public Authorities, capital readers, sponsors, providers, or media may infer authority, recognition, finance-readiness, certification, protocol effect, procurement approval, or execution authority.
20.2.6(e) The controlling rule shall be that interoperability must never become role collapse.
20.2.7 Evidence Integrity Risk. 20.2.7(a) Evidence Integrity Risk means risk that evidence is inaccurate, unsupported, stale, misclassified, incomplete, biased, fabricated, altered, untraceable, overgeneralized, overclaimed, taken out of context, or used beyond source authority.
20.2.7(b) Evidence Integrity Risk may arise through weak source lineage, poor intake, missing metadata, AI hallucination, inadequate review, stale data, biased samples, provider influence, sponsor influence, Public Authority misdescription, missing limitations, or public claims inflation.
20.2.7(c) Controls shall include evidence intake records, source lineage, Case IDs, metadata standards, review gates, peer or expert review where appropriate, public-safe review, versioning, no-silent-edit rules, correction paths, and evidence registers.
20.2.7(d) Evidence Integrity Risk shall be escalated where evidence supports public materials, Public Authority learning, finance-sensitive materials, technical baselines, dashboards, maps, datasets, or GRA / GRF / Protocol Authority interfaces.
20.2.7(e) The controlling rule shall be that public-good evidence must remain source-valid, limitation-aware, and correctionable.
20.2.8 Methods Integrity Risk. 20.2.8(a) Methods Integrity Risk means risk that methods, frameworks, evaluation harnesses, ontology, controlled vocabulary, benchmarks, Truth Engine methods, Observatory methods, technical baselines, or public-good software are flawed, unreviewed, biased, unreproducible where reproducibility is required, misapplied, unversioned, unsafe, or overclaimed.
20.2.8(b) Such risk may arise through weak protocol design, untested assumptions, hidden dependencies, unclear definitions, translation drift, benchmark misuse, model drift, software bugs, insecure dependencies, or uncontrolled adaptation across jurisdictions.
20.2.8(c) Controls shall include method records, protocol records, controlled vocabulary governance, versioning, change logs, review gates, reproducibility packages where lawful, limitation statements, technical release controls, and correction procedures.
20.2.8(d) Methods Integrity Risk shall be heightened where methods influence public authority learning, finance-sensitive evidence, public-safe reports, dashboards, maps, datasets, software releases, or Nexus interoperability.
20.2.8(e) The controlling rule shall be that methods must be as governed as evidence because methods determine what evidence can mean.
20.2.9 Research Integrity Risk. 20.2.9(a) Research Integrity Risk means risk affecting research ethics, human-subjects protections, protocols, peer review, reproducibility, conflicts, independence, authorship, data governance, publication, correction, and protected knowledge safeguards.
20.2.9(b) Research Integrity Risk may arise from inadequate ethics review, consent gaps, vulnerable participant risk, community extraction, Indigenous or protected knowledge misuse, sponsor influence, provider influence, publication suppression, AI misuse, false citation, undisclosed conflicts, or failure to correct.
20.2.9(c) Controls shall include research protocols, ethics review, community review where appropriate, protected knowledge protocols, conflict disclosures, peer review, AI-use records, data governance, publication review, and research correction procedures.
20.2.9(d) Research Integrity Risk shall be escalated where research affects people, communities, health, Public Authorities, rights-bearing data, public-safe publications, dashboards, maps, or policy-facing materials.
20.2.9(e) The controlling rule shall be that research integrity protects both truth and the people affected by truth-seeking.
20.2.10 Publication and Public Claims Risk. 20.2.10(a) Publication and Public Claims Risk means risk that publications, reports, dashboards, maps, datasets, software releases, technical notes, Academy materials, public authority learning materials, media statements, websites, social media, or public claims are inaccurate, unsupported, misleading, unsafe, overbroad, defamatory, rights-infringing, or authority-inflating.
20.2.10(b) Such risk may include Public Authority overclaim, finance-readiness overclaim, certification overclaim, recognition overclaim, provider preference, sponsor validation, procurement implication, public warning implication, emergency command implication, technical claim overstatement, impact claim inflation, or unsupported “verified,” “validated,” “approved,” “trusted,” or “ready” language.
20.2.10(c) Controls shall include claims substantiation, controlled vocabulary, publication classes, review gates, legal review where risk exists, public-safe review, disclaimers, versioning, correction notices, withdrawal, and retraction.
20.2.10(d) Publication and Public Claims Risk shall be heightened where materials are public, media-facing, Public Authority-facing, capital-facing, provider-facing, sponsor-facing, community-facing, or relied upon downstream.
20.2.10(e) The controlling rule shall be that public language is a risk surface because public meaning can exceed institutional authority.
20.2.11 Data Rights and Privacy Risk. 20.2.11(a) Data Rights and Privacy Risk means risk affecting personal information, sensitive personal information, health-sensitive data, rights-bearing data, Public Authority Data, community-protected data, Indigenous Knowledge, Local Knowledge, Territorial Knowledge, Cultural Knowledge, Environmental Knowledge, Protected Knowledge, cross-border data, sovereign data, and data rights.
20.2.11(b) Such risk may arise from over-collection, unclear lawful basis, missing notice, consent failure, unauthorized access, unauthorized sharing, improper AI use, uncontrolled embedding, cross-border transfer, stale retention, re-identification, public release error, weak deletion, or vendor misuse.
20.2.11(c) Controls shall include data classification, lawful basis review, purpose limitation, minimization, privacy notices, consent records where applicable, data rights processes, impact assessments, access controls, retention rules, deletion rules, breach response, and public-safe release review.
20.2.11(d) Data Rights and Privacy Risk shall be escalated where affected data is sensitive, rights-bearing, public authority-related, health-related, community-protected, protected knowledge-related, cross-border, AI-used, or public-facing.
20.2.11(e) The controlling rule shall be that data risk is rights risk, not merely information-management risk.
20.2.12 AI and Model Governance Risk. 20.2.12(a) AI and Model Governance Risk means risk arising from AI systems, models, embeddings, retrieval, inference, agentic AI, AI-assisted writing, AI-assisted coding, AI-assisted research, AI-assisted publication, AI dashboards, AI maps, AI outputs, AI vendors, and model-dependent workflows.
20.2.12(b) Such risk may include hallucination, false citation, bias, discrimination, data leakage, prompt leakage, unauthorized training, unauthorized fine-tuning, unauthorized embedding, unauthorized model improvement, stale retrieval, model drift, unsafe output, unauthorized agent action, overreliance, or AI-as-authority overclaim.
20.2.12(c) Controls shall include AI use inventory, model register, inference records, data authority review, vendor review, human review, impact review, bias review, safety review, AI-use restrictions, logging controls, deletion controls, and AI incident response.
20.2.12(d) AI and Model Governance Risk shall be heightened where AI affects Public Authorities, employment, research, health, finance-sensitive contexts, public-safe publications, dashboards, maps, rights-bearing data, or protected knowledge.
20.2.12(e) The controlling rule shall be that AI may support judgment but must not replace authority, review, records, or legal basis.
20.2.13 Cybersecurity and Technical Asset Risk. 20.2.13(a) Cybersecurity and Technical Asset Risk means risk affecting systems, repositories, public-good software, Open Technical Baselines, APIs, schemas, datasets, models, dashboards, maps, compute environments, controlled rooms, clean rooms, data rooms, secrets, keys, tokens, identities, release pipelines, SBOMs, dependencies, and technical infrastructure.
20.2.13(b) Such risk may include unauthorized access, weak authentication, credential compromise, secrets exposure, malicious pull request, repository compromise, insecure dependency, supply-chain attack, API compromise, dashboard compromise, AI leakage, insecure release, insufficient logging, backup failure, or vendor compromise.
20.2.13(c) Controls shall include system classification, identity and access management, MFA where appropriate, secrets management, repository security, secure development, secure release, vulnerability management, SBOMs, logging, incident response, backup, disaster recovery, and third-party security review.
20.2.13(d) Cybersecurity and Technical Asset Risk shall be escalated where Public Authority Data, personal information, protected knowledge, cyber-sensitive materials, infrastructure-sensitive materials, controlled technology, public interfaces, or critical repositories are affected.
20.2.13(e) The controlling rule shall be that technical integrity is a public trust condition.
20.2.14 Public Authority Boundary Risk. 20.2.14(a) Public Authority Boundary Risk means risk that GCRI Canada participation, materials, public authority learning, dashboards, maps, reports, rooms, data contributions, or references are understood as endorsement, adoption, regulation, procurement approval, funding approval, public finance approval, public warning, emergency command, official guidance, or sovereign obligation.
20.2.14(b) This risk may arise through Public Authority attendance, logos, names, titles, quotes, photos, agency names, jurisdictions, data contributions, regulator-listening status, public finance reader status, emergency-management participation, or public infrastructure participation.
20.2.14(c) Controls shall include capacity classification, reference approval, Public Authority Data terms, non-endorsement language, no-public-warning language, no-command language, public authority room controls, public-safe review, and correction procedures.
20.2.14(d) Public Authority Boundary Risk shall be treated as heightened because public power can be implied by proximity.
20.2.14(e) The controlling rule shall be that Public Authority meaning must arise only from competent public authority action, not GCRI Canada context.
20.2.15 Finance-Readiness Boundary Risk. 20.2.15(a) Finance-Readiness Boundary Risk means risk that GCRI Canada materials, evidence, Proof Pack inputs, GRA interfaces, capital-reader rooms, RNFD / NFD / UNFSD support, dashboards, maps, public authority learning, technical baselines, token / DLT / DePIN systems, proof receipts, or public claims are understood as finance-readiness, investment advice, insurance approval, rating, guarantee, public finance approval, lending approval, capital commitment, or transaction recommendation.
20.2.15(b) This risk may arise through capital-reader audiences, sponsor materials, provider materials, project materials, public finance readers, insurance-sensitive language, “bankable,” “investable,” “ready,” “rated,” “guaranteed,” “approved,” or similar terms.
20.2.15(c) Controls shall include GRA routing, finance-safe language, capital-reader room controls, no-advice language, no-solicitation language, no-rating language, no-guarantee language, no-public-finance-approval language, legal review, and correction.
20.2.15(d) Finance-Readiness Boundary Risk shall be escalated where public or market reliance may occur.
20.2.15(e) The controlling rule shall be that technical evidence shall not become financial reliance by audience, phrasing, or repetition.
20.2.16 Sponsor, Donor, Funder, Provider, Host, and Participant Capture Risk. 20.2.16(a) Sponsor, Donor, Funder, Provider, Host, and Participant Capture Risk means risk that support, funding, in-kind contributions, facilities, technical tools, data, compute, participation, visibility, or access influence GCRI Canada’s governance, evidence, methods, publications, corrections, Public Authority access, technical baselines, public claims, or institutional priorities.
20.2.16(b) Capture risk may arise through restricted funding, sponsor review rights, provider tools, host dependence, donor preferences, grant conditions, publication pressure, correction suppression, platform dependency, data dependency, event dependency, or repeated informal influence.
20.2.16(c) Controls shall include support-without-control clauses, conflict review, independence review, public acknowledgment rules, provider neutrality, sponsor non-control, restricted fund controls, contract clauses, publication independence, correction rights, and assurance.
20.2.16(d) Capture risk shall be escalated where support appears to purchase outcomes, access, recognition, finance-readiness, certification, public authority proximity, provider status, or public meaning.
20.2.16(e) The controlling rule shall be that support may fund public-good infrastructure but shall not own institutional truth.
20.2.17 Community Safeguards and Protected Knowledge Risk. 20.2.17(a) Community Safeguards and Protected Knowledge Risk means risk of harm, extraction, misdescription, exposure, re-identification, stigmatization, cultural harm, ecological harm, unsafe mapping, protected person exposure, or misuse of Indigenous Knowledge, Local Knowledge, Territorial Knowledge, Cultural Knowledge, Environmental Knowledge, community-protected data, or Protected Knowledge.
20.2.17(b) Such risk may arise through research, data collection, dashboards, maps, AI outputs, public reports, datasets, repositories, media, public authority learning, sensor data, geospatial data, environmental data, or public-safe summaries.
20.2.17(c) Controls shall include consent and non-consent handling where applicable, community review, Indigenous or protected knowledge protocols, public-safe mapping review, aggregation, redaction, access limits, grievance pathways, correction pathways, and withdrawal or sealing where required.
20.2.17(d) This risk shall be escalated where vulnerable communities, remote communities, protected persons, sensitive sites, ecological vulnerabilities, public health issues, or cultural materials may be affected.
20.2.17(e) The controlling rule shall be that public-good evidence shall not be created by unsafe extraction from communities or protected knowledge holders.
20.2.18 Legal, Tax, Sanctions, Export-Control, Competition, Professional-Boundary, and Contract Risk. 20.2.18(a) Legal, Tax, Sanctions, Export-Control, Competition, Professional-Boundary, and Contract Risk means risk that GCRI Canada’s activities, relationships, funding, contracts, data, technology, publications, public claims, or interfaces breach applicable legal obligations or create unauthorized legal roles.
20.2.18(b) Such risk may include corporate noncompliance, tax-status drift, improper receipting, private benefit, inurement, sanctions exposure, export-control breach, restricted-party engagement, competition-sensitive exchange, procurement steering, professional advice overclaim, unauthorized legal advice, contract breach, grant breach, or platform-term breach.
20.2.18(c) Controls shall include legal review triggers, compliance calendars, screening registers, controlled technology registers, contract review, grant review, procurement neutrality controls, professional-boundary language, and compliance assurance.
20.2.18(d) Legal risk shall be escalated where ambiguity, regulated perimeter, cross-border activity, controlled technology, public authority involvement, finance sensitivity, or public harm exists.
20.2.18(e) The controlling rule shall be that legal compliance risk must be treated as institutional risk, not merely external advisory risk.
20.2.19 Operational, People, Continuity, Reputation, and Public Trust Risk. 20.2.19(a) Operational, People, Continuity, Reputation, and Public Trust Risk means risk affecting the availability, reliability, staffing, competence, culture, continuity, public understanding, reputation, legitimacy, and resilience of GCRI Canada.
20.2.19(b) Such risk may arise from key-person dependency, inadequate staffing, weak training, contractor misclassification, volunteer overreliance, platform dependency, funding dependency, system outage, repository failure, incident response weakness, public misdescription, media distortion, unresolved corrections, or public trust erosion.
20.2.19(c) Controls shall include workforce planning, role documentation, training, backup, succession planning, business continuity, disaster recovery, communications controls, public-safe correction, incident response, records assurance, and Board reporting.
20.2.19(d) Reputation Risk shall be assessed as public trust risk and shall not be used to suppress lawful correction, transparency, affected-person notice, protected knowledge remedy, or public-safe clarification.
20.2.19(e) The controlling rule shall be that institutional reputation is protected by truth, correction, continuity, and trustworthiness, not by concealment.
20.2.20 Risk Register Ownership, Review Cycle, Scoring, Treatment, and Board Reporting. 20.2.20(a) The Institutional Risk Register shall have a designated owner, custodian, review cycle, scoring method where adopted, treatment method, escalation criteria, and Board or committee reporting process.
20.2.20(b) Risk scoring, where used, shall be consistent, documented, proportionate, and capable of reflecting likelihood, severity, public-benefit consequence, legal consequence, public trust consequence, data sensitivity, Public Authority sensitivity, finance sensitivity, protected knowledge sensitivity, and control effectiveness.
20.2.20(c) Risk treatment shall include avoidance, mitigation, transfer where lawful and appropriate, acceptance where permitted, escalation, correction, monitoring, or refusal. Transfer shall not be used to transfer GCRI Canada’s mission duties, legal duties, correction duties, public authority boundaries, finance boundaries, data duties, or protected knowledge duties.
20.2.20(d) Material risks, prohibited risks, accepted risks, unresolved high risks, repeated issues, failed controls, and assurance findings shall be reported to the Board or authorized committee.
20.2.20(e) The controlling rule shall be that risk registers must drive governance action, not merely preserve institutional memory.
20.3 Issue Register
20.3.1 Requirement to Maintain an Issue Register for Active Problems. 20.3.1(a) GCRI Canada shall maintain an Issue Register for active problems, unresolved control failures, open corrective actions, emerging operational defects, known weaknesses, repeated exceptions, near misses, unresolved incidents, failed reviews, stale records, unsafe public materials, and other matters requiring active management.
20.3.1(b) The Issue Register shall differ from the Institutional Risk Register by tracking specific active issues requiring action, owner assignment, due dates, interim controls, correction, verification, and closeout.
20.3.1(c) Issues may arise from audits, assurance, incidents, complaints, grievances, legal review, public challenges, community feedback, Public Authority clarification, capital-reader confusion, publication correction, data review, AI review, cybersecurity review, or Board oversight.
20.3.1(d) Issues shall not remain unmanaged because they are small, inconvenient, politically sensitive, sponsor-sensitive, provider-sensitive, public authority-sensitive, finance-sensitive, or reputationally uncomfortable.
20.3.1(e) The controlling rule shall be that known problems must be owned, tracked, corrected, and closed by record.
20.3.2 Issue Intake. 20.3.2(a) Issue intake shall provide a defined pathway for reporting, recording, and triaging active problems.
20.3.2(b) Intake shall identify reporter, date, source, issue description, affected Charter Part, affected records, affected systems, affected persons, affected communities, affected Public Authorities, affected sponsors or providers, affected publications, affected data classes, urgency, suspected severity, and immediate controls needed.
20.3.2(c) Issue sources may include staff reports, participant reports, Board requests, committee findings, assurance findings, incident reports, community grievances, Public Authority feedback, sponsor or provider notices, legal reviews, cybersecurity alerts, privacy requests, and publication corrections.
20.3.2(d) Intake shall allow good-faith reporting without retaliation.
20.3.2(e) The controlling rule shall be that issue intake must make problems visible before they become incidents.
20.3.3 Issue Classification. 20.3.3(a) Issues shall be classified by domain, severity, urgency, affected authority, affected records, affected controls, affected obligations, affected public materials, affected data, affected technology, affected people, affected communities, affected Public Authorities, affected finance boundaries, and affected Nexus interfaces.
20.3.3(b) Issue domains may include governance, fiduciary, mission drift, non-execution, evidence, methods, research, records, correction, data, AI, cybersecurity, publication, Public Authority boundary, finance boundary, fiscal, legal, tax, sanctions, export control, competition, contract, IP, workforce, community safeguards, protected knowledge, continuity, reputation, and public trust.
20.3.3(c) Classification shall identify whether the issue is also an incident, legal matter, compliance issue, privacy matter, cybersecurity matter, financial matter, public claims matter, research matter, Public Authority matter, or protected knowledge matter.
20.3.3(d) Classification shall be updated where facts change.
20.3.3(e) The controlling rule shall be that issue classification determines the correct controls, not the preferred narrative.
20.3.4 Issue Severity. 20.3.4(a) Issue severity shall be determined using criteria proportionate to institutional risk.
20.3.4(b) Severity criteria shall consider legal consequence, public-benefit consequence, safety consequence, privacy consequence, cybersecurity consequence, Public Authority consequence, finance-boundary consequence, community consequence, protected knowledge consequence, reputational consequence, operational consequence, recurrence risk, and correction urgency.
20.3.4(c) Severity levels may include low, moderate, high, and critical, or another Board-approved scale, provided the scale is documented and applied consistently.
20.3.4(d) High or critical issues shall require escalation, interim controls, leadership visibility, Board or committee reporting where appropriate, and verified corrective action.
20.3.4(e) The controlling rule shall be that severity must reflect harm and authority risk, not internal discomfort.
20.3.5 Issue Owner and Custodian. 20.3.5(a) Each issue shall have an assigned owner and custodian.
20.3.5(b) The issue owner shall be accountable for corrective action, escalation, coordination, deadlines, verification, and closeout.
20.3.5(c) The issue custodian shall maintain the issue record, supporting materials, status updates, dependencies, interim controls, approvals, and closeout evidence.
20.3.5(d) Where an issue crosses domains, co-owners or supporting owners may be assigned, but one accountable owner shall remain identified.
20.3.5(e) The controlling rule shall be that no issue shall remain ownerless because it is cross-functional or politically sensitive.
20.3.6 Issue Root Cause. 20.3.6(a) Material issues shall receive root cause review proportionate to severity.
20.3.6(b) Root causes may include policy gap, training gap, authority ambiguity, weak recordkeeping, poor access control, unclear role language, inadequate legal review, sponsor pressure, provider pressure, public authority ambiguity, finance-boundary ambiguity, data control failure, AI misuse, cybersecurity weakness, technical defect, staffing gap, vendor failure, or governance failure.
20.3.6(c) Root cause review shall distinguish symptom, immediate cause, underlying cause, systemic cause, and recurrence pattern where appropriate.
20.3.6(d) Corrective action shall address root cause, not merely surface appearance.
20.3.6(e) The controlling rule shall be that repeated issues are evidence of control weakness until proven otherwise.
20.3.7 Issue Affected Records, Systems, Programs, Participants, Publications, Interfaces, or Public Materials. 20.3.7(a) Each issue shall identify affected records, systems, programs, participants, publications, dashboards, maps, datasets, repositories, rooms, public materials, contracts, grants, Public Authority interfaces, GRA interfaces, GRF interfaces, Protocol Authority interfaces, National Company interfaces, Project SPV interfaces, provider interfaces, sponsor interfaces, community interfaces, and Nexus interfaces where applicable.
20.3.7(b) Affected-record review shall identify whether any record requires correction, reclassification, hold, withdrawal, supersession, archive, sealing, deletion, legal hold, or public-safe notice.
20.3.7(c) Affected-system review shall identify whether access restriction, patching, configuration change, key rotation, vendor action, backup restoration, or system suspension is required.
20.3.7(d) Affected-public-material review shall identify whether public claims, publications, dashboards, maps, reports, social media, media materials, public authority references, sponsor references, or provider references require correction.
20.3.7(e) The controlling rule shall be that issues must be mapped to affected dependencies before they can be closed.
20.3.8 Issue Interim Controls, Holds, Quarantine, Access Restrictions, or Public-Safe Measures. 20.3.8(a) Interim controls shall be applied where an issue may create ongoing harm, reliance, legal exposure, data exposure, cybersecurity exposure, public authority confusion, finance overclaim, protected knowledge exposure, or public trust risk before final correction.
20.3.8(b) Interim controls may include activity hold, publication hold, public claims hold, data quarantine, AI-use restriction, model restriction, repository restriction, access suspension, controlled-room suspension, public authority reference hold, finance-sensitive material hold, payment hold, transfer block, or public-safe interim clarification.
20.3.8(c) Interim controls shall be proportionate, recorded, time-bound where appropriate, reviewed, and lifted only when conditions are met.
20.3.8(d) Interim controls shall not be used to conceal an issue or indefinitely avoid correction.
20.3.8(e) The controlling rule shall be that active issues require risk containment before final resolution where reliance or harm may continue.
20.3.9 Issue Corrective Action Plan. 20.3.9(a) Each material issue shall have a corrective action plan.
20.3.9(b) The corrective action plan shall identify issue, root cause, corrective action, responsible owner, due date, interim controls, affected records, affected systems, affected public materials, required approvals, required legal review, required public-safe review, required controlled notice, training updates, policy updates, register updates, verification method, and closeout criteria.
20.3.9(c) Corrective actions may include record correction, policy update, control redesign, training, access change, legal review, contract amendment, publication correction, public-safe notice, controlled notice, system patch, data deletion, AI restriction, provider remedy, sponsor correction, or participant discipline.
20.3.9(d) Corrective action shall be verified before closeout where the issue is material.
20.3.9(e) The controlling rule shall be that correction must be planned, assigned, verified, and recorded.
20.3.10 Issue Due Dates, Dependencies, Escalation Triggers, and Closeout. 20.3.10(a) Each issue shall identify due dates, dependencies, escalation triggers, and closeout requirements.
20.3.10(b) Due dates shall reflect severity, legal deadlines, public-safe urgency, data sensitivity, cybersecurity exposure, public authority sensitivity, finance sensitivity, protected knowledge risk, and operational feasibility.
20.3.10(c) Dependencies shall identify required approvals, legal review, Public Authority clarification, vendor action, participant action, Board action, technical work, data remediation, publication correction, or external notice.
20.3.10(d) Escalation triggers shall include missed deadlines, increased severity, failed interim controls, public reliance, legal notice obligation, repeated issue, unresolved owner dispute, or Board-level risk.
20.3.10(e) Closeout shall require evidence that corrective actions have been completed, verified, recorded, and linked to affected registers.
20.3.10(f) The controlling rule shall be that issues remain open until closure is evidenced, not merely asserted.
20.3.11 Issue Recurrence and Pattern Review. 20.3.11(a) GCRI Canada shall conduct recurrence and pattern review for issues.
20.3.11(b) Pattern review shall identify repeated control failures, repeated public claims overreach, repeated Public Authority confusion, repeated finance overclaim, repeated data handling errors, repeated AI misuse, repeated cybersecurity weakness, repeated training gaps, repeated policy exceptions, repeated sponsor or provider influence, and repeated record failures.
20.3.11(c) Recurrent issues shall be escalated as control failures, governance risks, training failures, cultural risks, or systemic risks where appropriate.
20.3.11(d) Pattern review may require policy redesign, control redesign, role redesign, system redesign, access restriction, relationship restriction, Board review, or assurance cycle changes.
20.3.11(e) The controlling rule shall be that recurrence converts an issue from isolated problem to systemic risk.
20.3.12 Issue Register Assurance and Board / Committee Reporting. 20.3.12(a) GCRI Canada shall conduct Issue Register Assurance and report material issues to the Board or authorized committee.
20.3.12(b) Assurance shall review whether issues are complete, correctly classified, owned, timely, controlled, escalated, corrected, verified, and closed with evidence.
20.3.12(c) Assurance shall identify stale issues, ownerless issues, overdue issues, repeated issues, under-classified issues, unresolved high-risk issues, ineffective corrective actions, and missing Board reporting.
20.3.12(d) Board or committee reporting shall include material issue status, trend analysis, overdue items, high-risk issues, corrective action progress, unresolved barriers, and recommended governance action.
20.3.12(e) The controlling rule shall be that issue management must be assured because known problems that remain unmanaged become governance failures.
20.4 Control Register
20.4.1 Requirement to Maintain a Control Register. 20.4.1(a) GCRI Canada shall maintain a Control Register identifying material controls used to prevent, detect, correct, monitor, and assure institutional risks.
20.4.1(b) The Control Register shall include governance controls, evidence controls, methods controls, research controls, publication controls, records controls, correction controls, data controls, AI controls, cybersecurity controls, technical asset controls, Public Authority boundary controls, finance-boundary controls, fiscal controls, sponsorship controls, grant controls, anti-inurement controls, community safeguard controls, protected knowledge controls, legal compliance controls, sanctions controls, export-control controls, competition controls, professional-boundary controls, workforce controls, and Nexus-interface controls.
20.4.1(c) Each control shall identify owner, custodian, purpose, risk mapped, policy source, procedure source, system source where applicable, frequency, evidence of operation, testing method, exceptions, failures, corrective actions, and review cycle.
20.4.1(d) Controls may be manual, automated, technical, legal, governance, procedural, training-based, access-based, publication-based, or assurance-based.
20.4.1(e) The controlling rule shall be that controls must be visible and testable before they can be relied upon.
20.4.2 Controls Mapped to Risks, Issues, Charter Parts, Policies, Procedures, Registers, Systems, Owners, and Review Cycles. 20.4.2(a) Controls shall be mapped to risks, issues, Charter Parts, Bylaw provisions, policies, procedures, registers, systems, repositories, rooms, data classes, AI systems, Public Authority interfaces, finance-sensitive interfaces, owners, custodians, and review cycles.
20.4.2(b) Control mapping shall show which controls mitigate which risks and which risks lack sufficient controls.
20.4.2(c) Control mapping shall identify preventive controls, detective controls, corrective controls, compensating controls, and assurance controls.
20.4.2(d) Where a control relies on another control, the dependency shall be recorded.
20.4.2(e) The controlling rule shall be that unmapped controls and uncontrolled risks both require governance attention.
20.4.3 Governance Controls. 20.4.3(a) Governance controls shall protect Board authority, fiduciary duty, officer delegation, committee mandates, council limits, conflicts, recusal, related-party transactions, decision records, legal separateness, and mission lock.
20.4.3(b) Governance controls may include Board-reserved matters, committee charters, delegation registers, decision packs, meeting minutes, conflict disclosures, recusal records, related-party review, independent review, governance training, Board evaluation, and governance assurance.
20.4.3(c) Governance controls shall prevent informal governance, no-record approvals, email governance, council overreach, officer overreach, sponsor control, provider control, founder control, and public authority confusion.
20.4.3(d) Governance controls shall be tested for operation, completeness, timeliness, and correction where defects occur.
20.4.3(e) The controlling rule shall be that governance controls preserve lawful authority before decisions are made.
20.4.4 Evidence and Methods Controls. 20.4.4(a) Evidence and methods controls shall protect source lineage, evidence integrity, methods integrity, ontology, controlled vocabulary, Observatory Methods, Truth Engine Methods, technical truth, benchmark discipline, and public-good technical baselines.
20.4.4(b) Controls may include evidence intake procedures, Case IDs, metadata standards, source-lineage records, method protocols, review gates, controlled vocabulary registers, versioning, change logs, reproducibility packages where lawful, limitation statements, and correction paths.
20.4.4(c) Evidence and methods controls shall prevent unsupported claims, stale evidence use, method drift, benchmark overclaim, AI hallucination, source fabrication, translation drift, and use beyond authority.
20.4.4(d) Controls shall be heightened where evidence or methods support public authority learning, finance-sensitive materials, public-safe publications, dashboards, maps, datasets, technical releases, or Nexus interfaces.
20.4.4(e) The controlling rule shall be that evidence and methods controls preserve the truth function of GCRI Canada.
20.4.5 Research and Publication Controls. 20.4.5(a) Research and publication controls shall protect research ethics, human-subjects protections, community safeguards, protected knowledge, peer review, reproducibility, publication accuracy, claims substantiation, public-safe release, and correctionability.
20.4.5(b) Controls may include research protocols, ethics review, community review, Indigenous and protected knowledge protocols, conflict disclosures, peer review, expert review, AI-use disclosure, publication classes, review gates, public-safe publication review, legal review where required, and correction notices.
20.4.5(c) Publication controls shall prevent defamation risk, misrepresentation, unsupported claims, public authority overclaim, finance overclaim, certification overclaim, provider preference, sponsor control implication, public warning confusion, sensitive-location exposure, and protected knowledge exposure.
20.4.5(d) Research and publication controls shall apply before release and after release through monitoring, correction, withdrawal, retraction, supersession, and archive.
20.4.5(e) The controlling rule shall be that research and publication controls must protect both accuracy and public-safe meaning.
20.4.6 Records and Correction Controls. 20.4.6(a) Records and correction controls shall protect validity-by-record, no-silent-effect discipline, authoritative repositories, official registers, Gazette notices where applicable, versioning, metadata, authority mapping, retention, legal hold, correctionability, supersession, withdrawal, retraction, and archive.
20.4.6(b) Controls may include Case ID requirements, minimum metadata standards, authority mapping, official registers, repository controls, versioning, change logs, no-silent-edit rules, correction processes, public-safe correction notices, controlled correction notices, retention schedules, access logs, and record assurance.
20.4.6(c) Records and correction controls shall prevent unrecorded decisions, stale public materials, unauthorized edits, unsupported claims, missing authority, uncontrolled documents, uncorrectable outputs, and public reliance beyond recorded authority.
20.4.6(d) Correction controls shall be triggered by factual error, method error, source error, data error, AI error, public authority misdescription, finance overclaim, provider overclaim, sponsor overclaim, protected knowledge issue, or public harm risk.
20.4.6(e) The controlling rule shall be that institutional meaning must remain record-valid and correctionable.
20.4.7 Data, AI, Cybersecurity, and Technical Asset Controls. 20.4.7(a) Data, AI, cybersecurity, and technical asset controls shall protect privacy, rights-bearing data, Public Authority Data, protected knowledge, AI governance, cybersecurity, repositories, software releases, technical baselines, compute environments, dashboards, maps, APIs, schemas, and public-good technical assets.
20.4.7(b) Controls may include data classification, lawful basis review, privacy notices, impact assessments, access controls, retention and deletion controls, AI use inventories, model registers, inference records, human review, vendor review, secure development, repository security, secrets management, vulnerability management, SBOMs, secure release, incident response, and business continuity.
20.4.7(c) Controls shall prevent unauthorized data access, unauthorized AI use, unauthorized training, unauthorized embedding, hallucination reliance, model drift, cybersecurity compromise, sensitive data leakage, insecure release, and technical asset enclosure.
20.4.7(d) Controls shall be heightened where Public Authority Data, personal information, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, finance-sensitive data, community-protected data, protected knowledge, or controlled technology is involved.
20.4.7(e) The controlling rule shall be that technical systems must be governed as legal, ethical, and public trust systems.
20.4.8 Public Authority Boundary Controls. 20.4.8(a) Public Authority boundary controls shall prevent GCRI Canada materials, activities, relationships, rooms, dashboards, maps, data contributions, public authority learning, or references from being understood as endorsement, adoption, regulation, procurement approval, funding approval, public finance approval, public warning, emergency command, official guidance, or sovereign obligation.
20.4.8(b) Controls may include capacity classification, reference approval, Public Authority Data agreements, non-endorsement language, no-public-warning language, no-command language, procurement-neutrality controls, public finance boundary language, public authority room controls, and correction processes.
20.4.8(c) Public Authority boundary controls shall apply before using Public Authority names, logos, titles, quotes, photographs, agency names, jurisdictions, attendance, or data contributions in public or controlled materials.
20.4.8(d) Controls shall be heightened for regulator-listening contexts, procurement-sensitive contexts, public finance reader contexts, emergency-management contexts, public health contexts, infrastructure contexts, and public warning-like materials.
20.4.8(e) The controlling rule shall be that Public Authority proximity requires boundary controls before public meaning forms.
20.4.9 Finance-Boundary, Fiscal, Sponsorship, Grant, and Anti-Inurement Controls. 20.4.9(a) Finance-boundary, fiscal, sponsorship, grant, and anti-inurement controls shall protect GCRI Canada from financial-services drift, finance-readiness overclaim, sponsor control, donor control, grantor control, provider preference, public authority access purchase, procurement advantage, private benefit, inurement, restricted fund breach, and fiscal instability.
20.4.9(b) Controls may include budgets, restricted fund registers, donation registers, sponsorship registers, grant registers, in-kind contribution registers, signing authority, procurement registers, related-party review, compensation review, finance-safe language, GRA routing, capital-reader room controls, public finance boundary language, and fiscal assurance.
20.4.9(c) Controls shall prevent outcome purchase, publication suppression, correction suppression, finance-readiness purchase, recognition purchase, certification purchase, procurement advantage, and support-for-control arrangements.
20.4.9(d) Controls shall be heightened where funds, in-kind assets, Public Authority interfaces, capital-reader rooms, GRA materials, Proof Pack inputs, public finance readers, or provider participation create market or authority meaning.
20.4.9(e) The controlling rule shall be that financial support must remain lawful support, not control or financial authority.
20.4.10 Community Safeguard and Protected Knowledge Controls. 20.4.10(a) Community safeguard and protected knowledge controls shall protect communities, Indigenous knowledge holders, local knowledge holders, territorial knowledge holders, cultural knowledge holders, environmental knowledge holders, vulnerable participants, protected persons, confidential sources, sensitive sites, and community-protected information.
20.4.10(b) Controls may include consent and non-consent handling where applicable, community review, Indigenous-governed review where appropriate, protected knowledge protocols, public-safe mapping review, access restrictions, aggregation, redaction, resolution reduction, grievance pathways, non-retaliation protections, and correction pathways.
20.4.10(c) Controls shall prevent extraction, misdescription, exposure, stigmatization, re-identification, unsafe mapping, protected knowledge publication, AI misuse, dataset misuse, dashboard misuse, and media amplification harm.
20.4.10(d) Controls shall be heightened for remote communities, vulnerable communities, protected persons, youth, sensitive locations, cultural sites, ecological sites, public health vulnerabilities, and public safety contexts.
20.4.10(e) The controlling rule shall be that community trust and protected knowledge must be safeguarded before evidence is collected, visualized, published, or reused.
20.4.11 Legal Compliance, Sanctions, Export-Control, Competition, and Professional-Boundary Controls. 20.4.11(a) Legal compliance, sanctions, export-control, competition, and professional-boundary controls shall protect GCRI Canada from legal noncompliance, tax-status drift, restricted-party exposure, controlled technology transfer, competition-law risk, procurement-law risk, unauthorized professional practice, and regulated-perimeter breach.
20.4.11(b) Controls may include legal review triggers, compliance calendars, sanctions screening, restricted-party registers, export-control registers, controlled technology review, competition do-not-discuss rules, procurement-neutrality controls, professional-boundary language, contract templates, policy reviews, and compliance assurance.
20.4.11(c) Controls shall prevent unauthorized legal advice, investment advice, insurance advice, engineering certification, medical advice, public health direction, emergency command, public warning, procurement advice, compliance certification, rating, underwriting, or other regulated professional services.
20.4.11(d) Controls shall be heightened for international collaboration, controlled technology, Public Authority interfaces, finance-sensitive materials, policy-facing activity, public claims, and high-risk jurisdictions.
20.4.11(e) The controlling rule shall be that legal boundary controls preserve lawful mission activity before risk becomes noncompliance.
20.4.12 Control Testing, Exceptions, Failures, Corrective Actions, and Assurance. 20.4.12(a) Controls shall be tested, reviewed, and assured according to risk.
20.4.12(b) Control testing shall identify whether controls are designed, implemented, operating, documented, effective, current, and linked to relevant risks.
20.4.12(c) Control exceptions shall be recorded, narrow, time-bound where appropriate, approved by proper authority, risk-reviewed, and not used to permit prohibited functions, legal noncompliance, data misuse, AI misuse, cybersecurity weakness, protected knowledge exposure, public authority overclaim, finance overclaim, sponsor control, provider preference, or private inurement.
20.4.12(d) Control failures shall require issue registration, root cause review, corrective action, owner assignment, verification, and assurance follow-up.
20.4.12(e) The controlling rule shall be that a control that cannot be tested, evidenced, or corrected is not a reliable control.
20.5 Risk Appetite, Risk Tolerance, and Prohibited Risk
20.5.1 Risk Appetite as Board-Approved Institutional Guidance Where Adopted. 20.5.1(a) Risk appetite, where adopted, shall be Board-approved institutional guidance identifying the type and level of risk GCRI Canada may accept in pursuit of its public-benefit mission.
20.5.1(b) Risk appetite shall be consistent with law, articles, Bylaw, Charter, mission lock, nonprofit character, non-execution, public-good stack role separation, privacy, cybersecurity, protected knowledge safeguards, public authority boundaries, finance boundaries, anti-inurement, legal separateness, and correctionability.
20.5.1(c) Risk appetite shall not authorize prohibited functions, unlawful conduct, private inurement, intentional misrepresentation, sponsor control, provider preference, public authority confusion, finance-regulated activity, protected knowledge misuse, sanctions breach, export-control breach, or deliberate data misuse.
20.5.1(d) Risk appetite shall be reviewed periodically and after material changes in law, technology, data, funding, Public Authority interfaces, finance-sensitive interfaces, international collaboration, incidents, or assurance findings.
20.5.1(e) The controlling rule shall be that risk appetite may guide mission-aligned judgment but shall not override constitutional boundaries.
20.5.2 Risk Tolerance by Domain, Activity, Data Class, Public Audience, Public Authority Interface, Technology Class, and Nexus Interface. 20.5.2(a) Risk tolerance may be defined by domain, activity, data class, public audience, Public Authority interface, finance-sensitive interface, technology class, publication class, room type, participant category, jurisdiction, and Nexus interface.
20.5.2(b) Data risk tolerance shall consider whether data is public, public-safe, internal, confidential, restricted, personal, health-sensitive, Public Authority Data, cyber-sensitive, infrastructure-sensitive, finance-sensitive, community-protected, Indigenous or protected knowledge, controlled technology, or export-control-sensitive.
20.5.2(c) Technology risk tolerance shall consider AI systems, model use, embedding, retrieval, agentic AI, cyber tools, AI-RAN, DePIN, blockchain / DLT, geospatial systems, satellite systems, drones, robotics, autonomous systems, quantum-relevant systems, high-performance compute, public-good software, APIs, schemas, dashboards, maps, and technical baselines.
20.5.2(d) Public audience risk tolerance shall be lower where public materials may affect communities, Public Authorities, capital readers, media, providers, sponsors, vulnerable persons, protected knowledge, public safety, or public trust.
20.5.2(e) The controlling rule shall be that tolerance must be specific enough to guide actual decisions, not merely broad enough to sound prudent.
20.5.3 Low Tolerance for Evidence Misrepresentation. 20.5.3(a) GCRI Canada shall maintain low tolerance for evidence misrepresentation.
20.5.3(b) Evidence misrepresentation includes unsupported claims, false source attribution, stale evidence use, selective omission, inflated confidence, suppressed uncertainty, fabricated evidence, AI hallucination, false citation, misleading visualization, benchmark misuse, method overclaim, impact inflation, or use of evidence beyond source authority.
20.5.3(c) Evidence misrepresentation shall require correction, reclassification, withdrawal, retraction, public-safe notice, controlled notice, method review, publication review, training, or disciplinary action as appropriate.
20.5.3(d) Evidence misrepresentation shall be treated as heightened where Public Authorities, capital readers, communities, media, providers, sponsors, or public audiences may rely on the output.
20.5.3(e) The controlling rule shall be that evidence integrity is not reputational preference; it is the foundation of GCRI Canada’s public-benefit mandate.
20.5.4 Low Tolerance for Public Authority Confusion. 20.5.4(a) GCRI Canada shall maintain low tolerance for Public Authority confusion.
20.5.4(b) Public Authority confusion includes any statement, conduct, room, report, dashboard, map, public authority learning material, data contribution, quote, logo use, attendance reference, or public claim implying endorsement, adoption, regulation, procurement approval, funding approval, public finance approval, public warning, emergency command, official guidance, or sovereign obligation without proper authority.
20.5.4(c) Public Authority confusion shall require capacity clarification, reference correction, public-safe notice, controlled notice, takedown, access restriction, room redesign, legal review, or training as appropriate.
20.5.4(d) Public Authority confusion shall be treated as heightened where emergency management, public health, public infrastructure, procurement, regulatory, public finance, or public warning contexts are involved.
20.5.4(e) The controlling rule shall be that public power must not be implied by proximity, attendance, or public language.
20.5.5 Low Tolerance for Finance Overclaim. 20.5.5(a) GCRI Canada shall maintain low tolerance for finance overclaim.
20.5.5(b) Finance overclaim includes any implication that GCRI Canada provides investment advice, securities solicitation, brokerage, finder activity, placement activity, lending approval, guarantee, insurance approval, underwriting, rating, public finance approval, grant approval, budget approval, MDB / DFI approval, sovereign finance approval, capital commitment, transaction recommendation, token issuance, custody, payment intermediation, or market operation.
20.5.5(c) Finance overclaim also includes describing a project, provider, host, National Company, Project SPV, technology, evidence pack, technical baseline, dashboard, map, or public authority initiative as finance-ready, bankable, investable, creditworthy, insurable, rated, guaranteed, or approved by GCRI Canada.
20.5.5(d) Finance overclaim shall require immediate hold, legal review, GRA routing where appropriate, corrected language, public-safe clarification, controlled notice, access restriction, room redesign, withdrawal, or retraction as appropriate.
20.5.5(e) The controlling rule shall be that finance meaning must not arise from technical evidence, audience, or aspiration.
20.5.6 Low Tolerance for Privacy, Cybersecurity, Protected Knowledge, and Community Harm. 20.5.6(a) GCRI Canada shall maintain low tolerance for privacy, cybersecurity, protected knowledge, and community harm.
20.5.6(b) Such harm includes unauthorized access, unauthorized disclosure, over-collection, re-identification, unsafe mapping, sensitive-location exposure, Public Authority Data misuse, health-sensitive data misuse, cyber-sensitive data exposure, infrastructure-sensitive data exposure, protected knowledge exposure, community misdescription, stigmatization, AI data leakage, or cybersecurity compromise.
20.5.6(c) Low tolerance shall require strong preventive controls, rapid containment, legal review where required, affected-person or community consideration, Public Authority consideration where applicable, breach assessment, public-safe communication, correction, remediation, and assurance follow-up.
20.5.6(d) Privacy, cybersecurity, protected knowledge, and community harm risk shall not be accepted for convenience, speed, publication value, sponsor preference, provider preference, or public visibility.
20.5.6(e) The controlling rule shall be that public-benefit work must not create preventable rights, security, or community harms.
20.5.7 Low Tolerance for Sponsor Control, Provider Preference, and Private Inurement. 20.5.7(a) GCRI Canada shall maintain low tolerance for sponsor control, provider preference, donor control, funder control, host control, private inurement, improper private benefit, related-party abuse, pay-to-play, outcome purchase, and access purchase.
20.5.7(b) Sponsor control includes influence over governance, evidence, methods, publications, corrections, public authority access, technical baselines, public claims, or institutional priorities beyond recorded, lawful, mission-compatible terms.
20.5.7(c) Provider preference includes use of GCRI Canada participation, testing, benchmarking, demonstration, technical review, room access, public authority proximity, or public claims to imply preferred status, procurement advantage, certification, recognition, finance-readiness, or public authority approval.
20.5.7(d) Private inurement and improper private benefit shall require correction, return, repayment, repricing, rescission, access restriction, public claims correction, legal review, tax review, Board reporting, discipline, or termination where appropriate.
20.5.7(e) The controlling rule shall be that support and participation shall never purchase institutional truth, public authority proximity, market advantage, or private entitlement.
20.5.8 Zero or Near-Zero Tolerance for Prohibited Functions, Fraud, Retaliation, Bribery, Sanctions Breach, Export-Control Breach, Intentional Data Misuse, and Deliberate Public Misrepresentation. 20.5.8(a) GCRI Canada shall maintain zero or near-zero tolerance for prohibited functions, fraud, theft, bribery, corruption, retaliation, harassment, discrimination, sanctions breach, export-control breach, intentional data misuse, intentional AI misuse, deliberate cybersecurity misconduct, deliberate public misrepresentation, intentional protected knowledge misuse, and knowing public authority or finance overclaim.
20.5.8(b) Prohibited functions include public authority substitution, public warning issuance, emergency command, procurement authority, public finance approval, investment advice, securities solicitation, brokerage, lending, insurance placement, underwriting, rating, guarantee, certification by default, provider preference, sponsor control, and execution activity outside GCRI Canada’s lawful mandate.
20.5.8(c) Such risks shall not be accepted, normalized, waived, or treated as ordinary operational risk.
20.5.8(d) Response may include immediate hold, access suspension, investigation, legal review, notification where required, correction, withdrawal, retraction, termination, Board reporting, law enforcement or regulator interaction where appropriate, and assurance follow-up.
20.5.8(e) The controlling rule shall be that prohibited-risk conduct is not risk appetite; it is breach response.
20.5.9 Risk Acceptance Must Be Recorded, Time-Bound, Owned, Reviewed, and Escalated Where Material. 20.5.9(a) Risk acceptance shall be recorded, time-bound where appropriate, owned, reviewed, and escalated where material.
20.5.9(b) A risk acceptance record shall identify the risk, owner, authority, rationale, alternatives considered, controls in place, residual risk, duration, review date, conditions, monitoring, escalation triggers, affected records, affected persons or communities, affected Public Authorities, affected public materials, and Board or committee visibility where required.
20.5.9(c) Risk acceptance shall not be implied from inaction, silence, email, chat, informal meeting notes, repeated practice, sponsor pressure, provider pressure, funding pressure, public authority interest, or operational convenience.
20.5.9(d) Accepted risks shall be periodically reviewed and may be revoked, narrowed, escalated, corrected, or refused where conditions change.
20.5.9(e) The controlling rule shall be that accepted risk must be consciously authorized and continuously reviewable.
20.5.10 Prohibited Risk Cannot Be Accepted by Informal Approval or Operational Convenience. 20.5.10(a) Prohibited risk cannot be accepted by informal approval, operational convenience, funding need, sponsor preference, provider preference, grant deadline, public authority proximity, capital-reader interest, media opportunity, technical enthusiasm, founder preference, or repeated practice.
20.5.10(b) No Officer, Director, committee, council, Working Group, fellow, advisor, staff member, contractor, sponsor, provider, host, Public Authority participant, donor, funder, capital reader, National Company, Project SPV, or Nexus actor may authorize prohibited risk unless the Charter, law, and proper authority permit the activity; where the activity remains prohibited, it shall be refused.
20.5.10(c) Any attempted acceptance of prohibited risk shall be treated as an issue, incident, governance breach, compliance breach, or legal matter as appropriate.
20.5.10(d) Corrective action may include reversal, hold, correction, public-safe clarification, controlled notice, access restriction, legal review, Board reporting, training, discipline, termination, or relationship remedy.
20.5.10(e) The controlling rule shall be that no convenience, urgency, funding, or public-good aspiration can convert prohibited risk into permissible risk.
20.6 Stop-the-Line Authority
20.6.1 Stop-the-Line as Immediate Protective Authority. 20.6.1(a) Stop-the-Line Authority means the immediate protective authority to pause, hold, quarantine, restrict, suspend, freeze, escalate, or otherwise interrupt an activity, release, publication, communication, room, data flow, technical process, AI use, public claim, or institutional interface where a material risk to GCRI Canada’s mission, lawful authority, public-benefit character, public trust, non-execution, public authority boundary, finance boundary, data rights, cybersecurity, protected knowledge, community safeguards, evidence integrity, methods integrity, or legal separateness is reasonably identified.
20.6.1(b) Stop-the-Line Authority shall be protective, provisional, records-valid, non-retaliatory, and risk-based. It shall not be treated as a disciplinary finding, final decision, admission of liability, public position, or evidence that the underlying concern is confirmed.
20.6.1(c) Stop-the-Line Authority may be invoked before full investigation where delay could create public harm, legal exposure, privacy breach, cybersecurity exposure, Public Authority confusion, finance overclaim, protected knowledge exposure, reliance on unsupported materials, publication error, technical release error, or irreversible dissemination.
20.6.1(d) Stop-the-Line Authority shall preserve institutional truth, safety, lawful authority, public-safe publication, correctionability, and records integrity pending review.
20.6.1(e) The controlling rule shall be that where material harm or boundary failure may continue through action, publication, access, release, or silence, GCRI Canada shall have authority to pause first and review promptly.
20.6.2 Stop-the-Line May Be Invoked for Public Safety Risk, Public Authority Confusion, Public Warning Confusion, Finance Boundary Risk, Data Misuse, AI Misuse, Cybersecurity Risk, Protected Knowledge Risk, Community Harm Risk, Legal Noncompliance, Sponsor Control, Provider Preference, Publication Error, Technical Release Error, or Uncontrolled Public Claim. 20.6.2(a) Stop-the-Line Authority may be invoked where there is a reasonable concern involving public safety risk, Public Authority confusion, public warning confusion, emergency command confusion, finance-boundary risk, regulated financial-perimeter risk, data misuse, privacy risk, AI misuse, cybersecurity risk, protected knowledge risk, community harm risk, legal noncompliance, sanctions risk, export-control risk, competition risk, professional-boundary risk, sponsor control, donor control, funder control, provider preference, procurement overclaim, private inurement, publication error, technical release error, uncontrolled public claim, unsupported evidence, method error, dashboard error, map error, dataset release risk, or public-safe communication failure.
20.6.2(b) Stop-the-Line Authority may apply to Board or officer action pending proper authority, committee or council action pending mandate review, publication pending review, data access pending classification, AI use pending authorization, repository release pending security review, room participation pending boundary review, public authority reference pending approval, finance-sensitive material pending GRA or legal review, or sponsor / provider materials pending public claims review.
20.6.2(c) Stop-the-Line Authority may be invoked where the risk is observed directly, reported by a participant, identified through monitoring, detected by assurance, raised by a Public Authority, raised by a community or protected knowledge holder, identified by legal review, identified by technical review, or inferred from credible evidence.
20.6.2(d) Stop-the-Line Authority shall not require proof of final harm. A reasonable, good-faith, records-supported concern shall be sufficient to trigger provisional protection.
20.6.2(e) The controlling rule shall be that Stop-the-Line exists to prevent preventable harm before final certainty is available.
20.6.3 Authorized Stop-the-Line Persons and Escalation Channels. 20.6.3(a) Stop-the-Line Authority may be invoked by any Director, Officer, designated risk owner, legal or compliance lead, cybersecurity lead, data protection lead, research lead, publication lead, Public Authority interface lead, finance-boundary lead, protected knowledge or safeguards lead, room owner, repository owner, technical release owner, committee chair, or other person expressly authorized by policy, delegation, or emergency procedure.
20.6.3(b) Any employee, contractor, volunteer, fellow, advisor, contributor, Working Group participant, council participant, sponsor, provider, host, Public Authority participant, community participant, university participant, capital reader, or other participant may request Stop-the-Line review through the designated reporting channel where they identify a reasonable concern.
20.6.3(c) Policies may distinguish persons who may impose an immediate hold from persons who may request a hold, but shall ensure that urgent concerns can be raised without delay, intimidation, retaliation, or procedural obstruction.
20.6.3(d) Escalation channels shall identify primary and alternate contacts, emergency contacts, after-hours procedures where applicable, secure reporting pathways, anonymous or confidential reporting options where appropriate, and routing rules for legal, data, AI, cybersecurity, Public Authority, finance, community, protected knowledge, publication, and technical release concerns.
20.6.3(e) The controlling rule shall be that Stop-the-Line authority must be clear enough to be used when needed and broad enough to protect against silence.
20.6.4 Stop-the-Line Without Retaliation. 20.6.4(a) Good-faith invocation or request for Stop-the-Line review shall be protected from retaliation.
20.6.4(b) Retaliation includes dismissal, removal, demotion, contract termination, access denial, exclusion, harassment, intimidation, adverse assignment, reputational attack, funding penalty, publication penalty, authorship penalty, public claims retaliation, sponsor pressure, provider pressure, community pressure, or other adverse treatment because a person raised or supported a Stop-the-Line concern in good faith.
20.6.4(c) A person invoking Stop-the-Line in good faith shall not be required to prove that the concern is ultimately substantiated, provided the concern was reasonable, honestly held, and raised through appropriate channels or under circumstances requiring urgent protective action.
20.6.4(d) Retaliation or attempted retaliation for good-faith Stop-the-Line use shall be treated as a governance incident, conduct incident, participation incident, workforce incident, or contractual breach as appropriate.
20.6.4(e) The controlling rule shall be that GCRI Canada shall protect the person who pauses risk before protecting the convenience of the process that created risk.
20.6.5 Stop-the-Line Effect: Hold, Pause, Quarantine, Access Restriction, Publication Suspension, Release Freeze, Room Suspension, Data Transfer Hold, AI Use Hold, or Public Claims Hold. 20.6.5(a) Stop-the-Line effect may include hold, pause, quarantine, access restriction, publication suspension, technical release freeze, repository freeze, branch protection escalation, room suspension, clean-room hold, data-room hold, data transfer hold, AI-use hold, model restriction, retrieval restriction, embedding restriction, dashboard suspension, map suspension, dataset release hold, API freeze, schema release hold, public claims hold, media hold, Public Authority reference hold, finance-sensitive material hold, sponsor acknowledgment hold, provider reference hold, or procurement-sensitive communication hold.
20.6.5(b) The scope of the hold shall be proportionate to the risk and may apply to a single record, dataset, model, publication, interface, room, participant, system, repository, public statement, release, contract, activity, program, or relationship, or to a broader class of activity where the risk cannot be safely isolated.
20.6.5(c) Stop-the-Line action shall preserve records, evidence, metadata, logs, communications, versions, access records, and relevant materials pending triage and review.
20.6.5(d) Stop-the-Line action shall not be used to destroy records, suppress lawful complaints, conceal incidents, avoid correction, prevent legal notice, block affected-person rights, or retaliate against participants.
20.6.5(e) The controlling rule shall be that Stop-the-Line shall stop the risk pathway, preserve the evidence, and enable proper review.
20.6.6 Stop-the-Line Triage and Review. 20.6.6(a) A Stop-the-Line action shall be triaged promptly according to severity, affected domain, affected records, affected persons, affected communities, affected Public Authorities, affected data, affected systems, affected public materials, legal exposure, cybersecurity exposure, Public Authority consequence, finance consequence, protected knowledge consequence, public trust consequence, and need for immediate containment.
20.6.6(b) Triage shall determine whether the matter is an issue, incident, legal matter, privacy matter, AI matter, cybersecurity matter, publication matter, Public Authority matter, finance-boundary matter, protected knowledge matter, workforce matter, contract matter, grant matter, or governance matter.
20.6.6(c) Review shall identify the reason for the stop, authority invoked, materials affected, persons affected, interim controls, evidence to be preserved, reviewers required, escalation required, legal review required, Public Authority consultation required, community consultation required, and decision timeline.
20.6.6(d) Where the Stop-the-Line concerns urgent cybersecurity, privacy, data breach, public safety, legal notice, or protected knowledge exposure, containment shall proceed immediately while review continues.
20.6.6(e) The controlling rule shall be that Stop-the-Line must be triaged fast enough to prevent harm and reviewed carefully enough to preserve fairness and accuracy.
20.6.7 Stop-the-Line Decision, Continuation, Release, Correction, or Escalation. 20.6.7(a) Following triage and review, the Stop-the-Line action shall result in a decision to continue the hold, narrow the hold, release the hold, correct the affected matter, reclassify the matter, withdraw the matter, retract the matter, suspend the matter, escalate the matter, or convert the matter into an incident, issue, legal hold, investigation, or Board / committee matter.
20.6.7(b) A hold may be released only where the responsible authority determines, with appropriate records, that the risk has been resolved, controlled, accepted where permitted, corrected, or determined not to require continued restriction.
20.6.7(c) A hold shall continue where facts remain uncertain and continued activity could create material harm, reliance, legal exposure, data exposure, cybersecurity exposure, protected knowledge exposure, public authority confusion, finance overclaim, or public trust harm.
20.6.7(d) Correction may include revised record, revised publication, revised boundary language, public-safe notice, controlled notice, data deletion, access restriction, AI restriction, technical patch, release re-issue, room redesign, participant correction, sponsor correction, provider correction, Public Authority clarification, GRA routing, legal review, or Board action.
20.6.7(e) The controlling rule shall be that Stop-the-Line shall end only through recorded resolution, not through fatigue, pressure, or informal reassurance.
20.6.8 Stop-the-Line Records, Owner, Time, Scope, Reason, Affected Materials, and Closeout. 20.6.8(a) Each Stop-the-Line action shall be recorded.
20.6.8(b) The record shall identify requester, invoking person where different, date and time, authority, reason, affected activity, affected records, affected systems, affected data, affected persons, affected communities, affected Public Authorities, affected publications, affected rooms, affected repositories, affected public claims, affected contracts, affected sponsors or providers, scope, interim controls, owner, custodian, triage outcome, review outcome, decision, corrective action, escalation, and closeout.
20.6.8(c) Stop-the-Line records shall be classified, access-controlled, and linked to the Issue Register, Incident Register, Risk Register, Control Register, Publication Register, Data Register, AI Register, Cybersecurity Register, Public Authority Register, Finance Boundary Register, Legal Review Register, or other applicable register.
20.6.8(d) Closeout shall record final decision, evidence reviewed, corrective actions completed, notices issued, remaining risk, assurance follow-up, and lessons learned.
20.6.8(e) The controlling rule shall be that protective interruption must itself be record-valid and correctionable.
20.6.9 Abuse or Bad-Faith Use of Stop-the-Line. 20.6.9(a) Stop-the-Line shall not be abused or invoked in bad faith.
20.6.9(b) Abuse may include use of Stop-the-Line to retaliate, suppress lawful dissent, delay correction, conceal misconduct, gain commercial advantage, block publication for sponsor or provider convenience, prevent lawful Public Authority notice, obstruct investigation, harass a participant, manipulate procurement, influence finance-sensitive materials, or create strategic disruption without reasonable basis.
20.6.9(c) A finding that the underlying concern was not substantiated shall not by itself constitute abuse or bad faith.
20.6.9(d) Bad-faith use shall be reviewed according to conduct, workforce, participant, governance, contract, or legal procedures and may result in training, warning, access restriction, removal, discipline, contract remedy, termination, or legal action.
20.6.9(e) The controlling rule shall be that Stop-the-Line must protect good-faith caution while preventing weaponized obstruction.
20.6.10 Stop-the-Line Assurance and Training. 20.6.10(a) GCRI Canada shall maintain Stop-the-Line Assurance and training.
20.6.10(b) Training shall explain who may invoke Stop-the-Line, how concerns are raised, when immediate holds are appropriate, what non-retaliation means, how records are created, how triage occurs, how legal review is triggered, how holds are released, and how abuse is handled.
20.6.10(c) Assurance shall review Stop-the-Line records, timeliness, classification, interim controls, escalation, outcomes, retaliation concerns, repeated patterns, unresolved holds, improper releases, misuse, and training effectiveness.
20.6.10(d) Assurance findings may require policy updates, role clarification, reporting channel improvement, training refresh, access control changes, incident process updates, Board reporting, or corrective action.
20.6.10(e) The controlling rule shall be that Stop-the-Line authority must be trained and assured because protective authority fails if people fear using it or misuse it.
20.7 Incident Escalation
20.7.1 Incident Escalation as Mandatory for Material Boundary, Legal, Technical, Public-Safe, Data, AI, Cyber, Finance, Public Authority, Community, or Governance Incidents. 20.7.1(a) Incident escalation shall be mandatory for material boundary, legal, technical, public-safe, records, data, AI, cybersecurity, finance, Public Authority, community, protected knowledge, governance, research, publication, workforce, contract, grant, sponsorship, provider, host, participant, or Nexus-interface incidents.
20.7.1(b) Escalation shall ensure that incidents are reviewed by persons with proper authority, expertise, independence, legal awareness, technical competence, and institutional accountability.
20.7.1(c) Incident escalation shall not be delayed because the incident is reputationally sensitive, sponsor-sensitive, provider-sensitive, Public Authority-sensitive, finance-sensitive, media-sensitive, politically sensitive, cross-border, technically complex, or inconvenient.
20.7.1(d) Incident escalation shall preserve records, evidence, privilege where applicable, confidentiality, public-safe communication, non-retaliation, and correctionability.
20.7.1(e) The controlling rule shall be that material incidents move upward, across, or outward as required by risk, law, duty, and public trust.
20.7.2 Escalation to Officer. 20.7.2(a) Incidents shall be escalated to the appropriate Officer where they affect operations, programs, contracts, data, AI, cybersecurity, publications, public authority interfaces, finance boundaries, workforce, participants, sponsors, providers, hosts, research, technical releases, or public claims within that Officer’s delegated responsibility.
20.7.2(b) Officer escalation shall identify incident type, severity, affected materials, interim controls, legal review need, required notifications, correction pathway, and Board or committee reporting threshold.
20.7.2(c) Officers shall ensure immediate containment, assignment of incident owner, preservation of records, coordination with relevant leads, and timely reporting to higher authority where required.
20.7.2(d) An Officer with a conflict, implicated role, insufficient authority, or insufficient independence shall not be the sole decision-maker for escalation disposition.
20.7.2(e) The controlling rule shall be that operational incidents must reach an accountable Officer before they become unmanaged institutional exposure.
20.7.3 Escalation to Committee. 20.7.3(a) Incidents shall be escalated to an authorized committee where the incident falls within the committee’s mandate, requires multi-domain review, involves control failure, affects assurance, requires policy update, or exceeds ordinary officer authority.
20.7.3(b) Committees may include governance, finance, audit, internal controls, risk, legal compliance, data, AI, cybersecurity, research integrity, publication, safeguards, or other Board-approved committees.
20.7.3(c) Committee escalation shall be records-valid and shall include incident summary, severity, affected domains, immediate actions, legal review status, public-safe status, corrective action plan, unresolved decisions, and requested committee action.
20.7.3(d) Committees may recommend, monitor, review, or act within delegated authority, but shall not exceed Board-reserved matters or assume Public Authority, finance, certification, procurement, protocol, or execution authority.
20.7.3(e) The controlling rule shall be that committees support incident governance without becoming substitute authorities beyond their mandate.
20.7.4 Escalation to Board. 20.7.4(a) Incidents shall be escalated to the Board where they are high severity, critical, systemic, legally material, financially material, public-trust material, mission-lock material, governance-material, or Board-reserved.
20.7.4(b) Board escalation shall be required or appropriate for incidents involving prohibited functions, public authority confusion at material scale, finance-regulated-perimeter breach, major privacy breach, major cybersecurity incident, major protected knowledge exposure, sanctions or export-control risk, private inurement, fraud, bribery, retaliation, major public claims failure, material legal separateness breach, major litigation risk, or repeated control failure.
20.7.4(c) Board materials shall preserve legal privilege, confidentiality, public-safe status, privacy, cybersecurity, Public Authority sensitivity, finance sensitivity, employment sensitivity, and protected knowledge safeguards.
20.7.4(d) Board action may include direction, ratification where lawful, correction, withdrawal, reporting, policy amendment, investigation, independent review, resource allocation, relationship restriction, officer action, or strategic redesign.
20.7.4(e) The controlling rule shall be that the Board must see incidents that threaten mission, law, trust, or constitutional boundaries.
20.7.5 Escalation to Legal Counsel Where Required. 20.7.5(a) Incidents shall be escalated to legal counsel where legal review is required by law, contract, policy, legal review trigger, privilege need, regulatory risk, Public Authority risk, finance-regulated-perimeter risk, data breach, cybersecurity incident, sanctions risk, export-control risk, employment risk, IP risk, tax risk, contract risk, litigation risk, or professional-boundary risk.
20.7.5(b) Legal escalation shall occur before admissions of liability, settlement offers, external legal notices, regulatory responses, Public Authority responses, destruction of records, waiver of privilege, material public statements, or legally sensitive corrective actions, unless urgent containment is required and legal review follows promptly.
20.7.5(c) Legal counsel may advise on preservation, privilege, notification duties, breach duties, public-safe communications, contractual notices, insurance notice, regulatory interaction, employment action, dispute strategy, and correction obligations.
20.7.5(d) Legal escalation shall not be used to suppress lawful correction, conceal public harm, avoid affected-person notice, or prevent proper Board reporting.
20.7.5(e) The controlling rule shall be that legal review must protect lawful action and correction, not replace institutional accountability.
20.7.6 Escalation to Public Authority Where Required or Appropriate. 20.7.6(a) Incidents shall be escalated to a Public Authority where required by law, contract, public authority agreement, public authority data terms, breach notification rules, emergency conditions, public safety considerations, grant conditions, court order, regulatory obligation, or other competent authority requirement.
20.7.6(b) Escalation to Public Authority may also be appropriate where Public Authority Data is affected, a Public Authority reference is misused, public warning confusion exists, emergency command confusion exists, public infrastructure risk exists, public health risk exists, regulatory misdescription exists, public finance misdescription exists, or public reliance may affect public decision-making.
20.7.6(c) Public Authority escalation shall be authorized, accurate, timely, privilege-protective, confidentiality-protective, privacy-protective, cybersecurity-protective, public-safe, and records-valid.
20.7.6(d) GCRI Canada shall not use escalation to Public Authority to imply endorsement, adoption, regulatory approval, procurement approval, public finance approval, public warning, emergency command, or sovereign obligation.
20.7.6(e) The controlling rule shall be that Public Authority escalation shall occur where duty or public safety requires, while preserving GCRI Canada’s non-public-authority role.
20.7.7 Escalation to Affected Community, Participant, Partner, Provider, Sponsor, Host, University, GRF, GRA, Protocol Authority, Nexus Entity, National Company, or Project SPV Where Required or Appropriate. 20.7.7(a) Incidents shall be escalated to affected communities, participants, partners, providers, sponsors, hosts, universities, GRF, GRA, Protocol Authority, Nexus entities, National Companies, Project SPVs, or other affected actors where required by law, contract, safeguard protocol, data agreement, public authority term, room rule, grant term, sponsorship term, correction duty, or public trust duty.
20.7.7(b) Escalation may be appropriate where the incident affects shared records, shared data, shared publications, shared technical assets, public claims, Public Authority references, finance-sensitive materials, technical baselines, protected knowledge, community safeguards, participant rights, provider references, sponsor acknowledgments, or downstream dependencies.
20.7.7(c) Escalation shall identify affected scope, known facts, interim controls, required actions, confidentiality limits, public-safe constraints, correction pathway, and response expectations.
20.7.7(d) Escalation shall not transfer liability, authority, control, public authority meaning, finance authority, recognition authority, certification authority, protocol authority, procurement authority, or execution authority unless separate lawful records provide otherwise.
20.7.7(e) The controlling rule shall be that affected actors should be notified where required or appropriate, but notification shall not collapse roles.
20.7.8 Escalation Thresholds by Severity, Data Class, Public Harm, Public Authority Risk, Finance Risk, Cyber Risk, Protected Knowledge Risk, and Public Trust Risk. 20.7.8(a) Escalation thresholds shall be defined by severity, data class, public harm, Public Authority risk, finance risk, cybersecurity risk, protected knowledge risk, community risk, legal risk, records risk, publication risk, operational risk, and public trust risk.
20.7.8(b) High or critical severity incidents shall require escalation to Officers and, where appropriate, committees, legal counsel, Board, Public Authorities, affected communities, or affected actors.
20.7.8(c) Incidents involving restricted data, Public Authority Data, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, finance-sensitive data, community-protected data, protected knowledge, controlled technology, or personal information breach shall receive heightened escalation.
20.7.8(d) Incidents involving public authority confusion, public warning confusion, emergency command confusion, finance overclaim, public finance overclaim, certification overclaim, provider preference, sponsor control, procurement implication, or public reliance shall be escalated where material.
20.7.8(e) The controlling rule shall be that escalation thresholds must reflect harm, authority, sensitivity, and reliance, not organizational hierarchy alone.
20.7.9 Escalation Timing, Records, Notices, and Acknowledgments. 20.7.9(a) Escalation timing shall be proportionate to severity, legal deadlines, public harm risk, data exposure, cybersecurity exposure, public authority consequence, finance consequence, protected knowledge consequence, and public trust risk.
20.7.9(b) Critical incidents shall be escalated immediately or as soon as reasonably practicable. High severity incidents shall be escalated promptly. Moderate and low severity incidents shall be escalated according to policy, unless facts change.
20.7.9(c) Escalation records shall identify incident, severity, escalation recipient, time, method, content, attachments, confidentiality class, privilege status, required action, acknowledgment, follow-up, and closeout.
20.7.9(d) Required notices shall be tracked to completion and shall include confirmation where available.
20.7.9(e) The controlling rule shall be that escalation is incomplete until the right recipient has received and acknowledged the right information or a lawful alternative record exists.
20.7.10 Escalation Failure as Governance Incident. 20.7.10(a) Escalation failure shall be treated as a governance incident, compliance incident, records incident, workforce incident, participation incident, cybersecurity incident, privacy incident, or other incident as appropriate.
20.7.10(b) Escalation failure includes failure to report, late reporting, misclassification to avoid escalation, suppression of incident information, retaliation against reporter, failure to notify required persons, failure to preserve records, failure to involve legal counsel where required, or failure to inform the Board where Board reporting is required.
20.7.10(c) Escalation failure shall require root cause review, corrective action, training, access restriction, disciplinary action, contract remedy, policy update, Board reporting, or legal review where appropriate.
20.7.10(d) Escalation failure shall not be cured merely by later discovery where harm, reliance, legal exposure, or public trust consequence occurred.
20.7.10(e) The controlling rule shall be that failure to escalate a material incident is itself a material risk event.
20.8 Incident Management Integration
20.8.1 Incident Management Integrated Across Governance, Records, Research, Publication, Data, AI, Cybersecurity, Public Authority, Finance, Safeguards, Legal, and Participation Domains. 20.8.1(a) Incident management shall be integrated across governance, records, research, publication, data, AI, cybersecurity, Public Authority, finance, safeguards, legal, workforce, participation, fiscal, contract, grant, sponsorship, provider, host, community, protected knowledge, technical asset, and Nexus-interface domains.
20.8.1(b) Integration shall ensure that incidents are not fragmented, under-classified, double-counted without coordination, or closed in one domain while unresolved in another.
20.8.1(c) A single incident may require simultaneous treatment under privacy, cybersecurity, records, legal compliance, public claims, Public Authority boundary, finance-boundary, community safeguards, contract, and governance procedures.
20.8.1(d) Incident integration shall preserve domain-specific obligations, including legal privilege, breach notification, Public Authority notice, community consultation, protected knowledge safeguards, finance-safe language, public-safe notices, and Board reporting.
20.8.1(e) The controlling rule shall be that incidents shall be managed according to their full institutional meaning, not the first label assigned.
20.8.2 Common Incident Intake. 20.8.2(a) GCRI Canada shall maintain common incident intake procedures or interoperable intake pathways for material incidents.
20.8.2(b) Common intake shall capture reporter, date, source, incident description, affected domain, suspected severity, affected persons, affected communities, affected Public Authorities, affected data, affected systems, affected records, affected public materials, affected contracts, affected sponsors or providers, immediate containment needs, and legal review needs.
20.8.2(c) Intake shall allow incidents to be reported by Directors, Officers, staff, contractors, fellows, advisors, contributors, participants, Public Authorities, communities, providers, sponsors, hosts, universities, capital readers, and other affected actors.
20.8.2(d) Intake shall protect good-faith reporters from retaliation and shall include confidential reporting where appropriate.
20.8.2(e) The controlling rule shall be that common intake exists to make institutional risk visible before procedural routing narrows the issue.
20.8.3 Common Severity Classification. 20.8.3(a) GCRI Canada shall maintain common severity classification or interoperable severity criteria for incidents.
20.8.3(b) Severity classification shall consider legal consequence, public-benefit consequence, public trust consequence, public safety, data sensitivity, AI impact, cybersecurity impact, Public Authority implication, finance implication, protected knowledge implication, community harm, operational disruption, recurrence, and downstream reliance.
20.8.3(c) Severity classification shall be updated as facts change and shall not be held artificially low to avoid escalation, notice, correction, public-safe clarification, legal review, or Board reporting.
20.8.3(d) Severity classification shall identify whether immediate Stop-the-Line, legal hold, breach review, public-safe notice, controlled notice, or external notification is required.
20.8.3(e) The controlling rule shall be that severity follows potential consequence, not institutional embarrassment.
20.8.4 Common Triage Discipline. 20.8.4(a) GCRI Canada shall maintain common triage discipline for incidents.
20.8.4(b) Triage shall identify incident type, severity, owner, custodian, required reviewers, affected domains, containment actions, preservation needs, legal review needs, notification needs, correction needs, public-safe status, and escalation path.
20.8.4(c) Triage shall distinguish immediate containment from final determination and shall not require full fact-finding before protective controls are applied.
20.8.4(d) Triage shall include conflict review where the incident involves a person, sponsor, provider, host, Public Authority, donor, funder, officer, Director, or participant who may influence handling.
20.8.4(e) The controlling rule shall be that triage must route the incident to the right authority before informal handling becomes additional risk.
20.8.5 Common Containment and Preservation Discipline. 20.8.5(a) GCRI Canada shall maintain common containment and preservation discipline for incidents.
20.8.5(b) Containment may include access suspension, credential revocation, key rotation, data quarantine, publication hold, dashboard suspension, map suspension, AI-use restriction, model restriction, repository freeze, room suspension, contract hold, public claims hold, public authority reference hold, finance-sensitive material hold, or transfer block.
20.8.5(c) Preservation shall include relevant records, metadata, logs, versions, communications, repository history, prompt records, inference records, access logs, publication versions, data lineage, contract records, Public Authority records, room records, and correction records.
20.8.5(d) Containment and preservation shall be coordinated with legal hold, privilege, privacy, cybersecurity, Public Authority sensitivity, protected knowledge, employment, contract, and public-safe communication obligations.
20.8.5(e) The controlling rule shall be that incident response must stop the harm pathway and preserve the truth pathway.
20.8.6 Common Correction and Remediation Discipline. 20.8.6(a) GCRI Canada shall maintain common correction and remediation discipline for incidents.
20.8.6(b) Correction may include clarification, erratum, correction, reclassification, downgrade, upgrade, suspension, supersession, withdrawal, retraction, retirement, reinstatement, archive, sealing, deletion where lawful and required, public-safe notice, or controlled notice.
20.8.6(c) Remediation may include policy update, training update, access change, contract amendment, control redesign, technical patch, data deletion, AI restriction, vendor remedy, sponsor correction, provider correction, Public Authority clarification, community remedy, legal filing, or Board action.
20.8.6(d) Correction and remediation shall identify downstream dependencies, affected records, affected public materials, affected systems, affected actors, and verification steps.
20.8.6(e) The controlling rule shall be that incident closure requires corrected truth, corrected controls, and corrected reliance.
20.8.7 Common Public-Safe and Controlled Notice Discipline. 20.8.7(a) GCRI Canada shall maintain common public-safe and controlled notice discipline for incidents.
20.8.7(b) Public-safe notices shall be used where public materials, public reliance, public claims, public dashboards, public maps, public reports, public datasets, media statements, or public-safe outputs require correction without over-disclosing sensitive information.
20.8.7(c) Controlled notices shall be used where affected recipients require notice but materials involve confidential, personal, Public Authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, community-protected, protected knowledge, legal, employment, or security-sensitive information.
20.8.7(d) Notices shall identify scope, affected materials, correction state, effective date, replacement status, boundary language where relevant, and contact or challenge path where appropriate.
20.8.7(e) The controlling rule shall be that notice must prevent misunderstanding while avoiding additional harm.
20.8.8 Common Post-Incident Review and Learning Loop. 20.8.8(a) GCRI Canada shall conduct post-incident review and maintain a learning loop for material incidents.
20.8.8(b) Post-incident review shall identify facts, root cause, contributing factors, control failures, detection gaps, escalation performance, legal review performance, communication performance, correction performance, affected records, affected actors, unresolved risk, and recurrence prevention.
20.8.8(c) Lessons learned shall be translated into corrective action plans, policy updates, training updates, control updates, register updates, technical updates, contract updates, public claims updates, and assurance changes.
20.8.8(d) Post-incident review shall be proportionate and shall protect legal privilege, confidentiality, privacy, cybersecurity, Public Authority sensitivity, protected knowledge, and non-retaliation.
20.8.8(e) The controlling rule shall be that an incident is not fully resolved until the institution has learned from it.
20.8.9 Common Incident Register Cross-Reference. 20.8.9(a) Incident registers shall be cross-referenced to ensure complete institutional memory.
20.8.9(b) A material incident shall be linked, where applicable, to the Risk Register, Issue Register, Control Register, Records Incident Register, Correction Register, Publication Register, Data Breach Register, Privacy Register, AI Incident Register, Cybersecurity Incident Register, Public Authority Boundary Register, Finance Legal Boundary Register, Community Safeguards Register, Legal Review Register, Contract Register, Grant Register, Sponsorship Register, Workforce Register, and Board or committee records.
20.8.9(c) Cross-referencing shall identify primary register, secondary registers, owners, custodians, severity, status, corrective actions, notices, and closeout evidence.
20.8.9(d) Cross-referencing shall not expand access beyond lawful classification or privilege limits.
20.8.9(e) The controlling rule shall be that incident records must connect across domains without collapsing confidentiality or custody.
20.8.10 No Incident Shall Be Hidden, Reclassified, or Informally Resolved to Avoid Correction, Reporting, or Accountability. 20.8.10(a) No incident shall be hidden, minimized, misclassified, delayed, fragmented, informally resolved, silently edited, privately settled, or closed to avoid correction, reporting, notice, legal review, Board visibility, Public Authority escalation, affected-person notice, community remedy, sponsor accountability, provider accountability, or institutional responsibility.
20.8.10(b) Reclassification shall be permitted only where facts support reclassification and the reason is recorded.
20.8.10(c) Informal assurances, private apologies, verbal explanations, email exchanges, or chat messages shall not substitute for required incident records, correction records, notices, or Board / committee reporting.
20.8.10(d) Concealment or improper reclassification of an incident shall itself constitute a governance incident, compliance incident, records incident, or conduct incident as appropriate.
20.8.10(e) The controlling rule shall be that incident management protects public trust through correction, not concealment.
20.9 Monitoring, Evaluation, Assurance, Impact, and Renewal Framework
20.9.1 MEAIR as Monitoring, Evaluation, Assurance, Impact, and Renewal Framework. 20.9.1(a) GCRI Canada shall maintain a Monitoring, Evaluation, Assurance, Impact, and Renewal framework, which may be referred to as MEAIR.
20.9.1(b) MEAIR shall provide a structured institutional method for reviewing operations, controls, outputs, programs, publications, technical assets, public authority interfaces, finance boundaries, data practices, AI practices, cybersecurity practices, community safeguards, records, correction, and Nexus interfaces.
20.9.1(c) MEAIR shall connect monitoring, evaluation, assurance, impact review, corrective action, and renewal into a continuous governance loop.
20.9.1(d) MEAIR shall be public-benefit-oriented, evidence-based, limitation-aware, records-valid, correctionable, non-executing, and role-separated.
20.9.1(e) The controlling rule shall be that institutional learning must be structured, evidenced, and translated into renewal.
20.9.2 Monitoring as Ongoing Review of Operations, Controls, Outputs, and Interfaces. 20.9.2(a) Monitoring means ongoing or periodic review of operations, controls, outputs, systems, repositories, rooms, public materials, public claims, data flows, AI use, cybersecurity, technical releases, Public Authority interfaces, finance-sensitive interfaces, participant conduct, sponsor relationships, provider relationships, community safeguards, and Nexus interfaces.
20.9.2(b) Monitoring shall detect exceptions, anomalies, stale records, missing reviews, unauthorized access, boundary drift, unsupported claims, failed controls, repeated issues, incidents, overdue corrective actions, and emerging risks.
20.9.2(c) Monitoring may be manual, automated, sampled, continuous, event-triggered, register-based, dashboard-based, repository-based, audit-based, or assurance-based.
20.9.2(d) Monitoring shall produce records, alerts, issues, incidents, corrective actions, or assurance findings where appropriate.
20.9.2(e) The controlling rule shall be that monitoring must detect drift before drift becomes institutional practice.
20.9.3 Evaluation as Structured Review of Effectiveness, Fitness, Quality, and Public-Benefit Value. 20.9.3(a) Evaluation means structured review of effectiveness, fitness, quality, usefulness, proportionality, accessibility, public-benefit value, and alignment with mission.
20.9.3(b) Evaluation may apply to programs, research, evidence methods, observability methods, Truth Engine methods, technical baselines, public-good software, Academy materials, public authority learning materials, dashboards, maps, publications, rooms, data governance, AI governance, cybersecurity controls, community safeguards, and Nexus interfaces.
20.9.3(c) Evaluation shall consider whether the activity achieved its stated purpose, remained within role boundaries, protected affected persons and communities, used appropriate evidence, preserved limitations, respected public-safe requirements, and generated learning for improvement.
20.9.3(d) Evaluation shall not be used to inflate impact, market success, finance-readiness, recognition, certification, public authority adoption, provider preference, sponsor value, or procurement relevance beyond the evidence.
20.9.3(e) The controlling rule shall be that evaluation measures institutional fitness and public-benefit value without creating external status by implication.
20.9.4 Assurance as Evidence-Based Confidence That Controls Are Designed and Operating. 20.9.4(a) Assurance means evidence-based confidence that controls are appropriately designed, implemented, operating, documented, effective, reviewed, and corrected where needed.
20.9.4(b) Assurance may review governance controls, records controls, evidence controls, methods controls, research controls, publication controls, data controls, AI controls, cybersecurity controls, Public Authority boundary controls, finance-boundary controls, fiscal controls, sponsor controls, provider controls, community safeguards, legal compliance controls, and Nexus-interface controls.
20.9.4(c) Assurance shall test both control design and control operation and shall not treat written policy alone as proof of control effectiveness.
20.9.4(d) Assurance findings shall be recorded, assigned, corrected, verified, and reported according to risk.
20.9.4(e) The controlling rule shall be that assurance must be based on evidence of control operation, not confidence in intention.
20.9.5 Impact Review as Evidence-Based, Limitation-Aware, Non-Inflated Assessment of Public-Benefit Effects. 20.9.5(a) Impact review means evidence-based, limitation-aware, non-inflated assessment of public-benefit effects.
20.9.5(b) Impact review may consider evidence quality, public-benefit contribution, learning value, technical value, research value, public authority learning value, community safeguard value, publication usefulness, data governance improvement, AI governance improvement, cybersecurity improvement, records improvement, and Nexus interoperability improvement.
20.9.5(c) Impact review shall distinguish outputs, outcomes, contribution, attribution, correlation, causal inference, counterfactual uncertainty, limitations, assumptions, stage truth, and downstream dependency.
20.9.5(d) Impact review shall not claim that GCRI Canada caused public authority decisions, finance outcomes, procurement outcomes, market outcomes, insurance outcomes, recognition outcomes, certification outcomes, or execution outcomes unless proper evidence and authority support the exact statement.
20.9.5(e) The controlling rule shall be that impact claims must be more cautious than impact ambition.
20.9.6 Renewal as Updating of Policies, Methods, Records, Training, Systems, Technical Assets, Committees, Registers, and Public Materials. 20.9.6(a) Renewal means updating policies, procedures, methods, records, training, systems, repositories, technical assets, public-good software, Open Technical Baselines, controlled vocabulary, committees, councils, registers, room rules, contracts, public materials, dashboards, maps, datasets, publications, and public claims in response to monitoring, evaluation, assurance, impact review, incidents, legal changes, technical changes, public authority feedback, community feedback, or Nexus evolution.
20.9.6(b) Renewal may include correction, supersession, withdrawal, retraction, reclassification, redesign, retraining, contract amendment, access change, technical patch, method update, policy update, committee redesign, register update, or public-safe notice.
20.9.6(c) Renewal shall preserve versioning, change logs, authority records, effective dates, transition notes, dependency review, public-safe status, and correction paths.
20.9.6(d) Renewal shall not be used for silent edit, reputation management, sponsor appeasement, provider preference, public authority pressure, finance overclaim, or unrecorded authority expansion.
20.9.6(e) The controlling rule shall be that institutional renewal must be visible, authorized, recorded, and correctionable.
20.9.7 MEAIR as Internal Governance Function, Not Rating, Certification, Public Authority Approval, Finance-Readiness, or External Guarantee by Default. 20.9.7(a) MEAIR shall be an internal governance and public-benefit learning function and shall not constitute rating, certification, recognition, maturity status, public authority approval, regulatory approval, procurement approval, public finance approval, finance-readiness, insurance-readiness, external guarantee, provider endorsement, sponsor validation, or execution authority by default.
20.9.7(b) MEAIR findings may inform GCRI Canada governance, records, correction, public-safe summaries, Board reporting, and controlled learning, but shall not be marketed as external approval or assurance to third parties unless a separate lawful authority and proper records support the exact external use.
20.9.7(c) Where MEAIR summaries are shared externally, they shall include scope, limitations, public-safe status, role boundaries, and no-reliance language where appropriate.
20.9.7(d) MEAIR materials shall not be used by sponsors, providers, hosts, Public Authorities, capital readers, National Companies, Project SPVs, or Nexus actors to claim endorsement, finance-readiness, certification, procurement advantage, public authority adoption, or public approval.
20.9.7(e) The controlling rule shall be that internal confidence is not external status.
20.9.8 MEAIR as Periodic and Event-Triggered. 20.9.8(a) MEAIR shall be periodic and event-triggered.
20.9.8(b) Periodic MEAIR may occur annually, semi-annually, quarterly, monthly, by program cycle, by release cycle, by Board direction, by committee mandate, or by risk-based schedule.
20.9.8(c) Event-triggered MEAIR shall occur where material incidents, legal changes, public authority changes, finance-sensitive changes, major technical releases, major data changes, AI system changes, cybersecurity events, public claims issues, community concerns, protected knowledge concerns, sponsor or provider concerns, or Nexus-interface changes require review.
20.9.8(d) MEAIR schedules shall be recorded, owned, and linked to compliance calendars, risk registers, issue registers, control registers, and Board or committee reporting cycles.
20.9.8(e) The controlling rule shall be that review occurs both by calendar and by consequence.
20.9.9 MEAIR Records, Plans, Findings, Corrective Actions, and Public-Safe Summaries. 20.9.9(a) MEAIR records shall include monitoring plans, evaluation plans, assurance plans, impact review plans, renewal plans, findings, evidence reviewed, limitations, corrective actions, owners, due dates, verification methods, Board or committee reports, and public-safe summaries where appropriate.
20.9.9(b) Findings shall identify whether an issue relates to design weakness, operating failure, evidence weakness, public claims risk, data risk, AI risk, cybersecurity risk, Public Authority risk, finance-boundary risk, protected knowledge risk, legal risk, or public trust risk.
20.9.9(c) Corrective actions shall be assigned, tracked, verified, and linked to relevant registers.
20.9.9(d) Public-safe summaries may be issued where transparency is valuable and may summarize MEAIR activities without exposing legal privilege, confidential information, personal information, Public Authority Data, cybersecurity-sensitive information, finance-sensitive information, commercially sensitive information, community-protected information, or protected knowledge.
20.9.9(e) The controlling rule shall be that MEAIR must produce records and renewal, not merely observation.
20.9.10 MEAIR Assurance and Board / Committee Reporting. 20.9.10(a) GCRI Canada shall conduct MEAIR Assurance and report material MEAIR findings to the Board or authorized committee.
20.9.10(b) MEAIR Assurance shall review whether monitoring, evaluation, assurance, impact review, and renewal processes are planned, risk-based, timely, evidence-supported, corrective, non-inflating, records-valid, and linked to governance action.
20.9.10(c) Board or committee reporting shall include material findings, high-risk gaps, unresolved issues, repeated patterns, corrective action status, impact review limitations, renewal actions, public-safe summary recommendations, and resource needs.
20.9.10(d) MEAIR Assurance shall identify whether institutional learning is occurring or whether the same risks recur without control improvement.
20.9.10(e) The controlling rule shall be that MEAIR itself must be assured because learning systems can become ceremonial without evidence of renewal.
20.10 Monitoring
20.10.1 Monitoring of Governance Operations. 20.10.1(a) GCRI Canada shall monitor governance operations, including Board meetings, committee activity, council activity, Working Group activity, delegations, Board-reserved matters, officer authority, conflicts, recusals, related-party transactions, decision records, governance incidents, and governance corrective actions.
20.10.1(b) Monitoring shall identify defective authority, missing approvals, stale delegations, informal governance, missing conflict disclosures, recusal failures, committee overreach, council overreach, sponsor influence, provider influence, Public Authority confusion, finance overclaim, and records gaps.
20.10.1(c) Governance monitoring shall be linked to the Governance Register, Delegation Register, Conflict Register, Recusal Register, Board records, committee records, council records, Issue Register, Incident Register, and Risk Register.
20.10.1(d) Findings shall be escalated where lawful authority, fiduciary duty, mission lock, legal separateness, non-execution, or public trust may be affected.
20.10.1(e) The controlling rule shall be that governance must be monitored because authority can drift through routine practice.
20.10.2 Monitoring of Evidence, Methods, Observatory, and Truth Engine Operations. 20.10.2(a) GCRI Canada shall monitor evidence, methods, Observatory, and Truth Engine operations for source lineage, metadata completeness, review status, version currency, limitation statements, confidence levels, uncertainty, method integrity, controlled vocabulary use, public-safe status, and correction paths.
20.10.2(b) Monitoring shall identify unsupported evidence, stale evidence, source gaps, method drift, benchmark misuse, ontology drift, translation drift, AI-generated false citation, hallucinated source, missing review, dependency failure, and use beyond authority.
20.10.2(c) Monitoring shall apply to evidence packs, method records, ontology records, controlled vocabulary records, Observatory outputs, Truth Engine outputs, dashboards, maps, datasets, software outputs, technical baselines, and public-safe summaries.
20.10.2(d) Findings shall trigger correction, reclassification, method review, publication review, technical review, public-safe review, or Stop-the-Line where required.
20.10.2(e) The controlling rule shall be that evidence and methods must be monitored because technical truth can degrade through time, reuse, and context shift.
20.10.3 Monitoring of Research, Publications, Public Claims, Dashboards, Maps, and Communications. 20.10.3(a) GCRI Canada shall monitor research, publications, public claims, dashboards, maps, datasets, software releases, APIs, schemas, Academy materials, public authority learning materials, media statements, websites, social media, public-safe outputs, and controlled annexes.
20.10.3(b) Monitoring shall identify unsupported claims, stale materials, public authority overclaim, finance overclaim, certification overclaim, recognition overclaim, provider preference, sponsor validation, procurement implication, public warning implication, emergency command implication, defamation risk, privacy risk, IP risk, protected knowledge exposure, sensitive-location exposure, and misleading visualization.
20.10.3(c) Monitoring shall include post-publication review where reliance risk exists, including monitoring for third-party misuse, media misquotation, sponsor amplification, provider amplification, public authority misdescription, finance-sensitive misuse, and public misunderstanding.
20.10.3(d) Findings shall trigger correction, clarification, erratum, supersession, withdrawal, retraction, public-safe notice, controlled notice, takedown request, public claims correction, or legal review where required.
20.10.3(e) The controlling rule shall be that publication risk continues after publication.
20.10.4 Monitoring of Records, Registers, Gazette, Versioning, and Correction. 20.10.4(a) GCRI Canada shall monitor records, registers, Gazette where applicable, authoritative repositories, versioning, change logs, metadata, authority mapping, retention, legal holds, correction records, supersession chains, withdrawal records, retraction records, and archive records.
20.10.4(b) Monitoring shall identify missing Case IDs, incomplete metadata, ownerless records, stale registers, unauthorized edits, silent edits, missing change logs, missing authority source, uncontrolled documents, broken supersession chains, overdue corrections, unclosed incidents, and public materials inconsistent with current records.
20.10.4(c) Monitoring shall ensure that official registers are reconciled, repositories are authoritative, Gazette notices are accurate where used, and public-safe materials reflect current correction status.
20.10.4(d) Findings shall trigger record correction, register update, repository remediation, Gazette correction, public-safe notice, controlled notice, legal hold review, or assurance follow-up.
20.10.4(e) The controlling rule shall be that records must be monitored because institutional validity depends on current and correct records.
20.10.5 Monitoring of Data, AI, Cybersecurity, Technical Assets, Repositories, Controlled Rooms, and Secure Releases. 20.10.5(a) GCRI Canada shall monitor data, AI, cybersecurity, technical assets, repositories, controlled rooms, clean rooms, data rooms, evidence rooms, public authority rooms, capital-reader rooms, no-download rooms, secure releases, software, APIs, schemas, dashboards, maps, datasets, models, compute environments, keys, tokens, secrets, and system access.
20.10.5(b) Monitoring shall identify unauthorized data access, stale access, excessive permissions, missing classification, unauthorized AI use, sensitive data in unauthorized AI systems, hallucination reliance, model drift, prompt leakage, embedding leakage, cybersecurity alerts, secrets exposure, repository compromise, insecure dependency, SBOM gaps, vulnerability backlog, insecure release, room misuse, and unauthorized downloads.
20.10.5(c) Monitoring shall be proportionate to data sensitivity, system criticality, Public Authority Data, cyber-sensitive materials, infrastructure-sensitive materials, finance-sensitive materials, protected knowledge, and public trust risk.
20.10.5(d) Findings shall trigger access revocation, key rotation, data quarantine, model restriction, repository freeze, patching, incident response, breach assessment, public-safe release hold, or legal review where required.
20.10.5(e) The controlling rule shall be that technical monitoring is governance monitoring because systems carry institutional authority.
20.10.6 Monitoring of Public Authority Interfaces, Capacity Classifications, and Public Warning Boundaries. 20.10.6(a) GCRI Canada shall monitor Public Authority interfaces, capacity classifications, reference approvals, Public Authority Data terms, public authority rooms, public authority learning materials, dashboards, maps, public authority communications, public warning boundaries, emergency command boundaries, regulatory boundaries, procurement boundaries, funding boundaries, and public finance boundaries.
20.10.6(b) Monitoring shall identify missing capacity classification, unauthorized Public Authority reference, stale Public Authority approval, public authority overclaim, endorsement implication, adoption implication, regulatory implication, procurement implication, funding implication, public finance implication, public warning implication, emergency command implication, and sovereign obligation implication.
20.10.6(c) Monitoring shall apply to names, logos, titles, quotes, photographs, agency names, jurisdictions, attendance references, data contribution references, public authority learning materials, media statements, reports, dashboards, maps, and public-safe summaries.
20.10.6(d) Findings shall trigger reference correction, Public Authority clarification, public-safe notice, controlled notice, room redesign, access restriction, legal review, public claims correction, or Stop-the-Line where required.
20.10.6(e) The controlling rule shall be that Public Authority meaning must be monitored because public power can be inferred from repeated reference.
20.10.7 Monitoring of Finance Boundaries, GRA Interfaces, Capital-Reader Rooms, Sponsorship, Grants, Donations, and Procurement Neutrality. 20.10.7(a) GCRI Canada shall monitor finance boundaries, GRA interfaces, Proof Pack inputs, diligence gap maps, capital-reader rooms, RNFD / NFD / UNFSD materials, public finance reader participation, insurance-readiness references, sponsorships, grants, donations, restricted funds, in-kind contributions, procurement neutrality, related-party transactions, and anti-inurement controls.
20.10.7(b) Monitoring shall identify finance-readiness overclaim, investment advice implication, securities solicitation implication, brokerage implication, lending implication, insurance approval implication, rating implication, guarantee implication, public finance approval implication, capital commitment implication, token or payment implication, sponsor control, donor control, grantor control, provider preference, procurement steering, private benefit, and restricted fund misuse.
20.10.7(c) Monitoring shall apply to public materials, room materials, funder materials, sponsor materials, provider materials, grant reports, donor communications, public authority finance materials, capital-reader communications, and Nexus-interface materials.
20.10.7(d) Findings shall trigger GRA routing, finance-safe language correction, access restriction, room redesign, public-safe notice, controlled notice, legal review, fiscal correction, fund correction, public claims correction, or Board reporting.
20.10.7(e) The controlling rule shall be that finance meaning must be monitored because financial reliance can arise from audience, context, and repetition before formal transaction activity.
20.10.8 Monitoring of Participant Conduct, Conflicts, Access, and Public Claims. 20.10.8(a) GCRI Canada shall monitor participant conduct, conflicts, independence, access rights, confidentiality, data use, AI use, cybersecurity obligations, IP obligations, public claims, sponsor interactions, provider interactions, Public Authority interactions, finance-sensitive interactions, room behavior, and closeout obligations.
20.10.8(b) Monitoring shall identify conflict non-disclosure, recusal failure, unauthorized access, unauthorized data use, unauthorized AI use, confidentiality breach, cybersecurity weakness, public claims overreach, use of GCRI Canada name or materials without approval, sponsor influence, provider influence, procurement overclaim, finance overclaim, and Public Authority overclaim.
20.10.8(c) Monitoring shall apply to employees, contractors, fellows, advisors, volunteers, members where applicable, council participants, Working Group participants, contributors, maintainers, sponsors, donors, providers, hosts, universities, communities, Public Authorities, capital readers, National Companies, Project SPVs, and Nexus participants.
20.10.8(d) Findings shall trigger reminder, training, access restriction, conflict review, public claims correction, participant discipline, contract remedy, suspension, termination, or legal review where appropriate.
20.10.8(e) The controlling rule shall be that participant conduct must be monitored because people carry institutional authority into public and controlled spaces.
20.10.9 Monitoring of Community Safeguards and Protected Knowledge Controls. 20.10.9(a) GCRI Canada shall monitor community safeguards and protected knowledge controls.
20.10.9(b) Monitoring shall identify extraction risk, consent or non-consent failure where applicable, community misdescription, protected knowledge exposure, unsafe mapping, sensitive-location exposure, re-identification risk, group harm, cultural harm, ecological harm, vulnerable participant risk, whistleblower exposure, protected person exposure, and grievance pathway failure.
20.10.9(c) Monitoring shall apply to research, fieldwork, workshops, public authority learning, dashboards, maps, datasets, reports, media materials, AI outputs, repositories, public-safe summaries, Academy materials, and public claims involving communities or protected knowledge.
20.10.9(d) Findings shall trigger community consultation where appropriate, protected knowledge review, redaction, aggregation, access restriction, withdrawal, retraction, public-safe notice, controlled notice, grievance remedy, legal review, or Board / committee reporting where material.
20.10.9(e) The controlling rule shall be that community safeguards must be monitored because harm can arise after collection, through reuse, publication, visualization, or interpretation.
20.10.10 Monitoring Records, Exceptions, Alerts, and Escalations. 20.10.10(a) Monitoring records shall be maintained for material monitoring activities, exceptions, alerts, findings, escalations, corrective actions, and closeout.
20.10.10(b) Monitoring records shall identify monitoring activity, owner, custodian, date, scope, method, systems reviewed, records reviewed, exceptions found, severity, affected domains, affected records, affected persons, affected communities, affected Public Authorities, affected public materials, interim controls, issue registration, incident registration, escalation, corrective action, verification, and closeout.
20.10.10(c) Alerts shall be triaged according to severity and shall not be ignored, suppressed, or closed without review where they involve material risk.
20.10.10(d) Monitoring exceptions shall be linked to the Risk Register, Issue Register, Control Register, Incident Register, and applicable domain registers.
20.10.10(e) The controlling rule shall be that monitoring creates institutional duty to review, escalate, correct, and learn where signals show risk.
20.11 Evaluation
20.11.1 Evaluation of Mission Alignment. 20.11.1(a) GCRI Canada shall evaluate mission alignment across its governance, programs, research, evidence work, methods work, public-good software, Open Technical Baselines, data activities, AI activities, cybersecurity posture, publications, public authority learning, sponsorships, grants, participant relationships, community interfaces, and Nexus interfaces.
20.11.1(b) Evaluation of mission alignment shall determine whether an activity remains consistent with GCRI Canada’s Canadian public-benefit, nonprofit, non-share, non-distributing, non-executing, evidence-and-methods, observability, ontology, public-good R&D, public-good software, technical baseline, validity-by-record, correctionability, public-safe publication, and legal-separateness mandate.
20.11.1(c) Evaluation shall identify whether an activity has drifted toward consultancy, execution, provider preference, sponsor control, public authority substitution, finance-readiness activity, certification, procurement steering, market operation, public warning, emergency command, data brokerage, technical asset enclosure, or status-confusing Nexus role collapse.
20.11.1(d) Mission alignment evaluation shall consider purpose, authority, funding source, participants, outputs, public claims, data use, technical assets, downstream reliance, Public Authority proximity, finance sensitivity, community impact, and public trust consequence.
20.11.1(e) The controlling rule shall be that mission alignment must be evaluated by substance, not by label.
20.11.2 Evaluation of Public-Benefit Effectiveness. 20.11.2(a) GCRI Canada shall evaluate the public-benefit effectiveness of its activities.
20.11.2(b) Public-benefit effectiveness means the extent to which an activity advances lawful public-good evidence, methods, observability, ontology, technical truth, learning, transparency with protection, public-safe publication, institutional capacity, community safeguards, data rights, cybersecurity, correctionability, and Nexus-compatible public-good infrastructure.
20.11.2(c) Evaluation shall consider whether the activity addresses a real public-benefit need, is accessible to intended users where appropriate, avoids unnecessary complexity, preserves limitations, avoids extraction, supports correction, and improves institutional or public understanding without creating public authority, finance, certification, procurement, or provider-status overclaim.
20.11.2(d) Public-benefit effectiveness shall not be measured by publicity, capital interest, sponsor satisfaction, provider uptake, public authority attendance, media amplification, number of dashboards, number of publications, or technical sophistication alone.
20.11.2(e) The controlling rule shall be that public-benefit effectiveness is measured by useful, lawful, bounded, evidence-based contribution to public trust and public-good capacity.
20.11.3 Evaluation of Evidence Quality. 20.11.3(a) GCRI Canada shall evaluate evidence quality in material evidence records, evidence packs, publications, dashboards, maps, datasets, public-safe summaries, technical notes, research outputs, public authority learning materials, GRA inputs, GRF inputs, Protocol Authority inputs, and Nexus-interface materials.
20.11.3(b) Evidence quality evaluation shall consider source lineage, provenance, reliability, completeness, timeliness, representativeness, bias, uncertainty, confidence, limitations, review status, classification, access class, public-safe status, and correction path.
20.11.3(c) Evaluation shall identify unsupported evidence, stale evidence, overbroad evidence, misclassified evidence, misleading aggregation, missing source records, false citation, AI hallucination, public authority misdescription, sponsor influence, provider influence, and use beyond source authority.
20.11.3(d) Evidence quality findings shall trigger correction, reclassification, limitation update, review update, publication correction, dashboard correction, map correction, dataset correction, controlled notice, public-safe notice, or withdrawal where required.
20.11.3(e) The controlling rule shall be that evidence quality must be evaluated before evidence is reused, relied upon, or publicly communicated.
20.11.4 Evaluation of Method Fitness. 20.11.4(a) GCRI Canada shall evaluate method fitness for methods, protocols, ontology, controlled vocabulary, benchmarks, evaluation harnesses, Observatory Methods, Truth Engine Methods, technical baselines, public-good software, reference architectures, schemas, APIs, dashboards, maps, and public-safe analytical outputs.
20.11.4(b) Method fitness evaluation shall consider purpose fit, scope, assumptions, limitations, reproducibility where appropriate and lawful, review status, data requirements, technical dependencies, bias, failure modes, security implications, public-safe suitability, localization needs, translation risk, and correction path.
20.11.4(c) Evaluation shall identify method drift, uncontrolled adaptation, terminology drift, unsuitable benchmark use, hidden dependency, weak reproducibility, AI-generated method error, software defect, ontology inconsistency, public authority overmeaning, finance overmeaning, or public claims inflation.
20.11.4(d) Method fitness shall be evaluated when methods are created, materially changed, reused in a new context, localized to a new jurisdiction, connected to public authority learning, connected to finance-sensitive materials, or released publicly.
20.11.4(e) The controlling rule shall be that a method is fit only for its recorded purpose, scope, assumptions, and review status.
20.11.5 Evaluation of Research Integrity. 20.11.5(a) GCRI Canada shall evaluate research integrity in research design, evidence gathering, data use, participant engagement, human-subjects review, community review, Indigenous and protected knowledge protocols, analysis, peer review, publication, authorship, conflict management, AI use, and correction.
20.11.5(b) Research integrity evaluation shall consider ethics approval, consent or authority where applicable, participant protection, data minimization, research independence, sponsor and provider roles, conflicts, reviewer independence, reproducibility, limitation disclosure, publication controls, and correction history.
20.11.5(c) Evaluation shall identify fabrication, falsification, plagiarism, source misrepresentation, undisclosed conflict, sponsor influence, provider influence, data selection capture, publication suppression, AI false citation, unsupported conclusion, protected knowledge misuse, community extraction, or failure to correct.
20.11.5(d) Research integrity findings shall trigger ethics review, legal review, data remediation, publication correction, withdrawal, retraction, participant notice, community consultation, Public Authority notice, training, discipline, or Board / committee reporting where appropriate.
20.11.5(e) The controlling rule shall be that research integrity must protect truth, participants, communities, and public trust together.
20.11.6 Evaluation of Publication Quality and Public-Safe Communication. 20.11.6(a) GCRI Canada shall evaluate publication quality and public-safe communication for publications, reports, whitepapers, technical notes, dashboards, maps, datasets, software releases, API releases, schema releases, Academy materials, public authority learning materials, media statements, websites, social media, public-safe summaries, and controlled annexes.
20.11.6(b) Evaluation shall consider accuracy, claims substantiation, readability, accessibility, controlled vocabulary, boundary language, public-safe status, legal review status, evidence support, limitation disclosure, uncertainty, conflicts, sponsor and provider roles, AI use, Public Authority references, finance references, correction path, and public reliance risk.
20.11.6(c) Evaluation shall identify unsupported claims, stale claims, misleading visuals, public authority overclaim, finance overclaim, certification overclaim, procurement overclaim, provider preference, sponsor validation, public warning confusion, emergency command confusion, sensitive-location exposure, protected knowledge exposure, privacy risk, cybersecurity risk, and public harm risk.
20.11.6(d) Evaluation shall occur before release where risk exists and after release where public reliance, third-party reuse, media coverage, public authority use, or finance-sensitive reading may change meaning.
20.11.6(e) The controlling rule shall be that publication quality includes both factual accuracy and safe public meaning.
20.11.7 Evaluation of Data Governance, AI Governance, Cybersecurity, and Technical Asset Stewardship. 20.11.7(a) GCRI Canada shall evaluate data governance, AI governance, cybersecurity, and technical asset stewardship.
20.11.7(b) Data governance evaluation shall consider lawful basis, purpose limitation, minimization, classification, access, retention, deletion, cross-border transfer, sovereign data, Public Authority Data, rights-bearing data, community-protected data, protected knowledge, breach readiness, and public-safe release.
20.11.7(c) AI governance evaluation shall consider model register completeness, data authority, AI-use approvals, training and embedding limits, retrieval controls, inference records, human review, bias review, safety review, vendor terms, hallucination controls, and AI incident handling.
20.11.7(d) Cybersecurity and technical asset evaluation shall consider system classification, access controls, secrets management, repository security, secure development, secure release, SBOM status, vulnerability management, incident response, business continuity, dashboard security, API security, and technical baseline integrity.
20.11.7(e) Findings shall trigger control updates, access changes, data remediation, AI restrictions, security remediation, release correction, vendor review, training, legal review, or Board / committee reporting where required.
20.11.7(f) The controlling rule shall be that technical stewardship must be evaluated as legal, ethical, operational, and public-trust stewardship.
20.11.8 Evaluation of Public Authority Learning and Boundary Controls. 20.11.8(a) GCRI Canada shall evaluate public authority learning and boundary controls.
20.11.8(b) Evaluation shall consider whether public authority learning materials, rooms, dashboards, maps, simulations, scenario exercises, tabletop materials, technical outputs, public authority references, and public authority data uses remain educational, decision-supporting, public-safe, non-executing, and non-substitutive.
20.11.8(c) Evaluation shall identify whether Public Authority attendance, data contribution, access, quotes, names, logos, titles, agency names, jurisdiction references, or participation could be misunderstood as endorsement, adoption, procurement approval, regulatory approval, funding approval, public finance approval, public warning, emergency command, official guidance, or sovereign obligation.
20.11.8(d) Evaluation shall review capacity classifications, reference approvals, Public Authority Data terms, room rules, boundary language, publication controls, and correction history.
20.11.8(e) The controlling rule shall be that public authority learning must remain learning, not disguised public authority action.
20.11.9 Evaluation of Finance-Boundary Discipline and Fiscal Integrity. 20.11.9(a) GCRI Canada shall evaluate finance-boundary discipline and fiscal integrity.
20.11.9(b) Finance-boundary evaluation shall consider GRA interfaces, Proof Pack inputs, capital-reader rooms, RNFD / NFD / UNFSD support, public finance reader participation, insurance-readiness references, finance-sensitive materials, token / blockchain / DLT / DePIN references, proof receipts, sponsor materials, provider materials, and public claims.
20.11.9(c) Fiscal integrity evaluation shall consider budgets, restricted funds, donations, grants, sponsorships, in-kind contributions, cost recovery, procurement, related-party transactions, compensation, reimbursements, anti-inurement, private benefit, sanctions screening, export-control screening, and financial controls.
20.11.9(d) Evaluation shall identify finance-readiness overclaim, investment-advice implication, solicitation implication, lending implication, insurance approval implication, rating implication, guarantee implication, public finance implication, sponsor control, provider preference, restricted fund breach, private benefit, and fiscal control weakness.
20.11.9(e) The controlling rule shall be that financial support and finance-facing evidence must be evaluated to preserve public-benefit independence and regulated-perimeter discipline.
20.11.10 Evaluation of Community Safeguards, Accessibility, Inclusion, and Do-No-Harm. 20.11.10(a) GCRI Canada shall evaluate community safeguards, accessibility, inclusion, and do-no-harm.
20.11.10(b) Evaluation shall consider whether programs, research, publications, dashboards, maps, datasets, public authority learning, Academy materials, rooms, public claims, and Nexus interfaces protect vulnerable communities, remote communities, Indigenous knowledge holders, local knowledge holders, protected persons, confidential sources, youth, public officials in sensitive roles, and communities affected by risk evidence.
20.11.10(c) Evaluation shall review accessibility, language access, plain-language summaries, community context, consent or non-consent handling where applicable, grievance pathways, non-retaliation, protected knowledge controls, public-safe mapping, re-identification risk, group harm, cultural harm, ecological harm, and remedy pathways.
20.11.10(d) Evaluation shall identify where institutional outputs are technically accurate but socially unsafe, inaccessible, stigmatizing, extractive, misleading, or harmful through context loss.
20.11.10(e) The controlling rule shall be that public-good work must be evaluated for harm to affected communities, not only for benefit to institutional audiences.
20.11.11 Evaluation of Nexus Interface Effectiveness Without Legal Fusion. 20.11.11(a) GCRI Canada shall evaluate Nexus interface effectiveness without legal fusion.
20.11.11(b) Evaluation shall consider whether interfaces with GCRI US, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards / Protocol Authority, Nexus Network, Nexus Universe, Nexus Observatory, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Risk Management, Regional Nexus Consortiums, National Nexus Consortiums, National Companies, Project SPVs, providers, sponsors, hosts, Public Authorities, universities, and communities are effective, lawful, role-separated, records-valid, and correctionable.
20.11.11(c) Evaluation shall identify whether shared records, shared rooms, shared events, shared methods, shared doctrine, shared ontology, shared public communications, shared technical assets, or shared participants create merger, agency, partnership, shared treasury, shared liability, shared employer, authority transfer, public authority confusion, finance-readiness drift, certification drift, protocol-authority confusion, or execution drift.
20.11.11(d) Evaluation shall review interface records, divergence logs, equivalence notes, shared-record boundaries, public claims, legal-separateness language, data interfaces, IP interfaces, and correction coordination.
20.11.11(e) The controlling rule shall be that Nexus interfaces are effective only when they increase interoperability without collapsing institutional roles.
20.11.12 Evaluation Records, Findings, Recommendations, and Renewal Actions. 20.11.12(a) Evaluation records shall be maintained for material evaluations.
20.11.12(b) Evaluation records shall identify evaluation purpose, scope, owner, custodian, method, evidence reviewed, participants, limitations, findings, recommendations, affected records, affected systems, affected public materials, affected communities, affected Public Authorities, affected finance-sensitive materials, corrective actions, renewal actions, due dates, approvals, and closeout.
20.11.12(c) Findings shall distinguish observation, weakness, issue, incident, control failure, public claims risk, legal risk, data risk, AI risk, cybersecurity risk, Public Authority risk, finance-boundary risk, protected knowledge risk, and public trust risk.
20.11.12(d) Recommendations shall be assigned, tracked, verified, linked to relevant registers, and escalated where material.
20.11.12(e) The controlling rule shall be that evaluation must result in recorded learning and renewal, not merely descriptive review.
20.12 Assurance
20.12.1 Assurance as Evidence-Based Review of Control Design and Operating Effectiveness. 20.12.1(a) Assurance shall mean evidence-based review of whether controls are properly designed, implemented, operating, documented, reviewed, corrected, and effective for their intended risk.
20.12.1(b) Assurance shall test both control design and operating effectiveness. A policy, procedure, framework, register, or commitment shall not be treated as an effective control unless evidence shows it is used, maintained, reviewed, and corrected.
20.12.1(c) Assurance may be periodic, event-triggered, risk-based, sample-based, system-based, register-based, repository-based, publication-based, room-based, or Board-directed.
20.12.1(d) Assurance shall produce findings, corrective actions, owners, deadlines, verification methods, escalation decisions, and Board or committee reporting where appropriate.
20.12.1(e) The controlling rule shall be that assurance converts control claims into evidence-backed confidence.
20.12.2 Governance Assurance. 20.12.2(a) Governance Assurance shall review Board authority, officer authority, committee mandates, council boundaries, delegations, Board-reserved matters, conflicts, recusals, related-party transactions, decision packs, meeting records, legal separateness, mission lock, and governance training.
20.12.2(b) Assurance shall identify informal governance, missing records, defective authority, stale delegations, committee overreach, council overreach, officer overreach, sponsor control, provider control, public authority confusion, finance overclaim, and mission drift.
20.12.2(c) Assurance shall review whether governance decisions are properly recorded, scoped, authorized, conflict-managed, and correctionable.
20.12.2(d) Findings may require Board action, governance correction, delegation update, committee charter update, recusal correction, training, legal review, or public-safe clarification.
20.12.2(e) The controlling rule shall be that governance assurance protects the lawful source of all institutional authority.
20.12.3 Evidence Rail Assurance. 20.12.3(a) Evidence Rail Assurance shall review evidence intake, Case IDs, metadata, source lineage, authority mapping, evidence classification, review status, limitations, versioning, public-safe status, use restrictions, and correction path.
20.12.3(b) Assurance shall test whether evidence records are complete, traceable, current, properly classified, supported, reviewed, and used within authority.
20.12.3(c) Assurance shall identify unsupported evidence, stale evidence, missing source lineage, missing metadata, AI-fabricated evidence, public authority misdescription, finance-sensitive misuse, and public claims inflation.
20.12.3(d) Findings may require evidence correction, reclassification, source update, limitation update, downstream dependency review, public-safe notice, controlled notice, or withdrawal from active use.
20.12.3(e) The controlling rule shall be that evidence rail assurance protects the validity of the institutional truth function.
20.12.4 Methods Assurance. 20.12.4(a) Methods Assurance shall review methods, protocols, ontology, controlled vocabulary, evaluation harnesses, benchmarks, technical baselines, software methods, analytical workflows, Observatory Methods, Truth Engine Methods, and public-safe transformation methods.
20.12.4(b) Assurance shall test whether methods are documented, versioned, reviewed, purpose-fit, limitation-aware, reproducible where appropriate and lawful, secure where technical, and correctionable.
20.12.4(c) Assurance shall identify method drift, uncontrolled localization, weak assumptions, benchmark misuse, translation drift, hidden dependencies, model drift, software defects, controlled vocabulary inconsistency, and use outside approved scope.
20.12.4(d) Findings may require method update, controlled vocabulary update, technical review, peer review, benchmark revision, software patch, public-safe limitation update, or supersession.
20.12.4(e) The controlling rule shall be that methods assurance protects the meaning of evidence before evidence becomes output.
20.12.5 Observatory and Truth Engine Assurance. 20.12.5(a) Observatory and Truth Engine Assurance shall review observability methods, data sources, sensing inputs, dashboards, maps, signals, indicators, models, AI-assisted workflows, confidence statements, uncertainty notes, source lineage, public-safe status, and correction paths.
20.12.5(b) Assurance shall test whether Observatory and Truth Engine outputs remain evidence-based, limitation-aware, public-safe, non-executing, non-public-warning, non-public-authority, non-finance-ready, and correctionable.
20.12.5(c) Assurance shall identify stale signals, false signals, model drift, dashboard errors, map over-precision, unsafe location exposure, public warning confusion, Public Authority implication, finance implication, AI hallucination, data leakage, and downstream misuse.
20.12.5(d) Findings may require output correction, dashboard suspension, map revision, data source update, model restriction, public-safe notice, controlled notice, Public Authority clarification, or Stop-the-Line.
20.12.5(e) The controlling rule shall be that observability and truth-engine systems must be assured because public audiences may mistake signals for authority.
20.12.6 Research and Publication Assurance. 20.12.6(a) Research and Publication Assurance shall review research protocols, ethics approvals, human-subjects review, community review, protected knowledge safeguards, peer review, expert review, conflicts, AI use, publication classes, claims substantiation, public-safe review, legal review where required, disclaimers, corrections, withdrawals, and retractions.
20.12.6(b) Assurance shall test whether research outputs and publications are accurate, substantiated, limitation-aware, conflict-disclosed, public-safe, and records-valid.
20.12.6(c) Assurance shall identify publication overclaim, unsupported claims, public authority misdescription, finance overclaim, certification overclaim, provider preference, sponsor influence, public warning confusion, media misquotation, protected knowledge exposure, privacy risk, and IP risk.
20.12.6(d) Findings may require research correction, publication correction, public-safe notice, controlled notice, withdrawal, retraction, legal review, ethics review, or training.
20.12.6(e) The controlling rule shall be that research and publication assurance protects both institutional credibility and public reliance.
20.12.7 Records and Correction Assurance. 20.12.7(a) Records and Correction Assurance shall review official records, registers, authoritative repositories, Gazette notices where applicable, Case IDs, metadata, authority mapping, versioning, no-silent-edit compliance, retention, legal holds, correction states, public-safe correction notices, controlled correction notices, supersession chains, withdrawal records, retraction records, archive records, and access controls.
20.12.7(b) Assurance shall test whether records are complete, current, authoritative, accessible to authorized persons, properly classified, protected from unauthorized edit, and linked to correction paths.
20.12.7(c) Assurance shall identify missing records, stale registers, silent edits, unrecorded approvals, broken supersession chains, incomplete corrections, uncontrolled documents, stale public materials, and unclosed incidents.
20.12.7(d) Findings may require register reconciliation, repository remediation, record correction, public-safe notice, controlled notice, retention correction, legal hold update, or Board / committee reporting.
20.12.7(e) The controlling rule shall be that records and correction assurance protects institutional memory and public meaning.
20.12.8 Data, AI, Cybersecurity, and Technical Asset Assurance. 20.12.8(a) Data, AI, Cybersecurity, and Technical Asset Assurance shall review data governance, privacy, rights-bearing data safeguards, Public Authority Data controls, sovereign data controls, AI governance, model registers, inference records, cybersecurity controls, repository security, secure development, secure release, SBOMs, technical baselines, dashboards, maps, APIs, schemas, datasets, compute environments, controlled rooms, and clean rooms.
20.12.8(b) Assurance shall test whether data is lawfully collected, purpose-limited, minimized, classified, access-controlled, retained, deleted, transferred, published, and corrected.
20.12.8(c) Assurance shall test whether AI systems are authorized, recorded, human-reviewed, data-safe, bias-reviewed where needed, safety-reviewed where needed, vendor-reviewed, and correctionable.
20.12.8(d) Assurance shall test whether cybersecurity controls are designed and operating, including identity, access, secrets, vulnerability management, repository controls, secure release, incident response, and continuity.
20.12.8(e) Findings may require data deletion, access revocation, AI restriction, model restriction, repository freeze, patching, secure release correction, vendor review, breach response, public-safe notice, controlled notice, or legal review.
20.12.8(f) The controlling rule shall be that data, AI, cybersecurity, and technical asset assurance protects the digital foundations of institutional trust.
20.12.9 Public Authority Boundary Assurance. 20.12.9(a) Public Authority Boundary Assurance shall review Public Authority interfaces, capacity classifications, reference approvals, Public Authority Data terms, public authority learning materials, dashboards, maps, rooms, public statements, public warning boundaries, emergency command boundaries, regulatory boundaries, procurement boundaries, funding boundaries, and public finance boundaries.
20.12.9(b) Assurance shall test whether Public Authority participation is properly classified, references are approved, materials use correct boundary language, and no public authority meaning is implied beyond recorded authority.
20.12.9(c) Assurance shall identify endorsement implication, adoption implication, regulatory implication, procurement implication, funding implication, public finance implication, public warning implication, emergency command implication, sovereign obligation implication, and stale or unauthorized Public Authority references.
20.12.9(d) Findings may require Public Authority clarification, reference correction, public-safe notice, controlled notice, room redesign, access restriction, legal review, training, or Board reporting.
20.12.9(e) The controlling rule shall be that Public Authority boundary assurance protects both public authority integrity and GCRI Canada’s non-public-authority role.
20.12.10 Finance, Fiscal, Sponsorship, Grant, and Procurement Neutrality Assurance. 20.12.10(a) Finance, Fiscal, Sponsorship, Grant, and Procurement Neutrality Assurance shall review finance-boundary controls, GRA interfaces, Proof Pack inputs, capital-reader rooms, public finance reader materials, sponsorships, grants, donations, restricted funds, in-kind contributions, procurement, related-party transactions, compensation, reimbursements, anti-inurement, private benefit, and procurement neutrality.
20.12.10(b) Assurance shall identify finance-readiness overclaim, insurance-readiness overclaim, capital-reader reliance risk, investment-advice implication, solicitation implication, rating implication, guarantee implication, public finance approval implication, sponsor control, donor control, grantor control, provider preference, procurement steering, restricted fund breach, private inurement, and improper private benefit.
20.12.10(c) Assurance shall test whether support relationships remain support-without-control, provider relationships remain neutral, procurement processes remain competition-safe, and fiscal records remain accurate and restricted-fund compliant.
20.12.10(d) Findings may require GRA routing, finance-safe language correction, fund correction, public claims correction, sponsor or provider correction, access restriction, legal review, policy update, training, or Board reporting.
20.12.10(e) The controlling rule shall be that financial and support-related assurance preserves independence before money becomes influence.
20.12.11 Legal Compliance Assurance. 20.12.11(a) Legal Compliance Assurance shall review corporate compliance, tax and nonprofit status, charitable-status compatibility where applicable, contracts, grants, employment, contractor classification, research ethics, privacy, data protection, AI legal readiness, cybersecurity legal compliance, sanctions, export controls, competition, procurement-law safety, professional boundaries, IP, publications, lobbying, policy activity, political activity, international collaboration, entity boundaries, insurance, indemnification, legal holds, investigations, disputes, legal reviews, compliance policies, and compliance calendars.
20.12.11(b) Assurance shall test whether legal obligations are identified, calendared, assigned, implemented, recorded, reviewed, and corrected.
20.12.11(c) Assurance shall identify missed filings, stale policies, unreviewed legal risks, unimplemented contractual obligations, sanctions screening gaps, export-control gaps, professional-boundary overclaim, lobbying misclassification, entity-boundary confusion, and unresolved legal incidents.
20.12.11(d) Findings may require legal review, amended filing, contract amendment, activity hold, public-safe clarification, controlled notice, training, policy update, register update, Board reporting, or relationship restructuring.
20.12.11(e) The controlling rule shall be that legal compliance assurance protects the lawful perimeter within which public-benefit work may occur.
20.12.12 Participation, Community Safeguard, and Protected Knowledge Assurance. 20.12.12(a) Participation, Community Safeguard, and Protected Knowledge Assurance shall review member, supporter, sponsor, donor, provider, host, fellow, advisor, contributor, public authority, community, Indigenous knowledge holder, civil society, media, university, capital reader, National Company, Project SPV, and Nexus participant controls.
20.12.12(b) Assurance shall test whether participation is role-based, access-controlled, conflict-managed, confidentiality-protected, data-safe, AI-safe, cybersecurity-safe, public-claims-bounded, sponsor-non-controlling, provider-neutral, and correctionable.
20.12.12(c) Community safeguard and protected knowledge assurance shall review consent and non-consent handling where applicable, community review, protected knowledge protocols, public-safe mapping, grievance pathways, non-retaliation, access controls, publication controls, and correction pathways.
20.12.12(d) Findings may require access restriction, participant correction, sponsor correction, provider correction, community consultation, protected knowledge review, public-safe notice, controlled notice, training, discipline, termination, or Board / committee reporting.
20.12.12(e) The controlling rule shall be that participation assurance protects the people and communities through whom public-benefit work becomes possible.
20.12.13 Assurance Scope, Evidence, Sampling, Findings, Ratings Where Internal, Corrective Actions, and Follow-Up. 20.12.13(a) Each assurance activity shall define scope, evidence, sampling method where used, criteria, limitations, reviewer, owner, custodian, findings, internal rating where used, corrective actions, follow-up, and reporting route.
20.12.13(b) Assurance evidence may include records, registers, policies, procedures, meeting records, access logs, system logs, repository history, publication records, data records, model records, incident records, correction records, contracts, training records, interviews, attestations, technical tests, and sample review.
20.12.13(c) Internal ratings, where used, shall be limited to internal governance meaning and shall not be used as external certification, maturity recognition, finance-readiness, rating, guarantee, provider approval, public authority approval, procurement approval, or public claim unless separately authorized and properly bounded.
20.12.13(d) Corrective actions shall identify owner, due date, verification method, evidence of completion, affected registers, residual risk, and escalation.
20.12.13(e) The controlling rule shall be that assurance must identify what was tested, what was found, what was not tested, and what must change.
20.12.14 Assurance Reports as Internal or Public-Safe Outputs, Not External Certifications by Default. 20.12.14(a) Assurance reports shall be internal or public-safe outputs and shall not constitute external certifications, ratings, guarantees, finance-readiness determinations, insurance-readiness determinations, public authority approvals, procurement approvals, provider endorsements, sponsor validations, maturity recognitions, or protocol effects by default.
20.12.14(b) Internal assurance reports may be shared only according to classification, access class, legal privilege, confidentiality, privacy, cybersecurity, Public Authority sensitivity, finance sensitivity, commercial sensitivity, community-protected information, and protected knowledge requirements.
20.12.14(c) Public-safe assurance summaries may be issued where transparency supports public trust, provided they protect sensitive materials, preserve limitations, use controlled vocabulary, and avoid external-status implications.
20.12.14(d) Any public use of assurance findings shall be reviewed for public claims, Public Authority references, finance overclaim, certification implication, provider preference, sponsor control, legal risk, and correctionability.
20.12.14(e) The controlling rule shall be that assurance may support institutional confidence without becoming external approval.
20.13 Impact Review
20.13.1 Impact Review as Evidence-Based Review of Public-Benefit Effects. 20.13.1(a) Impact Review shall be an evidence-based review of GCRI Canada’s public-benefit effects.
20.13.1(b) Impact Review shall assess how GCRI Canada’s evidence, methods, observability, ontology, public-good R&D, public-good software, Open Technical Baselines, public-safe publications, Academy materials, public authority learning, data governance, AI governance, cybersecurity, community safeguards, and Nexus interfaces contribute to public-good understanding, capacity, literacy, trust, safety, resilience, and institutional learning.
20.13.1(c) Impact Review shall consider outputs, outcomes, contribution, limitations, uncertainty, beneficiary context, affected communities, public authority learning, downstream dependency, and risks of overclaim.
20.13.1(d) Impact Review shall not convert public-benefit contribution into recognition, finance-readiness, certification, procurement approval, public authority adoption, public warning, emergency command, provider preference, sponsor validation, or execution consequence.
20.13.1(e) The controlling rule shall be that impact review measures public-benefit contribution without inflating institutional authority.
20.13.2 Impact Review Shall Avoid Causal Overclaim, Attribution Inflation, Sponsor Amplification, Narrative Acceleration, and False Maturity. 20.13.2(a) Impact Review shall avoid causal overclaim, attribution inflation, sponsor amplification, provider amplification, narrative acceleration, false maturity, public authority over-attribution, finance-signaling, and unsupported public-benefit claims.
20.13.2(b) Impact Review shall distinguish what GCRI Canada directly produced, what it supported, what it influenced, what others adopted, what others executed, what was independently caused, and what cannot be attributed with confidence.
20.13.2(c) Sponsor-funded, donor-funded, provider-supported, Public Authority-adjacent, capital-reader-visible, media-visible, or Nexus-branded activities shall receive heightened impact-claim review.
20.13.2(d) Impact claims shall include limitations, assumptions, evidence basis, temporal scope, stage truth, uncertainty, and correction path.
20.13.2(e) The controlling rule shall be that impact ambition may be broad, but impact claims must remain narrow, evidenced, and correctionable.
20.13.3 Research Impact. 20.13.3(a) Research Impact Review shall assess the public-benefit contribution of research conducted, supported, reviewed, published, or relied upon by GCRI Canada.
20.13.3(b) Research impact may include improved evidence literacy, methods development, technical understanding, public authority learning, public-safe interpretation, data governance improvement, AI governance improvement, cybersecurity improvement, community safeguard improvement, or identification of correction needs.
20.13.3(c) Research impact review shall consider research integrity, ethics, peer review, reproducibility where appropriate, limitations, publication reach, public-safe status, community effects, protected knowledge safeguards, and downstream reuse.
20.13.3(d) Research impact shall not be overstated as policy adoption, public authority approval, market validation, finance-readiness, certification, provider validation, or public consensus unless proper evidence and authority support the exact claim.
20.13.3(e) The controlling rule shall be that research impact is public-benefit learning, not automatic public authority or market effect.
20.13.4 Evidence and Methods Impact. 20.13.4(a) Evidence and Methods Impact Review shall assess how GCRI Canada evidence, methods, ontology, controlled vocabulary, benchmarks, evaluation harnesses, Observatory Methods, Truth Engine Methods, and Open Technical Baselines improve clarity, interoperability, source discipline, correctionability, and public-good technical capacity.
20.13.4(b) Review shall consider whether evidence and methods reduced ambiguity, improved comparability, surfaced uncertainty, enabled public-safe learning, corrected misinformation, improved institutional capacity, or supported downstream role-separated actors within proper boundaries.
20.13.4(c) Review shall identify where methods were misunderstood, overused, underused, misapplied, translated incorrectly, or relied upon beyond scope.
20.13.4(d) Evidence and methods impact claims shall preserve limitation, scope, stage truth, source authority, and non-execution.
20.13.4(e) The controlling rule shall be that evidence and methods impact arises from better truth discipline, not from authority inflation.
20.13.5 Public Authority Learning Impact. 20.13.5(a) Public Authority Learning Impact Review shall assess how GCRI Canada materials, rooms, dashboards, maps, simulations, scenario exercises, technical outputs, public-safe summaries, and Academy materials support evidence literacy, technical literacy, AI literacy, cyber literacy, data governance literacy, observability literacy, and public-safe interpretation by Public Authority participants.
20.13.5(b) Review shall distinguish learning, exposure, participation, observation, feedback, and data contribution from endorsement, adoption, procurement approval, funding approval, public finance approval, regulation, public warning, emergency command, official guidance, or sovereign obligation.
20.13.5(c) Review shall consider whether boundary language was understood, whether materials were useful, whether public authority capacity was classified, whether public-safe controls were effective, and whether any public authority confusion occurred.
20.13.5(d) Public Authority Learning Impact shall not be claimed as public authority action unless the competent Public Authority separately makes and records such action.
20.13.5(e) The controlling rule shall be that public authority learning impact supports public decision capacity without becoming the decision.
20.13.6 Technical Asset Impact. 20.13.6(a) Technical Asset Impact Review shall assess the public-benefit contribution of public-good software, Open Technical Baselines, reference architectures, APIs, schemas, datasets, models, benchmarks, evaluation harnesses, dashboards, maps, repositories, secure release practices, and proof-related technical assets.
20.13.6(b) Review shall consider usefulness, reuse, maintainability, security, interoperability, documentation, accessibility, licensing, anti-enclosure, dependency risk, public-safe status, and correction history.
20.13.6(c) Review shall identify whether technical assets were misused to claim certification, provider preference, public authority approval, procurement advantage, finance-readiness, protocol effect, warranty, guarantee, or execution authority.
20.13.6(d) Technical asset impact claims shall distinguish public-good availability from adoption, conformance, certification, market acceptance, or regulated approval.
20.13.6(e) The controlling rule shall be that technical asset impact is measured by lawful public-good reuse and trustworthiness, not by unauthorized status claims.
20.13.7 Data, AI, Cybersecurity, and Public-Safe Publication Impact. 20.13.7(a) Data, AI, Cybersecurity, and Public-Safe Publication Impact Review shall assess whether GCRI Canada improved data stewardship, privacy protection, rights-bearing data safeguards, AI governance, cybersecurity resilience, technical integrity, public-safe release discipline, and correctionability.
20.13.7(b) Review shall consider impact on data minimization, lawful basis discipline, impact assessments, AI-use controls, model registers, human review, cybersecurity controls, repository security, secure release, incident response, public-safe publication, and reduction of public misunderstanding.
20.13.7(c) Review shall identify whether data, AI, or cybersecurity outputs created new risks, including privacy leakage, AI hallucination, unsafe automation, cybersecurity exposure, public-safe mapping harm, or public claims inflation.
20.13.7(d) Impact shall not be claimed as security certification, privacy certification, AI compliance certification, public authority approval, technology approval, or guarantee.
20.13.7(e) The controlling rule shall be that data, AI, cybersecurity, and public-safe publication impact must include both benefits and risks created by the same work.
20.13.8 Community Safeguard Impact. 20.13.8(a) Community Safeguard Impact Review shall assess whether GCRI Canada’s work protected communities, Indigenous knowledge holders, local knowledge holders, territorial knowledge holders, cultural knowledge holders, environmental knowledge holders, vulnerable participants, protected persons, and affected public-interest groups.
20.13.8(b) Review shall consider whether participation was protected rather than extractive, whether consent and non-consent pathways were respected where applicable, whether grievance and correction pathways were accessible, whether public-safe mapping avoided harm, and whether protected knowledge remained protected.
20.13.8(c) Review shall consider whether outputs improved contextual integrity, public-safe understanding, accessibility, inclusion, dignity, and trust.
20.13.8(d) Community safeguard impact claims shall not use community participation to imply endorsement, consent to all future uses, public authority approval, sponsor validation, or unrestricted publication.
20.13.8(e) The controlling rule shall be that community impact must be assessed with attention to harm avoided, dignity preserved, and control retained by affected communities where applicable.
20.13.9 Nexus Interface Impact. 20.13.9(a) Nexus Interface Impact Review shall assess whether GCRI Canada’s interfaces with GCRI US, GRF, GRA, Protocol Authority, Nexus bodies, Regional Nexus Consortiums, National Nexus Consortiums, National Companies, Project SPVs, providers, sponsors, hosts, Public Authorities, universities, communities, and capital readers improved interoperability without legal fusion.
20.13.9(b) Review shall consider whether shared records, divergence logs, equivalence notes, data interfaces, technical interfaces, public-safe materials, controlled rooms, public authority learning, and GRA / GRF / Protocol Authority interfaces functioned effectively.
20.13.9(c) Review shall identify role confusion, shared-liability implication, authority transfer implication, public authority confusion, finance-readiness drift, protocol-authority confusion, sponsor control, provider preference, or execution drift.
20.13.9(d) Nexus interface impact shall not be claimed as merger, adoption, shared authority, legal equivalence, public authority endorsement, finance-readiness, certification, or execution.
20.13.9(e) The controlling rule shall be that Nexus impact is successful when interoperability improves and role boundaries remain intact.
20.13.10 Climate, WEFH, Disaster, Infrastructure, AI, Cyber, Biosecurity, Energy, Supply Chain, and Public Trust Impact. 20.13.10(a) GCRI Canada may review impact across climate, water, energy, food, health, disaster, infrastructure, AI, cyber, biosecurity, energy systems, supply chains, resilience, Earth observation, geospatial systems, digital twins, robotics, drones, telecommunications, AI-RAN, DePIN, quantum-relevant systems, and public trust domains.
20.13.10(b) Domain impact review shall consider public-benefit contribution to evidence literacy, methods, observability, public-safe interpretation, cross-domain interoperability, risk understanding, public authority learning, community safeguards, and correctionability.
20.13.10(c) Domain impact review shall not convert GCRI Canada into an emergency responder, public warning authority, public authority decision-maker, infrastructure operator, public health authority, cyber defense operator, energy operator, supply-chain operator, provider, insurer, financier, or execution actor.
20.13.10(d) Claims of domain impact shall preserve uncertainty, stage truth, data limitations, public-safe constraints, and role boundaries.
20.13.10(e) The controlling rule shall be that domain impact must be framed as public-benefit evidence and learning unless another proper authority separately acts.
20.13.11 Impact Claims Require Evidence, Limits, Context, and Correction Path. 20.13.11(a) Impact claims shall require evidence, limits, context, and correction path.
20.13.11(b) Each material impact claim shall identify evidence basis, scope, time period, affected audience, contribution type, limitations, uncertainty, dependencies, conflicts, sponsor or provider roles where material, Public Authority role where material, AI use where material, and correction path.
20.13.11(c) Impact claims shall not exceed source authority, review status, evidence quality, method limits, public-safe status, or institutional role.
20.13.11(d) Unsupported, overstated, stale, misleading, or unsafe impact claims shall require correction, clarification, withdrawal, retraction, public-safe notice, controlled notice, or public claims update.
20.13.11(e) The controlling rule shall be that impact claims must remain as correctable as any evidence claim.
20.13.12 Impact Review Records and Public-Safe Impact Summaries. 20.13.12(a) Impact Review records and public-safe impact summaries shall be maintained where impact review is material.
20.13.12(b) Impact Review records shall identify scope, purpose, evidence reviewed, methodology, limitations, affected domains, affected communities, affected Public Authorities, sponsor or provider roles, findings, claims approved, claims rejected, corrective actions, public-safe status, and renewal actions.
20.13.12(c) Public-safe impact summaries may describe public-benefit learning and institutional improvement without exposing confidential, personal, Public Authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, community-protected, or protected knowledge materials.
20.13.12(d) Public-safe impact summaries shall avoid certification, rating, guarantee, finance-readiness, public authority approval, procurement approval, provider endorsement, sponsor validation, public warning, emergency command, or execution implication.
20.13.12(e) The controlling rule shall be that impact transparency must be useful, bounded, safe, and correctionable.
20.14 Renewal
20.14.1 Renewal as Institutional Learning and Updating Function. 20.14.1(a) Renewal shall be GCRI Canada’s institutional learning and updating function.
20.14.1(b) Renewal shall convert monitoring, evaluation, assurance, impact review, incidents, issues, legal changes, technical changes, public authority feedback, community feedback, participant feedback, research developments, Nexus Universe lessons, and assurance findings into updated governance, methods, records, policies, systems, training, technical assets, public materials, and controls.
20.14.1(c) Renewal shall be proactive where foreseeable risk, recurring issue, legal development, technical drift, public claims risk, or public trust risk requires action before incident occurs.
20.14.1(d) Renewal shall preserve versioning, authority, classification, public-safe status, change logs, effective dates, transition plans, dependency review, correction paths, and supersession chains.
20.14.1(e) The controlling rule shall be that a public-good institution must learn formally, not informally forget.
20.14.2 Renewal of Charter Interpretations, Bylaw Alignment, Policies, Procedures, Schedules, Annexes, and Forms. 20.14.2(a) GCRI Canada shall renew Charter interpretations, Bylaw alignment, policies, procedures, schedules, annexes, forms, manuals, templates, delegations, committee charters, council terms, room rules, controlled vocabulary references, and public claims guidance where review identifies need.
20.14.2(b) Renewal may be required by legal changes, governance evaluation, Board direction, assurance findings, incident lessons, public authority feedback, finance-boundary risk, privacy changes, AI changes, cybersecurity changes, research ethics developments, or Nexus interface updates.
20.14.2(c) Renewal shall identify authority, drafter, reviewer, approver, effective date, superseded materials, affected records, affected training, affected contracts, affected public materials, and communication needs.
20.14.2(d) No renewed interpretation, policy, or procedure shall expand GCRI Canada into prohibited functions or dilute non-execution, public authority boundaries, finance boundaries, legal separateness, provider neutrality, sponsor non-control, protected knowledge safeguards, or correctionability.
20.14.2(e) The controlling rule shall be that governance documents must evolve without weakening constitutional boundaries.
20.14.3 Renewal of Evidence Doctrine, Methods, Ontology, Controlled Vocabulary, Technical Baselines, Software, and Reference Architectures. 20.14.3(a) GCRI Canada shall renew evidence doctrine, methods, ontology, controlled vocabulary, technical baselines, public-good software, reference architectures, benchmarks, evaluation harnesses, schemas, APIs, datasets, models, documentation, and release practices where required.
20.14.3(b) Renewal may respond to method error, source error, benchmark failure, ontology drift, vocabulary drift, translation drift, new evidence, software vulnerability, dependency update, AI model change, public-safe concern, localization need, or Nexus interoperability requirement.
20.14.3(c) Renewal shall include versioning, change logs, review records, dependency review, backward-compatibility notes where applicable, breaking-change notices, public-safe summaries where appropriate, and correction records where prior materials are affected.
20.14.3(d) Technical renewal shall preserve licensing, anti-enclosure, cybersecurity, privacy, controlled technology, export-control, public claims, and protected knowledge controls.
20.14.3(e) The controlling rule shall be that technical renewal must update truth and function without creating hidden authority or uncontrolled reliance.
20.14.4 Renewal of Data Governance, AI Governance, Cybersecurity, Secure Collaboration, and Technical Asset Controls. 20.14.4(a) GCRI Canada shall renew data governance, AI governance, cybersecurity, secure collaboration, repository security, controlled room, clean room, data room, technical asset, secure development, secure release, incident response, and business continuity controls where required.
20.14.4(b) Renewal may be required by new data classes, new AI systems, model changes, vendor changes, cyber threats, vulnerabilities, breach events, new public authority data terms, cross-border changes, sovereign data requirements, protected knowledge concerns, secure release issues, or assurance findings.
20.14.4(c) Renewal shall update classifications, access controls, AI-use rules, model registers, inference records, vendor terms, secrets controls, vulnerability controls, repository controls, SBOM practices, release gates, monitoring, incident procedures, and training.
20.14.4(d) Renewal shall include technical implementation, not merely policy update, where the risk is technical or operational.
20.14.4(e) The controlling rule shall be that digital controls must renew at the pace of digital risk.
20.14.5 Renewal of Public Authority Protocols, Finance-Boundary Controls, Sponsorship Controls, and Participation Rules. 20.14.5(a) GCRI Canada shall renew Public Authority protocols, finance-boundary controls, sponsorship controls, donor controls, grant controls, provider controls, host controls, participation rules, room rules, public claims rules, and interface rules where review identifies risk or improvement need.
20.14.5(b) Public Authority protocol renewal may update capacity classifications, reference approval procedures, Public Authority Data terms, no-endorsement language, no-public-warning language, no-command language, procurement-neutrality controls, and public authority learning boundaries.
20.14.5(c) Finance-boundary renewal may update GRA routing, capital-reader room controls, no-advice language, no-solicitation language, no-rating language, no-guarantee language, public finance boundary language, token / DLT / DePIN review, and finance-sensitive publication controls.
20.14.5(d) Sponsorship and participation renewal may update support-without-control clauses, provider neutrality, public claims controls, conflicts, access rules, closeout obligations, and non-retaliation pathways.
20.14.5(e) The controlling rule shall be that boundary controls must renew whenever context creates new ways for public meaning to drift.
20.14.6 Renewal of Community Safeguards, Protected Knowledge Controls, Accessibility, and Non-Retaliation Pathways. 20.14.6(a) GCRI Canada shall renew community safeguards, protected knowledge controls, accessibility practices, inclusion practices, grievance pathways, challenge pathways, remedy pathways, and non-retaliation pathways where required.
20.14.6(b) Renewal may respond to community feedback, Indigenous or local knowledge holder concerns, protected knowledge protocols, public-safe mapping issues, re-identification risk, accessibility gaps, language gaps, participation barriers, grievance trends, retaliation concerns, or public harm.
20.14.6(c) Renewal shall consider consent and non-consent processes where applicable, culturally appropriate review, local context, language access, plain-language materials, sensitive-location controls, aggregation, redaction, public-safe summaries, withdrawal pathways, and correction pathways.
20.14.6(d) Renewal shall not treat communities as passive beneficiaries where they are affected participants, rights-bearing groups, knowledge holders, or protected persons.
20.14.6(e) The controlling rule shall be that safeguards must renew in response to lived risk, not only institutional assessment.
20.14.7 Renewal After Nexus Universe Lessons, Incidents, Assurance Findings, Legal Changes, Technology Changes, Public Authority Feedback, Community Feedback, and Research Developments. 20.14.7(a) Renewal shall occur after Nexus Universe lessons, simulations, exercises, pilots, incidents, near misses, assurance findings, legal changes, regulatory developments, technology changes, cybersecurity threats, AI developments, public authority feedback, community feedback, protected knowledge concerns, participant feedback, research developments, and public claims events.
20.14.7(b) Nexus Universe lessons shall be reviewed for governance, evidence, methods, data, AI, cybersecurity, Public Authority, finance-boundary, community safeguard, technical asset, public-safe publication, and Nexus-interface implications.
20.14.7(c) Legal and technology changes shall be translated into policies, controls, training, registers, contracts, public claims language, technical architecture, release gates, and assurance cycles where required.
20.14.7(d) Feedback shall be treated as evidence for renewal and shall not be dismissed merely because it comes from communities, participants, technical contributors, affected persons, external critics, or non-governance actors.
20.14.7(e) The controlling rule shall be that renewal shall be triggered by consequence and learning, not hierarchy alone.
20.14.8 Renewal Records, Owners, Deadlines, Effective Dates, Public-Safe Summaries, and Supersession Chains. 20.14.8(a) Renewal records shall identify renewal item, source of renewal, owner, custodian, affected materials, affected Charter Parts, affected policies, affected systems, affected data, affected participants, affected Public Authorities, affected public materials, deadline, approval authority, effective date, transition plan, communication plan, public-safe summary need, and supersession chain.
20.14.8(b) Renewal records shall link to risk registers, issue registers, control registers, incident registers, assurance reports, evaluation records, impact review records, legal review records, publication records, data records, AI records, cybersecurity records, Public Authority records, finance-boundary records, and Board or committee records where applicable.
20.14.8(c) Supersession chains shall identify prior version, new version, reason for change, effective date, dependency review, public-safe notice where needed, controlled notice where needed, and archive status.
20.14.8(d) Renewal actions shall not be closed until required updates, communications, training, register changes, and affected-material corrections are complete or otherwise lawfully deferred by record.
20.14.8(e) The controlling rule shall be that renewal is complete only when the new institutional state is recorded and operable.
20.14.9 Renewal Shall Not Be Silent Where Public Materials Are Affected. 20.14.9(a) Renewal shall not be silent where public materials are affected.
20.14.9(b) Where renewal changes public reports, dashboards, maps, datasets, software releases, technical notes, whitepapers, Academy materials, public authority learning materials, public claims, media statements, website materials, public-safe summaries, or Gazette notices where applicable, GCRI Canada shall determine whether public-safe correction, supersession notice, withdrawal notice, retraction notice, archive note, or version notice is required.
20.14.9(c) Silent replacement of public materials shall be prohibited where public reliance, Public Authority reliance, finance-sensitive reliance, community reliance, provider reliance, sponsor reliance, or technical dependency risk exists.
20.14.9(d) Public-facing renewal notices shall preserve sensitivity controls and shall not over-disclose confidential, personal, Public Authority, cybersecurity-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, community-protected, or protected knowledge materials.
20.14.9(e) The controlling rule shall be that public-facing renewal must update public meaning, not merely internal files.
20.14.10 Renewal Register and Board / Committee Reporting. 20.14.10(a) GCRI Canada shall maintain a Renewal Register and report material renewal matters to the Board or authorized committee.
20.14.10(b) The Renewal Register shall identify renewal action, source, owner, custodian, affected domain, affected records, affected public materials, affected systems, affected participants, affected Public Authorities, affected communities, approval status, effective date, supersession chain, communication status, training status, corrective action status, and closeout.
20.14.10(c) Board or committee reporting shall include material renewal themes, overdue renewal items, high-risk renewal gaps, repeated issues requiring structural renewal, public-safe notice needs, resource needs, and unresolved risks.
20.14.10(d) Renewal assurance shall review whether renewal actions were timely, complete, effective, recorded, communicated, and linked to affected controls.
20.14.10(e) The controlling rule shall be that renewal must be governed because learning without implementation is not institutional change.
20.15 Annual Assurance Report or Public-Safe Integrity Statement
20.15.1 Board May Require an Annual Assurance Report, Internal Integrity Report, Public-Safe Integrity Statement, or Equivalent Review. 20.15.1(a) The Board may require an Annual Assurance Report, Internal Integrity Report, Public-Safe Integrity Statement, or equivalent review.
20.15.1(b) Such report or statement may be internal, controlled, restricted, public-safe, or divided into internal and public-safe versions according to classification, legal privilege, confidentiality, privacy, cybersecurity, Public Authority sensitivity, finance sensitivity, protected knowledge, and public trust considerations.
20.15.1(c) The report may summarize institutional risk management, monitoring, evaluation, assurance, impact review, renewal, incidents, corrective actions, legal compliance, public-safe publication, public authority boundaries, finance boundaries, data governance, AI governance, cybersecurity, community safeguards, and Nexus interface discipline.
20.15.1(d) The Board may determine frequency, scope, audience, approval process, publication class, public-safe status, and archive status.
20.15.1(e) The controlling rule shall be that integrity reporting is a Board-directed trust instrument, not a marketing exercise.
20.15.2 Scope May Include Governance, Evidence, Methods, Research, Records, Data, AI, Cybersecurity, Public Authority Boundaries, Finance Boundaries, Technical Assets, Participation, Safeguards, Legal Compliance, and Nexus Interfaces. 20.15.2(a) The scope of an Annual Assurance Report, Internal Integrity Report, Public-Safe Integrity Statement, or equivalent review may include governance, fiduciary duty, mission lock, legal separateness, evidence, methods, observability, Truth Engine methods, research integrity, publication quality, records, registers, correctionability, data governance, AI governance, cybersecurity, technical assets, repositories, public-good software, Open Technical Baselines, Public Authority boundaries, finance boundaries, fiscal integrity, sponsorship, grants, procurement neutrality, participation, community safeguards, protected knowledge, legal compliance, international collaboration, and Nexus interfaces.
20.15.2(b) Scope shall identify included domains, excluded domains, period reviewed, evidence reviewed, limitations, methodology, assurance level where internally used, and public-safe constraints.
20.15.2(c) Scope shall be sufficient to support the claims made and shall not imply comprehensive assurance where review was limited.
20.15.2(d) Where material domains are excluded, the report shall not create misleading confidence about those domains.
20.15.2(e) The controlling rule shall be that integrity reporting must match its scope and evidence.
20.15.3 Public-Safe Version Shall Protect Confidential, Personal, Public Authority, Cyber-Sensitive, Infrastructure-Sensitive, Finance-Sensitive, Commercially Sensitive, Community-Protected, and Protected Knowledge Materials. 20.15.3(a) Any public-safe version shall protect confidential, personal, Public Authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, employment-sensitive, legal-privileged, security-sensitive, community-protected, Indigenous, Local, Territorial, Cultural, Environmental, and Protected Knowledge materials.
20.15.3(b) Public-safe versions may use aggregation, redaction, generalization, delayed disclosure, category-level reporting, public-safe summaries, controlled annexes, or omission where necessary to prevent harm.
20.15.3(c) Public-safe integrity reporting shall not expose vulnerabilities, sensitive locations, protected persons, confidential sources, personal information, security controls, breach details, Public Authority Data, finance-sensitive materials, protected knowledge, or information that could enable misuse.
20.15.3(d) Internal or controlled versions may contain more detail where lawful and necessary, subject to classification, access, privilege, and need-to-know controls.
20.15.3(e) The controlling rule shall be that transparency must be designed so that reporting trust does not create new harm.
20.15.4 Report Shall Identify Major Assurance Themes, Corrective Actions, Renewal Actions, and Public-Benefit Learning Where Appropriate. 20.15.4(a) The report shall identify major assurance themes, corrective actions, renewal actions, public-benefit learning, governance improvements, control improvements, policy updates, training updates, register improvements, technical updates, public-safe publication improvements, and boundary improvements where appropriate.
20.15.4(b) Corrective action reporting shall identify action type, status, domain, general severity where public-safe, completion state, and renewal effect without over-disclosing sensitive information.
20.15.4(c) Public-benefit learning may include improved evidence discipline, method discipline, data governance, AI governance, cybersecurity posture, Public Authority learning, finance-boundary controls, community safeguards, correctionability, and Nexus interoperability.
20.15.4(d) The report shall distinguish completed actions, active actions, deferred actions, unresolved risks, and limitations.
20.15.4(e) The controlling rule shall be that integrity reporting should show what the institution learned and changed, not merely what it claims to value.
20.15.5 Report Shall Avoid Certification, Rating, Guarantee, Finance-Readiness, Public Authority Approval, or Public Warning Implications. 20.15.5(a) The report shall avoid certification, rating, guarantee, finance-readiness, insurance-readiness, public authority approval, regulatory approval, procurement approval, public finance approval, provider endorsement, sponsor validation, public warning, emergency command, maturity recognition, protocol effect, or execution implication.
20.15.5(b) Internal assurance conclusions shall not be described as external certification, independent audit, legal compliance certification, security certification, AI certification, public authority approval, or finance-readiness unless a separate lawful authority and proper records support that exact statement.
20.15.5(c) Public-safe integrity statements shall use boundary language clarifying scope, limitations, non-execution, no public warning, no public authority approval, no finance advice, no certification by default, no provider preference, no sponsor control, and correctionability where appropriate.
20.15.5(d) Sponsors, providers, hosts, capital readers, Public Authorities, National Companies, Project SPVs, or Nexus actors shall not use the report to imply status beyond its stated scope.
20.15.5(e) The controlling rule shall be that assurance reporting shall not become a status product.
20.15.6 Report Shall Use Controlled Vocabulary and Boundary Language. 20.15.6(a) The report shall use controlled vocabulary and boundary language for material Charter and Nexus terms.
20.15.6(b) Terms such as assured, verified, validated, recognized, certified, finance-ready, insurance-ready, public-safe, Nexus-compatible, mature, approved, adopted, official, public authority, proof, truth, confidence, readiness, integrity, risk, assurance, impact, and renewal shall be used only within recorded scope and approved meaning.
20.15.6(c) Plain-language summaries shall preserve controlled meaning and shall not simplify in a manner that creates public authority, finance, certification, procurement, provider, sponsor, or execution overclaim.
20.15.6(d) Translations and localized versions shall be reviewed to prevent vocabulary drift.
20.15.6(e) The controlling rule shall be that integrity reporting must be semantically disciplined because trust words can create authority implications.
20.15.7 Report Shall Identify Limitations and Scope. 20.15.7(a) The report shall identify limitations and scope.
20.15.7(b) Limitations may include time period, domains reviewed, evidence reviewed, sampling limits, systems reviewed, exclusions, reliance on self-reported information, unresolved findings, pending legal review, public-safe redactions, confidentiality constraints, protected knowledge constraints, Public Authority sensitivity, cybersecurity sensitivity, and finance sensitivity.
20.15.7(c) The report shall not imply that unreviewed domains were assured, that unresolved issues were resolved, or that internal controls eliminate all risk.
20.15.7(d) Where limitations materially affect interpretation, they shall be stated clearly and placed where readers can reasonably see them.
20.15.7(e) The controlling rule shall be that limitations are part of integrity, not weakness.
20.15.8 Report Shall Be Correctable and Supersession-Aware. 20.15.8(a) The report shall be correctable and supersession-aware.
20.15.8(b) Each report shall identify version, date, owner, custodian, approval authority, scope, status, correction path, supersession path, archive status, and contact or challenge pathway where appropriate.
20.15.8(c) Errors, omissions, stale statements, unsupported claims, unsafe disclosures, public authority misdescriptions, finance overclaims, protected knowledge issues, or public-safe defects in the report shall require correction, supersession, withdrawal, retraction, controlled notice, or public-safe notice as appropriate.
20.15.8(d) Superseded reports shall remain available or archived according to records policy, public-safe requirements, legal requirements, and reliance risk.
20.15.8(e) The controlling rule shall be that an integrity statement must itself obey correctionability.
20.15.9 Report Records, Approvals, Publication Status, and Archive. 20.15.9(a) Report records, approvals, publication status, and archive status shall be maintained.
20.15.9(b) Records shall identify report title, period, scope, owner, custodian, contributors, reviewers, evidence sources, legal review where applicable, public-safe review, Board or committee approval, publication class, access class, limitations, redactions, version, release date, correction path, supersession status, withdrawal status, retraction status, archive status, and distribution list.
20.15.9(c) Public-safe versions and internal versions shall be linked by record while preserving access restrictions and sensitivity controls.
20.15.9(d) Archive procedures shall preserve prior versions, correction notices, supersession chains, and reliance context.
20.15.9(e) The controlling rule shall be that integrity reporting must have its own record integrity.
20.15.10 Annual Assurance Report Register. 20.15.10(a) GCRI Canada shall maintain an Annual Assurance Report Register.
20.15.10(b) The Register shall identify all Annual Assurance Reports, Internal Integrity Reports, Public-Safe Integrity Statements, equivalent reviews, drafts, approved versions, public-safe versions, controlled annexes, internal annexes, review periods, owners, custodians, approvals, publication status, correction status, supersession status, withdrawal status, retraction status, archive status, and public-safe summaries.
20.15.10(c) The Register shall link to assurance records, risk registers, issue registers, control registers, incident registers, corrective action records, renewal records, legal review records, publication records, Board records, committee records, and Gazette notices where applicable.
20.15.10(d) The Register shall be reviewed periodically for completeness, stale reports, unresolved corrections, improper public use, and missing archive records.
20.15.10(e) The controlling rule shall be that annual or periodic integrity reporting must be tracked as a material constitutional record.
20.16 Control Testing
20.16.1 Control Testing as Periodic or Event-Triggered Review of Key Controls. 20.16.1(a) GCRI Canada shall conduct Control Testing as a periodic or event-triggered review of key controls used to preserve mission lock, lawful authority, evidence integrity, methods integrity, research integrity, records validity, correctionability, data rights, AI governance, cybersecurity, Public Authority boundaries, finance boundaries, sponsor non-control, provider neutrality, community safeguards, protected knowledge, legal separateness, and public trust.
20.16.1(b) Control Testing shall determine whether controls are designed appropriately, implemented in practice, operating as intended, evidenced by records, understood by responsible persons, effective against the risks they address, and corrected when exceptions or failures occur.
20.16.1(c) Control Testing may be scheduled by calendar, directed by the Board or a committee, triggered by incident, triggered by issue recurrence, triggered by assurance finding, triggered by legal change, triggered by technology change, triggered by Public Authority interface, triggered by finance-sensitive activity, triggered by public release, or triggered by material Nexus-interface change.
20.16.1(d) Control Testing shall not be treated as a ceremonial review of written policy. It shall test actual practice, actual records, actual access, actual outputs, actual communications, actual public claims, actual system behavior, and actual correction pathways where applicable.
20.16.1(e) The controlling rule shall be that a key control is reliable only when tested, evidenced, corrected, and renewed.
20.16.2 Testing of Governance Controls. 20.16.2(a) GCRI Canada shall test governance controls relating to Board authority, officer authority, delegations, Board-reserved matters, committee charters, council mandates, Working Group terms, conflicts, recusals, related-party transactions, decision records, minutes, approvals, legal separateness, mission lock, and public claims authority.
20.16.2(b) Testing shall determine whether decisions were made by the proper body or delegate, whether required approvals were obtained, whether conflicts were disclosed and managed, whether recusals were recorded, whether committees and councils remained within mandate, whether Board-reserved matters were escalated, and whether records support the governance action taken.
20.16.2(c) Testing shall identify informal governance, email-only approvals, chat-only approvals, missing Case IDs, stale delegations, unauthorized commitments, founder control, sponsor influence, provider influence, committee overreach, council overreach, and public authority confusion.
20.16.2(d) Governance control failures shall be recorded, corrected, escalated, and, where necessary, subjected to legal review, Board reconsideration, lawful ratification, rescission, public-safe clarification, or governance redesign.
20.16.2(e) The controlling rule shall be that governance controls must be tested because institutional authority is valid only when exercised through proper process and record.
20.16.3 Testing of Evidence and Method Controls. 20.16.3(a) GCRI Canada shall test evidence and method controls relating to evidence intake, source lineage, minimum metadata, authority mapping, Case IDs, review status, classification, public-safe status, versioning, method protocols, ontology, controlled vocabulary, benchmarks, Observatory Methods, Truth Engine Methods, technical baselines, software methods, and correction paths.
20.16.3(b) Testing shall determine whether evidence is traceable, current, reviewed, limitation-aware, source-valid, properly classified, and used within recorded authority.
20.16.3(c) Testing shall determine whether methods are documented, versioned, fit for purpose, reviewed, reproducible where required and lawful, technically sound, semantically controlled, and not used beyond approved scope.
20.16.3(d) Testing shall identify unsupported evidence, stale sources, missing lineage, incomplete metadata, AI-fabricated sources, hallucinated citations, benchmark misuse, method drift, ontology drift, translation drift, technical dependency failure, and uncontrolled reuse.
20.16.3(e) Findings shall require correction, reclassification, method update, controlled vocabulary update, public-safe limitation update, dependency review, publication correction, supersession, withdrawal, or assurance follow-up where appropriate.
20.16.3(f) The controlling rule shall be that evidence and methods controls must be tested because the quality of public-good truth depends on the controls that produce it.
20.16.4 Testing of Research and Publication Controls. 20.16.4(a) GCRI Canada shall test research and publication controls relating to research protocols, ethics review, human-subjects review, community review, protected knowledge protocols, peer review, expert review, conflicts, AI use, claims substantiation, publication classes, review gates, legal review, public-safe review, disclaimers, public authority references, finance references, sponsor references, provider references, correction, withdrawal, and retraction.
20.16.4(b) Testing shall determine whether research and publications were properly authorized, reviewed, classified, substantiated, limitation-aware, conflict-managed, public-safe, and correctionable.
20.16.4(c) Testing shall identify unsupported claims, publication overclaim, public authority misdescription, finance overclaim, certification implication, recognition implication, procurement implication, provider preference, sponsor validation, public warning confusion, emergency command confusion, privacy exposure, IP issue, protected knowledge exposure, sensitive-location exposure, or misleading visualization.
20.16.4(d) Testing shall include post-publication testing where public reliance, Public Authority use, capital-reader reading, media coverage, provider reuse, sponsor reuse, or community impact may have changed the meaning or risk of a publication.
20.16.4(e) Findings shall require publication correction, public-safe notice, controlled notice, withdrawal, retraction, legal review, research review, training, or Board / committee reporting where appropriate.
20.16.4(f) The controlling rule shall be that publication controls must be tested before and after release because public meaning evolves through use.
20.16.5 Testing of Records and Register Controls. 20.16.5(a) GCRI Canada shall test records and register controls relating to Case IDs, minimum metadata, official registers, authoritative repositories, Gazette notices where applicable, authority mapping, versioning, change logs, no-silent-edit discipline, retention, legal holds, access logs, correction records, supersession chains, withdrawal records, retraction records, archive records, and classification.
20.16.5(b) Testing shall determine whether material records are complete, current, authoritative, searchable, properly classified, owner-assigned, custodian-assigned, access-controlled, versioned, and linked to correction paths.
20.16.5(c) Testing shall identify missing records, duplicate records, stale registers, ownerless records, incomplete metadata, broken links, silent edits, unauthorized replacements, missing change logs, missing authority source, broken supersession chains, unclosed corrections, uncontrolled documents, and public materials inconsistent with official records.
20.16.5(d) Testing shall verify that register entries align with underlying records and that public-safe outputs align with current record status.
20.16.5(e) Findings shall require record correction, register reconciliation, repository remediation, Gazette correction where applicable, public-safe notice, controlled notice, legal hold update, retention correction, or assurance follow-up.
20.16.5(f) The controlling rule shall be that records controls must be tested because validity-by-record fails when records are incomplete, stale, or ungoverned.
20.16.6 Testing of Data, AI, Cybersecurity, and Technical Controls. 20.16.6(a) GCRI Canada shall test data, AI, cybersecurity, and technical controls relating to data classification, lawful basis, consent or authority where applicable, purpose limitation, minimization, access rights, retention, deletion, cross-border transfer, sovereign data, AI use, model registers, inference records, retrieval controls, embedding controls, cybersecurity, repository security, secrets, tokens, keys, secure development, secure release, SBOMs, vulnerabilities, dashboards, maps, APIs, schemas, datasets, compute environments, controlled rooms, clean rooms, and technical baselines.
20.16.6(b) Data control testing shall determine whether data is collected, processed, shared, accessed, transferred, retained, deleted, published, and corrected according to classification, lawful authority, purpose, and safeguards.
20.16.6(c) AI control testing shall determine whether AI use is authorized, recorded, human-reviewed, data-safe, vendor-reviewed, bias-reviewed where needed, safety-reviewed where needed, and not used as authority without proper review.
20.16.6(d) Cybersecurity and technical control testing shall determine whether systems, repositories, secrets, access rights, release pipelines, dependencies, vulnerabilities, logs, backups, and incident response controls are designed and operating.
20.16.6(e) Testing shall identify unauthorized access, excessive permissions, stale access, missing deletion, unauthorized AI training, unauthorized embedding, hallucination reliance, prompt leakage, retrieval leakage, key exposure, secret exposure, repository compromise, insecure dependency, SBOM gap, release gate failure, dashboard vulnerability, API risk, and vendor control failure.
20.16.6(f) Findings shall require access revocation, key rotation, data deletion, AI restriction, model restriction, vendor review, repository freeze, patching, secure release correction, breach assessment, legal review, or Board / committee reporting where appropriate.
20.16.6(g) The controlling rule shall be that technical controls must be tested as mission controls because digital systems carry institutional trust.
20.16.7 Testing of Public Authority Boundary Controls. 20.16.7(a) GCRI Canada shall test Public Authority boundary controls relating to capacity classification, Public Authority Data terms, reference approvals, names, logos, titles, quotes, photographs, agency names, jurisdictions, attendance references, public authority learning materials, public authority rooms, dashboards, maps, public warning boundaries, emergency command boundaries, regulatory boundaries, procurement boundaries, funding boundaries, and public finance boundaries.
20.16.7(b) Testing shall determine whether Public Authority participation is correctly classified, references are approved, boundary language is present, public materials avoid overclaim, Public Authority Data is handled according to terms, and no public authority meaning is implied beyond competent authority.
20.16.7(c) Testing shall identify endorsement implication, adoption implication, public warning implication, emergency command implication, regulatory implication, procurement implication, funding implication, public finance implication, sovereign obligation implication, stale approval, unauthorized reference, and misleading public authority proximity.
20.16.7(d) Findings shall require Public Authority clarification, reference correction, public-safe notice, controlled notice, room redesign, access restriction, legal review, public claims correction, Stop-the-Line, or Board / committee reporting where appropriate.
20.16.7(e) The controlling rule shall be that Public Authority boundary controls must be tested because public power can be implied even when not intended.
20.16.8 Testing of Finance-Boundary and Fiscal Controls. 20.16.8(a) GCRI Canada shall test finance-boundary and fiscal controls relating to GRA interfaces, Proof Pack inputs, diligence gap maps, capital-reader rooms, RNFD / NFD / UNFSD support, public finance readers, insurance-readiness references, finance-sensitive public claims, token / blockchain / DLT / DePIN activities, proof receipts, budgets, restricted funds, donations, grants, sponsorships, in-kind contributions, procurement, related-party transactions, compensation, reimbursements, gifts, hospitality, sanctions screening, export-control screening, private benefit, and anti-inurement.
20.16.8(b) Finance-boundary testing shall determine whether materials, rooms, records, publications, and public claims avoid investment advice, securities solicitation, brokerage, finder activity, lending approval, guarantee, insurance approval, underwriting, rating, public finance approval, grant approval, capital commitment, token issuance, custody, payment intermediation, or market operation implications.
20.16.8(c) Fiscal testing shall determine whether funds are authorized, restricted funds are used properly, sponsorship and grant conditions preserve independence, procurement is neutral, related-party transactions are reviewed, compensation is reasonable, and anti-inurement controls operate.
20.16.8(d) Testing shall identify finance overclaim, insurance overclaim, public finance overclaim, sponsor control, donor control, grantor control, provider preference, procurement steering, private benefit, inurement, restricted fund breach, unauthorized payment, or fiscal record weakness.
20.16.8(e) Findings shall require GRA routing, finance-safe language correction, fund correction, payment correction, public claims correction, room redesign, access restriction, legal review, tax review, Board reporting, training, or relationship remedy.
20.16.8(f) The controlling rule shall be that finance-boundary and fiscal controls must be tested because money, capital audiences, and financial language can quickly change institutional meaning.
20.16.9 Testing of Participation, Sponsor, Provider, and Community Safeguard Controls. 20.16.9(a) GCRI Canada shall test participation, sponsor, provider, host, donor, funder, community safeguard, and protected knowledge controls.
20.16.9(b) Participation testing shall determine whether participants are properly classified, conflict-reviewed, access-controlled, trained, confidentiality-bound, data-bound, AI-bound, cybersecurity-bound, public-claims-bounded, and closed out where required.
20.16.9(c) Sponsor and provider testing shall determine whether support relationships preserve independence, support-without-control, provider neutrality, public claims discipline, no procurement advantage, no public authority overclaim, no finance overclaim, no certification implication, no recognition implication, and correction rights.
20.16.9(d) Community safeguard testing shall determine whether community participation is protected, consent and non-consent handling is respected where applicable, protected knowledge protocols are implemented, public-safe mapping controls operate, grievance pathways are accessible, non-retaliation protections are functioning, and correction pathways are available.
20.16.9(e) Testing shall identify sponsor influence, provider preference, unauthorized public claims, access misuse, confidentiality breach, protected knowledge exposure, unsafe mapping, community misdescription, retaliation, extraction risk, or public harm.
20.16.9(f) Findings shall require participant correction, sponsor correction, provider correction, access restriction, retraining, grievance remedy, community consultation, public-safe notice, controlled notice, legal review, suspension, termination, or Board / committee reporting where appropriate.
20.16.9(g) The controlling rule shall be that participation and safeguard controls must be tested because institutional risk often enters through relationships.
20.16.10 Testing Methods, Evidence, Exceptions, Findings, Remediation, and Retesting. 20.16.10(a) Control Testing shall identify testing method, testing scope, control owner, tester, evidence reviewed, sampling method where used, period reviewed, limitations, exceptions, findings, severity, affected risks, affected records, affected persons, affected systems, affected Public Authorities, affected communities, affected public materials, corrective actions, remediation owner, due date, and retesting requirement.
20.16.10(b) Testing methods may include record review, register sampling, system testing, access review, repository review, log review, publication review, room review, interview, walkthrough, technical scan, tabletop exercise, red-team review where appropriate, legal review, or independent review.
20.16.10(c) Exceptions shall be classified as design deficiency, operating deficiency, documentation deficiency, evidence deficiency, training deficiency, access deficiency, legal deficiency, technical deficiency, boundary deficiency, or corrective-action deficiency.
20.16.10(d) Material findings shall require remediation and retesting. Retesting shall verify that corrective action was implemented, operated, evidenced, and linked to affected risks and records.
20.16.10(e) Control Testing records shall be linked to the Control Register, Risk Register, Issue Register, Corrective Action Register, Incident Register, Assurance records, Board or committee records, and affected domain registers.
20.16.10(f) The controlling rule shall be that testing is complete only when exceptions are understood, remediated, and retested where material.
20.17 Corrective Action Plans
20.17.1 Corrective Action Plan Requirement for Material Assurance Findings, Incidents, Issues, Control Failures, or Boundary Breaches. 20.17.1(a) GCRI Canada shall require a Corrective Action Plan for material assurance findings, incidents, issues, control failures, legal noncompliance, public claims failures, records failures, data failures, AI failures, cybersecurity failures, Public Authority boundary breaches, finance-boundary breaches, sponsor-control risks, provider-preference risks, community safeguard failures, protected knowledge breaches, technical release errors, publication errors, or Nexus-interface failures.
20.17.1(b) A Corrective Action Plan shall be required where correction cannot be completed immediately, where multiple records or systems are affected, where root cause review is needed, where public-safe or controlled notice may be required, where legal review is required, where Board or committee reporting is required, or where recurrence risk exists.
20.17.1(c) Corrective Action Plans shall be proportionate to risk but shall not be omitted because the issue is embarrassing, politically sensitive, sponsor-sensitive, provider-sensitive, public authority-sensitive, finance-sensitive, technically complex, or inconvenient.
20.17.1(d) A Corrective Action Plan shall not substitute for immediate containment where immediate hold, quarantine, access restriction, public-safe clarification, or Stop-the-Line action is required.
20.17.1(e) The controlling rule shall be that material defects must be corrected through an owned, recorded, verifiable plan.
20.17.2 Corrective Action Owner. 20.17.2(a) Each Corrective Action Plan shall identify a Corrective Action Owner.
20.17.2(b) The Corrective Action Owner shall be accountable for plan execution, coordination, evidence collection, deadline management, escalation, verification support, and closeout.
20.17.2(c) The Owner shall have sufficient authority, access, competence, independence, and resources to complete the corrective action or shall escalate resource or authority gaps.
20.17.2(d) Where a corrective action crosses governance, legal, technical, data, AI, cybersecurity, publication, Public Authority, finance, community, or Nexus domains, supporting owners may be assigned, but a single accountable Owner shall remain identified.
20.17.2(e) The controlling rule shall be that no corrective action shall be ownerless, collectively vague, or dependent on informal goodwill.
20.17.3 Corrective Action Scope. 20.17.3(a) Each Corrective Action Plan shall define scope.
20.17.3(b) Scope shall identify the finding, incident, issue, control failure, boundary breach, affected domain, affected Charter Part, affected records, affected systems, affected data, affected AI use, affected cybersecurity controls, affected publications, affected Public Authority interfaces, affected finance-sensitive materials, affected communities, affected participants, affected sponsors or providers, affected contracts, affected technical releases, and affected Nexus interfaces.
20.17.3(c) Scope shall identify whether the corrective action is limited to a single event or addresses a systemic pattern.
20.17.3(d) Scope shall be updated where review discovers broader affected materials or downstream dependencies.
20.17.3(e) The controlling rule shall be that correction must be scoped to the actual risk, not to the smallest visible symptom.
20.17.4 Root Cause. 20.17.4(a) Each material Corrective Action Plan shall identify root cause.
20.17.4(b) Root cause may include governance gap, legal review gap, policy gap, procedure gap, training gap, resource gap, system gap, tool failure, access failure, data gap, method gap, AI-use gap, cybersecurity gap, public claims gap, Public Authority boundary gap, finance-boundary gap, sponsor or provider influence, culture gap, or accountability gap.
20.17.4(c) Root cause review shall distinguish immediate cause, contributing factors, systemic cause, recurrence pattern, and control weakness where appropriate.
20.17.4(d) Where root cause cannot be determined promptly, interim controls shall remain in place and root cause analysis shall continue.
20.17.4(e) The controlling rule shall be that correction without root-cause understanding risks repetition.
20.17.5 Interim Control. 20.17.5(a) Each Corrective Action Plan shall identify interim controls where risk may continue before permanent correction.
20.17.5(b) Interim controls may include Stop-the-Line, access restriction, publication hold, public claims hold, data quarantine, AI-use hold, model restriction, repository freeze, key rotation, technical patch, room suspension, Public Authority reference hold, finance-sensitive material hold, sponsor or provider communication hold, legal hold, or controlled notice.
20.17.5(c) Interim controls shall identify owner, scope, effective date, review date, release criteria, and affected persons or systems.
20.17.5(d) Interim controls shall not become indefinite substitutes for permanent correction unless a recorded decision explains why permanent correction is not possible or not required.
20.17.5(e) The controlling rule shall be that interim controls protect against continuing harm while permanent correction is designed.
20.17.6 Permanent Control. 20.17.6(a) Each Corrective Action Plan shall identify the permanent control or controls required to prevent recurrence.
20.17.6(b) Permanent controls may include policy amendment, procedure amendment, training update, legal review trigger, access-control redesign, system configuration, repository protection, data deletion rule, AI-use restriction, vendor term update, contract amendment, public claims approval process, Public Authority reference process, finance-boundary review gate, community safeguard protocol, protected knowledge control, secure release gate, or Board oversight mechanism.
20.17.6(c) Permanent controls shall be mapped to the relevant Risk Register, Control Register, Issue Register, policy, procedure, system, owner, review cycle, and assurance process.
20.17.6(d) Permanent controls shall be implemented in practice and evidenced by records, not merely described in a plan.
20.17.6(e) The controlling rule shall be that permanent correction must change the system that allowed the failure.
20.17.7 Affected Records, Materials, Systems, People, Partners, Interfaces, and Public Outputs. 20.17.7(a) Each Corrective Action Plan shall identify affected records, materials, systems, people, partners, interfaces, and public outputs.
20.17.7(b) Affected records may include Board records, decision records, evidence records, method records, data records, AI records, cybersecurity records, publication records, Public Authority records, finance-boundary records, sponsor records, provider records, community safeguard records, legal review records, contract records, and correction records.
20.17.7(c) Affected materials may include public reports, dashboards, maps, datasets, software releases, APIs, schemas, technical baselines, Academy materials, public authority learning materials, media statements, websites, social media, room materials, and controlled annexes.
20.17.7(d) Affected persons and partners may include Directors, Officers, staff, contractors, fellows, advisors, contributors, participants, Public Authorities, communities, Indigenous knowledge holders, protected persons, sponsors, donors, funders, providers, hosts, universities, capital readers, GRF, GRA, Protocol Authority, Nexus entities, National Companies, and Project SPVs.
20.17.7(e) The Plan shall determine whether affected public outputs require clarification, correction, supersession, withdrawal, retraction, public-safe notice, controlled notice, or archive update.
20.17.7(f) The controlling rule shall be that correction must follow the dependency chain created by the original failure.
20.17.8 Due Date and Milestones. 20.17.8(a) Each Corrective Action Plan shall include due dates and milestones.
20.17.8(b) Due dates shall reflect severity, legal deadlines, public-safe urgency, data sensitivity, cybersecurity exposure, Public Authority consequence, finance consequence, protected knowledge consequence, community harm, public trust risk, and operational dependency.
20.17.8(c) Milestones may include containment complete, root cause complete, legal review complete, affected-material inventory complete, interim notice issued, permanent control designed, permanent control implemented, training completed, public-safe correction issued, controlled notice issued, retesting complete, and closeout approved.
20.17.8(d) Due dates may be revised only by proper authority and with recorded reason, revised risk assessment, interim controls, and updated escalation where material.
20.17.8(e) The controlling rule shall be that correction deadlines must be governed because open corrective actions create continuing risk.
20.17.9 Evidence of Completion. 20.17.9(a) Each Corrective Action Plan shall identify required evidence of completion.
20.17.9(b) Evidence may include corrected record, updated policy, updated procedure, access log, system configuration, key rotation record, deletion certificate, vendor confirmation, contract amendment, publication correction, public-safe notice, controlled notice, training completion record, Board resolution, legal review record, repository change log, release note, assurance record, retesting result, or affected-party acknowledgment where appropriate.
20.17.9(c) Evidence of completion shall be sufficient to demonstrate that the action occurred, not merely that it was intended or verbally confirmed.
20.17.9(d) Evidence shall be stored in the appropriate register or repository and linked to the Corrective Action Plan.
20.17.9(e) The controlling rule shall be that corrective action is complete only when completion is evidenced by record.
20.17.10 Validation and Closeout. 20.17.10(a) Corrective Action Plans shall require validation and closeout.
20.17.10(b) Validation shall determine whether the corrective action was completed, effective, evidenced, properly approved, linked to affected records, and sufficient to address root cause.
20.17.10(c) Validation may include owner certification, independent review, control testing, assurance review, legal review, technical review, data review, publication review, Public Authority clarification, community confirmation where appropriate, or Board / committee review.
20.17.10(d) Closeout shall record final status, validation method, evidence reviewed, residual risk, remaining limitations, renewal actions, future review date, and responsible approver.
20.17.10(e) A Corrective Action Plan shall not be closed where material actions remain incomplete, unverified, or unsupported by evidence.
20.17.10(f) The controlling rule shall be that closeout requires validation, not optimism.
20.17.11 Escalation for Missed Deadlines or Ineffective Corrective Actions. 20.17.11(a) Missed deadlines, ineffective corrective actions, repeated extensions, incomplete evidence, unresolved root cause, or recurrence of the same issue shall trigger escalation.
20.17.11(b) Escalation may be to an Officer, committee, Board, legal counsel, cybersecurity lead, data protection lead, publication lead, Public Authority interface lead, finance-boundary lead, safeguards lead, or other responsible authority according to domain and severity.
20.17.11(c) Escalation shall identify reason for delay or ineffectiveness, continuing risk, interim controls, revised action plan, resource needs, authority gaps, and Board or committee reporting needs.
20.17.11(d) Repeated failure to complete corrective action may result in access restriction, suspension of activity, relationship restriction, training, discipline, contract remedy, policy change, governance redesign, or termination where appropriate.
20.17.11(e) The controlling rule shall be that failed correction is itself a risk signal requiring governance attention.
20.17.12 Corrective Action Register. 20.17.12(a) GCRI Canada shall maintain a Corrective Action Register.
20.17.12(b) The Register shall identify corrective action title, source, Case ID where applicable, domain, owner, custodian, root cause, affected records, affected systems, affected public materials, affected persons, affected communities, affected Public Authorities, affected sponsors or providers, interim controls, permanent controls, due dates, milestones, evidence of completion, validation, status, residual risk, escalation, Board or committee reporting, and closeout.
20.17.12(c) The Register shall link to the Risk Register, Issue Register, Control Register, Incident Register, Assurance records, Evaluation records, Legal Review Register, Publication Register, Data Register, AI Register, Cybersecurity Register, Public Authority Register, Finance Boundary Register, Community Safeguards Register, and Board or committee records where applicable.
20.17.12(d) The Register shall be reviewed periodically for overdue actions, repeated findings, ineffective controls, unverified closure, missing evidence, and systemic patterns.
20.17.12(e) The controlling rule shall be that corrective actions must remain visible until verified and closed.
20.18 Root-Cause Analysis and Lessons Learned
20.18.1 Root-Cause Analysis for Material Incidents, Repeated Issues, Control Failures, or Boundary Breaches. 20.18.1(a) GCRI Canada shall conduct Root-Cause Analysis for material incidents, repeated issues, control failures, boundary breaches, legal noncompliance, Public Authority confusion, finance overclaim, data breach, AI misuse, cybersecurity incident, protected knowledge exposure, publication error, sponsor-control event, provider-preference event, or governance failure.
20.18.1(b) Root-Cause Analysis shall identify what happened, how it happened, why controls failed, who or what was affected, whether the event was isolated or systemic, whether prior signals were missed, and what changes are required to prevent recurrence.
20.18.1(c) Root-Cause Analysis shall be proportionate to severity and may be conducted internally, independently, legally privileged, technically led, community-informed, or Board-directed depending on risk.
20.18.1(d) Root-Cause Analysis shall not be bypassed because the immediate symptom was corrected where recurrence risk remains.
20.18.1(e) The controlling rule shall be that material failures must be understood before they can be sustainably corrected.
20.18.2 Distinguish Human Error, Process Gap, Tool Failure, Training Gap, Governance Gap, Data Gap, Method Gap, Security Gap, Legal Gap, Sponsor / Provider Influence, Resource Gap, and Culture Gap. 20.18.2(a) Root-Cause Analysis shall distinguish human error, process gap, tool failure, training gap, governance gap, data gap, method gap, security gap, legal gap, sponsor influence, provider influence, donor influence, funder influence, resource gap, culture gap, communication gap, authority gap, documentation gap, and monitoring gap.
20.18.2(b) Human error shall not be treated as the sole cause where unclear procedures, inadequate training, excessive workload, poor tooling, ambiguous authority, weak access controls, public claims pressure, sponsor pressure, provider pressure, or cultural incentives contributed to the failure.
20.18.2(c) Sponsor or provider influence shall be identified where funding, tooling, data, facilities, visibility, publication interests, market interests, or relationship pressure affected evidence, methods, publications, corrections, access, public claims, or governance.
20.18.2(d) Culture gap shall be identified where informal shortcuts, fear of escalation, fear of correction, deference to hierarchy, avoidance of legal review, over-optimism, public-claims pressure, technical exceptionalism, or “move fast” practice contributed to risk.
20.18.2(e) The controlling rule shall be that root cause must identify systems and incentives, not merely assign blame to the last visible actor.
20.18.3 Lessons Learned Records. 20.18.3(a) GCRI Canada shall maintain Lessons Learned records for material incidents, repeated issues, assurance findings, control failures, public claims failures, technical release failures, data failures, AI failures, cybersecurity failures, public authority boundary failures, finance-boundary failures, community safeguard issues, protected knowledge issues, legal noncompliance, and Nexus-interface failures.
20.18.3(b) Lessons Learned records shall identify event, date, domain, root cause, affected records, affected persons, affected communities, affected Public Authorities, affected systems, affected public materials, corrective action, preventive action, policy implications, training implications, technical implications, legal implications, communication implications, and renewal actions.
20.18.3(c) Lessons Learned records shall distinguish internal lessons, controlled lessons, public-safe lessons, privileged lessons, confidential lessons, and protected knowledge-sensitive lessons.
20.18.3(d) Lessons Learned records shall be linked to the Risk Register, Issue Register, Control Register, Corrective Action Register, Incident Register, Renewal Register, and Assurance records.
20.18.3(e) The controlling rule shall be that lessons are institutional assets only when recorded and connected to future controls.
20.18.4 Lessons Integrated Into Policies, Methods, Training, Technical Controls, Public-Safe Materials, and Governance Structures. 20.18.4(a) Lessons learned shall be integrated into policies, procedures, methods, controlled vocabulary, training, technical controls, access controls, public-safe materials, publications, dashboards, maps, datasets, room rules, contracts, governance structures, committee mandates, risk registers, control registers, and assurance plans where appropriate.
20.18.4(b) Integration shall identify the specific instrument or control to be updated, responsible owner, deadline, approval authority, public-safe notice need, training need, and verification method.
20.18.4(c) Lessons shall not remain in post-incident reports without implementation where recurrence risk exists.
20.18.4(d) Where lessons require legal review, Public Authority clarification, community consultation, sponsor or provider correction, vendor action, or Board approval, such dependencies shall be recorded and tracked.
20.18.4(e) The controlling rule shall be that a lesson not integrated into controls is an observation, not institutional learning.
20.18.5 Lessons Shared Internally Where Appropriate. 20.18.5(a) Lessons learned shall be shared internally where appropriate to improve institutional practice, training, governance, risk awareness, technical discipline, public-safe communication, and correctionability.
20.18.5(b) Internal sharing shall be role-appropriate, classification-aware, privilege-protective, privacy-protective, cybersecurity-protective, Public Authority-sensitive, finance-sensitive, employment-sensitive, and protected knowledge-sensitive.
20.18.5(c) Internal lessons may be shared through training updates, governance briefings, technical postmortems, policy updates, room rule updates, repository notices, controlled memos, committee reports, or Board reports.
20.18.5(d) Internal sharing shall not expose personal information, protected knowledge, confidential sources, sensitive locations, legal privilege, security vulnerabilities, or employment-sensitive details beyond need-to-know.
20.18.5(e) The controlling rule shall be that internal learning should be broad enough to prevent recurrence and narrow enough to protect rights and sensitive information.
20.18.6 Public-Safe Lessons Shared Externally Where Appropriate. 20.18.6(a) Public-safe lessons may be shared externally where appropriate to strengthen public trust, support public-good learning, correct public misunderstanding, improve community safeguards, or contribute to broader risk literacy.
20.18.6(b) Public-safe lessons shall protect confidential, personal, Public Authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, employment-sensitive, community-protected, Indigenous, Local, Territorial, Cultural, Environmental, and Protected Knowledge materials.
20.18.6(c) Public-safe lessons shall avoid public authority overclaim, finance overclaim, certification implication, procurement implication, provider preference, sponsor validation, public warning implication, emergency command implication, or execution implication.
20.18.6(d) Public-safe lessons shall include scope, limitations, correction path, and boundary language where needed.
20.18.6(e) The controlling rule shall be that external learning shall be shared only when it is safe, lawful, bounded, and useful.
20.18.7 No-Blame Learning Where Appropriate Without Avoiding Accountability. 20.18.7(a) GCRI Canada may use no-blame learning where appropriate to encourage reporting, transparency, early escalation, Stop-the-Line use, incident learning, and correction.
20.18.7(b) No-blame learning may apply where conduct involved good-faith error, ambiguous procedure, inadequate training, tool failure, process weakness, unclear authority, or emerging risk not reasonably understood at the time.
20.18.7(c) No-blame learning shall not prevent accountability for misconduct, retaliation, fraud, bribery, intentional misrepresentation, deliberate data misuse, deliberate AI misuse, deliberate cybersecurity misconduct, knowing protected knowledge misuse, sponsor control, provider preference, or reckless boundary breach.
20.18.7(d) No-blame approaches shall still require correction, training, control update, record update, and recurrence prevention.
20.18.7(e) The controlling rule shall be that learning may be non-punitive without being non-accountable.
20.18.8 Accountability Where Misconduct, Negligence, Retaliation, Fraud, Misrepresentation, or Reckless Boundary Breach Exists. 20.18.8(a) Accountability shall apply where misconduct, negligence, retaliation, fraud, theft, bribery, corruption, harassment, discrimination, intentional misrepresentation, deliberate public overclaim, intentional data misuse, AI misuse, cybersecurity misconduct, protected knowledge misuse, Public Authority misdescription, finance overclaim, sponsor control, provider preference, or reckless boundary breach exists.
20.18.8(b) Accountability may include training, warning, access restriction, recusal, role restriction, removal from committee or council, suspension, termination, contract remedy, fund return, public claims correction, legal review, Board reporting, external notice, or legal action.
20.18.8(c) Accountability shall be proportionate, records-valid, non-retaliatory, procedurally fair where applicable, and protective of affected persons, communities, Public Authorities, and institutional trust.
20.18.8(d) Accountability shall not be avoided because the actor is senior, influential, a founder, sponsor, provider, donor, funder, Public Authority participant, key technical contributor, or commercially important relationship.
20.18.8(e) The controlling rule shall be that public-good learning requires courage to correct systems and courage to hold actors accountable where warranted.
20.18.9 Lessons Learned Register. 20.18.9(a) GCRI Canada shall maintain a Lessons Learned Register.
20.18.9(b) The Register shall identify lesson title, source event, domain, date, owner, custodian, root cause, affected risks, affected controls, affected records, affected systems, affected persons, affected communities, affected Public Authorities, affected public materials, lesson classification, required renewal actions, training actions, policy actions, technical actions, public-safe summary status, and closeout.
20.18.9(c) The Register shall link to the Risk Register, Issue Register, Control Register, Incident Register, Corrective Action Register, Renewal Register, Evaluation records, Assurance records, Impact Review records, Legal Review Register, and Board or committee records.
20.18.9(d) Access shall be controlled for legal privilege, confidentiality, privacy, cybersecurity, Public Authority sensitivity, finance sensitivity, employment sensitivity, protected knowledge, and governance need.
20.18.9(e) The controlling rule shall be that lessons must be registered so institutional memory survives personnel, platforms, and controversy.
20.18.10 Lessons Learned Assurance. 20.18.10(a) GCRI Canada shall conduct Lessons Learned Assurance.
20.18.10(b) Assurance shall review whether lessons were identified, recorded, classified, assigned, integrated into controls, translated into training, linked to corrective action, reflected in renewal, and verified for effectiveness.
20.18.10(c) Assurance shall identify repeated failures without learning, lessons not implemented, training not updated, policies not updated, technical controls not changed, corrective actions not verified, and public-safe lessons not shared where appropriate.
20.18.10(d) Findings may require Board reporting, committee review, renewed corrective action, policy update, training update, control redesign, technical remediation, public-safe summary, or independent review.
20.18.10(e) The controlling rule shall be that the institution must assure not only that it responded, but that it learned.
20.19 Early Warning for Institutional Risk Without Public Warning Authority
20.19.1 Internal Early Warning as Governance Tool, Not Official Public Warning. 20.19.1(a) Internal Early Warning shall be a governance tool for identifying and communicating emerging institutional risks within GCRI Canada and, where appropriate, to controlled audiences.
20.19.1(b) Internal Early Warning shall not constitute an official public warning, emergency alert, public safety order, evacuation notice, regulatory warning, public health notice, cyber command, infrastructure directive, procurement notice, finance notice, investment warning, insurance notice, or Public Authority determination.
20.19.1(c) Internal Early Warning may be used to alert Officers, Directors, committees, risk owners, technical leads, data leads, AI leads, cybersecurity leads, publication leads, Public Authority interface leads, finance-boundary leads, safeguards leads, and authorized participants to emerging risks requiring review, containment, correction, or escalation.
20.19.1(d) Internal Early Warning shall include boundary language where there is risk of confusion with official public warnings or Public Authority action.
20.19.1(e) The controlling rule shall be that GCRI Canada may warn itself and controlled participants about institutional risk without becoming a public warning authority.
20.19.2 Early Warning for Boundary Risk, Data Risk, Cyber Risk, AI Risk, Public Authority Confusion, Finance Overclaim, Sponsor Control, Provider Preference, Protected Knowledge Exposure, Publication Error, and Public Trust Risk. 20.19.2(a) Early Warning may be used for boundary risk, non-execution risk, Public Authority confusion, public warning confusion, emergency command confusion, finance overclaim, regulated financial-perimeter risk, data risk, privacy risk, AI risk, cybersecurity risk, technical release risk, publication error, public claims risk, sponsor control, provider preference, procurement implication, protected knowledge exposure, community harm, legal noncompliance, sanctions risk, export-control risk, competition risk, records failure, correction failure, and public trust risk.
20.19.2(b) Early Warning may be triggered by monitoring, control testing, assurance findings, incident trends, issue recurrence, data anomalies, AI anomalies, cybersecurity alerts, public claims monitoring, media misdescription, Public Authority feedback, community feedback, sponsor or provider behavior, legal developments, technology changes, or Nexus-interface signals.
20.19.2(c) Early Warning shall identify the risk, affected domain, known facts, uncertainty, audience, requested action, interim controls, review owner, expiration or review date, and escalation path.
20.19.2(d) Early Warning shall not be used to exaggerate risk, create panic, pressure Public Authorities, influence finance readers, advantage providers, punish participants, or suppress lawful disagreement.
20.19.2(e) The controlling rule shall be that early warning should accelerate responsible review, not create public authority or market effects.
20.19.3 Internal Alerts to Officers, Committees, Board, or Authorized Participants. 20.19.3(a) Internal alerts may be issued to Officers, committees, the Board, risk owners, control owners, program owners, repository owners, room owners, publication owners, legal or compliance leads, data leads, AI leads, cybersecurity leads, finance-boundary leads, Public Authority interface leads, safeguards leads, and authorized participants.
20.19.3(b) Internal alerts shall be classified according to sensitivity and shall be distributed only to persons with role-based need, subject to confidentiality, legal privilege, privacy, cybersecurity, Public Authority sensitivity, finance sensitivity, employment sensitivity, and protected knowledge controls.
20.19.3(c) Internal alerts shall specify whether action is required, whether Stop-the-Line is in effect, whether legal review is required, whether public claims are on hold, whether access restrictions apply, and whether further dissemination is prohibited.
20.19.3(d) Internal alerts shall be acknowledged where risk requires confirmation of receipt.
20.19.3(e) The controlling rule shall be that internal alerts must reach those who can act while avoiding unnecessary exposure.
20.19.4 Controlled Alerts to Affected Nexus Entities, Public Authorities, Providers, Hosts, Communities, or Partners Where Required or Appropriate. 20.19.4(a) Controlled alerts may be issued to affected Nexus entities, GRF, GRA, Protocol Authority, Regional Nexus Consortiums, National Nexus Consortiums, National Companies, Project SPVs, Public Authorities, providers, hosts, sponsors, universities, communities, protected knowledge holders, partners, vendors, or participants where required or appropriate.
20.19.4(b) Controlled alerts may be appropriate where shared records, shared data, shared rooms, shared technical assets, shared public authority references, shared publications, shared technical baselines, finance-sensitive interfaces, protected knowledge, public-safe materials, or downstream dependencies are affected.
20.19.4(c) Controlled alerts shall identify the affected scope, required action, confidentiality limits, handling class, permitted use, prohibited use, correction path, and boundary language.
20.19.4(d) Controlled alerts shall not imply that the recipient is liable, endorsed, authorized, certified, finance-ready, required to execute, or part of a Public Authority action unless separate lawful records provide otherwise.
20.19.4(e) The controlling rule shall be that controlled alerts may coordinate risk response without transferring authority or liability by implication.
20.19.5 Public-Safe Alerts Where Approved and Properly Framed. 20.19.5(a) Public-safe alerts may be issued where approved and properly framed to correct public misunderstanding, address public-safe publication risk, prevent reliance on erroneous materials, announce withdrawal or supersession, clarify boundary language, or communicate safe institutional updates.
20.19.5(b) Public-safe alerts shall be reviewed for accuracy, legal risk, public authority boundary, finance boundary, privacy, cybersecurity, protected knowledge, community harm, IP, sponsor or provider references, and public reliance risk.
20.19.5(c) Public-safe alerts shall not expose sensitive information, including personal information, Public Authority Data, cyber-sensitive information, infrastructure-sensitive information, finance-sensitive information, commercially sensitive information, confidential information, community-protected information, protected knowledge, vulnerabilities, sensitive locations, or protected persons.
20.19.5(d) Public-safe alerts shall include scope, limitation, version, date, affected materials, correction path, and boundary language where needed.
20.19.5(e) The controlling rule shall be that public-safe alerts may inform the public only within safe, lawful, bounded, and correctionable language.
20.19.6 No Emergency Command or Official Public Warning by Internal Early Warning. 20.19.6(a) No Internal Early Warning, controlled alert, public-safe alert, risk signal, dashboard signal, map signal, AI output, Observatory output, Truth Engine output, technical note, public-safe summary, or incident alert shall constitute emergency command or official public warning by GCRI Canada.
20.19.6(b) GCRI Canada shall not use internal early warning to direct dispatch, deployment, evacuation, shelter, rescue, logistics, public emergency action, public health order, cyber defense action by Public Authorities, infrastructure operation, public finance action, procurement action, or public authority decision.
20.19.6(c) Where urgent public safety conditions are identified, GCRI Canada shall route communications to competent Public Authorities, operators, or emergency actors where lawful and appropriate, while preserving records and boundary language.
20.19.6(d) Public-facing materials that may be confused with official warning shall require heightened legal, public-safe, Public Authority, and communications review.
20.19.6(e) The controlling rule shall be that GCRI Canada may escalate risk information but shall not command emergency or public authority action.
20.19.7 Alert Classification, Audience, Boundary Language, Correction Path, and Expiration. 20.19.7(a) Each material alert shall identify classification, audience, authority, purpose, scope, handling class, access class, public-safe status, boundary language, requested action, correction path, expiration, review date, and owner.
20.19.7(b) Alert classification shall determine whether the alert is internal, confidential, restricted, controlled, public-safe, legal-privileged, cybersecurity-sensitive, Public Authority-sensitive, finance-sensitive, employment-sensitive, community-protected, or protected knowledge-sensitive.
20.19.7(c) Alerts shall include boundary language where risk exists of public warning confusion, Public Authority confusion, finance overclaim, provider preference, sponsor implication, certification implication, or execution implication.
20.19.7(d) Alerts shall expire, be renewed, be superseded, or be withdrawn according to recorded status so stale alerts do not create ongoing confusion.
20.19.7(e) The controlling rule shall be that alerts must be classified, bounded, correctable, and time-aware.
20.19.8 Misuse of Internal Early Warning as Public Warning Requires Correction. 20.19.8(a) Misuse of Internal Early Warning as public warning, emergency command, Public Authority decision, finance signal, provider endorsement, sponsor validation, certification, procurement advice, or market signal shall require correction.
20.19.8(b) Misuse may include unauthorized forwarding, public posting, media use, sponsor amplification, provider amplification, capital-reader reliance, Public Authority misdescription, social media distortion, or removal of boundary language.
20.19.8(c) Corrective action may include takedown request, public-safe clarification, controlled notice, recipient notice, access restriction, participant discipline, sponsor or provider correction, legal review, public claims correction, or relationship remedy.
20.19.8(d) Repeated misuse shall trigger review of alert design, access controls, training, recipient eligibility, and distribution practices.
20.19.8(e) The controlling rule shall be that early warning misuse must be corrected before internal caution becomes public misinformation.
20.19.9 Early Warning Records. 20.19.9(a) GCRI Canada shall maintain Early Warning records.
20.19.9(b) Records shall identify alert title, Case ID where applicable, trigger, owner, custodian, date, audience, classification, scope, known facts, uncertainty, requested action, boundary language, expiration, review date, acknowledgments, related incidents, related issues, related risks, corrective actions, notices, supersession, withdrawal, and closeout.
20.19.9(c) Early Warning records shall link to the Risk Register, Issue Register, Incident Register, Control Register, Corrective Action Register, Publication Register, Public Authority Register, Finance Boundary Register, Data Register, AI Register, Cybersecurity Register, Community Safeguards Register, and Board or committee records where applicable.
20.19.9(d) Access shall be controlled according to sensitivity, privilege, confidentiality, privacy, cybersecurity, Public Authority sensitivity, finance sensitivity, employment sensitivity, community safeguards, protected knowledge, and public-safe status.
20.19.9(e) The controlling rule shall be that alerts must be recorded because warning-like communications can create reliance and must remain correctable.
20.19.10 Early Warning Assurance. 20.19.10(a) GCRI Canada shall conduct Early Warning Assurance.
20.19.10(b) Assurance shall review whether early warnings are timely, accurate, classified, properly distributed, boundary-safe, acknowledged where required, acted upon, expired or renewed, corrected where needed, and not misused as public warnings or authority signals.
20.19.10(c) Assurance shall identify stale alerts, overbroad alerts, under-escalated alerts, missing boundary language, unauthorized distribution, repeated misuse, failure to act, or failure to correct.
20.19.10(d) Findings may require alert process updates, access control changes, training, public-safe correction, controlled notice, legal review, Public Authority clarification, or Board / committee reporting.
20.19.10(e) The controlling rule shall be that early warning must be assured because alerts can prevent harm or create harm depending on how they are framed and used.
20.20 Key Risk Indicators and Integrity Indicators
20.20.1 Key Risk Indicators for Governance. 20.20.1(a) GCRI Canada may maintain Key Risk Indicators for governance to monitor changes in governance risk, authority discipline, mission lock, legal separateness, decision quality, and Board oversight.
20.20.1(b) Governance Key Risk Indicators may include overdue Board actions, missing minutes, missing decision records, stale delegations, unresolved conflicts, recusal failures, related-party exceptions, committee mandate exceptions, council overreach indicators, governance incidents, Board-reserved matters handled informally, and unclosed governance corrective actions.
20.20.1(c) Governance indicators shall be reviewed for patterns showing mission drift, informal governance, founder control, sponsor influence, provider influence, Public Authority confusion, finance overclaim, or legal-separateness risk.
20.20.1(d) Indicator thresholds shall trigger escalation, governance review, training, assurance, or Board action where required.
20.20.1(e) The controlling rule shall be that governance indicators exist to detect authority drift before it becomes institutional practice.
20.20.2 Key Risk Indicators for Evidence Quality. 20.20.2(a) GCRI Canada may maintain Key Risk Indicators for evidence quality.
20.20.2(b) Evidence quality indicators may include missing source lineage, incomplete metadata, stale source age, unresolved evidence limitations, unreviewed evidence packs, evidence corrections, public claims corrections, source disputes, confidence downgrades, unsupported claims identified, AI-generated citation errors, public authority misdescriptions, and downstream dependency corrections.
20.20.2(c) Evidence indicators shall be reviewed for patterns showing weak intake, weak review, stale evidence, sponsor influence, provider influence, overclaim, or poor correctionability.
20.20.2(d) Indicator thresholds shall trigger evidence review, publication review, method review, correction, or assurance.
20.20.2(e) The controlling rule shall be that evidence quality indicators protect public-good truth before public claims rely on weak records.
20.20.3 Key Risk Indicators for Methods Currency. 20.20.3(a) GCRI Canada may maintain Key Risk Indicators for methods currency.
20.20.3(b) Methods currency indicators may include methods past review date, uncontrolled vocabulary drift, unresolved translation issues, benchmark updates overdue, software dependencies stale, unreviewed method adaptations, reproducibility gaps, localization mismatches, method corrections, technical baseline supersessions, and recurring method-use exceptions.
20.20.3(c) Indicators shall be reviewed for patterns showing method drift, weak review cycles, public-safe transformation weakness, ontology inconsistency, technical dependency risk, or uncontrolled reuse.
20.20.3(d) Indicator thresholds shall trigger method renewal, controlled vocabulary review, technical review, peer review, software update, or supersession.
20.20.3(e) The controlling rule shall be that methods currency indicators protect the continuing fitness of the tools through which evidence becomes meaning.
20.20.4 Key Risk Indicators for Research Integrity. 20.20.4(a) GCRI Canada may maintain Key Risk Indicators for research integrity.
20.20.4(b) Research integrity indicators may include ethics reviews pending, protocol deviations, consent issues, community review gaps, protected knowledge concerns, undisclosed conflicts, reviewer recusals, publication conditions unresolved, reproducibility failures, AI-use issues, false citation issues, authorship disputes, data quality issues, research corrections, withdrawals, and retractions.
20.20.4(c) Indicators shall be reviewed for patterns showing inadequate research oversight, sponsor influence, provider influence, data selection capture, publication suppression, ethics weakness, or correction failure.
20.20.4(d) Indicator thresholds shall trigger research review, ethics review, conflict review, data review, publication review, or Board / committee reporting.
20.20.4(e) The controlling rule shall be that research integrity indicators protect both truth-seeking and affected persons.
20.20.5 Key Risk Indicators for Records Completeness. 20.20.5(a) GCRI Canada may maintain Key Risk Indicators for records completeness.
20.20.5(b) Records completeness indicators may include missing Case IDs, incomplete metadata, ownerless records, stale registers, unclosed correction records, broken supersession chains, unrecorded decisions, uncontrolled documents, missing authority mapping, missing change logs, overdue archival actions, legal hold conflicts, and discrepancies between repositories and registers.
20.20.5(c) Indicators shall be reviewed for patterns showing no-record governance, silent edits, unsupported public materials, weak authoritative repository discipline, or correctionability weakness.
20.20.5(d) Indicator thresholds shall trigger register reconciliation, records assurance, repository remediation, correction review, or Board / committee reporting.
20.20.5(e) The controlling rule shall be that records completeness indicators protect validity-by-record.
20.20.6 Key Risk Indicators for Data Rights and Privacy. 20.20.6(a) GCRI Canada may maintain Key Risk Indicators for data rights and privacy.
20.20.6(b) Data rights and privacy indicators may include overdue data reviews, missing lawful basis records, missing consent or authority records where applicable, incomplete privacy notices, unresolved data rights requests, overdue deletion, stale access, unreviewed cross-border transfers, unresolved impact assessments, vendor review gaps, public release reviews pending, re-identification risks, privacy incidents, and breach trends.
20.20.6(c) Indicators shall be reviewed for patterns showing over-collection, unauthorized sharing, weak deletion, unauthorized AI use, Public Authority Data risk, protected knowledge risk, or rights-bearing data weakness.
20.20.6(d) Indicator thresholds shall trigger data protection review, privacy impact assessment, access restriction, vendor review, deletion review, breach assessment, or legal review.
20.20.6(e) The controlling rule shall be that privacy indicators monitor rights risk before rights are harmed.
20.20.7 Key Risk Indicators for AI Use. 20.20.7(a) GCRI Canada may maintain Key Risk Indicators for AI use.
20.20.7(b) AI indicators may include unregistered models, unauthorized AI tools, missing inference records, sensitive data prompts, embedding exceptions, retrieval-source staleness, human review gaps, hallucination findings, false citations, bias findings, unsafe outputs, model drift, unauthorized agent actions, AI vendor review gaps, and AI-related publication corrections.
20.20.7(c) Indicators shall be reviewed for patterns showing overreliance on AI, AI-as-authority drift, uncontrolled data use, weak human review, vendor risk, or public claims inflation.
20.20.7(d) Indicator thresholds shall trigger AI use restriction, model review, data review, vendor review, human review update, publication correction, or legal review.
20.20.7(e) The controlling rule shall be that AI indicators protect GCRI Canada from treating probabilistic outputs as institutional authority.
20.20.8 Key Risk Indicators for Cybersecurity. 20.20.8(a) GCRI Canada may maintain Key Risk Indicators for cybersecurity.
20.20.8(b) Cybersecurity indicators may include stale access, privileged access exceptions, MFA gaps, secrets exposure, unrotated keys, vulnerability backlog, critical patch age, repository security exceptions, unsigned releases, SBOM gaps, insecure dependencies, failed backups, restore-test failures, incident response delays, vendor security gaps, and unauthorized downloads.
20.20.8(c) Indicators shall be reviewed for patterns showing weak identity control, weak repository security, supply-chain risk, poor incident readiness, insecure release, AI leakage risk, or business continuity weakness.
20.20.8(d) Indicator thresholds shall trigger access review, key rotation, patching, repository freeze, secure release hold, vendor review, incident response, or Board / committee reporting.
20.20.8(e) The controlling rule shall be that cybersecurity indicators monitor the technical conditions of institutional trust.
20.20.9 Key Risk Indicators for Public Authority Boundary. 20.20.9(a) GCRI Canada may maintain Key Risk Indicators for Public Authority boundary.
20.20.9(b) Public Authority boundary indicators may include missing capacity classifications, stale reference approvals, unauthorized logo use, public authority misdescription, public warning-like materials, emergency command ambiguity, procurement implication, funding implication, regulatory implication, public finance implication, Public Authority Data term exceptions, and public authority reference corrections.
20.20.9(c) Indicators shall be reviewed for patterns showing public authority proximity being misunderstood as endorsement, adoption, regulation, procurement, funding, public warning, emergency command, or sovereign obligation.
20.20.9(d) Indicator thresholds shall trigger Public Authority clarification, reference correction, public-safe notice, controlled notice, legal review, room redesign, or training.
20.20.9(e) The controlling rule shall be that Public Authority boundary indicators protect against authority being inferred from attendance, names, data, or repetition.
20.20.10 Key Risk Indicators for Finance Boundary. 20.20.10(a) GCRI Canada may maintain Key Risk Indicators for finance boundary.
20.20.10(b) Finance boundary indicators may include finance-sensitive materials without review, GRA routing gaps, capital-reader room exceptions, public finance reader ambiguity, insurance-readiness overclaim, “finance-ready” or “bankable” language exceptions, investment-advice implications, solicitation risk, rating-like language, guarantee-like language, token or payment risk, sponsor finance claims, provider finance claims, and finance-boundary corrections.
20.20.10(c) Indicators shall be reviewed for patterns showing technical evidence being converted into financial reliance, public finance implication, insurance implication, capital-reader overreliance, or GRA role collapse.
20.20.10(d) Indicator thresholds shall trigger finance-boundary review, legal review, GRA routing, public claims correction, room redesign, access restriction, or Board / committee reporting.
20.20.10(e) The controlling rule shall be that finance indicators monitor the point at which evidence may begin to look like capital judgment.
20.20.11 Key Risk Indicators for Sponsor / Provider Influence. 20.20.11(a) GCRI Canada may maintain Key Risk Indicators for sponsor, donor, funder, provider, host, and partner influence.
20.20.11(b) Influence indicators may include sponsor review requests, provider wording changes, donor restrictions, funder conditions, publication-delay requests, correction-resistance events, public acknowledgment exceptions, repeated provider references, provider ranking language, sponsor amplification, Public Authority access concerns, procurement-sensitive provider participation, and conflict disclosures involving sponsors or providers.
20.20.11(c) Indicators shall be reviewed for patterns showing outcome purchase, method capture, publication suppression, public claims influence, access purchase, provider preference, sponsor control, donor control, or grantor control.
20.20.11(d) Indicator thresholds shall trigger independence review, conflict review, sponsor or provider correction, public claims review, contract amendment, relationship restriction, or Board reporting.
20.20.11(e) The controlling rule shall be that influence indicators protect the independence of institutional truth.
20.20.12 Key Risk Indicators for Community Safeguards. 20.20.12(a) GCRI Canada may maintain Key Risk Indicators for community safeguards and protected knowledge.
20.20.12(b) Indicators may include unresolved grievances, community review gaps, consent or non-consent handling gaps where applicable, protected knowledge access exceptions, sensitive-location exposure, map over-precision, re-identification risk, public-safe publication concerns, translation or accessibility complaints, protected person exposure, retaliation concerns, and community correction requests.
20.20.12(c) Indicators shall be reviewed for patterns showing extraction, community misdescription, unsafe visualization, protected knowledge exposure, inaccessible participation, or inadequate remedy.
20.20.12(d) Indicator thresholds shall trigger safeguards review, community consultation, protected knowledge review, public-safe mapping review, access restriction, publication correction, withdrawal, or Board / committee reporting.
20.20.12(e) The controlling rule shall be that community safeguard indicators monitor harm pathways that institutional metrics may otherwise miss.
20.20.13 Integrity Indicators for Correction Timeliness, Public-Safe Claims Quality, Training Completion, Incident Closure, and Assurance Findings. 20.20.13(a) GCRI Canada may maintain Integrity Indicators for correction timeliness, public-safe claims quality, training completion, incident closure, assurance findings, corrective action closure, renewal completion, and public trust discipline.
20.20.13(b) Correction timeliness indicators may include average correction time, overdue corrections, unclosed correction records, repeated correction categories, public-safe notice delays, controlled notice delays, and supersession gaps.
20.20.13(c) Public-safe claims quality indicators may include claims requiring revision, boundary language exceptions, controlled vocabulary misuse, public authority reference corrections, finance-boundary corrections, provider reference corrections, sponsor reference corrections, and third-party misdescription corrections.
20.20.13(d) Training completion indicators may include required training completion, overdue refresh training, external participant acknowledgments, role-based training gaps, incident-driven training updates, and untrained persons with access.
20.20.13(e) Incident closure and assurance indicators may include open incidents by severity, overdue corrective actions, repeat findings, unresolved high-risk findings, ineffective corrective actions, and retesting failures.
20.20.13(f) The controlling rule shall be that integrity indicators measure whether the institution corrects, learns, and maintains boundary discipline over time.
20.20.14 Key Risk Indicator Review, Thresholds, Escalation, and Renewal. 20.20.14(a) Key Risk Indicators and Integrity Indicators shall be reviewed according to defined thresholds, owners, review cycles, escalation paths, and renewal procedures.
20.20.14(b) Thresholds may be quantitative, qualitative, event-based, severity-based, pattern-based, or Board-directed, provided they are recorded and capable of triggering action.
20.20.14(c) Indicator review shall identify trends, emerging risks, repeated issues, control gaps, underreported risks, false confidence, and areas requiring deeper evaluation or assurance.
20.20.14(d) Threshold breaches shall trigger escalation, issue registration, incident registration, control testing, corrective action, legal review, policy renewal, training update, public-safe correction, controlled notice, or Board / committee reporting as appropriate.
20.20.14(e) Indicators shall be renewed where they no longer reflect institutional activity, public-benefit risk, legal risk, data sensitivity, AI use, cybersecurity exposure, Public Authority sensitivity, finance sensitivity, protected knowledge risk, community risk, or Nexus-interface reality.
20.20.14(f) The controlling rule shall be that indicators are useful only when reviewed, acted upon, and renewed with institutional change.
20.21 Maturity Review Without Certification
20.21.1 Internal Maturity Review as Institutional Learning Tool. 20.21.1(a) GCRI Canada may conduct internal maturity review as an institutional learning tool for assessing the development, reliability, completeness, operating discipline, review status, and renewal needs of its governance, evidence, methods, research, records, data, AI, cybersecurity, technical assets, public authority interfaces, finance boundaries, safeguards, and Nexus interfaces.
20.21.1(b) Internal maturity review shall be used to identify what is nascent, emerging, developing, operational, tested, assured, corrected, renewable, or in need of strengthening, and shall not be used to create external status, market standing, public authority meaning, finance-readiness, certification, procurement preference, provider preference, or institutional self-promotion beyond the evidence.
20.21.1(c) Internal maturity review shall be records-valid, scope-limited, evidence-based, limitation-aware, role-separated, and correctionable.
20.21.1(d) Internal maturity review shall support Board oversight, officer planning, control improvement, policy renewal, training design, technical improvement, public-safe communication, and Nexus-interface discipline.
20.21.1(e) The controlling rule shall be that maturity review is a learning mechanism, not a status-conferring instrument.
20.21.2 Maturity Review of Governance, Evidence, Methods, Research, Records, Data, AI, Cybersecurity, Technical Assets, Public Authority Interfaces, Finance Boundaries, Safeguards, and Nexus Interfaces. 20.21.2(a) Internal maturity review may assess governance, Board operations, officer delegations, committee function, council function, conflict controls, legal separateness, mission lock, evidence intake, evidence lineage, methods, ontology, controlled vocabulary, research integrity, records, registers, Gazette discipline where applicable, correctionability, data governance, AI governance, cybersecurity, repositories, public-good software, Open Technical Baselines, dashboards, maps, datasets, APIs, schemas, public authority learning, finance-boundary discipline, fiscal controls, sponsorship controls, provider neutrality, community safeguards, protected knowledge controls, and Nexus interfaces.
20.21.2(b) Maturity review shall identify current state, required state, risk gaps, control gaps, documentation gaps, training gaps, assurance gaps, technical gaps, authority gaps, public claims gaps, and renewal needs.
20.21.2(c) Maturity review may consider whether the relevant function is documented, owned, resourced, implemented, tested, monitored, assured, corrected, renewed, and integrated with related functions.
20.21.2(d) Maturity review shall be heightened where the function affects Public Authorities, finance-sensitive materials, rights-bearing data, protected knowledge, public-safe outputs, public claims, technical releases, cross-border activity, or public trust.
20.21.2(e) The controlling rule shall be that maturity shall be reviewed across the institutional system, not isolated from the boundaries that make the system lawful.
20.21.3 Internal Maturity Review Does Not Create GRF Maturity Record by Default. 20.21.3(a) Internal maturity review by GCRI Canada shall not create a The Global Risks Forum (GRF) maturity record by default.
20.21.3(b) GRF maturity records, recognition, standing, claims discipline, stakeholder formation, registry status, and public-facing legitimacy outputs may arise only through the proper GRF authority, process, record, scope, review, and publication controls.
20.21.3(c) GCRI Canada internal maturity review may provide evidence inputs, methods inputs, correction signals, limitation notes, or public-good technical context to GRF only where properly authorized, classified, recorded, and bounded.
20.21.3(d) No internal maturity term, internal score, internal stage, internal readiness note, internal assurance finding, or internal renewal status shall be represented as a GRF maturity record, recognition, standing, registry status, or public-facing legitimacy statement unless GRF separately creates such record through proper authority.
20.21.3(e) The controlling rule shall be that GCRI Canada may review maturity internally but shall not convert that review into GRF recognition by implication.
20.21.4 Internal Maturity Review Does Not Create Certification, Rating, Finance-Readiness, Public Authority Approval, Procurement Preference, or Provider Preference. 20.21.4(a) Internal maturity review shall not create certification, rating, guarantee, finance-readiness, insurance-readiness, investment readiness, creditworthiness, public finance approval, public authority approval, regulatory approval, procurement preference, provider preference, sponsor validation, maturity recognition, protocol effect, public warning, emergency command, or execution authority by default.
20.21.4(b) Internal maturity review shall not be used by providers, sponsors, hosts, National Companies, Project SPVs, Public Authorities, capital readers, universities, media, or Nexus actors to claim approval, endorsement, adoption, recognition, certification, finance-readiness, procurement advantage, or market status.
20.21.4(c) Any external reference to internal maturity review shall require public claims review, controlled vocabulary review, boundary language, scope limitations, and authority verification.
20.21.4(d) Misuse of maturity review shall require correction, clarification, withdrawal, controlled notice, public-safe notice, access restriction, relationship remedy, or legal review where appropriate.
20.21.4(e) The controlling rule shall be that internal maturity language shall not become external status language.
20.21.5 Maturity Review Uses Stage Truth and Avoids Narrative Acceleration. 20.21.5(a) Internal maturity review shall use stage truth and shall avoid narrative acceleration.
20.21.5(b) Stage truth requires accurate description of whether a function, method, system, asset, record, publication, interface, control, or program is conceptual, drafted, piloted, tested, operational, reviewed, assured, corrected, superseded, withdrawn, retired, or otherwise limited.
20.21.5(c) Narrative acceleration includes describing early-stage, partial, pilot, draft, untested, unreviewed, or context-limited work as mature, proven, validated, scalable, adopted, official, finance-ready, certified, public authority-supported, provider-approved, or market-ready without proper evidence and authority.
20.21.5(d) Maturity review shall identify limits, dependencies, unresolved issues, control gaps, legal constraints, technical constraints, public-safe constraints, community constraints, and correction needs.
20.21.5(e) The controlling rule shall be that maturity truth must slow institutional narrative where evidence has not yet caught up.
20.21.6 Maturity Review May Generate Renewal Actions, Corrective Actions, Training, Policy Updates, or Technical Improvements. 20.21.6(a) Internal maturity review may generate renewal actions, corrective actions, training updates, policy updates, procedure updates, register updates, technical improvements, control redesign, legal review, public claims correction, public-safe review, community safeguard updates, data control updates, AI control updates, cybersecurity improvements, or Nexus-interface improvements.
20.21.6(b) Findings shall be assigned to owners, deadlines, milestones, evidence requirements, validation steps, and closeout criteria where action is required.
20.21.6(c) Maturity gaps shall be recorded in the Risk Register, Issue Register, Control Register, Corrective Action Register, Renewal Register, or other applicable register where material.
20.21.6(d) Maturity review shall not be closed by declaring aspiration; gaps shall be closed through implemented, recorded, and verified change.
20.21.6(e) The controlling rule shall be that maturity review must improve the system, not merely describe it.
20.21.7 Public-Safe Maturity Summaries Require Boundary Language. 20.21.7(a) Public-safe maturity summaries shall require boundary language.
20.21.7(b) Any public-safe summary of internal maturity review shall identify scope, period, methodology, limitations, public-safe status, reviewed domains, excluded domains, evidence basis, and correction path.
20.21.7(c) Public-safe summaries shall not disclose confidential, personal, Public Authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, employment-sensitive, community-protected, Indigenous, Local, Territorial, Cultural, Environmental, or Protected Knowledge materials.
20.21.7(d) Public-safe summaries shall avoid certification, rating, guarantee, GRF maturity record implication, finance-readiness implication, insurance-readiness implication, public authority approval implication, procurement implication, provider preference, sponsor validation, public warning, emergency command, protocol effect, or execution implication.
20.21.7(e) The controlling rule shall be that maturity transparency must be bounded so that internal learning does not become public overclaim.
20.21.8 Maturity Review Correction and Supersession. 20.21.8(a) Internal maturity reviews and public-safe maturity summaries shall be correctable and supersession-aware.
20.21.8(b) Errors, stale ratings, unsupported maturity descriptions, missing limitations, public authority overclaims, finance overclaims, certification implications, provider preference implications, sponsor validation implications, protected knowledge issues, or public-safe defects shall require correction.
20.21.8(c) Correction may include clarification, erratum, correction, reclassification, downgrade, suspension, supersession, withdrawal, retraction, public-safe notice, controlled notice, or archive update.
20.21.8(d) Supersession chains shall identify prior maturity review, new maturity review, reason for change, effective date, affected domains, affected public-safe summaries, affected downstream dependencies, and archive status.
20.21.8(e) The controlling rule shall be that maturity review must be corrected when institutional learning, evidence, or risk status changes.
20.21.9 Internal Maturity Review Register. 20.21.9(a) GCRI Canada shall maintain an Internal Maturity Review Register.
20.21.9(b) The Register shall identify maturity review title, scope, owner, custodian, reviewed domain, period reviewed, methodology, evidence reviewed, internal stage description, limitations, findings, renewal actions, corrective actions, training actions, policy actions, technical actions, public-safe summary status, correction status, supersession status, and closeout.
20.21.9(c) The Register shall link to Risk Register, Issue Register, Control Register, Corrective Action Register, Renewal Register, Assurance records, Evaluation records, Impact Review records, GRF interface records where applicable, GRA interface records where applicable, Public Authority records, Finance Boundary records, and Board or committee records.
20.21.9(d) Access shall be controlled according to classification, confidentiality, privilege, privacy, cybersecurity, Public Authority sensitivity, finance sensitivity, commercial sensitivity, protected knowledge, and governance need.
20.21.9(e) The controlling rule shall be that maturity review must be registered because maturity language can shape institutional behavior and public reliance.
20.21.10 Maturity Review Assurance. 20.21.10(a) GCRI Canada shall conduct Maturity Review Assurance.
20.21.10(b) Assurance shall review whether maturity reviews are evidence-based, scope-bound, stage-truth-aware, non-inflating, properly recorded, corrected where needed, linked to renewal actions, and not misused as certification, rating, GRF maturity record, finance-readiness, public authority approval, procurement preference, provider preference, or sponsor validation.
20.21.10(c) Assurance shall identify maturity overclaim, stale maturity descriptions, incomplete evidence, missing limitation statements, unresolved renewal actions, public-safe summary defects, and unauthorized public use.
20.21.10(d) Findings may require correction, downgrade, supersession, public-safe notice, controlled notice, public claims correction, training, register update, or Board / committee reporting.
20.21.10(e) The controlling rule shall be that maturity review must itself be assured because maturity language can create institutional overconfidence.
20.22 Nexus Universe After-Action and Learning Integration
20.22.1 Nexus Universe Lessons as Renewal Inputs. 20.22.1(a) Lessons from Nexus Universe activities shall be treated as renewal inputs for GCRI Canada where they relate to evidence, methods, observability, Truth Engine methods, public-good software, technical baselines, public authority learning, data governance, AI governance, cybersecurity, controlled rooms, public-safe publication, finance boundaries, community safeguards, sponsor controls, provider neutrality, host interfaces, public claims, or Nexus interfaces.
20.22.1(b) Nexus Universe lessons may arise from planning, design, controlled build, testing, simulation, tabletop exercise, live operation, observation, incident, near miss, participant feedback, Public Authority feedback, community feedback, sponsor feedback, provider feedback, technical failure, publication issue, teardown, or after-action review.
20.22.1(c) Lessons shall be recorded, classified, routed, reviewed, and integrated according to risk and relevance.
20.22.1(d) Nexus Universe lessons shall not be treated as execution authority, operational adoption, certification, recognition, finance-readiness, public authority approval, procurement advantage, provider preference, sponsor validation, or public warning by default.
20.22.1(e) The controlling rule shall be that Nexus Universe learning improves GCRI Canada’s public-good methods without converting GCRI Canada into an event operator, public authority, market actor, or execution body.
20.22.2 Planning-Phase Lessons. 20.22.2(a) Planning-phase lessons shall capture risks, assumptions, role boundaries, governance requirements, records requirements, data requirements, AI requirements, cybersecurity requirements, public authority requirements, finance-boundary requirements, sponsorship requirements, provider requirements, host requirements, community safeguards, and public-safe publication needs identified before Nexus Universe activity.
20.22.2(b) Planning lessons shall assess whether roles were clear, authorities were recorded, participants were classified, public claims were bounded, rooms were structured, technical assets were prepared, data flows were lawful, and safeguard protocols were adequate.
20.22.2(c) Planning lessons shall identify gaps in templates, policies, procedures, controlled vocabulary, legal review triggers, public authority capacity records, finance-boundary controls, and participant onboarding.
20.22.2(d) Planning lessons shall be routed to the responsible owners for renewal before similar activities are repeated.
20.22.2(e) The controlling rule shall be that planning lessons are preventive controls for future Nexus Universe activity.
20.22.3 Controlled-Build Lessons. 20.22.3(a) Controlled-build lessons shall capture learning from the development, configuration, rehearsal, staging, testing, integration, and controlled deployment of Nexus Universe environments, rooms, dashboards, maps, datasets, technical baselines, public-good software, APIs, schemas, Observatory methods, Truth Engine methods, communications, training materials, and participant workflows.
20.22.3(b) Controlled-build lessons shall assess whether technical controls, access controls, cybersecurity controls, data controls, AI controls, repository controls, room controls, public-safe controls, public authority boundary controls, finance-boundary controls, and community safeguards operated as designed.
20.22.3(c) Controlled-build lessons shall identify technical defects, dependency issues, integration gaps, role ambiguity, data leakage risk, AI misuse risk, security issues, public claims risk, sponsor or provider influence, and host-interface risk.
20.22.3(d) Controlled-build lessons may trigger technical patching, control redesign, access changes, training updates, method updates, release corrections, or Stop-the-Line before live use.
20.22.3(e) The controlling rule shall be that controlled build is where failure should be discovered before public or live reliance occurs.
20.22.4 Live-Operation Lessons. 20.22.4(a) Live-operation lessons shall capture learning from active Nexus Universe operation, participant behavior, room activity, public authority learning, dashboard use, map use, technical output use, data flows, AI use, public-safe communications, provider participation, sponsor presence, host support, community engagement, capital-reader observation, and incident response.
20.22.4(b) Live-operation lessons shall assess whether boundaries held under real-time pressure, whether role language remained clear, whether Public Authority participation was properly understood, whether finance-sensitive audiences were properly controlled, whether providers avoided preference claims, whether sponsors avoided control claims, and whether public-safe communications remained accurate.
20.22.4(c) Live-operation lessons shall identify public warning confusion, emergency command confusion, procurement implication, finance overclaim, data misuse, AI misuse, cybersecurity issue, protected knowledge exposure, community harm, participant conduct issue, media misdescription, or uncontrolled public claim.
20.22.4(d) Live-operation lessons may require immediate correction, Stop-the-Line, controlled notice, public-safe notice, access restriction, room redesign, technical patch, public claims correction, or escalation.
20.22.4(e) The controlling rule shall be that live operation tests whether written boundaries survive operational reality.
20.22.5 Teardown and After-Action Lessons. 20.22.5(a) Teardown and after-action lessons shall capture learning from closure, decommissioning, data disposition, access revocation, repository updates, room closeout, participant closeout, sponsor and provider closeout, public authority closeout, host closeout, archive, correction, public-safe summary, and post-event review.
20.22.5(b) Teardown lessons shall assess whether access was revoked, credentials were closed, data was returned, deleted, sealed, retained, or archived according to records, rooms were closed, materials were classified, public claims were reviewed, and participants understood post-event limitations.
20.22.5(c) After-action review shall identify what worked, what failed, what was unclear, what was misunderstood, what risks emerged, what incidents occurred, what corrections were required, and what renewal actions are needed.
20.22.5(d) Teardown and after-action lessons shall be linked to corrective actions, renewal actions, training updates, public-safe summaries, and future Nexus Universe planning.
20.22.5(e) The controlling rule shall be that Nexus Universe activity is not complete until records, access, public meaning, and lessons are closed.
20.22.6 Evidence, Observatory, Truth Engine, Academy, Docket, Grid, Rails, Public Authority, Provider, Sponsor, Host, Community, and Capital-Reader Lessons. 20.22.6(a) Nexus Universe after-action review shall identify lessons across evidence, Observatory, Truth Engine, Academy, Docket, Grid, Rails, Public Authority, provider, sponsor, host, community, capital-reader, and Nexus-interface dimensions where applicable.
20.22.6(b) Evidence lessons shall assess source quality, metadata, lineage, limitations, uncertainty, correction, and reuse. Observatory and Truth Engine lessons shall assess signal quality, dashboard accuracy, map safety, AI use, data flows, confidence language, and public-safe interpretation.
20.22.6(c) Academy lessons shall assess training value, public authority learning, participant literacy, controlled vocabulary comprehension, accessibility, and boundary understanding.
20.22.6(d) Docket, Grid, and Rails lessons shall be routed to the competent GRF, GRA, Protocol Authority, or Nexus-interface owners where relevant, without GCRI Canada assuming their authority.
20.22.6(e) Public Authority, provider, sponsor, host, community, and capital-reader lessons shall distinguish learning value from endorsement, finance-readiness, procurement, certification, public authority action, sponsor validation, provider preference, or execution.
20.22.6(f) The controlling rule shall be that lessons must be routed to the right institutional owner without collapsing roles.
20.22.7 Lessons Shall Not Be Treated as Certification, Recognition, Finance-Readiness, Public Authority Approval, Procurement Advantage, or Execution Determination by Default. 20.22.7(a) Nexus Universe lessons shall not be treated as certification, recognition, maturity record, finance-readiness, insurance-readiness, public authority approval, regulatory approval, procurement advantage, provider preference, sponsor validation, protocol effect, public warning, emergency command, operational approval, or execution determination by default.
20.22.7(b) Observation that a method, provider, host, dashboard, map, software release, technical baseline, room, process, or interface performed in a Nexus Universe context shall not mean that such item is certified, recognized, mature, finance-ready, procurement-ready, public authority-approved, or suitable for deployment.
20.22.7(c) Any external statement about Nexus Universe lessons shall require public claims review, controlled vocabulary review, evidence support, limitation language, and boundary language.
20.22.7(d) Misuse of Nexus Universe lessons for market, procurement, finance, certification, recognition, or public authority claims shall require correction.
20.22.7(e) The controlling rule shall be that learning from simulation or convening is not status by default.
20.22.8 Lessons Shall Be Routed to Correct Owners, Committees, Registers, Policies, Methods, Technical Assets, and Nexus Interfaces. 20.22.8(a) Nexus Universe lessons shall be routed to correct owners, committees, registers, policies, methods, technical assets, and Nexus interfaces.
20.22.8(b) Routing shall identify whether the lesson belongs to GCRI Canada governance, research, evidence, methods, data, AI, cybersecurity, publication, public authority interface, finance-boundary, community safeguard, legal compliance, technical release, sponsor, provider, host, participant, or Nexus-interface functions.
20.22.8(c) Lessons relevant to GRF, GRA, Protocol Authority, Nexus Network, Nexus Universe, Nexus Observatory, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Risk Management, Regional Nexus Consortiums, National Nexus Consortiums, National Companies, Project SPVs, qualified providers, hosts, sponsors, universities, Public Authorities, communities, or capital readers shall be routed through proper interface records and boundary language.
20.22.8(d) Routing shall identify required action, owner, due date, authority, classification, public-safe status, correction path, and closeout.
20.22.8(e) The controlling rule shall be that lessons have value only when they reach the owner able and authorized to act.
20.22.9 Nexus Universe After-Action Records and Public-Safe Summaries. 20.22.9(a) GCRI Canada shall maintain Nexus Universe after-action records and may issue public-safe summaries where appropriate.
20.22.9(b) After-action records shall identify activity, date, scope, owner, custodian, participants, roles, Public Authority capacity classifications, sponsor and provider roles, host roles, community roles, capital-reader roles, materials used, systems used, data used, AI used, incidents, issues, lessons, corrective actions, renewal actions, affected interfaces, and closeout.
20.22.9(c) Public-safe summaries may describe learning, improvements, corrections, and renewal actions without exposing confidential, personal, Public Authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, community-protected, Indigenous, Local, Territorial, Cultural, Environmental, or Protected Knowledge materials.
20.22.9(d) Public-safe summaries shall include limitations and boundary language to prevent certification, recognition, finance-readiness, public authority approval, procurement advantage, provider preference, sponsor validation, public warning, emergency command, or execution implication.
20.22.9(e) The controlling rule shall be that Nexus Universe after-action records must preserve learning while public summaries must preserve safety and role clarity.
20.22.10 Nexus Universe Learning Assurance. 20.22.10(a) GCRI Canada shall conduct Nexus Universe Learning Assurance.
20.22.10(b) Assurance shall review whether Nexus Universe lessons were captured, classified, routed, assigned, corrected, integrated, and closed.
20.22.10(c) Assurance shall identify unrecorded lessons, unresolved after-action findings, lessons not routed, lessons routed to the wrong authority, repeated operational issues, boundary misunderstandings, public claims misuse, sponsor or provider overclaim, Public Authority confusion, finance overclaim, community safeguard gaps, and technical defects not corrected.
20.22.10(d) Findings may require corrective action, renewal action, training, public-safe correction, controlled notice, interface correction, legal review, technical patching, Board / committee reporting, or future Nexus Universe design changes.
20.22.10(e) The controlling rule shall be that Nexus Universe learning must be assured because complex convenings create lessons across multiple institutional layers.
20.23 Nexus Interface Assurance
20.23.1 Assurance of Interfaces With GCRI US. 20.23.1(a) GCRI Canada shall assure its interfaces with GCRI US to preserve legal separateness, Canadian legal localization, public-good alignment, evidence integrity, methods interoperability, shared doctrine discipline, records boundaries, data boundaries, IP boundaries, public claims precision, and correction coordination.
20.23.1(b) Assurance shall review whether shared methods, shared ontology, shared public-good software, shared technical baselines, shared records, shared Directors or advisors where lawful, shared publications, shared events, shared rooms, or shared public authority learning are properly documented, scoped, classified, and bounded.
20.23.1(c) Assurance shall identify merger risk, agency risk, shared treasury risk, shared liability risk, shared employer risk, authority confusion, public claims confusion, data custody confusion, or correction-path ambiguity.
20.23.1(d) Findings may require interface record correction, legal-separateness language, data agreement update, public claims correction, role-language correction, divergence log, equivalence note, controlled notice, or Board reporting.
20.23.1(e) The controlling rule shall be that GCRI Canada and GCRI US may align in mission and methods without legal fusion.
20.23.2 Assurance of Interfaces With GRF. 20.23.2(a) GCRI Canada shall assure its interfaces with The Global Risks Forum (GRF) to preserve role separation between GCRI Canada’s evidence, methods, observability, ontology, public-good R&D, public-good software, and technical baseline function and GRF’s registry, recognition, standing, maturity records, claims discipline, stakeholder formation, public-safe reporting, and public-facing legitimacy function.
20.23.2(b) Assurance shall review whether GCRI Canada inputs to GRF are properly scoped, evidence-supported, classified, limitation-aware, corrected where needed, and not represented as GRF outputs unless GRF has acted through proper authority.
20.23.2(c) Assurance shall identify recognition overclaim, maturity-record overclaim, registry-status implication, public-facing legitimacy implication, claims-discipline confusion, and GRF authority substitution.
20.23.2(d) Findings may require GRF interface correction, public claims correction, controlled vocabulary update, public-safe notice, controlled notice, or correction of downstream dependencies.
20.23.2(e) The controlling rule shall be that GCRI Canada may support GRF truth inputs but shall not create GRF public status.
20.23.3 Assurance of Interfaces With GRA. 20.23.3(a) GCRI Canada shall assure its interfaces with The Global Risks Alliance (GRA) to preserve role separation between GCRI Canada’s evidence and methods function and GRA’s finance-readiness, capital readability, Proof Pack discipline, insurance-readiness, capital-reader rooms, RNFD, NFD, UNFSD, and regulated-perimeter discipline.
20.23.3(b) Assurance shall review whether GCRI Canada inputs to GRA are evidence-bounded, source-valid, limitation-aware, finance-safe, properly classified, and not represented as finance-readiness unless GRA separately acts through proper authority.
20.23.3(c) Assurance shall identify finance-readiness overclaim, capital-reader overreliance, insurance-readiness implication, investment advice implication, solicitation implication, rating implication, guarantee implication, public finance implication, and GRA role collapse.
20.23.3(d) Findings may require GRA routing, finance-boundary correction, public claims correction, room redesign, legal review, controlled notice, public-safe notice, or Board / committee reporting.
20.23.3(e) The controlling rule shall be that GCRI Canada may provide evidence inputs to finance-readable structures without becoming a finance actor.
20.23.4 Assurance of Interfaces With Nexus Standards / Protocol Authority. 20.23.4(a) GCRI Canada shall assure its interfaces with Nexus Standards / Protocol Authority to preserve role separation between GCRI Canada’s methods, technical truth, public-good software, Open Technical Baselines, and evidence functions and the Protocol Authority’s protocol discipline, conformance logic, role keys, smart licenses, proof receipts, entitlement states, anchoring discipline, and technical validity surfaces.
20.23.4(b) Assurance shall review whether GCRI Canada technical inputs are properly versioned, licensed, reviewed, security-checked, public-safe, and not represented as protocol conformance, entitlement state, certification, smart-license authority, or proof-receipt authority unless the competent authority has acted.
20.23.4(c) Assurance shall identify protocol overclaim, certification drift, proof-receipt misuse, smart-license overmeaning, conformance implication, entitlement-state confusion, and technical validity overclaim.
20.23.4(d) Findings may require protocol interface correction, technical release correction, controlled vocabulary update, public claims correction, proof-receipt correction, legal review, or technical assurance follow-up.
20.23.4(e) The controlling rule shall be that technical baselines can support protocol discipline without becoming protocol authority by default.
20.23.5 Assurance of Interfaces With Nexus Network, Nexus Universe, Nexus Observatory, Nexus Truth Engine, Nexus Rails, Nexus Grid, Nexus Academy, and Nexus Risk Management. 20.23.5(a) GCRI Canada shall assure its interfaces with Nexus Network, Nexus Universe, Nexus Observatory, Nexus Truth Engine, Nexus Rails, Nexus Grid, Nexus Academy, and Nexus Risk Management.
20.23.5(b) Assurance shall review whether evidence, methods, observability outputs, Truth Engine methods, Academy materials, Rails interfaces, Grid maturity-related inputs, risk management inputs, public-safe summaries, dashboards, maps, datasets, public-good software, and technical baselines are properly scoped, classified, reviewed, versioned, corrected, and role-bounded.
20.23.5(c) Assurance shall identify public claims drift, public authority confusion, finance overclaim, Grid maturity overclaim, Rails protocol overclaim, Academy certification overclaim, Observatory public warning confusion, Truth Engine authority overclaim, and Nexus Universe execution confusion.
20.23.5(d) Findings may require interface record correction, role-language correction, public-safe notice, controlled notice, training update, technical update, or Board / committee reporting.
20.23.5(e) The controlling rule shall be that Nexus functions may interoperate through common rails without dissolving GCRI Canada’s role boundaries.
20.23.6 Assurance of Interfaces With Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, Nexus Competence Cells, National Companies, Project SPVs, Qualified Providers, Hosts, Sponsors, Universities, Public Authorities, Communities, and Capital Readers. 20.23.6(a) GCRI Canada shall assure interfaces with Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, Nexus Competence Cells, National Companies, Project SPVs, qualified providers, hosts, sponsors, donors, funders, universities, Public Authorities, communities, civil society, media, and capital readers where GCRI Canada’s records, methods, evidence, technical assets, public-safe outputs, rooms, data, public claims, or public authority learning are involved.
20.23.6(b) Assurance shall review whether each interface preserves legal separateness, authority boundaries, data controls, public claims controls, finance boundaries, procurement neutrality, sponsor non-control, provider neutrality, community safeguards, protected knowledge controls, and correction paths.
20.23.6(c) Assurance shall identify overclaim that GCRI Canada evidence, participation, technical baselines, dashboards, maps, or public authority proximity create public authority approval, finance-readiness, procurement advantage, certification, recognition, provider status, sponsor validation, National Company status, Project SPV approval, or execution authorization.
20.23.6(d) Findings may require contract correction, interface correction, public claims correction, access restriction, controlled notice, public-safe notice, legal review, participant correction, or relationship remedy.
20.23.6(e) The controlling rule shall be that broad Nexus participation must remain role-specific, lawful, and correctionable.
20.23.7 Assurance of Shared Records Without Shared Liability. 20.23.7(a) GCRI Canada shall assure shared records without shared liability.
20.23.7(b) Shared records shall identify owner, custodian, authority, classification, access class, public-safe status, retention, correction path, publication status, liability boundary, entity boundary, and permitted use.
20.23.7(c) Assurance shall review whether shared records are used as interoperability tools rather than as evidence of merger, agency, partnership, joint venture, parent-subsidiary status, shared treasury, shared employer, shared liability, public authority delegation, finance authority, certification authority, or execution authority.
20.23.7(d) Assurance shall identify ownerless records, unclear custody, conflicting versions, inconsistent public claims, broken correction paths, access overreach, and downstream dependency risk.
20.23.7(e) The controlling rule shall be that shared records may connect institutions but shall not fuse legal responsibility by default.
20.23.8 Assurance of Role Separation, Boundary Language, Data Controls, Public Claims, Correction Signals, and Closeout. 20.23.8(a) Nexus Interface Assurance shall review role separation, boundary language, data controls, public claims, correction signals, closeout, and archive.
20.23.8(b) Role separation review shall confirm that each actor’s function, authority, limits, obligations, and public claims rights are recorded and understood.
20.23.8(c) Boundary language review shall confirm that materials preserve non-execution, no-public-authority-by-default, no-finance-readiness-by-default, no-certification-by-default, no-provider-preference, no-sponsor-control, no-procurement-advantage, and no-shared-liability where appropriate.
20.23.8(d) Data controls review shall confirm that data sharing, Public Authority Data, protected knowledge, AI use, cross-border transfers, retention, deletion, and publication are governed by proper authority and safeguards.
20.23.8(e) Correction signals and closeout review shall confirm that corrections, supersessions, withdrawals, retractions, access revocations, role changes, and relationship closeouts are communicated to affected interface actors where required.
20.23.8(f) The controlling rule shall be that interfaces must be assured from entry through correction and closeout.
20.23.9 Interface Assurance Findings and Corrective Actions. 20.23.9(a) Interface Assurance findings shall be recorded, classified, assigned, corrected, and verified.
20.23.9(b) Findings may include role confusion, boundary language gap, data control gap, public claims overreach, public authority reference issue, finance-boundary issue, shared-record issue, correction-path issue, legal-separateness issue, sponsor influence, provider preference, community safeguard gap, or protected knowledge concern.
20.23.9(c) Corrective actions may include interface agreement amendment, role-language correction, public claims correction, data control update, access restriction, public-safe notice, controlled notice, divergence log, equivalence note, legal review, training, relationship restriction, or Board / committee reporting.
20.23.9(d) Interface findings shall be linked to affected records, affected entities, affected public materials, affected data, affected technical assets, and affected downstream dependencies.
20.23.9(e) The controlling rule shall be that interface defects must be corrected where institutional boundaries meet.
20.23.10 Nexus Interface Assurance Register. 20.23.10(a) GCRI Canada shall maintain a Nexus Interface Assurance Register.
20.23.10(b) The Register shall identify interface, actor, owner, custodian, purpose, authority, records, data flows, technical flows, funding flows where any, public claims, Public Authority references, finance-sensitive references, sponsor or provider roles, legal-separateness language, boundary language, correction path, assurance findings, corrective actions, closeout, and archive.
20.23.10(c) The Register shall link to contracts, data agreements, public authority records, GRA records, GRF records, Protocol Authority records, Nexus records, risk records, issue records, control records, corrective action records, public claims records, and Board or committee records where applicable.
20.23.10(d) The Register shall be reviewed periodically for stale interfaces, unresolved findings, public claims drift, data custody gaps, and role-confusion risk.
20.23.10(e) The controlling rule shall be that Nexus interfaces must be registered because interoperability creates recurring boundary risk.
20.24 External Review, Independent Review, and Expert Challenge
20.24.1 External Review Where Appropriate for Public Trust, Technical Complexity, Legal Risk, Research Integrity, Public Authority Sensitivity, Community Sensitivity, or Major Assurance Findings. 20.24.1(a) GCRI Canada may obtain external review where appropriate for public trust, technical complexity, legal risk, research integrity, Public Authority sensitivity, community sensitivity, protected knowledge sensitivity, data risk, AI risk, cybersecurity risk, finance-boundary risk, major assurance findings, major incidents, major public claims, major publications, major technical releases, or major Nexus interfaces.
20.24.1(b) External review may be independent, expert, peer, legal, technical, research, data, AI, cybersecurity, privacy, safeguards, community, Public Authority boundary, finance-boundary, or other specialized review.
20.24.1(c) External review shall be scoped, classified, conflict-reviewed, confidentiality-bound, role-bounded, and records-valid.
20.24.1(d) External review shall not create certification, public authority approval, finance-readiness, provider preference, sponsor validation, procurement approval, rating, guarantee, or external assurance status unless separately authorized and properly bounded.
20.24.1(e) The controlling rule shall be that external challenge may strengthen public trust without transferring GCRI Canada’s authority or responsibility.
20.24.2 Independent Legal Review. 20.24.2(a) Independent legal review may be obtained where matters involve corporate law, tax status, charitable-status compatibility where applicable, privacy, data protection, AI law, cybersecurity law, sanctions, export controls, competition law, procurement-law safety, professional boundaries, employment, contracts, grants, IP, publications, Public Authority interfaces, finance-regulated perimeter, international collaboration, entity boundaries, insurance, indemnification, disputes, or legal holds.
20.24.2(b) Independent legal review shall identify scope, jurisdiction, facts reviewed, assumptions, legal issues, risks, options, required actions, prohibited actions, residual risk, privilege status, and implementation requirements.
20.24.2(c) Legal review shall be obtained from persons with appropriate independence, competence, jurisdictional knowledge, and conflict clearance.
20.24.2(d) Legal review findings shall be routed to the appropriate owner, committee, Board, register, corrective action plan, or policy renewal process.
20.24.2(e) The controlling rule shall be that independent legal review supports lawful restraint, not operational acceleration beyond authority.
20.24.3 Independent Technical Review. 20.24.3(a) Independent technical review may be obtained for public-good software, Open Technical Baselines, reference architectures, APIs, schemas, datasets, models, benchmarks, evaluation harnesses, dashboards, maps, compute environments, repositories, secure releases, AI-RAN systems, DePIN systems, cyber tools, geospatial systems, digital twins, sensor systems, satellite systems, drones, robotics, autonomous systems, quantum-relevant systems, and other technical assets.
20.24.3(b) Technical review may assess correctness, security, reliability, interoperability, scalability, privacy, public-safe status, dependency risk, controlled technology risk, export-control risk, documentation, limitations, and misuse potential.
20.24.3(c) Reviewers shall be conflict-screened, confidentiality-bound, access-limited, and restricted from using reviewed materials for unauthorized purposes.
20.24.3(d) Technical review findings may require patching, redesign, release hold, secure release update, public-safe limitation update, documentation update, vulnerability notice, or withdrawal.
20.24.3(e) The controlling rule shall be that technical review strengthens trust only when technical confidence remains bounded by scope and evidence.
20.24.4 Independent Research Review. 20.24.4(a) Independent research review may be obtained for research design, methodology, evidence interpretation, ethics, human-subjects concerns, data quality, peer review, reproducibility, conflicts, publication readiness, community safeguards, protected knowledge, AI-assisted research, and public-safe communication.
20.24.4(b) Research review shall assess whether research is evidence-based, ethically appropriate, methodologically sound, limitation-aware, conflict-managed, reproducible where appropriate and lawful, and correctionable.
20.24.4(c) Independent research reviewers shall disclose conflicts, protect confidentiality, respect participant protections, respect protected knowledge protocols, and avoid unauthorized reuse.
20.24.4(d) Findings may require protocol revision, ethics review, data correction, analysis revision, publication correction, limitation update, withdrawal, retraction, community consultation, or Board / committee reporting.
20.24.4(e) The controlling rule shall be that research challenge protects truth and affected persons before public claims are made.
20.24.5 Independent Data, AI, Cybersecurity, or Privacy Review. 20.24.5(a) Independent data, AI, cybersecurity, or privacy review may be obtained where activities involve personal information, health-sensitive data, Public Authority Data, rights-bearing data, community-protected data, protected knowledge, cross-border transfers, sovereign data, AI systems, model use, embeddings, retrieval, inference, cybersecurity controls, repositories, APIs, dashboards, maps, datasets, vendors, or incident response.
20.24.5(b) Review may assess lawful basis, purpose limitation, minimization, classification, access, retention, deletion, re-identification risk, AI training restrictions, model risk, bias risk, data leakage, prompt leakage, security controls, vulnerabilities, breach readiness, vendor terms, and public-safe release.
20.24.5(c) Reviewers shall be access-limited, confidentiality-bound, conflict-cleared, and subject to data, security, AI-use, and protected knowledge terms.
20.24.5(d) Findings may require data deletion, access restriction, AI restriction, model restriction, vendor amendment, security remediation, breach notice, public-safe correction, or legal review.
20.24.5(e) The controlling rule shall be that independent review of data, AI, cybersecurity, and privacy protects rights and trust where internal confidence is insufficient.
20.24.6 Independent Public Authority Boundary Review. 20.24.6(a) Independent Public Authority boundary review may be obtained where GCRI Canada materials, rooms, dashboards, maps, public authority learning, Public Authority Data, Public Authority references, public finance readers, emergency-management contexts, public health contexts, infrastructure contexts, regulatory contexts, or procurement-sensitive contexts create elevated risk.
20.24.6(b) Review shall assess whether materials or conduct could imply endorsement, adoption, public warning, emergency command, regulatory approval, procurement approval, funding approval, public finance approval, official guidance, sovereign obligation, or public-private partnership.
20.24.6(c) Review shall examine capacity classifications, reference approvals, boundary language, room rules, public-safe status, public claims, and correction paths.
20.24.6(d) Findings may require reference correction, Public Authority clarification, public-safe notice, controlled notice, room redesign, legal review, public claims revision, or withdrawal.
20.24.6(e) The controlling rule shall be that independent review may be necessary where public power could be inferred from proximity.
20.24.7 Independent Finance-Boundary Review. 20.24.7(a) Independent finance-boundary review may be obtained where GCRI Canada materials, GRA interfaces, Proof Pack inputs, capital-reader rooms, RNFD / NFD / UNFSD support, public finance readers, insurance-readiness references, token / blockchain / DLT / DePIN activities, proof receipts, public claims, or project-related materials create finance-sensitive risk.
20.24.7(b) Review shall assess whether materials or conduct could imply investment advice, securities offering, solicitation, brokerage, finder activity, placement activity, lending, guarantee, insurance approval, underwriting, rating, public finance approval, capital commitment, token issuance, custody, payment intermediation, or market operation.
20.24.7(c) Review shall examine audience, language, context, disclaimers, access controls, GRA routing, public claims, sponsor or provider materials, Public Authority interfaces, and reliance risk.
20.24.7(d) Findings may require GRA routing, finance-safe language, legal review, access restriction, room redesign, public-safe correction, controlled notice, withdrawal, or Board reporting.
20.24.7(e) The controlling rule shall be that finance-boundary review protects technical evidence from becoming regulated financial reliance.
20.24.8 Independent Safeguards or Community Review. 20.24.8(a) Independent safeguards or community review may be obtained where activities affect communities, Indigenous knowledge holders, local knowledge holders, territorial knowledge holders, cultural knowledge holders, environmental knowledge holders, vulnerable persons, protected persons, confidential sources, sensitive sites, public health vulnerabilities, ecological vulnerabilities, or protected knowledge.
20.24.8(b) Review may assess consent and non-consent pathways where applicable, community context, protected knowledge protocols, accessibility, language access, public-safe mapping, re-identification risk, group harm, cultural harm, ecological harm, grievance pathways, remedy pathways, and non-retaliation.
20.24.8(c) Reviewers shall be selected with attention to independence, competence, cultural safety, lived context, conflicts, confidentiality, and protection of knowledge rights.
20.24.8(d) Findings may require community consultation, protected knowledge restriction, redaction, aggregation, publication correction, withdrawal, access restriction, grievance remedy, public-safe notice, controlled notice, or Board / committee reporting.
20.24.8(e) The controlling rule shall be that affected communities and protected knowledge holders may reveal risks that institutional review cannot see alone.
20.24.9 Expert Challenge as Strengthening Mechanism. 20.24.9(a) Expert challenge shall be treated as a strengthening mechanism.
20.24.9(b) Expert challenge may be used to test assumptions, identify blind spots, challenge evidence quality, challenge method design, test technical claims, examine public-safe framing, review legal boundaries, assess Public Authority implications, assess finance-boundary implications, and improve safeguards.
20.24.9(c) Expert challenge shall permit dissent, minority views, uncertainty notes, reviewer conditions, unresolved disputes, and limitation statements to be recorded.
20.24.9(d) Expert challenge shall not be suppressed because it is inconvenient, slows publication, weakens a preferred narrative, contradicts sponsor or provider interests, complicates public claims, or requires correction.
20.24.9(e) The controlling rule shall be that challenge strengthens institutional truth where it is recorded, respected, and routed to correction.
20.24.10 External Review Records, Conditions, Findings, Limitations, and Follow-Up. 20.24.10(a) GCRI Canada shall maintain external review records.
20.24.10(b) Records shall identify review title, purpose, scope, reviewer, independence review, conflict review, confidentiality terms, data access, AI-use limits, protected knowledge limits, Public Authority sensitivity, finance sensitivity, materials reviewed, methodology, assumptions, findings, limitations, dissent, conditions, recommendations, corrective actions, follow-up, public-safe summary status, and closeout.
20.24.10(c) External review findings shall be linked to applicable Risk Register, Issue Register, Control Register, Corrective Action Register, Renewal Register, Assurance records, Publication Register, Data Register, AI Register, Cybersecurity Register, Public Authority Register, Finance Boundary Register, Community Safeguards Register, and Board or committee records.
20.24.10(d) Public references to external review shall not overstate scope, independence, assurance level, certification, public authority meaning, finance meaning, or endorsement.
20.24.10(e) The controlling rule shall be that external review improves integrity only when its limits and follow-up are recorded.
20.25 Complaints, Grievances, Challenge, and Whistleblower Pathways
20.25.1 Complaint Pathway for Participants, Staff, Fellows, Advisors, Contributors, Public Authorities, Communities, Sponsors, Providers, Hosts, Partners, and Public Stakeholders Where Appropriate. 20.25.1(a) GCRI Canada shall maintain complaint pathways for participants, staff, contractors, volunteers, fellows, advisors, contributors, maintainers, committee participants, council participants, Public Authorities, communities, sponsors, donors, funders, providers, hosts, universities, partners, capital readers, public stakeholders, and other affected persons where appropriate.
20.25.1(b) Complaint pathways may address conduct, access, confidentiality, data handling, AI use, cybersecurity, public claims, public authority references, finance-boundary claims, sponsor conduct, provider conduct, community safeguards, protected knowledge, publications, technical releases, governance process, or other institutional concerns.
20.25.1(c) Complaint pathways shall identify intake channels, eligibility, scope, classification, confidentiality, non-retaliation, triage, response timeline, escalation, investigation, remedy, appeal where applicable, and closeout.
20.25.1(d) Complaint pathways shall be accessible, role-appropriate, records-valid, and protective of privacy, confidentiality, legal privilege, cybersecurity, Public Authority sensitivity, finance sensitivity, and protected knowledge.
20.25.1(e) The controlling rule shall be that persons affected by GCRI Canada’s work must have a pathway to raise concerns that the institution can hear, record, and correct.
20.25.2 Grievance Pathway for Community, Protected Knowledge, Participation, Conduct, Data Rights, Research, Publication, and Public-Safe Concerns. 20.25.2(a) GCRI Canada shall maintain grievance pathways for community, protected knowledge, participation, conduct, data rights, research, publication, public-safe, accessibility, inclusion, non-retaliation, and safeguard concerns.
20.25.2(b) Community and protected knowledge grievances may concern extraction, misdescription, exposure, unsafe mapping, re-identification, cultural harm, ecological harm, protected person exposure, lack of consultation, inaccessible materials, translation issues, public-safe publication concerns, or misuse of Indigenous, Local, Territorial, Cultural, Environmental, or Protected Knowledge.
20.25.2(c) Data rights grievances may concern access, correction, deletion, restriction, objection, withdrawal where applicable, breach, unauthorized AI use, unauthorized sharing, or public release.
20.25.2(d) Research and publication grievances may concern ethics, consent, authorship, attribution, conflicts, unsupported claims, public authority overclaim, finance overclaim, sponsor influence, provider influence, protected knowledge exposure, or failure to correct.
20.25.2(e) The controlling rule shall be that grievances are not reputational problems; they are safeguard signals requiring respectful review and correction where warranted.
20.25.3 Challenge Pathway for Evidence, Methods, Publications, Dashboards, Maps, Technical Claims, Public Authority References, Finance-Boundary Claims, and Nexus Interface Claims. 20.25.3(a) GCRI Canada shall maintain a challenge pathway for evidence, methods, publications, dashboards, maps, datasets, software releases, technical claims, impact claims, Public Authority references, finance-boundary claims, sponsor references, provider references, controlled vocabulary use, public-safe summaries, and Nexus interface claims.
20.25.3(b) A challenge may assert that a record, method, claim, visualization, source, version, public authority reference, finance reference, maturity statement, technical statement, or boundary statement is inaccurate, unsupported, stale, unsafe, misleading, overbroad, misclassified, or outside authority.
20.25.3(c) Challenge intake shall identify challenged material, challenged claim, basis for challenge, evidence provided, affected audience, urgency, public-safe concern, and requested correction where known.
20.25.3(d) Challenges shall be reviewed by appropriate evidence, method, publication, legal, technical, data, AI, cybersecurity, Public Authority, finance-boundary, safeguard, or governance owners according to domain.
20.25.3(e) The controlling rule shall be that challenge pathways strengthen validity-by-record because public-good truth must remain contestable and correctable.
20.25.4 Whistleblower Pathway for Good-Faith Reports of Misconduct, Fraud, Data Misuse, Cyber Risk, Public Authority Misuse, Finance Overclaim, Sponsor Control, Provider Capture, Retaliation, or Legal Noncompliance. 20.25.4(a) GCRI Canada shall maintain a whistleblower pathway for good-faith reports of misconduct, fraud, theft, bribery, corruption, data misuse, AI misuse, cybersecurity risk, privacy breach, Public Authority misuse, finance overclaim, sponsor control, provider capture, procurement steering, private inurement, protected knowledge misuse, retaliation, harassment, discrimination, conflicts breach, records falsification, legal noncompliance, sanctions breach, export-control breach, or other serious wrongdoing.
20.25.4(b) The whistleblower pathway shall permit reporting by employees, contractors, volunteers, fellows, advisors, contributors, Directors, Officers, committee participants, council participants, providers, sponsors, hosts, Public Authorities, communities, partners, and other affected persons where appropriate.
20.25.4(c) The pathway shall provide confidential reporting where appropriate, escalation outside the implicated reporting line, conflict management, legal review where required, records preservation, non-retaliation, investigation, corrective action, and Board or committee reporting where material.
20.25.4(d) Whistleblower reports shall be triaged for immediate Stop-the-Line, legal hold, investigation, access restriction, breach response, public-safe notice, controlled notice, or external reporting where required.
20.25.4(e) The controlling rule shall be that serious wrongdoing must have a protected pathway to reach institutional authority before harm is normalized.
20.25.5 Non-Retaliation. 20.25.5(a) GCRI Canada shall prohibit retaliation against any person who in good faith makes a complaint, grievance, challenge, whistleblower report, Stop-the-Line request, correction request, safeguard concern, data rights request, public-safe concern, or legal compliance concern.
20.25.5(b) Retaliation includes dismissal, demotion, removal, suspension, role reduction, contract termination, access restriction, exclusion, harassment, intimidation, threats, reputational attack, funding penalty, authorship penalty, publication penalty, public claims retaliation, sponsor pressure, provider pressure, community pressure, or other adverse treatment because of protected reporting.
20.25.5(c) Non-retaliation protection shall apply even where the concern is not ultimately substantiated, provided the concern was raised in good faith.
20.25.5(d) Retaliation shall be treated as a serious conduct, governance, workforce, participation, compliance, or contractual incident and may result in discipline, termination, contract remedy, legal review, public-safe clarification, or Board reporting.
20.25.5(e) The controlling rule shall be that correction pathways fail if people fear using them.
20.25.6 Confidentiality and Protection of Reporter Where Appropriate. 20.25.6(a) GCRI Canada shall protect reporter confidentiality where appropriate and lawful.
20.25.6(b) Reporter identity, complaint details, grievance materials, whistleblower reports, supporting evidence, communications, and investigation records shall be handled according to confidentiality, privacy, legal privilege, cybersecurity, Public Authority sensitivity, finance sensitivity, employment sensitivity, protected knowledge, and need-to-know requirements.
20.25.6(c) Confidentiality shall not be promised absolutely where disclosure is required by law, due process, investigation needs, Public Authority obligation, legal obligation, safety, or rights of affected persons, but disclosure shall be limited to what is necessary.
20.25.6(d) Protection may include anonymous reporting where appropriate, restricted access, conflict-screened investigators, anti-retaliation measures, interim access controls, role separation, communication controls, and support for affected persons.
20.25.6(e) The controlling rule shall be that reporting systems must protect the reporter while preserving fair, lawful, and effective review.
20.25.7 Intake, Triage, Investigation, Response, Correction, Remedy, Appeal Where Applicable, and Closeout. 20.25.7(a) Complaints, grievances, challenges, and whistleblower reports shall be handled through intake, triage, classification, conflict review, interim control where needed, investigation or review, response, correction, remedy, appeal where applicable, and closeout.
20.25.7(b) Intake shall record reporter where known, date, concern type, affected materials, affected persons, affected communities, affected Public Authorities, affected systems, urgency, confidentiality request, non-retaliation needs, and immediate protection needs.
20.25.7(c) Triage shall determine severity, domain, owner, required reviewers, legal review need, Stop-the-Line need, incident status, data breach status, cybersecurity status, Public Authority status, finance-boundary status, protected knowledge status, and public-safe notice need.
20.25.7(d) Investigation or review shall be fair, proportionate, timely, impartial where required, evidence-based, confidential, non-retaliatory, and protective of affected persons and sensitive information.
20.25.7(e) Response shall inform the reporter where appropriate of receipt, process, outcome category, corrective action where disclosable, and appeal or further review path where applicable.
20.25.7(f) Correction and remedy may include record correction, publication correction, public-safe notice, controlled notice, withdrawal, retraction, access restriction, data deletion, policy update, training, apology where appropriate, grievance remedy, participant discipline, contract remedy, legal review, or Board action.
20.25.7(g) Closeout shall record findings, actions taken, unresolved issues, confidentiality limits, retaliation review, appeal status, correction status, and archive.
20.25.7(h) The controlling rule shall be that concerns are not closed until they are reviewed, responded to, corrected where warranted, and recorded.
20.25.8 Bad-Faith, Harassing, or Abusive Complaints. 20.25.8(a) GCRI Canada may address bad-faith, harassing, knowingly false, malicious, abusive, coercive, discriminatory, retaliatory, duplicative, or vexatious complaints, grievances, challenges, or reports.
20.25.8(b) A concern shall not be treated as bad-faith merely because it is mistaken, unsubstantiated, inconvenient, critical, strongly worded, repeated due to lack of response, or embarrassing to GCRI Canada.
20.25.8(c) Bad-faith or abusive use may include knowingly false allegations, harassment of participants, intimidation of staff, misuse to suppress publication, misuse to delay correction, sponsor-driven pressure, provider-driven pressure, procurement manipulation, finance-sensitive manipulation, public authority pressure, or retaliation disguised as complaint.
20.25.8(d) Response may include clarification, process limits, communication boundaries, access restriction, conduct action, contract remedy, legal review, or termination of abusive participation where appropriate.
20.25.8(e) The controlling rule shall be that pathways must remain open to good-faith challenge while protected from weaponized misuse.
20.25.9 Complaint, Grievance, Challenge, and Whistleblower Register. 20.25.9(a) GCRI Canada shall maintain a Complaint, Grievance, Challenge, and Whistleblower Register.
20.25.9(b) The Register shall identify report type, date, reporter status where known, confidentiality status, affected domain, affected records, affected persons, affected communities, affected Public Authorities, affected systems, affected public materials, severity, owner, custodian, triage outcome, interim controls, investigation status, findings, corrective actions, remedies, retaliation review, appeal status, closeout, and archive.
20.25.9(c) The Register shall link to the Risk Register, Issue Register, Control Register, Incident Register, Corrective Action Register, Lessons Learned Register, Legal Review Register, Data Register, AI Register, Cybersecurity Register, Public Authority Register, Finance Boundary Register, Community Safeguards Register, Publication Register, Participation Register, and Board or committee records where applicable.
20.25.9(d) Access shall be controlled according to privacy, confidentiality, legal privilege, employment sensitivity, cybersecurity, Public Authority sensitivity, finance sensitivity, community safeguards, protected knowledge, non-retaliation, and need-to-know.
20.25.9(e) The controlling rule shall be that complaints, grievances, challenges, and whistleblower reports must be registered because institutional courage requires institutional memory.
20.25.10 Pathway Assurance. 20.25.10(a) GCRI Canada shall conduct assurance of complaint, grievance, challenge, and whistleblower pathways.
20.25.10(b) Pathway Assurance shall review accessibility, timeliness, confidentiality, non-retaliation, triage quality, investigation quality, response quality, corrective action quality, remedy quality, appeal handling where applicable, register completeness, and closeout evidence.
20.25.10(c) Assurance shall identify underreporting, retaliation concerns, delayed responses, unresolved grievances, repeated complaints, weak correction, inaccessible processes, community distrust, protected knowledge concerns, public claims challenge patterns, and whistleblower process weaknesses.
20.25.10(d) Findings may require pathway redesign, training, access changes, independent review, policy update, public-safe clarification, community consultation, Board reporting, or corrective action.
20.25.10(e) The controlling rule shall be that complaint and challenge pathways must be assured because a correctionable institution must be reachable, responsive, and safe to challenge.
20.26 Public Trust Review
20.26.1 Public Trust as Institutional Asset. 20.26.1(a) Public trust shall be treated as a material institutional asset of GCRI Canada and as a necessary condition for lawful, durable, public-benefit evidence, methods, observability, ontology, public-good R&D, public-good software, technical baseline, public-safe publication, public authority learning, and Nexus-compatible work.
20.26.1(b) Public trust shall be protected through accuracy, records validity, correctionability, controlled vocabulary, non-execution, public-safe transparency, lawful protection of sensitive information, Public Authority boundary discipline, finance-boundary discipline, provider neutrality, sponsor non-control, community safeguards, cybersecurity, privacy, legal separateness, and clear role language.
20.26.1(c) Public trust shall not be treated as reputation management, narrative control, sponsor visibility, media strategy, public relations advantage, institutional prestige, or avoidance of criticism. Public trust shall be earned through truthfulness, restraint, correction, transparency with protection, and disciplined boundaries.
20.26.1(d) GCRI Canada shall recognize that public trust may be harmed by both concealment and over-disclosure, by both silence and hype, by both under-claiming necessary corrections and over-claiming institutional authority, and by both technical opacity and unsafe technical exposure.
20.26.1(e) The controlling rule shall be that public trust is preserved by trustworthy conduct, not by trust language alone.
20.26.2 Public Trust Review for High-Visibility Publications, Public Authority Interfaces, Sponsor Announcements, Provider Demonstrations, Nexus Universe Activities, Dashboards, Maps, Public-Safe Reports, and Public Controversies. 20.26.2(a) GCRI Canada shall conduct Public Trust Review where appropriate for high-visibility publications, Public Authority interfaces, sponsor announcements, donor announcements, funder announcements, provider demonstrations, host announcements, Nexus Universe activities, public-safe reports, dashboards, maps, datasets, technical releases, media statements, public campaigns, public authority learning materials, capital-reader-visible materials, community-facing materials, and public controversies.
20.26.2(b) Public Trust Review shall assess how a reasonable public reader, Public Authority participant, community member, sponsor, provider, capital reader, media actor, affected person, or Nexus participant may understand the relevant material, event, statement, interface, or output.
20.26.2(c) Public Trust Review shall be heightened where GCRI Canada’s name, marks, technical baselines, public-good software, Observatory outputs, Truth Engine outputs, public authority references, sponsor references, provider references, community references, or Nexus references may create public meaning beyond recorded authority.
20.26.2(d) Public Trust Review may be required before release, during active public attention, after controversy, after incident, after public correction, after Public Authority clarification, after media misdescription, or after sponsor or provider amplification.
20.26.2(e) The controlling rule shall be that high-visibility activity must be reviewed for public meaning before public meaning outruns institutional authority.
20.26.3 Public Trust Risks: Misdescription, Overclaim, Capture, Secrecy, Over-Disclosure, Public Authority Confusion, Finance Overclaim, Privacy Harm, Community Harm, Cyber Harm, Hype, and Uncorrected Error. 20.26.3(a) Public Trust Risks include misdescription, unsupported claim, inflated claim, stale claim, capture perception, sponsor control perception, provider preference perception, donor influence perception, secrecy perception, over-disclosure, unsafe transparency, Public Authority confusion, public warning confusion, emergency command confusion, finance overclaim, certification implication, procurement implication, privacy harm, cybersecurity harm, community harm, protected knowledge harm, misleading visualization, technical hype, narrative acceleration, and uncorrected error.
20.26.3(b) Misdescription includes inaccurate statements about GCRI Canada’s legal status, public-benefit purpose, non-execution posture, relationship with GCRI US, GRF, GRA, Protocol Authority, Nexus entities, Public Authorities, sponsors, providers, hosts, National Companies, Project SPVs, communities, or capital actors.
20.26.3(c) Capture risk includes any reasonable perception that a sponsor, donor, funder, provider, host, Public Authority, capital reader, founder, technical contributor, or partner controls evidence, methods, publications, corrections, public authority access, technical baselines, institutional priorities, or public claims.
20.26.3(d) Hype includes the presentation of early-stage, partial, untested, pilot, simulation, prototype, internal, controlled, limited, or unassured work as proven, validated, mature, official, adopted, finance-ready, certified, public authority-approved, market-ready, or execution-ready.
20.26.3(e) The controlling rule shall be that public trust risks arise not only from false statements, but also from missing limits, missing corrections, improper tone, unsafe silence, or ambiguous context.
20.26.4 Public Trust Review Shall Balance Transparency With Lawful Protection. 20.26.4(a) Public Trust Review shall balance transparency with lawful protection.
20.26.4(b) Transparency shall include accurate public-safe communication about purpose, scope, evidence, methods, limitations, funding, sponsor roles, provider roles, Public Authority roles, community safeguards, correction status, and institutional boundaries where appropriate.
20.26.4(c) Lawful protection shall include protection of confidential information, personal information, Public Authority Data, cyber-sensitive information, infrastructure-sensitive information, finance-sensitive information, commercially sensitive information, employment-sensitive information, legal privilege, security controls, vulnerabilities, protected persons, sensitive locations, community-protected information, Indigenous Knowledge, Local Knowledge, Territorial Knowledge, Cultural Knowledge, Environmental Knowledge, and Protected Knowledge.
20.26.4(d) Public Trust Review shall identify where too little disclosure may create suspicion, misunderstanding, capture concerns, or public harm, and where too much disclosure may create privacy harm, cyber harm, public authority harm, community harm, protected knowledge harm, finance harm, or legal harm.
20.26.4(e) The controlling rule shall be that transparency is trustworthy only when it is accurate, safe, lawful, bounded, and correctionable.
20.26.5 Public Trust Review Shall Preserve Controlled Vocabulary and Boundary Language. 20.26.5(a) Public Trust Review shall preserve controlled vocabulary and boundary language.
20.26.5(b) Terms including assured, verified, validated, recognized, certified, finance-ready, insurance-ready, public-safe, Nexus-compatible, mature, adopted, approved, official, public authority, proof, truth, confidence, readiness, integrity, risk, assurance, impact, renewal, maturity, warning, decision, endorsement, support, partner, provider, sponsor, host, and participant shall be reviewed for controlled meaning and public reliance risk.
20.26.5(c) Boundary language shall preserve non-execution, no public warning, no emergency command, no public authority approval, no regulatory approval, no procurement approval, no public finance approval, no investment advice, no insurance approval, no certification by default, no provider preference, no sponsor control, no GRF recognition by default, no GRA finance-readiness by default, no Protocol Authority effect by default, and no Nexus legal fusion.
20.26.5(d) Plain-language summaries, captions, headings, press materials, social media, speeches, slide decks, website content, and media responses shall preserve the same controlled meaning as formal documents.
20.26.5(e) The controlling rule shall be that public trust depends on words being accurate, bounded, and consistent across formal and public-facing materials.
20.26.6 Public Trust Review Shall Consider Accessibility, Plain-Language Legibility, Media Interpretation, and Public-Safe Context. 20.26.6(a) Public Trust Review shall consider accessibility, plain-language legibility, translation, localization, media interpretation, public-safe context, and likely audience understanding.
20.26.6(b) Materials shall be reviewed for whether intended audiences can understand purpose, scope, limits, uncertainty, role boundaries, correction path, and public-safe meaning without specialist knowledge.
20.26.6(c) Media-facing and public-facing materials shall be reviewed for foreseeable misquotation, headline distortion, selective quotation, sponsor amplification, provider amplification, public authority over-attribution, finance signaling, and social media decontextualization.
20.26.6(d) Accessibility review shall consider language clarity, disability access, plain-language summaries, translation integrity, culturally appropriate framing, community context, Indigenous or protected knowledge sensitivities, and avoidance of stigmatizing or exclusionary language.
20.26.6(e) The controlling rule shall be that materials are not public-safe merely because they are internally accurate; they must be legible and bounded in the context where they will be read.
20.26.7 Public Trust Review Findings and Corrective Actions. 20.26.7(a) Public Trust Review findings shall be recorded, classified, assigned, and corrected where required.
20.26.7(b) Findings may include public claims risk, vocabulary risk, boundary-language gap, public authority overclaim, finance overclaim, certification implication, provider preference, sponsor control implication, privacy risk, cybersecurity risk, protected knowledge risk, accessibility gap, media misinterpretation risk, narrative acceleration, missing limitation, missing correction path, or unsafe disclosure.
20.26.7(c) Corrective actions may include revised public language, added limitation statement, corrected boundary language, public-safe redaction, controlled annex, public-safe notice, controlled notice, publication delay, public claims hold, legal review, public authority clarification, GRA routing, GRF clarification, Protocol Authority clarification, sponsor correction, provider correction, accessibility update, translation review, or withdrawal.
20.26.7(d) Material Public Trust Review findings shall be linked to the Risk Register, Issue Register, Control Register, Corrective Action Register, Publication Register, Public Authority Register, Finance Boundary Register, Community Safeguards Register, or Board / committee records as applicable.
20.26.7(e) The controlling rule shall be that public trust review must produce correction where public meaning would otherwise become misleading, unsafe, or overbroad.
20.26.8 Public-Safe Public Trust Summaries Where Appropriate. 20.26.8(a) GCRI Canada may issue public-safe public trust summaries where appropriate to explain institutional purpose, role boundaries, corrections, safeguards, public-benefit learning, assurance themes, public-safe changes, or response to public controversy.
20.26.8(b) Public-safe public trust summaries shall be accurate, records-supported, limitation-aware, controlled-vocabulary-compliant, boundary-safe, accessible, and correctionable.
20.26.8(c) Such summaries shall protect confidential, personal, Public Authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, employment-sensitive, community-protected, Indigenous, Local, Territorial, Cultural, Environmental, and Protected Knowledge materials.
20.26.8(d) Public-safe public trust summaries shall not imply certification, rating, guarantee, finance-readiness, public authority approval, procurement approval, provider endorsement, sponsor validation, public warning, emergency command, GRF recognition, GRA finance-readiness, Protocol Authority effect, Nexus legal fusion, or execution consequence.
20.26.8(e) The controlling rule shall be that public trust summaries should clarify without exposing, reassure without overclaiming, and correct without concealing.
20.26.9 Public Trust Register. 20.26.9(a) GCRI Canada shall maintain a Public Trust Register.
20.26.9(b) The Register shall identify public trust review item, trigger, owner, custodian, date, scope, audience, materials reviewed, public claims reviewed, Public Authority references reviewed, sponsor references reviewed, provider references reviewed, finance-sensitive references reviewed, community and protected knowledge considerations, accessibility considerations, media-risk considerations, findings, corrective actions, public-safe summary status, approvals, release status, correction status, supersession status, and closeout.
20.26.9(c) The Register shall link to the Risk Register, Issue Register, Control Register, Publication Register, Public Claims Register, Public Authority Register, Finance Boundary Register, Sponsor Register, Provider Register, Community Safeguards Register, Corrective Action Register, Incident Register, Renewal Register, Assurance records, and Board or committee records where applicable.
20.26.9(d) Access shall be controlled according to confidentiality, legal privilege, privacy, cybersecurity, Public Authority sensitivity, finance sensitivity, commercial sensitivity, employment sensitivity, community safeguards, protected knowledge, and public-safe status.
20.26.9(e) The controlling rule shall be that public trust reviews must be registered because trust-risk decisions shape public meaning.
20.26.10 Public Trust Assurance. 20.26.10(a) GCRI Canada shall conduct Public Trust Assurance.
20.26.10(b) Public Trust Assurance shall review whether public trust reviews are timely, properly scoped, evidence-supported, boundary-safe, public-safe, accessible, correctionable, and linked to public claims controls, publication controls, Public Authority controls, finance-boundary controls, sponsor controls, provider controls, and community safeguards.
20.26.10(c) Assurance shall identify repeated public misdescription, repeated overclaim, missing boundary language, inaccessible public materials, public controversy patterns, media misinterpretation patterns, sponsor amplification issues, provider amplification issues, public authority confusion, finance signaling, uncorrected public errors, and unsafe transparency gaps.
20.26.10(d) Findings may require public claims training, controlled vocabulary update, publication process update, media protocol update, public-safe summary update, legal review, Public Authority clarification, sponsor or provider correction, community consultation, corrective action, or Board / committee reporting.
20.26.10(e) The controlling rule shall be that public trust must be assured because public trust can be lost through small repeated ambiguities as well as major failures.
20.27 Assurance Records and Registers
20.27.1 Risk Register. 20.27.1(a) GCRI Canada shall maintain a Risk Register as a material constitutional record.
20.27.1(b) The Risk Register shall identify material risks, owners, custodians, affected Charter Parts, affected records, affected systems, affected persons, affected communities, affected Public Authorities, affected public materials, inherent risk, controls, residual risk, treatment, review cycle, escalation threshold, status, corrective actions, assurance findings, and Board or committee reporting.
20.27.1(c) The Risk Register shall be reconciled with issue, control, incident, corrective action, assurance, renewal, and public trust records where applicable.
20.27.1(d) The Risk Register shall not be used to accept prohibited risk by recording it as ordinary residual risk.
20.27.1(e) The controlling rule shall be that material risk must be visible, owned, and governed.
20.27.2 Issue Register. 20.27.2(a) GCRI Canada shall maintain an Issue Register for active problems, control weaknesses, recurring exceptions, open corrective actions, unresolved defects, known public claims risks, and other matters requiring active management.
20.27.2(b) The Issue Register shall identify issue source, description, classification, severity, owner, custodian, affected records, affected systems, affected persons, affected communities, affected Public Authorities, interim controls, root cause, corrective action, due date, dependencies, escalation, status, recurrence, and closeout.
20.27.2(c) The Issue Register shall link to risk, control, incident, corrective action, monitoring, evaluation, assurance, and renewal records.
20.27.2(d) Issues shall not be closed without evidence of correction or a recorded decision that no correction is required.
20.27.2(e) The controlling rule shall be that known problems must remain visible until resolved.
20.27.3 Control Register. 20.27.3(a) GCRI Canada shall maintain a Control Register.
20.27.3(b) The Control Register shall identify controls, control owners, custodians, purposes, mapped risks, mapped Charter Parts, mapped policies, procedures, systems, registers, review cycles, evidence of operation, testing schedules, exceptions, failures, corrective actions, and assurance findings.
20.27.3(c) The Control Register shall distinguish preventive, detective, corrective, compensating, technical, legal, governance, training, access, publication, room, data, AI, cybersecurity, public authority, finance-boundary, sponsor, provider, and community safeguard controls.
20.27.3(d) Controls shall be updated where risks, legal obligations, systems, public claims, participants, or Nexus interfaces change.
20.27.3(e) The controlling rule shall be that controls must be mapped and testable.
20.27.4 Stop-the-Line Register. 20.27.4(a) GCRI Canada shall maintain a Stop-the-Line Register.
20.27.4(b) The Register shall identify Stop-the-Line request or invocation, date, time, requester, invoking authority, reason, affected activity, affected records, affected systems, affected data, affected persons, affected communities, affected Public Authorities, affected public materials, interim controls, owner, custodian, triage result, decision, correction, release, escalation, closeout, and lessons learned.
20.27.4(c) The Register shall link to issue, incident, risk, control, corrective action, legal review, publication, data, AI, cybersecurity, Public Authority, finance-boundary, and community safeguard records where applicable.
20.27.4(d) The Register shall be reviewed for retaliation concerns, misuse, delay, repeated triggers, and control weaknesses.
20.27.4(e) The controlling rule shall be that protective pauses must be visible and reviewable.
20.27.5 Incident Escalation Register. 20.27.5(a) GCRI Canada shall maintain an Incident Escalation Register.
20.27.5(b) The Register shall identify incident, severity, escalation threshold, escalation recipient, time, method, content summary, confidentiality class, privilege status, acknowledgment, required action, follow-up, notice, Board or committee reporting, Public Authority escalation, affected community escalation, partner escalation, and closeout.
20.27.5(c) The Register shall link to the applicable incident register, Issue Register, Risk Register, Corrective Action Register, Legal Review Register, and Board or committee records.
20.27.5(d) Escalation failures shall be recorded and treated as incidents where material.
20.27.5(e) The controlling rule shall be that escalation is complete only when recorded and acknowledged where required.
20.27.6 MEAIR Plan Register. 20.27.6(a) GCRI Canada shall maintain a MEAIR Plan Register.
20.27.6(b) The Register shall identify monitoring, evaluation, assurance, impact review, and renewal plans, scope, owner, custodian, schedule, triggers, methods, evidence sources, affected domains, reporting routes, public-safe summary status, and closeout.
20.27.6(c) The Register shall link to risk, issue, control, monitoring, evaluation, assurance, impact review, renewal, corrective action, and Board or committee records.
20.27.6(d) The Register shall be reviewed to ensure MEAIR activities are completed, updated, and risk-based.
20.27.6(e) The controlling rule shall be that institutional learning must be planned, tracked, and renewed.
20.27.7 Monitoring Register. 20.27.7(a) GCRI Canada shall maintain a Monitoring Register.
20.27.7(b) The Register shall identify monitoring activity, owner, custodian, scope, method, frequency, systems or records monitored, exceptions, alerts, findings, issue referrals, incident referrals, corrective actions, escalation, and closeout.
20.27.7(c) The Monitoring Register shall include monitoring of governance, evidence, methods, publications, records, data, AI, cybersecurity, technical assets, Public Authority interfaces, finance boundaries, participants, community safeguards, and public trust where applicable.
20.27.7(d) Monitoring exceptions shall be linked to appropriate registers and corrective actions.
20.27.7(e) The controlling rule shall be that monitoring signals must not disappear after detection.
20.27.8 Evaluation Register. 20.27.8(a) GCRI Canada shall maintain an Evaluation Register.
20.27.8(b) The Register shall identify evaluation title, purpose, scope, owner, custodian, method, evidence reviewed, limitations, findings, recommendations, affected records, affected public materials, corrective actions, renewal actions, approvals, and closeout.
20.27.8(c) Evaluations shall be linked to mission alignment, public-benefit effectiveness, evidence quality, method fitness, research integrity, publication quality, technical stewardship, Public Authority learning, finance-boundary discipline, community safeguards, Nexus interfaces, and public trust where applicable.
20.27.8(d) Evaluation recommendations shall be assigned and tracked where action is required.
20.27.8(e) The controlling rule shall be that evaluation must create recorded learning.
20.27.9 Assurance Register. 20.27.9(a) GCRI Canada shall maintain an Assurance Register.
20.27.9(b) The Register shall identify assurance activity, scope, criteria, reviewer, independence status where applicable, evidence reviewed, sampling method, findings, internal ratings where used, limitations, corrective actions, follow-up, report status, public-safe summary status, and closeout.
20.27.9(c) The Register shall cover governance, evidence, methods, research, publication, records, data, AI, cybersecurity, Public Authority boundary, finance-boundary, fiscal, participation, community safeguard, legal compliance, Nexus interface, public trust, and other assurance domains where applicable.
20.27.9(d) Assurance findings shall be linked to corrective action and retesting where material.
20.27.9(e) The controlling rule shall be that assurance must be traceable from scope to finding to correction.
20.27.10 Impact Review Register. 20.27.10(a) GCRI Canada shall maintain an Impact Review Register.
20.27.10(b) The Register shall identify impact review title, scope, period, owner, custodian, evidence basis, methodology, limitations, affected domains, affected communities, affected Public Authorities, sponsor or provider roles, findings, approved claims, rejected claims, corrective actions, public-safe summary status, and closeout.
20.27.10(c) The Register shall link to publications, public claims, evidence records, methods records, research records, public authority records, finance-boundary records, community safeguard records, and renewal records where applicable.
20.27.10(d) Impact claims shall not be entered as approved unless evidence, limits, context, and correction path are recorded.
20.27.10(e) The controlling rule shall be that impact review must preserve contribution discipline and avoid impact inflation.
20.27.11 Renewal Register. 20.27.11(a) GCRI Canada shall maintain a Renewal Register.
20.27.11(b) The Register shall identify renewal action, trigger, owner, custodian, affected documents, affected methods, affected systems, affected records, affected public materials, affected participants, affected Public Authorities, affected communities, approval status, effective date, supersession chain, communication status, training status, corrective action status, and closeout.
20.27.11(c) Renewal actions shall be linked to monitoring, evaluation, assurance, impact review, incidents, issues, legal changes, technology changes, Nexus Universe lessons, Public Authority feedback, community feedback, and Board or committee records where applicable.
20.27.11(d) Renewal shall not be closed until affected records and public materials are updated or a lawful deferral is recorded.
20.27.11(e) The controlling rule shall be that learning must become implemented change.
20.27.12 Annual Assurance Report Register. 20.27.12(a) GCRI Canada shall maintain an Annual Assurance Report Register.
20.27.12(b) The Register shall identify annual assurance reports, internal integrity reports, public-safe integrity statements, equivalent reviews, drafts, approved versions, controlled annexes, public-safe versions, periods covered, owners, custodians, reviewers, Board or committee approvals, publication status, correction status, supersession status, withdrawal status, retraction status, archive status, and distribution.
20.27.12(c) The Register shall link to assurance records, risk records, issue records, control records, corrective action records, incident records, renewal records, legal review records, publication records, and Board or committee records.
20.27.12(d) The Register shall be reviewed for stale reports, improper public use, unresolved corrections, and missing archive records.
20.27.12(e) The controlling rule shall be that integrity reporting must have record integrity.
20.27.13 Control Testing Register. 20.27.13(a) GCRI Canada shall maintain a Control Testing Register.
20.27.13(b) The Register shall identify control tested, testing purpose, tester, owner, custodian, scope, method, sample, period reviewed, evidence reviewed, exceptions, findings, severity, corrective actions, retesting requirements, retesting results, and closeout.
20.27.13(c) The Register shall link to the Control Register, Risk Register, Issue Register, Assurance Register, Corrective Action Register, and affected domain registers.
20.27.13(d) Material failed tests shall remain open until remediated and retested where appropriate.
20.27.13(e) The controlling rule shall be that control testing must be tracked from test to verified remediation.
20.27.14 Corrective Action Register. 20.27.14(a) GCRI Canada shall maintain a Corrective Action Register.
20.27.14(b) The Register shall identify corrective action, source, Case ID where applicable, domain, owner, custodian, root cause, affected records, affected systems, affected persons, affected communities, affected Public Authorities, affected public materials, interim controls, permanent controls, due dates, milestones, evidence of completion, validation, residual risk, escalation, and closeout.
20.27.14(c) The Register shall link to risk, issue, control, incident, assurance, evaluation, impact, renewal, legal review, publication, data, AI, cybersecurity, Public Authority, finance-boundary, and community safeguard records.
20.27.14(d) The Register shall be reviewed for overdue actions, repeated findings, ineffective corrective actions, and unverified closure.
20.27.14(e) The controlling rule shall be that corrective actions must remain open until verified by evidence.
20.27.15 Root-Cause and Lessons Learned Register. 20.27.15(a) GCRI Canada shall maintain a Root-Cause and Lessons Learned Register.
20.27.15(b) The Register shall identify event, domain, date, owner, custodian, root cause, contributing factors, affected risks, affected controls, affected records, affected systems, affected persons, affected communities, affected Public Authorities, affected public materials, lessons, renewal actions, training actions, policy actions, technical actions, public-safe summary status, and closeout.
20.27.15(c) The Register shall distinguish privileged, confidential, internal, controlled, public-safe, community-protected, and protected knowledge-sensitive lessons.
20.27.15(d) Lessons shall be linked to corrective actions and renewal actions where implementation is required.
20.27.15(e) The controlling rule shall be that lessons must be registered so that learning survives personnel and time.
20.27.16 Key Risk Indicator Register. 20.27.16(a) GCRI Canada shall maintain a Key Risk Indicator Register.
20.27.16(b) The Register shall identify indicators, purpose, owner, custodian, domain, data source, calculation or qualitative method, threshold, review cycle, escalation path, trend, alerts, actions, renewal date, and retirement status.
20.27.16(c) The Register may include governance, evidence, methods, research, records, data, AI, cybersecurity, Public Authority boundary, finance boundary, sponsor / provider influence, community safeguard, correction timeliness, public-safe claims quality, training completion, incident closure, and assurance indicators.
20.27.16(d) Threshold breaches shall be linked to issues, incidents, corrective actions, or Board / committee reporting where appropriate.
20.27.16(e) The controlling rule shall be that indicators must be owned and acted upon, not merely measured.
20.27.17 Internal Maturity Review Register. 20.27.17(a) GCRI Canada shall maintain an Internal Maturity Review Register.
20.27.17(b) The Register shall identify maturity review title, scope, domain, owner, custodian, methodology, evidence reviewed, stage description, limitations, findings, renewal actions, corrective actions, public-safe summary status, correction status, supersession status, and closeout.
20.27.17(c) The Register shall distinguish internal maturity review from GRF maturity records, certification, rating, finance-readiness, public authority approval, procurement preference, provider preference, and sponsor validation.
20.27.17(d) Maturity review records shall be corrected and superseded where evidence or stage truth changes.
20.27.17(e) The controlling rule shall be that maturity language must be registered because it can create institutional overconfidence or public overclaim.
20.27.18 Nexus Universe After-Action Register. 20.27.18(a) GCRI Canada shall maintain a Nexus Universe After-Action Register.
20.27.18(b) The Register shall identify Nexus Universe activity, date, scope, owner, custodian, participants, roles, Public Authority capacity classifications, sponsor roles, provider roles, host roles, community roles, capital-reader roles, systems used, data used, AI used, materials used, incidents, issues, lessons, corrective actions, renewal actions, public-safe summary status, and closeout.
20.27.18(c) The Register shall link to evidence, methods, Observatory, Truth Engine, Academy, Public Authority, finance-boundary, provider, sponsor, host, community, and Nexus-interface records where applicable.
20.27.18(d) The Register shall be reviewed for unresolved lessons, repeated issues, boundary misunderstandings, and public claims misuse.
20.27.18(e) The controlling rule shall be that Nexus Universe learning must be captured as structured institutional memory.
20.27.19 Nexus Interface Assurance Register. 20.27.19(a) GCRI Canada shall maintain a Nexus Interface Assurance Register.
20.27.19(b) The Register shall identify interface, actor, purpose, authority, owner, custodian, shared records, data flows, technical flows, funding flows where any, public claims, Public Authority references, finance-sensitive references, sponsor or provider roles, legal-separateness language, boundary language, correction path, assurance findings, corrective actions, closeout, and archive.
20.27.19(c) The Register shall include interfaces with GCRI US, GRF, GRA, Protocol Authority, Nexus entities, Regional Nexus Consortiums, National Nexus Consortiums, National Companies, Project SPVs, providers, hosts, sponsors, universities, Public Authorities, communities, and capital readers where applicable.
20.27.19(d) The Register shall be reviewed for stale interfaces, unresolved findings, role confusion, data custody gaps, and public claims drift.
20.27.19(e) The controlling rule shall be that Nexus interfaces must be assured because repeated coordination can create legal and public meaning.
20.27.20 External Review, Complaint, Grievance, Challenge, Whistleblower, and Public Trust Registers. 20.27.20(a) GCRI Canada shall maintain External Review, Complaint, Grievance, Challenge, Whistleblower, and Public Trust Registers or interoperable register sections.
20.27.20(b) External Review records shall identify reviewer, scope, independence, conflicts, confidentiality, materials reviewed, findings, limitations, recommendations, corrective actions, public-safe summary status, and follow-up.
20.27.20(c) Complaint, Grievance, Challenge, and Whistleblower records shall identify concern type, reporter status where known, confidentiality status, affected domain, severity, owner, custodian, triage, investigation, findings, remedies, corrective actions, retaliation review, appeal status where applicable, and closeout.
20.27.20(d) Public Trust records shall identify public trust review trigger, audience, public claims, boundary language, accessibility, media interpretation, findings, corrective actions, public-safe summaries, and closeout.
20.27.20(e) Access shall be controlled for privacy, confidentiality, privilege, cybersecurity, Public Authority sensitivity, finance sensitivity, employment sensitivity, community safeguards, protected knowledge, non-retaliation, and public-safe status.
20.27.20(f) The controlling rule shall be that challenge, review, and trust records must be maintained because accountability depends on institutional memory.
20.28 Assurance Governance
20.28.1 Assurance Governance by Board, Committees, Officers, and Delegated Leads. 20.28.1(a) Assurance governance shall be carried out by the Board, authorized committees, Officers, and delegated leads according to law, articles, Bylaw, Charter, Board resolutions, committee charters, policies, procedures, and recorded delegations.
20.28.1(b) The Board shall oversee material assurance architecture, assurance priorities, assurance independence where required, major findings, corrective action, unresolved high risks, and annual or periodic integrity reporting where directed.
20.28.1(c) Committees may review assurance within their mandates, including governance, finance, audit, risk, legal compliance, data, AI, cybersecurity, research, publication, public authority, finance-boundary, safeguards, and participation domains.
20.28.1(d) Officers and delegated leads shall implement assurance plans, maintain registers, assign owners, track corrective actions, and escalate material findings.
20.28.1(e) The controlling rule shall be that assurance governance must connect evidence of control performance to accountable institutional authority.
20.28.2 Assurance Independence Where Appropriate. 20.28.2(a) Assurance shall include independence where appropriate to risk, materiality, legal sensitivity, public trust consequence, technical complexity, Public Authority sensitivity, finance sensitivity, community sensitivity, protected knowledge sensitivity, or prior control failure.
20.28.2(b) Independence may require separation between operator and reviewer, conflict screening, recusal, committee oversight, independent expert review, external review, legal review, technical review, community review, or Board-directed review.
20.28.2(c) Persons who designed, operated, approved, or are implicated in a control, activity, output, publication, interface, incident, or corrective action shall not be the sole assurance reviewer where independence is required.
20.28.2(d) Independence shall not eliminate the duty of responsible owners to provide records, explanations, access, and corrective action.
20.28.2(e) The controlling rule shall be that assurance confidence increases when review is sufficiently independent from the activity reviewed.
20.28.3 Assurance Scope Approval. 20.28.3(a) Assurance scope shall be approved by the appropriate Board, committee, Officer, or delegated lead according to risk and authority.
20.28.3(b) Scope approval shall identify domain, period, criteria, records, systems, programs, outputs, controls, interfaces, data classes, public materials, participants, exclusions, limitations, review method, reporting route, confidentiality class, public-safe summary status, and expected corrective action process.
20.28.3(c) Scope shall be sufficient to support the assurance conclusions made and shall not imply broader review than was performed.
20.28.3(d) Material exclusions shall be recorded and, where they affect interpretation, disclosed in internal or public-safe summaries as appropriate.
20.28.3(e) The controlling rule shall be that assurance scope must be clear before assurance findings can be trusted.
20.28.4 Assurance Evidence Standards. 20.28.4(a) Assurance evidence shall be sufficient, relevant, reliable, current, traceable, and proportionate to the assurance objective.
20.28.4(b) Assurance evidence may include policies, procedures, Board records, committee records, delegations, registers, repositories, logs, access records, metadata, source lineage, version history, change logs, contracts, data records, AI records, inference records, cybersecurity records, publication records, public claims records, incident records, correction records, training records, interviews, attestations, technical tests, and external review records.
20.28.4(c) Attestations alone shall not be sufficient where objective records, logs, system evidence, source records, or technical evidence are required.
20.28.4(d) Assurance evidence shall be protected according to classification, confidentiality, privilege, privacy, cybersecurity, Public Authority sensitivity, finance sensitivity, commercial sensitivity, employment sensitivity, community safeguards, and protected knowledge controls.
20.28.4(e) The controlling rule shall be that assurance is only as credible as the evidence on which it rests.
20.28.5 Assurance Sampling Standards. 20.28.5(a) Where assurance uses sampling, sampling standards shall be documented.
20.28.5(b) Sampling shall identify population, sample size, selection method, risk basis, period, exclusions, limitations, and confidence limits where applicable.
20.28.5(c) Higher-risk domains may require targeted sampling, expanded sampling, full-population review, technical testing, or independent review.
20.28.5(d) Sampling shall not be used to conceal known issues, avoid review of high-risk items, or create misleading assurance.
20.28.5(e) The controlling rule shall be that sampling must be honest about what was tested and what remains untested.
20.28.6 Assurance Confidentiality and Public-Safe Handling. 20.28.6(a) Assurance activities and assurance records shall be handled according to confidentiality, public-safe status, legal privilege, privacy, cybersecurity, Public Authority sensitivity, finance sensitivity, commercial sensitivity, employment sensitivity, community safeguards, protected knowledge, and need-to-know.
20.28.6(b) Assurance may require internal, controlled, restricted, public-safe, or split reporting versions.
20.28.6(c) Public-safe assurance summaries shall protect sensitive information while providing accurate, bounded, limitation-aware information where transparency is appropriate.
20.28.6(d) Assurance handling shall not suppress required correction, legal notice, affected-person notice, Public Authority escalation, community remedy, or Board reporting.
20.28.6(e) The controlling rule shall be that assurance confidentiality protects sensitive truth while public-safe handling enables responsible trust.
20.28.7 Assurance Findings Classification. 20.28.7(a) Assurance findings shall be classified according to severity, domain, control impact, legal consequence, public-benefit consequence, public trust consequence, recurrence risk, public-safe consequence, data sensitivity, cybersecurity consequence, Public Authority consequence, finance consequence, protected knowledge consequence, and required corrective action.
20.28.7(b) Findings may be classified as observation, improvement opportunity, minor deficiency, significant deficiency, material finding, critical finding, issue, incident, legal matter, control failure, or boundary breach according to policy.
20.28.7(c) Classification shall be updated where facts change.
20.28.7(d) Findings shall not be under-classified to avoid escalation, correction, reporting, or public-safe notice.
20.28.7(e) The controlling rule shall be that assurance classification must reflect risk and consequence, not institutional preference.
20.28.8 Assurance Corrective Action Tracking. 20.28.8(a) Assurance findings requiring action shall be tracked through corrective action processes.
20.28.8(b) Corrective action tracking shall identify finding, owner, root cause, interim control, permanent control, affected records, due date, milestones, evidence of completion, validation, residual risk, retesting, and closeout.
20.28.8(c) Overdue corrective actions, ineffective corrective actions, repeated extensions, or unverified closures shall be escalated.
20.28.8(d) Corrective action status shall be reported to the appropriate Officer, committee, or Board according to severity and authority.
20.28.8(e) The controlling rule shall be that assurance without corrective action tracking is observation without governance.
20.28.9 Assurance Reporting to Board and Committees. 20.28.9(a) Material assurance findings shall be reported to the Board or authorized committee according to risk, mandate, and reporting thresholds.
20.28.9(b) Reports shall identify scope, methodology, evidence, limitations, findings, severity, affected risks, corrective actions, overdue items, unresolved issues, resource needs, escalation needs, and public-safe implications where appropriate.
20.28.9(c) Reports shall preserve privilege, confidentiality, privacy, cybersecurity, Public Authority sensitivity, finance sensitivity, employment sensitivity, community safeguards, and protected knowledge.
20.28.9(d) Board and committee reports shall distinguish matters requiring decision, matters requiring oversight, matters requiring information, and matters requiring future assurance.
20.28.9(e) The controlling rule shall be that assurance reporting must enable governance action, not merely information receipt.
20.28.10 Assurance Public-Safe Summaries Where Directed. 20.28.10(a) Public-safe assurance summaries may be prepared where directed by the Board or authorized committee.
20.28.10(b) Public-safe summaries shall identify scope, period, high-level themes, limitations, corrective action themes, renewal actions, and public-benefit learning where appropriate.
20.28.10(c) Public-safe summaries shall avoid exposing confidential, personal, Public Authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, employment-sensitive, community-protected, Indigenous, Local, Territorial, Cultural, Environmental, or Protected Knowledge materials.
20.28.10(d) Public-safe summaries shall not imply certification, rating, guarantee, finance-readiness, public authority approval, procurement preference, provider endorsement, sponsor validation, public warning, emergency command, protocol effect, or execution consequence.
20.28.10(e) The controlling rule shall be that public-safe assurance summaries may strengthen trust only when bounded by scope, limitation, and safety.
20.28.11 Assurance Conflicts and Recusal. 20.28.11(a) Assurance conflicts shall be disclosed, reviewed, managed, and recorded.
20.28.11(b) Conflicts may arise where a reviewer designed, operated, approved, funded, sponsored, supplied, promoted, published, or was implicated in the activity, control, record, output, incident, or corrective action under review.
20.28.11(c) Conflict management may include recusal, independent review, restricted access, reviewer substitution, additional oversight, disclosure, or Board / committee review.
20.28.11(d) A conflicted person shall not suppress findings, alter scope, influence evidence selection, delay correction, or approve closure where independence is required.
20.28.11(e) The controlling rule shall be that assurance independence must be protected from the same influence risks that assurance is meant to detect.
20.28.12 Assurance Governance Records. 20.28.12(a) GCRI Canada shall maintain Assurance Governance records.
20.28.12(b) Records shall identify assurance governance structure, Board oversight, committee mandates, Officer responsibilities, delegated leads, assurance plans, scope approvals, independence decisions, conflict disclosures, evidence standards, sampling standards, findings classifications, reporting records, public-safe summary approvals, corrective action tracking, and closeout.
20.28.12(c) Assurance Governance records shall link to risk, issue, control, incident, corrective action, renewal, annual assurance, public trust, and Board or committee records.
20.28.12(d) Records shall be classified, access-controlled, versioned, retained, corrected, and archived according to applicable records rules.
20.28.12(e) The controlling rule shall be that assurance governance must itself be record-valid, because assurance is a governance function.
20.29 Part XX Closing Integration Clause
20.29.1 Part XX shall govern the risk management, assurance, monitoring, evaluation, impact, renewal, stop-the-line, incident escalation, and institutional-learning reading of all later Parts. 20.29.1(a) This Part XX shall govern the interpretation of all later Parts concerning risk management, institutional risk registers, issue ownership, control mapping, control testing, monitoring, evaluation, assurance, impact review, renewal, Stop-the-Line Authority, incident escalation, integrated incident management, corrective action, root-cause analysis, lessons learned, early warning, Key Risk Indicators, integrity indicators, internal maturity review, Nexus Universe after-action learning, Nexus Interface Assurance, external review, complaints, grievances, challenge pathways, whistleblower pathways, public trust review, assurance registers, and assurance governance.
20.29.1(b) All later Parts shall be read consistently with the principle that GCRI Canada’s public-benefit work requires proportionate risk discipline, evidence of controls, timely escalation, correctionability, public-safe transparency, renewal, and institutional learning.
20.29.1(c) Part XX shall control where later operational, programmatic, technical, public authority, finance-sensitive, cross-border, research, publication, community-facing, participant-facing, or Nexus-interface provisions could otherwise be read to permit unmanaged risk, unowned issues, untested controls, uncorrected failures, unassured public claims, or unreviewed public trust exposure.
20.29.1(d) The controlling rule shall be that risk management and assurance are not administrative afterthoughts; they are constitutional disciplines through which GCRI Canada preserves lawful public-benefit action.
20.29.2 No later Part shall be interpreted to permit GCRI Canada to operate without risk registers, issue ownership, control mapping, stop-the-line authority, incident escalation, corrective action, assurance, renewal, and learning loops proportionate to the risk, sensitivity, public consequence, legal consequence, and public-trust consequence of the activity. 20.29.2(a) No later Part shall be interpreted to permit GCRI Canada to operate material governance, research, evidence, methods, data, AI, cybersecurity, technical assets, public-good software, Open Technical Baselines, dashboards, maps, datasets, publications, public authority learning, finance-boundary interfaces, sponsor relationships, provider relationships, community interfaces, controlled rooms, clean rooms, Nexus Universe activities, or Nexus interfaces without proportionate risk registers, issue ownership, control mapping, Stop-the-Line Authority, incident escalation, corrective action, assurance, renewal, and learning loops.
20.29.2(b) The level of risk management and assurance required shall be proportionate to legal consequence, public-benefit consequence, public trust consequence, data sensitivity, AI risk, cybersecurity risk, technical complexity, Public Authority sensitivity, finance sensitivity, protected knowledge sensitivity, community sensitivity, publication reach, participant reliance, cross-border exposure, and Nexus-interface effect.
20.29.2(c) No person may rely on informality, speed, public visibility, donor urgency, sponsor preference, provider preference, grant deadline, public authority interest, capital-reader interest, technical opportunity, or operational convenience to bypass required risk ownership, Stop-the-Line review, incident escalation, corrective action, or assurance.
20.29.2(d) Where later provisions create new activities, systems, interfaces, publications, rooms, data flows, AI uses, technical releases, or public claims, the corresponding risk, issue, control, monitoring, evaluation, assurance, correction, renewal, and public trust controls shall be established or adapted before material reliance occurs.
20.29.2(e) The controlling rule shall be that GCRI Canada shall not scale activity faster than it can govern, assure, correct, and learn from that activity.
20.29.3 No later Part shall be interpreted to convert GCRI Canada monitoring, evaluation, assurance, impact review, maturity review, after-action review, public-safe integrity statements, risk indicators, or Nexus interface assurance into certification, rating, guarantee, finance-readiness, public authority approval, procurement preference, provider endorsement, public warning, emergency command, protocol effect, or execution consequence by implication. 20.29.3(a) No later Part shall be interpreted to convert monitoring, evaluation, assurance, impact review, internal maturity review, Nexus Universe after-action review, public-safe integrity statements, annual assurance reports, risk indicators, integrity indicators, early warnings, Public Trust Review, Nexus Interface Assurance, external review, expert challenge, or corrective action findings into certification, rating, guarantee, finance-readiness, insurance-readiness, public authority approval, regulatory approval, procurement approval, procurement preference, provider endorsement, sponsor validation, GRF recognition, GRA finance-readiness, Protocol Authority effect, public warning, emergency command, market operation, or execution consequence by implication.
20.29.3(b) Internal assurance confidence shall remain internal unless a separate lawful authority, proper records, approved publication class, controlled vocabulary review, public claims review, and boundary language support a specified external statement.
20.29.3(c) Public-safe summaries shall be interpreted as bounded transparency outputs and not as guarantees of completeness, absence of risk, legal compliance certification, security certification, AI certification, maturity status, finance-readiness, Public Authority adoption, or provider approval.
20.29.3(d) Any third-party misuse of GCRI Canada assurance, maturity, impact, after-action, indicator, or interface materials to claim external status shall require correction, clarification, access restriction, public-safe notice, controlled notice, relationship remedy, or legal review where appropriate.
20.29.3(e) The controlling rule shall be that institutional learning outputs do not become external approvals by audience, repetition, branding, or implication.
20.29.4 Where ambiguity exists, the interpretation that better preserves risk discipline, assurance discipline, institutional learning, public-benefit effectiveness, correctionability, public-safe transparency, privacy, cybersecurity, protected knowledge, public authority boundaries, finance-readiness boundaries, provider neutrality, sponsor non-control, non-execution, Nexus role separation, legal separateness, validity-by-record, and public trust shall prevail. 20.29.4(a) Where ambiguity exists in this Part XX or any later Part concerning risk management, assurance, monitoring, evaluation, impact, renewal, Stop-the-Line Authority, incident escalation, maturity review, after-action review, public trust, external review, complaints, challenges, whistleblowing, Nexus interfaces, Public Authority interfaces, finance-sensitive interfaces, technical assets, publications, data, AI, cybersecurity, safeguards, or institutional learning, the interpretation that better preserves risk discipline shall prevail.
20.29.4(b) The preferred interpretation shall preserve assurance discipline, institutional learning, public-benefit effectiveness, correctionability, public-safe transparency, privacy, cybersecurity, protected knowledge, Public Authority boundaries, finance-readiness boundaries, provider neutrality, sponsor non-control, donor non-control, grantor non-control, non-execution, Nexus role separation, legal separateness, validity-by-record, controlled vocabulary, and public trust.
20.29.4(c) Ambiguity shall not be resolved in favor of speed, scale, visibility, funding, sponsor satisfaction, provider convenience, public authority proximity, capital-reader interest, media appeal, technical enthusiasm, operational convenience, or informal precedent.
20.29.4(d) Where necessary to preserve this clause, GCRI Canada shall pause activity, invoke Stop-the-Line, narrow scope, assign ownership, obtain legal review, restrict access, correct records, issue public-safe or controlled notices, update controls, conduct assurance, renew policies, withdraw materials, reclassify risk, escalate to the Board, or refuse the activity.
20.29.4(e) The controlling rule shall be that ambiguity in risk and assurance matters must be resolved toward restraint, review, correction, learning, and trust.
Last updated
Was this helpful?