VIII. TRUTH
8.1 Nexus Truth Engine Purpose and Non-Oracle Rule
8.1.1 Nexus Truth Engine as a Method-Supported Confidence, Corroboration, Dispute, Evidence-Routing, and Correction System. 8.1.1(a) GCRI Canada shall steward the Nexus Truth Engine as a method-supported confidence, corroboration, dispute, evidence-routing, and correction system within GCRI Canada’s public-benefit, non-executing, evidence-and-methods mandate.
8.1.1(b) The Nexus Truth Engine shall support the disciplined treatment of evidence by helping identify what is known, what is not known, what is probable, what is uncertain, what is disputed, what is stale, what is corrected, what is superseded, what is public-safe, what is restricted, what is source-supported, what is method-supported, what is confidence-supported, what is outside the record, and what must not be publicly overstated.
8.1.1(c) The Nexus Truth Engine may support evidence comparison, source comparison, corroboration, contradiction detection, confidence treatment, uncertainty treatment, dispute routing, stale-evidence detection, missing-evidence identification, spoof-risk flagging, source-lineage review, method-dependency review, correction triggering, supersession tracking, withdrawal routing, retraction routing, and downstream dependency review.
8.1.1(d) The Nexus Truth Engine shall operate through records, methods, registered evidence categories, controlled vocabulary, source lineage, provenance, custody, classification, confidence logic, uncertainty logic, limitation treatment, review status, public-safe status, access controls, correction paths, and dependency tracking.
8.1.1(e) The Nexus Truth Engine shall not treat volume, repetition, popularity, institutional prestige, public authority attention, sponsor support, provider prominence, media circulation, AI output, dashboard display, blockchain anchoring, proof receipt, or technical sophistication as a substitute for method-supported evidence.
8.1.1(f) The Nexus Truth Engine may identify conflicts among records, but conflict identification shall not by itself resolve institutional truth, create public meaning, assign legal responsibility, establish recognition, determine finance-readiness, create public authority effect, certify a system, rank a provider, or execute a downstream action.
8.1.1(g) The Nexus Truth Engine shall support correctionability by routing defects, disputes, stale records, overclaims, source-lineage gaps, method defects, confidence defects, uncertainty defects, public-safe classification defects, and downstream dependency concerns to the appropriate correction, review, withdrawal, retraction, supersession, or archival pathway.
8.1.1(h) The controlling rule shall be that the Nexus Truth Engine is a disciplined evidence infrastructure for better truth stewardship, not an automatic machine for producing institutional authority.
8.1.2 Nexus Truth Engine as Decision-Supporting, Not Decision-Making. 8.1.2(a) The Nexus Truth Engine shall be decision-supporting and shall not be decision-making. It may assist competent actors by structuring evidence, identifying confidence, disclosing uncertainty, comparing sources, surfacing disputes, routing corrections, and clarifying limitations, but it shall not itself decide, approve, certify, recognize, procure, fund, finance, insure, underwrite, rate, warn, command, regulate, enforce, operate, deploy, or execute.
8.1.2(b) The Nexus Truth Engine may support internal GCRI Canada governance, public authority learning, GRF evidence inputs, GRA evidence inputs, Protocol Authority support, Nexus Observatory review, Nexus Risk Management review, Nexus Rails handoffs, Nexus Grid inputs, Nexus Academy materials, National Consortium evidence work, National Company interfaces, Project SPV interfaces, provider-facing evidence review, sponsor-facing boundary review, host-facing evidence review, and community-facing public-safe outputs, provided that each use remains within its recorded boundary.
8.1.2(c) Decision-supporting outputs shall include confidence notes, uncertainty notes, evidence comparison notes, source-lineage notes, dispute flags, missing-evidence flags, stale-evidence flags, correction flags, evidence-routing notes, public-safe review notes, dependency notes, and boundary notes.
8.1.2(d) No Nexus Truth Engine output shall be described as a final decision, approval, adoption, determination, authorization, certificate, rating, guarantee, public authority finding, public warning, finance-readiness determination, procurement decision, protocol entitlement, recognition record, maturity record, provider endorsement, sponsor approval, investment recommendation, or execution command.
8.1.2(e) Where a competent downstream actor relies on Nexus Truth Engine outputs, such reliance shall remain the downstream actor’s own reliance within its own lawful authority, duty, procedure, accountability, and record. GCRI Canada’s support shall not convert GCRI Canada into the downstream decision-maker.
8.1.2(f) Where a Nexus Truth Engine output is used in a Decision Pack, public authority learning material, GRF input, GRA input, Protocol Authority support, Docket record, Grid record, Rails handoff, Observatory output, public-safe publication, dashboard, map, technical baseline, or public claim, the output shall carry or be linked to sufficient source, method, status, confidence, uncertainty, limitation, permitted-use, prohibited-use, and correction information.
8.1.2(g) Where a Nexus Truth Engine output creates credible risk of being mistaken for a decision, GCRI Canada shall narrow, relabel, restrict, correct, withdraw, reissue, route to a competent actor, or add public-safe boundary language sufficient to restore the decision-supporting character of the output.
8.1.2(h) The controlling rule shall be that the Nexus Truth Engine may inform judgment but shall not replace judgment, authority, accountability, or lawful decision-making by competent actors.
8.1.3 Nexus Truth Engine as Evidence Infrastructure, Not Public Authority, Regulator, Certifier, Rating Agency, Financial Actor, Emergency Commander, or Public Warning System. 8.1.3(a) The Nexus Truth Engine shall be evidence infrastructure and shall not be public authority, regulator, certifier, rating agency, financial actor, emergency commander, public warning system, procurement authority, market operator, infrastructure operator, protocol authority, professional adviser, insurer, lender, underwriter, broker, dealer, fund, public finance approver, or execution actor.
8.1.3(b) The Nexus Truth Engine shall not issue public authority decisions, regulatory approvals, enforcement positions, procurement approvals, funding approvals, public finance approvals, official guidance, emergency commands, public warnings, public health orders, evacuation instructions, permits, licenses, safe harbors, compliance determinations, or sovereign obligations.
8.1.3(c) The Nexus Truth Engine shall not issue certification, recognition, maturity records, standing, public-facing legitimacy, provider endorsement, sponsor approval, protocol entitlements, role keys, smart licenses, proof-receipt legal effect, conformance states with external force, technical performance guarantees, security approvals, or operational clearances.
8.1.3(d) The Nexus Truth Engine shall not issue investment advice, securities recommendations, brokerage outputs, placement outputs, finder outputs, capital suitability determinations, lending decisions, underwriting decisions, insurance placement decisions, ratings, guarantees, public finance approvals, capital commitments, bankability determinations, fundability determinations, or finance-readiness determinations by default.
8.1.3(e) The Nexus Truth Engine shall not become a public warning system merely because it handles risk evidence, hazard evidence, public authority evidence, emergency-management evidence, cyber evidence, health-sensitive evidence, climate evidence, disaster evidence, infrastructure evidence, dashboard outputs, maps, sensor signals, AI-RAN signals, DePIN records, digital twin outputs, or observability signals.
8.1.3(f) The Nexus Truth Engine shall not become a public authority, regulator, certifier, rating agency, financial actor, emergency commander, or public warning system by reason of public authority participation, sponsor support, provider participation, capital-reader interest, Nexus branding, dashboard visibility, media attention, public reliance, or technical sophistication.
8.1.3(g) Where Nexus Truth Engine outputs are used by GRF, GRA, Protocol Authority, public authorities, National Consortiums, National Companies, Project SPVs, providers, sponsors, hosts, universities, capital readers, or communities, GCRI Canada shall preserve role-specific boundary language and shall not allow evidence infrastructure to be misdescribed as downstream authority.
8.1.3(h) The controlling rule shall be that evidence infrastructure may support lawful authority held by others, but it shall not itself become the authority it supports.
8.1.4 Nexus Truth Engine as Confidence-Aware and Limitation-Aware. 8.1.4(a) The Nexus Truth Engine shall be confidence-aware and limitation-aware. It shall preserve, generate, route, display, or reference confidence and limitation information only within recorded method, evidence, classification, and public-safe boundaries.
8.1.4(b) Confidence treatment shall address, where material, source reliability, source independence, source completeness, provenance, custody, data quality, method quality, calibration, corroboration, contradiction, reproducibility, timeliness, stale status, missing data, model dependence, AI dependence, sensor quality, spoof risk, cyber integrity, geospatial precision, benchmark conditions, public authority context, community context, protected knowledge limitations, and public-safe status.
8.1.4(c) Limitation treatment shall identify, where material, source limits, method limits, dataset limits, model limits, geographic limits, temporal limits, jurisdictional limits, public authority limits, privacy limits, cybersecurity limits, sovereign data limits, protected knowledge limits, community safeguard limits, finance-boundary limits, provider-neutrality limits, sponsor-non-control limits, and downstream-use limits.
8.1.4(d) Confidence indicators, confidence scores, certainty language, readiness-context signals, maturity-context signals, dashboard colors, map overlays, risk indicators, resilience indicators, proof receipts, benchmark results, and model outputs shall not be used in a manner that creates false precision, rating-like meaning, certification-like meaning, recognition-like meaning, finance-readiness meaning, public authority meaning, procurement meaning, provider preference, sponsor validation, public warning, or execution implication.
8.1.4(e) Where confidence is low, disputed, source-limited, method-limited, model-dependent, AI-dependent, context-limited, stale, incomplete, or unsuitable for public release, the Nexus Truth Engine shall reflect such status in records and shall not allow outputs to be communicated as stronger than the record supports.
8.1.4(f) Where limitations materially affect reliance, the Nexus Truth Engine shall support limitation disclosure in Evidence Packs, Decision Packs, public-safe outputs, dashboards, maps, Docket records, Grid records, Observatory records, Rails handoffs, GRF inputs, GRA inputs, Protocol Authority support, public authority materials, finance-facing materials, provider materials, sponsor materials, community-facing materials, and public claims.
8.1.4(g) Where confidence or limitation treatment is corrected, downgraded, disputed, restricted, superseded, withdrawn, retracted, or reissued, the Nexus Truth Engine shall support dependency review and downstream correction.
8.1.4(h) The controlling rule shall be that confidence and limitations are not decorative notes; they are core evidence conditions without which truth claims become unsafe.
8.1.5 Nexus Truth Engine as Source-Lined, Contextual, Versioned, Reviewable, Challengeable, and Correctionable. 8.1.5(a) The Nexus Truth Engine shall be source-lined, contextual, versioned, reviewable, challengeable, and correctionable.
8.1.5(b) Source-lined means that material Nexus Truth Engine inputs, outputs, comparisons, confidence assessments, dispute flags, correction triggers, routing decisions, and public-safe summaries shall be connected to source records, provenance, custody, method records, dataset records, model records, observability records, ontology records, evidence records, and dependency records where material.
8.1.5(c) Contextual means that the Nexus Truth Engine shall preserve technology domain, risk domain, jurisdictional context, public authority context, community context, Indigenous or local knowledge context, protected knowledge context, data class, evidence class, method scope, public-safe status, audience, intended use, prohibited use, and downstream boundary conditions where material.
8.1.5(d) Versioned means that material Nexus Truth Engine methods, evidence classes, confidence logic, dispute logic, source-comparison logic, correction logic, outputs, summaries, dashboards, integrations, public-safe artifacts, and interface records shall carry version identity, effective date, status, supersession path, withdrawal path, and archive path where material.
8.1.5(e) Reviewable means that authorized reviewers shall be able to inspect the evidence basis, method basis, source treatment, confidence treatment, uncertainty treatment, limitation treatment, classification treatment, public-safe treatment, AI-use treatment where applicable, and correction path for material Nexus Truth Engine outputs without exposing protected material beyond proper access controls.
8.1.5(f) Challengeable means that material Nexus Truth Engine outputs may be challenged by authorized actors, affected persons, data stewards, evidence stewards, method stewards, public authority participants, community participants, Indigenous or local knowledge holders, GRF, GRA, Protocol Authority, Nexus entities, providers, sponsors, hosts, universities, or other credible challengers through appropriate challenge pathways.
8.1.5(g) Correctionable means that material Nexus Truth Engine records and outputs shall be capable of correction, confidence change, uncertainty change, reclassification, restriction, supersession, withdrawal, retraction, downgrade, suspension, reinstatement, retirement, archive, and downstream dependency notification.
8.1.5(h) The controlling rule shall be that a Truth Engine output that cannot be sourced, contextualized, versioned, reviewed, challenged, and corrected shall not be treated as institutionally reliable.
8.1.6 Nexus Truth Engine as AI-Assisted Only Under Governance, Records, Human Review Where Material, and Public-Safe Controls. 8.1.6(a) The Nexus Truth Engine may be AI-assisted only under governance, records, human review where material, public-safe controls, data controls, cybersecurity controls, privacy controls, sovereign data controls, protected knowledge controls, and correction controls.
8.1.6(b) AI assistance may support retrieval, classification, summarization, comparison, anomaly detection, contradiction detection, source matching, entity resolution, translation support, routing support, dispute flagging, stale-evidence detection, missing-evidence identification, public-safe drafting support, metadata generation, and correction workflow support, provided that AI assistance does not become AI authority.
8.1.6(c) Material AI-assisted Nexus Truth Engine work shall be supported by model registration, dataset registration where applicable, system cards where applicable, model cards where applicable, benchmark cards where applicable, inference records where material, retrieval records where material, prompt or input records where material and safe, human review requirements, access controls, output limits, and correction paths.
8.1.6(d) AI systems used in the Nexus Truth Engine shall be governed against hallucination, bias, drift, overconfidence, data leakage, prompt injection, insecure integration, unauthorized tool use, agentic overreach, hidden training use, cross-border transfer, vendor capture, model dependency, public authority overclaim, finance overclaim, provider preference, sponsor influence, and public-safe publication failure.
8.1.6(e) Rights-bearing data, public authority restricted data, cyber-sensitive data, infrastructure-sensitive data, health-sensitive data, sovereign-sensitive data, finance-sensitive data, community-protected data, Indigenous knowledge, local knowledge, protected knowledge, source-protected information, and confidential materials shall not be processed through AI systems within the Nexus Truth Engine unless lawful, authorized, classification-compliant, secure, purpose-bound, records-valid, and consistent with public-safe publication and safeguard requirements.
8.1.6(f) Human review shall be required where AI outputs materially affect evidence meaning, confidence, uncertainty, public-safe classification, public authority interpretation, finance-facing interpretation, provider-facing interpretation, sponsor-facing interpretation, protected knowledge treatment, community safeguard treatment, technical baseline status, correction status, or public claims.
8.1.6(g) AI-generated outputs, summaries, scores, classifications, confidence estimates, dispute flags, translations, routing suggestions, or public-safe drafts shall not create certification, recognition, finance-readiness, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, market authority, infrastructure operation, or execution consequence by default.
8.1.6(h) The controlling rule shall be that AI may assist the Nexus Truth Engine only where it remains governed, recorded, reviewed, bounded, safe, and correctionable.
8.1.7 Nexus Truth Engine as Interoperable With Nexus Observatory, Nexus Network, Nexus Risk Management, Nexus Rails, Nexus Grid, GRF, GRA, Nexus Standards / Protocol Authority, National Consortiums, National Companies, Project SPVs, Public Authorities, Providers, Hosts, Universities, and Communities. 8.1.7(a) The Nexus Truth Engine may be interoperable with Nexus Observatory, Nexus Network, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Universe, Nexus Competence Cells, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards / Protocol Authority, Global Nexus Consortium, Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, National Consortium Companies, Project SPVs, public authorities, providers, hosts, sponsors, universities, laboratories, communities, Indigenous institutions, civil society actors, media actors, and capital readers.
8.1.7(b) Interoperability shall mean controlled exchange, reference, routing, comparison, handoff, evidence linkage, method linkage, confidence linkage, correction linkage, vocabulary linkage, dependency linkage, and public-safe summary linkage. It shall not mean legal merger, shared liability, shared treasury, agency, partnership, joint venture, parent-subsidiary status, alter ego status, shared employer status, public authority delegation, finance authority, protocol authority, recognition authority, procurement authority, certification authority, or execution authority.
8.1.7(c) Interoperability with Nexus Observatory shall support observability evidence, node evidence, sensor evidence, AI-RAN signal evidence, DePIN evidence, geospatial evidence, cyber telemetry, digital twin assumptions, dashboard methods, public-safe evidence outputs, confidence treatment, uncertainty treatment, public-safe classification, and correction routing without making GCRI Canada an infrastructure operator, emergency commander, or public warning authority.
8.1.7(d) Interoperability with GRF shall support evidence inputs, method inputs, public-safe reporting inputs, Docket inputs, Grid inputs, recognition-supporting evidence inputs, maturity-supporting evidence inputs, claims-discipline support, and correction records without making GCRI Canada the issuer of GRF recognition, standing, maturity records, claims determinations, stakeholder formation, public-facing legitimacy, or public-safe reporting status.
8.1.7(e) Interoperability with GRA shall support evidence inputs, risk evidence, host readiness evidence, node evidence, Proof Pack components, insurance-readiness inputs, capital-reader literacy inputs, RNFD inputs, NFD inputs, UNFSD inputs, and correction records without making GCRI Canada the issuer of finance-readiness, capital-readiness, insurance-readiness, investment advice, underwriting, lending, ratings, guarantees, public finance approval, or capital commitments.
8.1.7(f) Interoperability with Nexus Standards / Protocol Authority shall support evidence requirements, method profiles, ontologies, schemas, controlled vocabulary, technical baselines, proof-receipt logic, public-good software, reference architectures, conformance-supporting tools, and correction records without making GCRI Canada the issuer of protocol effect, role keys, smart licenses, entitlement states, conformance determinations, certification, or external force.
8.1.7(g) Interoperability with National Consortium Companies, Project SPVs, providers, hosts, and enterprise-stack actors shall support evidence understanding, technical baseline interpretation, observability methods, public-safe outputs, and correction records without creating execution authority, asset ownership, operational control, investment recommendation, procurement preference, provider endorsement, finance-readiness, rating, guarantee, or market consequence by GCRI Canada.
8.1.7(h) Interoperability with public authorities shall support public authority learning, evidence literacy, technical literacy, AI literacy, cyber literacy, systems-risk understanding, public-safe interpretation, and correction records without creating public authority delegation, public adoption, regulatory approval, procurement approval, funding approval, public finance approval, official guidance, public warning, emergency command, or sovereign obligation.
8.1.7(i) Interoperability with universities, laboratories, communities, Indigenous institutions, civil society actors, and media actors shall support research integrity, technical challenge, community safeguards, protected knowledge handling, public-safe communication, public legibility, and correction without creating governance capture, public voice confusion, protected knowledge misuse, or public overclaim.
8.1.7(j) The controlling rule shall be that the Nexus Truth Engine may interoperate widely only by preserving role boundaries, records, public-safe controls, dependency tracking, and correction paths at every interface.
8.1.8 Nexus Truth Engine as Not an Absolute Oracle, Final Arbiter, Official Truth Source, Public Law Source, or Unchallengeable Determination. 8.1.8(a) The Nexus Truth Engine shall not be represented or treated as an absolute oracle, final arbiter, official truth source, public law source, sovereign truth source, regulatory truth source, market truth source, public authority finding, public warning source, certification source, finance-readiness source, recognition source, protocol authority source, or unchallengeable determination.
8.1.8(b) The Nexus Truth Engine shall not produce truth by institutional assertion, automation, AI output, dashboard presentation, model confidence, majority agreement, sponsor funding, provider documentation, public authority attendance, media repetition, blockchain anchoring, DePIN proof, proof receipt, or technical display.
8.1.8(c) Nexus Truth Engine outputs shall remain evidence artifacts whose meaning depends on source authority, source lineage, method, confidence, uncertainty, limitations, classification, review, public-safe status, audience, permitted use, prohibited use, boundary language, and correction path.
8.1.8(d) A Nexus Truth Engine output may be strong, useful, technically sophisticated, widely relied upon, public-safe, or highly confidence-supported without becoming final, absolute, legal, public authority, financial, certification, recognition, protocol, procurement, or execution authority.
8.1.8(e) Disagreement, challenge, dispute, uncertainty, missing data, conflicting evidence, stale evidence, correction, downgrade, supersession, withdrawal, or retraction shall not be treated as system failure. Such conditions are part of responsible public-good truth stewardship.
8.1.8(f) Where a Nexus Truth Engine output is presented or perceived as final, official, oracle-like, unchallengeable, public authority-backed, finance-backed, recognition-backed, protocol-effective, certification-like, or execution-ready, GCRI Canada shall correct, relabel, restrict, reissue, withdraw, or clarify the output as appropriate.
8.1.8(g) No public material, interface, dashboard, map, API, repository, technical baseline, evidence pack, decision pack, public authority material, finance-facing material, provider material, sponsor material, Nexus material, Academy material, media statement, or AI-generated summary shall describe the Nexus Truth Engine in a manner inconsistent with the non-oracle rule.
8.1.8(h) The controlling rule shall be that the Nexus Truth Engine exists to make truth claims more disciplined, not to make them unchallengeable.
8.1.9 Nexus Truth Engine as a Public-Good Methods Domain Stewarded by GCRI Canada Within Its Non-Executing Boundary. 8.1.9(a) GCRI Canada shall steward the Nexus Truth Engine as a public-good methods domain within GCRI Canada’s non-executing boundary.
8.1.9(b) GCRI Canada’s stewardship may include method design, method registration, evidence-category design, confidence logic, uncertainty logic, source-comparison logic, dispute logic, correction logic, ontology support, controlled vocabulary support, public-safe publication support, technical documentation, public-good software support, AI-governance support, model-governance support, observability-method support, interface support, and correction assurance.
8.1.9(c) GCRI Canada’s stewardship of the Nexus Truth Engine shall remain distinct from GRF recognition, GRA finance-readiness, Protocol Authority effect, public authority decision-making, procurement decisions, certification decisions, provider selection, sponsor control, National Company execution, Project SPV execution, regulated professional advice, financial activity, market activity, emergency command, public warning, and infrastructure operation.
8.1.9(d) GCRI Canada may maintain or contribute to Nexus Truth Engine public-good software, schemas, APIs, reference architectures, technical baselines, evidence-class logic, confidence logic, and correction tools, provided that such technical stewardship does not create protocol authority, certification, recognition, finance-readiness, public authority meaning, provider preference, sponsor control, procurement advantage, market infrastructure, or execution authority.
8.1.9(e) Nexus Truth Engine methods shall be stewarded as public-good assets subject to anti-capture, anti-enclosure, anti-drift, anti-substitution, public-good stack separation, enterprise-stack separation, privacy, cybersecurity, sovereign data, protected knowledge safeguards, public-safe publication, validity-by-record, and correctionability.
8.1.9(f) Sponsors, donors, funders, providers, hosts, public authorities, capital readers, universities, technical contributors, AI model providers, cloud providers, repository maintainers, or other participants may support Nexus Truth Engine methods only under support-without-control, provider-neutrality, public-safe, records-valid, and correctionable conditions.
8.1.9(g) Where stewardship of Nexus Truth Engine methods creates risk of authority inflation, public authority confusion, finance overclaim, provider preference, sponsor control, protocol drift, certification drift, recognition drift, procurement implication, market reliance, or execution by stealth, GCRI Canada shall narrow, reclassify, restrict, correct, hand off, or refuse the activity.
8.1.9(h) The controlling rule shall be that GCRI Canada may steward Truth Engine methods only so long as stewardship remains public-good, non-executing, role-bounded, and correctionable.
8.1.10 Nexus Truth Engine Outputs as Record-Bound Artifacts Whose Meaning Depends on Source Authority, Method, Review, Status, Audience, and Boundary Language. 8.1.10(a) Nexus Truth Engine outputs shall be record-bound artifacts whose meaning depends on source authority, method, review, status, audience, boundary language, confidence, uncertainty, limitations, public-safe classification, access class, handling class, permitted use, prohibited use, dependency links, and correction path.
8.1.10(b) Nexus Truth Engine outputs may include evidence comparison records, source comparison records, confidence notes, uncertainty notes, contradiction flags, corroboration flags, dispute flags, stale-evidence flags, missing-evidence flags, spoof-risk flags, correction triggers, routing notes, public-safe summaries, controlled summaries, dashboard indicators, map indicators, Evidence Pack inputs, Decision Pack inputs, Docket inputs, Grid inputs, Observatory inputs, Rails handoff notes, GRF input notes, GRA input notes, Protocol Authority support notes, public authority learning notes, and public claim support notes.
8.1.10(c) Each material Nexus Truth Engine output shall identify or link to, where appropriate, the evidence records used, source lineage, method records, dataset records, model records, observability records, ontology terms, confidence treatment, uncertainty treatment, limitation treatment, review status, public-safe status, audience, intended use, prohibited use, and correction path.
8.1.10(d) Audience shall be part of meaning. A controlled-room output, public authority learning output, GRF-facing output, GRA-facing output, Protocol Authority-facing output, provider-facing output, sponsor-facing output, community-facing output, finance-facing output, Board-facing output, public-safe output, or public output shall not be assumed to carry the same meaning, permitted use, boundary condition, or disclosure status.
8.1.10(e) Status shall be part of meaning. Draft, experimental, pilot, internal, controlled, public-safe, released, restricted, disputed, corrected, superseded, withdrawn, retracted, downgraded, suspended, reinstated, retired, and archived outputs shall be distinguished.
8.1.10(f) Boundary language shall be part of meaning. A Nexus Truth Engine output shall state or preserve, where material, that it does not create certification, recognition, finance-readiness, investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.1.10(g) Where a Nexus Truth Engine output is re-used, excerpted, summarized, translated, embedded, visualized, published, routed, exported, included in a dashboard, included in a map, used in a Decision Pack, used in an Evidence Pack, incorporated into public-safe output, or referenced in public claims, the receiving use shall preserve source authority, method, review, status, audience limits, boundary language, and correction path.
8.1.10(h) The controlling rule shall be that Nexus Truth Engine outputs do not mean what readers wish them to mean; they mean only what their records, methods, status, audience, limitations, and boundary language permit.
8.2 GCRI Canada’s Truth Engine Methods Role
8.2.1 GCRI Canada as Steward of Truth Engine Methods, Not Sole Owner of Truth. 8.2.1(a) GCRI Canada shall serve as steward of Nexus Truth Engine methods within its public-benefit, non-executing, evidence-and-methods mandate, and shall not be treated as the sole owner of truth, the final arbiter of truth, the public law source of truth, the market source of truth, the official public authority source of truth, or the exclusive institutional source through which all truth claims must pass.
8.2.1(b) GCRI Canada’s Truth Engine methods role shall consist of disciplined stewardship of methods, evidence classes, source comparison logic, confidence rules, corroboration logic, dispute logic, correction triggers, ontology, controlled vocabulary, schemas, data dictionaries, AI-readable knowledge structures, public-safe output methods, model governance, evaluation records, and correction pathways.
8.2.1(c) GCRI Canada may design, maintain, test, publish in public-safe form, restrict, correct, supersede, withdraw, retire, archive, or support adoption of Truth Engine methods, provided that such activities remain evidence-supporting, method-supporting, public-good, records-valid, reviewable, challengeable, and correctionable.
8.2.1(d) GCRI Canada’s stewardship shall not displace local truth, public authority truth, community truth, Indigenous or protected knowledge context, technical source context, legal context, scientific challenge, public-safe limits, or the lawful authority of competent downstream actors.
8.2.1(e) Truth Engine methods shall not create institutional monopoly over evidence interpretation. GCRI Canada shall preserve challenge, dissent, minority evidence, disputed evidence, local context, jurisdictional context, community context, source limitations, uncertainty, and correction pathways.
8.2.1(f) GCRI Canada shall not allow its Truth Engine methods role to be used to suppress legitimate disagreement, foreclose lawful public authority judgment, replace GRF recognition processes, replace GRA finance-readiness processes, replace Protocol Authority processes, override public authority duties, privilege sponsors or providers, or create execution consequence by implication.
8.2.1(g) Where GCRI Canada’s stewardship of Truth Engine methods is described by participants, sponsors, providers, public authorities, capital readers, media, Nexus entities, or downstream actors as ownership of truth, final authority, official approval, recognition, finance-readiness, certification, public authority determination, or execution clearance, GCRI Canada shall correct, clarify, restrict, or withdraw the misleading description.
8.2.1(h) The controlling rule shall be that GCRI Canada stewards methods for disciplined truth treatment, but truth remains record-bound, context-bound, source-bound, challengeable, and correctionable.
8.2.2 Stewardship of Evidence Classes, Source Comparison Logic, Confidence Rules, Corroboration Logic, Dispute Logic, Correction Triggers, and Public-Safe Output Methods. 8.2.2(a) GCRI Canada shall steward Truth Engine evidence classes, source comparison logic, confidence rules, corroboration logic, dispute logic, correction triggers, and public-safe output methods as public-good methods infrastructure within the Evidence Rail.
8.2.2(b) Evidence classes stewarded for Truth Engine purposes may include scientific evidence, technical evidence, observational evidence, sensor evidence, AI-RAN and telecommunications signal evidence, DePIN evidence, cyber evidence, geospatial evidence, Earth observation evidence, digital twin evidence, simulation evidence, public authority context evidence, community evidence, Indigenous and local knowledge evidence, field evidence, operator evidence, host evidence, provider evidence, sponsor-supplied evidence, university or laboratory evidence, documentary evidence, legal-context evidence, public records, finance-readiness input evidence, risk evidence, resilience evidence, infrastructure evidence, WEFH evidence, health evidence, climate evidence, energy evidence, supply-chain evidence, and public trust evidence.
8.2.2(c) Source comparison logic shall address, where material, source identity, source independence, source conflict, source authority, source reliability, provenance, custody, permissions, licensing, lawful basis, consent or non-consent treatment where applicable, public authority authority, community authority, Indigenous or protected knowledge context, source completeness, source bias, source recency, source consistency, and source limitations.
8.2.2(d) Confidence rules shall address evidence quality, method quality, completeness, timeliness, calibration, reproducibility, corroboration, contradiction, source independence, missing data, stale data, disputed data, model dependence, AI dependence, sensor quality, spoof risk, cyber integrity, geospatial precision, benchmark conditions, and public-safe status.
8.2.2(e) Corroboration logic shall distinguish corroboration, triangulation, replication, independent confirmation, partial support, contextual support, weak support, unverified support, conflicting support, source-dependent support, model-dependent support, and unsupported assertion.
8.2.2(f) Dispute logic shall identify contested evidence, incompatible sources, unresolved uncertainty, conflicting methods, contradictory signals, stale records, disputed classifications, public authority disagreement, community challenge, protected knowledge concerns, provider-supplied disputes, sponsor-supplied disputes, and downstream reliance concerns.
8.2.2(g) Correction triggers shall include source-lineage defects, data errors, method errors, confidence defects, uncertainty defects, classification errors, public-safe errors, ontology errors, model errors, observability errors, dashboard errors, map errors, overclaims, boundary risks, privacy risks, cybersecurity risks, sovereign data risks, protected knowledge risks, community harm risks, public authority ambiguity, finance overclaim, provider preference, sponsor influence, and Nexus role confusion.
8.2.2(h) Public-safe output methods shall determine how Truth Engine outputs may be summarized, redacted, aggregated, generalized, withheld, restricted, published, corrected, superseded, withdrawn, retracted, or reissued without creating unsafe disclosure, false certainty, public authority confusion, finance overclaim, provider preference, sponsor control, public warning implication, or execution consequence.
8.2.2(i) The controlling rule shall be that Truth Engine methods must discipline how evidence is compared, weighted, disputed, corrected, and communicated without converting method outputs into authority.
8.2.3 Stewardship of Truth Engine Ontology, Controlled Vocabulary, Schemas, Data Dictionaries, and AI-Readable Knowledge Structures. 8.2.3(a) GCRI Canada shall steward Truth Engine ontology, controlled vocabulary, schemas, data dictionaries, semantic mappings, crosswalks, equivalence notes, divergence logs, localization notes, compatibility notes, and AI-readable knowledge structures.
8.2.3(b) Truth Engine ontology shall support consistent treatment of evidence classes, source types, method types, confidence states, uncertainty states, dispute states, correction states, public-safe states, access classes, handling classes, technology domains, risk domains, public authority contexts, finance-facing contexts, provider contexts, sponsor contexts, community contexts, Nexus interface states, and downstream dependency states.
8.2.3(c) Controlled vocabulary shall govern terms including evidence, source, lineage, provenance, custody, verified, validated, corroborated, disputed, corrected, superseded, withdrawn, retracted, confidence, uncertainty, limitation, public-safe, restricted, decision-grade, technical truth, recognition, finance-readiness, maturity, standing, certification, protocol effect, proof receipt, Docket, Grid, Observatory, Truth Engine, AI-assisted, model output, dashboard output, public authority, provider, sponsor, host, public-good stack, enterprise stack, non-execution, and correctionability.
8.2.3(d) Schemas and data dictionaries shall identify, where material, required fields, optional fields, prohibited fields, source fields, method fields, confidence fields, uncertainty fields, classification fields, public-safe fields, access fields, handling fields, correction fields, dependency fields, boundary-language fields, and archive fields.
8.2.3(e) AI-readable knowledge structures shall be designed to preserve role separation, source lineage, public-safe status, classification, access controls, confidence, uncertainty, limitations, permitted use, prohibited use, and correction paths when used for retrieval, summarization, classification, comparison, routing, or public-safe drafting support.
8.2.3(f) Truth Engine ontology and AI-readable structures shall not encode or imply authority beyond the record. Schema fields, metadata labels, badges, categories, scores, status names, API responses, and machine-readable outputs shall not create certification, recognition, finance-readiness, public authority meaning, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, market authority, infrastructure operation, or execution consequence by default.
8.2.3(g) Where ontology, controlled vocabulary, schemas, data dictionaries, translations, localization notes, mappings, or AI-readable knowledge structures create ambiguity, overclaim, unsafe inference, public authority confusion, finance-facing confusion, provider preference, sponsor control, protected knowledge risk, or public-safe risk, GCRI Canada shall correct, restrict, supersede, withdraw, or reissue the relevant semantic structure.
8.2.3(h) The controlling rule shall be that Truth Engine meaning must be governed at the semantic layer because uncontrolled language and machine-readable labels can create authority by stealth.
8.2.4 Stewardship of Truth Engine Model Governance, Inference Records, Evaluation Harnesses, and Benchmark Cards. 8.2.4(a) GCRI Canada shall steward Truth Engine model governance, inference records, evaluation harnesses, benchmark cards, system cards, model cards, dataset cards where applicable, test cards, validation-sprint cards, and related technical evidence cards for material Truth Engine systems and methods.
8.2.4(b) Model governance shall address model identity, model type, owner where known, custodian, steward, provider where any, developer where any, version, purpose, scope, training status, fine-tuning status, embedding status, retrieval status, inference status, deployment status, access status, public-safe status, AI-use status, dataset dependencies, benchmark dependencies, evaluation records, human review requirements, permitted use, prohibited use, correction path, supersession path, withdrawal path, retirement path, and archive path.
8.2.4(c) Inference records shall be maintained where material to evidence meaning, public-safe output, public authority interpretation, finance-facing interpretation, provider-facing interpretation, sponsor-facing interpretation, protected knowledge treatment, community safeguard treatment, correction, or downstream dependency review.
8.2.4(d) Evaluation harnesses shall be used, where appropriate, to test Truth Engine methods, AI-assisted components, retrieval systems, classification systems, source-comparison systems, confidence logic, dispute logic, correction triggers, public-safe output methods, dashboard outputs, map outputs, and integration pathways.
8.2.4(e) Benchmark cards shall identify benchmark purpose, benchmark method, dataset or test corpus, evaluation criteria, conditions, limitations, reproducibility status, baseline comparisons where any, confidence, uncertainty, exclusions, prohibited claims, public-safe status, provider-neutrality status, sponsor non-control status, and correction path.
8.2.4(f) Truth Engine model governance shall address hallucination, bias, drift, unsafe summarization, overconfident classification, missing context, prompt injection, data leakage, unauthorized retrieval, embedding misuse, model dependency, provider dependency, hidden training use, cross-border transfer, protected knowledge misuse, public authority overclaim, finance overclaim, provider preference, sponsor influence, and public-safe publication failure.
8.2.4(g) Model outputs, inference records, evaluation results, benchmark results, system cards, model cards, dataset cards, validation-sprint cards, and technical evidence cards shall not create certification, recognition, finance-readiness, investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.2.4(h) Where a Truth Engine model, evaluation harness, benchmark card, inference record, or related technical evidence card is corrected, challenged, reclassified, restricted, superseded, withdrawn, retired, or archived, affected downstream outputs and dependencies shall be reviewed.
8.2.4(i) The controlling rule shall be that Truth Engine model governance must make automated support inspectable, bounded, testable, challengeable, and correctable.
8.2.5 Stewardship of Truth Engine Public-Safe Dashboards, Reports, Summaries, and Controlled Annex Methods. 8.2.5(a) GCRI Canada shall steward methods for Truth Engine public-safe dashboards, public-safe reports, public-safe summaries, public-safe visualizations, technical notes, controlled annexes, controlled-room outputs, public authority learning materials, finance-facing summaries, provider-facing summaries, sponsor-facing summaries, host-facing summaries, community-facing summaries, Academy materials, and public-safe correction notices.
8.2.5(b) Public-safe dashboard methods shall address dashboard purpose, audience, source records, method records, update frequency, latency, confidence display, uncertainty display, limitations, public-safe status, access class, handling class, geospatial treatment, visual labels, colors, filters, scores, warnings, legends, captions, tooltips, boundary language, correction path, supersession path, withdrawal path, and archive path.
8.2.5(c) Report and summary methods shall address source selection, evidence selection, method selection, redaction, aggregation, generalization, responsible non-disclosure, public-safe framing, confidence language, uncertainty language, limitation language, audience limits, permitted use, prohibited use, public authority boundary language, finance boundary language, provider-neutrality language, sponsor non-control language, recognition boundary language, protocol-effect boundary language, and correction language.
8.2.5(d) Controlled annex methods shall address what may be disclosed only under controlled access, including restricted evidence, public authority evidence, health-sensitive evidence, cyber-sensitive evidence, infrastructure-sensitive evidence, finance-sensitive evidence, commercially sensitive evidence, personal information, rights-bearing data, sovereign data, community-protected data, Indigenous or local knowledge, protected knowledge, controlled technology, source-protected information, and other sensitive material.
8.2.5(e) Truth Engine public-safe dashboards, reports, summaries, and annexes shall not create public warning, emergency command, public authority decision, official guidance, finance-readiness, investment advice, procurement approval, provider endorsement, sponsor approval, recognition, certification, rating, guarantee, protocol effect, operational clearance, legal status, market authority, infrastructure operation, or execution consequence by default.
8.2.5(f) Where public-safe dashboards, reports, summaries, or controlled annexes use maps, geospatial layers, scores, colors, alerts, risk indicators, resilience indicators, confidence indicators, AI summaries, model outputs, digital twin outputs, DePIN records, sensor records, or proof receipts, GCRI Canada shall ensure that presentation methods do not create false precision, public warning implication, finance implication, provider preference, sponsor validation, public authority confusion, or unbounded public reliance.
8.2.5(g) Where a dashboard, report, summary, annex, visualization, or public-safe output becomes inaccurate, incomplete, stale, unsafe, overbroad, overclaimed, misclassified, misused, or no longer fit for purpose, GCRI Canada shall correct, reclassify, restrict, supersede, withdraw, retract, or reissue the output and review downstream dependencies.
8.2.5(h) The controlling rule shall be that Truth Engine public-safe outputs must make evidence legible without making it unsafe, final, official, financial, certification-like, recognition-like, or executable.
8.2.6 Truth Engine Methods Support to GRF Without Issuing Recognition, Standing, Claims Approval, Maturity Records, or Public-Facing Legitimacy. 8.2.6(a) GCRI Canada may provide Truth Engine methods support to The Global Risks Forum (GRF), including evidence classes, source comparison logic, confidence rules, corroboration logic, dispute logic, correction triggers, public-safe output methods, ontology support, controlled vocabulary, Docket inputs, Grid inputs, recognition-supporting evidence inputs, maturity-context evidence inputs, claims-discipline support, and public-safe reporting support.
8.2.6(b) Truth Engine methods support to GRF shall remain technical evidence and methods support. It shall not constitute GRF recognition, standing, maturity record, claims approval, stakeholder formation, public-facing legitimacy, public-safe reporting status, registry status, public claim approval, or any other GRF act by GCRI Canada.
8.2.6(c) GRF shall remain responsible for any GRF recognition, standing, maturity record, claims discipline, public-facing legitimacy, stakeholder formation, public-safe reporting, or registry act created through GRF’s own authority, records, procedures, review, and boundary language.
8.2.6(d) GCRI Canada shall not describe Truth Engine methods support, Evidence Packs, Decision Packs, confidence notes, source-comparison outputs, dispute flags, correction triggers, Docket inputs, Grid inputs, or public-safe summaries as GRF approval unless GRF has separately created the relevant status through its own proper record.
8.2.6(e) Truth Engine methods support to GRF shall preserve source lineage, method records, confidence, uncertainty, limitations, public-safe status, access class, handling class, permitted use, prohibited use, correction path, supersession path, withdrawal path, retraction path where applicable, and dependency records.
8.2.6(f) Where GCRI Canada materials are incorporated into GRF-facing records, public-facing GRF materials, Docket materials, Grid materials, recognition-supporting materials, or claims-discipline materials, the interface shall preserve role separation between evidence support and GRF public-facing legitimacy.
8.2.6(g) Where a GCRI Canada Truth Engine output is misdescribed as GRF recognition, GRF standing, GRF maturity, GRF claims approval, or GRF public-facing legitimacy, GCRI Canada shall coordinate appropriate correction with GRF where necessary and shall update relevant records.
8.2.6(h) The controlling rule shall be that GCRI Canada may support GRF truth discipline but shall not issue GRF legitimacy.
8.2.7 Truth Engine Methods Support to GRA Without Issuing Finance-Readiness, Capital-Readiness, Insurance-Readiness, Routeability, Ratings, Guarantees, or Public Finance Approval. 8.2.7(a) GCRI Canada may provide Truth Engine methods support to The Global Risks Alliance (GRA), including evidence classes, risk evidence methods, source comparison logic, confidence rules, corroboration logic, dispute logic, correction triggers, public-safe output methods, finance-boundary methods, host readiness evidence inputs, node evidence inputs, Proof Pack component methods, insurance-readiness input methods, capital-reader literacy methods, RNFD input methods, NFD input methods, UNFSD input methods, and correction records.
8.2.7(b) Truth Engine methods support to GRA shall remain technical evidence and methods support. It shall not constitute GRA finance-readiness, capital-readiness, insurance-readiness, routeability, capital suitability, investor suitability, bankability, fundability, investment advice, securities recommendation, brokerage, placement, finder activity, lending, underwriting, insurance placement, rating, guarantee, public finance approval, capital commitment, or any other financial or regulated-market act by GCRI Canada.
8.2.7(c) GRA shall remain responsible for any GRA finance-readiness, capital-readiness, insurance-readiness, capital readability, Proof Pack, capital-reader room, RNFD, NFD, UNFSD, or regulated-perimeter output created through GRA’s own authority, records, procedures, review, and finance-safe boundary language.
8.2.7(d) GCRI Canada shall not describe Truth Engine methods support, Evidence Packs, Decision Packs, risk evidence, confidence notes, source-comparison outputs, dispute flags, correction triggers, Proof Pack inputs, host readiness evidence, node evidence, Rails handoffs, or finance-facing summaries as finance-readiness, capital-readiness, insurance-readiness, investment recommendation, rating, guarantee, public finance approval, or capital commitment.
8.2.7(e) Truth Engine methods support to GRA shall preserve source lineage, method records, confidence, uncertainty, limitations, finance-safe status, public-safe status, access class, handling class, permitted use, prohibited use, correction path, supersession path, withdrawal path, retraction path where applicable, and dependency records.
8.2.7(f) Where GCRI Canada materials are incorporated into GRA-facing records, capital-reader rooms, Proof Packs, insurance-readiness inputs, RNFD inputs, NFD inputs, UNFSD inputs, Rails handoffs, or finance-facing materials, the interface shall preserve role separation between evidence support and finance-readiness.
8.2.7(g) Where a GCRI Canada Truth Engine output is misdescribed as GRA finance-readiness, capital-readiness, insurance-readiness, routeability, rating, guarantee, public finance approval, investment advice, or capital commitment, GCRI Canada shall coordinate appropriate correction with GRA where necessary and shall update relevant records.
8.2.7(h) The controlling rule shall be that GCRI Canada may support GRA evidence discipline but shall not issue finance-readiness or financial consequence.
8.2.8 Truth Engine Methods Support to Nexus Standards / Protocol Authority Without Creating Protocol Effect by Default. 8.2.8(a) GCRI Canada may provide Truth Engine methods support to Nexus Standards / Protocol Authority, including evidence requirements, method profiles, source comparison logic, confidence rules, dispute logic, correction triggers, ontology, controlled vocabulary, schemas, data dictionaries, proof-receipt logic, technical baselines, public-good software, APIs, reference architectures, conformance-supporting tools, evaluation harnesses, benchmark cards, and correction records.
8.2.8(b) Truth Engine methods support to Nexus Standards / Protocol Authority shall remain evidence and methods support. It shall not constitute protocol authority, certification, conformance determination, role key issuance, smart-license issuance, entitlement state, proof-receipt legal effect, external force, legal validity, operational clearance, or protocol effect by default.
8.2.8(c) Nexus Standards / Protocol Authority shall remain responsible for any protocol effect, conformance logic, role keys, smart licenses, proof receipts, entitlement states, anchoring discipline, technical validity surface, external force, or standards effect created through its own authority, instruments, records, procedures, and boundary language.
8.2.8(d) Technical authorship, method authorship, schema authorship, API authorship, repository custody, software maintenance, benchmark support, evaluation support, or proof-receipt support by GCRI Canada shall not create protocol supremacy, certification, conformance status, entitlement, legal effect, public authority meaning, finance-readiness, provider preference, procurement advantage, or execution authority.
8.2.8(e) Truth Engine methods support to Protocol Authority shall preserve source lineage, method records, versioning, review status, confidence, uncertainty, limitations, public-safe status, access class, handling class, permitted use, prohibited use, correction path, supersession path, withdrawal path, retirement path, and dependency records.
8.2.8(f) Where GCRI Canada materials are incorporated into protocol-facing records, technical baselines, schemas, APIs, conformance-supporting tools, proof-receipt templates, smart-license support materials, role-key support materials, or standards-support materials, the interface shall preserve role separation between method support and protocol effect.
8.2.8(g) Where a GCRI Canada Truth Engine method, technical baseline, schema, proof-receipt support artifact, benchmark, evaluation harness, or public-good software artifact is misdescribed as protocol authority, certification, conformance determination, role key, smart license, entitlement state, or external legal effect, GCRI Canada shall coordinate appropriate correction with the relevant Protocol Authority where necessary and shall update relevant records.
8.2.8(h) The controlling rule shall be that GCRI Canada may support protocol truth discipline but shall not create protocol effect by default.
8.2.9 Truth Engine Methods Support to Public Authorities Without Creating Public Authority Decisions, Public Warnings, Emergency Commands, or Regulatory Determinations. 8.2.9(a) GCRI Canada may provide Truth Engine methods support to public authorities for public authority learning, evidence literacy, technical literacy, AI literacy, cyber literacy, scenario learning, systems-risk understanding, public-safe interpretation, source-comparison support, confidence treatment, uncertainty treatment, dispute awareness, correction awareness, and decision-support literacy.
8.2.9(b) Truth Engine methods support to public authorities shall not create public authority decisions, public warnings, emergency commands, regulatory determinations, procurement approvals, funding approvals, public finance approvals, permits, licenses, safe harbors, enforcement positions, official guidance, public adoption, public health orders, public safety directives, sovereign obligations, or delegated public authority.
8.2.9(c) Public authorities shall remain responsible for their own lawful decisions, regulatory actions, procurement actions, funding actions, public finance actions, emergency actions, public warnings, official guidance, public communications, and public accountability through their own authority, procedures, records, legal duties, and public law frameworks.
8.2.9(d) Truth Engine methods support to public authorities shall preserve capacity classification, public authority data classification, lawful basis, permitted use, prohibited use, non-delegation language, non-endorsement language, non-reliance language where appropriate, public-safe status, access status, handling class, confidence, uncertainty, limitations, and correction path.
8.2.9(e) Public authority names, logos, titles, quotes, photos, agency references, jurisdiction references, data contributions, public finance references, regulator-listening references, emergency-management references, and public-sector participation references shall be used only under approved reference controls and shall not imply endorsement, adoption, delegation, procurement approval, funding approval, regulatory approval, public finance approval, official warning, or sovereign obligation.
8.2.9(f) Where Truth Engine outputs are used in public authority learning materials, dashboards, maps, public-safe briefings, controlled annexes, scenario exercises, emergency-management learning, public-sector workshops, or regulator-listening contexts, GCRI Canada shall preserve the distinction between evidence support and public authority action.
8.2.9(g) Where a GCRI Canada Truth Engine method or output is misdescribed as a public authority decision, official warning, emergency command, regulatory determination, procurement approval, funding approval, public finance approval, public adoption, official guidance, or sovereign obligation, GCRI Canada shall correct, clarify, restrict, withdraw, or reissue the relevant material and notify affected public authority interfaces where appropriate.
8.2.9(h) The controlling rule shall be that GCRI Canada may support public authority learning through Truth Engine methods, but public authority remains with public authorities.
8.2.10 Truth Engine Methods Support to National Companies, Project SPVs, Providers, and Hosts Without Creating Procurement Preference, Investment Recommendation, Certification, or Execution Authority. 8.2.10(a) GCRI Canada may provide Truth Engine methods support to National Consortium Companies, Project SPVs, qualified providers, vendors, contractors, hosts, and other enterprise-stack or support actors for evidence understanding, technical baseline interpretation, observability method support, public-safe output support, source-comparison support, confidence treatment, uncertainty treatment, correction routing, and boundary-safe handoff.
8.2.10(b) Truth Engine methods support to National Companies, Project SPVs, providers, and hosts shall not create procurement preference, investment recommendation, certification, recognition, finance-readiness, provider endorsement, sponsor approval, project approval, SPV approval, host approval, public authority endorsement, market allocation, rating, guarantee, operational clearance, infrastructure operation, asset ownership, management authority, financing authority, insurance authority, underwriting authority, or execution authority by GCRI Canada.
8.2.10(c) National Companies and Project SPVs shall remain separate enterprise-stack and execution actors responsible for their own lawful corporate acts, contracts, financing, operations, asset ownership, delivery, compliance, risk, liabilities, public claims, provider relationships, host relationships, and execution decisions.
8.2.10(d) Providers, vendors, and contractors shall remain separate delivery actors and shall not acquire preferred status, procurement advantage, certification, recognition, finance-readiness, maturity, public authority endorsement, or Nexus-compatible status merely by contributing to, testing with, referencing, integrating with, or being evaluated through Truth Engine methods.
8.2.10(e) Hosts shall remain support and context contributors, not owners or controllers of GCRI Canada’s evidence, methods, Truth Engine outputs, public-safe publications, technical baselines, public authority access, provider access, finance-facing materials, or institutional meaning.
8.2.10(f) Truth Engine methods support to National Companies, Project SPVs, providers, and hosts shall preserve role records, interface records, source lineage, method records, data agreements, IP agreements, confidentiality terms, cybersecurity controls, privacy controls, sovereign data controls, public authority boundaries, finance boundaries, provider-neutrality controls, sponsor non-control controls, public claims controls, permitted use, prohibited use, and correction path.
8.2.10(g) Where Truth Engine methods support is used in project materials, provider materials, host materials, SPV materials, National Company materials, demonstrations, validation sprints, pilots, technical baselines, dashboards, maps, investor-facing rooms, public authority rooms, procurement-adjacent materials, or public claims, GCRI Canada shall require boundary language sufficient to prevent procurement preference, investment recommendation, certification, recognition, finance-readiness, provider endorsement, sponsor control, public authority approval, or execution implication.
8.2.10(h) Where a National Company, Project SPV, provider, vendor, contractor, host, sponsor, or other enterprise-stack actor misdescribes Truth Engine methods support as approval, certification, endorsement, procurement advantage, investment recommendation, finance-readiness, public authority support, operational clearance, guarantee, or execution authority, GCRI Canada shall require correction, withdrawal, public-safe clarification, controlled notice, interface suspension, termination, or other remedy as appropriate.
8.2.10(i) The controlling rule shall be that Truth Engine methods may support enterprise-stack understanding only by preserving public-good stack separation and never by converting evidence support into procurement, finance, certification, endorsement, or execution.
8.3 Source Comparison Logic
8.3.1 Source Comparison Across Sensors, Reference Sensors, AI-RAN Signals, O-RAN Signals, Private Wireless Signals, DePIN Telemetry, Cyber Logs, Geospatial Data, Earth Observation, Satellite Data, Digital Twins, Operator Observations, Public Authority Context, Community Context, University / Laboratory Outputs, Provider Systems, Sponsor-Supplied Data, and Field Evidence. 8.3.1(a) GCRI Canada shall steward Source Comparison Logic as a Nexus Truth Engine method for comparing, contextualizing, corroborating, challenging, routing, and correcting evidence across heterogeneous sources, including sensors, reference sensors, AI-RAN signals, O-RAN signals, private wireless signals, DePIN telemetry, cyber logs, geospatial data, Earth observation, satellite data, digital twins, operator observations, public authority context, community context, university and laboratory outputs, provider systems, sponsor-supplied data, host inputs, field evidence, public records, documentary evidence, historical records, and model-based outputs.
8.3.1(b) Source Comparison Logic shall support the determination of whether sources are consistent, independent, mutually dependent, partially corroborating, contradictory, stale, incomplete, spoofed, corrupted, biased, context-limited, permission-limited, method-limited, public-safe limited, legally restricted, or unsuitable for the proposed evidence use.
8.3.1(c) Source Comparison Logic shall not presume equivalence among sources merely because they address the same subject, domain, asset, location, hazard, technology, event, system, project, node, cluster, provider, public authority context, community context, or Nexus interface. Each source shall be compared according to its source type, origin, method, custody, context, resolution, latency, confidence, uncertainty, limitation, permission, classification, and correction path.
8.3.1(d) Source Comparison Logic may compare signals and records across technical, human, institutional, community, and automated systems, provided that comparison does not erase local meaning, Indigenous or protected knowledge context, public authority context, rights-bearing data status, sovereign data restrictions, public-safe limits, source permissions, confidentiality obligations, or source-specific uncertainty.
8.3.1(e) Source Comparison Logic shall distinguish reference sources, primary sources, secondary sources, derived sources, machine-generated sources, human-generated sources, public authority sources, community sources, Indigenous or local knowledge sources, provider sources, sponsor sources, host sources, academic sources, field sources, public records, and historical sources.
8.3.1(f) No source comparison output shall create certification, recognition, finance-readiness, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, market authority, infrastructure operation, or execution consequence by default.
8.3.1(g) Where Source Comparison Logic is used in Evidence Packs, Decision Packs, Truth Engine outputs, Observatory outputs, dashboards, maps, Docket records, Grid records, Rails handoffs, GRF inputs, GRA inputs, Protocol Authority support, public authority materials, finance-facing materials, provider materials, sponsor materials, host materials, community-facing materials, Academy materials, public-safe reports, technical baselines, public-good software, or public claims, the comparison shall be records-valid, method-supported, limitation-aware, and correctionable.
8.3.1(h) The controlling rule shall be that source comparison is a disciplined method for understanding evidence relationships, not a mechanism for converting multiple sources into automatic truth or authority.
8.3.2 Source Independence, Source Conflict, Source Reliability, Source Timeliness, Source Permission, Source Bias, and Source Completeness. 8.3.2(a) Source Comparison Logic shall evaluate source independence, source conflict, source reliability, source timeliness, source permission, source bias, and source completeness as material attributes of evidence quality and confidence.
8.3.2(b) Source independence shall assess whether sources are genuinely independent or whether they depend on the same sensor, dataset, provider system, model, public authority feed, sponsor-supplied material, field team, vendor platform, repository, methodology, publication, public record, media narrative, AI-generated summary, or underlying source.
8.3.2(c) Source conflict shall assess whether sources contradict each other, partially diverge, use incompatible methods, describe different time windows, operate at different spatial resolutions, rely on different assumptions, use different definitions, reflect different jurisdictional contexts, or encode different community, public authority, provider, sponsor, or technical perspectives.
8.3.2(d) Source reliability shall assess source integrity, provenance, custody, calibration, validation, reputation for accuracy where relevant, method discipline, historical performance, review status, reproducibility, tamper resistance, spoof resistance, cyber integrity, documentation quality, source transparency, and correction history.
8.3.2(e) Source timeliness shall assess recency, latency, update frequency, stale status, event relevance, time-zone treatment, version currency, supersession status, withdrawal status, retraction status, archive status, and whether a source remains fit for the evidence question at the time of use.
8.3.2(f) Source permission shall assess lawful basis, consent or non-consent where applicable, license, data-sharing authority, public authority authority, community authority, Indigenous or protected knowledge authority, confidentiality restrictions, publication restrictions, AI-use restrictions, transfer restrictions, derivative-use restrictions, and public-safe release status.
8.3.2(g) Source bias shall assess whether source selection, source framing, data collection, method design, dashboard design, model training, sampling, omission, public authority position, sponsor interest, provider interest, host interest, capital-reader interest, media framing, academic incentives, or community context may materially affect evidence interpretation.
8.3.2(h) Source completeness shall assess whether the source covers the relevant time, place, population, system, asset, event, hazard, technology, infrastructure, community, public authority context, provider context, sponsor context, and evidence question, and whether gaps, missing fields, missing data, blind spots, exclusions, redactions, or inaccessible annexes materially affect confidence.
8.3.2(i) Where source independence, conflict, reliability, timeliness, permission, bias, or completeness cannot be adequately established, the source comparison output shall reflect such uncertainty and shall not overstate evidence strength.
8.3.2(j) The controlling rule shall be that sources are not strengthened by being numerous unless their independence, reliability, permission, timeliness, completeness, bias, and conflict status support the comparison.
8.3.3 Machine-Generated Source Treatment. 8.3.3(a) Source Comparison Logic shall apply specific treatment to machine-generated sources, including sensor outputs, reference sensor outputs, AI-RAN signals, O-RAN signals, private wireless signals, DePIN telemetry, cyber logs, system logs, geospatial layers, Earth observation outputs, satellite data, digital twin outputs, simulation outputs, model outputs, AI-generated summaries, automated classifications, dashboard states, proof receipts, blockchain anchors, smart-contract logs, and other machine-produced records.
8.3.3(b) Machine-generated sources shall be evaluated for system identity, device identity, model identity, software version, firmware version where applicable, sensor calibration, clock integrity, location integrity, network integrity, custody, access control, logging integrity, tamper resistance, spoof resistance, cyber integrity, data pipeline integrity, transformation method, aggregation method, inference method, and output limitation.
8.3.3(c) Machine-generated sources shall be evaluated for automation bias, false precision, silent preprocessing, hidden filtering, vendor dependency, model dependency, training-data limits, retrieval limits, dashboard design bias, alert threshold bias, telemetry loss, clock drift, sensor drift, model drift, calibration drift, and pipeline drift.
8.3.3(d) AI-generated or model-generated sources shall not be treated as primary evidence merely because they are fluent, scored, probabilistic, visually persuasive, or generated from large-scale systems. Their evidentiary status shall depend on model record, dataset record, inference record, retrieval record where material, human review where material, source grounding, method, confidence, uncertainty, limitations, and public-safe status.
8.3.3(e) Blockchain entries, DePIN records, hashes, anchors, tokens, smart-contract events, proof receipts, or tamper-evident records shall not be treated as truthful merely because they are time-stamped, signed, distributed, immutable, or cryptographically verifiable. They may evidence that a record or event was asserted, anchored, signed, or transmitted, but shall not by default evidence that the underlying claim is true, complete, lawful, public-safe, authorized, or fit for purpose.
8.3.3(f) Machine-generated sources involving personal information, rights-bearing data, location data, public authority data, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, sovereign data, community-protected data, Indigenous or protected knowledge, or controlled technology shall be subject to heightened classification, access, privacy, cybersecurity, sovereign data, protected knowledge, and public-safe controls.
8.3.3(g) Where machine-generated sources are spoofed, corrupted, interrupted, miscalibrated, adversarially manipulated, incomplete, stale, model-drifted, sensor-drifted, pipeline-drifted, or suspected of compromise, Source Comparison Logic shall flag the condition and route affected evidence for review, reclassification, correction, restriction, supersession, withdrawal, or incident handling as appropriate.
8.3.3(h) The controlling rule shall be that machine generation may improve scale, speed, and repeatability, but it does not eliminate the need for source lineage, method review, human judgment where material, safeguards, and correction.
8.3.4 Human-Generated Source Treatment. 8.3.4(a) Source Comparison Logic shall apply specific treatment to human-generated sources, including field observations, operator observations, expert judgments, researcher notes, public authority statements, community statements, Indigenous or local knowledge contributions, host observations, provider submissions, sponsor submissions, participant reports, interview notes, workshop records, council records, advisory notes, media statements, public comments, and documentary narratives.
8.3.4(b) Human-generated sources shall be evaluated for role, authority, competence, proximity to the event or subject, observation context, time of observation, method of recording, source independence, conflicts of interest, incentives, pressure, memory limits, translation issues, interpretation issues, cultural context, community context, public authority context, confidentiality, consent or non-consent where applicable, and correction path.
8.3.4(c) Human-generated sources shall not be dismissed merely because they are qualitative, local, experiential, community-based, Indigenous, narrative, contextual, or non-instrumental. Their evidentiary treatment shall depend on source context, authority, safeguards, relevance, corroboration where appropriate, limitations, public-safe status, and permitted use.
8.3.4(d) Human-generated sources shall not be over-weighted merely because they come from senior officers, public officials, renowned experts, sponsors, funders, providers, media figures, founders, directors, professors, technical leaders, or persons with high public visibility. Institutional prestige shall not substitute for source lineage, method, review, and conflict treatment.
8.3.4(e) Expert judgment shall be distinguished from direct observation, institutional opinion, professional opinion, regulated professional advice, public authority determination, sponsor view, provider claim, and community testimony. Where regulated professional advice is implicated, GCRI Canada shall apply applicable boundary controls and shall not convert evidence treatment into regulated professional opinion by default.
8.3.4(f) Human-generated sources involving vulnerable persons, protected participants, confidential sources, whistleblowers, youth, public officials in sensitive roles, communities at risk, Indigenous or local knowledge holders, protected knowledge holders, or persons exposed to retaliation shall receive appropriate confidentiality, redaction, access, public-safe, and do-no-harm treatment.
8.3.4(g) Where human-generated sources conflict, Source Comparison Logic shall not resolve conflict by title, seniority, reputation, institutional power, sponsor relationship, provider relationship, public authority rank, media salience, or majority narrative alone. The conflict shall be assessed through source context, evidence support, method, independence, corroboration, limitation, and correction pathway.
8.3.4(h) The controlling rule shall be that human-generated sources are essential to public-good evidence, but they must be handled with context, safeguards, conflict awareness, and records-valid discipline.
8.3.5 Public Authority Source Treatment. 8.3.5(a) Source Comparison Logic shall apply specific treatment to public authority sources, including public authority data, public records, official reports, regulatory materials, emergency-management materials, public health materials, infrastructure materials, public finance materials, procurement materials, administrative data, public-sector dashboards, public authority statements, regulator-listening inputs, and public authority participation records.
8.3.5(b) Public authority sources shall be evaluated for authority, jurisdiction, legal status, publication status, official or non-official character, draft or final status, public or restricted status, statutory context, administrative context, policy context, capacity classification, data authority, permitted use, prohibited use, confidentiality, public-safe status, public authority reference approval, and correction path.
8.3.5(c) Public authority participation, attendance, data contribution, verbal comment, workshop statement, regulator-listening presence, emergency-management presence, public finance presence, procurement presence, or technical learning participation shall not be treated as public authority endorsement, public adoption, official guidance, regulatory approval, procurement approval, funding approval, public finance approval, public warning, emergency command, or sovereign obligation.
8.3.5(d) Public authority sources may carry high evidentiary relevance for legal, jurisdictional, public administration, infrastructure, emergency, health, environment, finance, procurement, or civic context, but such relevance shall not convert GCRI Canada into a public authority or make GCRI Canada outputs public authority decisions.
8.3.5(e) Where public authority sources conflict with community sources, technical sources, provider sources, public records, field evidence, or other public authority sources, Source Comparison Logic shall preserve the conflict, identify the context, record limitations, and route the matter for appropriate review rather than treating official status as automatic resolution.
8.3.5(f) Public authority data involving personal information, sensitive public-sector information, emergency information, health information, critical infrastructure information, procurement information, public finance information, regulatory information, law-enforcement-sensitive information, national security-sensitive information, or restricted administrative information shall be subject to heightened access, classification, privacy, cybersecurity, lawful-use, and public-safe controls.
8.3.5(g) Public authority sources used in public-safe outputs, dashboards, maps, public authority learning materials, GRF inputs, GRA inputs, Protocol Authority support, Docket records, Grid records, Rails handoffs, provider-facing materials, sponsor-facing materials, finance-facing materials, or public claims shall carry appropriate non-delegation, non-endorsement, non-warning, non-procurement, non-finance, and public-safe boundary language where material.
8.3.5(h) The controlling rule shall be that public authority sources may inform evidence, but only public authorities create public authority acts through their own lawful processes.
8.3.6 Community, Indigenous, Local, Territorial, Cultural, Environmental, and Protected Knowledge Source Treatment. 8.3.6(a) Source Comparison Logic shall apply specific treatment to community, Indigenous, local, territorial, cultural, environmental, and protected knowledge sources, including community observations, Indigenous knowledge, local knowledge, territorial knowledge, cultural site knowledge, environmental knowledge, traditional ecological knowledge, lived experience, community risk information, community resilience information, informal infrastructure knowledge, protected knowledge, and knowledge shared under conditions of trust.
8.3.6(b) Such sources shall be treated as rights-bearing, context-bearing, relationship-bearing, and safeguard-bearing sources, not merely as extractive data inputs. Their use shall be governed by authority, consent or non-consent where applicable, community protocol, Indigenous protocol where applicable, cultural context, permitted use, prohibited use, access limits, public-safe limits, withdrawal or challenge pathways where applicable, and do-no-harm controls.
8.3.6(c) Source Comparison Logic shall not flatten community, Indigenous, local, territorial, cultural, environmental, or protected knowledge into generic evidence categories where doing so would erase context, expose sensitive knowledge, misrepresent authority, permit extraction, enable public harm, or breach trust.
8.3.6(d) Where such sources relate to sensitive sites, sacred sites, cultural sites, environmental vulnerabilities, community vulnerabilities, informal survival systems, health-sensitive conditions, migration routes, water sources, food systems, energy systems, local hazards, infrastructure dependencies, or protected persons, GCRI Canada shall apply public-safe mapping, aggregation, redaction, access restriction, controlled annex, or responsible non-disclosure as appropriate.
8.3.6(e) Source comparison involving community or Indigenous sources shall not resolve conflict by subordinating local knowledge to technical instrumentation, public authority records, provider data, sponsor data, academic outputs, or AI-generated summaries merely because those sources appear more formal, quantitative, or machine-readable.
8.3.6(f) Where community or Indigenous sources conflict with other sources, Source Comparison Logic shall record the conflict, preserve context, identify limitations, assess public-safe treatment, and route the matter through appropriate safeguards, community, Indigenous, public authority, legal, or technical review where material.
8.3.6(g) Public-safe outputs derived from community, Indigenous, local, territorial, cultural, environmental, or protected knowledge shall not expose protected persons, sensitive places, cultural knowledge, environmental vulnerabilities, community-protected information, confidential sources, or retaliatory risk.
8.3.6(h) The controlling rule shall be that community and Indigenous knowledge may be essential to truth, but truth treatment must never become extraction, exposure, erasure, or harm.
8.3.7 Provider and Sponsor Source Treatment With Conflict and Influence Controls. 8.3.7(a) Source Comparison Logic shall apply specific treatment to provider-supplied, vendor-supplied, contractor-supplied, sponsor-supplied, donor-supplied, funder-supplied, host-supplied, and capital-reader-supplied sources.
8.3.7(b) Provider sources may include system logs, technical documentation, architecture diagrams, test results, benchmark claims, validation-sprint materials, dashboards, datasets, model cards, system cards, security documents, compliance materials, deployment observations, field reports, incident reports, service records, product claims, and technical representations.
8.3.7(c) Sponsor, donor, funder, host, or capital-reader sources may include funding reports, program narratives, impact claims, host context, site data, facility information, finance-facing materials, public authority access descriptions, project materials, public claims, event materials, and support-related materials.
8.3.7(d) Provider and sponsor source treatment shall include conflict review, influence review, financial-interest review, procurement-risk review, market-advantage review, publication-influence review, method-influence review, data-selection review, benchmark-design review, omission review, public-claims review, and dependency review.
8.3.7(e) Provider or sponsor sources shall not be rejected solely because they are provider-supplied or sponsor-supplied, but they shall not be treated as independent, neutral, complete, authoritative, public authority-approved, finance-ready, certified, recognized, or procurement-relevant without appropriate records, corroboration where needed, conflicts treatment, limitations, and boundary language.
8.3.7(f) Provider benchmarks, sponsor impact claims, host readiness claims, vendor performance claims, implementation claims, technical maturity claims, finance-facing claims, or public authority access claims shall be compared against independent sources where feasible and shall preserve limitations where independent comparison is unavailable.
8.3.7(g) Where provider or sponsor source treatment reveals influence risk, outcome purchase risk, provider preference risk, sponsor control risk, public authority access purchase risk, finance overclaim, procurement implication, benchmark manipulation, selective disclosure, or public claim overreach, GCRI Canada shall route the source or affected output to restriction, conflict disclosure, additional review, correction, reclassification, withdrawal, retraction, interface revision, or refusal as appropriate.
8.3.7(h) The controlling rule shall be that provider and sponsor sources may inform evidence, but they must never buy, steer, suppress, certify, recognize, finance, or execute institutional truth.
8.3.8 Comparison of Raw Data, Processed Data, Model Outputs, Expert Judgments, Public Records, Field Observations, and Historical Records. 8.3.8(a) Source Comparison Logic shall distinguish raw data, processed data, derived data, model outputs, AI outputs, expert judgments, public records, field observations, operator observations, community observations, laboratory outputs, public authority records, provider records, sponsor records, media records, and historical records.
8.3.8(b) Raw data shall be compared with attention to source, collection method, calibration, completeness, timestamp, location, custody, permissions, data class, quality, missingness, corruption, and transformation requirements.
8.3.8(c) Processed or derived data shall be compared with attention to transformation method, aggregation method, cleaning method, filtering method, normalization, deduplication, inference, exclusions, assumptions, software or model dependency, version, and reproducibility.
8.3.8(d) Model outputs and AI outputs shall be compared with attention to model identity, training or retrieval context, dataset dependencies, input conditions, inference records, human review where material, limitations, bias, drift, hallucination, confidence treatment, uncertainty treatment, and public-safe status.
8.3.8(e) Expert judgments shall be compared with attention to expertise, scope, independence, assumptions, method, discipline, conflicts, professional boundary, evidence basis, limitations, and whether the judgment is an individual view, institutional view, regulated professional opinion, or public authority determination.
8.3.8(f) Public records shall be compared with attention to issuing authority, legal status, publication status, date, jurisdiction, scope, official or non-official character, supersession, amendment, withdrawal, public-safe limits, and relevance to the evidence question.
8.3.8(g) Field observations shall be compared with attention to observer identity where safe, role, location, timing, conditions, method of observation, recording method, chain of custody, safety context, community context, public authority context, source protection, and corroboration where appropriate.
8.3.8(h) Historical records shall be compared with attention to date, origin, purpose, archive status, continuity, historical context, prior terminology, jurisdictional context, source bias, missing records, subsequent correction, supersession, and changed present conditions.
8.3.8(i) No source type shall be allowed to dominate comparison solely because it is quantitative, qualitative, official, technical, automated, historical, expert, public, confidential, visually persuasive, or easier to process. Weight shall depend on the evidence question, source lineage, method, context, confidence, uncertainty, limitations, permissions, and public-safe status.
8.3.8(j) The controlling rule shall be that different source forms may illuminate different parts of truth, but comparison must preserve their differences rather than collapse them into a single unsupported score.
8.3.9 Source Comparison Under Missing, Stale, Conflicting, Spoofed, Corrupted, Incomplete, or Contested Conditions. 8.3.9(a) Source Comparison Logic shall include specific treatment for missing, stale, conflicting, spoofed, corrupted, incomplete, or contested source conditions.
8.3.9(b) Missing source conditions shall be recorded where expected sources are absent, inaccessible, unavailable, withheld, not collected, lost, deleted, restricted, unlawfully unavailable, public-safe unavailable, or not yet produced. Missingness shall not be silently treated as absence of risk, absence of event, absence of harm, absence of defect, or absence of evidence.
8.3.9(c) Stale source conditions shall be recorded where sources are outdated, superseded, time-limited, context-changed, no longer maintained, no longer representative, no longer authorized, no longer public-safe, or inconsistent with current conditions.
8.3.9(d) Conflicting source conditions shall be recorded where sources materially disagree, use inconsistent definitions, apply different methods, measure different periods, reflect different jurisdictions, include different populations, encode different assumptions, or produce incompatible conclusions.
8.3.9(e) Spoofed source conditions shall be recorded where signals, records, identities, locations, device outputs, telemetry, AI outputs, DePIN records, blockchain entries, public claims, documents, images, videos, media, or source credentials are suspected or confirmed to be falsified, impersonated, manipulated, fabricated, replayed, adversarially generated, or fraudulently presented.
8.3.9(f) Corrupted source conditions shall be recorded where data, records, logs, files, models, repositories, dashboards, maps, sensors, devices, software, metadata, custody records, or outputs are damaged, compromised, altered, incomplete, mislinked, malformed, insecure, or unreliable.
8.3.9(g) Incomplete source conditions shall be recorded where sources contain partial coverage, missing fields, redactions, omitted context, excluded populations, inaccessible annexes, low resolution, insufficient sampling, limited time windows, limited geography, incomplete chain of custody, or unsupported conclusions.
8.3.9(h) Contested source conditions shall be recorded where affected persons, communities, Indigenous or local knowledge holders, public authorities, providers, sponsors, hosts, universities, technical reviewers, safeguards reviewers, or other credible challengers dispute source meaning, authority, accuracy, permission, context, public-safe treatment, or use.
8.3.9(i) Where any condition under this section materially affects evidence quality, confidence, uncertainty, public-safe status, public authority interpretation, finance-facing interpretation, provider-facing interpretation, sponsor-facing interpretation, community-facing interpretation, Nexus interface meaning, or public claims, GCRI Canada shall route the matter to review, reclassification, correction, downgrade, restriction, supersession, withdrawal, retraction, dispute handling, incident handling, or public-safe clarification as appropriate.
8.3.9(j) The controlling rule shall be that adverse source conditions must be surfaced, not smoothed away, because missingness, staleness, conflict, spoofing, corruption, incompleteness, and contestation are themselves evidence conditions.
8.3.10 Source Comparison Records, Reviewer Records, Method Records, and Correction Paths. 8.3.10(a) GCRI Canada shall maintain, or cause to be maintained, source comparison records for material source comparisons conducted within or in support of the Nexus Truth Engine.
8.3.10(b) Source comparison records shall identify the comparison title or identifier, evidence question, source records compared, source types, source lineage, provenance, custody, permissions, classification, public-safe status, technology domain, risk domain, jurisdictional context, community context where applicable, public authority context where applicable, method used, reviewer, review status, comparison date, version, confidence treatment, uncertainty treatment, limitations, conflicts, missing sources, stale sources, contested sources, source-independence treatment, source-reliability treatment, source-bias treatment, source-completeness treatment, permitted use, prohibited use, dependency links, correction path, supersession path, withdrawal path, and archive path.
8.3.10(c) Reviewer records shall identify the reviewer role, authority, competence, conflict status, access authority, review scope, review method, dissent where any, limitation where any, approval where any, and escalation pathway where the comparison raises material risk.
8.3.10(d) Method records shall identify the source comparison method, method version, scope, assumptions, exclusions, evidence categories supported, technology domains supported, public-safe status, limitations, dependency on AI or models where any, dependency on datasets where any, required human review, and correction path.
8.3.10(e) Source comparison records shall be linked, where applicable, to the Evidence Register, Method Register, Dataset Register, Model Register, Observability Register, Ontology and Controlled Vocabulary Register, Evidence Pack Register, Decision Pack Register, Publication and Public-Safe Output Register, Correction Register, Dependency Register, public authority records, GRF interface records, GRA interface records, Protocol Authority interface records, Nexus interface records, and public claims records.
8.3.10(f) Where a source comparison is corrected, challenged, reclassified, confidence-changed, uncertainty-changed, restricted, superseded, withdrawn, retracted, downgraded, suspended, reinstated, retired, or archived, affected downstream records and outputs shall be reviewed.
8.3.10(g) Source comparison records shall not create certification, recognition, finance-readiness, investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.3.10(h) The controlling rule shall be that source comparison must be recorded because unrecorded comparison cannot be reviewed, challenged, corrected, or safely relied upon as evidence support.
8.4 Corroboration, Contradiction, and Dispute Handling
8.4.1 Corroboration as Method-Based Agreement Across Sources, Not Automatic Truth. 8.4.1(a) GCRI Canada shall treat corroboration as method-based agreement, alignment, reinforcement, or consistency across sources, not as automatic truth, final truth, official truth, public authority truth, recognition, finance-readiness, certification, rating, procurement approval, provider endorsement, sponsor approval, protocol effect, public warning, emergency command, or execution consequence.
8.4.1(b) Corroboration shall require source comparison, source-lineage review, method review, confidence treatment, uncertainty treatment, limitation treatment, classification review, permission review, public-safe review, and dependency review proportionate to the evidence question and risk.
8.4.1(c) Corroboration may arise from independent sources, partially independent sources, methodologically distinct sources, cross-domain sources, repeated measurements, reference sensors, calibrated instruments, public records, field observations, community inputs, public authority context, university or laboratory outputs, provider records, sponsor records, geospatial layers, cyber logs, AI-RAN signals, DePIN records, digital twins, models, or historical records, provided that their relationship, independence, limits, and permitted meanings are recorded.
8.4.1(d) Corroboration shall be distinguished from repetition, duplication, shared-source amplification, dashboard replication, media circulation, sponsor narrative, provider claim repetition, public authority attendance, AI-generated restatement, blockchain anchoring, proof receipt, or multiple outputs derived from the same underlying source.
8.4.1(e) Corroboration may support increased confidence only where the corroborating sources are sufficiently independent, reliable, timely, permissioned, complete, contextually relevant, methodologically compatible, and public-safe for the recorded use.
8.4.1(f) Corroboration shall not erase uncertainty, limitations, conflicting evidence, missing evidence, stale evidence, community challenge, public authority challenge, protected knowledge restrictions, privacy limits, cybersecurity limits, sovereign data limits, finance-boundary limits, provider conflict, sponsor conflict, or downstream dependency concerns.
8.4.1(g) Corroboration outputs shall be recorded where material and shall identify the sources compared, method used, degree of agreement, degree of independence, confidence effect, uncertainty effect, limitations, public-safe status, permitted use, prohibited use, and correction path.
8.4.1(h) The controlling rule shall be that corroboration strengthens evidence only to the extent the method, sources, context, confidence, uncertainty, and records justify that strengthening.
8.4.2 Contradiction as Evidence Event Requiring Review. 8.4.2(a) GCRI Canada shall treat contradiction among material sources, records, outputs, methods, dashboards, maps, models, public authority inputs, community inputs, provider inputs, sponsor inputs, or Nexus interface records as an evidence event requiring review.
8.4.2(b) Contradiction shall include direct factual inconsistency, incompatible measurements, inconsistent timestamps, inconsistent locations, inconsistent source lineage, conflicting method results, conflicting model outputs, inconsistent public authority context, inconsistent community context, inconsistent provider claims, inconsistent sponsor claims, inconsistent benchmark results, inconsistent geospatial layers, inconsistent cyber logs, inconsistent sensor readings, inconsistent AI-RAN signals, inconsistent DePIN records, inconsistent dashboard states, or inconsistent public-safe claims.
8.4.2(c) Contradiction shall not be resolved by title, hierarchy, institutional prestige, official proximity, sponsor influence, provider prominence, media visibility, technical sophistication, AI confidence, dashboard appearance, proof receipt, or the number of repeated claims.
8.4.2(d) Contradiction review shall identify the affected evidence question, sources in conflict, source lineage, methods used, collection time, location or safe location treatment, evidence class, data class, confidence, uncertainty, limitations, classification, public-safe status, review status, permissions, possible causes, affected dependencies, and required correction path.
8.4.2(e) Possible causes of contradiction may include source error, data error, method error, calibration difference, timing difference, geographic mismatch, jurisdictional context, semantic mismatch, translation error, model drift, AI hallucination, sensor spoofing, cyber compromise, incomplete evidence, stale evidence, public authority capacity difference, community context difference, provider conflict, sponsor interest, or public claim overreach.
8.4.2(f) Where contradiction affects public-safe outputs, public authority materials, finance-facing materials, GRF inputs, GRA inputs, Protocol Authority support, Docket records, Grid records, Observatory outputs, Truth Engine outputs, Rails handoffs, dashboards, maps, technical baselines, provider materials, sponsor materials, host materials, community-facing materials, or public claims, GCRI Canada shall evaluate whether hold, restriction, correction, qualification, downgrade, supersession, withdrawal, retraction, or notice is required.
8.4.2(g) A contradiction may remain unresolved where the record does not support resolution. In such case, GCRI Canada shall preserve the contradiction, state limitations where appropriate, prevent overclaim, and maintain a correction path.
8.4.2(h) The controlling rule shall be that contradiction is not institutional inconvenience; it is evidence requiring disciplined review and transparent treatment.
8.4.3 Disputed Evidence Handling. 8.4.3(a) GCRI Canada shall maintain disputed evidence handling for evidence records, datasets, models, methods, observability outputs, Evidence Packs, Decision Packs, dashboards, maps, public-safe outputs, technical baselines, public-good software outputs, Docket records, Grid records, Truth Engine outputs, Rails handoffs, GRF inputs, GRA inputs, Protocol Authority support, public authority materials, finance-facing materials, provider materials, sponsor materials, host materials, community-facing materials, interface records, and public claims.
8.4.3(b) Evidence may be treated as disputed where its accuracy, source lineage, provenance, custody, permission, lawful basis, context, method, confidence, uncertainty, classification, public-safe status, interpretation, boundary meaning, dependency, or downstream use is challenged by a credible source or affected actor.
8.4.3(c) Dispute handling shall identify the disputed record, challenger where appropriate and safe, nature of dispute, basis for dispute, affected sources, affected methods, affected confidence, affected uncertainty, affected classification, affected public-safe status, affected permissions, affected boundaries, affected dependencies, reviewer, review pathway, interim status, and correction path.
8.4.3(d) Disputed evidence may be marked, restricted, held, downgraded, qualified, reclassified, separated from public-safe outputs, removed from dashboards, removed from maps, withheld from finance-facing materials, withheld from public authority materials, withheld from GRF inputs, withheld from GRA inputs, withheld from Protocol Authority support, or prevented from public claim use pending review where risk requires.
8.4.3(e) Disputed status shall not imply that evidence is false. It shall mean that the evidence requires review, limitation, qualification, or correction before it may be relied upon or communicated beyond recorded boundaries.
8.4.3(f) Disputed evidence shall not be used to create or imply certification, recognition, finance-readiness, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, market authority, infrastructure operation, or execution consequence by default.
8.4.3(g) Dispute handling shall preserve confidentiality, source protection, protected participation, community safeguards, Indigenous and protected knowledge safeguards, privacy, cybersecurity, sovereign data, public authority restrictions, finance-safe treatment, provider neutrality, sponsor non-control, and public-safe publication.
8.4.3(h) The controlling rule shall be that disputed evidence remains part of the record but must be marked, bounded, reviewed, and corrected or resolved through a records-valid pathway.
8.4.4 Conflicting Source Handling. 8.4.4(a) GCRI Canada shall maintain conflicting source handling for sources that materially disagree, diverge, contradict, measure different conditions, use different assumptions, apply different definitions, reflect different jurisdictions, encode different methods, or represent different public authority, community, provider, sponsor, technical, historical, or model contexts.
8.4.4(b) Conflicting source handling shall classify the conflict as factual, methodological, temporal, geographic, semantic, jurisdictional, evidentiary, public authority-related, community-related, protected knowledge-related, model-related, AI-related, sensor-related, cyber-related, provider-related, sponsor-related, finance-facing, public-safe, or boundary-related where material.
8.4.4(c) Conflicting sources shall be compared through source independence, source reliability, source timeliness, source permission, source bias, source completeness, source context, method, confidence, uncertainty, limitations, and public-safe status.
8.4.4(d) Where sources conflict because they describe different contexts, GCRI Canada shall not force artificial reconciliation. It shall preserve context and record whether the conflict is real, apparent, unresolved, context-dependent, terminology-dependent, time-dependent, geography-dependent, method-dependent, or authority-dependent.
8.4.4(e) Where sources conflict because of controlled vocabulary mismatch, translation mismatch, localization mismatch, schema mismatch, data dictionary mismatch, or AI-readable structure mismatch, GCRI Canada shall route the matter to ontology or controlled vocabulary review.
8.4.4(f) Where conflicting sources affect public authority interpretation, finance-facing interpretation, provider-facing interpretation, sponsor-facing interpretation, community-facing interpretation, protected knowledge treatment, Nexus interface meaning, or public claims, GCRI Canada shall apply heightened boundary review before further use.
8.4.4(g) Conflicting source handling may result in confirming one source, qualifying multiple sources, downgrading confidence, segmenting contexts, reclassifying evidence, suspending use, triggering additional evidence collection, correcting records, superseding records, withdrawing outputs, retracting public claims, or archiving unresolved disputes.
8.4.4(h) The controlling rule shall be that conflict must be governed as evidence, not hidden as noise or prematurely resolved for narrative convenience.
8.4.5 Missing Evidence Handling. 8.4.5(a) GCRI Canada shall maintain missing evidence handling for cases where expected, material, required, or useful evidence is absent, inaccessible, uncollected, withheld, deleted, restricted, delayed, not yet available, not permissioned, not public-safe, not capable of verification, or not fit for use.
8.4.5(b) Missing evidence shall be recorded where its absence materially affects confidence, uncertainty, completeness, fitness for purpose, public-safe status, public authority interpretation, finance-facing interpretation, provider-facing interpretation, sponsor-facing interpretation, community-facing interpretation, Nexus interface meaning, or public claims.
8.4.5(c) Missing evidence shall not be treated as proof that no risk, harm, event, defect, vulnerability, capability, condition, conflict, community concern, public authority concern, provider issue, sponsor influence, or system failure exists.
8.4.5(d) Missing evidence handling shall identify the expected evidence, reason for missingness where known, source or custodian where known, access restriction, permission issue, public-safe issue, privacy issue, cybersecurity issue, sovereign data issue, protected knowledge issue, community safeguard issue, public authority restriction, collection feasibility, substitute evidence where any, limitation effect, confidence effect, uncertainty effect, and correction or follow-up path.
8.4.5(e) Where missing evidence is caused by rights-based refusal, community non-consent, Indigenous or protected knowledge restrictions, public authority restrictions, lawful confidentiality, privacy limits, cybersecurity limits, sovereign data restrictions, or safety concerns, GCRI Canada shall treat such missingness as a governed constraint, not a defect to be bypassed.
8.4.5(f) Where missing evidence materially affects an output, GCRI Canada shall consider whether to qualify, restrict, downgrade, delay, suspend, withdraw, or withhold the output rather than permit unsupported certainty.
8.4.5(g) Missing evidence status shall be updated where evidence later becomes available, becomes unavailable, is corrected, is restricted, is rejected, or is determined no longer material.
8.4.5(h) The controlling rule shall be that missing evidence must be visible in the record because hidden missingness creates false confidence.
8.4.6 Stale Evidence Handling. 8.4.6(a) GCRI Canada shall maintain stale evidence handling for evidence whose time-bound validity, source context, method context, public-safe status, permission status, confidence, uncertainty, limitation, classification, or downstream use may no longer be current.
8.4.6(b) Evidence may be stale where it has been superseded, time-limited, context-changed, event-changed, jurisdiction-changed, community-context changed, technology-changed, model-drifted, sensor-drifted, policy-changed, public authority-changed, provider-changed, sponsor-changed, data-permission changed, public-safe status changed, or no longer maintained.
8.4.6(c) Stale evidence handling shall identify the evidence record, date of creation, date of review, time sensitivity, source update frequency, method update frequency, public-safe review date, status, supersession status, withdrawal status, retraction status, archive status, downstream dependencies, and required refresh or retirement path.
8.4.6(d) Stale evidence shall not be used as current evidence merely because it is publicly available, widely cited, technically sophisticated, convenient, incorporated in a dashboard, embedded in software, included in a prior Evidence Pack, referenced by a public authority, relied upon by a sponsor, used by a provider, or repeated in Nexus materials.
8.4.6(e) Where stale evidence affects public-safe outputs, dashboards, maps, public authority materials, finance-facing materials, GRF inputs, GRA inputs, Protocol Authority support, Docket records, Grid records, Observatory outputs, Truth Engine outputs, Rails handoffs, provider materials, sponsor materials, host materials, community-facing materials, or public claims, GCRI Canada shall determine whether correction, qualification, downgrade, supersession, withdrawal, retraction, or notice is required.
8.4.6(f) Time-sensitive evidence shall carry review cadence, expiry, refresh trigger, or use-by limitation where appropriate.
8.4.6(g) Stale evidence handling shall preserve historical value where appropriate while preventing historical evidence from being misrepresented as current evidence.
8.4.6(h) The controlling rule shall be that evidence can be true in history and unsafe in present use unless its currency is recorded and reviewed.
8.4.7 Spoofed, Tampered, Failed, Synthetic, Adversarial, or Manipulated Signal Handling. 8.4.7(a) GCRI Canada shall maintain handling methods for spoofed, tampered, failed, synthetic, adversarial, or manipulated signals affecting sensors, reference sensors, AI-RAN signals, O-RAN signals, private wireless signals, DePIN telemetry, cyber logs, geospatial data, Earth observation data, satellite data, digital twin outputs, model outputs, AI outputs, dashboard states, map layers, blockchain entries, proof receipts, smart-contract logs, documents, images, videos, audio, public claims, or source credentials.
8.4.7(b) Spoofed signal handling shall apply where signal identity, device identity, source identity, location, timestamp, telemetry, provenance, custody, proof record, or asserted condition is suspected or confirmed to be falsified, replayed, impersonated, fabricated, adversarially generated, or fraudulently presented.
8.4.7(c) Tampered signal handling shall apply where records, devices, files, logs, metadata, repositories, dashboards, maps, models, datasets, evidence packs, technical baselines, or outputs are suspected or confirmed to have been altered, modified, corrupted, injected, suppressed, selectively edited, or manipulated without proper authority.
8.4.7(d) Failed signal handling shall apply where sensors, systems, models, dashboards, maps, pipelines, data feeds, compute environments, communication systems, repositories, APIs, or evidence processes have failed, degraded, lost integrity, lost availability, lost calibration, lost synchronization, or become unreliable.
8.4.7(e) Synthetic or adversarial signal handling shall apply where AI-generated content, synthetic media, deepfakes, generated documents, fabricated telemetry, adversarial examples, prompt-injected outputs, synthetic datasets, simulated outputs, or model-generated artifacts may be mistaken for real-world evidence without proper treatment.
8.4.7(f) Manipulated signal handling shall include review of signal origin, custody, access logs, cryptographic records where any, device records, model records, dataset records, pipeline records, cyber indicators, anomaly indicators, corroborating sources, conflict sources, public-safe implications, and incident response requirements.
8.4.7(g) Where spoofed, tampered, failed, synthetic, adversarial, or manipulated signals materially affect evidence quality, public-safe outputs, dashboards, maps, public authority materials, finance-facing materials, provider materials, sponsor materials, GRF inputs, GRA inputs, Protocol Authority support, Nexus interface records, or public claims, GCRI Canada shall hold, restrict, flag, downgrade, correct, supersede, withdraw, retract, quarantine, route to cyber or technical review, or notify affected dependencies as appropriate.
8.4.7(h) GCRI Canada shall not publicly disclose technical details of spoofing, tampering, adversarial manipulation, cyber compromise, infrastructure vulnerability, or exploitability where disclosure would create security risk, public safety risk, protected knowledge risk, community harm, or unlawful exposure.
8.4.7(i) The controlling rule shall be that manipulated signals are not merely bad data; they are integrity events requiring evidence, cyber, public-safe, and correction treatment.
8.4.8 Community or Public Authority Challenge Handling. 8.4.8(a) GCRI Canada shall maintain challenge handling for community challenges and public authority challenges affecting evidence records, source treatment, methods, confidence, uncertainty, public-safe status, dashboard outputs, map outputs, Truth Engine outputs, Observatory outputs, Evidence Packs, Decision Packs, public-safe reports, public authority materials, community-facing materials, GRF inputs, GRA inputs, Protocol Authority support, Nexus interface records, or public claims.
8.4.8(b) Community challenge may include challenge by affected persons, local participants, community representatives, Indigenous institutions, Indigenous or local knowledge holders, protected knowledge holders, civil society actors, vulnerable community representatives, hosts, residents, workers, field participants, or other affected actors.
8.4.8(c) Public authority challenge may include challenge by public authorities, public officials acting in appropriate capacity, regulators, emergency-management actors, public health actors, public finance actors, procurement actors, infrastructure actors, public-sector data custodians, or other competent public bodies.
8.4.8(d) Community or public authority challenges shall be received, classified, recorded, protected where necessary, and reviewed through an appropriate pathway that respects confidentiality, authority, public-safe status, lawful restrictions, cultural context, Indigenous protocol where applicable, public authority capacity, and conflict-of-interest controls.
8.4.8(e) GCRI Canada shall not dismiss community challenge merely because it is qualitative, local, non-technical, non-institutional, inconvenient, politically sensitive, contrary to sponsor narratives, contrary to provider claims, contrary to public-facing materials, or difficult to reconcile with machine-generated sources.
8.4.8(f) GCRI Canada shall not treat public authority challenge as automatic public authority decision, official guidance, regulatory order, procurement instruction, public warning, emergency command, funding approval, public finance position, or sovereign obligation unless the public authority has separately acted through its own lawful process and record.
8.4.8(g) Where a community or public authority challenge has merit or cannot safely be dismissed, GCRI Canada shall consider qualification, correction, reclassification, public-safe revision, restriction, downgrade, supersession, withdrawal, retraction, controlled notice, public-safe notice, additional evidence review, safeguards review, public authority reference review, or board escalation as appropriate.
8.4.8(h) The controlling rule shall be that community and public authority challenges are evidence-governance events that must be heard without converting challenge into either automatic override or automatic authority.
8.4.9 Provider, Sponsor, Host, or Capital-Reader Challenge Handling. 8.4.9(a) GCRI Canada shall maintain challenge handling for provider, sponsor, host, donor, funder, capital-reader, vendor, contractor, National Company, Project SPV, or other enterprise-stack challenges affecting evidence records, methods, benchmarks, source treatment, confidence, uncertainty, public-safe status, provider references, sponsor references, host references, finance-facing materials, dashboards, maps, technical baselines, Evidence Packs, Decision Packs, Truth Engine outputs, Observatory outputs, Rails handoffs, GRF inputs, GRA inputs, Protocol Authority support, Nexus interface records, or public claims.
8.4.9(b) Provider, sponsor, host, or capital-reader challenges shall be received and recorded where credible, but shall be reviewed through conflict, influence, boundary, competition, finance, public-safe, and correction controls proportionate to the challenge and relationship.
8.4.9(c) GCRI Canada shall not ignore a provider, sponsor, host, or capital-reader challenge merely because the challenger has an interest. Interested challengers may identify real defects, missing context, technical errors, method errors, data errors, public-safe issues, confidentiality issues, IP issues, or boundary risks.
8.4.9(d) GCRI Canada shall not accept a provider, sponsor, host, or capital-reader challenge merely because the challenger funds, supports, hosts, supplies, integrates, demonstrates, maintains, operates, invests in, evaluates, or is affected by the relevant activity.
8.4.9(e) Provider challenges shall be reviewed for technical merit, evidence basis, benchmark context, source lineage, method scope, provider-interest effects, procurement implication, certification implication, recognition implication, provider-neutrality risk, market-allocation risk, and public-claims risk.
8.4.9(f) Sponsor, donor, or funder challenges shall be reviewed for evidence merit, public-benefit merit, conflict, influence, outcome-purchase risk, publication-suppression risk, sponsor-control risk, public authority access purchase risk, recognition-purchase risk, finance-readiness-purchase risk, certification-purchase risk, and public-claims risk.
8.4.9(g) Host challenges shall be reviewed for evidence merit, site context, data authority, community context, public authority context, operational sensitivity, public-safe status, privacy, cybersecurity, sovereign data, infrastructure sensitivity, public claims, and support-without-control boundaries.
8.4.9(h) Capital-reader challenges shall be reviewed for evidence merit, finance-boundary risk, reliance risk, rating-like interpretation, investment-advice risk, public finance implication, guarantee implication, insurance implication, securities implication, and public-claims risk.
8.4.9(i) Where a provider, sponsor, host, or capital-reader challenge has merit or cannot safely be dismissed, GCRI Canada shall consider qualification, correction, reclassification, restriction, downgrade, supersession, withdrawal, retraction, public-safe revision, controlled notice, interface revision, conflict disclosure, or board escalation as appropriate.
8.4.9(j) The controlling rule shall be that interested challenges may improve evidence but shall never purchase, suppress, steer, certify, finance, endorse, or execute truth.
8.4.10 Escalation Pathways for High-Consequence Disputes. 8.4.10(a) GCRI Canada shall maintain escalation pathways for high-consequence disputes affecting evidence integrity, public-safe status, public authority interpretation, finance-facing interpretation, provider neutrality, sponsor non-control, community safeguards, Indigenous or protected knowledge, privacy, cybersecurity, sovereign data, controlled technology, public claims, GRF inputs, GRA inputs, Protocol Authority support, Nexus interface records, National Company interfaces, Project SPV interfaces, or downstream dependency.
8.4.10(b) A dispute shall be high-consequence where it may materially affect public safety, rights-bearing data, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, sovereign-sensitive data, public authority materials, finance-facing materials, public claims, community harm, protected knowledge exposure, Indigenous or local knowledge misuse, public warning confusion, emergency-command confusion, procurement implication, certification implication, recognition implication, finance-readiness implication, provider preference, sponsor control, market consequence, legal compliance, or institutional trust.
8.4.10(c) Escalation pathways may include evidence steward review, method steward review, data steward review, public-safe publication review, privacy review, cybersecurity review, AI review, sovereign data review, safeguards review, Indigenous or protected knowledge review, public authority boundary review, finance boundary review, competition review, legal review, interface review, committee review, officer escalation, board escalation, or external expert review where appropriate.
8.4.10(d) High-consequence disputes may require interim controls including hold, stop-the-line action, quarantine, access restriction, dashboard suspension, map suspension, publication hold, public-claim freeze, finance-facing hold, public authority-facing hold, GRF input hold, GRA input hold, Protocol Authority support hold, interface suspension, provider-reference hold, sponsor-reference hold, or downstream dependency notice.
8.4.10(e) Escalation shall identify responsible actor, authority, interim status, review question, evidence affected, method affected, data affected, output affected, public-safe status, boundary risks, required reviewers, timeline, notice decision, and closeout condition.
8.4.10(f) Where urgent public safety, cybersecurity, privacy, protected knowledge, public authority, or legal risk exists, GCRI Canada may apply immediate protective measures before completing full review, provided that such measures are recorded, proportionate, temporary where appropriate, and subject to follow-up review.
8.4.10(g) Escalation shall not convert GCRI Canada into an emergency commander, public warning authority, public authority, regulator, financial actor, certifier, provider selector, sponsor controller, Protocol Authority, GRF, GRA, National Company, Project SPV, or execution actor.
8.4.10(h) The controlling rule shall be that high-consequence disputes must be escalated early enough to prevent evidence defects from becoming public harm, authority confusion, finance overclaim, provider preference, sponsor control, or execution drift.
8.4.11 Dispute Outcomes: Confirm, Qualify, Downgrade, Suspend, Correct, Supersede, Withdraw, Retract, Reclassify, or Archive. 8.4.11(a) Dispute outcomes may include confirmation, qualification, downgrade, suspension, correction, supersession, withdrawal, retraction, reclassification, restriction, reinstatement, retirement, archive, additional review, continued monitoring, or no-change determination with recorded reasons.
8.4.11(b) Confirmation may be used where the challenged evidence, method, output, classification, confidence, uncertainty, or public-safe status remains supported after review, provided that confirmation does not create certification, recognition, finance-readiness, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, market authority, infrastructure operation, or execution consequence by default.
8.4.11(c) Qualification may be used where evidence remains useful only with revised limitation, audience, confidence, uncertainty, public-safe status, permitted use, prohibited use, boundary language, or dependency warning.
8.4.11(d) Downgrade may be used where evidence quality, confidence, public-safe status, maturity-context meaning, readiness-context meaning, method reliability, dashboard meaning, map meaning, claim strength, or permitted use must be reduced.
8.4.11(e) Suspension may be used where use must be temporarily held pending review, challenge, investigation, correction, public-safe review, legal review, privacy review, cybersecurity review, sovereign data review, safeguards review, public authority boundary review, finance boundary review, competition review, or interface review.
8.4.11(f) Correction may be used where a record, method, output, claim, classification, confidence statement, uncertainty statement, limitation, attribution, boundary language, dashboard, map, publication, interface, or dependency is inaccurate, incomplete, misleading, stale, misclassified, overclaimed, unsafe, or no longer fit for purpose.
8.4.11(g) Supersession may be used where a new version replaces a prior version while preserving prior identity, version history, correction history, status history, dependency links, access restrictions, and archive treatment.
8.4.11(h) Withdrawal may be used where a record or output cannot safely or lawfully remain in active use, lacks authority, lacks permission, exposes restricted material, mishandles protected knowledge, creates public authority confusion, creates finance overclaim, creates procurement implication, creates provider preference, creates sponsor control, creates community harm, or cannot be corrected in place.
8.4.11(i) Retraction may be used where a public or material claim was materially wrong, unsupported, unsafe, authority-inflating, finance-inflating, procurement-inflating, provider-preferential, sponsor-controlled, privacy-invasive, security-sensitive, community-harming, protected-knowledge-infringing, or inconsistent with GCRI Canada’s public-benefit duties.
8.4.11(j) Reclassification may be used where evidence, data, methods, outputs, dashboards, maps, Evidence Packs, Decision Packs, public-safe materials, public authority materials, finance-facing materials, provider materials, sponsor materials, community-facing materials, or interface records require changed access, handling, public-safe, finance-safe, public authority-facing, provider-facing, sponsor-facing, protected knowledge, or archive status.
8.4.11(k) Archive may be used to preserve identity, history, challenge, review, correction, status, dependency, and closure while preventing active use beyond recorded limits.
8.4.11(l) The controlling rule shall be that dispute outcomes must repair the record, protect affected dependencies, preserve institutional memory, and prevent continued use beyond what the reviewed evidence supports.
8.4.12 Corroboration, Contradiction, Dispute, and Challenge Records. 8.4.12(a) GCRI Canada shall maintain, or cause to be maintained, corroboration, contradiction, dispute, and challenge records for material corroboration reviews, contradiction reviews, disputed evidence reviews, conflicting source reviews, missing evidence reviews, stale evidence reviews, manipulated signal reviews, community challenges, public authority challenges, provider challenges, sponsor challenges, host challenges, capital-reader challenges, and high-consequence dispute escalations.
8.4.12(b) Corroboration records shall identify the evidence question, sources compared, method used, degree of agreement, degree of independence, source reliability, source timeliness, source permission, source bias, source completeness, confidence effect, uncertainty effect, limitation effect, reviewer, review status, permitted use, prohibited use, dependency links, and correction path.
8.4.12(c) Contradiction records shall identify the sources or outputs in conflict, nature of contradiction, conflict type, possible causes, evidence affected, methods affected, confidence effect, uncertainty effect, public-safe effect, classification effect, affected dependencies, interim controls, reviewer, escalation pathway, and resolution status.
8.4.12(d) Dispute records shall identify the disputed record or output, challenger where appropriate and safe, challenge basis, challenge type, affected source, affected method, affected classification, affected public-safe status, affected confidence, affected uncertainty, affected boundary language, affected dependencies, review pathway, interim status, outcome, notice decision, and closeout requirements.
8.4.12(e) Challenge records shall preserve confidentiality, protected participation, source protection, public authority restrictions, community safeguards, Indigenous and protected knowledge safeguards, privacy, cybersecurity, sovereign data, finance-safe treatment, provider-neutrality treatment, sponsor non-control treatment, and public-safe publication treatment where applicable.
8.4.12(f) Records under this section shall be linked, where applicable, to the Evidence Register, Method Register, Dataset Register, Model Register, Observability Register, Ontology and Controlled Vocabulary Register, Evidence Pack Register, Decision Pack Register, Publication and Public-Safe Output Register, Correction Register, Dependency Register, public authority records, GRF interface records, GRA interface records, Protocol Authority interface records, Nexus interface records, provider records, sponsor records, host records, and public claims records.
8.4.12(g) Where a corroboration, contradiction, dispute, or challenge record results in confirmation, qualification, downgrade, suspension, correction, supersession, withdrawal, retraction, reclassification, reinstatement, retirement, or archive, affected downstream records and outputs shall be reviewed.
8.4.12(h) Corroboration, contradiction, dispute, and challenge records shall not create certification, recognition, finance-readiness, investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.4.12(i) The controlling rule shall be that truth stewardship requires records of agreement, disagreement, dispute, and challenge because unrecorded conflict cannot be reviewed, corrected, or safely communicated.
8.5 Confidence Scoring and Confidence Governance
8.5.1 Confidence Scores as Evidence-Quality and Corroboration Signals. 8.5.1(a) GCRI Canada may use confidence scores, confidence bands, confidence labels, confidence notes, confidence states, confidence indicators, confidence narratives, or equivalent confidence artifacts within the Nexus Truth Engine as evidence-quality and corroboration signals.
8.5.1(b) Confidence scores shall indicate, within a recorded method and context, the relative strength, quality, reliability, corroboration, completeness, timeliness, independence, reproducibility, review status, and limitation profile of evidence or evidence-related outputs.
8.5.1(c) Confidence scores may be applied to evidence records, source comparisons, corroboration outputs, contradiction reviews, dispute reviews, datasets, models, system cards, benchmark cards, observability records, dashboards, maps, Evidence Packs, Decision Packs, Truth Engine outputs, Observatory outputs, Docket inputs, Grid inputs, Rails handoffs, GRF inputs, GRA inputs, Protocol Authority support, public authority learning materials, technical publications, public-safe reports, controlled annexes, and public-safe summaries.
8.5.1(d) Confidence scoring shall not be used as a substitute for source lineage, provenance, custody, method documentation, evidence classification, public-safe classification, uncertainty treatment, limitation disclosure, access controls, boundary language, reviewer judgment, or correction path.
8.5.1(e) Confidence scores shall be contextual. A confidence score assigned for one purpose, audience, domain, jurisdiction, technology, source class, public-safe status, finance-facing status, public authority-facing status, or interface shall not be assumed to apply to another purpose, audience, domain, jurisdiction, technology, status, or interface without review.
8.5.1(f) Confidence scores may increase, decrease, be qualified, be suspended, be withdrawn, be superseded, or be reissued as source records, methods, data, models, evidence classes, public-safe classifications, disputes, corrections, or downstream uses change.
8.5.1(g) Confidence scores shall be records-bound and shall carry or link to the evidence, source, method, context, assumptions, limitations, review status, public-safe status, permitted use, prohibited use, and correction path that give the score meaning.
8.5.1(h) The controlling rule shall be that confidence scores are structured evidence-quality signals, not free-standing truth, status, authority, approval, maturity, readiness, certification, or execution indicators.
8.5.2 Confidence Scores as Non-Rating, Non-Certification, Non-Public-Authority, Non-Finance, and Non-Execution Artifacts. 8.5.2(a) Confidence scores shall be non-rating, non-certification, non-public-authority, non-finance, non-procurement, non-provider-endorsement, non-sponsor-approval, non-protocol-effect, non-public-warning, non-emergency-command, and non-execution artifacts.
8.5.2(b) No confidence score, confidence band, confidence label, dashboard color, map layer, risk indicator, resilience indicator, benchmark indicator, maturity-context signal, readiness-context signal, Truth Engine output, Observatory output, or Evidence Pack score shall create certification, recognition, finance-readiness, investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.5.2(c) Confidence scores shall not be marketed, relied upon, displayed, exported, integrated, or summarized as credit ratings, investment ratings, insurance ratings, resilience ratings, project ratings, provider ratings, technology ratings, safety approvals, security approvals, compliance approvals, public authority findings, GRF recognition, GRA finance-readiness, Protocol Authority conformance, procurement rankings, or operational clearances.
8.5.2(d) Confidence scoring shall not convert GCRI Canada into a rating agency, investment adviser, securities actor, insurer, underwriter, lender, guarantor, public finance approver, public authority, regulator, certifier, procurement body, emergency commander, public warning authority, protocol authority, infrastructure operator, National Company, Project SPV, provider, or execution actor.
8.5.2(e) Where confidence scores are displayed in dashboards, maps, reports, public-safe outputs, public authority materials, finance-facing materials, provider-facing materials, sponsor-facing materials, Academy materials, public websites, repositories, APIs, or public claims, boundary language shall prevent score inflation into authority, rating, approval, finance-readiness, certification, recognition, procurement advantage, or execution readiness.
8.5.2(f) Where a third party uses or describes a confidence score as a rating, approval, certification, recognition, finance-readiness determination, public authority decision, procurement preference, provider endorsement, sponsor approval, guarantee, or execution clearance, GCRI Canada shall require correction, clarification, withdrawal, retraction, controlled notice, public-safe notice, interface suspension, or other remedy as appropriate.
8.5.2(g) Confidence scores may support evidence interpretation by competent actors, but any downstream authority, decision, reliance, financial consequence, public authority consequence, recognition consequence, protocol consequence, procurement consequence, or execution consequence shall arise only from the competent actor’s own lawful process and record.
8.5.2(h) The controlling rule shall be that confidence scoring makes evidence more transparent; it does not make GCRI Canada an authority over ratings, finance, public decisions, certification, procurement, protocol effect, or execution.
8.5.3 Confidence Method Documentation. 8.5.3(a) GCRI Canada shall maintain, or cause to be maintained, documentation for material confidence scoring methods used in the Nexus Truth Engine.
8.5.3(b) Confidence method documentation shall identify the method title or identifier, purpose, scope, evidence classes covered, source classes covered, technology domains covered, risk domains covered, data classes covered, output types covered, intended audiences, excluded uses, owner, custodian, steward, version, effective date, status, assumptions, inputs, weights where any, scoring logic, threshold logic where any, qualitative judgment factors, human review requirements, AI-use status, model dependencies, dataset dependencies, calibration basis, validation basis, limitations, public-safe status, permitted use, prohibited use, correction path, supersession path, withdrawal path, and archive path.
8.5.3(c) Confidence method documentation shall state whether a confidence score is numeric, categorical, narrative, banded, ordinal, qualitative, hybrid, or contextual, and shall identify how score meaning changes across evidence classes, technology domains, audiences, public-safe status, controlled-room use, finance-facing use, public authority learning use, GRF input, GRA input, Protocol Authority support, technical publication, dashboard, map, Evidence Pack, or Decision Pack.
8.5.3(d) Confidence method documentation shall identify the relationship between confidence and uncertainty. A high confidence score shall not be used to erase material uncertainty, and a low confidence score shall not be used to imply falsity without record.
8.5.3(e) Confidence method documentation shall identify required downgrade factors, hold factors, dispute factors, exclusion factors, review triggers, public-safe release constraints, controlled-room constraints, finance-boundary constraints, public authority boundary constraints, provider-neutrality constraints, sponsor non-control constraints, and correction triggers.
8.5.3(f) Confidence method documentation shall be versioned and shall not be silently changed. Material method updates shall identify prior method, new method, reason for change, effective date, affected records, affected outputs, affected scores, downstream dependency review, correction path, and public-safe communication where required.
8.5.3(g) Where confidence scoring uses AI, statistical models, weighted scoring, automated classification, dashboard rules, benchmark rules, or retrieval systems, method documentation shall identify model governance, inference records where material, evaluation records, benchmark cards, system cards, bias risks, drift risks, hallucination risks, false precision risks, and human review requirements.
8.5.3(h) The controlling rule shall be that confidence scoring is not valid unless the method for producing, interpreting, updating, and correcting confidence is documented, versioned, bounded, and reviewable.
8.5.4 Confidence Inputs: Source Quality, Corroboration, Timeliness, Calibration, Completeness, Independence, Reproducibility, Review Status, and Context. 8.5.4(a) Confidence scoring shall consider, where material, source quality, corroboration, timeliness, calibration, completeness, independence, reproducibility, review status, and context.
8.5.4(b) Source quality shall consider source lineage, provenance, custody, source authority, source reliability, source integrity, source transparency, source documentation, permissions, lawful basis, correction history, conflict status, public-safe status, and classification.
8.5.4(c) Corroboration shall consider whether evidence is supported by independent sources, partially independent sources, methodologically distinct sources, repeated measurements, reference sources, field observations, public records, community context, public authority context, university or laboratory outputs, technical sources, observability records, or other relevant sources, and whether such support is genuine rather than shared-source amplification.
8.5.4(d) Timeliness shall consider date of collection, date of review, update frequency, latency, stale status, supersession status, withdrawal status, retraction status, context change, technology change, public authority change, community context change, provider change, sponsor change, and continuing fitness for purpose.
8.5.4(e) Calibration shall consider instrument calibration, sensor calibration, model calibration, benchmark calibration, method calibration, evaluation conditions, environmental conditions, hardware conditions, software conditions, geospatial precision, clock integrity, location integrity, and known drift.
8.5.4(f) Completeness shall consider coverage of the relevant time, place, population, system, asset, event, hazard, technology, infrastructure, community, public authority context, provider context, sponsor context, evidence class, and evidence question, including missing data, missing sources, redactions, inaccessible annexes, and known blind spots.
8.5.4(g) Independence shall consider whether sources depend on common origin, common dataset, common model, common sensor, common provider platform, common sponsor material, common public authority feed, common field team, common repository, common method, common publication, or common AI-generated summary.
8.5.4(h) Reproducibility shall consider whether evidence or method outcomes can be replicated, re-run, rechecked, re-observed, independently reviewed, or otherwise verified within lawful, safe, privacy-preserving, cybersecurity-compatible, sovereign-data-compatible, and protected-knowledge-compatible limits.
8.5.4(i) Review status shall consider whether evidence has been unreviewed, internally reviewed, technically reviewed, public-safe reviewed, legal reviewed, safeguards reviewed, public authority boundary reviewed, finance boundary reviewed, peer reviewed, committee reviewed, board reviewed, or independently reviewed.
8.5.4(j) Context shall consider jurisdictional context, public authority context, community context, Indigenous or local knowledge context, protected knowledge context, technology domain, risk domain, stage truth, intended audience, permitted use, prohibited use, public-safe status, finance-facing status, provider-facing status, sponsor-facing status, and downstream dependency.
8.5.4(k) The controlling rule shall be that confidence must arise from traceable inputs, not from institutional intuition, technical elegance, public visibility, authority proximity, sponsor support, provider prominence, or narrative force.
8.5.5 Confidence Downgrades for Conflict, Staleness, Missing Data, Spoof Risk, Bias, Model Uncertainty, Sponsor Influence, Provider Influence, or Boundary Risk. 8.5.5(a) GCRI Canada shall maintain downgrade rules for confidence scoring where conflict, staleness, missing data, spoof risk, tamper risk, corruption risk, bias, model uncertainty, AI uncertainty, sponsor influence, provider influence, host influence, capital-reader influence, public authority ambiguity, protected knowledge risk, community harm risk, privacy risk, cybersecurity risk, sovereign data risk, finance-boundary risk, public-safe risk, or other boundary risk materially affects evidence strength.
8.5.5(b) Conflict downgrade shall apply where sources materially disagree, methods conflict, public authority context differs, community context differs, provider claims diverge, sponsor claims diverge, benchmark outcomes conflict, observability signals conflict, model outputs conflict, or unresolved contradiction affects evidence meaning.
8.5.5(c) Staleness downgrade shall apply where evidence is outdated, superseded, time-limited, context-changed, method-changed, data-permission changed, technology-changed, public authority-changed, community-context changed, provider-changed, sponsor-changed, model-drifted, sensor-drifted, policy-changed, public-safe status changed, or no longer maintained.
8.5.5(d) Missing data downgrade shall apply where expected, material, required, or useful evidence is absent, inaccessible, restricted, withheld, uncollected, deleted, unavailable, not permissioned, not public-safe, incomplete, or unfit for use.
8.5.5(e) Spoof, tamper, synthetic, adversarial, failed-signal, or corruption downgrade shall apply where signals, records, devices, identities, locations, logs, dashboards, maps, models, datasets, repositories, proof receipts, blockchain records, DePIN records, AI outputs, images, videos, documents, or source credentials are suspected or confirmed to be manipulated, compromised, fabricated, replayed, corrupted, or unreliable.
8.5.5(f) Bias downgrade shall apply where source selection, data collection, sampling, method design, model training, dashboard design, public authority context, sponsor interest, provider interest, host interest, capital-reader interest, media framing, academic incentive, community exclusion, missing voices, or institutional incentive may materially affect evidence meaning.
8.5.5(g) Model uncertainty downgrade shall apply where outputs depend materially on AI, statistical models, simulations, digital twins, scenario engines, classification systems, retrieval systems, sensor fusion systems, or other models with unresolved assumptions, limitations, drift, hallucination risk, bias risk, calibration uncertainty, or incomplete validation.
8.5.5(h) Sponsor, provider, host, or capital-reader influence downgrade shall apply where support relationships, technical dependencies, funding, in-kind contributions, platform control, data access, benchmark design, publication timing, public authority access, finance-facing use, or public claim incentives create actual or perceived influence risk.
8.5.5(i) Boundary-risk downgrade shall apply where confidence scoring may be interpreted as public authority approval, finance-readiness, investment advice, certification, recognition, procurement preference, provider endorsement, sponsor approval, protocol effect, rating, guarantee, public warning, emergency command, or execution readiness.
8.5.5(j) A downgrade shall be recorded with the basis, affected score, prior status, new status, effective date, reviewer, method used, affected dependencies, and correction path.
8.5.5(k) The controlling rule shall be that confidence must be reduced, qualified, held, or restricted where evidence conditions make stronger confidence unsafe, unsupported, or boundary-inflating.
8.5.6 Confidence Updates and Confidence Change Logs. 8.5.6(a) GCRI Canada shall maintain, or cause to be maintained, confidence updates and confidence change logs for material confidence scores, confidence bands, confidence labels, confidence indicators, confidence notes, and equivalent confidence artifacts.
8.5.6(b) Confidence updates shall be required where new evidence, corrected evidence, corrected source lineage, corrected data, corrected methods, corrected confidence inputs, corrected public-safe classification, corrected ontology, corrected model records, corrected observability records, additional corroboration, new contradiction, dispute, challenge, missing evidence, stale evidence, spoof risk, cyber risk, privacy risk, public authority risk, finance-boundary risk, provider influence, sponsor influence, or changed context materially affects confidence.
8.5.6(c) Confidence change logs shall identify the affected record or output, prior confidence status, new confidence status, reason for change, source of change, reviewer, approving actor where required, method used, date, effective date, evidence affected, methods affected, data affected, models affected, observability affected, public-safe effect, finance-safe effect where material, public authority effect where material, provider effect where material, sponsor effect where material, affected dependencies, notice decision, and correction path.
8.5.6(d) Confidence changes shall distinguish increase, decrease, qualification, suspension, reinstatement, correction, recalibration, reclassification, supersession, withdrawal, retraction, retirement, archive, and no-change determinations.
8.5.6(e) Confidence increases shall require adequate basis and shall not be made merely because evidence has become more visible, sponsor-supported, provider-promoted, public authority-attended, finance-facing, repeated in public materials, displayed in dashboards, or incorporated into Nexus interfaces.
8.5.6(f) Confidence decreases shall not be suppressed because reduction may affect reputation, sponsor comfort, provider comfort, public authority comfort, finance-facing usefulness, media narrative, project momentum, or public visibility.
8.5.6(g) Where confidence changes materially affect public-safe outputs, dashboards, maps, Evidence Packs, Decision Packs, GRF inputs, GRA inputs, Protocol Authority support, public authority materials, finance-facing materials, provider materials, sponsor materials, host materials, community-facing materials, technical baselines, public-good software, Nexus interface records, or public claims, GCRI Canada shall review downstream dependencies and determine whether correction, reissue, notice, restriction, supersession, withdrawal, or retraction is required.
8.5.6(h) The controlling rule shall be that confidence must be capable of changing because evidence stewardship requires transparent adjustment when the record changes.
8.5.7 Confidence Thresholds for Public-Safe Release, Controlled-Room Release, GRF Input, GRA Input, Protocol Authority Input, Public Authority Learning, and Technical Publication. 8.5.7(a) GCRI Canada may establish confidence thresholds, threshold bands, release criteria, review criteria, or readiness-for-use criteria for public-safe release, controlled-room release, GRF input, GRA input, Protocol Authority input, public authority learning, technical publication, dashboards, maps, Evidence Packs, Decision Packs, Academy materials, technical baselines, public-good software outputs, and other Truth Engine-supported outputs.
8.5.7(b) Confidence thresholds shall be method-documented, versioned, fit for purpose, proportionate to risk, audience-specific, classification-aware, public-safe aware, boundary-aware, and correctionable.
8.5.7(c) Public-safe release thresholds shall account for source quality, corroboration, confidence, uncertainty, limitations, public-safe classification, privacy, cybersecurity, sovereign data, protected knowledge, community safeguards, public authority boundaries, finance boundaries, provider neutrality, sponsor non-control, and risk of public overclaim.
8.5.7(d) Controlled-room release thresholds shall account for access authority, handling class, confidentiality, restricted evidence status, public authority restrictions, finance-sensitive status, cyber-sensitive status, infrastructure-sensitive status, rights-bearing data, protected knowledge, source protection, permitted use, prohibited use, and recipient obligations.
8.5.7(e) GRF input thresholds shall account for whether evidence is sufficient for recognition-supporting, standing-supporting, maturity-context, claims-discipline, Docket, Grid, or public-safe reporting input without being described as GRF recognition or claims approval by GCRI Canada.
8.5.7(f) GRA input thresholds shall account for whether evidence is sufficient for finance-readiness input, capital-reader literacy input, Proof Pack component input, insurance-readiness input, RNFD input, NFD input, UNFSD input, or Rails handoff without being described as finance-readiness, investment advice, rating, guarantee, public finance approval, or capital commitment by GCRI Canada.
8.5.7(g) Protocol Authority input thresholds shall account for whether evidence and methods are sufficient for standards support, conformance-supporting tools, proof-receipt support, technical validity support, or protocol evidence support without creating protocol effect, certification, conformance determination, role key, smart license, entitlement state, or external force by default.
8.5.7(h) Public authority learning thresholds shall account for whether evidence is sufficient to support learning, literacy, scenario review, technical understanding, or public-safe interpretation without creating public authority decision, official guidance, regulatory approval, procurement approval, funding approval, public finance approval, public warning, emergency command, or sovereign obligation.
8.5.7(i) Technical publication thresholds shall account for accuracy, reproducibility where appropriate, method documentation, confidence, uncertainty, public-safe status, IP status, privacy, cybersecurity, controlled technology, export-control, sanctions, protected knowledge, provider-neutrality, sponsor non-control, and correction path.
8.5.7(j) Failure to meet a confidence threshold shall not necessarily mean evidence is false; it shall mean that the evidence does not meet the recorded threshold for the proposed use without further review, qualification, restriction, correction, or additional evidence.
8.5.7(k) The controlling rule shall be that confidence thresholds govern permitted use and release conditions, not institutional authority, recognition, certification, finance-readiness, public authority effect, or execution.
8.5.8 Confidence Scores in Dashboards, Maps, Reports, Evidence Packs, and Decision Packs. 8.5.8(a) Confidence scores used in dashboards, maps, reports, Evidence Packs, Decision Packs, public-safe summaries, Observatory outputs, Truth Engine outputs, Docket records, Grid records, Rails handoffs, GRF inputs, GRA inputs, Protocol Authority support, public authority materials, finance-facing materials, provider materials, sponsor materials, host materials, community-facing materials, Academy materials, technical baselines, public-good software, APIs, or public claims shall be displayed or described only with appropriate context and boundary controls.
8.5.8(b) Dashboard and map confidence displays shall avoid false precision, misleading colors, unexplained labels, hidden uncertainty, omitted limitations, unreviewed aggregation, unsafe geospatial specificity, public warning implication, emergency command implication, public authority implication, finance implication, provider preference, sponsor validation, or execution implication.
8.5.8(c) Reports and public-safe summaries using confidence scores shall state, where material, what the score measures, what it does not measure, what sources and methods support it, what limitations apply, what uncertainty remains, what use is permitted, what use is prohibited, and how the score may be corrected or updated.
8.5.8(d) Evidence Packs and Decision Packs using confidence scores shall link confidence to source records, method records, evidence records, dataset records, model records, observability records, ontology records, review records, uncertainty treatment, limitations, dependency records, and correction path.
8.5.8(e) Confidence scores used in finance-facing materials shall include finance-safe boundary language and shall not be displayed or described as finance-readiness, investment quality, bankability, fundability, credit quality, insurance quality, underwriting quality, rating, guarantee, or capital suitability.
8.5.8(f) Confidence scores used in public authority materials shall include public authority boundary language and shall not be displayed or described as official guidance, public authority finding, regulatory approval, procurement approval, funding approval, public finance approval, public warning, emergency command, or public adoption.
8.5.8(g) Confidence scores used in provider-facing or sponsor-facing materials shall preserve provider neutrality and sponsor non-control and shall not be displayed or described as endorsement, preferred status, procurement advantage, certification, recognition, sponsor approval, or outcome purchase.
8.5.8(h) Confidence scores used in public dashboards, public maps, public reports, or public claims shall be public-safe, limitation-aware, correctionable, and accompanied by sufficient explanation to prevent score inflation.
8.5.8(i) The controlling rule shall be that confidence scores must be shown in ways that improve interpretation without creating false certainty, unsafe reliance, or unauthorized status.
8.5.9 Prohibition on Marketing Confidence Scores as Ratings, Approvals, Guarantees, Certifications, Finance-Readiness, or Public Authority Decisions. 8.5.9(a) GCRI Canada shall prohibit the marketing, promotion, sale, public framing, public claim, sponsor use, provider use, host use, National Company use, Project SPV use, public authority-adjacent use, capital-reader use, media use, or Nexus use of confidence scores as ratings, approvals, guarantees, certifications, finance-readiness, public authority decisions, procurement preference, provider endorsement, sponsor approval, protocol effect, operational clearance, legal status, market authority, infrastructure operation, or execution readiness.
8.5.9(b) No person shall use a GCRI Canada confidence score to state or imply that a technology, provider, sponsor, host, National Company, Project SPV, node, cluster, Observatory output, dashboard, map, public authority context, project, asset, community, risk, resilience claim, evidence pack, decision pack, technical baseline, public-good software artifact, or Nexus interface has been certified, recognized, approved, endorsed, rated, guaranteed, made finance-ready, made procurement-ready, made public-authority-approved, or cleared for execution by GCRI Canada.
8.5.9(c) Prohibited marketing uses include use of confidence scores in pitch decks, investor materials, insurance materials, lending materials, public finance materials, procurement materials, RFP responses, provider sales materials, sponsor materials, host materials, media claims, websites, social media, badges, labels, seals, dashboards, maps, repository descriptions, technical documentation, or event materials in a manner that implies unauthorized status.
8.5.9(d) GCRI Canada shall require confidence-score users to preserve approved boundary language, permitted-use limits, prohibited-use limits, public-safe context, finance-safe context where applicable, public authority boundary language where applicable, provider-neutrality language where applicable, sponsor non-control language where applicable, correction paths, and supersession status.
8.5.9(e) Where a confidence score is marketed or used in violation of this section, GCRI Canada may require correction, withdrawal, retraction, relabeling, removal of references, public-safe clarification, controlled notice, suspension of access, termination of interface, contract remedy, or legal action where appropriate.
8.5.9(f) Sponsor support, provider participation, host support, public authority attendance, capital-reader interest, media coverage, Nexus Universe participation, Docket presence, Grid presence, Observatory visibility, Truth Engine output, technical baseline use, or public-good software use shall not cure confidence-score misuse.
8.5.9(g) GCRI Canada shall not sell, license, distribute, package, or endorse confidence scores as commercial ratings, investment scores, insurance scores, procurement rankings, provider certifications, public authority approvals, maturity seals, resilience ratings, or execution readiness marks.
8.5.9(h) The controlling rule shall be that confidence scores may support evidence interpretation, but they shall not be converted into marketable authority.
8.5.10 Confidence Records, Reviewer Records, Approval Records, and Correction Records. 8.5.10(a) GCRI Canada shall maintain, or cause to be maintained, confidence records, reviewer records, approval records where applicable, and correction records for material confidence scores, confidence bands, confidence labels, confidence indicators, confidence notes, threshold determinations, confidence changes, confidence downgrades, confidence suspensions, confidence reinstatements, and confidence-related public-safe outputs.
8.5.10(b) Confidence records shall identify the confidence artifact, evidence question, affected record or output, confidence method, method version, sources considered, evidence classes considered, data classes considered, technology domain, risk domain, context, score or label assigned, confidence basis, uncertainty treatment, limitations, downgrade factors, boundary factors, public-safe status, permitted use, prohibited use, reviewer, approval status where applicable, effective date, dependency links, and correction path.
8.5.10(c) Reviewer records shall identify reviewer role, authority, competence, access authority, conflict status, review scope, review method, dissent where any, limitation where any, approval where any, escalation pathway, and closeout requirement.
8.5.10(d) Approval records shall identify, where applicable, the actor approving use of a confidence score or threshold for public-safe release, controlled-room release, GRF input, GRA input, Protocol Authority input, public authority learning, technical publication, dashboard display, map display, Evidence Pack use, Decision Pack use, finance-facing use, provider-facing use, sponsor-facing use, or public claim support.
8.5.10(e) Correction records shall identify confidence correction type, prior confidence status, corrected confidence status, reason, source of correction, reviewer, approving actor where applicable, effective date, confidence effect, uncertainty effect, public-safe effect, finance-safe effect where material, public authority effect where material, provider effect where material, sponsor effect where material, affected dependencies, notice decision, and archive treatment.
8.5.10(f) Confidence records shall be linked, where applicable, to source comparison records, corroboration records, contradiction records, dispute records, Evidence Register entries, Method Register entries, Dataset Register entries, Model Register entries, Observability Register entries, Ontology and Controlled Vocabulary Register entries, Evidence Pack Register entries, Decision Pack Register entries, Publication and Public-Safe Output Register entries, Correction Register entries, Dependency Register entries, GRF interface records, GRA interface records, Protocol Authority interface records, public authority records, provider records, sponsor records, host records, Nexus interface records, and public claims records.
8.5.10(g) Where confidence records are corrected, challenged, reclassified, restricted, superseded, withdrawn, retracted, downgraded, suspended, reinstated, retired, or archived, affected downstream records and outputs shall be reviewed.
8.5.10(h) Confidence records, reviewer records, approval records, and correction records shall not create certification, recognition, finance-readiness, investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.5.10(i) The controlling rule shall be that confidence governance requires records because confidence that cannot be reviewed, challenged, corrected, or traced is merely institutional assertion.
8.6 Uncertainty, Limitations, and False-Precision Controls
8.6.1 Uncertainty as Required Attribute of Material Truth Engine Outputs. 8.6.1(a) GCRI Canada shall require uncertainty treatment as a material attribute of Nexus Truth Engine outputs where uncertainty affects evidence meaning, confidence, public-safe status, public authority interpretation, finance-facing interpretation, provider-facing interpretation, sponsor-facing interpretation, community-facing interpretation, protected knowledge treatment, Nexus interface meaning, public claims, or downstream dependency.
8.6.1(b) Uncertainty treatment shall apply to source comparison outputs, corroboration outputs, contradiction records, dispute records, confidence scores, Evidence Packs, Decision Packs, dashboards, maps, reports, public-safe summaries, controlled annexes, technical baselines, public-good software outputs, model outputs, AI outputs, digital twin outputs, simulation outputs, observability outputs, Docket inputs, Grid inputs, Rails handoffs, GRF inputs, GRA inputs, Protocol Authority support, public authority materials, finance-facing materials, provider materials, sponsor materials, host materials, community-facing materials, Academy materials, public claims, and correction notices.
8.6.1(c) Uncertainty shall not be omitted merely because it is difficult to quantify, inconvenient to explain, unattractive in public materials, uncomfortable for sponsors, uncomfortable for providers, uncomfortable for public authorities, undesirable for finance-facing materials, inconsistent with media narrative, or disruptive to program momentum.
8.6.1(d) Uncertainty shall be recorded in a form proportionate to the output and audience, including narrative uncertainty, categorical uncertainty, quantitative uncertainty, confidence-linked uncertainty, assumption-based uncertainty, range-based uncertainty, limitation-based uncertainty, source-based uncertainty, or controlled-room uncertainty where public disclosure would be unsafe.
8.6.1(e) Uncertainty treatment shall distinguish known facts, supported inferences, assumptions, estimates, modeled outputs, disputed points, missing evidence, stale evidence, contested evidence, public-safe omissions, and matters outside the record.
8.6.1(f) Uncertainty shall not prevent GCRI Canada from producing evidence support where the record is useful, bounded, public-safe, and fit for purpose; but uncertainty shall prevent GCRI Canada from overstating truth, precision, confidence, maturity, readiness, recognition, finance-readiness, public authority meaning, certification, procurement relevance, provider status, sponsor validation, protocol effect, or execution consequence.
8.6.1(g) Where uncertainty is material and cannot be responsibly characterized, GCRI Canada shall hold, qualify, restrict, downgrade, delay, reclassify, or decline the output rather than permit false certainty.
8.6.1(h) The controlling rule shall be that Truth Engine outputs are not institutionally reliable unless material uncertainty is identified, bounded, communicated where appropriate, and correctionable.
8.6.2 Uncertainty Types: Measurement, Model, Source, Temporal, Spatial, Contextual, Statistical, Operational, Legal, Public Authority, Community, and Interpretive. 8.6.2(a) GCRI Canada shall recognize and govern distinct types of uncertainty, including measurement uncertainty, model uncertainty, source uncertainty, temporal uncertainty, spatial uncertainty, contextual uncertainty, statistical uncertainty, operational uncertainty, legal uncertainty, public authority uncertainty, community uncertainty, protected knowledge uncertainty, finance-boundary uncertainty, provider-related uncertainty, sponsor-related uncertainty, and interpretive uncertainty.
8.6.2(b) Measurement uncertainty shall include limits arising from sensor calibration, reference sensor status, device quality, telemetry integrity, AI-RAN signal interpretation, O-RAN signal interpretation, private wireless signal interpretation, DePIN telemetry, cyber logs, geospatial resolution, satellite imagery, Earth observation conditions, environmental noise, sampling conditions, clock drift, location accuracy, and instrument error.
8.6.2(c) Model uncertainty shall include limits arising from model assumptions, training data, fine-tuning, retrieval, embedding, inference conditions, calibration, validation, drift, bias, hallucination risk, digital twin assumptions, simulation parameters, scenario boundaries, statistical fit, sensitivity, uncertainty propagation, and model applicability to the evidence question.
8.6.2(d) Source uncertainty shall include limits arising from source identity, source reliability, source independence, source completeness, source bias, source authority, source permission, source custody, source documentation, sponsor-supplied information, provider-supplied information, host-supplied information, public authority source status, community source context, and correction history.
8.6.2(e) Temporal uncertainty shall include limits arising from stale evidence, delayed data, different collection times, update frequency, latency, time-zone treatment, event sequencing, version currency, changing technology, changing public authority context, changing community context, changing provider context, changing sponsor context, and changed conditions after publication.
8.6.2(f) Spatial uncertainty shall include limits arising from location accuracy, geospatial resolution, aggregation, safe location treatment, map scale, projection, boundary ambiguity, remote sensing limits, public-safe masking, sensitive-site redaction, community-identifiable geography, infrastructure-sensitive geography, and territorial or jurisdictional boundary complexity.
8.6.2(g) Contextual uncertainty shall include limits arising from jurisdiction, legal context, public authority capacity, community context, Indigenous or local knowledge context, protected knowledge context, cultural context, technology domain, risk domain, operating conditions, sector conditions, public-safe constraints, and audience-specific meaning.
8.6.2(h) Statistical uncertainty shall include limits arising from sample size, representativeness, missing data, variance, confidence intervals where applicable, uncertainty intervals where applicable, error rates, false positives, false negatives, selection bias, survivorship bias, data imbalance, and extrapolation.
8.6.2(i) Operational uncertainty shall include limits arising from system status, deployment status, maintenance status, degraded mode, cyber conditions, incident conditions, operator context, host conditions, provider conditions, infrastructure status, supply-chain status, and field conditions.
8.6.2(j) Legal and public authority uncertainty shall include limits arising from applicable law, jurisdictional authority, public authority capacity, official or non-official source status, regulatory context, procurement context, public finance context, emergency-management context, public warning context, confidentiality, data-sharing authority, and whether a public authority has acted through its own lawful process and record.
8.6.2(k) Community, Indigenous, local, territorial, cultural, environmental, and protected knowledge uncertainty shall include limits arising from consent or non-consent, access restrictions, cultural protocol, community protocol, translation, contextual meaning, public-safe restrictions, relationship-based knowledge, protected knowledge limits, and risks of extraction, exposure, erasure, or harm.
8.6.2(l) Interpretive uncertainty shall include limits arising from competing explanations, ambiguous evidence, conflicting definitions, semantic drift, translation differences, localization differences, controlled vocabulary mismatch, incomplete context, inference chains, and unresolved disputes.
8.6.2(m) The controlling rule shall be that uncertainty must be named at the level at which it arises because generic uncertainty language cannot safely govern complex evidence.
8.6.3 Limitation Statements for Sources, Methods, Models, Data, Dashboards, Maps, Digital Twins, Simulations, and AI Outputs. 8.6.3(a) GCRI Canada shall require limitation statements for material Truth Engine outputs where sources, methods, models, data, dashboards, maps, digital twins, simulations, AI outputs, observability systems, confidence scores, or public-safe summaries could be misread beyond their recorded scope.
8.6.3(b) Source limitation statements shall identify, where material, source type, source authority, source completeness, source independence, source permission, source reliability, source timeliness, source bias, source custody, source context, lawful-use limits, public-safe limits, and correction path.
8.6.3(c) Method limitation statements shall identify, where material, method scope, method version, assumptions, exclusions, required inputs, output limits, validation status, calibration status, context limits, technology-domain limits, public-safe limits, finance-boundary limits, public authority boundary limits, provider-neutrality limits, sponsor non-control limits, and correction path.
8.6.3(d) Model and AI limitation statements shall identify, where material, model identity, model version, dataset dependencies, training or retrieval limits, inference limits, hallucination risks, bias risks, drift risks, prompt or input limits, human review requirements, prohibited uses, public-safe limits, privacy limits, cyber limits, sovereign data limits, protected knowledge limits, and correction path.
8.6.3(e) Data limitation statements shall identify, where material, dataset source, data class, quality, completeness, missingness, sampling limits, temporal coverage, spatial coverage, transformations, de-identification status, re-identification risk, inference risk, lawful basis, permission limits, transfer limits, publication limits, and correction path.
8.6.3(f) Dashboard and map limitation statements shall identify, where material, update frequency, latency, data coverage, aggregation, geospatial precision, safe-location treatment, visualization simplification, label meaning, score meaning, color meaning, public warning boundary, emergency command boundary, public authority boundary, finance boundary, provider neutrality, sponsor non-control, permitted use, prohibited use, and correction path.
8.6.3(g) Digital twin and simulation limitation statements shall identify, where material, assumptions, boundary conditions, calibration, validation, scenario scope, sensitivity, input data limits, uncertainty propagation, model drift, omitted variables, counterfactual limits, temporal limits, spatial limits, and the distinction between scenario output and decision.
8.6.3(h) Limitation statements shall be linked, where applicable, to evidence records, source comparison records, confidence records, method records, dataset records, model records, observability records, public-safe output records, correction records, and dependency records.
8.6.3(i) Limitation statements shall not be used to excuse defective evidence, unsafe publication, unreviewed methods, unlawful data use, public authority confusion, finance overclaim, provider preference, sponsor control, or unsupported public claims.
8.6.3(j) The controlling rule shall be that limitations must define what an output can and cannot mean; they are part of the output, not peripheral disclaimers.
8.6.4 False-Precision Controls. 8.6.4(a) GCRI Canada shall maintain false-precision controls to prevent Truth Engine outputs from appearing more exact, certain, current, complete, authoritative, comparable, public-safe, finance-relevant, public authority-relevant, provider-relevant, sponsor-relevant, or execution-ready than the records support.
8.6.4(b) False precision may arise through numeric scores, confidence bands, percentages, rankings, colors, dashboards, maps, heatmaps, thresholds, badges, labels, maturity-context signals, readiness-context signals, benchmark outputs, model outputs, AI-generated summaries, digital twin outputs, geospatial overlays, proof receipts, blockchain anchors, DePIN records, sensor fusion, risk indicators, resilience indicators, or simplified public-facing statements.
8.6.4(c) Numeric outputs shall not be used where the underlying evidence does not support numeric precision. Where numeric outputs are used, GCRI Canada shall identify method, scale, meaning, limits, uncertainty, public-safe status, permitted use, prohibited use, and correction path.
8.6.4(d) Rankings and ordered lists shall not be used where they would imply certification, rating, provider preference, procurement preference, public authority approval, finance-readiness, maturity status, recognition, or market superiority without proper authority and record.
8.6.4(e) Dashboard colors, map colors, alert-like symbols, warning-like icons, labels, badges, seals, and visual status indicators shall not imply public warning, emergency command, public authority decision, certification, recognition, finance-readiness, procurement approval, provider endorsement, sponsor approval, protocol effect, rating, guarantee, or execution readiness.
8.6.4(f) Aggregated outputs shall not conceal material variation, community-specific risk, protected knowledge limits, local context, Indigenous or territorial context, public authority context, minority evidence, missing data, stale data, or conflicting evidence where such concealment would mislead.
8.6.4(g) Simplified public-safe summaries shall not remove uncertainty, limitations, confidence caveats, classification limits, public authority boundaries, finance boundaries, provider-neutrality limits, sponsor non-control limits, or correction paths where removal would create misleading certainty.
8.6.4(h) Where false precision is detected, GCRI Canada shall relabel, revise, qualify, downgrade, reclassify, restrict, correct, supersede, withdraw, retract, or reissue the affected output and review downstream dependencies.
8.6.4(i) The controlling rule shall be that precision is permitted only where earned by the record; otherwise precision becomes overclaim.
8.6.5 Uncertainty Visualization and Public-Safe Explanation. 8.6.5(a) GCRI Canada may use uncertainty visualization and public-safe explanation methods to make uncertainty understandable without making it misleading, unsafe, overly technical, falsely reassuring, falsely alarming, public-authority-like, finance-like, certification-like, recognition-like, or execution-like.
8.6.5(b) Uncertainty visualization may include ranges, bands, categories, confidence intervals where appropriate, uncertainty intervals where appropriate, shaded areas, qualitative labels, missing-data markers, stale-data markers, disputed-evidence markers, source-limitation markers, map-resolution limits, dashboard notes, public-safe annotations, controlled annexes, and explanatory text.
8.6.5(c) Uncertainty visualization shall not use designs that imply public warning, emergency command, official hazard designation, regulatory finding, procurement ranking, financial rating, insurance rating, credit rating, provider endorsement, sponsor approval, certification, recognition, maturity status, protocol effect, operational clearance, or execution readiness.
8.6.5(d) Public-safe explanation shall state, where material, what is known, what is uncertain, what is disputed, what is missing, what is stale, what is inferred, what is assumed, what is modeled, what is excluded, what is restricted, what cannot be published, what should not be relied upon, and how the output may change.
8.6.5(e) Public-safe explanations shall be proportionate to audience and risk. Technical audiences may receive detailed method and uncertainty treatment, while public-facing audiences may receive bounded plain-language explanations, provided that simplification does not create false certainty or unsafe reliance.
8.6.5(f) Where full uncertainty explanation cannot be public because of privacy, cybersecurity, public authority restrictions, protected knowledge, community safety, sovereign data, commercial sensitivity, finance sensitivity, legal sensitivity, source protection, or controlled technology, GCRI Canada may issue public-safe summaries and controlled annexes that preserve public meaning without unsafe disclosure.
8.6.5(g) Uncertainty visualization and explanation shall be reviewed for accessibility, translation, localization, cultural context, community context, public authority context, and public-safe interpretation where material.
8.6.5(h) The controlling rule shall be that uncertainty must be made legible enough to prevent overclaim and bounded enough to prevent harm.
8.6.6 Treatment of Unknowns, Assumptions, Proxies, Gaps, and Inference Chains. 8.6.6(a) GCRI Canada shall maintain methods for the treatment of unknowns, assumptions, proxies, gaps, and inference chains in material Truth Engine outputs.
8.6.6(b) Unknowns shall be recorded where material facts, sources, conditions, causes, impacts, permissions, contexts, dependencies, or downstream effects are not known, not yet known, not knowable through available methods, not lawfully accessible, not safely publishable, or not properly within GCRI Canada’s role to determine.
8.6.6(c) Assumptions shall be recorded where an output depends on unstated or stated premises, model conditions, scenario conditions, source interpretation, method selection, public authority context, community context, technology status, provider status, sponsor status, legal context, finance-facing context, or operating conditions.
8.6.6(d) Proxies shall be recorded where an indirect measure, surrogate indicator, representative dataset, benchmark, model output, similarity measure, public record, index, synthetic data, reference sensor, or substituted source is used in place of direct evidence.
8.6.6(e) Gaps shall be recorded where evidence is missing, incomplete, stale, restricted, non-public-safe, inaccessible, uncollected, redacted, disputed, geographically limited, temporally limited, population-limited, source-limited, method-limited, or outside current review capacity.
8.6.6(f) Inference chains shall be recorded where an output depends on multiple steps from source to data, data to evidence, evidence to confidence, confidence to summary, summary to dashboard, dashboard to public-safe output, public-safe output to handoff, or handoff to downstream use.
8.6.6(g) Assumptions, proxies, gaps, and inference chains shall be distinguished from direct evidence and shall not be hidden inside confidence scores, dashboards, maps, AI-generated summaries, digital twins, simulations, risk indicators, resilience indicators, Evidence Packs, Decision Packs, or public claims.
8.6.6(h) Where an output materially depends on assumptions, proxies, gaps, or inference chains, GCRI Canada shall determine whether the output requires qualification, downgrade, controlled-room treatment, public-safe explanation, additional evidence collection, restriction, delay, supersession, withdrawal, or correction.
8.6.6(i) The controlling rule shall be that unknowns, assumptions, proxies, gaps, and inference chains must be visible in the record because hidden assumptions create false certainty.
8.6.7 Confidence / Uncertainty Pairing Requirements. 8.6.7(a) GCRI Canada shall pair confidence and uncertainty treatment in material Nexus Truth Engine outputs so that confidence is not communicated without uncertainty and uncertainty is not communicated without sufficient context for interpretation.
8.6.7(b) Where a confidence score, confidence band, confidence label, confidence note, or confidence indicator is used, the output shall state or link to the uncertainty, limitation, assumptions, source constraints, method constraints, missing evidence, stale evidence, disputed evidence, public-safe constraints, and correction path material to that confidence.
8.6.7(c) Where uncertainty is substantial, unresolved, high-consequence, context-dependent, or public-safe restricted, the output shall not use confidence language that implies stronger evidence than the record supports.
8.6.7(d) Where confidence is high but uncertainty remains material, GCRI Canada shall explain the difference between confidence in the available evidence and uncertainty about scope, future conditions, external validity, legal meaning, public authority meaning, finance-facing meaning, provider meaning, sponsor meaning, or downstream effect.
8.6.7(e) Where uncertainty is low but evidence remains limited in purpose, scope, audience, public-safe status, finance-facing status, public authority-facing status, provider-facing status, sponsor-facing status, or jurisdiction, GCRI Canada shall preserve the limitation and shall not permit confidence to migrate into unauthorized contexts.
8.6.7(f) Confidence / uncertainty pairing shall apply to dashboards, maps, public-safe summaries, reports, Evidence Packs, Decision Packs, Truth Engine outputs, Observatory outputs, Docket inputs, Grid inputs, Rails handoffs, GRF inputs, GRA inputs, Protocol Authority support, public authority materials, finance-facing materials, provider materials, sponsor materials, community-facing materials, Academy materials, technical baselines, public-good software documentation, and public claims.
8.6.7(g) Confidence / uncertainty pairing shall not create certification, recognition, finance-readiness, investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.6.7(h) The controlling rule shall be that confidence without uncertainty overstates truth, and uncertainty without context obscures truth.
8.6.8 Uncertainty Escalation for High-Consequence Outputs. 8.6.8(a) GCRI Canada shall escalate uncertainty treatment for high-consequence outputs where uncertainty may materially affect public safety, privacy, cybersecurity, sovereign data, protected knowledge, community harm, public authority interpretation, finance-facing interpretation, provider-neutrality, sponsor non-control, procurement implication, certification implication, recognition implication, protocol implication, public warning implication, emergency-command implication, market consequence, legal compliance, or institutional trust.
8.6.8(b) High-consequence outputs may include public-safe reports, public dashboards, public maps, hazard-adjacent outputs, health-adjacent outputs, cyber-sensitive outputs, infrastructure-sensitive outputs, public authority learning materials, finance-facing materials, GRF inputs, GRA inputs, Protocol Authority support, Docket records, Grid records, Observatory outputs, Truth Engine outputs, Rails handoffs, National Company interfaces, Project SPV interfaces, provider-facing materials, sponsor-facing materials, host-facing materials, community-facing materials, media materials, and public claims.
8.6.8(c) Uncertainty escalation may require evidence steward review, method steward review, data steward review, model steward review, public-safe publication review, privacy review, cybersecurity review, AI review, sovereign data review, safeguards review, Indigenous or protected knowledge review, public authority boundary review, finance boundary review, provider-neutrality review, sponsor non-control review, competition review, legal review, committee review, officer escalation, board escalation, or external expert review where appropriate.
8.6.8(d) Where uncertainty is high and consequence is high, GCRI Canada shall consider hold, restriction, controlled-room use, public-safe qualification, downgrade, additional evidence collection, method review, model review, public authority boundary review, finance-boundary review, safeguards review, delay, withdrawal, or non-publication.
8.6.8(e) Where uncertainty cannot be publicly explained without exposing protected material, GCRI Canada may issue controlled uncertainty notes, controlled annexes, or targeted notices to authorized recipients while preserving public-safe meaning in any public output.
8.6.8(f) High-consequence uncertainty shall not be suppressed by sponsor request, provider request, public authority discomfort, capital-reader preference, media strategy, program deadline, event timing, technical convenience, or public-relations concern.
8.6.8(g) Escalation records shall identify the output, uncertainty type, consequence type, review pathway, interim controls, decision, limitations, public-safe status, notice decision, and correction path.
8.6.8(h) The controlling rule shall be that uncertainty must be escalated when the cost of being misunderstood is high.
8.6.9 Correction Where Uncertainty Is Understated or Misread. 8.6.9(a) GCRI Canada shall correct Truth Engine outputs where uncertainty has been understated, omitted, misclassified, concealed, visually minimized, compressed, mistranslated, misread, misused, or communicated in a manner that creates false precision, false confidence, public authority confusion, finance overclaim, provider preference, sponsor validation, certification implication, recognition implication, protocol implication, public warning implication, emergency-command implication, or execution implication.
8.6.9(b) Correction shall apply where uncertainty is understated in confidence scores, dashboards, maps, reports, public-safe summaries, controlled annexes, Evidence Packs, Decision Packs, Docket records, Grid records, Observatory outputs, Truth Engine outputs, Rails handoffs, GRF inputs, GRA inputs, Protocol Authority support, public authority materials, finance-facing materials, provider materials, sponsor materials, host materials, community-facing materials, technical baselines, public-good software documentation, Academy materials, media materials, public claims, or correction notices.
8.6.9(c) Misread uncertainty shall include cases where audiences reasonably interpret uncertainty language, labels, scores, colors, bands, maps, charts, dashboards, summaries, or caveats as stronger, weaker, more official, more public-safe, more finance-relevant, more public authority-relevant, more provider-relevant, more sponsor-validating, or more execution-ready than intended.
8.6.9(d) Where uncertainty is understated or misread, GCRI Canada shall consider relabeling, revised uncertainty language, revised limitation statement, revised dashboard design, revised map design, revised confidence pairing, public-safe clarification, controlled correction notice, public correction notice, downgrade, restriction, supersession, withdrawal, retraction, training update, method update, or interface correction.
8.6.9(e) Where third parties use GCRI Canada outputs to suppress uncertainty, remove limitations, exaggerate confidence, market evidence as ratings, claim approval, imply finance-readiness, imply public authority decision, imply provider endorsement, imply sponsor validation, imply certification, imply recognition, imply protocol effect, or imply execution readiness, GCRI Canada shall require correction, withdrawal, retraction, removal, public-safe clarification, controlled notice, interface suspension, or other remedy as appropriate.
8.6.9(f) Correction of understated uncertainty shall include dependency review where affected outputs have been used in public authority materials, finance-facing materials, GRF materials, GRA materials, Protocol Authority materials, provider materials, sponsor materials, host materials, community-facing materials, public-safe publications, dashboards, maps, technical baselines, public-good software, Academy materials, media materials, or public claims.
8.6.9(g) GCRI Canada shall not allow reputational concern, sponsor concern, provider concern, public authority concern, capital-reader concern, or media concern to prevent correction where uncertainty has been understated or misread.
8.6.9(h) The controlling rule shall be that uncertainty correction is required whenever the public or controlled meaning of an output becomes more certain than the record permits.
8.6.10 Uncertainty Records, Limitation Records, Public-Safe Notes, and Supersession Records. 8.6.10(a) GCRI Canada shall maintain, or cause to be maintained, uncertainty records, limitation records, public-safe notes, and supersession records for material Truth Engine outputs where uncertainty, limitations, public-safe explanation, or later replacement affects evidence meaning, confidence, permitted use, public-safe status, public authority interpretation, finance-facing interpretation, provider-facing interpretation, sponsor-facing interpretation, community-facing interpretation, Nexus interface meaning, downstream dependency, or public claims.
8.6.10(b) Uncertainty records shall identify the output, evidence question, uncertainty type, uncertainty source, affected sources, affected methods, affected datasets, affected models, affected observability records, affected assumptions, affected proxies, affected gaps, affected inference chains, confidence relationship, public-safe effect, finance-safe effect where material, public authority effect where material, provider effect where material, sponsor effect where material, community effect where material, reviewer, review status, permitted use, prohibited use, and correction path.
8.6.10(c) Limitation records shall identify source limitations, method limitations, data limitations, model limitations, AI limitations, digital twin limitations, simulation limitations, dashboard limitations, map limitations, public-safe limitations, access limitations, handling limitations, jurisdictional limitations, temporal limitations, spatial limitations, community limitations, public authority limitations, finance-boundary limitations, provider-neutrality limitations, sponsor non-control limitations, and downstream-use limitations.
8.6.10(d) Public-safe notes shall identify what uncertainty or limitation information may be publicly communicated, what information must remain controlled, what information is restricted by privacy, cybersecurity, sovereign data, public authority restriction, protected knowledge, community safeguard, commercial sensitivity, finance sensitivity, legal sensitivity, source protection, or controlled technology, and how the public-safe explanation preserves meaning without unsafe disclosure.
8.6.10(e) Supersession records shall identify prior output, superseding output, reason for supersession, uncertainty change, limitation change, confidence change, source change, method change, data change, model change, public-safe change, boundary-language change, effective date, affected dependencies, notice decision, archive status, and continuing validity where any.
8.6.10(f) Uncertainty records, limitation records, public-safe notes, and supersession records shall be linked, where applicable, to Evidence Register entries, Method Register entries, Dataset Register entries, Model Register entries, Observability Register entries, Ontology and Controlled Vocabulary Register entries, source comparison records, confidence records, corroboration records, contradiction records, dispute records, Evidence Pack entries, Decision Pack entries, Publication and Public-Safe Output Register entries, Correction Register entries, Dependency Register entries, GRF interface records, GRA interface records, Protocol Authority interface records, public authority records, provider records, sponsor records, host records, Nexus interface records, and public claims records.
8.6.10(g) Uncertainty records, limitation records, public-safe notes, and supersession records shall not create certification, recognition, finance-readiness, investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.6.10(h) The controlling rule shall be that uncertainty and limitations must be recorded because unrecorded uncertainty cannot govern confidence, publication, reliance, correction, or trust.
8.7 Truth Engine Output Classes
8.7.1 Internal Evidence Output. 8.7.1(a) GCRI Canada may classify a Nexus Truth Engine output as an Internal Evidence Output where the output is intended for internal evidence review, method review, data review, model review, observability review, ontology review, public-safe review, correction review, governance review, committee review, officer review, Board review, or other internal institutional use within GCRI Canada’s non-executing evidence-and-methods mandate.
8.7.1(b) Internal Evidence Outputs may include source comparison notes, confidence notes, uncertainty notes, limitation notes, contradiction notes, dispute notes, missing-evidence notes, stale-evidence notes, spoof-risk notes, method review notes, data quality notes, model evaluation notes, observability review notes, ontology review notes, correction triggers, dependency notes, draft Evidence Pack components, draft Decision Pack components, and internal public-safe review materials.
8.7.1(c) Internal Evidence Outputs shall identify, where material, the evidence question, source records, method records, dataset records, model records, observability records, ontology terms, confidence treatment, uncertainty treatment, limitations, reviewer, status, access class, handling class, permitted use, prohibited use, public-safe status, dependency links, and correction path.
8.7.1(d) Internal Evidence Outputs shall not be externally circulated, publicly referenced, finance-facing, public authority-facing, GRF-facing, GRA-facing, Protocol Authority-facing, provider-facing, sponsor-facing, host-facing, community-facing, or media-facing unless reclassified, reviewed, and approved for the relevant output class.
8.7.1(e) Internal classification shall not permit weak records, uncontrolled methods, missing source lineage, improper AI use, unsafe data handling, public authority ambiguity, finance overclaim, provider preference, sponsor influence, protected knowledge exposure, or uncorrectable outputs. Internal materials remain subject to evidence integrity, safeguards, privacy, cybersecurity, controlled vocabulary, validity-by-record, and correctionability.
8.7.1(f) No Internal Evidence Output shall create certification, recognition, finance-readiness, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.7.1(g) Where an Internal Evidence Output is later used in another output class, GCRI Canada shall preserve source lineage, method, confidence, uncertainty, limitations, review status, access status, boundary language, and correction path.
8.7.1(h) The controlling rule shall be that internal Truth Engine output is for institutional evidence discipline, not hidden authority, informal decision-making, or unreviewed external reliance.
8.7.2 Controlled-Room Output. 8.7.2(a) GCRI Canada may classify a Nexus Truth Engine output as a Controlled-Room Output where the output may be used only within a controlled room, data room, evidence room, clean room, secure collaboration room, public authority room, finance-safe room, technical review room, safeguards room, cyber room, protected knowledge room, or other restricted-access environment.
8.7.2(b) Controlled-Room Outputs may include restricted evidence summaries, controlled annexes, source comparison records, sensitive dashboards, sensitive maps, cyber-sensitive materials, infrastructure-sensitive materials, public authority restricted materials, finance-sensitive materials, health-sensitive materials, sovereign data materials, community-protected materials, Indigenous or protected knowledge materials, model evaluation materials, vulnerability-sensitive materials, and high-consequence dispute materials.
8.7.2(c) Controlled-Room Outputs shall identify room purpose, room sponsor where any, room host where any, room custodian, access authority, permitted participants, prohibited participants, data classes, evidence classes, handling class, public-safe status, confidentiality terms, AI-use limits, recording limits, export limits, citation limits, redistribution limits, permitted use, prohibited use, boundary language, review status, correction path, and closeout path.
8.7.2(d) Controlled-Room Outputs shall not be copied, exported, summarized, photographed, screen-captured, embedded, quoted, redistributed, used in public materials, used in finance-facing materials, used in public authority materials, used in provider materials, used in sponsor materials, or used in public claims except as expressly permitted by the room rules and applicable record.
8.7.2(e) Controlled-room treatment shall be used where public disclosure would risk privacy harm, cybersecurity harm, infrastructure exposure, public authority confusion, finance overclaim, protected knowledge misuse, community harm, source exposure, retaliation, legal risk, commercial sensitivity, controlled technology exposure, sanctions or export-control risk, or unsafe public reliance.
8.7.2(f) Controlled-Room Outputs shall not create certification, recognition, finance-readiness, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.7.2(g) Where a Controlled-Room Output is converted into a public-safe summary, GRF input, GRA input, Protocol Authority input, public authority learning output, technical annex, dashboard, map, or report, GCRI Canada shall apply reclassification, redaction, aggregation, public-safe review, boundary review, and correction review before release.
8.7.2(h) The controlling rule shall be that controlled-room output permits safer review of sensitive evidence; it does not create secret authority, privileged status, financial effect, public authority effect, or execution clearance.
8.7.3 Public-Safe Output. 8.7.3(a) GCRI Canada may classify a Nexus Truth Engine output as a Public-Safe Output where the output has been reviewed and approved for public-safe release within recorded scope, audience, limitations, classification, confidence, uncertainty, public authority boundary, finance boundary, provider-neutrality boundary, sponsor non-control boundary, protected knowledge safeguards, and correction path.
8.7.3(b) Public-Safe Outputs may include public-safe reports, public-safe summaries, public-safe dashboards, public-safe maps, public-safe visualizations, public-safe technical notes, public-safe glossaries, public-safe Academy materials, public-safe correction notices, public-safe Observatory summaries, public-safe Truth Engine summaries, public-safe Docket summaries, public-safe Grid summaries, public-safe Rails summaries, public-good software documentation, and technical baseline summaries.
8.7.3(c) Public-Safe Outputs shall identify, where material, source records, method records, evidence class, data class, public-safe status, redactions, aggregations, generalizations, responsible non-disclosure basis where any, confidence, uncertainty, limitations, permitted use, prohibited use, boundary language, correction path, supersession path, withdrawal path, retraction path where applicable, and archive path.
8.7.3(d) Public-safe status shall not mean complete disclosure, unrestricted reuse, public authority approval, finance-readiness, certification, recognition, procurement relevance, provider endorsement, sponsor approval, protocol effect, public warning, emergency command, operational clearance, or execution readiness.
8.7.3(e) Public-Safe Outputs shall not disclose personal information, rights-bearing data, cyber-sensitive information, infrastructure-sensitive information, public authority restricted information, sovereign-sensitive information, protected knowledge, community-sensitive information, source-protected information, controlled technology, confidential materials, or other restricted content unless lawful, safe, authorized, mission-compatible, and records-valid.
8.7.3(f) Public-Safe Outputs shall not create certification, recognition, finance-readiness, investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.7.3(g) Where a Public-Safe Output becomes inaccurate, stale, unsafe, overclaimed, misclassified, misused, or misread, GCRI Canada shall correct, supersede, withdraw, retract, relabel, restrict, or reissue the output and review downstream dependencies.
8.7.3(h) The controlling rule shall be that public-safe output makes evidence publicly usable only within recorded limits, not publicly authoritative for all purposes.
8.7.4 Public Authority Learning Output. 8.7.4(a) GCRI Canada may classify a Nexus Truth Engine output as a Public Authority Learning Output where the output is prepared for evidence literacy, technical literacy, AI literacy, cyber literacy, systems-risk learning, scenario learning, public-safe interpretation, public authority capacity-building, or public-sector learning without delegated public authority.
8.7.4(b) Public Authority Learning Outputs may include briefings, scenario notes, evidence comparison summaries, confidence and uncertainty notes, public-safe dashboards, public-safe maps, controlled annexes, technical explainers, model limitation notes, cyber learning notes, observability learning materials, public authority room materials, and correction notices.
8.7.4(c) Public Authority Learning Outputs shall identify public authority capacity classification, audience, source records, method records, public authority data status, public-safe status, access class, handling class, permitted use, prohibited use, confidence, uncertainty, limitations, non-delegation language, non-endorsement language, non-procurement language, non-warning language, non-regulatory language, non-funding language, non-public-finance language, and correction path.
8.7.4(d) Public Authority Learning Outputs shall not be represented as official guidance, regulatory approval, procurement approval, funding approval, public finance approval, public warning, emergency command, public health order, public safety directive, compliance determination, enforcement position, safe harbor, public adoption, sovereign obligation, or public authority decision.
8.7.4(e) Public authority names, logos, titles, photos, quotes, agency references, jurisdiction references, regulator-listening references, public finance references, emergency-management references, and public-sector data references shall be used only under applicable reference controls.
8.7.4(f) Public Authority Learning Outputs shall not create certification, recognition, finance-readiness, investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.7.4(g) Where Public Authority Learning Outputs are used or misread as public authority decisions, official guidance, public warnings, procurement approvals, regulatory approvals, funding approvals, public finance approvals, or sovereign obligations, GCRI Canada shall correct, clarify, restrict, withdraw, reissue, or notify affected interfaces as appropriate.
8.7.4(h) The controlling rule shall be that public authority learning output supports public-sector understanding but leaves public authority with public authorities.
8.7.5 GRF Input Output. 8.7.5(a) GCRI Canada may classify a Nexus Truth Engine output as a GRF Input Output where the output is prepared to support The Global Risks Forum (GRF) through technical evidence inputs, source comparison records, confidence notes, uncertainty notes, Docket inputs, Grid inputs, maturity-context inputs, recognition-supporting evidence inputs, claims-discipline support, public-safe reporting support, correction records, or public-safe summaries.
8.7.5(b) GRF Input Outputs shall remain evidence and methods support to GRF. They shall not constitute GRF recognition, standing, maturity records, claims approval, public-facing legitimacy, registry status, stakeholder formation, public-safe reporting status, or public claim approval by GCRI Canada.
8.7.5(c) GRF Input Outputs shall identify source records, method records, evidence class, data class, public-safe status, GRF-facing status, access class, handling class, confidence, uncertainty, limitations, permitted use, prohibited use, boundary language, correction path, supersession path, withdrawal path, retraction path where applicable, and dependency links.
8.7.5(d) GRF shall remain responsible for any GRF act, including recognition, standing, maturity record, claims discipline, stakeholder formation, public-safe reporting, registry status, or public-facing legitimacy, through GRF’s own authority, procedures, records, and review.
8.7.5(e) GRF Input Outputs shall not be publicly described as GRF approval unless GRF has separately created the relevant approval or status through its own proper record and public-safe process.
8.7.5(f) GRF Input Outputs shall not create certification, finance-readiness, investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.7.5(g) Where a GRF Input Output is corrected, disputed, downgraded, reclassified, superseded, withdrawn, or retracted, GCRI Canada shall review affected GRF interface records and coordinate correction with GRF where appropriate.
8.7.5(h) The controlling rule shall be that GRF Input Outputs support GRF’s legitimacy function but do not perform it.
8.7.6 GRA Input Output. 8.7.6(a) GCRI Canada may classify a Nexus Truth Engine output as a GRA Input Output where the output is prepared to support The Global Risks Alliance (GRA) through technical evidence inputs, risk evidence, host readiness evidence, node evidence, source comparison records, confidence notes, uncertainty notes, Proof Pack components, insurance-readiness inputs, capital-reader literacy inputs, RNFD inputs, NFD inputs, UNFSD inputs, Rails handoffs, correction records, or finance-safe summaries.
8.7.6(b) GRA Input Outputs shall remain evidence and methods support to GRA. They shall not constitute finance-readiness, capital-readiness, insurance-readiness, routeability, capital suitability, investor suitability, bankability, fundability, investment advice, securities recommendation, brokerage, placement, finder activity, lending, underwriting, insurance placement, rating, guarantee, public finance approval, capital commitment, or other financial act by GCRI Canada.
8.7.6(c) GRA Input Outputs shall identify source records, method records, evidence class, data class, finance-safe status where material, public-safe status, GRA-facing status, access class, handling class, confidence, uncertainty, limitations, permitted use, prohibited use, no-advice language, no-solicitation language, no-rating language, no-guarantee language, no-public-finance-approval language, correction path, supersession path, withdrawal path, retraction path where applicable, and dependency links.
8.7.6(d) GRA shall remain responsible for any GRA output, including finance-readiness, capital-readiness, insurance-readiness, capital readability, Proof Pack discipline, capital-reader room, RNFD, NFD, UNFSD, or regulated-perimeter output, through GRA’s own authority, procedures, records, review, and finance-safe boundary language.
8.7.6(e) GRA Input Outputs shall not be used in pitch decks, investment materials, insurance materials, lending materials, public finance materials, securities materials, procurement materials, sponsor materials, provider materials, SPV materials, National Company materials, or capital-reader materials in a manner that implies GCRI Canada investment advice, rating, guarantee, finance-readiness, or public finance approval.
8.7.6(f) GRA Input Outputs shall not create certification, recognition, public authority decision, procurement approval, provider endorsement, sponsor approval, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.7.6(g) Where a GRA Input Output is corrected, disputed, downgraded, reclassified, superseded, withdrawn, or retracted, GCRI Canada shall review affected GRA interface records and coordinate correction with GRA where appropriate.
8.7.6(h) The controlling rule shall be that GRA Input Outputs support finance-readiness discipline but do not issue finance-readiness or financial consequence.
8.7.7 Protocol Authority Input Output. 8.7.7(a) GCRI Canada may classify a Nexus Truth Engine output as a Protocol Authority Input Output where the output is prepared to support Nexus Standards / Protocol Authority through evidence requirements, method profiles, source comparison records, confidence notes, uncertainty notes, ontology, controlled vocabulary, schemas, data dictionaries, proof-receipt logic, technical baselines, public-good software, APIs, reference architectures, conformance-supporting tools, evaluation harnesses, benchmark cards, correction records, or technical validity support.
8.7.7(b) Protocol Authority Input Outputs shall remain evidence and methods support. They shall not constitute protocol authority, certification, conformance determination, role key issuance, smart-license issuance, entitlement state, proof-receipt legal effect, external force, legal validity, operational clearance, technical certification, or protocol effect by default.
8.7.7(c) Protocol Authority Input Outputs shall identify source records, method records, evidence class, data class, technical baseline status where any, software status where any, public-safe status, protocol-facing status, access class, handling class, confidence, uncertainty, limitations, permitted use, prohibited use, protocol-boundary language, no-certification language, no-conformance-determination language, correction path, supersession path, withdrawal path, retirement path, and dependency links.
8.7.7(d) Nexus Standards / Protocol Authority shall remain responsible for any protocol effect, conformance logic, role keys, smart licenses, proof receipts, entitlement states, anchoring discipline, technical validity surface, or standards effect created through its own authority, instruments, records, procedures, and boundary language.
8.7.7(e) Technical authorship, schema authorship, benchmark support, proof-receipt support, software maintenance, API custody, repository custody, or technical baseline support by GCRI Canada shall not create protocol effect or certification by implication.
8.7.7(f) Protocol Authority Input Outputs shall not create recognition, finance-readiness, investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.7.7(g) Where a Protocol Authority Input Output is corrected, disputed, downgraded, reclassified, superseded, withdrawn, or retired, GCRI Canada shall review affected Protocol Authority interface records and coordinate correction with the relevant Protocol Authority where appropriate.
8.7.7(h) The controlling rule shall be that Protocol Authority Input Outputs support protocol discipline but do not create protocol effect by default.
8.7.8 Nexus Observatory Output. 8.7.8(a) GCRI Canada may classify a Nexus Truth Engine output as a Nexus Observatory Output where the output is prepared to support observability evidence, node evidence, hub evidence, cluster evidence, hotspot evidence, regional cluster evidence, national dense core evidence, sensor evidence, AI-RAN signal evidence, O-RAN signal evidence, private wireless signal evidence, DePIN evidence, geospatial evidence, cyber telemetry, digital twin assumptions, dashboard methods, map methods, degraded-mode records, resilience indicator records, continuity signal records, Observatory Evidence Packs, and public-safe Observatory summaries.
8.7.8(b) Nexus Observatory Outputs shall remain observability evidence and methods outputs. They shall not constitute surveillance authority, public warning, emergency command, infrastructure operation, public authority decision, regulatory finding, procurement approval, finance-readiness, provider endorsement, sponsor approval, certification, recognition, rating, guarantee, protocol effect, operational clearance, or execution consequence by default.
8.7.8(c) Nexus Observatory Outputs shall identify observability surface, source records, system records, node or cluster context, owner where known, operator where applicable, host where applicable, provider where any, GCRI Canada role, GCRI Canada non-role, data classes, evidence classes, collection method, update frequency, latency, geography or safe location treatment, confidence, uncertainty, limitations, classification, public-safe status, access status, permitted use, prohibited use, boundary language, correction path, supersession path, withdrawal path, and archive path.
8.7.8(d) Nexus Observatory Outputs involving dashboards, maps, alerts, indicators, scores, colors, or geospatial layers shall be reviewed to prevent public warning implication, emergency command implication, public authority confusion, infrastructure exposure, privacy harm, community harm, protected knowledge exposure, finance overclaim, provider preference, sponsor validation, and false precision.
8.7.8(e) Nexus Observatory Outputs shall distinguish raw signal, processed signal, fused signal, inferred condition, modeled condition, dashboard output, map layer, public-safe summary, controlled annex, Docket input, Grid input, Truth Engine comparison, Rails handoff, GRF input, GRA input, Protocol Authority support, and enterprise-stack handoff.
8.7.8(f) Nexus Observatory Outputs shall not create investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, public warning, emergency command, certification, recognition, finance-readiness, rating, guarantee, protocol effect, operational clearance, legal status, market authority, infrastructure operation, or execution consequence by default.
8.7.8(g) Where a Nexus Observatory Output is corrected, disputed, downgraded, reclassified, restricted, superseded, withdrawn, or retracted, GCRI Canada shall update applicable observability records and review affected downstream dependencies.
8.7.8(h) The controlling rule shall be that Nexus Observatory Outputs make observable conditions evidence-legible, not officially actionable by GCRI Canada.
8.7.9 Nexus Risk Management Output. 8.7.9(a) GCRI Canada may classify a Nexus Truth Engine output as a Nexus Risk Management Output where the output is prepared to support risk evidence, resilience evidence, scenario evidence, continuity evidence, interdependency evidence, hazard evidence, exposure evidence, vulnerability evidence, capability evidence, control evidence, degraded-mode evidence, or corrective-action evidence within Nexus Risk Management interfaces.
8.7.9(b) Nexus Risk Management Outputs shall remain evidence and methods support. They shall not constitute public authority risk determinations, insurance ratings, credit ratings, investment ratings, project ratings, resilience ratings, regulatory findings, public warnings, emergency commands, finance-readiness, guarantees, procurement approval, provider endorsement, sponsor approval, certification, recognition, protocol effect, operational clearance, or execution consequence by default.
8.7.9(c) Nexus Risk Management Outputs shall identify risk question, source records, method records, scenario assumptions where any, model records where any, evidence class, data class, confidence, uncertainty, limitations, public-safe status, finance-safe status where material, public authority-facing status where material, access class, handling class, permitted use, prohibited use, boundary language, correction path, supersession path, withdrawal path, and dependency links.
8.7.9(d) Scenario outputs, risk indicators, resilience indicators, dashboard outputs, maps, scores, and model-based outputs shall be described as decision support and shall not be represented as decisions, official risk ratings, insurance decisions, credit decisions, public authority findings, public warnings, or operational commands.
8.7.9(e) Nexus Risk Management Outputs used in GRF, GRA, public authority, National Consortium, National Company, Project SPV, provider, sponsor, host, community, or capital-reader interfaces shall preserve role separation and shall not exceed the authority of the source record.
8.7.9(f) Nexus Risk Management Outputs shall not create investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, certification, recognition, finance-readiness, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, market authority, infrastructure operation, or execution consequence by default.
8.7.9(g) Where a Nexus Risk Management Output is corrected, disputed, downgraded, reclassified, restricted, superseded, withdrawn, or retracted, GCRI Canada shall update applicable records and review affected downstream dependencies.
8.7.9(h) The controlling rule shall be that Nexus Risk Management Outputs support risk understanding without becoming risk authority.
8.7.10 Nexus Rails Output. 8.7.10(a) GCRI Canada may classify a Nexus Truth Engine output as a Nexus Rails Output where the output is prepared to support evidence routing, public-safe routing, standards-support routing, finance-readiness input routing, deployment-readiness evidence routing, GRF handoff, GRA handoff, Protocol Authority handoff, public authority learning handoff, National Company interface, Project SPV interface, provider interface, host interface, community interface, or correction routing within Nexus Rails.
8.7.10(b) Nexus Rails Outputs shall remain routing, translation, evidence, and handoff support artifacts. They shall not constitute finance-readiness, investment advice, securities solicitation, brokerage, lending, underwriting, insurance placement, rating, guarantee, public finance approval, procurement approval, provider endorsement, public authority decision, certification, recognition, protocol effect, operational clearance, market authority, infrastructure operation, or execution consequence by default.
8.7.10(c) Nexus Rails Outputs shall identify source records, method records, routing purpose, handoff actor, receiving actor, authority mapping, public-safe status, finance-safe status where material, public authority-facing status where material, access class, handling class, confidence, uncertainty, limitations, permitted use, prohibited use, boundary notices, handoff record, correction path, supersession path, withdrawal path, and dependency links.
8.7.10(d) Rails outputs involving GRA, capital readers, National Companies, Project SPVs, providers, public finance actors, insurers, lenders, underwriters, or other finance-adjacent actors shall include no-advice, no-solicitation, no-rating, no-guarantee, no-public-finance-approval, and no-capital-commitment controls where material.
8.7.10(e) Rails outputs involving public authorities shall include non-delegation, non-endorsement, non-procurement, non-funding, non-public-finance, non-regulatory, non-warning, and non-emergency-command controls where material.
8.7.10(f) Nexus Rails Outputs shall not create certification, recognition, finance-readiness, investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.7.10(g) Where a Nexus Rails Output is corrected, disputed, downgraded, reclassified, restricted, superseded, withdrawn, or retracted, GCRI Canada shall update applicable handoff and dependency records and notify affected interfaces where required.
8.7.10(h) The controlling rule shall be that Nexus Rails Outputs route evidence and handoffs; they do not execute the consequences to which evidence may be routed.
8.7.11 Academy and Training Output. 8.7.11(a) GCRI Canada may classify a Nexus Truth Engine output as an Academy and Training Output where the output is prepared for evidence literacy, methods training, AI governance literacy, cybersecurity literacy, public authority literacy, observability methods training, confidence and uncertainty training, public-safe publication training, controlled vocabulary training, correction training, or public-good technical training.
8.7.11(b) Academy and Training Outputs may include curricula, training notes, case studies, simulation materials, scenario materials, technical explainers, public-safe examples, controlled examples, lab materials, exercises, model cards for teaching, benchmark cards for teaching, dashboard demonstrations, map demonstrations, evidence pack examples, decision pack examples, correction examples, and public-safe glossaries.
8.7.11(c) Academy and Training Outputs shall identify audience, purpose, source records where applicable, synthetic or example status where applicable, public-safe status, access class, handling class, permitted use, prohibited use, confidence where material, uncertainty where material, limitations, IP status, data status, AI-use status, public authority boundary language, finance boundary language, provider-neutrality language, sponsor non-control language, credential boundary language, and correction path.
8.7.11(d) Academy and Training Outputs shall not create professional certification, licensure, public authority qualification, procurement preference, provider status, sponsor status, finance-readiness, investment suitability, regulated professional advice, technical certification, recognition, maturity record, protocol effect, operational clearance, or execution authority by default.
8.7.11(e) Attendance, completion, participation, fellowship, lab involvement, badge, certificate of attendance, training record, or Academy listing shall not imply certification, recognized competence, public authority qualification, procurement status, provider approval, finance-readiness, Nexus-compatible status, or execution readiness unless separately and lawfully created by proper authority and record.
8.7.11(f) Academy and Training Outputs shall not create investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.7.11(g) Where Academy and Training Outputs become inaccurate, stale, unsafe, overclaimed, misclassified, or misused, GCRI Canada shall correct, supersede, withdraw, reissue, relabel, restrict, or update the materials and related training records.
8.7.11(h) The controlling rule shall be that Academy and Training Outputs build literacy and competence without creating regulated credentials or downstream authority by default.
8.7.12 Dashboard, Map, Report, API, Dataset, Evidence Pack, Decision Pack, and Technical Annex Output. 8.7.12(a) GCRI Canada may classify Nexus Truth Engine outputs by form, including dashboard output, map output, report output, API output, dataset output, Evidence Pack output, Decision Pack output, technical annex output, controlled annex output, public-safe summary output, public-good software output, technical baseline output, model output, benchmark output, system card output, and correction notice output.
8.7.12(b) Dashboard Outputs shall identify source records, update frequency, latency, confidence display, uncertainty display, limitations, filters, labels, colors, scores, boundary language, public-safe status, access class, handling class, permitted use, prohibited use, and correction path.
8.7.12(c) Map Outputs shall identify geospatial source records, resolution, aggregation, safe-location treatment, sensitive-site treatment, community-identifiability treatment, infrastructure-sensitive treatment, public-safe status, uncertainty, limitations, public warning boundary, public authority boundary, permitted use, prohibited use, and correction path.
8.7.12(d) Report Outputs shall identify purpose, audience, source records, method records, confidence, uncertainty, limitations, redactions, responsible non-disclosure basis, public-safe status, boundary language, permitted use, prohibited use, correction path, supersession path, withdrawal path, and archive path.
8.7.12(e) API Outputs shall identify endpoint purpose, data class, evidence class, source records where applicable, schema version, ontology version, access class, rate limits where any, permitted use, prohibited use, public-safe status, machine-readable boundary language, correction path, deprecation path, and versioning status.
8.7.12(f) Dataset Outputs shall identify dataset source, owner where known, custodian, steward, data class, evidence class, technology domain, purpose, lawful basis or authority where applicable, permissions, licenses, consent or non-consent treatment where applicable, AI-use status, training-use status, embedding-use status, transfer status, publication status, retention status, quality, completeness, limitations, public-safe status, and correction path.
8.7.12(g) Evidence Pack Outputs and Decision Pack Outputs shall identify purpose, audience, source records, method records, evidence classes, data classes, confidence, uncertainty, limitations, review status, authority mapping where applicable, permitted use, prohibited use, boundary language, correction path, supersession path, withdrawal path, retraction path where applicable, closeout path where applicable, and dependency links.
8.7.12(h) Technical Annex Outputs and Controlled Annex Outputs shall identify technical scope, sensitive content class, access class, handling class, source records, method records, models where any, data where any, limitations, public-safe summary relationship, permitted use, prohibited use, confidentiality, cybersecurity controls, privacy controls, sovereign data controls, protected knowledge controls, and correction path.
8.7.12(i) Outputs by form shall not create certification, recognition, finance-readiness, investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.7.12(j) The controlling rule shall be that output form affects access, risk, and review, but no form transforms evidence into authority by default.
8.7.13 Output Class Controls, Review Requirements, Access Rights, Disclaimers, Versioning, and Correction Paths. 8.7.13(a) GCRI Canada shall maintain output class controls for Nexus Truth Engine outputs, including classification rules, review requirements, access rights, handling rules, disclaimer requirements, boundary-language requirements, versioning requirements, correction paths, supersession paths, withdrawal paths, retraction paths, archive paths, and dependency-tracking requirements.
8.7.13(b) Output class controls shall be proportionate to source sensitivity, evidence class, data class, technology domain, public-safe status, audience, intended use, prohibited use, public authority relevance, finance relevance, provider relevance, sponsor relevance, community relevance, protected knowledge relevance, cybersecurity relevance, privacy relevance, sovereign data relevance, and downstream dependency.
8.7.13(c) Review requirements may include evidence steward review, method steward review, data steward review, model steward review, observability steward review, ontology review, controlled vocabulary review, public-safe publication review, privacy review, cybersecurity review, AI review, sovereign data review, public authority boundary review, finance boundary review, provider-neutrality review, sponsor non-control review, safeguards review, legal review, interface review, committee review, officer approval, or Board reporting.
8.7.13(d) Access rights shall identify who may view, use, quote, export, reproduce, rely upon, modify, route, publish, summarize, embed, API-call, dashboard-view, map-view, train on, retrieve from, translate, localize, or otherwise process the output.
8.7.13(e) Disclaimers and boundary language shall address, where material, no certification, no recognition, no finance-readiness, no investment advice, no public authority decision, no procurement approval, no provider endorsement, no sponsor approval, no rating, no guarantee, no public warning, no emergency command, no protocol effect, no operational clearance, no legal status, no professional advice, no market authority, no infrastructure operation, and no execution consequence.
8.7.13(f) Versioning shall identify version number or identifier, effective date, prior version, superseding version, status, change basis, reviewer, approving actor where applicable, affected dependencies, correction relationship, withdrawal relationship, retraction relationship, and archive treatment.
8.7.13(g) Correction paths shall identify how an output may be challenged, corrected, reclassified, restricted, downgraded, superseded, withdrawn, retracted, suspended, reinstated, retired, archived, and notified to affected downstream users.
8.7.13(h) Output class controls shall prevent output migration. An output approved for one class shall not automatically be used in another class without reclassification, review, boundary treatment, and records-valid approval.
8.7.13(i) The controlling rule shall be that output classes must control how Truth Engine artifacts are used, by whom, for what purpose, under what boundary, and with what correction path.
8.7.14 Output Class Register and Public-Safe Output Catalogue. 8.7.14(a) GCRI Canada shall maintain, or cause to be maintained, an Output Class Register for material Nexus Truth Engine outputs and may maintain a Public-Safe Output Catalogue for outputs approved for public-safe release.
8.7.14(b) The Output Class Register shall identify output title or identifier, output class, output form, purpose, audience, owner, custodian, steward, source records, method records, data class, evidence class, technology domain, risk domain, version, status, classification, access class, handling class, public-safe status, finance-safe status where material, public authority-facing status where material, GRF-facing status where material, GRA-facing status where material, Protocol Authority-facing status where material, provider-facing status where material, sponsor-facing status where material, host-facing status where material, community-facing status where material, confidence, uncertainty, limitations, permitted use, prohibited use, boundary language, review status, correction path, supersession path, withdrawal path, retraction path where applicable, archive path, and dependency links.
8.7.14(c) The Public-Safe Output Catalogue may identify public-safe reports, public-safe summaries, public dashboards, public maps, public-safe technical notes, public-safe glossaries, public-safe Academy materials, public-good software documentation, technical baseline summaries, public-safe correction notices, public-safe Observatory summaries, public-safe Truth Engine summaries, public-safe Docket summaries, public-safe Grid summaries, and public-safe Rails summaries.
8.7.14(d) The Public-Safe Output Catalogue shall not include restricted evidence, controlled annexes, personal information, rights-bearing data, cyber-sensitive information, infrastructure-sensitive information, public authority restricted information, sovereign-sensitive information, protected knowledge, community-sensitive information, confidential source information, controlled technology, unsafe geospatial detail, or other material not approved for public-safe release.
8.7.14(e) Catalogue inclusion shall not create certification, recognition, finance-readiness, investment advice, public authority decision, procurement approval, provider endorsement, sponsor approval, rating, guarantee, public warning, emergency command, protocol effect, operational clearance, legal status, professional advice, market authority, infrastructure operation, or execution consequence by default.
8.7.14(f) Where an output in the Output Class Register or Public-Safe Output Catalogue is corrected, challenged, reclassified, restricted, superseded, withdrawn, retracted, downgraded, suspended, reinstated, retired, or archived, the register or catalogue shall be updated and affected downstream dependencies shall be reviewed.
8.7.14(g) The Output Class Register and Public-Safe Output Catalogue shall support auditability, public-safe legibility, controlled access, dependency tracking, interface assurance, correctionability, and institutional memory.
8.7.14(h) The controlling rule shall be that Truth Engine outputs must be catalogued by class because output meaning depends on class, audience, access, status, limitations, and correction path.